Vehicle type project management method and device, electronic equipment and storage medium

Abstract

The invention relates to a vehicle type project management method and device, electronic equipment and a storage medium. The method comprises the following steps: when a creation request of a vehicle type project is received, obtaining a plurality of key nodes of a pre-configured vehicle type project and time points of the key nodes, and associating the time points of the key nodes with safety activities of the vehicle type project; creating and executing a vehicle type project; when it is monitored that the current time point reaches the time point of the target key node, obtaining a time window of the safety activity of the vehicle type item; acquiring associated data of the security activity based on the time window of the security activity; determining a risk project and a disposal mode of the risk project according to the associated data of the safety activity; and generating a compliance report of the vehicle type item according to the associated data of the safety activity. By adopting the method, the full-life-cycle standardized and automatic management of the vehicle type project can be realized.

Description

Technical Field

[0001] This application relates to the field of data processing application technology, and in particular to a vehicle model project management method, apparatus, electronic device, and storage medium. Background Technology

[0002] As the automotive industry becomes increasingly intelligent and connected, cybersecurity activities during vehicle development are becoming more complex. Currently, the industry generally adopts a decentralized management model, with related tasks relying on paper work orders, independent spreadsheets, or multiple unrelated software systems for segmented execution, and a unified management mechanism that runs through the entire project lifecycle has not yet been formed.

[0003] In this model, the lack of an effective electronic link between the overall project schedule and key security milestones easily leads to a disconnect between cybersecurity activities and project milestones, posing a risk of delays for critical tasks. Risk identification relies heavily on manually compiling fragmented records, making it difficult to promptly identify and respond to high-risk vulnerabilities. During compliance verification, engineers must manually review numerous regulatory texts and annotate each item, consuming significant human resources and posing a risk of incomplete coverage. Summary of the Invention

[0004] Therefore, it is necessary to provide a vehicle model project management method, device, electronic equipment, and storage medium to address the aforementioned technical issues, enabling standardized and automated management of the entire lifecycle of vehicle model projects.

[0005] According to a first aspect of certain exemplary embodiments of the present disclosure, a vehicle model project management method is provided, comprising: upon receiving a vehicle model project creation request, obtaining multiple key nodes of a pre-configured vehicle model project and the time points of each key node, and associating the time points of each key node with the safety activities of the vehicle model project; creating and executing the vehicle model project; upon detecting that the current time point has reached the time point of a target key node, obtaining the time window of the safety activities of the vehicle model project; obtaining associated data of the safety activities based on the time window of the safety activities; determining risk projects and the handling methods of risk projects based on the associated data of the safety activities; and generating a compliance report of the vehicle model project based on the associated data of the safety activities.

[0006] According to certain exemplary embodiments of this disclosure, obtaining the time window for safety activities of a vehicle model project includes: obtaining the end time of the time window corresponding to the previous key node of the target key node; and determining the time window for safety activities based on the end time of the time window corresponding to the previous key node and the current time point.

[0007] According to certain exemplary embodiments of this disclosure, creating and executing a vehicle model project includes: creating safety activity tasks for the vehicle model project based on a predefined safety activity template, and assigning the safety activity tasks to a corresponding first responsible person so that the first responsible person executes the safety activity tasks for the vehicle model project; monitoring the execution progress of the safety activity tasks for the vehicle model project, and generating an approval list for the safety activity tasks based on the execution progress; sending the approval list to a second responsible person so that the second responsible person approves the approval list; and confirming that the safety activity tasks have been completed in response to the second responsible person's approval of the approval list.

[0008] According to certain exemplary embodiments of this disclosure, generating a compliance report for a vehicle model project based on associated data of safety activities includes: extracting deliverables generated by safety activities from the associated data of safety activities, and converting the text content of the deliverables into a word vector space model; obtaining multiple regulatory clauses from a preset regulatory library and identifying key constraints of each regulatory clause; calculating the semantic matching degree between the word vector space model and each key constraint; determining target regulatory clauses based on the semantic matching degree, and determining the compliance level of the safety activity based on the target regulatory clauses; determining one or more compliance deviations of the safety activity based on the compliance level, and generating associated rectification information for each compliance deviation in combination with the key constraints of the target clauses; and generating a compliance report for the vehicle model project based on the compliance level, each compliance deviation, and the associated rectification information.

[0009] According to certain exemplary embodiments of this disclosure, a vehicle model project management method further includes: archiving associated data and compliance reports of safety activities according to a preset hierarchical structure to generate archive files; generating digital fingerprints of the archive files through an encryption processing algorithm; obtaining operation logs of safety activities; packaging the archive files, the digital fingerprints of the archive files, and the operation logs to generate audit data packets; and storing the audit data packets on a blockchain.

[0010] According to certain exemplary embodiments of this disclosure, a vehicle model project management method further includes: upon detecting a request to create a new vehicle model project, obtaining verified historical security activity templates and project assets associated with each template; filtering out matching target historical security activity templates and project assets associated with the target historical security activity templates based on the development requirements of the new vehicle model project; and generating security activity tasks for the new vehicle model project based on the target historical security activity templates and project assets associated with the target historical security activity templates.

[0011] According to a second aspect of certain exemplary embodiments of the present disclosure, a vehicle model project management device is provided, characterized in that the device comprises: a first acquisition module, configured to acquire, upon receiving a vehicle model project creation request, a plurality of pre-configured key nodes of the vehicle model project and the time points of each key node, and associate the time points of each key node with the safety activities of the vehicle model project; an execution module, configured to create and execute the vehicle model project; a second acquisition module, configured to acquire the time window of the safety activities of the vehicle model project when the current time point is detected to have reached the time point of the target key node; a third acquisition module, configured to acquire associated data of the safety activities based on the time window of the safety activities; a determination module, configured to determine risky projects and the handling methods of risky projects based on the associated data of the safety activities; and a first generation module, configured to generate a compliance report of the vehicle model project based on the associated data of the safety activities.

[0012] According to a third aspect of certain exemplary embodiments of the present disclosure, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of any of the above methods.

[0013] According to a fourth aspect of certain exemplary embodiments of the present disclosure, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the steps of any of the above methods.

[0014] According to a fifth aspect of certain exemplary embodiments of the present disclosure, a computer program product is provided, the computer program product including computer instructions stored in a computer-readable storage medium, the computer instructions implementing the steps of any of the methods described above when read from and executed by a processor from the computer-readable storage medium.

[0015] The aforementioned vehicle model project management method, apparatus, electronic device, and storage medium, upon receiving a vehicle model project creation request, acquire multiple pre-configured key nodes of the vehicle model project and the time points of each key node, and associate the time points of each key node with the safety activities of the vehicle model project; create and execute the vehicle model project; when the time point of the target key node is detected to be reached at the current time point, acquire the time window of the safety activities of the vehicle model project; acquire the associated data of the safety activities based on the time window of the safety activities; determine the risk projects and the handling methods of the risk projects based on the associated data of the safety activities; and generate a compliance report for the vehicle model project based on the associated data of the safety activities.

[0016] Therefore, by linking key milestones with the security activities of a vehicle project, a linkage mechanism between project progress and security activities can be established. This eliminates the time discrepancy between cybersecurity activities and key milestones (such as milestones) in the vehicle project, avoiding the risk of delays in critical tasks and improving the efficiency and accuracy of vehicle project management. By acquiring relevant data from security activities within their time windows, and then automatically determining risk items and their handling methods based on this data, compared to the traditional risk identification model that relies on manually compiling fragmented records, this approach enables centralized integration and intelligent analysis of risk data from a technical perspective. This solves problems such as untimely discovery and delayed response to high-risk vulnerabilities, thereby achieving precise risk management. Furthermore, by automatically generating vehicle project compliance reports based on security activity-related data, compared to the traditional model that relies on engineers manually reviewing regulatory texts and marking each item for inspection, this approach not only significantly improves the efficiency of compliance verification and reduces labor costs but also ensures comprehensive coverage of regulatory clauses, effectively avoiding potential omissions. Through the synergistic linkage of these various stages, spanning the entire process of a vehicle project from creation, execution, risk management to compliance verification, standardized and automated management of the entire vehicle project lifecycle can be achieved. Attached Figure Description

[0017] Figure 1 This is a schematic diagram illustrating the application environment of a vehicle model project management method as shown in some exemplary embodiments of this disclosure. Figure 2 This is a flowchart illustrating a vehicle model project management method as one of the exemplary embodiments of this disclosure; Figure 3 This is a schematic diagram illustrating the process of creating and executing a vehicle model project in some exemplary embodiments of this disclosure; Figure 4 This is a flowchart illustrating the time window for obtaining safety activities for vehicle model items in some exemplary embodiments of this disclosure; Figure 5 This is a schematic diagram of a process for generating a compliance report for a vehicle model project based on associated data of safety activities, as illustrated in some exemplary embodiments of this disclosure. Figure 6 This is a schematic diagram of the process of hierarchical archive files in some exemplary embodiments of this disclosure; Figure 7 This is a flowchart illustrating the reuse of historical security activity templates in some exemplary embodiments of this disclosure; Figure 8 This is a structural block diagram of a vehicle model project management device according to some other exemplary embodiments of this disclosure; Figure 9 This is a diagram illustrating the internal structure of an electronic device in some other exemplary embodiments of this disclosure. Detailed Implementation

[0018] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0019] The following detailed descriptions are provided to aid the reader in gaining a comprehensive understanding of the methods, apparatus, electronic devices, storage media, and / or computer program products described herein. However, upon understanding the disclosure of this disclosure, various changes, modifications, and equivalents of the methods, apparatus, storage media, and / or computer program products described herein will become apparent. For example, the order of operations described herein is merely illustrative and is not limited to those orders set forth herein, but may be changed as will become clear upon understanding the disclosure of this disclosure, except for operations that must occur in a specific order. Furthermore, for clarity and conciseness, descriptions of features known in the art may be omitted.

[0020] The features described herein may be implemented in different forms and should not be construed as limited to the examples described herein. Rather, the examples described herein are provided only to illustrate some of the many feasible ways of implementing the methods, electronic devices, and / or storage media described herein, many of which will become clear upon understanding this disclosure.

[0021] The terminology used herein is for the purpose of describing various examples only and is not intended to limit disclosure. Unless the context clearly indicates otherwise, the singular form is intended to include the plural form as well. The terms “comprising,” “including,” and “having” indicate the presence of the described features, quantities, operations, components, elements, and / or combinations thereof, but do not exclude the presence or addition of one or more other features, quantities, operations, components, elements, and / or combinations thereof. Unless otherwise stated, “ / ” means “or,” for example, A / B can mean A or B; “and / or” in the text is merely a description of the relationship between related objects, indicating that three relationships can exist, for example, A and / or B can mean: A alone, A and B simultaneously, and B alone. Furthermore, in the description of embodiments of the invention, “multiple” means two or more.

[0022] Unless otherwise defined, all terms used herein (including technical and scientific terms) shall have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains upon understanding this disclosure. Unless expressly defined herein, terms (such as those defined in a general dictionary) shall be interpreted as having a meaning consistent with their meaning in the context of the relevant field and in this disclosure, and shall not be interpreted in an idealized or overly formalistic manner.

[0023] It should be noted that the terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this disclosure are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this disclosure described herein can be implemented in orders other than those illustrated or described herein. The embodiments described in some of the following exemplary embodiments do not represent all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appended claims.

[0024] Furthermore, in the description of the examples, detailed descriptions of well-known related structures or functions will be omitted when it is believed that such detailed descriptions would lead to a vague interpretation of this disclosure.

[0025] In the following description, embodiments will be described in detail with reference to the accompanying drawings. However, embodiments may be implemented in various forms and are not limited to the examples described herein.

[0026] The abbreviations and key terms in this disclosure are explained as follows: 1. Valve Point: A key time node and process control unit in the vehicle project management system that is strongly tied to project milestones. It is the core hub that connects safety activities, risk warnings, and deliverable management. 2. Deliverables: Standardized compliance deliverables generated during the execution of the vehicle model project are the core evidence carriers of project progress, risk management, and compliance, including penetration test reports, vulnerability remediation verification records, TARA risk assessment summaries, compliance audit reports, etc. 3. Threat Analysis and Risk Assessment (TARA) tool: Identifies potential threat scenarios for in-vehicle systems, analyzes attack paths and impact ranges, and outputs risk levels and handling recommendations. It is a core tool for vehicle safety compliance. 4. Common Vulnerability Scoring System (CVSS) scoring: Quantifies the risk level (0-10 points, ≥7.0 is high risk) by dimensions such as attack vector, complexity, and impact scope of the vulnerability, providing a basis for prioritizing vulnerability handling; 5. Application Programming Interface (API): A data interaction interface between different systems / modules (such as the interface between the vehicle project management system and the TARA tool), supporting standardized data transmission and function calls; 6. Blockchain technology: an immutable technology based on cryptography and distributed ledgers. It stores data through multi-node consensus to ensure that the data is traceable and cannot be forged throughout the entire process. It is often used for compliance evidence chain storage in vehicle project (such as signatures of delivered items and solidification of operation logs). 7. Start of Production (SOP) Node: A key milestone in the transition of a vehicle project from the development and verification phase to the mass production phase. It signifies that the vehicle has completed all design verifications, compliance checks, and risk closure, and is ready for mass production.

[0027] This application provides a vehicle model project management method, applicable to, for example... Figure 1 The application environment shown. For example... Figure 1 As shown, the vehicle model project management system 20 is used to execute a vehicle model project management method according to this application. Specifically, when a user initiates a vehicle model project creation request on a terminal device 10, the vehicle model project management system 20, upon receiving the request, obtains multiple key nodes of the pre-configured vehicle model project and the time points of each key node, and associates the time points of each key node with the safety activities of the vehicle model project; creates and executes the vehicle model project; when it detects that the current time point has reached the time point of the target key node, it obtains the time window of the safety activities of the vehicle model project; obtains the associated data of the safety activities based on the time window; determines the risk projects and their handling methods based on the associated data of the safety activities; and generates a compliance report for the vehicle model project based on the associated data of the safety activities. The terminal device 10 can be a mobile phone, tablet computer, etc.

[0028] In some exemplary embodiments of this disclosure, such as Figure 2 As shown, a vehicle model project management method is provided. Taking the application of this method to an electronic device in a vehicle model project management system 20 as an example, the method includes the following steps: Step 201: Upon receiving a request to create a vehicle model project, obtain multiple key nodes of the pre-configured vehicle model project and the time points of each key node, and associate the time points of each key node with the security activities of the vehicle model project.

[0029] Specifically, when an electronic device receives a vehicle model project creation request submitted by a user through the central console of project details, the vehicle model project management system first extracts core information from the request, such as the vehicle model code, project cycle, and contact person. It then obtains multiple key nodes of the pre-configured vehicle model project and the time points of each key node, performs information integrity and validity checks, and initiates automatic time verification logic (ensuring that the time points of subsequent key nodes are later than those of previous nodes). After successful verification, it establishes a mapping between the time points of each key node and the safety activities of the vehicle model project, and assigns a unique identifier to each project threshold. Further, the vehicle model project management system associates the time points of key nodes with the safety activities of the vehicle model project through the following steps, and automatically updates the associated data of the vehicle model project, such as recalculating the remaining days in the project overview countdown component, adjusting the warning thresholds in the project risk module, and automatically updating the deliverable submission deadline.

[0030] In some embodiments, when a vehicle model project is detected as not yet created, the vehicle model project management system locks the entry point of the target functional module until a vehicle model project creation request is received, at which point the target functional module is generated and activated. The target functional module may include a project details module, a security activity module, and a project risk module. The electronic device first receives project creation application information submitted by the user through the project details central console. This information must include the vehicle model code (a 6-digit alphanumeric combination, such as "NEV2025"), the project period (the system automatically verifies the date logic to ensure the end time is later than the start time), and the contact person (associated with the enterprise OA system identity database, matching a real, currently employed employee account). After submission, the vehicle model project management system monitors the creation status of the vehicle model project in real time through an access control engine.

[0031] When no vehicle model project creation request is received, such as when a user only enters the creation page but does not submit an application or the application information fails verification, the vehicle model project management system will automatically lock the functional entry points of target modules such as the project details module, safety activity module, and project risk module. Specifically, when the user clicks the module icon, there is no response, and a warning message pops up on the interface: "Please create a vehicle model project first to activate system functions." This prevents unauthorized operations without project approval and meets the core requirement of "separation of permissions" in the UNECE R155 regulation. After receiving a vehicle model project creation request, the vehicle model project management system will immediately execute the generation and activation process of the target functional modules. For example, it will generate a globally unique project ID (exemplary format is CP_[vehicle model code][date][serial number], such as CP_NEV2025_20260315_001, which can also be customized according to enterprise needs), and simultaneously initialize the database relationship tables of the three major modules (including fields: project ID, module identifier, initial status, and creation time), completing the module function activation. Users can then normally enter each module for subsequent operations. In addition, the project ID generated in this step can serve as the primary key for the entire lifecycle data of the vehicle project, running through subsequent processes such as valve point configuration, safety activity execution, risk management, and deliverable archiving, ensuring the consistency and traceability of the data chain.

[0032] In one example, the security activity module is used to generate activity tasks for security activities based on predefined security activity templates and associate the activity tasks with the corresponding responsible persons. The types of security tasks include one or more of penetration testing, vulnerability scanning, and security requirement verification.

[0033] Specifically, after the security activity module is activated, upon receiving the user's selected predefined security activity template (such as "New Energy Vehicle CSMS Template V3.1"), the vehicle project management system will call the template verification interface to confirm that the template contains a complete definition of cybersecurity activities (at least including three core tasks: penetration testing, vulnerability scanning, and security requirement verification). If the template is missing any task type, it will prompt "The template is incomplete. Please select again or supplement the configuration". Once the template verification is successful, the security activity module automatically generates a task work order (e.g., "ECU Firmware Verification_TASK2026_001") based on the predefined security activity template. The work order can include key information such as task description (e.g., "Verify the validity of the ECU firmware signature to prevent malicious tampering"), expected deliverables (e.g., "Firmware Signature Test Report V1.0"), and reference standards (e.g., "ISO 21434 Clause 9.2"). At the same time, the vehicle project management system will call the role-member mapping table built into the project settings module to match the corresponding responsible person according to the task type. For example, penetration testing tasks are bound to the "Security Test Engineer" role member, vulnerability scanning tasks are bound to the "Vulnerability Management Specialist" role member. In this example, the ECU firmware verification task automatically matches the "Security Manager" role member in the role library (responsible for key task review and progress control), and pushes a task to-do notification to the responsible person's OA account, and simultaneously generates a "Pending Task" reminder on the system workbench.

[0034] In another embodiment, the project details module serves as the central console for project management. Upon activation, it automatically loads one or more of the following sub-modules: Project Overview, Security Activities, Project Assets, Risk Assessment, Deliverables, Risk Control, Activity Logs, Compliance Evidence Chain, and Project Settings. This enables the aggregation and refined management of comprehensive data across all vehicle model projects. Specifically, the Project Overview sub-module aggregates basic project information (such as vehicle model code and cycle), security activity completion rate, and risk quantity statistics in real time, displaying the overall project progress intuitively in a dashboard format. The Project Assets sub-module initializes the hardware resource inventory library (supporting component information entry) and software version library (recording software iteration history), providing an asset foundation for subsequent vulnerability association and risk tracing. The Compliance Evidence Chain sub-module creates a deliverable storage directory (which can be divided by project-stage hierarchy), supporting the uploading and version management of subsequent audit reports and test reports. The Project Settings sub-module provides entry points for threshold time configuration, role and permission allocation, and security activity template adjustment, offering configuration support for personalized project control. All sub-modules are linked through tab switching, with core data synchronized in real time, avoiding information fragmentation and improving project management efficiency.

[0035] In another embodiment, after the project risk module is activated, it can automatically connect to the API interface of the TARA tool, configure data synchronization rules (such as receiving structured risk data in real time and updating residual risk information hourly) to ensure that the risk data source is compliant and real-time; it has built-in risk classification standards, such as the judgment standards for technical risks and process risks, to provide a basis for subsequent risk identification; it activates the early warning function, and when the preset risk early warning threshold is reached (such as "high-risk risks not handled for more than 24 hours triggers an early warning"), it configures notification channels (such as system pop-ups, SMS, etc.) and initializes a risk visualization view to facilitate users to quickly locate high-priority risks.

[0036] Step 202: Create and execute the vehicle model project.

[0037] Specifically, once the target functional modules of a vehicle model project are activated and the key nodes and safety activities are associated, the vehicle model project management system generates and executes the vehicle model project.

[0038] In some exemplary embodiments of this disclosure, based on the above embodiments, a specific implementation method for creating and executing a vehicle model project is further described. That is, as follows... Figure 3 As shown, the steps to create and execute a vehicle model project can specifically include the following steps: Step 301: Create safety activity tasks for the vehicle model project based on the predefined safety activity template, and assign the safety activity tasks to the corresponding primary responsible persons so that the primary responsible persons can perform the safety activity tasks for the vehicle model project.

[0039] Step 302: Monitor the execution progress of safety activities for the vehicle model project and generate an approval list for safety activities based on the execution progress.

[0040] Step 303: Send the approval list to the second responsible person so that the second responsible person can approve the approval list.

[0041] Step 304: In response to the second responsible person's approval of the approval list, confirm that the safety activity task has been completed.

[0042] Specifically, firstly, based on the basic information of the predefined safety activity template (such as associated project ID, activity type, preset responsible person role, etc.), the system automatically creates safety activity tasks for vehicle model projects (including core elements such as task description, execution standards, expected deliverables, and time requirements), and assigns the task work orders to the corresponding primary responsible persons through the system's built-in role-member mapping rules. Then, the vehicle model project management system monitors the execution progress of the safety activity tasks for vehicle model projects in real time. When the system detects that the safety activity task has progressed to the preset approval node (such as after the task is completed or the deliverables are submitted), it automatically extracts the task execution data (including completion status, deliverable verification results, process records, etc.) and generates an approval list for the safety activity task (i.e., OA approval form). The OA approval form includes core fields such as a globally unique project ID (e.g., “CP_NEV2025_20260315_001”), a security activity number (e.g., “Penetration Test_TASK2026_003”), the roles of the primary and secondary responsible persons (e.g., “Security Test Engineer”, “Security Manager”), the project threshold time corresponding to the activity (e.g., “SOP Threshold = 2026-12-31”), and the expected deliverables of the activity (e.g., “Penetration Test Report V1.0”), ensuring that the approval information is highly matched with the actual needs of the project.

[0043] Furthermore, the vehicle model project management system pushes OA approval forms to the second responsible person via the Enterprise Service Bus (ESB), simultaneously triggering approval reminders (such as system workbench pop-ups and OA message notifications) so that the second responsible person can promptly perform the approval operation. In response to the second responsible person's approval of the approval list, the vehicle model project management system automatically marks the security activity task status as "completed" and archives the entire task execution process data (including work orders, deliverables, and approval records) to the project deliverables module. In some embodiments, when the completion of the security activity task is confirmed, the progress bar in the project overview module is also updated simultaneously (e.g., after the "Vehicle System Penetration Testing" task is approved, the "Security Testing Phase" progress bar updates from 0% to 20%). If there are still related tasks, the system will automatically generate the next stage of pending tasks and push them to the corresponding responsible person. These pending tasks must be verified by digital signature (using the RSA 2048 algorithm) before execution can begin, ensuring the non-repudiation of task operations. If the approval fails, the system will display a red warning box on the corresponding activity interface in the security activity module, clearly indicating the reason for rejection (such as "not associated with TARA risk assessment ID" or "test report missing key data appendix"), and guide the user to supplement and improve the materials; after the user corrects the materials, he / she will re-initiate the security activity approval instruction, and the system will regenerate and push the OA approval form according to the above process.

[0044] Therefore, by deeply linking the activity status of security activities with the approval status of OA approval forms, standardized control of the security activity initiation process and real-time linkage of project data are achieved. When approval is granted, the execution progress of the security activity is updated synchronously, ensuring that the project team has a consistent understanding of the activity's progress; when approval is rejected, the reason for rejection is clearly stated so that users can quickly correct the problem and avoid repeated trial and error. This ensures both the compliance and traceability of security activity initiation and the global consistency of project management data through status linkage, solving the problems of disconnect between approval status and project progress and untimely information transmission in traditional email or general office systems.

[0045] Step 203: When the time point at which the target critical node is reached is detected, obtain the time window of the safety activities of the vehicle model project.

[0046] Specifically, the vehicle model project management system monitors the matching status of the current system time with the time points of each key node in real time through the timed task component. When it detects that the current time point has reached the target key node time point, it triggers the calculation process of the safety activity time window, thereby obtaining the time window of the corresponding safety activity for the vehicle model project.

[0047] In some exemplary embodiments of this disclosure, based on the above embodiments, a specific implementation method for obtaining the time window of safety activities for vehicle model projects is further described. That is, as follows... Figure 4 As shown, the steps for obtaining the time window of safety activities for a vehicle model project may specifically include the following steps: Step 401: Obtain the end time of the time window corresponding to the previous key node of the target key node.

[0048] Step 402: Determine the time window for security activities based on the end time of the time window corresponding to the previous critical node and the current time point.

[0049] Specifically, the system first obtains the end time of the time window corresponding to the previous key node of the target key node (such as the SOP node) by querying the project configuration database. For example, the vehicle model project management system first generates a precise database query statement based on the globally unique ID of the vehicle model project to be processed (such as CP_NEV2025_20260315_001) to locate the key node configuration table corresponding to the project; then, it filters out the target key node (such as the SOP node, identified as "SOP_20261231") in the configuration table, and then queries the information of its associated previous key node (such as the trial production node, identified as "PilotRun_20261031") through the node hierarchy association field (such as "prev_node_id"); then, it extracts the time window configuration record corresponding to the previous key node and obtains the end time of the node's time window (such as "2026-10-31 23:59:59"). If the query results show that the target key node has no associated preceding key node (i.e., the node is the first key node of the project, such as the project start node), the official start time of the vehicle model project (such as "2026-01-01 00:00:00") will be automatically retrieved from the project basic information table and used as the base time equivalent to "the end time of the previous key node time window".

[0050] After obtaining the baseline time (the end time of the preceding node time window or the project start time), the system further retrieves the preset fixed buffer period parameter (such as 15 calendar days, which can be customized by the enterprise according to the project type) from the project configuration database; combined with the preset time point of the target critical node itself (such as the SOP node time "2026-12-31"), the system calculates the time window of the security activity through the built-in scheduling algorithm: the start time of the time window directly adopts the above-mentioned baseline time (the end time of the preceding node time window or the project start time), and the end time of the time window is calculated by "target critical node time point - fixed buffer period". For example, if the deadline for the preceding trial production node is October 31, 2026, the deadline for the SOP node is December 31, 2026, and the fixed buffer period is 15 days, then the start time of the safety activity time window is October 31, 2026, and the end time is December 31, 2026 minus 15 days, which is December 16, 2026. Therefore, the execution time window for this safety activity is determined to be from 00:00:00 on October 31, 2026 to 23:59:59 on December 16, 2026.

[0051] In addition, the vehicle model project management system will monitor the changes in key node times in the project configuration database in real time through scheduled tasks. If the target key node time or the time of the preceding key node is modified (such as the SOP time being adjusted to 2027-01-15), the above query and calculation process will be automatically triggered to regenerate the time window of the safety activity and update it synchronously in the safety activity module, the project overview module and the task reminders of the relevant responsible persons. This ensures that the execution time of the safety activity is always dynamically synchronized with the progress of the project's key nodes and avoids the safety activity from becoming disconnected from the project milestones due to node time adjustments.

[0052] Step 204: Obtain associated data of security activities based on the time window of the security activities.

[0053] Specifically, the vehicle model project management system can obtain relevant data such as task execution data, vulnerability detection data, asset association data, and risk assessment data corresponding to security activities within the time window, from multiple sources such as the security activity module, project asset module, TARA tool, and vehicle vulnerability scanning tool. At the same time, the system performs format standardization processing and duplicate data removal on the obtained data to ensure the validity and consistency of the relevant data.

[0054] Step 205: Determine the risk items and the handling methods for the risk items based on the associated data of the security activities.

[0055] Specifically, the vehicle model project management system performs multi-dimensional fusion analysis based on the associated data of acquired security activities (such as task execution data, vulnerability detection data, asset association data, risk assessment data, etc. corresponding to security activities within a time window), combined with a predefined risk judgment rule base, to accurately identify risky projects. First, the vehicle model project management system calls the risk identification engine to compare task execution data with preset task completion standards, filtering out process-related abnormal data such as "task overdue and incomplete" and "deliverables missing key elements." At the same time, it analyzes vulnerability detection data and risk assessment data, matching the corresponding risk types (such as "communication protocol not encrypted" and "ECU access control failure" corresponding to technical risks, and "TARA assessment score ≥ 7.0" corresponding to high-risk risks), locking down risky projects with potential security vulnerabilities, and marking the risk type (technical / process), risk level (high / medium / low), and associated security activities and project asset information.

[0056] After identifying risky projects, the vehicle project management system automatically matches differentiated handling methods based on the risk type and level. For example, if the risk is identified as technical, the risk assessment submodule's classification interface is called to further confirm the risk level, generating a targeted technical handling plan (such as "upgrading the TLS 1.3 communication protocol" or "optimizing the ECU permission allocation strategy"). A tracking work order is created in the risk control module and pushed to the responsible person in the technical R&D team, requiring them to submit progress reports by a preset time limit. After the repair is completed, it must be verified by a second detection using an onboard vulnerability scanning tool to ensure a closed-loop risk management system. If the risk is process-related, a standardized process defect record is generated, clearly defining the defective link (such as the task approval link or the deliverable archiving link) and rectification requirements. A three-level early warning mechanism is triggered (responsible person's workbench pop-up, safety officer's SMS notification, and project management committee's email reminder). At the same time, the defect details and processing time limit are fully recorded in the activity log module. Failure to rectify within the time limit will be linked to project performance indicators. After rectification, it must be reviewed and confirmed by a compliance auditor to ensure process compliance and traceability.

[0057] Therefore, by accurately identifying risk items and different handling methods for risk items through the correlation data of safety activities, full-cycle management of safety activity risks can be achieved; by adopting a dual risk handling path for technical and process risks, the problems of data lag, ambiguous types, and inefficient handling in traditional risk management can be solved, ensuring timely repair of technical vulnerabilities and compliant rectification of process defects, and providing strong support for the standardized execution of safety activities in vehicle model projects.

[0058] Step 206: Generate a compliance report for the vehicle model project based on the associated data of the safety activities.

[0059] Specifically, the associated data of security activities obtained in the above steps includes deliverables such as test reports, vulnerability remediation verification records, and risk assessment summaries. The vehicle model project management system can obtain these deliverables through a multi-channel collection mechanism, including internal module data linkage (such as retrieving task deliverables from the security activity module) and external tool interface integration (such as obtaining assessment / detection reports from TARA tools and vehicle vulnerability scanning tools). Then, the vehicle model project management system will perform format parsing and integrity verification on the deliverables. If it finds that the deliverables are missing key modules (such as test data appendices and responsible person signatures), it will return a "materials incomplete" prompt and guide the supplementation. After the verification is passed, the NLP compliance verification process will be initiated, and the deliverable text will be deeply semantically matched with a preset regulatory library to finally generate a standardized compliance report containing compliance conclusions, deviations, and rectification suggestions. This automated verification method based on natural language processing technology not only effectively avoids problems such as omissions in clauses and semantic misunderstandings that are prone to occur in manual comparison, but also significantly shortens the audit cycle. Furthermore, through standardized verification logic and output format, it ensures the consistency and impartiality of audit results for different projects and different batches of deliverables, providing accurate basis for compliance audits of vehicle model project safety activities, while strengthening risk traceability capabilities and process standardization.

[0060] In some exemplary embodiments of this disclosure, based on the above embodiments, a specific implementation method for generating a compliance report for a vehicle model project based on associated data of safety activities is further described. That is, as follows... Figure 5 As shown, the steps for generating a compliance report for a vehicle model project based on associated data from safety activities may specifically include the following steps: Step 501: Extract the deliverables generated by the security activities from the associated data of the security activities, and convert the text content of the deliverables into a word vector space model.

[0061] Step 502: Obtain multiple legal provisions from the preset legal database and identify the key constraints of each legal provision.

[0062] Step 503: Calculate the semantic matching degree between the word vector space model and each key constraint term.

[0063] Step 504: Determine the target regulatory clauses based on semantic matching degree, and determine the compliance level of security activities based on the target regulatory clauses.

[0064] Step 505: Based on the compliance level, identify one or more compliance deviations of the security activities, and generate associated rectification information for each compliance deviation in conjunction with the key constraints of the target clauses.

[0065] Step 506: Generate a compliance report for the vehicle model project based on the compliance level, each compliance deviation item, and related rectification information.

[0066] Specifically, the vehicle model project management system extracts deliverables generated from security activities (such as test reports, vulnerability remediation verification records, risk assessment summaries, etc.) from the associated data of security activities, and performs format parsing and integrity verification on the extracted deliverables. After the verification is passed, the system retrieves multiple structured regulatory clauses in the field of automotive cybersecurity from a pre-set regulatory library. It then uses NLP technology to parse the regulatory clauses in the pre-set regulatory library. For example, it first splits the text using a word segmentation tool, and then uses named entity recognition technology to locate "requirement" keywords (such as "must," "should," "prohibited," etc.) to identify the mandatory or advisory norms in the clauses. Finally, it extracts the key constraints of each clause, such as the constraining subject, constraining behavior, and constraint strength. At the same time, the vehicle model project management system identifies the text content of the verified deliverables (such as "vehicle controller software update test report"), and then calls a word vector model to convert these text contents into a word vector space model. In this model, each text word corresponds to a vector in the space, and the distance between vectors directly reflects the semantic relevance. Furthermore, based on the pre-trained compliance determination model, the cosine similarity algorithm is used to calculate the semantic matching degree between the word vector space model and each key constraint item. Regulatory clauses with matching degrees higher than a preset minimum threshold are selected as target regulatory clauses. Based on the constraint requirements of the target regulatory clauses and the matching results, the compliance level is determined according to preset thresholds (e.g., matching degree ≥ 85% is fully compliant, 60% ≤ matching degree < 85% is partially compliant, and matching degree < 60% is non-compliant). Compliance deviation items are selected, and the associated rectification information for each deviation item is simultaneously marked. Finally, the compliance level, each compliance deviation item, and the associated rectification information are integrated to generate a standardized compliance report. Therefore, by achieving automated compliance verification of deliverables and generation of compliance reports through the semantic matching process, the accuracy and consistency of compliance determination are ensured, and clear regulatory basis is provided for subsequent audit traceability, significantly improving the efficiency and standardization of compliance management for vehicle model project safety activities.

[0067] In some embodiments, when extracting deliverables generated from security activities from associated data, a two-factor authentication process is performed on critical deliverables such as penetration test reports to ensure the authenticity, integrity, and non-repudiation of the deliverables. The two-factor authentication process includes identity verification and deliverable verification. Identity verification requires the responsible party to perform digital certificate signing (using the RSA 2048 algorithm) and fingerprint biometric identification to ensure the authenticity and traceability of the operator's identity. Deliverable verification compares the hash value of the deliverable file with a pre-stored template to ensure the deliverable file has not been tampered with. Simultaneously, a compliance verification engine matches corresponding regulatory clauses (such as UNECE R155 Clause 5.3 onboard communication encryption requirements) to preliminarily screen core compliance items. Deliverables that pass the two-factor authentication are synchronously stored in the compliance evidence chain module. The activity log records the operation trajectory in real time, for example: "2026-03-15 09:23 Zhang San completed #TASK2026_008", providing a basis for subsequent traceability.

[0068] The aforementioned vehicle model project management method, upon receiving a vehicle model project creation request, obtains the pre-configured key nodes and time points of the vehicle model project, and associates the time points of the key nodes with the safety activities of the vehicle model project; creates and executes the vehicle model project; when the current time point is detected to have reached the time point of the key node, obtains the time window of the safety activities of the vehicle model project; obtains the associated data of the safety activities based on the time window of the safety activities; determines the risk projects and the handling methods of the risk projects based on the associated data of the safety activities; and generates a compliance report for the vehicle model project based on the associated data of the safety activities.

[0069] Therefore, by linking key milestones with the security activities of a vehicle project, a linkage mechanism between project progress and security activities can be established. This eliminates the time discrepancy between cybersecurity activities and key milestones (such as milestones) in the vehicle project, avoiding the risk of delays in critical tasks and improving the efficiency and accuracy of vehicle project management. By acquiring relevant data from security activities within their time windows, and then automatically determining risk items and their handling methods based on this data, compared to the traditional risk identification model that relies on manually compiling fragmented records, this approach enables centralized integration and intelligent analysis of risk data from a technical perspective. This solves problems such as untimely discovery and delayed response to high-risk vulnerabilities, thereby achieving precise risk management. Furthermore, by automatically generating vehicle project compliance reports based on security activity-related data, compared to the traditional model that relies on engineers manually reviewing regulatory texts and marking each item for inspection, this approach not only significantly improves the efficiency of compliance verification and reduces labor costs but also ensures comprehensive coverage of regulatory clauses, effectively avoiding potential omissions. Through the synergistic linkage of these various stages, spanning the entire process of a vehicle project from creation, execution, risk management to compliance verification, standardized and automated management of the entire vehicle project lifecycle can be achieved.

[0070] In some exemplary embodiments of this disclosure, based on the above embodiments, further descriptions are provided, such as... Figure 6 As shown, a vehicle model project management method also includes the following steps: Step 601: Archive the associated data and compliance reports of security activities according to the preset hierarchical structure to generate archive files.

[0071] Step 602: Generate a digital fingerprint of the archived file using an encryption processing algorithm.

[0072] Step 603: Obtain the operation log of the security activity.

[0073] Step 604: Generate an audit data package based on the archived file, the digital fingerprint of the archived file, and the operation log, and store the audit data package on the blockchain.

[0074] Specifically, the vehicle model project management system archives deliverables (such as test reports) according to a pre-defined hierarchical structure (e.g., a directory tree of project ID / development stage / valve point name / safety activity number), generating archived files to ensure orderly storage and efficient retrieval. After archiving, the system calls the encryption module to perform hash calculations on each archived file using the SHA-256 encryption algorithm, generating a digital fingerprint containing the file content hash value, storage path, generation time, and the responsible person's digital signature. This achieves a one-to-one binding between the archived file and the digital fingerprint, providing a core basis for subsequent file integrity verification. Simultaneously, the system uses a log collection engine to acquire a full set of safety activity operation logs (including the entire process of task creation, approval workflow, deliverable upload, and risk handling) recorded by time, user, and module dimensions. It then integrates the archived files, their corresponding digital fingerprints, and the full set of safety activity operation logs, packaging them into an audit data package according to a pre-defined format. Finally, using blockchain technology, the core information of this audit data package (including the data package hash value, generation timestamp, and project unique identifier) ​​is written into a blockchain distributed ledger (e.g., Hyperledger). Fabric chaincode, through which automakers, core suppliers, regulatory agencies and other nodes jointly complete data verification and consensus confirmation, ultimately uses blockchain technology to build a full-process tamper-proof traceability chain for vehicle projects to meet compliance audit and risk traceability needs.

[0075] In some embodiments, during the archiving and blockchain evidence storage process in the vehicle model project management system, risk linkage will also be carried out. When an unclosed residual risk is detected, that is, when the current risk status is not "closed", the archiving process will be automatically blocked and an early warning will be pushed to the project risk module.

[0076] For example, after the vehicle model project management system obtains user operation logs recorded by time, user, and module dimensions, it archives and constructs a traceability chain according to the following logic: First, deliverables and audit reports that have passed compliance verification are stored in a distributed file storage system according to a preset hierarchical structure. For example, deliverables are stored in a directory tree of " / project ID / development stage / valve point name / safety activity number", such as / CP_NEV2025_003 / concept design / SOP valve point / vehicle firewall audit_008 / , where the project ID corresponds to the unique identifier of the vehicle model (such as CP_NEV2025_001), the development stage distinguishes between development stages such as concept design and mass production verification, the valve point name is associated with key time nodes of the project (such as SOP valve point), and the safety activity number corresponds to a specific activity (such as vehicle firewall audit_008), ensuring that the storage path of each file is unique and locatable. Simultaneously, the vehicle model project management system performs SHA-256 encryption calculations on each archived file, generating a digital fingerprint file containing the file's content hash value, storage path, generation time, and the responsible person's digital signature. This fingerprint file is uniquely associated with the original file, becoming the core basis for subsequent verification of file integrity. Then, the vehicle model project management system integrates the digital fingerprint file generated in the above steps, an audit report containing deviation items and rectification suggestions, and operation logs recorded in all dimensions, packaging them into a uniformly formatted audit data package (e.g., file extension .csmspkg). This format file has a built-in anti-tampering mechanism, and automatically embeds the responsible person's digital signature and a timestamp certificate issued by a third-party timestamp service provider during packaging, further strengthening the data's legality and traceability.

[0077] Finally, the vehicle model project management system writes the hash value of the audit data package into a blockchain distributed ledger (such as Hyperledger Fabric chaincode). This data is jointly verified by nodes including the automaker, core suppliers, and regulatory agencies to ensure that the stored information cannot be unilaterally tampered with or deleted. Once the hash value is uploaded to the chain and confirmed by node consensus, the vehicle model project management system changes the project status to "archived" and freezes all modification and deletion permissions for all deliverables, audit reports, and operation logs under that project, retaining only read-only permissions for audit queries. This constructs a full-process tamper-proof traceability chain. Therefore, by generating valve point configuration data that depends on the project settings center through digital fingerprints, ensuring consistency with project management standards, and by applying blockchain technology to guarantee the non-repudiation of operation records, coupled with a directory tree structure that strictly corresponds to project valve points, the system comprehensively meets the full-chain traceability requirements for security activity data in the automotive cybersecurity field, providing reliable and complete technical support for compliance audits, risk tracing, and regulatory inspections.

[0078] In some exemplary embodiments of this disclosure, based on the above embodiments, further descriptions are provided, such as... Figure 7As shown, a vehicle model project management method may also include the following steps: Step 701: When a new vehicle model project creation request is detected, obtain the verified historical security activity templates and the project assets associated with each template.

[0079] Step 702: Based on the development requirements of the new vehicle model project, select the matching target historical safety activity template and the project assets associated with the target historical safety activity template.

[0080] Step 703: Generate safety activity tasks for the new vehicle model project based on the target historical safety activity template and the project assets associated with the target historical safety activity template.

[0081] Specifically, the vehicle model project management system can also achieve experience transfer through the historical project cloning function. The system continuously monitors the creation entry point of vehicle model projects. When a user submits a new vehicle model project creation request, the system first verifies the integrity of the request information (including core parameters such as vehicle type, development stage, and compliance objectives). Then, it automatically retrieves the historical project database to obtain all verified historical security activity templates and the associated project assets (such as test case sets, acceptance criteria, tool versions, and deliverable templates). The system then provides the user with a project copying interface, allowing the user to select verified security activities from historical projects (such as "ECU firmware signature audit" and "vehicle communication encryption verification"). Furthermore, based on the development requirements of the new vehicle model project (such as new energy vehicles, intelligent connected vehicle function configuration, and target market compliance requirements), the system automatically filters out matching target historical security activity templates and associated project assets, such as test case sets, acceptance criteria, and tool versions. At the same time, it performs desensitization processing on the deliverables of historical projects, removing sensitive code, keys, and other confidential information to ensure the security and compliance of asset reuse. After completing target template selection, asset reuse, and desensitization, the system further optimizes template adaptation. On one hand, the vehicle model project management system calls the latest regulatory database from the central knowledge base, automatically comparing differences between old and new regulations (such as the addition of the "V2X Safety Certification" clause in UNECE R155 Rev.2), highlighting the new compliance requirements in the reused templates and linking them to the test case library. On the other hand, the vehicle model project management system uniformly resets the inherited TARA historical risk assessment data status to "Pending Assessment" and automatically creates new versions of risk analysis tasks through the interface ( / tara / task / clone), ensuring that the risk assessment for new vehicle model projects aligns with their specific needs. Finally, based on the optimized target historical safety activity templates and associated project assets, the vehicle model project management system automatically generates a safety activity task list for the new vehicle model project, clearly defining the responsible person, execution deadline, deliverable requirements, and associated thresholds for each task. Simultaneously, the task list is pushed to the safety activity module and project overview module, enabling rapid configuration and startup of safety activities for the new vehicle model project.

[0082] Therefore, this template reuse mechanism not only efficiently inherits the mature experience and verified assets of historical projects, but also avoids legal risks through compliance difference visualization, while resetting risk assessment data to ensure the accuracy of assessment, significantly shortening the configuration cycle of new model projects, and significantly improving the efficiency of new project launch and compliance management.

[0083] It should be understood that although the steps in the flowchart are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order constraint on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowchart may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the sub-steps or stages of other steps.

[0084] In some exemplary embodiments of this disclosure, such as Figure 8 As shown, a vehicle model project management device is provided, including a first acquisition module 801, an execution module 802, a second acquisition module 803, a third acquisition module 804, a determination module 805, and a first generation module 806. The first acquisition module 801 is used to acquire multiple key nodes of a pre-configured vehicle model project and the time points of each key node when a vehicle model project creation request is received, and to associate the time points of each key node with the safety activities of the vehicle model project; the execution module 802 is used to create and execute the vehicle model project; the second acquisition module 803 is used to acquire the time window of the safety activities of the vehicle model project when the current time point reaches the time point of the target key node; the third acquisition module 804 is used to acquire the associated data of the safety activities based on the time window of the safety activities; the determination module 805 is used to determine risk projects and the handling methods of risk projects based on the associated data of the safety activities; and the first generation module 806 is used to generate a compliance report for the vehicle model project based on the associated data of the safety activities.

[0085] In one embodiment of this disclosure, the second acquisition module 803 is specifically used to: acquire the end time of the time window corresponding to the previous key node of the target key node; and determine the time window of the security activity based on the end time of the time window corresponding to the previous key node and the current time point.

[0086] In one embodiment of this disclosure, the execution module 802 is specifically configured to: create safety activity tasks for a vehicle model project based on a predefined safety activity template, and assign the safety activity tasks to the corresponding first responsible person so that the first responsible person can execute the safety activity tasks for the vehicle model project; monitor the execution progress of the safety activity tasks for the vehicle model project, and generate an approval list for the safety activity tasks based on the execution progress; send the approval list to a second responsible person so that the second responsible person can approve the approval list; and confirm that the safety activity tasks have been completed in response to the second responsible person's approval of the approval list.

[0087] In one embodiment of this disclosure, the first generation module 806 is specifically configured to: extract deliverables generated by the safety activity from the associated data of the safety activity, and convert the text content of the deliverables into a word vector space model; obtain multiple regulatory clauses from a preset regulatory library, and identify the key constraints of each regulatory clause; calculate the semantic matching degree between the word vector space model and each key constraint; determine the target regulatory clause based on the semantic matching degree, and determine the compliance level of the safety activity based on the target regulatory clause; determine one or more compliance deviations of the safety activity based on the compliance level, and generate associated rectification information for each compliance deviation in combination with the key constraints of the target clause; and generate a compliance report for the vehicle model project based on the compliance level, each compliance deviation, and the associated rectification information.

[0088] In one embodiment of this disclosure, a vehicle model project management device further includes: an archiving module, used to archive associated data and compliance reports of safety activities according to a preset hierarchical structure to generate archive files; a second generation module, used to generate digital fingerprints of the archive files through an encryption processing algorithm; a third acquisition module, used to acquire operation logs of safety activities; and a third generation module, used to package and generate audit data packets based on the archive files, the digital fingerprints of the archive files, and the operation logs, and store the audit data packets on a blockchain.

[0089] In one embodiment of this disclosure, a vehicle model project management device further includes: a fourth acquisition module, used to acquire verified historical security activity templates and project assets associated with each template when a new vehicle model project creation request is detected; a filtering module, used to filter out matching target historical security activity templates and project assets associated with the target historical security activity templates based on the development requirements of the new vehicle model project; and a fourth generation module, used to generate security activity tasks for the new vehicle model project based on the target historical security activity templates and project assets associated with the target historical security activity templates.

[0090] For specific limitations regarding a vehicle model project management device, please refer to the limitations regarding a vehicle model project management method described above, which will not be repeated here. Each module in the aforementioned vehicle model project management device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in the electronic device in hardware form, or stored in the memory of the electronic device in software form, so that the processor can call and execute the operations corresponding to each module.

[0091] In some exemplary embodiments of this disclosure, an electronic device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 8As shown, the electronic device includes a processor, memory, network interface, and database connected via a system bus. The processor provides computing and control capabilities. The memory includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores the operating system, computer programs, and database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The database stores relevant data for vehicle model projects. The network interface is used for communication with external terminals via a network connection. When the computer program is executed by the processor, it implements a vehicle model project management method.

[0092] Those skilled in the art will understand that Figure 8 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the electronic device to which the present application is applied. The specific electronic device may include more or fewer components than shown in the figure, or combine certain components, or have different component arrangements.

[0093] In some exemplary embodiments of this disclosure, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the steps of a vehicle model project management method in any of the above exemplary embodiments.

[0094] In some exemplary embodiments of this disclosure, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the steps of a vehicle model project management method in any of the above exemplary embodiments.

[0095] In some exemplary embodiments of this disclosure, a computer program product is provided, which includes computer instructions stored in a computer-readable storage medium. When the computer instructions are read from and executed by a processor from the computer-readable storage medium, they implement the steps of a vehicle model project management method in any of the exemplary embodiments described above.

[0096] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments of the above methods. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), RAMbus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0097] The technical features of the above embodiments can be combined in any way. For the sake of brevity, 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.

[0098] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the invention patent. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this patent application should be determined by the appended claims.

Claims

1. A vehicle model project management method, characterized in that, The method includes: Upon receiving a request to create a vehicle model project, the system obtains multiple pre-configured key nodes of the vehicle model project and the time points of each key node, and associates the time points of each key node with the security activities of the vehicle model project. Create and execute the vehicle model project; When the time point at which the target critical node is reached is detected, the time window of the safety activities of the vehicle model project is obtained; Obtain associated data of the security activity based on the time window of the security activity; Based on the associated data of the security activities, risk items and the handling methods for the risk items are determined; A compliance report for the vehicle model project is generated based on the associated data from the safety activities.

2. The method according to claim 1, characterized in that, The time window for obtaining the safety activities of the vehicle model project includes: Obtain the end time of the time window corresponding to the previous key node of the target key node; The time window for the security activity is determined based on the end time of the time window corresponding to the previous critical node and the current time point.

3. The method according to claim 1, characterized in that, The creation and execution of the vehicle model project includes: Safety activity tasks for the vehicle model project are created based on a predefined safety activity template, and the safety activity tasks are assigned to the corresponding first responsible person so that the first responsible person can perform the safety activity tasks for the vehicle model project. Monitor the execution progress of safety activities for the vehicle model project, and generate an approval list for the safety activities based on the execution progress; The approval list is sent to the second responsible person so that the second responsible person can approve the approval list; In response to the second responsible person's approval of the approval list, the completion of the security activity task is confirmed.

4. The method according to claim 1, characterized in that, The process of generating a compliance report for the vehicle model project based on the associated data of the safety activities includes: Extract the deliverables generated by the security activities from the associated data of the security activities, and convert the text content of the deliverables into a word vector space model; Retrieve multiple legal provisions from a pre-defined legal database and identify the key constraints of each legal provision; Calculate the semantic matching degree between the word vector space model and each key constraint term; The target regulatory clauses are determined based on the semantic matching degree, and the compliance level of the security activity is determined based on the target regulatory clauses. Based on the compliance level, one or more compliance deviations of the security activity are determined, and associated rectification information for each compliance deviation is generated in conjunction with the key constraints of the target clause; A compliance report for the vehicle model project is generated based on the compliance level, each compliance deviation item, and the associated rectification information.

5. The method according to claim 1, characterized in that, The method further includes: The associated data of the security activities and the compliance reports are archived according to a preset hierarchical structure to generate archive files; A digital fingerprint of the archived file is generated using an encryption algorithm; Obtain the operation logs of the security activities; An audit data package is generated based on the archived file, the digital fingerprint of the archived file, and the operation log, and the audit data package is stored on the blockchain.

6. The method according to claim 1, characterized in that, The method further includes: When a new vehicle model creation request is detected, retrieve the verified historical security activity templates and the project assets associated with each template; Based on the development requirements of the new vehicle model project, a matching target historical safety activity template and the project assets associated with the target historical safety activity template were selected. The safety activity tasks for the new vehicle model project are generated based on the target historical safety activity template and the project assets associated with the target historical safety activity template.

7. A vehicle model project management device, characterized in that, The device includes: The first acquisition module is used to acquire multiple pre-configured key nodes of the vehicle project and the time points of each key node when a vehicle project creation request is received, and associate the time points of each key node with the security activities of the vehicle project. The execution module is used to create and execute the vehicle model project; The second acquisition module is used to acquire the time window of the safety activities of the vehicle model project when the current time point is detected to reach the target key node; The third acquisition module is used to acquire associated data of the security activity based on the time window of the security activity. The determination module is used to determine risk items and the handling methods for the risk items based on the associated data of the security activities. The first generation module is used to generate a compliance report for the vehicle model project based on the associated data of the safety activities.

8. 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 computer program, it implements the steps of the method according to any one of claims 1 to 6.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

10. A computer program product, characterized in that, The computer program product includes computer instructions stored in a computer-readable storage medium, which a processor reads from and executes to implement the steps of the method as described in any one of claims 1 to 6.

Images