Communication design device and communication design method

The communication design device optimizes in-vehicle network communication by allocating time slots based on delay times and packet lengths, addressing the challenge of varying application requirements for efficient data transmission.

JP2024170210APending Publication Date: 2024-12-06ASTEMO LTD
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
JP2023087240
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-26
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

Existing communication design methods for in-vehicle networks struggle to set appropriate time slot widths according to the varying communication requirements of different applications, leading to suboptimal communication designs.

Method used

A communication design device that allocates time slots based on allowable delay times and packet lengths for each application, using the TSN standard to ensure optimal communication timing and bandwidth guarantees for multiple devices.

Benefits of technology

Enables an optimal communication design that meets the diverse requirements of various applications within in-vehicle networks, ensuring reliable and efficient data transmission.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024170210000001_ABST
    Figure 2024170210000001_ABST
Patent Text Reader

Abstract

To provide a technique that can perform optimal communication design for a network in which communication is performed according to the requests of various applications with different communication requirements.SOLUTION: A communication design device 22 includes a communication requirement storage unit 50 that stores communication requirement information representing an allowable delay time indicating the length of a communication delay time allowed for each time guarantee application and a packet length of communication data determined for each time guarantee application, and a schedule setting unit 51 that allocates a communication time slot for each application. The schedule setting unit 51 sets a time slot period based on the allowable delay times related to the plurality of time guarantee applications, and sets a time slot length based on the packet lengths related to the plurality of time guarantee applications.SELECTED DRAWING: Figure 4
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to an apparatus and method for performing communication design for a network. [Background technology]

[0002] Conventionally, there are known communication networks in which communication by multiple types of applications is performed in parallel, and communication requirements such as delay tolerance time differ for each application, such as an in-vehicle network composed of multiple electronic control units (ECUs) mounted on a vehicle. In such communication networks, the communication requirements of all applications must be guaranteed without fail, so it is important to perform a communication design that sets appropriate communication timing for each application.

[0003] Time-sensitive networking (TSN), for example, is known as a technology that guarantees real-time communication data in a network. TSN is defined as a communication method that extends standard Ethernet (registered trademark), and realizes real-time communication in Ethernet communication. The TSN standard includes a time synchronization method within a network (IEEE 802.1AS), a method that guarantees a transmission band using a credit-based shaper (IEEE 802.1Qav), and a method that communicates for each time slot that is set in advance with respect to a synchronized time (IEEE 802.1Qbv).

[0004] In recent years, a method has been proposed for realizing an optimal communication design by treating communication requirements that differ for each application as an optimization problem and solving the problem. For example, Patent Document 1 describes a wireless communication method in which a single channel can be used by multiple wireless systems in a time-division manner by using a time slot commonly defined based on information on all devices included in the wireless communication system, and a counter value is set for traffic that each communication device is about to transmit, the counter value being expressed by an integer value with the time slot length as a unit, taking into consideration the transmission timing and the allowable delay amount, and the traffic to be transmitted in each time slot is specified based on the counter value. According to this wireless communication method, a combinatorial optimization problem of what timing is best to transmit each time slot can be solved by a simple method, so that the timing of transmitting traffic can be appropriately controlled even in a narrow space where many wireless communication devices exist. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] JP 2020-155857 A Summary of the Invention [Problem to be solved by the invention]

[0006] In the method described in Patent Document 1, it is necessary to define time slots in advance without taking into account the communication requirements of each application, making it difficult to set an appropriate time slot width according to the different communication requirements of each application. As a result, there is a problem in that it is not possible to realize an optimal communication design.

[0007] Therefore, an object of the present invention is to provide a technique capable of realizing an optimal communication design for a network in which communication is performed according to the requests of various applications with different communication requirements. [Means for solving the problem]

[0008] The communication design device according to the present invention is a device that performs communication design for a network to which a plurality of communication devices are connected and which communicate with each other in accordance with application requirements, and is equipped with a communication requirements memory unit that stores an allowable delay time indicating the length of the communication delay time allowable for each application and a packet length of communication data determined for each application, and a schedule setting unit that assigns a time slot for the communication to each application, and the schedule setting unit sets the period of the time slot based on the allowable delay time for each of the applications, and sets the length of the time slot based on the packet length for each of the applications. A communication design method according to the present invention is a method for designing communications for a network to which a plurality of communication devices are connected and which communicate with each other in accordance with application requests, the method including storing in a computer an allowable delay time indicating the length of the communication delay time allowable for each application and a packet length of communication data determined for each application, and allocating a time slot for the communication for each application by the computer, and in allocating the time slots, setting a period of the time slot based on the allowable delay time for each of the applications, and setting the length of the time slot based on the packet length for each of the applications. Effect of the Invention

[0009] According to the present invention, it is possible to provide a technique capable of realizing an optimal communication design for a network in which communication is performed according to the requests of various applications having different communication requirements. [Brief description of the drawings]

[0010] [Figure 1] 1 is a diagram illustrating an example of a network for which a communication design device of the present invention performs communication design; [Diagram 2]FIG. 2 is a diagram illustrating an example of the configuration of each communication device in an in-vehicle network. [Diagram 3] 1 is a diagram illustrating an example of the configuration of a system including a communication design device according to a first embodiment of the present invention. [Figure 4] 1 is a functional block diagram showing a configuration of a communication design apparatus according to a first embodiment of the present invention. [Diagram 5] FIG. 2 is a diagram illustrating an example of a communication schedule of an in-vehicle network. [Figure 6] FIG. 13 is a diagram illustrating an example of a time-guaranteed communication requirement table. [Figure 7] FIG. 13 is a diagram illustrating an example of a bandwidth guaranteed communication requirement table. [Figure 8] 4 is a flowchart illustrating a method for setting a communication schedule in the communication design device according to the first embodiment of the present invention. [Figure 9] 13 is a flowchart showing the flow of a schedule calculation process for time guaranteed communication. [Figure 10] 11 is a diagram showing an example of time slots assigned to a time assurance application by a schedule calculation process for time assurance communication; FIG. [Figure 11] 13 is a diagram showing an example of a schedule calculation process result of time guaranteed communication. [Figure 12] 13 is a flowchart showing the flow of a communication path calculation process for bandwidth guaranteed communication. [Figure 13] FIG. 11 is a diagram illustrating an example of link usage information. [Figure 14] FIG. 11 is a diagram illustrating an example of network design data. [Figure 15] FIG. 11 is a diagram illustrating an example of the configuration of a system including a communication design device according to a second embodiment of the present invention. [Figure 16] FIG. 11 is a functional block diagram showing a configuration of a communication design apparatus according to a second embodiment of the present invention. [Figure 17] 10 is a flowchart illustrating a method for resetting a communication schedule in a communication design device according to a second embodiment of the present invention. [Figure 18] 13 is a flowchart showing the flow of a schedule recalculation process for time guaranteed communication. [Figure 19] 13 is a flowchart showing the flow of a communication path recalculation process for bandwidth guaranteed communication. [Figure 20] FIG. 11 is a functional block diagram showing a configuration of a communication design apparatus according to a third embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] Hereinafter, a communication design apparatus of the present invention will be described with reference to the drawings.

[0012] (Network Configuration) Fig. 1 is a diagram showing an example of the configuration of an in-vehicle network used in an automobile as an example of a network for which the communication design device of the present invention performs communication design. In Fig. 1, (a) shows an example of the configuration of an in-vehicle network based on a domain architecture, and (b) shows an example of the configuration of an in-vehicle network based on a zone architecture.

[0013] 1(a) and 1(b) are mounted on a vehicle 1 and perform communication by various applications used during operation of the vehicle 1. In the example of the domain-specific architecture configuration shown in FIG. 1(a), the vehicle network 20 is configured by connecting a gateway 2, a plurality of domain ECUs 3, sensors 4, and actuators 5 combined by domain, and a TCU (Telematics Control Unit) 7 to each other.

[0014] The domain ECUs 3 each execute a predetermined application, transmit and receive various signals to and from the sensors 4 and actuators 5 connected via the signal lines 6, and communicate with each other via the gateway 2 in accordance with requests from the applications executed by each of them. The domain ECUs 3 include, for example, a domain ECU 3a that executes an application related to an ADAS (Advanced Driver Assistance Systems) of the vehicle 1, a domain ECU 3b that executes an application related to driving control of the vehicle 1, a domain ECU 3c that executes an application related to electrical equipment of the vehicle 1, and a domain ECU 3d that executes an application related to an infotainment device (navigation device, audio device, etc.) mounted on the vehicle 1. Note that the domain ECUs 3 may further include a domain ECU 3 that executes other applications, or may be replaced with the domain ECUs 3a to 3d.

[0015] The domain ECUs 3a to 3d are connected to the sensors 4a to 4d and the actuators 5a to 5d via the signal lines 6a to 6d, respectively. The domain ECUs 3a to 3d control the actuators 5a to 5d based on the sensor signals received from the sensors 4a to 4d, respectively, and can transmit and receive communication data related to the sensor signals of the sensors 4a to 4d and communication data related to the control of the actuators 5a to 5d to each other via the gateway 2, and can use the data for controlling the actuators 5a to 5d, etc.

[0016] The TCU 7 is a device that performs wireless communication with a predetermined communication partner (for example, a vehicle control device that controls a plurality of vehicles including the vehicle 1, or other vehicles existing around the vehicle 1). The TCU 7 and the domain ECUs 3a to 3d are connected to each other via a gateway 2. By using the TCU 7, the in-vehicle network 20 in FIG. 1(a) can transmit communication data transmitted and received between the domain ECUs 3a to 3d to the communication partner, and provide communication data received from the communication partner to the domain ECUs 3a to 3d.

[0017] The gateway 2 is a device that performs communication control required when transmitting and receiving communication data between the domain ECUs 3a to 3d and the TCU 7. The domain ECUs 3a to 3d and the TCU 7 can communicate with each other via the gateway 2.

[0018] In the configuration example of the zone architecture shown in FIG. 1(b), the in-vehicle network 20 is configured by interconnecting a central ECU 8, a plurality of zone ECUs 9 combined according to zone, sensors 4, actuators 5, and a TCU 7.

[0019] The zone ECUs 9 each execute a predetermined application, transmit and receive various signals to and from the sensors 4 and actuators 5 arranged for each zone in the vehicle 1, and communicate with each other via the central ECU 8 and the shared bus 10 in accordance with requests from the applications they execute. The zone ECUs 9 include, for example, zone ECUs 9a and 9b arranged on the right and left sides of the front of the vehicle 1 and execute predetermined applications, and zone ECUs 9c and 9d arranged on the right and left sides of the rear of the vehicle 1 and execute predetermined applications. Note that the zone ECUs 9 may further include zone ECUs 9 arranged in other locations, or may be replaced by the zone ECUs 9a to 9d.

[0020] The zone ECUs 9a to 9d are connected to the sensors 4a to 4d and the actuators 5a to 5d via signal lines and communication buses, respectively. The zone ECUs 9a to 9d control the actuators 5a to 5d based on the sensor signals received from the sensors 4a to 4d, respectively, in the same manner as the domain ECUs 3a to 3d in Fig. 1(a), and can transmit and receive communication data related to the sensor signals of the sensors 4a to 4d and communication data related to the control of the actuators 5a to 5d to each other via the central ECU 8 and the shared bus 10, and use the data for controlling the actuators 5a to 5d, etc.

[0021] The TCU 7 performs the same operation as in Fig. 1(a). By using this TCU 7, the in-vehicle network 20 in Fig. 1(b) can transmit communication data transmitted and received between the central ECU 8 and the zone ECUs 9a to 9d to the communication counterpart, and provide communication data received from the communication counterpart to the central ECU 8 and the zone ECUs 9a to 9d.

[0022] FIG. 2 is a diagram showing an example of the configuration of each communication device (the domain ECU 3, the zone ECU 9, the gateway 2, and the central ECU 8) in the in-vehicle network 20 shown in FIG.

[0023] Fig. 2(a) shows an example of the configuration of the domain ECU 3. As shown in Fig. 2(a), the domain ECU 3 is configured to include a CPU 11 and a memory 12. The CPU 11 executes a predetermined process using various data and programs stored in the memory 12, thereby executing an application according to the function of the domain ECU 3. In accordance with the request of this application, communication is performed between the CPU 11 and the gateway 2, and various signals are transmitted and received between the CPU 11 and the sensor 4 and the actuator 5.

[0024] 2(b) shows an example of the configuration of the zone ECU 9. As shown in FIG. 2(b), the zone ECU 9 is configured to include a CPU 11, a memory 12, and a network switch 13. The network switch 13 performs communication control processing for communication data transmitted and received between other zone ECUs 9 and the central ECU 8. The CPU 11 executes a predetermined process using various data and programs stored in the memory 12, thereby executing an application according to the function of the zone ECU 9. In accordance with the request of this application, network communication is performed between the CPU 11 and other zone ECUs 9 and the central ECU 8 via the network switch 13, and various signals are transmitted and received between the CPU 11 and the sensors 4 and the actuators 5.

[0025] Fig. 2(c) shows a configuration example of the gateway 2. As shown in Fig. 2(c), the gateway 2 is configured to include a CPU 11, a memory 12, and a network switch 13. The CPU 11 controls the operation of the network switch 13 by executing predetermined processes using various data and programs stored in the memory 12. The network switch 13 operates under the control of the CPU 11, and performs communication control processing for communication data transmitted and received between each domain ECU 3.

[0026] Fig. 2(d) shows a configuration example of the central ECU 8. As shown in Fig. 2(d), the central ECU 8 is configured to include a CPU 11, a memory 12, and a network switch 13. The CPU 11 executes predetermined processes using various data and programs stored in the memory 12, thereby controlling the operation of the network switch 13 and executing predetermined applications. The network switch 13 operates under the control of the CPU 11, and performs communication control processes for communication data transmitted and received between the network switch 13 and the zone ECUs 9.

[0027] [First embodiment] Next, a communication design device according to a first embodiment of the present invention will be described below with reference to Fig. 3 to Fig. 14. In this embodiment, an example of a communication design device will be described in which communication design of the in-vehicle network 20 described in Fig. 1 is performed in advance and the design result is reflected in the in-vehicle network 20.

[0028] (System Configuration) Fig. 3 is a diagram showing an example of the configuration of a system including a communication design device according to the first embodiment of the present invention. The system shown in Fig. 3 is a system for performing communication settings for an in-vehicle network 20 of a vehicle 1, and includes a network information input device 21 and a communication design device 22 provided at a design base 30, and a communication setting device 23 provided at a manufacturing base 31.

[0029] The network information input device 21 inputs network information required for communication design of the in-vehicle network 20 to the communication design device 22. The network information input device 21 can accept an operation from a designer working at the design base 30, for example, and set the network information specified by this operation as a prerequisite for the communication design of the in-vehicle network 20 and input it to the communication design device 22.

[0030] The communication design device 22 automatically performs communication design for the in-vehicle network 20 based on the network information input from the network information input device 21. At this time, the communication design device 22 accepts operations from the designer and determines communication setting conditions for each application so as to satisfy the communication requirements of each application specified by this operation. The results of the communication design by the communication design device 22 are transmitted from the communication design device 22 to the communication setting device 23 as network design data 40 for the in-vehicle network 20. The communication design device 22 will be described in detail later.

[0031] The communication setting device 23 determines the setting contents for each communication device (such as the domain ECU 3, the zone ECU 9, the gateway 2, and the central ECU 8) in the in-vehicle network 20 based on the network design data 40 transmitted from the communication design device 22. The setting contents for each communication device by the communication setting device 23 are transmitted from the communication setting device 23 to the in-vehicle network 20 as network setting data 41 for the in-vehicle network 20.

[0032] In the in-vehicle network 20, the settings of each communication device are made based on the network setting data 41 transmitted from the communication setting device 23. As a result, communication settings for the in-vehicle network 20 can be made so that each communication device can communicate with each other in accordance with requests from applications executed in each domain ECU 3 and each zone ECU 9.

[0033] (Configuration of communication design device) Fig. 4 is a functional block diagram showing the configuration of a communication design device according to the first embodiment of the present invention. As shown in Fig. 4, the communication design device 22 is configured to include, for example, functional blocks of a communication requirement storage unit 50, a schedule setting unit 51, and a setting output unit 52. These functional blocks in the communication design device 22 are realized, for example, by a computer executing a predetermined program.

[0034] The communication requirement storage unit 50 stores communication requirement information, which is information related to communication requirements of each application in the in-vehicle network 20. The communication requirement storage unit 50 can be realized, for example, by using various storage devices (HDD, SSD, flash memory, etc.) provided in a computer. The communication requirement information stored in the communication requirement storage unit 50 will be described in detail later.

[0035] The schedule setting unit 51 sets a communication schedule for the in-vehicle network 20 for each application based on the communication requirement information stored in the communication requirement storage unit 50. The schedule setting unit 51 can set the communication schedule for the in-vehicle network 20 by allocating time slots for communication by each application so as to satisfy the communication requirements that differ for each application. The method of setting the communication schedule by the schedule setting unit 51 will be described in detail later.

[0036] The setting output unit 52 determines setting information related to communication control of the in-vehicle network 20 based on the communication schedule set by the schedule setting unit 51, and outputs this setting information as network design data 40. The network design data 40 output from the setting output unit 52 is transmitted from the communication design device 22 to the communication setting device 23 as described above, and is used in the processing performed by the communication setting device 23.

[0037] (Communication Schedule) 5 is a diagram showing an example of a communication schedule of the in-vehicle network 20 set by the schedule setting unit 51. The schedule setting unit 51, for example, sets time slots 100, 101, and 102 at a predetermined cycle, and assigns these time slots to communication for each application, thereby setting the communication schedule of the in-vehicle network 20. The time slots can be realized by the IEEE 802.1Qbv of the TSN standard.

[0038] The time slot 100 is assigned to an application that performs communication at a short period and requires time guarantee to suppress delay time within a predetermined delay tolerance. In the in-vehicle network 20, the time slot 100 is reserved at regular intervals for communication performed according to the request of the application, and communication data is transmitted and received between communication devices in the in-vehicle network 20 within the period of the time slot 100. This allows communication that satisfies the communication requirements of the application to be performed.

[0039] The time slot 101 is assigned to an application that performs communication requiring time guarantee at a long period. In the in-vehicle network 20, the time slot 101 is reserved at regular intervals with a period longer than the above-mentioned time slot 100 for communication performed according to the request of the application, and communication data is transmitted and received between communication devices in the in-vehicle network 20 within the period of this time slot 101. This allows communication that satisfies the communication requirements of the application to be performed.

[0040] The time slot 102 is assigned to each application that performs communication that does not require time guarantee. In the in-vehicle network 20, a period other than the above-mentioned time slots 100 and 101 is reserved as the time slot 102 for communication performed according to the request of the application, and communication data is transmitted and received between communication devices in the in-vehicle network 20 during the period of the time slot 102. In the time slot 102, three classes that guarantee communication bands and other best-effort classes are set corresponding to multiple communication ports of the communication device, and one of the classes is assigned according to the communication requirements of each application. The guarantee of communication bands can be realized by IEEE 802.1Qav of the TSN standard. As a result, communication that satisfies the communication requirements of the application is performed.

[0041] 5 is an example, and other communication schedules may be used. For example, one or three or more time slots for time guarantee may be set, and the number of bandwidth guaranteed classes set in the time slots 102 may be other than three. All the time slots 102 may be assigned to the bandwidth guaranteed class, or conversely, all the time slots 102 may be assigned to the best effort class. In addition to the above, the communication schedule of the in-vehicle network 20 may be set with any other time slot configuration.

[0042] (Communication requirements information) Fig. 6 is a diagram showing an example of a time-guaranteed communication requirement table showing communication requirement information for applications (hereinafter referred to as "time-guaranteed applications") performing communication requiring time assurance, among the communication requirement information stored in the communication requirement storage unit 50. The time-guaranteed communication requirement table 200 shown in Fig. 6 has records set for each type of communication data by each time-guaranteed application, and each record has data of a source 201, a destination 202, a communication cycle 203, a delay requirement 204, and a packet length 205.

[0043] Source 201 and destination 202 store information indicating the source and destination communication devices of each communication data, respectively. Communication cycle 203 stores information indicating the communication cycle of each communication data. Delay requirement 204 stores information indicating the allowable delay time of each communication data. Packet length 205 stores information indicating the packet length (amount of communication data) of each communication data. With this information, communication requirements to be satisfied for each communication data are represented for each time assurance application.

[0044] Fig. 7 is a diagram showing an example of a bandwidth-guaranteed communication requirement table showing communication requirement information for applications (hereinafter referred to as "bandwidth-guaranteed applications") that perform communication that does not require time guarantee and requires securing a predetermined communication bandwidth, among the communication requirement information stored in communication requirement storage unit 50. Bandwidth-guaranteed communication requirement table 210 shown in Fig. 7 has records set for each type of communication data by each bandwidth-guaranteed application, and each record has data of source 211, destination 212, and communication bandwidth 213.

[0045] Information representing the communication device of the source and destination of each communication data is stored in source 211 and destination 212, respectively. Information representing the communication bandwidth of each communication data is stored in communication bandwidth 213. This information represents the communication requirements to be satisfied for each communication data for each bandwidth guaranteed application that has a relatively large amount of communication data and therefore needs to periodically secure a certain amount of communication bandwidth.

[0046] 6 and the contents of the bandwidth-guaranteed communication requirement table 210 shown in Fig. 7 are stored in the communication requirement storage unit 50, for example, by a designer inputting them in advance to the communication design device 22 using the network information input device 21. Alternatively, the contents automatically set by the network information input device 21 based on information of past design history or information collected from outside and input to the communication design device 22 may be stored in the communication requirement storage unit 50 as the time-guaranteed communication requirement table 200 or the bandwidth-guaranteed communication requirement table 210.

[0047] (How to set up a communication schedule) Fig. 8 is a flowchart for explaining a method for setting a communication schedule in the communication design device according to the first embodiment of the present invention. In the communication design device 22 of this embodiment, the schedule setting unit 51 sets a communication schedule for the in-vehicle network 20 by, for example, executing the process shown in the flowchart of Fig. 8 in response to an instruction from a designer.

[0048] In step S100, a schedule calculation process for time-guaranteed communication is performed. Here, the process shown in the flowchart of Fig. 9 is executed to determine the time slots to be assigned to each time-guaranteed application whose communication requirements are defined by the communication requirement information exemplified in Fig. 6. Details of the process shown in the flowchart of Fig. 9 will be described later.

[0049] In step S101, time slots for bandwidth guaranteed communication and best effort communication are determined. Here, the period excluding the time slots for time guaranteed communication determined in the process of step S100 is determined as the time slots for bandwidth guaranteed communication and best effort communication.

[0050] In step S102, a communication path calculation process for bandwidth guaranteed communication is performed. Here, the process shown in the flowchart of Fig. 12 is executed to determine the communication path and class of each bandwidth guaranteed application whose communication requirements are defined by the communication requirement information exemplified in Fig. 7. Details of the process shown in the flowchart of Fig. 12 will be described later.

[0051] In step S103, a class for best-effort communication is determined. Here, in the time slot determined in the process of step S101, the remaining classes except for the classes used in bandwidth guaranteed communication are determined as classes for best-effort communication.

[0052] In step S104, it is determined whether or not the communication design result of the in-vehicle network 20 by the communication design device 22 satisfies the communication requirements of each application represented by the communication requirement information stored in the communication requirement storage unit 50. Here, it is determined whether or not the delay time and communication bandwidth when each application communicates according to the communication schedule obtained in the processes of steps S100 to S103 satisfies the communication requirements of all the applications. As a result, if the communication requirements of all the applications are satisfied, the process proceeds to step S105, and if the communication requirements of at least one of the applications are not satisfied, the process proceeds to step S106.

[0053] In step S105, information indicating that the communication design of the in-vehicle network 20 by the communication design device 22 has been successful is output to the network information input device 21. This information is received by the network information input device 21, and a predetermined message is presented to the network information input device 21 in response to this information, thereby making it possible to inform the designer that the communication design of the in-vehicle network 20 has been successful. This makes it possible to prompt the designer to output the obtained design result as network design data 40 from the communication design device 22 to the communication setting device 23.

[0054] In step S106, information indicating that the communication design of the in-vehicle network 20 by the communication design device 22 has failed is output to the network information input device 21. This information is received by the network information input device 21, and by presenting a predetermined message to the network information input device 21 in response to this, it is possible to inform the designer that the communication design of the in-vehicle network 20 has failed. This makes it possible to prompt the designer to reconsider the settings of the communication requirements and the configuration of the in-vehicle network 20.

[0055] After executing the process of step S105 or S106, the communication design device 22 ends the process shown in the flowchart of FIG.

[0056] (Schedule calculation process for time-guaranteed communication) FIG. 9 is a flowchart showing the flow of the schedule calculation process for time guaranteed communication executed in step S100 of FIG.

[0057] In steps S110 to S118, a loop process is performed for each delay requirement of the time guaranteed communication. Here, for example, in the communication requirement information represented by the time guaranteed communication requirement table 200 shown in FIG. 6, communication data having the same value of the delay requirement 204 are grouped into one group, thereby grouping the time guaranteed applications for each delay requirement. Note that other information related to the time guaranteed communication, such as the communication cycle 203, may be used for grouping. Then, the process of steps S110 to S118 is performed for each group, thereby performing a schedule calculation process for the time guaranteed communication. In this way, time slots with the same cycle are assigned to multiple time guaranteed applications having the same delay allowable time. In the following, the group of time guaranteed applications currently subject to the loop process is referred to as the "first group of applications to be processed", and the contents of the loop process of steps S110 to S118 will be described.

[0058] After loop processing is started in step S110, the next step S111 is to determine a class to be used for the first group of applications to be processed. Here, one of the currently available classes is selected and determined as the class to be used for the first group of applications to be processed.

[0059] In step S112, the total packet length of all communication data flows of the first target application group having the same delay requirement is calculated. Here, the total packet length of communication data by the first target application group is calculated by adding up the values ​​of packet length 205 of records corresponding to each time-guaranteed application of the first target application group in the communication requirement information represented by the time-guaranteed communication requirement table 200 in Fig. 6.

[0060] In step S113, the maximum number of hops in the in-vehicle network 20 for communication by the first processing target application group is calculated from the topology information of the in-vehicle network 20. Here, in the communication requirement information represented by the time-guaranteed communication requirement table 200 in FIG. 6, the communication devices in the in-vehicle network 20 corresponding to each time-guaranteed application in the first processing target application group are identified from the contents of the source 201 and destination 202 of the record corresponding to each time-guaranteed application in the first processing target application group. Then, the number of other communication devices that may be passed through when communicating between these communication devices is identified from the topology information of the in-vehicle network 20, and the maximum number among them can be obtained as the maximum number of hops. Note that the topology information of the in-vehicle network 20 is information that indicates the connection relationship between each communication device in the in-vehicle network 20, and is included in the network information input from the network information input device 21, for example.

[0061] In step S114, the maximum delay time in communication by the first processing target application group is calculated based on the maximum number of hops calculated in step S113. Here, the delay time at the maximum number of hops can be calculated as the maximum delay time by multiplying a preset delay time per hop by the maximum number of hops calculated in step S113. Note that the delay time calculated here includes the switch delay time (switch processing time, store-and-forward time, etc.) by the network switch 13, the transmission delay time of communication data, etc.

[0062] In step S115, the time slot length of the communication by the first processing target application group is calculated based on the total packet length calculated in step S112 and the maximum delay time calculated in step S114. Here, the total packet length is added to the maximum delay time to calculate the time slot length of the communication by the first processing target application group. In this way, the time slot length is set based on the sum of the total packet length related to multiple time guarantee applications to which time slots of the same period are assigned, the total switch delay time in the in-vehicle network 20, which is the time required for switch processing by the network switch 13 in the communication device, and the total transmission delay time in the in-vehicle network 20, which is the time required for communication transmission.

[0063] In step S116, a time slot for communication by the first application group to be processed is set for each communication cycle based on the time slot length calculated in step S115. Here, the end time of the time slot determined in the previous loop process is set as the start time (offset) of the time slot by the current loop process, and the time obtained by adding the time slot length determined in step S115 to that time is set as the time slot for communication by the first application group to be processed. In this way, the schedule setting unit 51 of this embodiment can set the time slot cycle for multiple time guarantee applications included in the first application group to be processed based on the delay allowance associated with these time guarantee applications, and set the time slot length based on the packet length associated with these time guarantee applications. As a result, it is possible to assign a time slot for communication performed by each time guarantee application of the first application group to be processed.

[0064] In step S117, routing for the first group of applications to be processed is performed. Here, for example, the shortest route for communication by the first group of applications to be processed is identified based on the topology information of the in-vehicle network 20, and routing is performed along this shortest route. Note that, at this time, routing other than the shortest route may be performed so that the communication load in the entire in-vehicle network 20 is distributed.

[0065] In step S118, the loop process for the current first group of applications to be processed is terminated. Then, it is determined whether or not this loop process has been performed for all of the above-mentioned groups in which applications requiring time guarantee are grouped by delay requirement. As a result, if there is a group for which the loop process has not been performed, one of the groups is set as the next first group of applications to be processed, and the next loop process is started. On the other hand, if the loop process has been performed for all groups, the schedule calculation process for time guaranteed communication shown in the flowchart of FIG. 9 is terminated.

[0066] In the schedule calculation process for time guaranteed communication, the above-described process is executed for each of the multiple time guaranteed applications by the schedule setting unit 51. As a result, the cycle of the time slots for communication assigned to each time guaranteed application is set based on the allowable delay times for the multiple time guaranteed applications, and the length of the time slot is set based on the packet length of the communication data for the multiple time guaranteed applications.

[0067] Fig. 10 is a diagram showing an example of time slots assigned to time assurance applications by the schedule calculation process of time assurance communication described above. Fig. 10 shows an example in which communication data is transmitted from one ECU ("ECU1" in Fig. 10) to another ECU ("ECU2" in Fig. 10) via network switches 13 ("Switch1" and "Switch3" in Fig. 10) provided in ECU1 and ECU2, respectively, and a network switch 13 ("Switch2" in Fig. 10) of another communication device located between them. The network switches 13 of each ECU are time-synchronized by the TSN function.

[0068] For example, suppose that communication data 110, 111, and 112 by different time guarantee applications have the same delay requirement, and time slots 100a and 100b are assigned to the communication data for each predetermined communication period by the schedule calculation process of the time guarantee communication. In these time slots 100a and 100b, packets of the communication data 110 to 112 are transmitted from ECU1 to ECU2. However, if communication data is output from the time guarantee application being executed in ECU1 at a timing where the communication data cannot reach ECU2 within the time slot 100a, such as packet 110c in FIG. 10, the transmission of the communication data is temporarily suspended by the network switch 13 (Switch1) of ECU1. After that, when the time 120 from the time slot 100a to the next time slot 110b has elapsed, the communication data 110 to 112 are continuously transmitted from ECU1 to ECU2.

[0069] In time slot 110b, communication data 110-112 output from the time guarantee application being executed in ECU1 are assembled into a series of packets by Switch1 in ECU1, and then handed over to the time guarantee application being executed in ECU2 via Switch2 and Switch3. At this time, a transmission delay time 121a and a switch delay time 122a in Switch2 are generated between the transmission timing of ECU1 and the transmission timing of Switch2. Similarly, a transmission delay time 121b and a switch delay time 122b in Switch3 are added between the transmission timing of Switch2 and the reception timing of Switch3. Furthermore, a transmission delay time 121c in ECU2 and a packet length 123 obtained by summing up the communication data 110-112 are added between the reception timing of Switch3 and the handover timing to the time guarantee application being executed in ECU2.

[0070] The length (time slot width) of the time slots 110a and 110b is τ i Then, τ i is expressed by the following formula (1). In formula (1), τ Packets represents the total value of the packet length for time-guaranteed communication flows with the same delay requirement, which corresponds to the packet length 123 in FIG. Proc and τ SF τ represents the sum of the internal processing delay and the store-and-forward delay in each network switch 13 in the in-vehicle network 10, and corresponds to the switch delay times 122a and 122b in FIG. Trans represents the total value of the transmission delay in each link in the in-vehicle network 10, which corresponds to the transmission delay times 121a to 121c in FIG. τ i = τ Packets +τ Proc +τ Trans +τ SF (1)

[0071] In addition, the maximum delay time of the time-guaranteed communication flow in the time slots 110a and 110b (the time from when the ECU1 starts transmitting the head of the packet of the communication data 110 to 112 to when the ECU2 completes receiving the tail of the packet of the communication data 110 to 112) is denoted by d E2E Then, d E2E is expressed by the following formula (2). In formula (2), d Timeslot represents the time from the end of the time slot of the previous period to the start of the time slot of the next period, which corresponds to time 120 in FIG. 10. Also, C i represents the period of time-guaranteed communication. d E2E =d Timeslot +τ SF +τ Trans +τ Packets +τ Proc =C i -τ i +τ SF +τ Trans +τ Packets +τ Proc =C i (2)

[0072] As described above, various delay times related to the transmission of communication data are added between the start of output in the application and the end of transmission. In the schedule calculation process for time-guaranteed communication described in the flowchart of Fig. 9, the time slots 100a and 100b can be set taking these delay times into consideration.

[0073] Fig. 11 is a diagram showing an example of the schedule calculation process result of time guaranteed communication. Schedule table 220 shown in Fig. 11 has a record set for each time slot determined by the schedule calculation process of time guaranteed communication, and each record has data of period 221, reference time 222, and slot length 223. These data represent the setting contents of each time slot in which time guaranteed communication is performed.

[0074] (Communication path calculation process for bandwidth guaranteed communication) FIG. 12 is a flowchart showing the flow of the communication path calculation process for bandwidth guaranteed communication executed in step S102 of FIG.

[0075] In step S120, the communication bandwidth of each link available for bandwidth guaranteed communication is calculated by subtracting the bandwidths used for all time slots calculated by the schedule calculation process for time guaranteed communication in step S100 from the available bandwidths of all links of the in-vehicle network 20. The available bandwidths of all links of the in-vehicle network 20 are included in the network information input from the network information input device 21, for example.

[0076] In steps S121 to S129, a loop process is executed for each communication flow that requires bandwidth guarantee. Here, for example, from each record of bandwidth guaranteed communication requirement table 210 shown in FIG. 7, one or more bandwidth guaranteed applications having a common source and destination are identified, and communication data by these bandwidth guaranteed applications are grouped as a series of communication flows. The loop process of steps S121 to S129 is executed for each communication flow set by grouping one or more bandwidth guaranteed applications in this way. In the following, the group of applications corresponding to the communication flow that is the target of the current loop process among the bandwidth guaranteed applications whose communication requirement information is indicated by bandwidth guaranteed communication requirement table 210 is referred to as a "second group of applications to be processed", and the contents of the loop process of steps S121 to S129 will be described.

[0077] In the loop process of steps S121 to S129, the loop process of steps S122 to S125 is executed for each communication path available for communication by the second processing target application group. Here, in the communication requirement information represented by the bandwidth guaranteed communication requirement table 210 shown in FIG. 7, for example, the communication devices of the in-vehicle network 20 corresponding to the source 211 and destination 212 of the records corresponding to the bandwidth guaranteed applications belonging to the second processing target application group are identified. Then, a route list is created by listing all the communication paths of the in-vehicle network 20 connecting these communication devices, and the loop process of steps S122 to S125 is executed for each communication path shown in the route list. In the following, the communication path currently being the target of the loop process is referred to as the "processing target path", and the loop process of steps S122 to S125 will be described.

[0078] After starting the loop process in step S122, the next step S123 obtains the available bandwidth and the number of available classes for each link on the target route. Here, the available bandwidth and the number of available classes for each link on the target route can be obtained, for example, by using the link usage information described below.

[0079] Fig. 13 is a diagram showing an example of link usage information indicating the bandwidth usage and the number of usage classes of each link used in the process of step S123 in Fig. 12. The link usage table 230 shown in Fig. 13 has a record set for each link in the in-vehicle network 20, and each record has data of a link 231, a bandwidth usage 232, and a number of usage classes 233. These data indicate the bandwidth usage and the number of classes of each link assigned to the communication route set in the previous process. The link usage table 230 is stored in the communication design device 22, and its contents are updated in step S127 described later.

[0080] Returning to the explanation of Fig. 12, in step S123, the available bandwidth and the number of available classes for each link on the target route can be found from the link usage information as follows. That is, for each link on the target route, the available bandwidth for each link can be calculated by subtracting the value of the bandwidth used 232 in the link usage table 230 illustrated in Fig. 13 from the value of the available bandwidth calculated in step S120. Also, the number of available classes for each link on the target route can be calculated by subtracting the value of the number of used classes 233 in the link usage table 230 from the number of classes set in advance.

[0081] In step S124, it is determined whether the available bandwidth and the number of available classes of each link of the processing target route calculated in step S123 satisfy the use condition of the communication route. Here, for example, in the communication requirement information represented by the bandwidth guaranteed communication requirement table 210 shown in FIG. 7, the total communication bandwidth (flow bandwidth) required for the communication flow of the second processing target application group is calculated from the value of the communication bandwidth 213 of the record corresponding to each bandwidth guaranteed application belonging to the second processing target application group. Then, if the available bandwidth is equal to or greater than the flow bandwidth and the number of available classes is equal to or greater than one for all links on the processing target route, it is determined that the use condition of the communication route is satisfied, and the process proceeds to step S127, and the loop process of steps S122 to S125 for all communication routes is terminated. On the other hand, if the available bandwidth is less than the flow bandwidth or the number of available classes is less than one for any link on the processing target route, it is determined that the use condition of the communication route is not satisfied, and the process proceeds to step S125.

[0082] In step S125, the loop process of steps S122 to S125 for the current processing target route is ended. Then, it is determined whether or not this loop process has been performed for all communication routes in the route list created in step S122. As a result, if there is a communication route for which the loop process has not been performed, one of the communication routes is set as the next processing target route, and the next loop process is started. In this way, a communication route different from the previous one is determined to satisfy the communication route use condition in step S124, and the communication load related to the request of the second processing target application group is distributed to multiple communication routes. On the other hand, if the loop process has been performed for all communication routes, the loop process is ended and the process proceeds to step S126.

[0083] In step S126, a message indicating that the communication path calculation process for the bandwidth guaranteed communication has failed is output. This message is notified to the designer by being displayed on the network information input device 21, for example. This can prompt the designer to review the configuration and communication requirements of the in-vehicle network 20.

[0084] In step S127, the link usage table 230 illustrated in Fig. 13 is updated. Specifically, records corresponding to each link on the target route that was the target of the immediately preceding loop process are identified in the link usage table 230, and the required bandwidth value used in the determination process in step S124 and 1 are added to the values ​​of the bandwidth in use 232 and the number of classes in use 233 of these records, respectively. This makes it possible to update the link usage table 230 to reflect the results of the communication route setting performed in the next step S128.

[0085] In step S128, the communication paths and classes for which it has been determined in step S124 that the available bandwidth and the number of available classes for each link satisfy the use conditions are set as the communication paths and classes to be used in the communication of each bandwidth guaranteed application belonging to the second processing target application group, and information indicating these settings is output as the processing result of step S102 in FIG.

[0086] After execution of step S126 or S128, in step S129, the loop process of steps S121 to S129 for the current second group of applications to be processed is terminated. Then, it is determined whether or not this loop process has been performed for all of the communication flows set in step S121. As a result, if there is a communication flow for which the loop process has not been performed, one of the remaining communication flows is selected, and the group of the bandwidth guaranteed application corresponding to that communication flow is set as the next second group of applications to be processed, and the next loop process is started. On the other hand, if the loop process has been performed for all of the communication flows, the communication path calculation process for bandwidth guaranteed communication shown in the flowchart of FIG. 12 is terminated.

[0087] In the communication path calculation process for bandwidth guaranteed communication, the above-described process is executed for each of the multiple bandwidth guaranteed applications by schedule setting unit 51. As a result, the multiple bandwidth guaranteed applications are divided into one or more groups for each communication flow, and a communication path is set and a class is assigned for each group according to the communication bandwidth.

[0088] In the communication path calculation process for the bandwidth guaranteed communication described above, the scheduler 51 may determine the communication path in consideration of the arrangement of the communication devices through which the communication flow passes in the in-vehicle network 20. For example, in the in-vehicle network 20 based on the zone architecture shown in FIG. 1(b), the communication load may be distributed by changing the communication path between the zone ECUs 9a and 9b, which are communication devices arranged at the front of the vehicle 1, for at least a part of the communication related to the requests of the bandwidth guaranteed application grouped for each communication flow from a communication path between the zone ECUs 9c and 9d, which are communication devices arranged at the rear of the vehicle. In addition, the communication load in the in-vehicle network 20 may be distributed by setting an arbitrary communication path for each communication flow by the bandwidth guaranteed application.

[0089] (Network design data) FIG. 14 is a diagram showing an example of network design data 40 output from the communication design device 22 to the communication setup device 23 when the communication design of the in-vehicle network 20 by the communication design device 22 is completed.

[0090] The network design data 40 includes, for example, a schedule table 220 shown in Fig. 14(a) and a routing table 240 shown in Fig. 14(b). The schedule table 220 represents the result of the schedule calculation process for time-guaranteed communication executed in step S100 of Fig. 8, and is the same as the example shown in Fig. 11. The routing table 240 represents the result of the communication path calculation process for bandwidth-guaranteed communication executed in step S102 of Fig. 8, and has records set for each type of communication data by a bandwidth-guaranteed application executed in the in-vehicle network 20.

[0091] Each record in the routing table 240 has data of a source 241, a destination 242, and a communication path 243. Information representing the source and destination communication devices of each communication data is stored in the source 241 and the destination 242, respectively. Information on the communication path of each bandwidth guaranteed application output in step S128 of Fig. 12 is stored in the communication path 243 as information representing the communication path of each communication data.

[0092] According to the first embodiment of the present invention described above, the following advantageous effects are achieved.

[0093] (1) The communication design device 22 is a device that performs communication design for an in-vehicle network 20 to which a plurality of communication devices are connected and communicate with each other according to application requirements. The communication design device 22 includes a communication requirement storage unit 50 that stores communication requirement information (a time-guaranteed communication requirement table 200 and a bandwidth-guaranteed communication requirement table 210) that indicates an allowable delay time indicating the length of communication delay time allowed for each time-guaranteed application and a packet length of communication data determined for each time-guaranteed application, and a schedule setting unit 51 that assigns a communication time slot for each application. The schedule setting unit 51 sets a time slot period based on the allowable delay time related to the plurality of time-guaranteed applications, and sets a time slot length based on the packet length related to the plurality of time-guaranteed applications (steps S115 and S116). This makes it possible to realize an optimal communication design for a network in which communication is performed according to the requirements of various applications with different communication requirements.

[0094] (2) The schedule setting unit 51 executes a schedule calculation process for time guaranteed communication for the time guaranteed application (step S100). In this process, time slots with the same cycle are assigned to multiple time guaranteed applications having the same delay allowance. In this way, it is possible to assign time slots to each time guaranteed application so that communication can be reliably performed within the specified delay allowance.

[0095] (3) In addition, in the schedule calculation process for time guaranteed communication, the schedule setting unit 51 sets the length of the time slot based on the packet lengths related to multiple time guaranteed applications to which time slots of the same period are assigned (step S115). Specifically, the length of the time slot is set based on the sum of the total packet lengths related to multiple time guaranteed applications to which time slots of the same period are assigned, the total switch delay time in the in-vehicle network 20, which is the time required for switch processing in each communication device of the in-vehicle network 20, and the total transmission delay time in the network, which is the time required for communication transmission. This makes it possible to appropriately set the length of the time slot used for communication related to the time guaranteed application.

[0096] (4) The applications executed in the in-vehicle network 20 include a first application group that performs communication requiring time guarantee and a second application group that performs communication requiring bandwidth guarantee. The schedule setting unit 51 determines one or more time slots to be assigned to the first application group according to the delay allowance of each time-guaranteed application belonging to the first application group (step S100). After determining the time slots to be assigned to the first application group, the schedule setting unit 51 determines one or more time slots to be assigned to the second application group (step S102). This makes it possible to reliably assign time slots that satisfy the respective communication requirements to each time-guaranteed application belonging to the first application group and each bandwidth-guaranteed application belonging to the second application group.

[0097] (5) One or more classes that guarantee a predetermined communication bandwidth are set in the time slots assigned to the second application group. The scheduler 51 divides each bandwidth-guaranteed application belonging to the second application group into one or more groups, and assigns a class to each group according to the communication bandwidth. Specifically, the scheduler 51 sets a group of bandwidth-guaranteed applications having a common source and destination according to the communication path in the in-vehicle network 20 (step S121), and calculates the available bandwidth and the number of available classes of each link included in the communication path for each group (step S123). Then, in any link on the communication path, if the total bandwidth of the communication of each bandwidth-guaranteed application belonging to the same group exceeds the available bandwidth, or if the total number of classes of the communication of each bandwidth-guaranteed application belonging to the same group exceeds the number of available classes (step S124: No), the loop process of steps S122 to S125 is executed for another communication path, and the communication load related to the request of the second application group is distributed to multiple communication paths. In this way, the bandwidth-guaranteed communication can be realized in the entire in-vehicle network 20.

[0098] [Second embodiment] Next, a communication design device according to a second embodiment of the present invention will be described below with reference to Fig. 15 to Fig. 19. In this embodiment, an example of a communication design device will be described in which, when a change in communication control is required due to an application update for the in-vehicle network 20 described in Fig. 1, time slots and communication paths are redesigned and the design results are reflected in the in-vehicle network 20.

[0099] (System Configuration) Fig. 15 is a diagram showing a configuration example of a system including a communication design device according to a second embodiment of the present invention. The system shown in Fig. 15 is a system mounted on a vehicle 1 for use, and includes the in-vehicle network 20 and communication design device 22 described in the first embodiment, and an application management device 24.

[0100] The application management device 24 receives update data transmitted from an OTA (Over The Air) server 32 installed on the cloud, and updates the application executed in the in-vehicle network 20 using the update data. In this embodiment, the communication design device 22 determines whether or not a change in communication control is required due to the application update based on the update data output from the application management device 24, and if it is determined that a change in communication control is required, redesigns the time slots and communication paths, and outputs the results to the in-vehicle network 20. In the in-vehicle network 20, by reflecting the redesign results of the time slots and communication paths by the communication design device 22, communication between the communication devices can be continued even if a change in communication control is required due to the application update.

[0101] (Configuration of communication design device) Fig. 16 is a functional block diagram showing the configuration of a communication design device according to the second embodiment of the present invention. As shown in Fig. 16, the communication design device 22 is configured to further include functional blocks of a network information collection unit 53 and a schedule storage unit 54 in addition to the communication requirement storage unit 50, schedule setting unit 51, and setting output unit 52 described in the first embodiment. These functional blocks in the communication design device 22 are realized, for example, by a computer executing a predetermined program.

[0102] The network information collection unit 53 collects network information including the connection relationships and operation states of each communication device in the in-vehicle network 20, and updates the communication requirement information stored in the communication requirement storage unit 50 as necessary based on the collected network information. For example, when the most recently collected network information has changed compared to previously collected network information, the communication requirement information stored in the communication requirement storage unit 50 is updated to reflect the changes.

[0103] In this embodiment, the communication requirement information stored in the communication requirement storage unit 50 is updated according to the contents of update data when update data is input from the application management device 24, in addition to when network information is changed as described above. Specifically, when a new application is added to the in-vehicle network 20, when an application is deleted, when an application update changes the allowable communication delay time or packet length, and so on, update data is input from the application management device 24 to the communication requirement storage unit 50, and the communication requirement information is updated.

[0104] The schedule storage unit 54 stores a schedule for communication by each application of the in-vehicle network 20. That is, time slot information on time slots for time guaranteed communication by the time guaranteed application, such as information on communication cycle, timing, slot length, etc., and information on communication paths for bandwidth guaranteed communication by the bandwidth guaranteed application are stored in the schedule storage unit 54. These pieces of information have the same data configuration as the network design data 40 in Fig. 14 exemplified in the first embodiment, for example.

[0105] In this embodiment, when the schedule setting unit 51 determines that a change in communication control is necessary due to an application update, the schedule setting unit 51 re-sets the communication schedule using the information stored in the schedule storage unit 54. As a result, the time slots and communication paths are redesigned according to the update contents of the application, and are reflected in the communication control of the in-vehicle network 20.

[0106] (Communication rescheduling method) Fig. 17 is a flowchart for explaining a method for resetting a communication schedule in a communication design device according to the second embodiment of the present invention. In the communication design device 22 of this embodiment, when update data is input from the application management device 24, the schedule setting unit 51 executes the process shown in the flowchart of Fig. 17 in response to the input, thereby resetting the communication schedule of the in-vehicle network 20.

[0107] In step S200, it is determined whether or not redesign of time guaranteed communication is necessary. Here, for example, if any of the following conditions (a1) to (d1) is satisfied, it is determined that redesign of time guaranteed communication is necessary and the process proceeds to step S201, whereas if none of the conditions is satisfied, it is determined that redesign of time guaranteed communication is unnecessary and the process proceeds to step S204. Note that these conditions are merely examples, and the determination in step S200 may be made using other conditions. Alternatively, since condition (b1) does not degrade the communication performance of time guaranteed applications that are not deleted, it can be determined that redesign of time guaranteed communication is unnecessary. (a1) Addition of a time assurance application (b1) Removal of time assurance application (c1) Changes in the communication time limit or packet length of the time assurance application (d1) Changes in network information

[0108] In step S201, a schedule recalculation process for time guaranteed communication is performed. Here, the time slots to be assigned to each time guaranteed application are re-determined by executing the process shown in the flowchart of Fig. 18. Details of the process shown in the flowchart of Fig. 18 will be described later.

[0109] In step S202, the time slots for bandwidth guaranteed communication and best effort communication are redetermined. Here, the period excluding the time slots for time guaranteed communication redetermined in the process of step S201 is redetermined as the time slots for bandwidth guaranteed communication and best effort communication.

[0110] In step S203, it is determined whether or not there is a link where the bandwidth of the bandwidth guaranteed communication is overflowing in the time slot redetermined in step S202. For example, the available bandwidth of each link in the redetermined time slot is calculated, and this available bandwidth is compared with the bandwidth used by each link in the current communication schedule by the bandwidth guaranteed application. If the available bandwidth of all links is equal to or greater than the bandwidth used, it is determined that there is no link where the bandwidth is overflowing, and the process proceeds to step S205. On the other hand, if the available bandwidth of any link is less than the bandwidth used, it is determined that there is a link where the bandwidth is overflowing, and the process proceeds to step S204. Note that information on the bandwidth used by each link in the current communication schedule by the bandwidth guaranteed application is stored, for example, in schedule storage unit 54.

[0111] In step S204, the redesign of the bandwidth guaranteed communication is set to "necessary." For example, by switching a predetermined flag information regarding the redesign of the bandwidth guaranteed communication from "invalid" to "valid," the communication design device 22 executes the process of step S206 described later.

[0112] In step S205, it is determined whether or not redesign of the bandwidth-guaranteed communication is necessary. Here, for example, if the redesign of the bandwidth-guaranteed communication is set to "necessary" in step S204, or if any of the following conditions (a2) to (d2) is satisfied, it is determined that redesign of the bandwidth-guaranteed communication is necessary and the process proceeds to step S206, whereas if not, it is determined that redesign of the bandwidth-guaranteed communication is not necessary and the process shown in the flowchart in Fig. 8 is terminated. Note that these conditions are merely examples, and the determination in step S205 may be made using other conditions. Alternatively, since condition (b2) does not degrade the communication performance of the bandwidth-guaranteed application that is not deleted, it can be determined that redesign of the bandwidth-guaranteed communication is not necessary. (a2) Adding a bandwidth guaranteed application (b2) Removal of bandwidth guaranteed application (c2) Changes in communication bandwidth for bandwidth guaranteed applications (d2) Changes in network information

[0113] In step S206, a communication path recalculation process for bandwidth guaranteed communication is performed. Here, the communication path and class allocation for each bandwidth guaranteed application are redetermined by executing the process shown in the flowchart of Fig. 19. The process shown in the flowchart of Fig. 19 will be described in detail later.

[0114] After executing the process of step S206, the communication design device 22 ends the process shown in the flowchart of FIG.

[0115] (Schedule recalculation process for time-guaranteed communication) Fig. 18 is a flowchart showing the flow of the schedule recalculation process for time-guaranteed communication executed in step S201 in Fig. 17. In the flowchart in Fig. 18, the same processes as those in the schedule calculation process for time-guaranteed communication shown in the flowchart in Fig. 9 explained in the first embodiment are assigned common step numbers. The processes with the common step numbers to Fig. 9 will not be explained below unless otherwise necessary.

[0116] 9 described in the first embodiment. After starting the loop process in step S110, in the next step S210, time slot information indicating the current communication schedule of the first processing target application group is obtained from the schedule storage unit 54.

[0117] In step S211, the current communication schedule indicated by the time slot information acquired in step S210 is compared with the update data input from the application management device 24 to determine whether or not there is a change in the communication schedule of the first group of applications to be processed. For example, if a new time guarantee application with communication requirements different from those of other time guarantee applications is added in the update data, and a time slot for communication by the time guarantee application needs to be added, etc., the process proceeds to step S111 if a change in the communication schedule is required. In this case, the process is the same as that shown in the flowchart of FIG. 9 described in the first embodiment for the first group of applications to be processed. On the other hand, if no change in the communication schedule is required, the process proceeds to step S118, and the loop process for the current first group of applications to be processed is terminated.

[0118] In the schedule recalculation process for time guarantee communication, the above-described process is executed for each of the multiple time guarantee applications by the schedule setting unit 51. As a result, the cycle of the communication time slots assigned to each time guarantee application is reset on the vehicle 1 in accordance with the communication requirements of the updated time guarantee applications, and the length of the time slot is reset on the vehicle 1 based on the packet length of the communication data related to the multiple time guarantee applications.

[0119] (Recalculation of communication route for bandwidth guaranteed communication) FIG. 19 is a flowchart showing the flow of the communication path recalculation process for bandwidth guaranteed communication executed in step S206 of FIG.

[0120] In step S220, it is determined whether the application update contents represented by the update data input from application management device 24 are changes only to time-guaranteed communication, and whether there are any changes to bandwidth-guaranteed communication. If there are no changes to bandwidth-guaranteed communication, the process proceeds to step S221, and if there are changes, it is determined that the communication path for bandwidth-guaranteed communication needs to be recalculated, and the process proceeds to step S102.

[0121] In step S221, it is determined whether there is a link where the total bandwidth of the bandwidth guaranteed communication exceeds the available bandwidth. If there is a link in the in-vehicle network 20 where the available bandwidth has decreased due to a change in the time guaranteed communication and the available bandwidth after the decrease is equal to or less than the total bandwidth of the bandwidth guaranteed communication, it is determined that the communication path of the bandwidth guaranteed communication needs to be recalculated, and the process proceeds to step S102. On the other hand, if there is no such link, it is determined that there is no need to recalculate the communication path of the bandwidth guaranteed communication, and the process shown in the flowchart of FIG. 19 is terminated.

[0122] When the process proceeds from step S220 or S221 to step S102, the process performs a communication path calculation process for bandwidth guaranteed communication similar to that described in the first embodiment. That is, the process shown in the flowchart of Fig. 12 is performed to determine the communication path and class of each bandwidth guaranteed application. After the process of step S102 is performed, the process shown in the flowchart of Fig. 19 is terminated.

[0123] In the communication path recalculation process for bandwidth guaranteed communication, the above-described processes are executed by schedule setting unit 51. As a result, the communication path is reconfigured and the class is reassigned according to the communication requirements of the updated bandwidth guaranteed application.

[0124] According to the second embodiment of the present invention described above, the communication design device 22 further includes a network information collecting unit 53 that collects network information including the connection relationship and operation state of the communication devices in the in-vehicle network 20, and a schedule storage unit 54 that stores time slot information related to the time slots set by the schedule setting unit 51. When at least one of the following conditions is satisfied (step S200: Yes): a new time guarantee application is added to the in-vehicle network 20, a time guarantee application is deleted from the in-vehicle network 20, the delay allowable time or packet length is changed, and the network information collected by the network information collecting unit 53 is changed, the schedule setting unit 51 resets the period or length of the time slot based on the time slot information stored in the schedule storage unit 54 (steps S115, S116). As a result, when it becomes necessary to change the communication control due to an application update in the in-vehicle network 20, it is possible to immediately respond to the change.

[0125] [Third embodiment] Next, a communication design device according to a third embodiment of the present invention will be described below with reference to Fig. 20. In this embodiment, an example of a communication design device will be described, which monitors the communication status of the in-vehicle network 20 described in Fig. 1, and if there is an application that does not satisfy the desired communication performance requirements, redesigns the time slots and communication paths, and reflects the design results in the in-vehicle network 20.

[0126] (Configuration of communication design device) Fig. 20 is a functional block diagram showing the configuration of a communication design device according to the third embodiment of the present invention. As shown in Fig. 20, the communication design device 22 is configured to include, for example, the communication requirement storage unit 50, the schedule setting unit 51, and the setting output unit 52 described in the first embodiment, and the network information collection unit 53 and the schedule storage unit 54 described in the second embodiment, as well as the functional blocks of a communication performance monitoring unit 55. These functional blocks in the communication design device 22 are realized, for example, by a computer executing a predetermined program.

[0127] The communication performance monitoring unit 55 monitors, for each application executed in the in-vehicle network 20, the fulfillment status of communication performance requirements, including the allowable delay time, among the communication requirements of each application. If there is an application that does not satisfy the communication performance requirements, the communication performance monitoring unit 55 identifies the application and outputs the result to the schedule setting unit 51.

[0128] In this embodiment, the schedule setting unit 51 resets the communication schedule of the in-vehicle network 20 not only when each of the conditions described in the second embodiment is satisfied, but also when the communication performance monitoring unit 55 identifies an application that does not satisfy the communication performance requirements. At this time, the schedule setting unit 51 can reset the communication schedule of the in-vehicle network 20 in the same manner as in the second embodiment, for example, by executing the process shown in the flowchart of Fig. 17 described in the second embodiment.

[0129] According to the third embodiment of the present invention described above, the communication design device 22 further includes a network information collecting unit 53 that collects network information including connection relationships and operation states of communication devices in the in-vehicle network 20, a communication performance monitoring unit 55 that monitors, for each application, the fulfillment status of communication performance requirements including a delay allowance time among the communication requirements of the application, and identifies the application if there is an application that does not satisfy the communication performance requirements, and a schedule storage unit 54 that stores time slot information regarding the time slot set by the schedule setting unit 51. The schedule setting unit 51 resets the period or length of the time slot based on the time slot information stored in the schedule storage unit 54 when at least one of the following conditions is satisfied: when a new time guarantee application is added to the in-vehicle network 20, when a time guarantee application is deleted from the in-vehicle network 20, when the delay allowance time or packet length has changed, when the network information collected by the network information collecting unit 53 has changed, and when the communication performance monitoring unit 55 has identified an application that does not satisfy the communication performance requirements. As a result of this, it is possible to immediately respond to an application that does not satisfy the desired communication performance requirements in the in-vehicle network 20.

[0130] The present invention is not limited to the various embodiments described above, and includes various modified examples. For example, the above-described embodiments have been specifically described in order to easily explain the present invention, and are not necessarily limited to those having all of the configurations described. Also, a part of the configuration of one embodiment can be replaced with a part of the configuration of another embodiment. Also, a configuration of another embodiment can be added to a configuration of one embodiment. Also, a part of the configuration of each embodiment can be deleted, a part of another configuration can be added, and a part of another configuration can be replaced with a part of another configuration.

[0131] The present invention is not limited to the above-described embodiment, and various modifications are possible without departing from the spirit of the present invention. [Explanation of symbols]

[0132] 1 vehicle 20 In-vehicle network 21 Network information input device 22 Communication design equipment 23 Communication setting device 24 Application Management Device 50 Communication requirements storage unit 51 Schedule setting section 52 Setting output section 53 Network Information Collection Department 54 Schedule memory section 55 Communication Performance Monitoring Department

Claims

1. An apparatus for designing communication of a network to which a plurality of communication devices are connected and in which the plurality of communication devices communicate with each other in accordance with a request from an application, comprising: a communication requirement storage unit that stores an allowable delay time indicating a length of a delay time of the communication allowed for each application and a packet length of communication data determined for each application; a schedule setting unit that assigns a time slot of the communication to each of the applications; The schedule setting unit is setting a period of the time slot based on the allowable delay times related to the plurality of applications; A communication design device that sets the length of the time slot based on the packet lengths related to the multiple applications.

2. 2. A communication design device according to claim 1, The schedule setting unit assigns the time slots of the same cycle to a plurality of the applications having the same delay allowable time.

3. 3. A communication design device according to claim 2, The schedule setting unit sets the length of the time slot based on the packet lengths related to the multiple applications to which the time slots of the same period are assigned.

4. A communication design device according to claim 3, The schedule setting unit sets the length of the time slot based on the sum of the packet lengths related to multiple applications to which the time slots of the same period are assigned, the sum of the switch delay time within the network, which is the time required for switch processing in the communication device, and the sum of the transmission delay time within the network, which is the time required for transmitting the communication.

5. 2. A communication design device according to claim 1, The applications include a first application group that performs communication requiring time guarantee and a second application group that performs communication requiring bandwidth guarantee; The schedule setting unit is determining one or more of the time slots to be assigned to the first application group according to the tolerable delay time of each application belonging to the first application group; a communication design device that determines one or more of the time slots to be allocated to the second application group after determining the time slots to be allocated to the first application group.

6. A communication design device according to claim 5, One or more classes that guarantee a predetermined communication bandwidth are set for the time slots to be assigned to the second application group, The schedule setting unit divides each application belonging to the second application group into one or more groups, and assigns the class to each group according to the communication bandwidth.

7. A communication design device according to claim 6, The schedule setting unit is setting the group according to a communication path in the network; Calculating an available bandwidth and an available number of classes of each link included in the communication path for each group; A communication design device that distributes the communication load related to requests from the second group of applications to multiple communication paths when, in any link on the communication path, the total bandwidth of the communications of each application belonging to the same group exceeds the available bandwidth, or the total number of classes of the communications of each application belonging to the same group exceeds the number of available classes.

8. A communication design device according to claim 7, the network is an in-vehicle network in which the plurality of communication devices mounted in a vehicle communicate with each other, the plurality of communication devices are disposed at least at the front and rear of the vehicle; The schedule setting unit distributes the communication load by changing the communication path for at least a portion of the communications related to requests from the second application group from the communication path passing through the communication devices arranged at the front of the vehicle to the communication path passing through the communication devices arranged at the rear of the vehicle.

9. 2. A communication design device according to claim 1, a network information collection unit that collects network information including connection relationships and operation states of the communication devices in the network; a schedule storage unit that stores time slot information related to the time slots set by the schedule setting unit, the schedule setting unit re-sets the period or length of the time slot based on the time slot information stored in the schedule memory unit when at least one of the following conditions is satisfied: a new application is added to the network, an application is deleted from the network, the allowable delay time or the packet length changes, and the network information collected by the network information collection unit changes.

10. 2. A communication design device according to claim 1, a network information collection unit that collects network information including connection relationships and operation states of the communication devices in the network; a communication performance monitoring unit that monitors, for each of the applications, a fulfillment status of communication performance requirements including the delay allowance time among the communication requirements of the applications, and identifies an application that does not satisfy the communication performance requirements if there is an application; and a schedule storage unit that stores time slot information related to the time slots set by the schedule setting unit, wherein the schedule setting unit re-sets the period or length of the time slot based on the time slot information stored in the schedule memory unit when at least one of the following conditions is satisfied: a new application is added to the network, the application is deleted from the network, the allowable delay time or the packet length has changed, the network information collected by the network information collecting unit has changed, and the communication performance monitoring unit has identified an application that does not satisfy the communication performance requirements.

11. 2. A communication design device according to claim 1, The network is mounted on a vehicle, A communication design device that receives information regarding communication requirements of the application related to control of the vehicle as input and outputs setting information related to communication control of the network.

12. 2. A communication design device according to claim 1, The vehicle is equipped with the network, In the network, the plurality of communication devices mounted on the vehicle communicate with each other in accordance with requests from the plurality of applications related to control of the vehicle; A communication design device that reconfigures a communication schedule of the network within the vehicle.

13. A method for performing communication design of a network to which a plurality of communication devices are connected and which communicate with each other in accordance with a request from an application, comprising the steps of: storing in a computer an allowable delay time indicating a length of a delay time of the communication allowed for each of the applications and a packet length of the communication data determined for each of the applications; allocating a time slot for the communication for each of the applications by the computer; In the time slot allocation, setting a period of the time slot based on the allowable delay times related to the plurality of applications; A communication design method, comprising: setting a length of the time slot based on the packet lengths related to a plurality of the applications.

Citation Information

Patent Citations

  • Radio communication method, program, and coordinator device

    JP2020155857A