Software query information management system and software query information management method

Abstract

The present invention provides a software query information management system and a software query information management method, which can efficiently generate evidence required for the legal license of software installed in a device installed in a vehicle. The software query information management system stores device requirement specifications in association with the regulation ID of the regulations that stipulate the requirements that a vehicle must meet to obtain a legal license, determines the regulation ID corresponding to the device requirement specifications associated with the traceability information of the device associated with the device requirement specifications, generates software query information that associates the determined regulation ID with one or more software IDs contained in the traceability information, determines the software IDs of other software corresponding to the regulation ID corresponding to the software ID of the software installed in the device where an event occurred based on the software query information, and generates evidence based on the communication data of the device installed with the determined software ID.

Description

Technical Field

[0001] The invention relates to a software query information management system and a software query information management method. Background Art

[0002] Patent document 1 describes a vehicle design support device that is designed to solve the problem of requiring a great deal of labor in confirming whether a design concept complies with laws and regulations during the vehicle design process. The vehicle design support device includes: a legal information storage unit that stores information on laws and regulations related to each component installed in the vehicle; a unit that inputs vehicle shape information that determines the shape of the vehicle; a unit that inputs component shape information that determines the shape of the component installed in the vehicle and the installation position of the component; a judgment unit that reads component-related legal information related to the component from the legal information storage unit and judges whether the component satisfies the specified conditions contained in the component-related legal information; and an output unit that changes the display form of the component according to the judgment result of the judgment unit.

[0003] Patent document 2 describes a file management device configured to be able to determine the impact range of a change to a portion of a file. The file management device includes: information that determines a first portion of a file in a first table format; a storage unit that stores a correspondence relationship with information that determines a second portion of a file in a second table format; and a control unit that, upon receiving a search request for the impact range of the first portion, refers to the storage unit, extracts information that determines the second portion corresponding to the information that determines the first portion, and outputs information that determines the second portion and information that determines the file in a second table format that includes the second portion as a response to the search request.

[0004] Patent document 3 describes a vehicle-mounted device log collection system that is configured to efficiently obtain log information that developers really need from vehicle-mounted devices in development of distributed tests without excessive shortages. The vehicle-mounted device log collection system includes: a log management device that sends a condition for extracting summary information that is a priority analysis object from the log information of the vehicle-mounted device and an analysis script that records an instruction to send the content of the extracted summary information to the log management device to the vehicle-mounted log collection device, and extracts log information at the time when an error occurred in the vehicle-mounted device from the summary information; and the vehicle-mounted log collection device extracts the summary information from the log information based on the analysis script, and sends the extracted summary information and the time when the error occurred to the log management device.

[0005] Prior art literature

[0006] Patent Literature

[0007] Patent Document 1: Japanese Patent Application Publication No. 2005-173761

[0008] Patent Document 2: Japanese Patent Application Publication No. 2014-130547

[0009] Patent Document 3: Japanese Patent Application Publication No. 2017-220135 Summary of the invention

[0010] Problems to be solved by the invention

[0011] Nowadays, with the development of wireless communication technology, vehicle providers such as automobile manufacturers can assemble and update (performance change, function change, function addition, etc.) the software of equipment such as ECU (Electronic Control Unit) installed in vehicles through OTA (Over The Air) when the vehicle is manufactured and after it is sold. As a result, vehicle providers can develop, produce and sell cars, for example, foreseeing the addition of autonomous driving functions in the future, and it is believed that the update opportunities for software installed in vehicles will increase dramatically in the future.

[0012] In view of this situation, WP29 (World Forum for Harmonization of Vehicle Regulations) has developed international standards for software updates. WP29 has discussed, for example: evaluating the impact of software updates on vehicle type certification (type approval) and documenting the results; reporting to government departments (such as the Ministry of Land, Infrastructure, Transport and Tourism of Japan) when software updates affect the content of completed type certification; introducing the concept of defining a number that is a summary of the version level of one or more software installed in a vehicle system that has completed formal certification (hereinafter referred to as "software query number"); submitting evidence and other information related to software updates at the request of government departments; and institutionalizing, etc.

[0013] When the above system is implemented, vehicle providers will need to effectively and practically analyze the impact of the software installed in the large number of devices in the vehicle, the assignment of software query numbers, and the impact of updating these software on model certification, and obtain evidence that needs to be reported for model certification.

[0014] However, most of the devices installed in the vehicle are usually provided by the device provider such as a supplier to the vehicle provider (OEM), and the software-related information such as traceability information is managed by the provider (supplier). Therefore, it is expected that when responding to the above-mentioned system, it will be necessary to perform cumbersome work in order to associate information such as model certification managed by the vehicle provider (OEM) with information about the software.

[0015] Here, although the vehicle design assistance device described in the above-mentioned patent document 1 determines whether the components installed on the vehicle meet the prescribed conditions contained in the component-related legal and regulatory information, it does not provide any technology for the coordinated management of information managed by the equipment provider and information managed by the vehicle provider.

[0016] Furthermore, the file management device described in Patent Document 2 determines the scope of impact of the change to the file portion, but does not specifically mention an analysis of the impact on model certification when updating software and a specific method for obtaining evidence required to be reported for model certification.

[0017] In addition, the vehicle-mounted device log collection system described in the above-mentioned patent document 3 is a system for obtaining log information that developers actually need from vehicle-mounted devices under development in distributed experiments, but does not provide an analysis of the impact on model certification when updating software and a specific method for obtaining evidence that needs to be reported on model certification.

[0018] The present invention is completed in view of such background, and its purpose is to provide a software query information management system and a software query information management method that can efficiently manage information related to legal licenses of software installed in devices installed in vehicles, and efficiently acquire and provide information required by users.

[0019] Technical solutions to solve problems

[0020] One mode of the present invention for achieving the above-mentioned object is a software query information management system for managing information about legal licenses for software, wherein the software is used to realize the function of a device installed in a vehicle, wherein device requirement specifications are stored in association with a regulation ID, wherein the regulation ID is information for determining a regulation that stipulates requirements that a vehicle must meet in order to obtain a legal license, and the device requirement specifications are information about specifications required by the regulation for the device, obtaining traceability information, the traceability information being information about the traceability of the device associated with the device requirement specifications, the traceability information including a software ID for determining the software installed in the device, and generating software query information, the software query information being information about the device requirement specifications associated with the acquired traceability information. The regulatory ID corresponding to the specification is requested, and information associated with one or more software IDs is obtained, and event information as information about an event occurring in the device is stored, the event information including information obtained by establishing a correspondence between information used to determine the device where the event occurred and the software ID of the software that implements the function of the device; based on the software query information, the software IDs of other software associated with the regulatory ID corresponding to the software ID in the event information are determined; based on the traceability information, the device in which the determined software ID is installed is determined; communication data including content of communication between the determined device and other devices is obtained; and evidence required to obtain the statutory license is generated based on the communication data.

[0021] Furthermore, the problems disclosed in the present application and their solutions will be made clear by the embodiments and the accompanying drawings by which the present invention is implemented.

[0022] Effects of the Invention

[0023] According to the present invention, it is possible to efficiently manage information related to legal licenses of software installed in a device mounted in a vehicle, and to efficiently acquire and provide information required by a user. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] Figure 1 It is a diagram illustrating software query information.

[0025] Figure 2 This shows an example of licensed software query information.

[0026] Figure 3 This shows an example of vehicle structure information.

[0027] Figure 4 (a) and (b) show examples of traceability information.

[0028] Figure 5This is a diagram showing a schematic structure of a software query information management system.

[0029] Figure 6 An example of an information processing device constituting a software inquiry information management system is shown.

[0030] Figure 7 This shows an example of test history information.

[0031] Figure 8 This shows an example of test vehicle information.

[0032] Fig. 9 An example of an error message.

[0033] Fig.10 is a flow chart illustrating the software query number generation process.

[0034] Fig.11 It is a diagram that illustrates traceability information and its transformation.

[0035] Fig.12 is a flowchart illustrating the software update management process.

[0036] Fig.13 It is a flowchart explaining the software query information reference processing.

[0037] Fig.14 This shows an example of the software query information management screen.

[0038] Fig.15 This shows an example of a related information search screen.

[0039] Fig.16 This shows an example of a new software query information registration screen.

[0040] Fig.17 This shows an example of the software query information update screen.

[0041] Fig.18 This is an example of a display when the determination of whether or not the software query code needs to be updated cannot be made.

[0042] Fig.19 This is a diagram for explaining how to use the software query information management effect diagram.

[0043] Fig. 20 This shows an example of a test environment that is constructed when obtaining evidence.

[0044] Fig.21 is a flow chart illustrating the evidence generation process.

[0045] Fig. 22 : is a flowchart explaining the communication data acquisition process.

[0046] Fig.23 This shows an example of communication data. DETAILED DESCRIPTION

[0047] Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. In the following description, sometimes the same or similar structures are marked with common reference numerals and repeated descriptions are omitted. In addition, a plurality of individuals having a common structure are marked with common reference numerals, and in order to distinguish each individual, the reference numerals are marked with characters such as English letters.

[0048] In the following description, "regulations" refer to the laws (laws, government orders, rules, etc.) that must be followed in order to receive certification (permit) that a vehicle meets safety standards such as model certification. In addition, regulations are not limited to regulations in Japan, but also include regulations in the export destination (destination country) of the vehicle.

[0049] In the following description, "software" refers to control commands written into an information processing device such as an ECU (Electronic Control Unit) and data necessary for the control commands.

[0050] In the following description, "installing software on a device" means recording (storing, writing, downloading, etc.) the software on a storage element of the device. In addition, in the following description, "managing information" means storing (storing) information in a database, etc., and managing it in a state where it can be retrieved, updated, deleted, etc.

[0051] In the following description, "traceability" is sometimes abbreviated as "traceability". In addition, in the following description, "evidence" refers to test results, software execution results (execution logs, etc.), review results, etc., which are related materials submitted by the vehicle provider to government departments (such as the Ministry of Land, Infrastructure, Transport and Tourism of Japan) during model certification.

[0052] In the following description, the provider of the vehicle (the manufacturer of the vehicle, designer, person in charge of the regulatory department, etc. (OEM) such as an automobile manufacturer) is referred to as the "vehicle provider". In addition, the provider (supplier) of the equipment installed in the vehicle (ECU, etc.) and the provider (supplier) of the server device on the outside of the vehicle that cooperates with the vehicle is referred to as the "equipment provider". However, the vehicle provider (OEM) and the equipment provider (supplier) are only defined for the convenience of explanation, and are not limited to the management subject and operation subject of the various structures described below.

[0053] In the following description, information not specifically specified as being created by a subject is, for example, information set by a user's input operation or an existing information processing system.

[0054] <Software query information>

[0055] This is information describing how a vehicle provider or a device provider manages software of a device such as an ECU mounted in a vehicle (hereinafter referred to as “software query information 6 ”).

[0056] Figure 1 2 is a diagram for explaining software query information 6. As shown in the figure, software query information 6 includes licensed software query information 21, which is information managed by vehicle provider 2, regulatory requirement information 22, vehicle requirement specifications 23, vehicle structure information 24, system integration verification result report 25, qualification verification result report 26, device requirement specifications 31, software 37, and traceability information 20. In addition, software query information 6 includes device requirement specifications 31, design documents 32 and source code 33, unit verification result report 34, ECU integration verification result report 35, ECU qualification verification result report 36, software 37, and traceability information 30, which are information managed by device providers 3A to 3C. Software query information 6 is managed by a certain grouping such as each vehicle model. In the present embodiment, software query information 6 is managed by each vehicle model.

[0057] Among the information shown in the figure, the licensed software query information 21 is information indicating the correspondence between the regulations under which the license is obtained and the software associated with the license.

[0058] Figure 2 2 is a diagram for explaining the licensed software query information 21. The licensed software query information 21 includes information corresponding to a regulation ID 211 as an identifier of the regulation, a software query number (licensed identifier) ​​212 as an identifier (an identifier for distinguishing each license) newly assigned when the regulation is licensed each time the software is updated, etc., a software ID 213 as an identifier of the software, and verification data D214 as data for verifying the integrity of the binary data indicated by the software ID 213. The software ID 213 includes information for determining the type of software (ID for identifying the ECU, name of the module, etc.) and software version information ("v1.0", etc.). In addition, the software ID may only include version information, and the information for determining the type of software may be managed separately. In this way, the licensed software query information 21 is composed of a combination of a regulation ID, a software query number, and one or more software IDs (information for determining the type (name, etc.) + version information), so that the correspondence between the licensed regulation and the software associated with the license can be managed by distinguishing the software by version level.

[0059] In the example of the licensed software query information 21, for example, in the regulation ID 211 of the record indicated by the reference symbol D21A, "R7902" indicating the second series of the protocol rule No. 79 (Uniform regulations on the licensing of vehicles involving steering devices) is set. In addition, in the record, "R7902001" is set as the software query number 212 indicating the software combination constituting the function corresponding to the regulation, and the record indicates that the software IDs of the software constituting the software combination are "ECU-A v1.0", "ECU-B v1.0" and "ECU-C v1.0".

[0060] return Figure 1 The regulatory requirement information 22 includes information indicating the content required by the regulations for each permission. In the figure, as an example, the regulatory requirement information 22 for use in accordance with "R7902" includes "PREQ79-1" and "PREQ79-2". These correspond to requirements such as "If the driver does not maintain steering control after a maximum of 15 seconds, a visual warning is given." and "If the driver does not maintain steering control after a maximum of 30 seconds, an audible warning is given in addition to the above signal."

[0061] The vehicle requirement specification 23 includes information indicating the requirement specifications of the vehicle system derived from laws and regulations and other requirements. In the figure, as examples, "SREQ4" and "SREQ5" are shown as the vehicle requirement specifications 23. These correspond to requirements such as "If the driver does not maintain steering control after a maximum of 15 seconds, a visual warning is given." and "If the driver does not maintain steering control after a maximum of 30 seconds, an audible warning is given in addition to the above signal." derived from the above-mentioned legal requirements.

[0062] The vehicle configuration information 24 includes information such as the architecture and ECU configuration, and the vehicle model used to configure the vehicle system.

[0063] Figure 3 This is an example of information included in the vehicle configuration information 24. The illustrated vehicle configuration information 24 has a structure in which the identifiers of the devices mounted on the vehicle, i.e., the device IDs, are hierarchically managed (in a tree form) with the vehicle configuration information 24 being the root of the vehicle configuration ID, i.e., the identifier assigned to each vehicle configuration. The correspondence between the vehicle configuration ID and the device IDs of the vehicle configuration ID can be obtained from the illustrated vehicle configuration information 24. Figure 1 The information managed by the equipment providers 3A to 3C shown (equipment requirement specifications 31 and design documents 32 , etc.) is usually also assigned a vehicle model ID and an equipment ID, so the correspondence between this information and the vehicle configuration information 24 can also be obtained.

[0064] Figure 1The system integration verification result report 25 shown includes various information (test specifications, test result reports, etc.) related to the design contents specified by the vehicle requirement specifications 23 and the vehicle structure information 24. In this figure, as examples of the system integration verification result reports 25, there are "TRSREQ 4", "TRSREQ 5", etc.

[0065] The conformity verification result report 26 includes various information (test specification details, test result report, etc.) related to the conformity verification of the function specified by the regulatory requirement information 22. In the figure, the conformity verification result report 26 is exemplified as "TRPREQ 29-1", "TRPREQ 79-2", etc.

[0066] The device requirement specification 31 includes information indicating the content of the specification required for the device installed in the vehicle based on the vehicle requirement specification 23 and the processing structure information 24. In the figure, the device requirement specification 31 of "ECU-A" is shown as "REQ A-1", "REQ A-2", "REQ A-3", etc. These correspond to, for example, "Perform detection (15 seconds)", "Perform detection (30 seconds)", and "Notify ECU-B" derived from the above-mentioned vehicle requirement specification 23 "SREQ4". In addition, the figure also shows that there are device requirement specifications for ECU-B and ECU-C in order to realize the vehicle requirement specification 23. The device requirement specification 31 is specified by the vehicle provider 2 and is open to the device provider. All requirements for ECU (for example, "ECU-A requirements v1.0") are composed of a combination of these device requirement specifications ("REQ A-1", "REQ A-2", "REQ A-3"). The software presented from the device provider 3 to the vehicle provider 2 is managed in accordance with the requirements, and for example, when the provided software is 1 binary data, it corresponds to all requirements for ECU.

[0067] The design document 32 includes various information related to the design of the device (basic design document, detailed design document, test specification details, test results, etc.). In the figure, as an example, the design document 32 of the ECU ("ECU-A design document") manages the design contents composed of "DSN A-1", "DSN A-2", "DSN A-2", etc.

[0068] The source code 33 is the source code of the software installed in the device. In this figure, as the source code 33, a source code "a1.c" etc. composed of a plurality of functions or classes ("Func A-1", "FuncA-2", "FuncA-3") etc. is managed.

[0069] The unit verification result report 34 includes various information related to the verification at the function level (test specification details, test result report, etc.) In the figure, as examples, there are "TRFunc A-1", "TRFunc A-2", "TRFunc A-3", etc. for the verification result report.

[0070] The ECU integration verification result report 35 includes various information (test specification details, test result report, etc.) related to the verification of the design content specified in the design document 32. In this figure, as an example, there are "TRDSN A-1", "TRDSN A-2", "TRDSN A-3", etc. as ECU integration verification result reports.

[0071] The ECU eligibility verification result report 36 includes various information (test specification details, test result report, etc.) related to the eligibility verification of the functions specified by the equipment requirement specifications 31. In the figure, as an example, there are "TRREQ A-1", "TRREQ A-2", "TRREQ A-3", etc. as ECU eligibility verification result reports.

[0072] The software 37 includes software produced based on the device requirement specification 31. The software is produced by the device provider 3 and provided to the vehicle provider 2. The software includes binary codes describing control commands, data (calibration data, etc.) used in executing the control commands, and verification data for verifying their integrity. The software 37 is generated by compiling the source code 33 of the device provider 3.

[0073] The traceability information 20 is information that associates information (hereinafter referred to as "product") created and managed by the vehicle provider 2. The traceability information 20 includes associations between the regulatory requirement information 22 and the vehicle requirement specifications 23, associations between the vehicle requirement specifications 23 and the equipment requirement specifications 31, associations between the regulatory requirement information 22 and the eligibility verification result report 26, and associations between the vehicle requirement specifications 23 and the eligibility verification result report 26.

[0074] The traceability information 30 is information that associates the products produced and managed by the device provider 3. The traceability information 30 includes the association between the device requirement specification 31 and the design document 32, the association between the design document 32 and the source code 33, the association between the source code 33 and the unit verification result report 34, the association between the design document 32 and the ECU integration verification result report 35, the association between the device requirement specification 31 and the ECU qualification verification result report 36, and the association between the device requirement specification 31 and the software 37.

[0075] Figure 4 Examples of traceability information (traceability information 20, 30) are shown. For example, Figure 4The traceability information 20 illustrated in (a) represents the association between the vehicle requirement specification 23 and the equipment requirement specification 31, and the record marked with reference numeral 20a indicates that the vehicle requirement specification "SREQ4 v1.0" is satisfied by the equipment requirement specifications "REQ A-1v1.0", "REQ A-2v1.0", "REQ B-2v1.0", "REQ B-3v1.0", "REQ C-1v1.0", and "REQ C-2v1.0".

[0076] also, Figure 4 The traceability information 30 illustrated in (b) shows the association between the design document 32 and the source code 33, and the record with reference numeral 30a shows that the design "DSN A-1v1.0" is implemented as the function "FUNC A-1v1.0". In the traceability information 20, the required specifications and the like are each assigned an ID to show the association between the IDs. As an example of expressing such traceability information, there is a table format illustrated in the figure.

[0077] Figure 1 The information shown is managed by vehicle model, for example. Figure 1 In the example of management information of the device provider 3 of "ECU-A" (information of device provider 3A) is described, but the device requirement specification 31, design document 32 and source code 33, unit verification result report 34, ECU integration verification result report 35, ECU qualification verification result report 36, and software 37 are prepared and managed for each device provider 3. For example, the device providers 3 of "ECU-B" and "ECU-C" manage the information of device provider 3B and the information of device provider 3C, respectively.

[0078] <Software Query Information Management System>

[0079] Next, an information processing system (hereinafter referred to as "software query information management system 1") shown as one embodiment will be described.

[0080] Figure 5 The schematic structure of the software query information management system 1 is shown. The software query information management system 1 is a management Figure 1 The system for software query information 6 shown in the figure includes a vehicle provider system 100 as an information processing system managed by the vehicle provider 2, one or more device provider systems 200 as information processing systems managed by each device provider 3A to 3C, a test vehicle management device 300, a software distribution device 400, and a test result analysis device 500. These systems and devices are all constructed using one or more information processing devices. In addition, Figure 1The information not explicitly shown in the figure in the software query information 6 is managed in the vehicle provider system 100 or the equipment provider system 200 in a state where it can be searched, updated, deleted, etc. using a database or the like.

[0081] The vehicle provider system 100 and the device provider system 200 are connected in a manner that allows communication via a communication network. In addition, the vehicle provider system 100 is connected in a manner that allows communication with the test vehicle management device 300, the software distribution device 400, and the test result analysis device 500 via a communication network. Each of the above communication networks is constructed using a wired or wireless communication infrastructure, such as a WAN (Wide Area Network), a LAN (Local Area Network), a CAN (Controller Area Network), the Internet, a dedicated line, various public communication networks, etc.

[0082] Figure 6 The following is a hardware configuration example of an information processing device (computer) constituting a vehicle provider system 100, a device provider system 200, a test vehicle management device 300, a software distribution device 400, and a test result analysis device 500. The illustrated information processing device 10 includes a processor 11, a main storage device 12, an auxiliary storage device 13, an input device 14, an output device 15, and a communication device 16. These are connected in a manner capable of communicating via a communication means such as a bus (not shown).

[0083] The information processing device 10 is, for example, a desktop personal computer, an office computer, a host, a mobile communication terminal (a smart phone, a tablet computer, a wearable terminal, a notebook-type personal computer), etc. The information processing device 10 may also include, for example, an operating system, a device driver, a file system, a DBMS (DataBase Management System) (a relational database, NoSQL, etc.), etc. In addition, the information processing device 10 may be implemented using virtual information processing resources such as a cloud server provided by a cloud system, or may be provided as a cloud service by the vehicle provider system 100 or the device provider system 200.

[0084] The processor 11 is composed of, for example, a CPU (Central Processing Unit), an MPU (MicroProcessing Unit), a GPU (Graphics Processing Unit), an AI (Artificial Intelligence) chip, an FPGA (Field Programmable Gate Array), an ASIC (Application Specific Integrated Circuit), or the like.

[0085] The main storage device 12 is a device for storing programs and data, and is, for example, a ROM (Read Only Memory), a RAM (Random Access Memory), a non-volatile memory (NVRAM (NonVolatile RAM)), or the like.

[0086] The auxiliary storage device 13 is, for example, an SSD (Solid State Drive), a hard disk drive, an optical storage device (CD (Compact Disc), DVD (Digital Versatile Disc), etc.), a storage system, a reading / writing device for recording media such as an IC card, an SD card, and an optical recording medium, a storage area of ​​a cloud server, etc. In the auxiliary storage device 13, programs and data can be read in via a reading device for the recording medium and a communication device 16. Programs and data stored (stored) in the auxiliary storage device 13 are read into the main storage device 12 at any time.

[0087] The input device 14 is an interface for receiving input from the outside, and is, for example, a keyboard, a mouse, a touch panel, a card reader, a voice input device, or the like.

[0088] The output device 15 is an interface for outputting various information such as the processing process and processing results. The output device 15 is, for example, a display device (liquid crystal monitor, LCD (Liquid Crystal Display), graphics card, etc.) for visualizing the above various information, a device for converting the above various information into sound (sound output device (speaker, etc.)), and a device for converting the above various information into characters (printing device, etc.). The output device 15 and the input device 14 together constitute a user interface.

[0089] In addition, for example, the information processing device 10 may input and output information with other devices (such as smart phones, tablet computers, notebook computers, and various mobile information terminals) via the communication device 16 .

[0090] The communication device 16 implements communication with other devices. The communication device 16 is a wireless or wired communication interface that implements communication with other devices via a communication network, such as a NIC (Network Interface Card), a wireless communication module, a USB (Universal Serial Bus) module, a serial communication module, etc.

[0091] return Figure 5 The functions of each system and device are described below. The vehicle provider system 100 includes a traceability information management unit 110, an information management unit 111, a regulatory information management unit 112, a traceability information conversion unit 113, an information integration unit 114, a software query number generation unit 115, a software query management unit 116, a test-related information management unit 118, an error information management unit 119, and a software update management unit 125. These functions are realized by the processor 11 of the information processing device 10 constituting the vehicle provider system 100 reading and executing a program stored in the main storage device 12, or by the hardware (FPGA, ASIC, AI chip, etc.) of the information processing device 10.

[0092] The traceability information management unit 110 receives and manages the traceability information (traceability information 30' described later) sent from the equipment provider system 200. Figure 1 The traceability information 20 generated by the vehicle provider 2 is shown.

[0093] Information Management Department 111 Management Figure 1 The vehicle requirement specifications 23, vehicle structure information 24, equipment requirement specifications 31, software 37, system integration verification result report 25, and eligibility verification result report 26 are shown. In addition, these information can be managed by the information management unit 111 using multiple engineering tools or managed in a unified manner using one engineering tool. In short, any structure is sufficient as long as the information management unit 111 can provide the information required when necessary.

[0094] The regulatory information management unit 112 manages information related to regulations applied at the time of vehicle model certification (hereinafter referred to as "regulatory information 1121"). The regulatory information 1121 includes regulatory requirement information 22, templates for reporting materials submitted to government departments, and reported materials. The regulatory information management unit 112 manages regulatory information not only for Japan but also for export destinations (destination countries) of vehicles other than Japan. From the regulatory information of the export destination determined by the destination country information, it is possible to obtain information required for obtaining model certification at the export destination.

[0095] The traceability information conversion unit 113 reads the traceability information 30' prepared in the format prepared by the equipment provider 3, and converts it into a common representation format (hereinafter also referred to as "common format") that can be used by the vehicle provider. The common format is, for example, RDF (Resource Description Framework).

[0096] The information integration unit 114 associates the information managed by the vehicle provider system 100 and the equipment provider system 200 (the information managed by the information management unit 111 and the regulatory information management unit 112) respectively based on the traceability information 30' converted into a common format and the traceability information 20, thereby generating information in which the regulatory requirement information 22, the vehicle requirement specification 23, the equipment requirement specification 31, the design document 32, the source code 33 and the information associated with the regulatory requirement information 22 are associated with the regulatory ID, that is, the vehicle traceability information 40 (equivalent to Figure 1 In this way, by managing the traceability information in a common format such as RDF format, a query language such as SPARQL (Protocol and RDF Query Language) can be used to easily realize a search system capable of flexible multi-angle searches.

[0097] The software inquiry number generating unit 115 generates the licensed software inquiry information 21 based on the vehicle tracing information 40 .

[0098] The software query information management unit 116 combines the vehicle tracing information 40 generated by the information integration unit 114 and the licensed software query information 21 (equivalent to Figure 1 The software query information management unit 116 manages the software related to the software installed on the device in association with the licensed software query information 21). Thus, the information related to the software installed on the device in the software query information 6 is associated with the software query number and the regulatory ID. In addition, the software query information management unit 116 searches the vehicle tracing information 40 in response to the user's request and feeds back the search result to the user. The details of the software query information management unit 116 will be described later.

[0099] The test-related information management unit 118 manages information related to past tests performed on equipment installed in the vehicle during development and previous maintenance (information related to the history of tests performed in the past (hereinafter referred to as "test history information 1181"), and information about the vehicle used in past tests (hereinafter referred to as "test history information 1182"). The test-related information management unit 118 provides the software query information management unit 116 with information based on the managed test history information 1181 and test vehicle information 1182, namely, test information 41, at any time.

[0100] Figure 7 An example of test history information 1181 is shown. The illustrated test history information 1181 is composed of one or more records having test ID 811 , test content 812 , test vehicle structure 813 , software query number 814 , tool used 815 , test implementer 816 , test result 817 , and evidence 818 .

[0101] In the above items, a test ID as an identifier assigned to each test performed on the vehicle is set in the test ID 811. Information indicating the content of the test is set in the test content 812. Information indicating the structure of the test vehicle (the model ID of the test vehicle, the device ID of the device mounted in the test vehicle, the software ID of the software installed on the device, etc.) is set in the test vehicle structure 813. The software query number associated with the test is set in the software query number 814. Information indicating the tool used when performing the test is set in the tool used 815. The name of the implementer of the test is set in the test implementer 816. Information indicating the result of the test is set in the test result 817. The entity of the evidence obtained when implementing the test and the location of the evidence (information indicating a storage location such as a URL) are set in the evidence 818. In addition, the evidence is generated by the test result analysis device 500 and provided to the user via the software query information management unit 116. The specific method for generating the evidence will be described later.

[0102] Figure 8 8 shows an example of the test vehicle information 1182. The test vehicle information 1182 shown in the example is composed of one or more records of each item of the vehicle model ID 821, the vehicle name 822, and the location 823. One record of the test vehicle information 1182 corresponds to one test vehicle.

[0103] Among the above items, the vehicle model ID of the vehicle is set in the vehicle model ID 821. The name of the vehicle is set in the process name 822. The information indicating the arrangement location of the vehicle is set in the arrangement location 823.

[0104] return Figure 5The error information management unit 119 manages information about errors (events) occurring in the equipment mounted in the vehicle (hereinafter referred to as "error information 1191"). The error information management unit 119 provides error information 1191 (information) to the software query information management unit 116 and the test result analysis device 500 at any time. The error information management unit 119 acquires error information by, for example, communicating with an actual vehicle and a test environment. However, the method of acquiring error information is not limited to this.

[0105] Error information 1191 is created, for example, using a template of a declaration material submitted to a government department contained in the regulatory information 1121. The software installed in the device is updated, for example, for the purpose of responding to the error registered in error information 1191. Error information 1191 is used, for example, to inform the user of the error content during vehicle testing and to generate evidence after the test is implemented.

[0106] Fig. 9 An example of error information 1191 is shown. The illustrated error information 1191 is composed of one or more records including error ID 911, date and time 912, vehicle ID 913, vehicle name 914, vehicle model ID 915, motor model 916, content 917, device name 918, device ID 919, software name 921, software ID 922, driving distance 923, driving route 924, error appearance location 925, weather 926, and supplementary information 927.

[0107] In the above items, an error ID as an identifier assigned to each error occurring in the vehicle is set in error ID 911. The date and time at which the error occurred is set in date and time 912. A vehicle ID as an identifier of the vehicle (hereinafter referred to as "the vehicle") in which the error occurred is set in vehicle ID 913. The vehicle name of the vehicle is set in vehicle name 914. The vehicle model ID of the vehicle is set in vehicle model ID 915. The model of the motor installed in the vehicle is set in motor model 916. Information indicating the content of the error is set in content 917. The name of the device (hereinafter referred to as "the device") in which the error occurred is set in device name 918. The device ID of the device is set in device ID 919.

[0108] The name of the software installed in the device is set in software name 921. The software ID of the software installed in the device is set in software ID 922. The total driving distance of the vehicle is set in driving distance 923. Information indicating the driving route of the vehicle when the error occurred is set in driving route 924. Information indicating the location where the error appeared is set in error appearance location 925. Information indicating the weather (weather) when the error occurred is set in weather 926. Supplementary information related to the error (information about evidence, etc.) is set in supplementary information 927.

[0109] When the software of the device installed in the vehicle is updated, the software update management unit 125 performs processing related to the update of the vehicle traceability information 40 and the licensed software query information 21. In addition, the software update management unit 125 receives keyword information of the specified software (for example, identifiers of functions and classes described in the source code (hereinafter referred to as "function ID"), regulatory ID, software query number, software ID, etc.) from the user, determines the software query information 6 (vehicle traceability information 40) containing the source code containing the received keyword information, and provides the user with information related to the determined software query information 6. By referring to the above information, the user can easily and quickly obtain information related to the objects (software, equipment, regulations, etc.) required for re-acceptance of the license and the test (verification) required for acceptance of the license, information related to the test results (evidence, etc.), etc.

[0110] Next, explain Figure 5 As shown in the figure, the device provider system 200 includes an information management unit 201, a traceability information management unit 202, and a traceability information conversion and transmission unit 203. These functions are realized by the processor 11 of the information processing device 10 constituting the device provider system 200 reading out and executing the program stored in the main storage device 12, or by the hardware (FPGA, ASIC, AI chip, etc.) of the information processing device 10.

[0111] Figure 4 The information management unit 201 shown manages Figure 1 The device requirement specification 31, design document 32, source code 33, unit verification result report 34, integration verification result report 35, qualification verification result report 36, software 37, etc. (only a part is shown) are all or part of the software query information 6 (products). The information management unit 111 can manage them separately using multiple engineering tools or can manage them in an overall manner using one engineering tool, as long as the structure can refer to the required information when necessary.

[0112] Traceability Information Management Department 202 Management Figure 1 The traceability information 30 is shown.

[0113] The traceability information conversion and transmission unit 203 transmits the traceability information 30 managed by the traceability information management unit 202 to the vehicle provider system 100. At this time, the information (the traceability information 30) managed by the device provider 3 side that the device providers 3A to 3C want to hide (for example, the part of the source code that they want to hide (function name, etc.)) may be converted (encrypted or replaced with other codes, etc.) and transmitted to the vehicle provider system 100 as the traceability information 30'. By converting the information in this way, the traceability information from the request to the source code can be generated while hiding the information of the device provider 3. When performing the conversion, the traceability information conversion and transmission unit 203, for example, generates and stores the conversion table 38 of the traceability information 30 and the traceability information 30'. When the device provider 3 is requested to provide information from the vehicle provider 2, the traceability information conversion and transmission unit 203, for example, reversely converts the data using the conversion table 38 and refers to the required data.

[0114] Figure 5 The test vehicle management device 300 shown performs information processing related to provision of a test vehicle used when performing a test (verification) related to a license (management of information related to the structure of the test vehicle, test vehicle reservation processing, etc.).

[0115] Figure 5 The software distribution device 400 shown communicates with the gateway device and the server device installed in the vehicle to distribute the software to the device installed in the vehicle and perform processing related to the execution of the software. In addition, the software distribution device 400 provides the execution result of the software to the test result analysis device 500. In addition, the software distribution device 400 communicates with the vehicle provider system 100 to perform various information processing related to the installation of the software in the device installed in the vehicle (management of information related to the tool used for installation, reservation of the tool, sending of the software to the tool, etc.).

[0116] Figure 5 The test result analysis device 500 shown analyzes the execution result of the software provided by the software distribution device 400. In addition, the test result analysis device 500 generates evidence based on the data (communication data) of the communication performed between the devices sent from the bus tracer 60 described later. The test result analysis device 500 communicates with the vehicle provider system 100 via the communication network, and obtains the information (licensed software query information 21, error information 1191, etc.) managed in the vehicle provider system 100 at any time.

[0117] Next, the processing performed in the software inquiry information management system 1 will be described.

[0118] <Software Query Information Generation Process>

[0119] Fig.10 This is a flowchart for explaining the process (hereinafter referred to as "software query information generation process S1000") performed by the vehicle provider system 100 when generating software query information 6 (vehicle tracing information 40, licensed software query information 21). The software query information generation process S1000 will be described below based on this figure.

[0120] Among them, when the software query information generation process S1000 starts, the traceability information management unit 110 is instructed to manage the traceability information 20 (traceability information generated by the vehicle provider 2) and the traceability information 30' (traceability information 30' obtained from the device provider system 200). In addition, at the above start, the information management unit 111 is instructed to manage information such as the vehicle requirement specification 23 and the device requirement specification 31. In addition, at the above start, the regulatory information management unit 112 is instructed to manage the regulatory information 1121 set in advance by the user or the like.

[0121] As shown in the figure, first, the traceability information conversion unit 113 reads the traceability information 30 ′ in a format created by the equipment provider (supplier), and converts it into a common format ( S1011 ).

[0122] Fig.11 is a diagram for explaining traceability information 30' and its conversion. Figure 4 The traceability information 30 shown in the example is information converted by the traceability information conversion and transmission unit 203. The traceability information 30'a, which is a record of the traceability information 30' shown in the example, indicates that the equipment requirement specification "REQ A-1v1.0" is satisfied by the design "DSN yyy v1.0" and the design "DSN zzz v1.0". In addition, "DSN yyy v1.0" and the design "DSN zzz v1.0" are expressions after conversion by the traceability information conversion and transmission unit 203.

[0123] The traceability information 30"a shown in the figure is information in a common format (RDF format) converted by the traceability information conversion unit 113. When using the RDF format, the information is expressed as a sentence composed of subject / predicate / object. In the illustrated traceability information 30"a, "REQ A v1.0" is the subject, "DSN yyy v1.0" and the design "DSN zzz v1.0" are the objects, and "satisfiedby" indicating that "REQ A v1.0" is satisfied by "DSN yyy v1.0" and the design "DSN zzz v1.0" is the predicate. In addition, in RDF, this information is expressed as a URI (Uniform Resource Identifier). In this way, by jointly managing the traceability information in the RDF format, it is possible to use query languages ​​such as SPARQL, and it becomes easy to retrieve related information.

[0124] return Fig.10 Next, the information integration unit 114 associates the information respectively managed by the vehicle provider system 100 and the equipment provider system 200 (the information respectively managed by the information management unit 111 and the regulatory information management unit 112) based on the traceability information 30" converted into a common form and the traceability information 20, and generates information associated with the regulatory ID of the regulatory requirement information 22, the vehicle requirement specification 23, the equipment requirement specification 31, the design document 32, the source code 33, the software 37, and the regulatory requirement information 22, i.e., the vehicle traceability information 40 (S1012).

[0125] In the next loop process S1013S to S1013E, the software inquiry number generating unit 115 generates the licensed software inquiry information 21. The software inquiry number generating unit 115 sequentially selects the regulations (regulation ID) of the regulatory information 1121 managed by the regulatory information managing unit 112 in each loop.

[0126] In the above loop processing S1013S to S1013E, first, the software query number generation unit 115 compares the selected regulation with the vehicle traceability information 40 managed by the software query information management unit 116 (S1014), obtains the ECU associated with the selected regulation through the vehicle requirement specification 23 and the equipment requirement specification 31, and extracts the information of the software 37 installed with the equipment requirement specification 31 (S1015). In addition, when the regulation is only associated with hardware, the subsequent processing is not performed and the process ends.

[0127] In the loop processing S1016S to S1016E, the software query number generating unit 115 sequentially selects the vehicle traceability information 40 associated with the selected regulation extracted in S1015, and acquires the software ID included in the selected vehicle traceability information 40 (S1017).

[0128] When the above loop processing S1013S to S1013E is completed, next, the software inquiry number generating unit 115 newly issues (issues) a software inquiry number for the selected regulation, and generates a set of the selected regulation (regulation ID) and the newly issued software inquiry number (S1018).

[0129] Next, the software inquiry number generating unit 115 associates the set of the regulatory ID and the software inquiry number generated in S1017 with all the software IDs acquired in S1017, and generates the licensed software inquiry information 21 (S1019).

[0130] Next, the software query information management unit 116 associates all the vehicle tracing information 40 extracted in S1015 with the licensed software query information 21 generated in S1019 and stores them as management objects ( S1020 ).

[0131] As described above, the vehicle provider system 100 can efficiently generate the software query information 6 (the vehicle tracing information 40 and the licensed software query information 21 ) based on the tracing information 30 transmitted from the device provider system 200 .

[0132] <Software query information update process>

[0133] Fig.12 This is a flowchart for explaining the process (hereinafter referred to as "software update management process S1200") performed by the software update management unit 125 of the vehicle provider system 100 when updating the software installed in the device. The software update management process S1200 will be explained below using this figure.

[0134] When the software update management process S1200 is started, the traceability information management unit 110 registers updated traceability information 20 (traceability information generated by the vehicle provider) and traceability information 30 ′ (traceability information acquired from the device provider system 200 ) along with the software update.

[0135] First, the software update management unit 125 receives a vehicle model ID from a user ( S1211 ).

[0136] Next, the software update management unit 125 updates the vehicle traceability information 40 using the newly registered traceability information 20 , 30 ′ via the traceability information conversion unit 113 and the message integration unit 114 ( S1212 ).

[0137] Next, the software update management unit 125 extracts the difference between the vehicle traceability information 40 before and after the update (S1213). The difference is extracted by the difference in the version included in each element of the vehicle traceability information 40. In addition, for example, when a function is corrected due to an error, a difference occurs in the source code 33, so it is extracted.

[0138] Next, the software update management unit 125 extracts the regulation ID associated with the element in which the difference is detected ( S1214 ).

[0139] In the subsequent loop processing S1215S to S1215E, the software update management unit 125 sequentially selects the extracted regulation IDs.

[0140] In the above-mentioned loop processing, first, the software update management unit 125 updates the software query information 6 with the updated software ID for the selected regulation ID and registers it (S1216).

[0141] Next, the software update management unit 125 determines whether the software update has an impact on the content of the certification of the selected regulation ID (S1217). If the content of the certification has an impact (S1217: has an impact), the process proceeds to S1218. If the certification has no impact (S1217: has no impact), the process proceeds to S1215E, and the next regulation ID is selected for loop processing (S1215S to S1215E). The judgment of whether the content of the certification has an impact here is performed by, for example, comparing the specification information and verification results obtained from the information management unit 111 based on the traceability information with the content recorded in the declared materials obtained from the regulation information management unit 112, and investigating whether the content of the declared materials needs to be changed. Then, if the content of the declared materials needs to be changed, it is judged that "there is an impact on the content of the certification", and if it does not need to be changed, it is judged that "there is no impact on the content of the certification".

[0142] In S1218, the software update management unit 125 updates the software query number of the selected regulation ID and registers it.

[0143] According to the above description, the user can efficiently grasp the software query number associated with the software update or the software that needs to be updated.

[0144] In addition, in S1218, for example, various information related to the vehicle traceability information 40 associated with the licensed software query information acquired in S1214 may be presented to the user. Thus, for example, the user can refer to various information related to the software to be tested (legal requirement information 22, vehicle requirement specifications 23, equipment requirement specifications 31, design documents 32 (basic design document, detailed design document, test specification details, test results, etc.), source code 33, and submission materials for certification, and can efficiently promote the testing work.

[0145] <Reference Processing of Software Query Information>

[0146] Fig.13 1300 is a flowchart for explaining the processing (hereinafter referred to as "software query information reference processing S1300") performed by the software query information management unit 116 when referring to the software query information. The software query information reference processing S1300 will be explained below using this figure.

[0147] First, the software query information management unit 116 receives the vehicle model ID and information that becomes a keyword (hereinafter referred to as "keyword information") from the user (S1311). In addition, in this example, the reception of the vehicle model ID is optional, and the reception of the keyword information is required.

[0148] Next, the software query information management unit 116 confirms whether the vehicle model ID is specified according to the input from the user (S1312). If the vehicle model ID is included (S1312: YES), the process proceeds to S1316, and if the vehicle model ID is not included (S1312: NO), the process proceeds to S1313S.

[0149] In the loop processing S1313S to S1313E, the software query information management unit 116 sequentially selects the vehicle traceability information 40 for each of all the registered vehicle model IDs.

[0150] In the above loop processing, first, the software query information management unit 116 determines whether the selected vehicle tracing information 40 contains the keyword information received in S1311 (S1314). If the keyword information is contained (S1314: Yes), the process proceeds to S1315. If the keyword information is not contained (S1314: No), the process proceeds to S1313E, the next vehicle tracing information 40 is selected, and the loop processing S1313S to S1313E is performed.

[0151] In S1315 , the software query information management unit 116 acquires and displays the vehicle model ID associated with the selected vehicle traceability information 40 , and receives the selection of the vehicle model ID.

[0152] In S1316, the software query information management unit 116 obtains information associated with the input keyword information (regulatory ID, software query number, vehicle requirements, eligibility verification result report, etc.) from the vehicle traceability information 40 corresponding to the vehicle model ID input or selected by the user, and prompts the user with the obtained information (S1316).

[0153] Thus, the user can easily refer to various information about the software (legislative requirement information 22, vehicle requirement specifications 23, equipment requirement specifications 31, etc.) by appropriately specifying keyword information, and can use it to efficiently promote impact analysis and testing work when updating software.

[0154] <User Interface / Interface>

[0155] Fig.14 The figure shows an example of a menu screen (hereinafter referred to as “software query information management screen 1400 ”) displayed as a user interface by the software query information management unit 116 . As shown in the figure, the illustrated software query information management screen 1400 has a related information query button 1410 , a new registration button 1420 , and an update button 1430 .

[0156] When the related information query button 1410 is operated, the software query information management unit 116 displays Fig.15 The related information query screen 1500 shown in FIG. 1 is displayed when the new registration button 1420 is operated. Fig.16 The software query information new registration screen 1600 shown in FIG. 1600 is displayed when the update button 1430 is operated. Fig.17 The software query information update screen 1700 is shown.

[0157] As shown in FIG. 15 , the related information search screen 1500 includes a vehicle model ID and keyword information input field 1511 , a search result display field 1512 , a tester information display field 1513 , and various menu display fields 1514 .

[0158] When the user inputs a vehicle model ID or keyword information into the keyword information input column 1511 and operates the search button 15111, the software query information management unit 116 receives the input information. The software query information management unit 116 uses, for example, the vehicle traceability information 40 corresponding to the input vehicle model ID to obtain various information associated with the function specified by the keyword information, and displays the obtained information in the display column 1512 of the search result (in addition, the information can also be provided as a link destination). When the vehicle model ID is not set in the input column 1511, the software query information management unit 116 selects the vehicle traceability information 40 having a function associated with it from all the vehicle traceability information 40, and selectably displays the vehicle model ID in the display column 1512 of the search result.

[0159] When a vehicle model ID is selected, the software query information management unit 116 uses the vehicle traceability information 40 corresponding to the selected vehicle model ID to obtain various information and displays it in the search result display column 1512. The various information includes, for example, the regulation ID 211, the software query number 212, the software ID 213, the vehicle requirement specification 23, the system integration verification result report 25, the qualification verification result report 26, the equipment requirement specification 31, the design document 32, the source code 33, the unit verification result report 34, the ECU integration verification result report 35, and the ECU qualification verification result report 36.

[0160] In the display field 1513 of the test-related information, a vehicle reservation button 15131 , a tool reservation button 15132 , and an installation button 15133 are provided.

[0161] The user can make a reservation for a test vehicle (specify the date and time, the place of implementation, the type (model) of the vehicle, and specify a substitute vehicle when an appropriate test vehicle cannot be secured, etc.) by, for example, operating the vehicle reservation button 15131. When the vehicle reservation button 15131 is operated, the software query information management unit 116 sends, for example, the test information 41 associated with the licensed software query information 21 displayed in the display column 1512 of the search result to the test vehicle management device 300. Upon receiving the above test information 41, the test vehicle management device 300 performs a reservation process for the test vehicle based on the test information 41, and sends the result (information about the reservation) to the software query information management unit 116. Upon receiving the above result, the software query information management unit 116 prompts the user with the content (reservation status, etc.).

[0162] In addition, the user can make a reservation of the tool used for the test (specify the date and time, the type and quantity of the tool, etc.) by operating the tool reservation button 15132, for example. When the tool reservation button 15132 is operated, the software query information management unit 116 sends, for example, the test information 41 (information about the tool) associated with the licensed software query information 21 of the information displayed in the display field 1512 of the search result to the software distribution device 400. When the software distribution device 400 receives the test information 41, it performs a tool reservation process based on the test information 41 and sends the result (information about the reservation) to the software query information management unit 116. When receiving the result, the software query information management unit 116 notifies the user of the content (reservation status, etc.).

[0163] When the user operates the installation button 15133, the installation operation required for testing (e.g., sending the program to the software distribution device 400, loading the program to the tool, etc.) is automatically performed. When the installation button 15133 is operated, the software query information management unit 116 sends, for example, the program associated with the licensed software query information 21 displayed in the display field 1512 of the search structure, and the program specified from the information about the software included in the test information 41 associated with the licensed software query information 21 to the software distribution device 400. When receiving the above-mentioned program, the software distribution device 400 writes the received program to each installation target device.

[0164] In the display column 1514 of the various menus, there are provided various information registration buttons 15141 and evidence generation buttons 15142. The user can register (register as a management object of the software query information management unit 116) new messages (such as the licensed software query message 21, the vehicle traceability information 40, and the test information 41) associated with the software to be updated by operating the various information registration buttons 15141. In addition, for example, when the evidence generation button 15142 is operated, the test-related information management unit 118 generates evidence (such as evidence related to the updated software) based on the test information 41 and inputs it into the software query information management unit 116.

[0165] As described above, according to the software query information management system 1 of the present embodiment, when the software is updated, the user can efficiently and reliably determine the software required for the test to be licensed through the update. In addition, for example, when the software is used across vehicle models, the software required for the test can be determined across vehicle models. In addition, the user can use the output license software query information 21 to efficiently obtain traceability information and evidence that needs to be reported to government departments.

[0166] like Fig.16 As shown, the software query information new registration screen 1600 has an input field 1621 for the vehicle model ID and a display field 1622 for the generated result.

[0167] When the user inputs the vehicle model ID in the vehicle model ID input field 1621 and operates the new registration button 16211 , the software query information management unit 116 receives the vehicle model ID.

[0168] The software query information management unit 116 uses the traceability information 20, 30' corresponding to the input vehicle model ID to generate vehicle traceability information 40 together with the traceability information conversion unit 113 and the information integration unit 114. In addition, the software query number generation unit 115 generates software query information and a software query number.

[0169] The software inquiry information management unit 116 outputs the result of the generation process and the generated software inquiry number to the display field 1622 of the generation result.

[0170] As described above, according to the software inquiry information management system 1 of the present embodiment, the user can generate software inquiry information when a new vehicle is developed, and efficiently number the combination of software required for licensing and its inquiry number.

[0171] like Fig.17 As shown, the software query information update screen 1700 includes an input field 1731 for a vehicle model ID and a display field 1732 for update results.

[0172] When the user inputs the vehicle model ID in the vehicle model ID input field 1731 and operates the update button 17311 , the software query information management unit 116 receives the input of the vehicle model ID.

[0173] The software query information management unit 116 uses the traceability information 20, 30' corresponding to the input vehicle model ID to update the vehicle traceability information 40 through the traceability information conversion unit 113 and the message integration unit 114. Then, the software update management unit 125 updates the software query information and the software query number.

[0174] The software query information management unit 116 displays the update processing result and the updated software query number in the update result display column 1732. In this example, the vehicle tracing information 40, the software query information, and the software query number are all successfully updated, and the software query number that is not updated due to the possibility of being affected by the change is displayed as "R13H001", and the software query number that is actually updated due to the change is displayed as "R7902002 (updated)".

[0175] Fig.18 This is a display example when the software query information management system 1 cannot determine whether the software query number needs to be updated when the software query information 6 is updated. The example shown in the figure has the same structure as above except for the display example 1733 of the update result. In the case where it is impossible to determine whether the software query number needs to be updated, as shown in the display example 1733 of the update result in the figure, the software query information management unit 116 displays the vehicle tracing information 40 and the software query information are successfully updated, and displays that the update of the software query number is reserved. In addition, the software query information management unit 116 will display "R13H001 (waiting)" because there is a possibility that it will be affected by the change and it cannot determine whether the software query number needs to be updated, and the software query number that is actually affected and updated is displayed as "R7902002 (update)".

[0176] As described above, according to the software inquiry information management system 1 of the present embodiment, the user can update the software inquiry information when the software is updated, and efficiently update the combination of software required for licensing and its inquiry number.

[0177] As described above in detail, according to the software inquiry information management system 1 of this embodiment, the software inquiry information 6 can be managed collectively using the licensed software inquiry information 21, and information related to legal licenses of software installed in devices mounted in vehicles can be efficiently managed.

[0178] [How to use the system]

[0179] Fig.19 This is a diagram for explaining the usage (use case) of the software inquiry information management system 1 described above.

[0180] For example, before implementing a modification of a function corresponding to model certification, a designer or a person in charge of a regulatory department in a vehicle provider 2 (OEM, etc.) uses software to query the information management system 1 in order to investigate whether the model needs to be certified again, whether there are any models other than the current model required for the re-certification, etc.

[0181] In addition, for example, designers and quality control personnel of vehicle providers 2 (OEM, etc.), or designers among local providers 3, use the software query information management system 1 to determine and distribute the type of software required to build a test environment after implementing modifications to functions corresponding to model certification, or to implement testing after modifications to functions corresponding to model certification are completed.

[0182] Furthermore, for example, after implementing a modification of a function corresponding to model certification, a designer or a person in charge of quality control of the vehicle provider 2 (OEM, etc.) queries the information management system 1 using software in order to obtain evidence by conducting a test.

[0183] In this way, the software inquiry information management system 1 can be used for various purposes and can promptly provide the information required by the user.

[0184] [Test environment]

[0185] Fig. 20This is an example of a test environment (evidence acquisition environment) constructed by a vehicle provider 2 (OEM, etc.) and a device provider (supplier, etc.) when acquiring evidence. As shown in the figure, the illustrated test environment 2000 includes one or more devices 51 to 54 (in this example, ADECU (AD: Autonomous Driving), manufacturer ECU, steering ECU, and operating status recording ECU) that distribute and execute software that becomes a test object (evidence acquisition object), TCU56 (TCU: Telematics Control Unit) that can be connected to a mobile communication network, etc. by controlling these devices 51 to 54, bus tracker 60, and test result analysis device 500. They can be connected to communicate via a communication network 50 such as CAN. TCU56 is connected to the communication network 50 via a gateway 55, for example.

[0186] Device 51 (ADECU) performs information processing related to monitoring and control of autonomous driving. Device 52 (manufacturer ECU) includes a user interface / interface for receiving information from the driver and providing information, such as constituting an IVI (In-Vehicle Infotainment). Device 53 (steering gear ECU) performs information processing related to the control of the steering of the vehicle. Device 54 (operation status recording ECU) performs information processing related to the collection and recording of information on the operating status of each part (function) of the vehicle (collection and recording of log information, etc.). In addition, devices 51 to 54 shown in the figure are merely an example, and the test environment 2000 may also include elements that perform other types of control (transmission ECU, engine control ECU, etc.).

[0187] The bus tracer 60 is constituted by an information processing device provided with a communication device, acquires communication data (packets) circulating in the communication network 50 (packet capture), and inputs the acquired communication data into the test result analysis device 500. The test result analysis device 500 generates evidence based on the input communication data, and transmits the generated evidence to the vehicle provider system 100 via the communication network.

[0188] In addition, the functions of the test result analysis device 500 may be implemented as the functions of the vehicle provider system 100 and the functions of the device provider system 200, and the functions of the test result analysis device 500 and the functions of the bus tracker 60 may be installed in a vehicle or a test bench. In addition, the functions of the test result analysis device 500 may be implemented by various dispersed elements such as the vehicle provider system 100, the device provider system 200, the vehicle constituting the test environment 2000, and the test bench.

[0189] [Generation of evidence]

[0190] Fig.21 This is a flowchart for explaining the process of automatically generating evidence (hereinafter referred to as "evidence generation process S2100") performed by the vehicle provider system 100 in the software query information management system 1 using information acquired in the test environment 2000. The evidence generation process S2100 will be explained below using this figure.

[0191] The error information management unit 119 of the vehicle provider system 100 obtains error information (event information) from the actual vehicle and test environment at any time, and stores the obtained error information as error information 1191 (S2111). The error information management unit 119 provides the error information 1191 to the test result analysis device 500 via the communication network at any time. Fig. 9 As shown, the error information 1191 includes information that associates information identifying the device where the error occurred (device name 918, device ID 919) with information identifying software installed in the device (software name 921, software ID 922).

[0192] The test result analysis device 500 compares the error information 1191 provided from the error information management unit 119 with the licensed software query information 21, and identifies the regulation ID associated with the software ID 922 of the error information 1191 (S2112).

[0193] Next, the test result analysis device 500 determines other software IDs associated with the determined regulation ID based on the licensed software query information 21 (S2113). The test result analysis device 500 acquires the licensed software query information 21 at any time by communicating with the vehicle provider system 100 via a communication network, for example.

[0194] Next, the test result analysis device 500 identifies the device in which the software having the software ID identified in S3113 is installed based on the vehicle traceability information 40 (S2114). In addition, the result analysis device 500 acquires the traceability information 40 by communicating with the vehicle provider system 100 via a communication network, for example.

[0195] Next, the test result analysis device 500 acquires the communication data related to the device specified in S2114 from the bus tracer 60 (S2115). The communication data includes information specifying the source address of the communication data and the destination address of the communication data as header information.

[0196] Next, the test result analysis device 500 generates evidence based on the communication data acquired in S2115 and transmits it to the test-related information management unit 118 via the communication network ( S2116 ). The test-related information management unit 118 stores the transmitted evidence as evidence 818 of the test history information 1181 .

[0197] Fig. 22 Yes Description Fig. 20 2 is a sequence diagram of the process performed by the bus tracer 60 in the test environment 2000 when acquiring communication data (hereinafter referred to as "communication data acquisition process S2200"). In the communication data acquisition process S2200, the bus tracer 60 acquires communication data related to the operation of the automatic operation function performed by the device 51 (ADECU) as the main body.

[0198] As shown in the figure, first, when device 51 (ADECU) starts to operate, the communication data notifying the content is sent from device 51 (ADECU) to device 54 (operating status recording ECU) (S2211) via the communication network 50, and device 54 (operating status recording ECU) receives the above communication data and records (stores in a storage device, the same below) the content of the communication data.

[0199] Next, when device 51 (ADECU) detects that the driving environment has changed (for example, the weather has changed and the road conditions have changed), communication data notifying the content is sent from device 51 (ADECU) to device 54 (operating status recording ECU) (S2212) via communication network 50, and device 54 (operating status recording ECU) receives the above communication data and records the content of the communication data.

[0200] Next, device 51 (ADECU) sends communication data containing an alarm output start indication for prompting the driver to continue driving (switch to manual driving) to device 52 (manufacturer ECU) (S2213), and device 52 (manufacturer ECU) receives the above communication data and outputs (display, sound output, etc.) an alarm.

[0201] Next, device 51 (ADECU) sends communication data notifying the activation of the alarm to device 54 (operation status recording ECU) via communication network 50 (S2214), and device 54 (operation status recording ECU) receives the communication data and records the content of the communication data.

[0202] Next, device 51 (ADECU) sends communication data notifying the driver of the reason (main cause) for continuing driving (for example, the center line of the road (central dividing line, etc.) cannot be detected) to device 54 (operating status recording ECU) (S2215) via communication network 50, and device 54 (operating status recording ECU) receives the above communication data and records the content of the communication data.

[0203] Next, the device 53 (steering gear ECU) sends the communication data of the content that the driver has started manual driving to the device 51 (ADECU) via the communication network 50 (S2216), and the device 51 (ADECU) receives the above communication data. In addition, the device 53 (steering gear ECU) sends the communication data of the content that the automatic driving is stopped and the manual driving is started to the device 54 (operation status recording ECU) via the communication network 50 (S2217), and the device 54 (operation status recording ECU) receives the above communication data and records the content of the communication data.

[0204] Next, the device 53 (steering gear ECU) sends the communication data including the alarm output stop instruction to the device 52 (manufacturer ECU) (S2218), and the device 52 (manufacturer ECU) receives the communication data and stops the alarm output. In addition, the device 53 (steering gear ECU) sends the communication data notifying that the alarm output has stopped to the device 54 (operation status recording ECU) (S2219) via the communication network 50, and the device 54 (operation status recording ECU) receives the communication data and records the content of the communication data.

[0205] The bus tracer 60 acquires (captures) the communication data circulating in the communication network 50 in the above sequence, and inputs the acquired communication data into the test result analysis device 500 .

[0206] Fig.23 An example of communication data acquired by the bus tracer 60 and input into the test result analysis device 500 according to the above sequence is shown (each line is equivalent to one communication data). The test-related information management unit 118 generates evidence 818 based on the communication data input from the test result analysis device 500. In addition, the communication data can also be recorded in the process of generating evidence for subsequent analysis. As shown in the example, the communication data includes information indicating the date and time of sending from the sending address to the delivery address (hereinafter referred to as "time stamp"). By using this time stamp, for example, it is possible to compare the generation interval (time) of the newly acquired communication data with the generation interval (time) of the communication data acquired in the past to realize error detection and sign detection, and determine whether a warning output is necessary.

[0207] As described above, according to the software query information management system 1 of this embodiment, it is possible to efficiently generate evidence 818 using the information obtained in the test environment 2000. In addition, the method for generating evidence shown above is only an example, and evidence can also be obtained using other methods. In addition, in the above description, evidence is generated based on information about an event called an error, but evidence can also be generated based on information about events other than errors.

[0208] The embodiments of the present invention are described in detail above, but the present invention is not limited to the embodiments described above, but includes various modifications and equivalent structures within the scope of the claimed rights. For example, the above-mentioned embodiments are described in detail to make the present invention easy to understand, but are not necessarily limited to including all the structures described. In addition, a part of the structure of one embodiment can be replaced with the structure of another embodiment. In addition, the structure of another embodiment can be added to the structure of one embodiment. In addition, other structures can be added / deleted / replaced to a part of the structure of each embodiment.

[0209] In the description of the present invention, an example of ECU is illustrated as a component, but there is also a case where regulatory requirements and system requirements are constituted in cooperation with not only the on-board ECU but also a server device configured outside the vehicle. In this case, the system requirements are decomposed into requirements for the server device and requirements for the vehicle, and the requirements for the vehicle are further decomposed into requirements for the ECU. However, in the case where the requirements are directed to the server device, it can also be considered that in such a case, as long as the above-mentioned equipment requirement specifications are regarded as requirements for the server device, the same management can be performed. That is, the impact analysis on the license can also be uniformly performed on the functions across the vehicle and the server device.

[0210] In the above invention, the traceability information conversion unit 113 is configured in the vehicle provider system 100, but it may be configured in the traceability information conversion and transmission unit 203 of the equipment provider 200. In this way, the vehicle provider can receive the traceability information in a unified format.

[0211] In addition, the above-mentioned structures, functions, processing parts, processing units, etc. can be implemented in part or in whole by hardware, for example, by designing with integrated circuits, or by software by interpreting and executing programs that implement their respective functions on processors.

[0212] Information such as programs, diagrams, and files that implement various functions can be stored in recording devices such as memories, hard disks, SSDs (Solid State Drives), or recording media such as IC (Integrated Circuit) cards, SD cards, and DVDs (Digital Versatile Discs).

[0213] For control lines and information lines, only those considered necessary for the description are shown, and not all control lines and information lines on the product are necessarily shown. In fact, it can also be considered that almost all structures are connected to each other.

[0214] Description of Reference Numerals

[0215] 1…Software query information management system, 2…Vehicle provider, 3A~3C…Equipment provider, 6…Software query information, 21…Licensed software query information, 22…Regulatory requirements information, 23…Vehicle requirements specifications, 30…Traceability information, 31…Equipment requirements specifications, 32…Design document, 33…Source code, 40…Vehicle traceability information, 100…Vehicle provider system, 111…Information management department, 112…Regulatory information management department, 113…Traceability information conversion department, 1121…Regulatory information, 114…Information integration department, 115…Software query number generation department, 116…Software query information management department, 118…Test related information Information management unit, 1181…test history information, 1182…test vehicle information, 119…error information management unit, 1191…error information, 200…equipment provider system, 202…traceability information management unit, 203…traceability information conversion and sending unit, 300…test vehicle management device, 400…software distribution device, 500…test result analysis device, 2000…test environment, 51~54…equipment, 50…communication network, 55…gateway, 56…TCU, 60…bus tracker, S700…software query information generation processing, S2100…evidence generation processing, S2200…communication data acquisition processing.

Claims

1. A software query information management system for managing information about legal licenses for software, wherein the software is used to implement a function of a device mounted on a vehicle, the software query information management system being characterized by: storing device requirement specifications in association with a regulation ID, wherein the regulation ID is information for identifying a regulation that stipulates requirements that a vehicle must satisfy in order to obtain a legal license, and the device requirement specifications are information on specifications required by the regulation for the device, acquiring traceability information, the traceability information being information on the traceability of the device associated with the device requirement specification, The traceability information includes a software ID for determining the software installed in the device, generating software query information, the software query information being information obtained by associating the regulation ID corresponding to the equipment requirement specification associated with the acquired traceability information with one or more software IDs, storing event information as information about an event occurring in the device, the event information including information obtained by establishing a correspondence between information for identifying the device in which the event occurred and a software ID of the software that implements a function of the device, determining the software ID of the other software associated with the regulatory ID corresponding to the software ID in the event information based on the software query information, Based on the traceability information, determining the device on which the determined software ID is installed, acquiring, via a bus tracer connected to a communication network that communicatively connects the devices, communication data including content of communication performed between the determined device and other devices, Evidence required to obtain the legal consent is generated based on the communication data.

2. The software query information management system according to claim 1, characterized in that: The software ID includes information for identifying the type of the software and version information.

3. The software query information management system according to claim 1, characterized in that: For each combination of one or more vehicle models, one or more devices, and one or more regulations, a software query number as information associating the regulation ID with the one or more software IDs is generated and managed.

4. The software query information management system according to claim 3, characterized in that: The traceability information includes the source code of the software, The software query information is information obtained by establishing a corresponding relationship between the software query number and the traceability information. receiving keyword information as information identifying a function of the source code or a part thereof, determining one or more software query numbers including the received keyword information, The software ID of the other software associated with the regulatory ID corresponding to the software ID in the event information is determined based on the software query information associated with the determined software query number.

5. The software query information management system according to claim 4, characterized in that: The keyword information is an identifier of a function described in the source code or an identifier of a device requirement specification.

6. The software query information management system according to claim 4, characterized in that: One or more software IDs included in the traceability information of the determined one or more software query numbers are determined as the software IDs of the other software.

7. A software query information management method for managing information about legal licenses for software, wherein the software is used to implement a function of a device mounted on a vehicle, the software query information management method being characterized by: The information processing device performs: a step of storing equipment requirement specifications in association with a regulation ID, wherein the regulation ID is information for identifying a regulation that stipulates requirements that a vehicle must satisfy in order to obtain a legal license, and the equipment requirement specifications are information on specifications required by the regulation for the equipment; and a step of acquiring traceability information, the traceability information being information on the traceability of the device associated with the device requirement specification, The traceability information includes a software ID for determining the software installed in the device, The information processing device executes: generating software query information by associating the regulation ID corresponding to the equipment requirement specification associated with the acquired traceability information with one or more software IDs; A step of storing event information as information about an event occurring in the device, the event information including information obtained by establishing a correspondence between information for identifying the device in which the event occurred and a software ID of the software that implements a function of the device; Based on the software query information, determining the software ID of other software associated with the regulatory ID corresponding to the software ID in the event information; Based on the traceability information, determine the device on which the determined software ID is installed; A step of acquiring communication data including the content of the communication conducted between the determined device and other devices via a bus tracer connected to a communication network that communicatively connects the devices; and The step of generating evidence required to obtain the legal permission based on the communication data.

8. The software query information management method according to claim 7, characterized in that: The software ID includes information for identifying the type of the software and version information.

9. The software query information management method according to claim 7, characterized in that: The information processing device further executes the step of generating and managing a software query number as information associating the regulation ID with one or more software IDs for each combination of one or more vehicle models, one or more devices, and one or more regulations.

10. The software query information management method according to claim 9, characterized in that: The traceability information includes the source code of the software, The software query information is information obtained by establishing a corresponding relationship between the software query number and the traceability information. The information processing device further executes: The step of receiving keyword information as information for determining a function of said source code or a part thereof; The step of determining one or more software query numbers including the received keyword information; and The step of determining the software ID of the other software associated with the regulatory ID corresponding to the software ID in the event information based on the software query information associated with the determined software query number.

11. The software query information management method according to claim 10, characterized in that: The keyword information is an identifier of a function described in the source code or an identifier of a device requirement specification.

12. The software query information management method according to claim 10, characterized in that: The information processing device further executes a step of determining one or more software IDs included in the traceability information of the determined one or more software query numbers as the software IDs of other software.

Images