Information processing device

Abstract

To make it possible to obtain communication specifications for a specific vehicle without imposing enormous labor on a designer.SOLUTION: An information processing device 20 is configured to: acquire architecture model information including information obtained by aggregating communication paths between ECUs in multiple types of vehicles and information representing, for each communication path, a data communication standard by which data can be exchanged via each communication path; acquire variation information including information for specifying a necessary communication path required in a specific vehicle and information for specifying necessary data that needs to be exchanged via the necessary communication path; and generate communication specifications that specify a relation between the necessary data and the communication path through which the necessary data should be transmitted based on the architecture model information and the variation information. When the communication specifications are generated, a communication path is specified for each necessary data so as to satisfy the data communication standard defined for each necessary data.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to an information processing device. [Background technology]

[0002] The vehicle disclosed in Patent Document 1 includes a plurality of ECUs, which are connected to one another via a bus, and which transmit and receive necessary data via the bus. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2022-121156 Summary of the Invention [Problem to be solved by the invention]

[0004] In a vehicle having multiple ECUs, such as that described in Patent Document 1, the types of ECUs installed in the vehicle vary depending on the vehicle model. Furthermore, the communication paths between ECUs and the data communication standards between ECUs vary depending on the type of ECU installed in the vehicle. Therefore, when designing a new vehicle having multiple ECUs, it is necessary to redesign communication rules, such as data transmission timing, taking into account the communication paths used in the vehicle and the types of data that need to be exchanged over those communication paths. Meanwhile, the number of ECUs installed in a vehicle is enormous. Conventionally, designers themselves have designed communication rules for each vehicle, taking into account the combinations of such a huge number of ECUs. Therefore, designing communication rules for each vehicle required a huge amount of effort. [Means for solving the problem]

[0005] An information processing device for solving the above problem acquires architecture model information including information aggregating communication paths between ECUs in multiple types of vehicles and information representing, for each communication path, one or more data communication standards by which data can be exchanged over each of the communication paths; acquires variation information including information specifying necessary communication paths required in a specific vehicle and information specifying necessary data that needs to be exchanged over the necessary communication paths; and generates communication specifications that specify the relationship between the necessary data and the communication paths through which the necessary data should be transmitted based on the architecture model information and the variation information; and when generating the communication specifications, specifies the communication path for each of the necessary data so as to satisfy the data communication standard defined for each of the necessary data. [Effects of the Invention]

[0006] The above technical concept allows the communication specifications of a particular vehicle to be obtained without imposing a huge amount of effort on the designer. [Brief explanation of the drawings]

[0007] [Figure 1] FIG. 1 is a schematic diagram of the design system. [Figure 2] FIG. 2 is a diagram showing a schematic representation of architecture model information. [Figure 3] FIG. 3 is a flowchart showing the procedure of the specification generation process. [Figure 4] FIG. 4 is a diagram showing a schematic diagram of how necessary data is grouped. [Figure 5] FIG. 5 is a diagram showing a schematic diagram of how necessary data is grouped. DETAILED DESCRIPTION OF THE INVENTION

[0008] An embodiment of an information processing apparatus will be described below with reference to the drawings. <Overall structure> 1 is installed in, for example, a vehicle design facility. The design system 10 includes an information processing device 20, a display 12, and an input device 14.

[0009] The information processing device 20 is a so-called computer. The information processing device 20 includes a CPU 21, a database 22, and a primary storage device 23. The database 22 is a non-volatile memory. The primary storage device 23 is a volatile memory. The database 22 stores in advance a program W in which the processing to be executed by the CPU 21 is described. The database 22 also stores in advance architecture model information AM. The architecture model information AM will be described in detail later.

[0010] The display 12 is capable of communicating with the information processing device 20. The display 12 displays an image according to a signal output by a CPU 21 of the information processing device 20. The input device 14 is capable of communicating with the information processing device 20. The input device 14 is used to input information to the information processing device 20 from outside. The input device 14 is, for example, a keyboard and a mouse.

[0011] The CPU 21 of the information processing device 20 can execute a specification generation process by executing a program W stored in the database 22. The specification generation process is a process for generating communication specifications for a vehicle. The specification generation process is used when a designer designs a new vehicle. Here, the vehicle to be designed includes multiple on-board devices and multiple ECUs for controlling these on-board devices. The communication specifications specify the relationship between the data exchanged between these ECUs and the communication path RT to be used for exchanging the data. In this embodiment, one communication path RT is defined as follows: That is, one communication path RT is a path connecting two ECUs. One ECU is the ECU that transmits data. The other ECU is the ECU that receives data. ECU is an abbreviation for "Electronic Control Unit."

[0012] <Architecture model information> As shown in FIG. 2, the architecture model information AM includes total route information AR, total standard information AS, and application information AP.

[0013] The total route information AR is information that aggregates the communication routes RT between ECUs in multiple types of vehicles. FIG. 2 shows the total route information AR in a schematic manner. FIG. 2 also shows only five representative ECUs among the multiple ECUs. In this embodiment, the multiple types of vehicles refer to all possible types of vehicles, including, for example, all vehicle models sold by a specific vehicle manufacturer and all vehicle models expected to be designed in the future. The communication routes RT aggregated in the total route information AR are a collection of communication route RT patterns adopted in each vehicle model for all vehicle models, covering all of these types of vehicles.

[0014] For example, the total route information AR is a table summarizing the communication routes RTs shown in FIG. 2. For example, this table summarizes, for each communication route RT, four identification values ​​prepared for each communication route RT. The four identification values ​​are a route identification value, a first identification value, a second identification value, and a route identification value. The route identification value is an identification value for each communication route RT assigned to each communication route RT. The first identification value is an ECU identification value for one of the two ECUs connected by the target communication route RT. The second identification value is an ECU identification value for the other of the two ECUs connected by the target communication route RT. The route identification value is an identification value indicating a route pattern when the target communication route RT passes through another relay ECU between two ECUs. As can be seen from the existence of the route identification value, for example, there are multiple communication routes RTs connecting two ECUs, ECU1 and ECU3, shown in FIG. 2. The ECU identification value is an identification value for each ECU assigned to each ECU.

[0015] The total standard information AS is a compilation of the data communication standards DS prepared for each communication route RT for all communication routes RT. The data communication standards DS are a table summarizing the communication standards that can exchange data over each communication route RT. One or more data communication standards DS are prepared for each communication route RT. For example, only one data communication standard DS is prepared for communication route RT1 shown in Figure 2. On the other hand, multiple data communication standards DS are prepared for communication route RT2 shown in Figure 2. Each data communication standard DS is assigned an individual standard identification value. When multiple data communication standards DS are prepared for one communication route RT, the standard identification values ​​of these multiple data communication standards DS are different from each other. The standard identification value of each data communication standard DS is linked to information indicating the communication route RT in the total route information AR, i.e., the route identification value.

[0016] The data communication standard DS defines the following multiple items: a data source ECU, a data destination ECU, a data transmission cycle, a data capacity per transmission / reception, a security level, and a communication route RT targeted by the data communication standard DS. Among these multiple items, the data source ECU, the data destination ECU, and the communication route RT are represented by the identification values ​​already described. In this embodiment, the security level is either "0" or "1." A security level of "0" means that security information does not need to be assigned to the data. A security level of "1" means that security information needs to be assigned to the data. Note that, as described above, multiple data communication standards DS may be prepared for one communication route RT. In this case, these multiple data communication standards DS may have items that share common content and items that may have different content. The items that share common content are the data source ECU, the data destination ECU, and the communication route RT. The items that may have different content are the data transmission cycle, the data capacity, and the security level.

[0017] The application information AP is a compilation of application lists LP prepared for each communication route RT for all communication routes RT. Here, multiple types of data are transmitted and received over a given communication route RT. The application list LP defines, for each data type, the correspondence between the type of data transmitted and received over a given communication route RT and the data communication standard DS to be used when transmitting and receiving that type of data. The data type here refers to the type of parameters detected by each sensor, such as intake air volume and fuel injection volume. As shown in Figure 2, the application list LP associates the data identification values ​​of multiple types of data transmitted and received over a given communication route RT with the standard identification values ​​of the data communication standard DS to be applied to each data. The data identification value is an identification value assigned to each data.

[0018] As explained above in the total standard information AS, there are cases where only one data communication standard DS is set for one communication route RT, and cases where multiple data communication standards DS are set for one communication route RT. When only one data communication standard DS is set for one communication route RT, all data exchanged over this communication route RT is exchanged using the same data communication standard DS. Reflecting this, for example, when only one data communication standard DS is set for one communication route RT, as in the communication route RT1 shown in Figure 2, only one application list LP is prepared for this communication route RT.

[0019] On the other hand, when multiple data communication standards DS are set for one communication route RT, such as the communication route RT2 shown in FIG. 2, data exchanged over this communication route RT is transmitted and received using various data communication standards DS. There are various patterns for applying the data communication standard DS to each data. Specifically, even for the same type of data, the data communication standard DS to be applied when transmitting the data may differ depending on the various programs applied to the vehicle. Reflecting this, when multiple data communication standards DS are prepared for one communication route RT, multiple application lists LP are prepared for the communication route RT. Each application list LP assigns the multiple data communication standards DS to each data in a different way. For example, suppose two of the multiple application lists LP prepared for the communication route RT1 are compared. In one application list LP, the first data communication standard DS1 is assigned to data "A" and data "C," and the second data communication standard DS2 is assigned to data "B." In contrast, in the other application list LP, the first data communication standard DS1 is assigned to data "A" and data "B", and the second data communication standard DS2 is assigned to data "C". In this way, the way in which the data communication standard DS is assigned to each data differs for each application list LP. Each application list LP is assigned a unique application identification value. As with the data communication standard DS, if multiple application lists LP are prepared for one communication route RT, the application identification values ​​of these multiple application lists LP are different from one another. The application identification value of each application list LP is linked to information indicating the communication route RT in the total route information AR, i.e., to the route identification value.

[0020] <Variation information> When generating communication specifications for a new vehicle using a specification generation process, a designer creates variation information V in advance. The variation information V is information for specifying basic communication information for a specific vehicle to be designed. Specifically, the variation information V includes information specifying multiple required communication paths and information specifying multiple required data. The required communication paths are communication paths RT required for the vehicle to be designed. The required data is data that needs to be exchanged via the required communication paths. The information specifying the required communication paths is, for example, a path identification value indicating the required communication paths. The information specifying the required data is, for example, a data identification value indicating the required data. The required communication paths and required data are basically determined by the types of multiple on-board devices to be installed in the vehicle to be designed. In other words, once the types of multiple on-board devices to be installed in the vehicle are determined, the multiple ECUs required to control those on-board devices are determined. Once the multiple ECUs to be installed in the vehicle are determined, the communication paths RT connecting those multiple ECUs are determined. Furthermore, once the multiple ECUs to be installed in the vehicle are determined, the required data is determined in consideration of the processing content performed by those ECUs. From this perspective, multiple necessary communication paths and multiple necessary data are defined. The multiple necessary data specified in the variation information V are limited to those that can be transmitted via any of the multiple necessary communication paths specified in the variation information V. However, the variation information V does not specify which communication path RT should be used to transmit each piece of necessary data. Once the multiple necessary communication paths and multiple pieces of necessary data to be used in the design vehicle are determined, the transmission cycle, data volume per transmission / reception, and security level required for each piece of necessary data are also determined. Accordingly, in the variation information V of this embodiment, these three items are also specified for each piece of necessary data.

[0021] <Details of the specification generation process> When the designer creates the variation information V, the designer stores the created variation information V in the database 22 of the information processing device 20. Thereafter, the designer instructs the CPU 21 of the information processing device 20 to execute a specification generation process. Upon receiving this instruction, the CPU 21 starts the specification generation process. Note that, although a detailed description will be omitted, in the specification generation process, the CPU 21 identifies the communication path RT and the like by referencing various identification values ​​indicated in the architecture model information AM and the variation information V. Also, although a detailed description will be omitted, in the specification generation process, the CPU 21 appropriately uses the primary storage device 23.

[0022] 3, when the CPU 21 starts the specification generation process, it first executes the process of step S10. In step S10, the CPU 21 acquires architecture model information AM from the database 22. The CPU 21 also acquires variation information V from the database 22. After this, the CPU 21 proceeds to the process of step S20. Note that in step S10, the CPU 21 may acquire the architecture model information AM and the variation information V from an external server that is an information processing device different from the information processing device 20. In this case, it is sufficient to store the architecture model information AM and the variation information V in the external server. Then, it is sufficient to enable communication between the information processing device 20 and the external server.

[0023] In step S20, the CPU 21 identifies an application list LP for each necessary communication path specified in the variation information V. Specifically, the CPU 21 first identifies multiple necessary communication paths specified in the variation information V from all communication paths RT included in the total path information AR of the architecture model information AM. Then, the CPU 21 performs the following for each identified necessary communication path. That is, the CPU 21 identifies an application list LP linked to the necessary communication path from the application information AP of the architecture model information AM. Note that if multiple application lists LP are prepared for the target necessary communication path, the CPU 21 identifies one optimal application list LP from the multiple application lists LP based on the combination of necessary communication paths and the combination of necessary data specified in the variation information V. Once the CPU 21 has identified one application list LP for one necessary communication path, the process proceeds to step S30.

[0024] In step S30, the CPU 21 generates a required data standard DSX for each required data item specified in the variation information V. Specifically, in step S30, the CPU 21 performs the following process. Using the application list LP for each required communication path identified in step S20, the CPU 21 identifies a data communication standard DS corresponding to each required data item specified in the variation information V. For example, one of the multiple required data items is referred to as first data. With regard to this first data item, the CPU 21 references the application list LP identified in step S20 that includes the data identification value of the first data item. Based on this application list LP, the CPU 21 then identifies a standard identification value corresponding to the first data item. The CPU 21 then identifies a data communication standard DS corresponding to the identified standard identification value from the total standard information AS in the architecture model information AM. The CPU 21 then assigns the data identification value of the first data item to the identified data communication standard DS. The CPU 21 treats the set of the data communication standard DS and the data identification value thus obtained as the required data standard DSX for the first data item. Depending on the combination of the required data and required communication paths specified in the variation information V, the following may occur. That is, there are multiple cases in which there are multiple routes through which the first data can be transmitted among the multiple required communication paths specified in the variation information V. In these multiple cases, there are as many application lists LP containing the data identification value of the first data as there are routes through which the first data can be transmitted. Therefore, in the multiple cases, the CPU 21 selects a data communication standard DS corresponding to one of the multiple application lists LP based on the following criteria. That is, the CPU 21 selects a data communication standard DS that matches the transmission cycle, data volume, and security level specified for the first data in the variation information V. If this selection does not yet narrow down the data communication standard DS to one, the CPU 21 further narrows down the options. That is, the CPU 21 selects one data communication standard DS from the multiple data communication standards DS narrowed down based on the above criteria, in accordance with a predetermined rule.The predetermined rule may be, for example, to select the data communication standard DS corresponding to the shortest route among multiple routes over which the first data can be transmitted. The predetermined rule may be any rule established from the viewpoint of efficient vehicle communication. The CPU 21 generates the required data standard DSX for all the required data specified in the variation information V in the same manner as for the first data described above. Then, the CPU 21 obtains one required data standard DSX for each required data. After this, the CPU 21 proceeds to step S40.

[0025] In step S40, CPU 21 groups the multiple pieces of necessary data specified in variation information V. In performing this grouping, CPU 21 refers to the necessary data standard DSX for each piece of necessary data generated in step S30. Note that, below, a detailed description of how CPU 21 refers to the necessary data standard DSX will be omitted.

[0026] The processing of step S40 will be described in detail. First, the CPU 21 designates a group of multiple pieces of necessary data that satisfy the prerequisite that the ECU from which they are sent is the same as one another. By doing so, the CPU 21 divides the multiple pieces of necessary data into multiple groups. After this, the CPU 21 performs the following processing for each group divided based on the prerequisite. The contents of this processing will be described with reference to Figures 4 and 5. Note that in Figures 4 and 5, solid-lined squares represent necessary data.

[0027] First, if there is a plurality of pieces of required data that satisfy the first condition among the plurality of pieces of required data that satisfy the prerequisites, the CPU 21 designates a group of the plurality of pieces of required data that satisfy the first condition. As a result, the CPU 21 divides the plurality of pieces of required data that satisfy the prerequisites into a plurality of groups, as shown by the two-dot chain line G1 in Figure 4. The first condition is that the destination ECUs defined in the required data standard DSX are the same, and the communication paths RT defined in the required data standard DSX are the same.

[0028] Furthermore, if there is a plurality of pieces of required data that satisfy the second condition among the plurality of pieces of required data that satisfy the first condition, CPU 21 designates a group of the plurality of pieces of required data that satisfy both the first and second conditions as one group. As a result, CPU 21 divides the plurality of pieces of required data that satisfy the first condition into multiple groups, as shown by the dashed-dotted line G2 in Figure 4. The second condition is that the transmission cycles defined in the required data standard DSX are the same.

[0029] Furthermore, if there is a plurality of pieces of required data that satisfy the third condition among the plurality of pieces of required data that satisfy the first and second conditions, the CPU 21 designates a group of the plurality of pieces of required data that satisfy the first, second, and third conditions. As a result, as shown by the dotted line G3 in Figure 4, the CPU 21 divides the plurality of pieces of required data that satisfy the first and second conditions into multiple groups. The third condition is that the security levels defined by the required data standard DSX are the same. In Figure 4, required data with a security level of "0" are shown in white. In Figure 4, required data with a security level of "1" are shown in black.

[0030] After this, the CPU 21 performs the following on a group of multiple necessary data that satisfy the first, second, and third conditions. That is, the CPU 21 groups multiple necessary data that satisfy the first, second, and third conditions, as shown by the dotted line G4 in Figure 5, so that the total volume of the multiple necessary data included in one group is equal to or less than a set capacity. The set capacity is the maximum total volume of necessary data allowed in one transmission and reception. Figure 5 shows an example in which the six necessary data surrounded by the dotted line G3 in Figure 4 are divided into two groups. In Figure 5, as in Figure 4, the necessary data is shown in white or black depending on the security level.

[0031] Thereafter, the CPU 21 assigns an individual group identification value ID to each group. In FIG. 5, the group identification value IDs are represented by "Q1," "Q2," and "Q3." Note that there may be necessary data that cannot be grouped, for example, because the first condition or the second condition is not satisfied. The CPU 21 assigns an individual group identification value ID to such necessary data. As shown in FIG. 3, once the CPU 21 has assigned a group identification value ID to each group, the process proceeds to step S50.

[0032] In step S50, the CPU 21 generates a communication specification list. The communication specification list is a collection of communication specifications that specify the relationship between various types of necessary data and the communication route RT through which each required data should be transmitted. Specifically, the communication specification list is a table that summarizes communication-related settings for each group finally grouped in step S40. The settings include a group identification value ID, a source ECU, a destination ECU, the communication route RT to be used, a transmission cycle, a security level, each required data to be transmitted, and whether or not grouping is required. The CPU 21 generates the communication specification list for each group, reflecting the content of the required data standard DSX for each required data included in the group. The CPU 21 represents the settings in the communication specification list, such as the source ECU, the destination ECU, the communication route RT to be used, and each required data to be transmitted, using the identification values ​​already described. The CPU 21 also represents whether or not grouping is required using a dedicated identification value. If this identification value indicates a required setting, communication is specified to be performed using a data set in which each required data to be transmitted is grouped. It should be noted that for the necessary data that could not be grouped in step S40, CPU 21 sets whether or not grouping is necessary, and specifies only one necessary data to be transmitted. After generating the communication specification list, CPU 21 displays a message on display 12 indicating that the communication specification list has been generated. CPU 21 may also display the contents of the communication specification list on display 12. When displaying the contents of the communication specification list on display 12, CPU 21 converts each identification value shown in the communication specification list into an actual ECU name or the like and displays it on display 12. After performing the necessary display on display 12, CPU 21 ends the processing of step S50. At the same time, CPU 21 ends the specification generation processing.

[0033] As described above, CPU 21 generates the communication specification list through the processes of steps S10 to S50. During the processes of steps S10 to S50, CPU 21 generates the communication specification list based on architecture model information AM and variation information V.

[0034] <Operation of the embodiment> In step S30, CPU 21 generates a required data standard DSX for each required data. Each required data standard DSX defines a communication route RT for transmitting the target required data. In step S40, CPU 21 performs grouping so that each communication route RT is realized while also satisfying all other items in each required data standard DSX. That is, in generating the communication specification list, CPU 21 defines each group along with the communication route RT for each required data so that all items in the data communication standard DS defined for each required data are satisfied.

[0035] <Effects of the embodiment> (1) In the specification generation process, the CPU 21 acquires the architecture model information AM and the variation information V, and then generates a communication specification list that defines the relationship between the necessary communication paths and necessary data specified in the variation information V. The use of such a specification generation process offers the following advantages to the designer: In designing the communication specifications for a vehicle to be designed, the designer only needs to prepare the variation information V that he or she wishes to adopt for the vehicle. Therefore, the designer can obtain a communication specification list for a new vehicle model without excessive effort.

[0036] (2) It is preferable from the viewpoint of improving communication efficiency that the destination ECU can transmit the same multiple required data in one batch. In the communication specification list, the CPU 21 of this embodiment determines that the destination ECU will communicate using a data set in which the same multiple required data are grouped. Generating such a communication specification list by the CPU 21 has the following advantage for the designer: Namely, the designer does not need to take the time to search for combinations of required data that should be grouped in relation to the destination.

[0037] (3) Being able to transmit multiple pieces of necessary data with the same transmission cycle together is preferable from the perspective of improving communication efficiency while ensuring appropriate transmission timing for each piece of necessary data. In the communication specification list, the CPU 21 of this embodiment determines that communication is to be performed using a data set in which multiple pieces of necessary data with the same transmission cycle are grouped. Generating such a communication specification list by the CPU 21 has the following advantage for designers: Namely, the designer does not need to take the time to search for combinations of necessary data that should be grouped in relation to their transmission cycles.

[0038] (4) Being able to transmit multiple pieces of required data with the same security level together is preferable from the perspective of improving communication efficiency while ensuring the security level of each piece of required data. In this embodiment, the CPU 21 determines in the communication specification list that communication is to be performed using a data set in which multiple pieces of required data with the same security level are grouped. Generating such a communication specification list by the CPU 21 has the following advantage for the designer: Namely, the designer does not need to take the time to search for combinations of required data that should be grouped in relation to security levels.

[0039] (5) The total amount of necessary data that can be transmitted and received at one time is predetermined. Therefore, even if multiple pieces of necessary data are grouped, it is preferable to set each group so that the total amount fits within the allowable total amount for one transmission and reception. In the communication specification list, the CPU 21 of this embodiment determines that communication is to be performed using data sets grouped so that the total amount of multiple pieces of necessary data included in one group is equal to or less than the set amount. Generating such a communication specification list by the CPU 21 has the following advantage for the designer. That is, the designer does not need to take the time to find a combination of necessary data that should be grouped taking into account the amount of necessary data.

[0040] <Example of change> The above embodiment can be modified as follows: The above embodiment and the following modifications can be combined with each other within the scope of technical compatibility.

[0041] Regarding grouping of required data, it is not necessary to group multiple required data so that the total volume of the required data is equal to or less than the set volume. In other words, multiple required data may be grouped solely based on whether the first, second, and third conditions are met. The communication specification list may then display the communication settings for each group.

[0042] It is not necessary to consider the third condition when grouping required data. In other words, multiple required data may be grouped based solely on whether they satisfy the first and second conditions. Then, the communication settings for each group may be listed in the communication specification list.

[0043] It is not necessary to consider the second condition when grouping required data. In other words, multiple required data may be grouped based solely on whether the first condition is met. Then, the communication settings for each group may be listed in the communication specification list.

[0044] It is not necessary to group the required data. The communication specifications generated by the specification generation process only need to specify the relationship between the required data and the communication path over which the required data should be transmitted. The communication specifications do not have to be a list.

[0045] When generating communication specifications, it is not necessary to specify a communication route RT for each required data or perform grouping so that all items of the data communication standard DS defined for each required data are satisfied. It is sufficient to specify a communication route RT for each required data so that the required items of each item of the data communication standard DS defined for each required data are satisfied. The same applies to grouping.

[0046] The content of the architecture model information AM is not limited to the example of the above embodiment. The architecture model information AM as a whole may include content corresponding to the total route information AR, total standard information AS, and application information AP of the above embodiment. The way each piece of information is represented and summarized may be changed as appropriate. For example, the total standard information AS and application information AP may be grouped together rather than being separate. The architecture model information AM may include information that aggregates the communication routes between ECUs in multiple types of vehicles, and information that indicates, for each communication route, one or more data communication standards that can be used to exchange data over each communication route.

[0047] It is not necessary to treat one communication path RT as a path connecting the ECU that is the source of data and the ECU that is the destination of data. For example, if there is another relay ECU between the ECU that is the source of data and the ECU that is the destination of data, the path from the ECU that is the source of data to the relay ECU may be treated as one communication path RT.

[0048] The content of the data communication standard is not limited to the example of the above embodiment. The items specified in the data communication standard may be increased or decreased from those in the above embodiment. The data communication standard may be any standard that defines the communication standards required for transmitting and receiving data over a specific communication path.

[0049] There may be three or more security levels. When there are three or more security levels, in addition to whether or not to add security information to the data, it is also possible to specify the level of security when adding the security information.

[0050] The content of the variation information V is not limited to the example of the above embodiment. The variation information V may include information specifying the required communication path and information specifying the required data. For example, the transmission cycle, data capacity, and security level for each required data item may be omitted from the variation information V of the above embodiment.

[0051] The information indicating the necessary communication path is not limited to a path identification value indicating the necessary communication path. The information indicating the necessary communication path may be any information that can indicate the necessary communication path. Similarly, the information specifying the necessary data is not limited to a data identification value indicating the necessary data. [Explanation of symbols]

[0052] 20...information processing device 21...CPU 22...database

Claims

1. Acquiring architecture model information including information that aggregates communication paths between ECUs in a plurality of types of vehicles and information that indicates, for each of the communication paths, one or more data communication standards that can transmit and receive data over the communication paths; acquiring variation information including information specifying a necessary communication path required in a specific vehicle and information specifying necessary data that needs to be exchanged through the necessary communication path; generating a communication specification that specifies a relationship between the necessary data and the communication path through which the necessary data should be transmitted, based on the architecture model information and the variation information; When generating the communication specifications, the communication path is specified for each of the necessary data so as to satisfy the data communication standard defined for each of the necessary data. Information processing device.

2. When generating the communication specification, if there are a plurality of pieces of necessary data that satisfy a first condition that the destination ECU is the same as that specified in the data communication standard, the communication specification specifies that communication is to be performed using a data set that groups the plurality of pieces of necessary data that satisfy the first condition. The information processing device according to claim 1 .

3. When generating the communication specifications, if there are a plurality of pieces of necessary data that satisfy, in addition to the first condition, a second condition that the data transmission cycles defined in the data communication standard are the same, the communication specifications stipulate that communication is to be performed using a data set obtained by grouping the plurality of pieces of necessary data that satisfy both the first condition and the second condition. The information processing device according to claim 2 .

4. When generating the communication specification, if there is a plurality of pieces of necessary data that satisfy, in addition to the first and second conditions, a third condition that the security levels defined in the data communication standard are the same, the communication specification specifies that communication will be performed using a data set obtained by grouping the plurality of pieces of necessary data that satisfy the first, second, and third conditions. The information processing device according to claim 3 .

5. When generating the communication specifications, it is determined that communication is to be performed using a data set obtained by grouping the plurality of pieces of necessary data that satisfy the first condition, the second condition, and the third condition so that the total volume of the plurality of pieces of necessary data is equal to or less than a predetermined set volume. The information processing device according to claim 4 .

Images