Vehicle software identifier management method and system and storage medium

Abstract

The invention provides a vehicle software identifier management method and system and a storage medium, and is applied to a vehicle end, and the method comprises the following steps: analyzing input first software upgrading data; the first software upgrading data comprises a plurality of pieces of first software identification information, and the first software identification information is provided with corresponding regulation identification numbers; the regulation identification number is a unique identifier of the vehicle software; and transmitting the first software identification information to a target electronic controller through a preset transmission link, and associating a regulation identification number corresponding to the first software identification information with the target electronic controller. And after the software of the target electronic controller is upgraded, directly querying the software versions of all related software of related regulation identification numbers and the capability of integrity verification data of the software versions through the target electronic controller.

Description

Technical Field

[0001] The present invention relates to the field of vehicle technology, and in particular to a vehicle software identification management method, system and storage medium. Background Art

[0002] With the development of autonomous driving, people have higher and higher requirements for the computing and control capabilities of automobiles. More and more functions are provided to users in the form of software, so software-defined cars are becoming an important trend in the development of automobiles. When the software in the car needs to be installed or updated, the over-the-air download technology can be used to install or update the software in the car with the help of the cloud. When upgrading the vehicle's software, the vehicle needs to set RXSWIN (RX Software Identification Number, regulatory identification number) to identify the impact of software changes before and after the upgrade on regulatory-related content.

[0003] Due to software version updates or regulatory updates, RXSWIN is prone to loss or untimely updates, which in turn leads to failure to verify or incorrect verification of the impact of regulatory content before and after the software upgrade. Those skilled in the art are in urgent need of solving the above problems. Summary of the invention

[0004] In view of this, the purpose of the present invention is to provide a vehicle software identification management method, system and storage medium, which solves the problem in the prior art that RXSWIN is easily lost or updated in an untimely manner, resulting in the inability to verify or incorrect verification, and the impact on regulatory-related content before and after software upgrades.

[0005] In a first aspect, the present application provides a vehicle software identification management method, which is applied to a vehicle side, including:

[0006] Parsing the entered first software upgrade data; the first software upgrade data includes a plurality of first software identification information, the first software identification information is provided with a corresponding regulatory identification number; the regulatory identification number is a unique identifier of the vehicle software;

[0007] The first software identification information is transmitted to a target electronic controller through a preset transmission link, and the regulatory identification number corresponding to the first software identification information is associated with the target electronic controller.

[0008] In one embodiment, the transmitting the first software identification information to the target electronic controller via a preset transmission link specifically includes:

[0009] The first software identification information is transmitted to the target electronic controller in sequence according to the transmission links of the target functional module, the target subsystem and the target electronic controller.

[0010] In one embodiment, the target function module is provided with a corresponding function identifier, the target subsystem is provided with a corresponding subsystem identifier, and the target electronic controller is provided with a corresponding electronic controller identifier; the first software identification information is transmitted to the target electronic controller in accordance with the transmission links of the target function module, the target subsystem and the target electronic controller in sequence, specifically including:

[0011] Entering the first software identification information into a target functional module, and associating the regulatory identification number corresponding to the first software identification information with the functional identification corresponding to the target functional module;

[0012] Determine a target subsystem corresponding to the target functional module, and associate a function identifier corresponding to the target functional module with a subsystem identifier corresponding to the target subsystem;

[0013] Determine the target electronic controller corresponding to the target subsystem, and associate the subsystem identifier corresponding to the target subsystem with the electronic controller identifier corresponding to the target electronic controller;

[0014] The first software identification information is transmitted to a target electronic controller through the target subsystem.

[0015] In one embodiment, associating the regulatory identification number corresponding to the first software identification information with the target electronic controller specifically includes:

[0016] A mapping relationship is established between the regulatory identification number of the first software identification information and the electronic controller identification corresponding to the target electronic controller.

[0017] In one embodiment, after parsing the input software upgrade data, the method further includes:

[0018] The software identification information is tested and authenticated through a test link of a target scenario test unit and a target test case.

[0019] In one embodiment, the target scenario test unit is provided with a corresponding test identifier, and before the software identification information is tested and authenticated through the test link of the target scenario test unit and the target test case, the following is further included:

[0020] Determine a target scenario test unit corresponding to the target function module, and associate a function identifier corresponding to the target function module with a test identifier corresponding to the target scenario test unit;

[0021] A target test case corresponding to the target scenario test unit is determined, and the target scenario test unit is associated with the target test case.

[0022] In one embodiment, after transmitting the software identification information to the target electronic controller through a preset transmission link and associating the regulatory identification number corresponding to the software identification information with the target electronic controller, the method further includes:

[0023] Parsing the entered second software upgrade data; the second software upgrade data includes function information and / or second software identification information, and an association relationship between a function module, a subsystem module, and an electronic controller corresponding to the function information and / or the second software identification information;

[0024] When the second software upgrade data includes second software identification information, the electronic controller corresponding to the second software identification information is included in a preset list to be authenticated.

[0025] In one embodiment, after parsing the entered second software upgrade data, the method further includes:

[0026] When the second software upgrade data includes the function information, and the function module corresponding to the function information is the target function module, the electronic controller corresponding to the function information is included in a preset list to be authenticated.

[0027] In one embodiment, it further includes:

[0028] In response to a fault detection instruction input by a user, determining fault information data corresponding to the fault detection instruction; the fault information data includes the first software identification information and / or the second software identification information and / or the function information;

[0029] When the fault information data includes the first software identification information and / or the second software identification information, the target electronic controller corresponding to the first software identification information and / or the electronic controller corresponding to the second software identification information is included in a preset list to be authenticated.

[0030] In one embodiment, after determining the fault information data corresponding to the fault detection instruction in response to the fault detection instruction input by the user, the method further includes:

[0031] When the fault information data includes the functional information, and the functional module corresponding to the functional information is the target functional module, the electronic controller corresponding to the functional information is included in a preset list to be authenticated.

[0032] In a second aspect, the present application provides a vehicle software identification management system, comprising: a processor and a memory; wherein the memory stores a computer program, and the computer program is used to be loaded by the processor and execute the vehicle software identification management method as described in any one of the first aspects.

[0033] In a third aspect, the present application provides a computer-readable storage medium storing instructions for a processor to load and execute a vehicle software identification management method as described in any one of the first aspects.

[0034] In the vehicle software identification management method, system and storage medium of the embodiment of the present application, the regulatory identification number corresponding to the first software identification information is associated with the target electronic controller, and after the software of the target electronic controller is upgraded, the software version and integrity verification data of all relevant software of the relevant regulatory identification number can be directly queried through the target electronic controller. In addition, since the regulatory identification number corresponding to the first software identification information is different after the regulatory-related software upgrade, the relevant regulatory identification number can be queried through the target electronic controller to determine whether the software upgrade is successfully completed. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for use in the embodiments are briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present invention and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without creative work.

[0036] Figure 1 It is a flowchart of the method for managing vehicle software identification in an embodiment of the present application.

[0037] Figure 2 This is a schematic diagram of the structure of the vehicle software identification management device in an embodiment of the present application. DETAILED DESCRIPTION

[0038] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0039] It should be noted that, in this article, the terms "include", "comprises" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "includes a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element. In addition, components, features, and elements with the same name in different embodiments of the present application may have the same meaning or different meanings, and their specific meanings need to be determined by their explanation in the specific embodiment or further combined with the context of the specific embodiment.

[0040] It should be understood that, although the terms first, second, third, etc. may be used to describe various information in this article, these information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of this article, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein can be interpreted as "at the time of..." or "when..." or "in response to determination". Furthermore, as used in this article, the singular forms "one", "one" and "the" are intended to also include plural forms, unless there is an opposite indication in the context. It should be further understood that the terms "comprising", "including" indicate that there are described features, steps, operations, elements, components, projects, kinds, and / or groups, but do not exclude the existence, occurrence or addition of one or more other features, steps, operations, elements, components, projects, kinds, and / or groups. The terms "or" and "and / or" used herein are interpreted as inclusive, or mean any one or any combination. Thus, “A, B, or C” or “A, B and / or C” means “any of the following: A; B; C; A and B; A and C; B and C; A, B, and C.” An exception to this definition will occur only when a combination of elements, functions, steps, or operations are inherently mutually exclusive in some manner.

[0041] It should be understood that, although the various steps in the flowchart in the embodiment of the present application are displayed in sequence according to the indication of the arrows, these steps are not necessarily performed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and it can be performed in other orders. Moreover, at least a portion of the steps in the figure may include a plurality of sub-steps or a plurality of stages, and these sub-steps or stages are not necessarily performed at the same time, but can be performed at different times, and their execution order is not necessarily performed in sequence, but can be performed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.

[0042] It should be noted that in this article, step codes such as S1 and S2 are used for the purpose of expressing the corresponding content more clearly and concisely, and do not constitute a substantial limitation on the order. When implementing the step, those skilled in the art may execute S2 first and then S1, etc., but these should all be within the scope of protection of this application.

[0043] It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0044] In the subsequent description, the suffixes such as "module", "component" or "unit" used to represent elements are only used to facilitate the description of the present application, and have no specific meanings. Therefore, "module", "component" or "unit" can be used in a mixed manner.

[0045] like Figure 1 As shown, this embodiment provides a vehicle software identification management method, which is applied to the vehicle side, including:

[0046] Step S100: parsing the entered first software upgrade data; the first software upgrade data includes a plurality of first software identification information, the first software identification information is provided with a corresponding regulatory identification number; the regulatory identification number is a unique identifier of the vehicle software;

[0047] Step S200: transmitting the first software identification information to a target electronic controller via a preset transmission link, and associating the regulatory identification number corresponding to the first software identification information with the target electronic controller.

[0048] In the vehicle software identification management method of this embodiment, the regulatory identification number corresponding to the first software identification information is directly associated with the target electronic controller. After the software of the target electronic controller is upgraded, the software version of all software related to the regulatory identification number and its integrity verification data capability can be directly queried through the target electronic controller, so as to determine the impact of the software version before and after the software upgrade. In addition, since the regulatory identification number corresponding to the first software identification information is different after the regulatory-related software upgrade, the relevant regulatory identification number can be queried through the target electronic controller to determine whether the software upgrade is successfully completed.

[0049] In step S100, the first software upgrade data includes regulatory data (or also includes functional data). Regulatory data includes first software identification information determined according to regulations. When upgrading the software, the corresponding regulations will be interpreted according to various standards (such as ISO26262 functional safety standard system, ASPICE standard), and the corresponding first software identification information will be generated according to the interpreted regulations. For example, a certain regulation stipulates that "the brightness of the rear taillights of the car shall not affect the driving safety of other vehicles behind", and the technicians can query the safety function standards related to the rear taillights to find that "when the brightness of the taillights of the car is 4.0cd±1.0cd, there is no obvious dazzling effect on the driver of the rear vehicle", that is, the first software identification information determined according to the regulation is "the brightness of the rear taillights of the car is 3.0cd-5.0cd", and the RXSWIN corresponding to the software identification is determined to be "TL3" according to the regulations.

[0050] RXSWIN refers to a unique identifier that defines a unique set of software that complies with a given UN regulation "X" for the type approval system. RXSWIN represents a set of software versions of a series of parts related to the vehicle type approval system. RXSWIN is equivalent to the "identity card number" of the vehicle software in the whole vehicle. Generally speaking, each automobile developer has its own specific software development system. The same batch of vehicles belonging to each automobile developer usually have the same initial configuration and hardware basis. The vehicle software of the same batch of vehicles upgraded through the software development system of the developer is the updated new version of RXSWIN or the newly added RXSWIN, while the vehicle software of the vehicles that have not been upgraded is the previous version of RXSWIN or no RXSWIN is configured.

[0051] Before performing a software upgrade, the software development engineers of the automobile developer need to upload the regulatory data and / or functional data to the software development system, and define the storage address of the regulatory data and functional data on the vehicle side in the software development system. When the vehicle side is connected to the software development system and performs a software upgrade, after receiving the transmitted software upgrade data, the vehicle side can parse the storage addresses corresponding to the regulatory data and functional data in the software upgrade data, and store the regulatory data and functional data in the corresponding storage addresses. For example, when data is transmitted to the vehicle side through the OBD interface of the vehicle side, the OBD scanning tool on the vehicle side can accept the regulatory data and functional data in the software upgrade data and parse their corresponding storage addresses (the storage address can be an in-vehicle entertainment system for displaying vehicle performance and status, or an electronic controller for monitoring and controlling vehicle performance and status).

[0052] In step S200, the electronic controller generally refers to the ECU, which is a core component in modern cars and is responsible for controlling multiple functions of the vehicle, such as engine management, transmission control, body electronics, etc. With the development of automotive technology, the functions of the ECU are becoming more and more complex, and its software also needs to be continuously updated to adapt to new regulatory requirements, improve performance or fix known problems.

[0053] The hardware version number and software version number of the ECU are important components of the automotive electronic system. They represent the specific versions of the ECU's physical hardware and running software, respectively. The hardware version number usually refers to the physical design and manufacturing information of the ECU, while the software version number refers to the version information of the firmware or software running in the ECU. Each ECU has its own software version number, which is very important for automobile manufacturers or suppliers. They are responsible for recording and managing this information to ensure software updates and maintenance. After the ECU's software is updated, the corresponding software version number will be updated accordingly. The target electronic controller is an ECU in the electronic controller that is associated with regulatory-related software identification information for the purpose of meeting regulatory requirements.

[0054] The transmitting the software identification information to the target electronic controller via a preset transmission link specifically includes: transmitting the first software identification information to the target electronic controller in sequence according to the transmission links of the target functional module, the target subsystem and the target electronic controller.

[0055] When upgrading the software, multiple functional modules are set according to the functional requirements of the software, and each functional module can meet at least one functional requirement. When designing the target functional module, the engineer extracts the corresponding regulatory requirements according to the rules defined by the regulations, designs the regulatory requirements into the functional module in the form of functions, and designs the target functional module.

[0056] A subsystem is a larger component or module that undertakes the specific functions or business logic of each functional module and works with other subsystems to provide a complete software solution. The target subsystem mainly undertakes regulatory requirements and passes them to the target electronic controller.

[0057] The target function module is provided with a corresponding function identifier, the target subsystem is provided with a corresponding subsystem identifier, and the target electronic controller is provided with a corresponding electronic controller identifier; the first software identification information is transmitted to the target electronic controller according to the transmission link of the target function module, the target subsystem and the target electronic controller in sequence, specifically including:

[0058] Entering the first software identification information into a target functional module, and associating the regulatory identification number corresponding to the software identification information with the functional identification corresponding to the target functional module;

[0059] Determine a target subsystem corresponding to the target functional module, and associate a function identifier corresponding to the target functional module with a subsystem identifier corresponding to the target subsystem;

[0060] Determine the target electronic controller corresponding to the target subsystem, and associate the subsystem identifier corresponding to the target subsystem with the electronic controller identifier corresponding to the target electronic controller;

[0061] The first software identification information is transmitted to a target electronic controller through the target subsystem.

[0062] When the first software identification information is entered into the target function module, the functional requirement information related to the first software identification information is also entered into the same target function module, and the subsystems that undertake different functions undertake the corresponding functional requirements, wherein the functional requirements of the software identification information are undertaken by the target subsystem, and the ID of the target subsystem is mapped to the regulatory identification number of the software identification information through the target function module. Then the target subsystem determines the corresponding target electronic controller through the function execution command defined by the ECU hardware end (for example, the ECU that executes the engine control command, the ECU that executes the brake control, and the ECU that executes the central control, etc.), and establishes a mapping relationship between the ID of the target electronic controller and the regulatory identification number of the software identification information through the target subsystem and the target function module.

[0063] In this embodiment, the function identifier of the target function module is the ID of the target function module, the subsystem identifier of the target subsystem is the ID of the target subsystem, and the electronic controller identifier of the target electronic controller is the ID of the target electronic controller. A mapping relationship is established between the regulatory identification number corresponding to the first software identification information and the ID of the target function module, the ID of the target subsystem, and the ID of the target electronic controller in sequence, and the corresponding first software identification information can be directly queried through the target electronic controller, and it can be determined whether the target electronic controller has completed the software version and its integrity verification data capabilities according to regulatory requirements.

[0064] Associating the regulatory identification number corresponding to the first software identification information with the target electronic controller specifically includes: establishing a mapping relationship between the regulatory identification number of the first software identification information and the electronic controller identification corresponding to the target electronic controller.

[0065] After a mapping relationship is established between the regulatory identification number of the first software identification information and the electronic controller identification of the target electronic controller, the regulatory identification number corresponding to the first software identification information can be used to determine which link has a problem along the target electronic controller, target subsystem, target functional module and software upgrade data, thereby achieving traceability of full-link functional requirements.

[0066] During the test verification, the first software identification information can be used to determine which link fails the test, thereby facilitating the technician to quickly locate the relevant link and make adjustments.

[0067] In one embodiment, after parsing the input software upgrade data, the method further includes:

[0068] The software identification information is tested and authenticated through a test link of a target scenario test unit and a target test case.

[0069] The scenario test unit is a specific environment or module collection for testing the software system. It focuses on simulating complex scenarios of software operation in the real world. These scenarios usually contain multiple related operations, processes and conditions to comprehensively test the performance, function and stability of the software in specific situations. For example, the urban road driving scenario test unit will simulate various traffic conditions, such as changes in traffic lights at intersections, pedestrians crossing, merging and overtaking of other vehicles, etc.

[0070] A test case is a set of detailed test steps, input data, expected results, and execution conditions designed for a specific test purpose. A test case is the basic unit of software testing and is used to verify whether a specific function or feature of the software meets the expected design requirements.

[0071] The target scenario test unit is provided with a corresponding test identification, and before the software identification information is tested and authenticated through the test link of the target scenario test unit and the target test case, it also includes:

[0072] Determine a target scenario test unit corresponding to the target function module, and associate a function identifier corresponding to the target function module with a test identifier corresponding to the target scenario test unit;

[0073] A target test case corresponding to the target scenario test unit is determined, and the target scenario test unit is associated with the target test case.

[0074] By establishing a mapping relationship between the function identifier corresponding to the target function module and the test identifier corresponding to the target scenario test unit, the test link of the target scenario test unit and the target test case can be associated with the transmission link of the target function module, the target subsystem and the target electronic controller, thereby combining the two functions of regulatory certification and software testing.

[0075] Usually, a scenario test unit is associated with multiple test cases, which can test whether the software performs well under different test cases. When the software fails a test case, the regulatory identification number corresponding to the first software identification information can be used to trace the corresponding target functional module along the test link of the test case and the target scenario test unit, and combined with the transmission link of the target functional module, target subsystem and target electronic controller, quickly locate the link where the failure occurs, and achieve full-link traceability.

[0076] Furthermore, when performing software upgrades, regulatory functions can be upgraded, and other related functions can also be upgraded or updated. Regulatory functions include regulatory data, which are provided with corresponding first identification information, and other related functions include functional data, which are provided with corresponding second identification information. When a new function needs to be added after the vehicle is launched, it is necessary to first determine whether the function is a regulatory-related function. If so, the electronic controller that implements the function needs to be certified to meet product compliance requirements. At this time, it is also necessary to determine whether the electronic controller that implements the function is a target electronic controller related to the regulations. If it is a target electronic controller related to the regulations, it is also necessary to determine whether the change affects other regulations.

[0077] After transmitting the software identification information to the target electronic controller through a preset transmission link and associating the regulatory identification number corresponding to the software identification information with the target electronic controller, the method further includes:

[0078] Parsing the entered second software upgrade data; the second software upgrade data includes function information and / or second software identification information, and an association relationship between a function module, a subsystem module, and an electronic controller corresponding to the function information and / or the second software identification information;

[0079] When the second software upgrade data includes second software identification information, the electronic controller corresponding to the second software identification information is included in a preset list to be authenticated.

[0080] In one embodiment, after transmitting the software identification information to the target electronic controller through a preset transmission link and associating the regulatory identification number corresponding to the software identification information with the target electronic controller, the method further includes:

[0081] Parsing the entered second software upgrade data; the second software upgrade data includes function information and / or second software identification information, and an association relationship between a function module, a subsystem module, and an electronic controller corresponding to the function information and / or the second software identification information;

[0082] When the second software upgrade data includes second software identification information, the electronic controller corresponding to the second software identification information is included in a preset list to be authenticated.

[0083] The second software upgrade data includes functional data and / or regulatory data, wherein the functional data includes functional information determined according to the functional requirements of the software upgrade, and the regulatory data includes second software identification information according to the regulatory requirements corresponding to the software certification. The regulatory data corresponding to the second software identification information may be different from the regulations corresponding to the first software identification information, or may be an update of the regulations corresponding to the first software identification information.

[0084] When upgrading the software, the car developer can determine the corresponding functional information according to the user's usage requirements or safety requirements. For example, before the software upgrade, the driver of the car could not determine whether the rear taillights of the car were on in the cockpit, so when changing lanes or turning, the driver could not determine whether to provide prompt information for the following car. After understanding the usage requirements, the technicians determined that the solution to achieve this usage requirement is to "detect the status of the rear car's taillights and display the taillight status on the on-board display in the cockpit", thereby determining the functional information "displaying the lighting status of the rear taillights of the car".

[0085] When the second software upgrade data includes regulatory data, the regulatory identification number corresponding to the second software identification information and the transfer link that undertakes the changed function are sequentially associated in the order of the target functional module, the target subsystem, and the target electronic controller. Similarly, when the second software upgrade data includes functional data, the functional information is also sequentially associated in the order of the corresponding target functional module, the target subsystem, and the transfer link of the target electronic controller.

[0086] The list to be certified stores the storage address and other related information of the electronic controllers that need to be certified. When the second software upgrade data includes the second software identification information, it means that there are regulatory-related functions in the second software upgrade data that need to be updated during the software upgrade process. At this time, the electronic controller that implements the function needs to be recorded in the list to be certified and wait for the certification to be completed to meet the product compliance requirements.

[0087] The first software identification information and the second software identification information can also be used to determine which link has a fault, so that technicians can quickly locate the faulty link and make adjustments. When a vehicle is launched on the market, if a function fails or is missing due to a fault, it is necessary to first determine whether the function is a regulatory function. If so, the target electronic controller that implements the function must determine whether the change affects the function and other regulatory functions. If it affects other regulatory functions, the function must be re-certified. If it does not, no re-certification is required. In one embodiment, in response to a fault detection instruction input by a user, fault information data corresponding to the fault detection instruction is determined; the fault information data includes the first software identification information and / or the second software identification information and / or the function information;

[0088] When the fault information data includes the first software identification information and / or the second software identification information, the target electronic controller corresponding to the first software identification information and / or the electronic controller corresponding to the second software identification information is included in a preset list to be authenticated.

[0089] The fault detection instruction is used to detect the target software identification information, and the faulty electronic controller has not established an association with the regulatory identification number of the target software identification information; after determining whether the target electronic controller is the faulty electronic controller, it also includes: when it is determined that the target electronic controller is the faulty electronic controller, responding to the fault detection instruction and locating the fault information of the faulty electronic controller.

[0090] The fault detection instruction includes the regulatory identification number of the target software identification information, as well as which target functional modules, target subsystems and target electronic controllers the target software identification information needs to be associated with, and can directly locate which link in the target electronic controller, target subsystem, target functional module and software upgrade data has a problem.

[0091] For example, in a fault detection instruction, the target software identification information needs to establish an association relationship with the target functional module a, the target subsystem b1, the target subsystem b2 and the target electronic controller C. However, during the detection, it is found that the ID of the target functional module a, the ID of the target subsystem b2 and the ID of the target electronic controller C are all mapped with the regulatory identification number of the target software identification information, while the ID of the target subsystem b1 is not mapped with the regulatory identification number of the target software identification information. In this case, it can be located that a fault has occurred in this link of the target subsystem, resulting in the loss of data of the target subsystem b1.

[0092] After determining the fault information data corresponding to the fault detection instruction in response to the fault detection instruction input by the user, the method further includes:

[0093] When the fault information data includes the functional information, and the functional module corresponding to the functional information is the target functional module, the electronic controller corresponding to the functional information is included in a preset list to be authenticated.

[0094] When the functional module corresponding to the functional information included in the fault information data is the target functional module, it indicates that the functional development of the functional information and the first software identification information (and / or the second software identification information) is performed by the same functional module. At this time, the functional information is also associated with the regulations. After a fault occurs, it will also affect the certification of relevant regulations, thereby the electronic controller corresponding to the functional information is also included in the preset list to be certified.

[0095] When the electronic controller is the target electronic controller, the design requirements of the target subsystem can be searched according to the corresponding subsystem of the forward development. The functional requirements of which functional module are taken over by the design requirements, and then the target functional module, as well as the functional requirements and which regulations correspond to them, are queried to complete the traceability of the regulatory requirements.

[0096] To solve the traceability of regulatory requirements, the existing requirements only have inputs but no clear labels. It is unclear which requirements are regulatory requirements, which are safety requirements, and which are attribute requirements. This requires re-judgment when querying problems after development, which wastes a lot of resources. The requirement labels established through regulatory identification numbers can trace the sources of regulatory requirements.

[0097] After associating the regulatory identification number corresponding to the software identification information with the target electronic controller, the method further includes: writing the association relationship between the software identification information and the target electronic controller into a diagnostic identification table of the target electronic controller.

[0098] The DID code (Data Identifier) ​​in the car is an identifier used for vehicle diagnosis, which is used to identify and obtain specific parameter data in the electronic control unit (ECU). The diagnostic identification table records the information of the DID code and the electronic control unit. A mapping relationship is established between the ID of each electronic control unit and the DID code, and the corresponding electronic control unit can be directly queried through the DID. DID can be used to read sensor data, check the status of the electronic control unit, read fault codes, clear fault codes, read freeze frame data, etc.

[0099] In this embodiment, the software is upgraded through the OBD (On-Board Diagnostics) interface by connecting the diagnostic instrument to the electronic controller. There is no need to upgrade the software in the cloud through OTA (Over-the-Air), which makes it convenient for car companies to upgrade the software directly on the vehicle side, reduces the risks caused by network attacks or interference, and ensures the accuracy and security of the upgrade process.

[0100] An information query table of the software upgrade data and the target electronic controller is stored in the cloud; after the association between the software identification information and the target electronic controller is written into the diagnostic identification table of the target electronic controller, it also includes: sending the diagnostic identification table to the cloud and / or server, and updating the information query table based on the diagnostic identification table.

[0101] An information query table is stored in the cloud. The BSS data and individual ECU information are summarized in the information query table. The ECU name, ECU VBF version and other information of each ECU are located in the same column. At the same time, the regulatory identification number mapped to the ECU, the regulatory number and regulatory name associated with RXSWIN are also located in the same column.

[0102] When car companies release software, one BSS data contains the software and hardware information corresponding to forty or fifty ECUs (Electronic Control Units). Each ECU must have corresponding software and hardware from different suppliers, and it must pass testing and review before it can be officially released.

[0103] Through the information query table, users or car companies can directly query the regulatory information corresponding to the electronic controller on the cloud or server side, which makes it more convenient to change the platform after the subsequent increase, reduction, and change of regulations, optimizes the operating procedures of business personnel, and reduces unnecessary operation processes.

[0104] To sum up, in the vehicle software identification management method of the present embodiment, on the one hand, the regulatory identification number corresponding to the software identification information is associated with the target electronic controller, and after the software of the target electronic controller is upgraded, the software version of all relevant software related to RXSWIN and the ability of its integrity verification data are queried directly through the target electronic controller; on the other hand, a mapping relationship is established between the regulatory identification number corresponding to the software identification information and the ID of the target functional module, the ID of the target subsystem and the ID of the target electronic controller in sequence, and the regulatory identification number corresponding to the software identification information can be used to determine which link has a problem along the target electronic controller, the target subsystem, the target functional module and the software upgrade data, thereby achieving traceability of full-link functional requirements.

[0105] like Figure 2 As shown, based on the same inventive concept as the above-mentioned embodiment, this embodiment provides a vehicle software identification management device, including:

[0106] The parsing module M10 is used to parse the entered first software upgrade data; the first software upgrade data includes a plurality of first software identification information, the first software identification information is provided with a corresponding regulatory identification number; the regulatory identification number is a unique identifier of the vehicle software;

[0107] The association module M20 is used to transmit the first software identification information to the target electronic controller through a preset transmission link, and associate the regulatory identification number corresponding to the first software identification information with the target electronic controller.

[0108] Based on the same inventive concept as the above embodiments, this embodiment also provides a vehicle software identification management system, including: a processor and a memory; wherein the memory stores a computer program, and the computer program is used to be loaded by the processor and execute the vehicle software identification management method as described above.

[0109] Based on the same inventive concept as the above embodiments, this embodiment further provides a computer-readable storage medium, wherein the computer-readable storage medium stores instructions, and the instructions are used for a processor to load and execute the vehicle software identification management method as described above.

[0110] In the embodiments of the mobile terminal and computer-readable storage medium provided in the present application, all technical features of the above-mentioned control method embodiments are included, and the expansion and explanation content of the specification are basically the same as those of the above-mentioned method embodiments, which will not be repeated here.

[0111] The embodiment of the present application further provides a computer program product, which includes a computer program code. When the computer program code runs on a computer, the computer executes the methods in the above various possible implementation modes.

[0112] An embodiment of the present application also provides a chip, including a memory and a processor, the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that a device equipped with the chip executes the methods in various possible implementation modes as described above.

[0113] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0114] In the present application, the same or similar terminology concepts, technical solutions and / or application scenario descriptions are generally described in detail only the first time they appear. When they appear again later, they are generally not repeated for the sake of brevity. When understanding the technical solutions and other contents of the present application, for the same or similar terminology concepts, technical solutions and / or application scenario descriptions that are not described in detail later, reference can be made to the previous related detailed descriptions.

[0115] In the present application, the description of each embodiment has its own emphasis. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0116] The various technical features of the technical solution of the present application can be arbitrarily combined. In order to make the description concise, not all possible combinations of the various 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 the present application.

[0117] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, and the computer software product is stored in a storage medium as above, including a number of instructions for a terminal device to execute the method of each embodiment of the present application. The above is only a preferred embodiment of the present application, and does not limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made by using the content of the specification and drawings of this application, or directly or indirectly used in other related technical fields, is similarly included in the patent protection scope of the present application.

[0118] It should be noted that the various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referenced to each other.

[0119] The above is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any changes or substitutions that can be easily thought of by a person skilled in the art within the technical scope disclosed by the present invention should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the attached claims.

Claims

1. A vehicle software identification management method, applied to the vehicle side, characterized in that: include: Parsing the entered first software upgrade data; The first software upgrade data includes a plurality of first software identification information, wherein the first software identification information is provided with a corresponding regulatory identification number; the regulatory identification number is a unique identifier of the vehicle software; The first software identification information is transmitted to a target electronic controller through a preset transmission link, and the regulatory identification number corresponding to the first software identification information is associated with the target electronic controller.

2. The vehicle software identification management method according to claim 1, characterized in that: The step of transmitting the first software identification information to the target electronic controller via a preset transmission link specifically includes: The first software identification information is transmitted to the target electronic controller in sequence according to the transmission links of the target functional module, the target subsystem and the target electronic controller.

3. The vehicle software identification management method according to claim 2, characterized in that: The target function module is provided with a corresponding function identifier, the target subsystem is provided with a corresponding subsystem identifier, and the target electronic controller is provided with a corresponding electronic controller identifier; the first software identification information is transmitted to the target electronic controller according to the transmission link of the target function module, the target subsystem and the target electronic controller in sequence, specifically including: Entering the first software identification information into a target functional module, and associating the regulatory identification number corresponding to the first software identification information with the functional identification corresponding to the target functional module; Determine a target subsystem corresponding to the target functional module, and associate a function identifier corresponding to the target functional module with a subsystem identifier corresponding to the target subsystem; Determine the target electronic controller corresponding to the target subsystem, and associate the subsystem identifier corresponding to the target subsystem with the electronic controller identifier corresponding to the target electronic controller; The first software identification information is transmitted to a target electronic controller through the target subsystem.

4. The vehicle software identification management method according to claim 3, characterized in that: Associating the regulatory identification number corresponding to the first software identification information with the target electronic controller specifically includes: A mapping relationship is established between the regulatory identification number of the first software identification information and the electronic controller identification corresponding to the target electronic controller.

5. The vehicle software identification management method according to claim 3, characterized in that: After parsing the entered software upgrade data, the following steps are also included: The software identification information is tested and authenticated through a test link of a target scenario test unit and a target test case.

6. The vehicle software identification management method according to claim 5, characterized in that: The target scenario test unit is provided with a corresponding test identification, and before the software identification information is tested and authenticated through the test link of the target scenario test unit and the target test case, it also includes: Determine a target scenario test unit corresponding to the target function module, and associate a function identifier corresponding to the target function module with a test identifier corresponding to the target scenario test unit; A target test case corresponding to the target scenario test unit is determined, and the target scenario test unit is associated with the target test case.

7. The vehicle software identification management method according to claim 2, characterized in that: After transmitting the software identification information to the target electronic controller through a preset transmission link and associating the regulatory identification number corresponding to the software identification information with the target electronic controller, the method further includes: Parsing the entered second software upgrade data; the second software upgrade data includes function information and / or second software identification information, and an association relationship between a function module, a subsystem module, and an electronic controller corresponding to the function information and / or the second software identification information; When the second software upgrade data includes second software identification information, the electronic controller corresponding to the second software identification information is included in a preset list to be authenticated.

8. The vehicle software identification management method according to claim 7, characterized in that: After parsing the entered second software upgrade data, the method further includes: When the second software upgrade data includes the function information, and the function module corresponding to the function information is the target function module, the electronic controller corresponding to the function information is included in a preset list to be authenticated.

9. The vehicle software identification management method according to claim 7, characterized in that: Also includes: In response to a fault detection instruction input by a user, determining fault information data corresponding to the fault detection instruction; The fault information data includes the first software identification information and / or the second software identification information and / or the function information; When the fault information data includes the first software identification information and / or the second software identification information, the target electronic controller corresponding to the first software identification information and / or the electronic controller corresponding to the second software identification information is included in a preset list to be authenticated.

10. The vehicle software identification management method according to claim 9, characterized in that: After determining the fault information data corresponding to the fault detection instruction in response to the fault detection instruction input by the user, the method further includes: When the fault information data includes the functional information, and the functional module corresponding to the functional information is the target functional module, the electronic controller corresponding to the functional information is included in a preset list to be authenticated.

11. A vehicle software identification management system, comprising: A processor and a memory; wherein the memory stores a computer program, and the computer program is used to be loaded by the processor and execute the vehicle software identification management method as described in any one of claims 1-10.

12. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores instructions, and the instructions are used by a processor to load and execute the vehicle software identification management method as described in any one of claims 1-10.

Images