Gateway device and in-vehicle communication system

Abstract

To make it easier to dynamically change a transmission / reception destination of data in a gateway device.SOLUTION: A gateway device 10 includes a collection target information reception unit 101 that receives collection target information transmitted from a central ECU in response to a request from a collection request device that is an end ECU requesting collection of data, a data collection unit 102 that collects data requested by the collection request device from a collection destination device that is an end ECU as a collection destination indicated by the collection target information based on the collection target information received by the collection target information reception unit 101, a packing unit 103 that performs packing for combining data collected by the data collection unit 102, and a packing data transmission unit 104 that transmits packing data packed by the packing unit 103 to the collection request device.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present disclosure relates to a gateway device and an in-vehicle communication system used in a vehicle. [Background technology]

[0002] In an in-vehicle communication system in which multiple networks exist, a gateway device that relays communications between different networks is known. For example, Patent Document 1 discloses that the gateway device stores in a storage unit a routing table related to the routing of data communicated between different buses. The routing table associates identification information of data communicated on a certain bus with information on whether the data should be relayed to another bus. [Prior art documents] [Patent documents]

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

[0004] In the gateway device disclosed in Patent Document 1, the routing table is maintained as it is set in advance. Therefore, when changing the relay rules that determine the destination of information transmission and reception between different networks, reprogramming or the like is required at the dealer, and changing the relay rules in the gateway device is not easy. In recent in-vehicle networks, the functional layout within the vehicle may change due to software updates via communication with the outside of the vehicle. In response to such changes in the functional layout within the vehicle, it is required to dynamically change the destination of data transmission and reception in the gateway device. However, in the gateway device disclosed in Patent Document 1, it is not easy to dynamically change the destination of data transmission and reception in the gateway device.

[0005] One object of the present disclosure is to provide a gateway device and an in-vehicle communication system that makes it easier to dynamically change the transmission and reception destination of vehicle data in the gateway device. [Means for solving the problem]

[0006] The above object is achieved by the combination of features recited in the independent claims, and the subclaims define further advantageous embodiments of the disclosure. The reference numerals in parentheses in the claims correspond to specific means described in the following embodiment as one aspect, and do not limit the technical scope of the present disclosure.

[0007] In order to achieve the above object, the first gateway device of the present disclosure is a gateway device that relays data communicated between terminal devices (30, 30a to 30c) connected to different networks of a vehicle, and includes a collection target information receiving unit (101) that receives collection target information transmitted from a data master device (20) that transmits collection target information indicating the terminal device that is the collection destination of the data requested by the collection requesting device in response to a request from the collection requesting device (30a), which is the terminal device that requests the collection of data; a data collecting unit (102) that collects the data requested by the collection requesting device from the collection destination devices (30b, 30c), which are the terminal devices that are the collection destinations indicated by the collection target information, based on the collection target information received by the collection target information receiving unit; a packing unit (103) that performs packing to combine the data collected by the data collecting unit; and a packed data transmitting unit (104) that transmits packed data, which is the data packed by the packing unit, to the collection requesting device.

[0008] According to the above configuration, the gateway device collects data requested by the collection requesting device from the collection destination device indicated by the collection target information received by the collection target information receiving unit, packs the data, and transmits the packed data to the collection requesting device. Therefore, as the collection target information transmitted from the data master device changes, the packed data and the destination of the data can also be changed. This can be done without reprogramming the gateway device. Therefore, it becomes easier to dynamically change the destination of data transmission and reception in the gateway device.

[0009] In order to achieve the above object, the second gateway device of the present disclosure is a gateway device that relays data communicated between terminal devices (30, 30d to 30f) connected to different networks of a vehicle, and includes: a distribution target information receiving unit (105) that receives distribution target information transmitted from a data master device (20) that transmits distribution target information indicating the terminal device to which the data requested by the distribution request device is to be distributed in response to a request from the distribution request device (30d), which is an terminal device that requests distribution of data; a packed data receiving unit (106) that receives packed data transmitted from the distribution request device, which is data obtained by combining and packing data requested to be distributed by the distribution request device; an unpacking unit (107) that unpacks the packed data received by the packed data receiving unit to break down the combined data; and a data distribution unit (108) that transmits the data unpacked by the unpacking unit to distribution destination devices (30e, 30f), which are terminal devices to which the distribution target information indicates, based on the distribution target information received by the distribution target information receiving unit.

[0010] According to the above configuration, the gateway device unpacks packed data, which is data requested for distribution by the distribution request device, and transmits the unpacked data to the distribution destination device indicated by the collection target information received by the distribution target information receiving unit. Therefore, as the distribution target information and packed data transmitted from the data master device change, the distribution destination of the unpacked packed data can also be changed. This can be done without reprogramming the gateway device. Therefore, it becomes easier to dynamically change the data transmission and reception destinations in the gateway device.

[0011] In order to achieve the above object, the first in-vehicle communication system of the present disclosure includes terminal devices (30, 30a to 30c) connected to different networks of the vehicle, the above-mentioned first gateway device (10), and a data master device (20) that transmits collection target information indicating the terminal device from which the data requested by the collection request device is to be collected in response to a request from the collection request device, which is the terminal device requesting the collection of data.

[0012] In order to achieve the above object, the second in-vehicle communication system of the present disclosure includes terminal devices (30, 30d to 30f) connected to different networks of the vehicle, the second gateway device (10) described above, and a data master device (20) that transmits, in response to a request from a distribution request device that is an terminal device requesting data distribution, distribution target information indicating the terminal device to which the data requested by the distribution request device is to be distributed.

[0013] According to these configurations, since the gateway device described above is included, it becomes easier to dynamically change the destination of data transmission and reception at the gateway device. [Brief explanation of the drawings]

[0014] [Figure 1] FIG. 1 is a diagram illustrating an example of a schematic configuration of an in-vehicle communication system. [Figure 2] FIG. 2 is a diagram illustrating an example of a schematic configuration of a gateway device. [Figure 3]FIG. 10 is a diagram illustrating an example of packing a plurality of data into a container. [Figure 4] FIG. 10 is a schematic diagram illustrating an example of a flow of data collection-related processing. [Figure 5] FIG. 10 is a sequence diagram illustrating an example of a flow of data collection-related processing. [Figure 6] FIG. 10 is a schematic diagram illustrating an example of the flow of a data distribution-related process. [Figure 7] FIG. 10 is a sequence diagram illustrating an example of the flow of a data distribution-related process. DETAILED DESCRIPTION OF THE INVENTION

[0015] A number of embodiments for the purpose of disclosure will be described with reference to the drawings. For the sake of convenience, parts having the same functions as parts shown in the drawings used in the previous explanations in the number of embodiments will be given the same reference numerals, and their description may be omitted. For parts given the same reference numerals, the explanations in other embodiments may be referred to.

[0016] (Embodiment 1) <Schematic configuration of in-vehicle communication system 1> A first embodiment of the present disclosure will be described below with reference to the drawings. The in-vehicle communication system 1 shown in FIG. 1 can be used in a vehicle. The in-vehicle communication system 1 can also be referred to as an in-vehicle network system. The in-vehicle communication system 1 is a communication network based on a zone architecture. As shown in FIG. 1, the in-vehicle communication system 1 includes a gateway device 10, a central ECU 20, and an end ECU 30. Although a vehicle using the in-vehicle communication system 1 is not necessarily limited to an automobile, the following description will be given taking the case of use in an automobile as an example.

[0017] The central ECU 20 is an electronic control unit used in a vehicle. The central ECU 20 is a higher-level ECU relative to the gateway device 10. The central ECU 20 performs integrated control of the multiple gateway devices 10. As shown in FIG. 1, the in-vehicle communication system 1 preferably includes multiple gateway devices 10. The central ECU 20 corresponds to a data master device.

[0018] The central ECU 20 holds a correspondence relationship (hereinafter referred to as a collection correspondence relationship) between the type of data requested to be collected and identification information identifying the end ECU 30 from which the data is to be collected. The identification information identifying the end ECU 30 from which the data is to be collected will be referred to as the identification information of the collection destination. The central ECU 20 holds a correspondence relationship (hereinafter referred to as a delivery correspondence relationship) between the type of data requested to be distributed and identification information identifying the end ECU 30 from which the data is to be distributed. The identification information identifying the end ECU 30 from which the data is to be distributed will be referred to as the identification information of the distribution destination. In the collection correspondence relationship and the delivery correspondence relationship, identification information of multiple end ECUs 30 may be associated with one piece of data. In the collection correspondence relationship and the delivery correspondence relationship, identification information of multiple end ECUs 30 may be associated with multiple pieces of data. The collection correspondence relationship and the delivery correspondence relationship may be, for example, a table or a map. The collection correspondence relationship and the delivery correspondence relationship correspond to relay rules. The collection correspondence relationship and the delivery correspondence relationship may be stored in a non-volatile memory of the central ECU 20. The collection correspondence relationship and the distribution correspondence relationship are preferably rewritable. The collection correspondence relationship and the distribution correspondence relationship may be updatable via communication with an external device such as a software-defined vehicle (SDV) or over-the-air (OTA).

[0019] The central ECU 20 performs the following process in response to a request from an end ECU 30 (hereinafter referred to as a collection requesting device) that requests data collection. The central ECU 20 transmits collection target information indicating the end ECU 30 from which the data requested by the collection requesting device is to be collected to the gateway device 10. The collection target information may include, for example, identification information of the end ECU 30 from which the data is to be collected. The collection target information may also include identification information of the collection requesting device so that the source of the data can be identified. The central ECU 20 may determine the identification information of the end ECU 30 from which the data is to be collected by referring to the collection correspondence relationship based on the data requested by the collection requesting device. Then, the central ECU 20 may transmit the collection target information including the determined identification information to the gateway device 10.

[0020] The central ECU 20 performs the following process in response to a request from an end ECU 30 (hereinafter referred to as a distribution request device) that requests data distribution. The central ECU 20 transmits distribution target information indicating the end ECU 30 that is the distribution destination of the data requested by the distribution request device to the gateway device 10. The distribution target information may include, for example, identification information of the end ECU 30 that is the data distribution destination. The central ECU 20 may determine the identification information of the end ECU 30 that is the data distribution destination by referring to the above-mentioned distribution correspondence based on the data requested for distribution from the distribution request device. Then, the central ECU 20 may transmit the distribution target information including the determined identification information to the gateway device 10.

[0021] The end ECU 30 is an electronic control unit used in a vehicle. The end ECU 30 corresponds to a terminal device. The end ECU 30 is a subordinate ECU relative to the gateway device 10. In a vehicle, a plurality of end ECUs 30 are connected to each other via communication lines so as to be able to communicate with each other, forming a network (hereinafter referred to as an in-vehicle network). A vehicle has a plurality of different in-vehicle networks. The different in-vehicle networks may be in-vehicle networks with different communication protocols, or may be in-vehicle networks with the same communication protocol. Examples of standards for in-vehicle networks include CAN (registered trademark) and Ethernet (registered trademark).

[0022] The gateway device 10 is mainly configured with a computer including, for example, a processor, a volatile memory, a non-volatile memory, an I / O, and a bus connecting these. An example of the processor is a CPU. The processor may also be an MPU, a GPU, a DFP (Data Flow Processor), or the like, in addition to a CPU. Note that some of the functions performed by the processor may be performed by a hardware circuit. The gateway device 10 is connected to a plurality of different in-vehicle networks. In the example of FIG. 1, two gateway devices 10 are each connected to three in-vehicle networks. Although FIG. 1 shows an example in which the in-vehicle communication system 1 includes two gateway devices 10, this is not necessarily limited to this. The gateway devices 10 are respectively arranged in a plurality of pre-set zones of the vehicle, such as the front, rear, left, and right of the vehicle.

[0023] The gateway device 10 relays data communicated between end ECUs 30 connected to different in-vehicle networks. When transferring data between in-vehicle networks with different communication protocols, the gateway device 10 also converts the data protocol. The relay process in the gateway device 10 may be performed using the AUTOSAR (registered trademark) standard, for example. The gateway device 10 is a zone ECU that is paired with the central ECU 20 in the zone architecture. Details of the gateway device 10 will be described later.

[0024] Although FIG. 1 illustrates an example in which all in-vehicle networks are bus-type, this is not necessarily limited to this. The network topology of the in-vehicle network may be a connection form other than the bus-type. Although FIG. 1 illustrates a configuration in which the in-vehicle communication system 1 includes three in-vehicle networks for each zone, this is not necessarily limited to this. For example, the number of in-vehicle networks for each zone and the number of end ECUs 30 included in the in-vehicle networks may be numbers other than those illustrated in FIG. 1. Furthermore, the number of in-vehicle networks for each zone may be different, and the number of end ECUs 30 included in each in-vehicle network may be different.

[0025] <Schematic Configuration of Gateway Device 10> Next, a schematic configuration of the gateway device 10 will be described with reference to Fig. 2. As shown in Fig. 2, the gateway device 10 includes, as functional blocks, a collection target information receiving unit 101, a data collecting unit 102, a packing unit 103, a packed data transmitting unit 104, a distribution target information receiving unit 105, a packed data receiving unit 106, an unpacking unit 107, and a data distribution unit 108. Note that some or all of the functions executed by the gateway device 10 may be configured as hardware using one or more ICs or the like. Also, some or all of the functional blocks included in the gateway device 10 may be realized by a combination of software execution by a processor and hardware components.

[0026] The collection target information receiving unit 101 receives the collection target information transmitted from the central ECU 20. The collection target information is transmitted from the central ECU 20 in response to a request from a collection requesting device that requests collection of data.

[0027] The data collection unit 102 performs the following processing based on the collection target information received by the collection target information receiving unit 101. The data collection unit 102 collects data requested by the collection requesting device from a collection destination device, which is the end ECU 30 as the collection destination indicated by the collection target information. As an example, the data requested by the collection requesting device may be collected from the end ECU 30 indicated by the collection destination identification information included in the collection target information as the collection destination device.

[0028] The packing unit 103 performs packing to combine the data collected by the data collection unit 102. As shown in FIG. 3, the packing unit 103 may pack a plurality of pieces of data collected by the data collection unit 102 into a virtual container for data exchange between different in-vehicle networks. FIG. 3 is a diagram schematically illustrating an example of packing a plurality of pieces of data into a container. In FIG. 3, CT represents a container, and DA represents data. Packing a plurality of pieces of data into a container makes it possible to improve the efficiency of the transfer process and facilitate data exchange between different in-vehicle networks.

[0029] The container may be a dynamic container in the AUTOSAR standard, or a static container. A dynamic container is a container that stores input data sequentially. A static container is a container in which the arrangement in which input data is stored is fixed. Here, of dynamic and static containers, it is preferable to use a static container. This is because static containers are more suitable for applications in which specified information is updated to the latest value and sent. Also, static containers can reduce unnecessary bandwidth occupation. The following explanation will continue using an example in which a static container is used as a container.

[0030] The packed data transmission unit 104 transmits packed data, which is data packed by the packing unit 103, to the collection requesting device. The collection requesting device can obtain the data requested for collection by receiving this packed data. The collection requesting device can obtain the packed data by unpacking the packed data. Unpacking is a process of breaking down data that has been combined by packing. In the example of this embodiment, a static container in which data has been packed is transmitted to the collection requesting device.

[0031] According to the above configuration, the gateway device 10 collects data requested by the collection requesting device from a collection destination device indicated by the collection target information received by the collection target information receiving unit 101, packs the data, and transmits the packed data to the collection requesting device. Therefore, as the collection target information transmitted from the central ECU 20 changes, the packed data and the destination of the data can also be changed. For example, even if the type of data handled by the end ECU 30 changes due to SDV, OTA, or the like, the change can be accommodated by changing the received collection target information without the need for reprogramming the gateway device 10. Therefore, it becomes easier to dynamically change the destination of transmission and reception of data in the gateway device 10.

[0032] The distribution target information receiving unit 105 receives the distribution target information transmitted from the central ECU 20. The distribution target information is transmitted from the central ECU 20 in response to a request from a distribution request device that requests data distribution.

[0033] The packed data receiving unit 106 receives packed data, which is data obtained by combining and packing data requested for distribution by the distribution request device and is transmitted from the distribution request device. This packed data is assumed to be generated by the distribution request device. In this embodiment, the packed data receiving unit 106 receives a static container in which data is packed from the distribution request device.

[0034] The unpacking unit 107 performs unpacking to break down combined data from the packed data received by the packed data receiving unit 106. In the example of the present embodiment, the unpacking unit 107 unpacks the static container and extracts the data stored in the static container.

[0035] The data distribution unit 108 performs the following processing based on the distribution target information received by the distribution target information receiving unit 105. The data distribution unit 108 transmits the data unpacked by the unpacking unit 107 to the distribution destination device, which is the end ECU 30 as the distribution destination indicated by the distribution target information. As an example, the data requested by the distribution request device may be distributed to the end ECU 30 indicated by the identification information of the distribution destination included in the distribution target information as the distribution destination device.

[0036] According to the above configuration, the gateway device 10 unpacks packed data, which is data requested for distribution by a distribution request device, and transmits the unpacked data to a distribution destination device indicated by the collection target information received by the distribution target information receiving unit 105. Therefore, as the distribution target information transmitted from the central ECU 20 changes, the distribution destination of the unpacked data can also be changed. For example, even if the type of data handled by the end ECU 30 changes due to SDV, OTA, or the like, the change can be accommodated by changing the received distribution target information without the need for reprogramming the gateway device 10. Therefore, it becomes easier to dynamically change the transmission and reception destination of data in the gateway device 10.

[0037] Furthermore, with the above configuration, even when updating the collection correspondence relationships and distribution correspondence relationships (i.e., relay rules) stored in the central ECU 20, it is possible to reduce the effort required for updating compared to a configuration in which the relay rules are stored in the gateway device 10. This is because it is only necessary to update the relay rules of the central ECU 20, which controls the multiple gateway devices 10 in an integrated manner, without having to update the relay rules of each of the multiple gateway devices 10.

[0038] <Data collection related processing> Here, an example of processing related to the collection of data requested by a collection requesting device in the in-vehicle communication system 1 (hereinafter referred to as data collection-related processing) will be described with reference to Figures 4 and 5. Figure 4 is a schematic diagram for describing an example of the flow of the data collection-related processing. Figure 5 is a sequence diagram for describing an example of the flow of the data collection-related processing. For convenience, the description will be given assuming that the end ECUs 30 subordinate to the gateway device 10 are end ECUs 30a, 30b, and 30c. Here, it is assumed that the end ECU 30a is the collection requesting device, and the end ECUs 30b and 30c are collection destination devices.

[0039] First, at t1 in FIG. 5, the end ECU 30a, which is a collection requesting device, transmits a collection start request requesting data collection to the central ECU 20 (see A in FIG. 4). Then, the central ECU 20 receives the collection start request transmitted from the end ECU 30a. The collection start request may include information capable of identifying the type of data requested by the end ECU 30a and identification information of the end ECU 30a as the collection source. At t2, the central ECU 20 enables a collection function, which is a function related to data collection. At t3, the central ECU 20 starts a timer that counts the time limit for enabling the collection function. The collection function is intended to disable the collection function when the count reaches a specified value and times out, even if data collection has not been completed.

[0040] At t4, the central ECU 20 transmits a notification to start data collection (hereinafter, referred to as collection start notification) to the gateway device 10 (see B in FIG. 4). The collection start notification includes the above-mentioned collection target information. The central ECU 20 refers to the collection correspondence relationship and includes, in the collection target information, identification information of the end ECU 30 that is the collection destination, which corresponds to the type of data requested by the end ECU 30a. In this example of the present embodiment, the identification information of the end ECU 30b and the end ECU 30c is included in the collection target information as identification information of the end ECU 30 that is the collection destination. The collection start notification may also include, as identification information of the collection source, identification information of the end ECU 30a, which is the collection requesting device. Then, at t4, the gateway device 10 receives the collection start notification transmitted from the central ECU 20. At this time, the collection target information receiving unit 101 of the gateway device 10 receives the collection target information included in the collection start notification.

[0041] At t5, a response to the collection start notification sent at t4 (hereinafter referred to as a collection start response) is transmitted to the end ECU 30a, which is the collection requesting device. The collection start response may be a response as to whether communication is possible between the gateway device 10 and the in-vehicle network connected to the gateway device 10. The central ECU 20 may determine whether communication is possible from the diagnostic information. In this embodiment, a case will be described in which a collection start response indicating that communication is possible between the gateway device 10 and the in-vehicle network connected to the gateway device 10 is transmitted.

[0042] At t6, the packing unit 103 of the gateway device 10 generates a static container. At t7, the data collection unit 102 of the gateway device 10 collects the data requested by the collection requesting device from the end ECU 30b as the collection destination indicated by the collection target information (see C in FIG. 4). In FIG. 5, the data requested by the collection requesting device is described as collection target data. At t8, the data collection unit 102 collects the data requested by the collection requesting device from the end ECU 30c as the collection destination indicated by the collection target information (see C in FIG. 4).

[0043] At t9, the packing unit 103 stores the data collected at t7 and t8 in the static container generated at t6 and packs the data. At t10, the packed data transmitting unit 104 transmits the packed data packed at t9 to the end ECU 30a, which is the collection requesting device (see D in FIG. 4). The packed data transmitting unit 104 may identify the end ECU 30a as the destination of the packed data from the collection source identification information included in the collection start notification. Then, at t10, the end ECU 30a receives the packed data transmitted from the gateway device 10. The end ECU 30a that has received the packed data may unpack the packed data and use the extracted data.

[0044] At t11, the end ECU 30a, which is the collection requesting device, transmits a collection stop request to the central ECU 20 to request that data collection be stopped. Then, the central ECU 20 receives the collection stop request transmitted from the end ECU 30a. At t12, the central ECU 20 disables the collection function. At t13, the central ECU 20 stops the timer.

[0045] At t14, the central ECU 20 transmits a notification to stop data collection (hereinafter, collection stop notification) to the gateway device 10. Then, at t14, the gateway device 10 receives the collection stop notification transmitted from the central ECU 20. At t15, a response to the collection stop notification transmitted at t14 (hereinafter, collection stop response) is transmitted to the end ECU 30a, which is the collection requesting device. The collection stop response may be a response regarding whether communication is possible between the gateway device 10 and the in-vehicle network connected to the gateway device 10. In this embodiment, a case will be described in which a collection stop response is transmitted indicating that communication is possible between the gateway device 10 and the in-vehicle network connected to the gateway device 10. At t16, the packing unit 103 of the gateway device 10 deletes the static container.

[0046] In the present embodiment, the collection requesting device is the end ECU 30, but this is not necessarily limited to this. The collection requesting device is not limited to a device installed inside the vehicle. For example, the collection requesting device may be a device outside the vehicle that is connected to the gateway device 10 via communication.

[0047] <Data distribution related processing> Next, an example of processing related to the distribution of data requested by a distribution request device in the in-vehicle communication system 1 (hereinafter referred to as data distribution related processing) will be described with reference to Figs. 6 and 7. Fig. 6 is a schematic diagram for describing an example of the flow of the data distribution related processing. Fig. 7 is a sequence diagram for describing an example of the flow of the data distribution related processing. Here, for convenience, the description will be given assuming that the end ECUs 30 lower than the gateway device 10 are end ECU 30d, end ECU 30e, and end ECU 30f. Here, it is assumed that the end ECU 30d is the distribution request device, and the end ECU 30e and end ECU 30f are distribution destination devices.

[0048] First, at t21 in FIG. 7, the end ECU 30d, which is a distribution requesting device, transmits a distribution start request requesting data distribution to the central ECU 20 (see E in FIG. 6). Then, the central ECU 20 receives the distribution start request transmitted from the end ECU 30d. The distribution start request may include information capable of identifying the type of data requested to be distributed by the end ECU 30d and identification information of the end ECU 30a as the distribution source. At t22, the central ECU 20 enables a distribution function related to data distribution. At t23, the central ECU 20 starts a timer that counts the time limit for enabling the distribution function. The distribution function is designed to disable the distribution function when the count reaches a specified value and times out, even if data distribution has not been completed.

[0049] At t24, the central ECU 20 transmits a notification to start data distribution (hereinafter, distribution start notification) to the gateway device 10 (see F in FIG. 6). The distribution start notification includes the above-mentioned distribution target information. The central ECU 20 refers to the distribution correspondence relationship and includes, in the distribution target information, identification information of the end ECU 30 of the distribution destination, which corresponds to the type of data requested to be distributed by the end ECU 30d. In the example of the present embodiment, the identification information of the end ECU 30e and the end ECU 30f is included in the distribution target information as identification information of the end ECU 30 of the distribution destination. The distribution start notification may also include, as identification information of the distribution source, identification information of the end ECU 30d, which is the distribution request device. Then, at t24, the gateway device 10 receives the distribution start notification transmitted from the central ECU 20. At this time, the distribution target information receiving unit 105 of the gateway device 10 receives the distribution target information included in the distribution start notification.

[0050] At t25, a response to the distribution start notification sent at t24 (hereinafter referred to as distribution start response) is transmitted to the end ECU 30d, which is the distribution request device. The distribution start response may be a response as to whether communication is possible between the gateway device 10 and the in-vehicle network connected to the gateway device 10. Whether communication is possible may be determined in the same manner as described at t5. In this embodiment, a case will be described in which a distribution start response indicating that communication is possible between the gateway device 10 and the in-vehicle network connected to the gateway device 10 is transmitted.

[0051] At t26, the end ECU 30d, which is the distribution request device, transmits packed data, in which data requested to be distributed is packed, to the gateway device 10 (see G in FIG. 6). Then, the packed data receiving unit 106 of the gateway device 10 receives this packed data. In the example of the present embodiment, the packed data is data packed in a static container. At t27, the unpacking unit 107 of the gateway device 10 unpacks the packed data received by the packed data receiving unit 106.

[0052] At t28, the data distribution unit 108 of the gateway device 10 transmits the data that the distribution request device requested to be distributed and that was unpacked and extracted at t27 to the end ECU 30e, which is the distribution destination device (see H in FIG. 6). Then, at t28, the end ECU 30e receives this data transmitted from the gateway device 10. At t29, the data distribution unit 108 transmits the data that the distribution request device requested to be distributed and that was unpacked and extracted at t27 to the end ECU 30f, which is the distribution destination device (see H in FIG. 6). Then, at t29, the end ECU 30f receives this data transmitted from the gateway device 10. The data distribution unit 108 may identify the end ECU 30e and the end ECU 30f as the data destinations from the distribution target information included in the distribution start notification.

[0053] At t30, the end ECU 30d, which is a distribution request device, transmits a distribution stop request to the central ECU 20, requesting that data distribution be stopped. Then, the central ECU 20 receives the distribution stop request transmitted from the end ECU 30d. At t31, the central ECU 20 disables the distribution function. At t32, the central ECU 20 stops the timer.

[0054] At t33, the central ECU 20 transmits a notification to stop data distribution (hereinafter, distribution stop notification) to the gateway device 10. Then, at t33, the gateway device 10 receives the distribution stop notification transmitted from the central ECU 20. At t34, a response to the distribution stop notification transmitted at t33 (hereinafter, distribution stop response) is transmitted to the end ECU 30d, which is the distribution request device. The distribution stop response may be a response regarding whether communication is possible between the gateway device 10 and the in-vehicle network connected to the gateway device 10. In this embodiment, a case will be described in which a distribution stop response indicating that communication is possible between the gateway device 10 and the in-vehicle network connected to the gateway device 10 is transmitted.

[0055] (Embodiment 2) In the above embodiment, the in-vehicle communication system 1 includes two gateway devices 10, but this is not necessarily limited to this. For example, the in-vehicle communication system 1 may include one gateway device 10, or may include three or more gateway devices 10.

[0056] The present disclosure is not limited to the above-described embodiments, and various modifications are possible within the scope of the claims. Embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also within the technical scope of the present disclosure. The control unit and method described in the present disclosure may be implemented by a special-purpose computer comprising a processor programmed to execute one or more functions embodied in a computer program. Alternatively, the apparatus and method described in the present disclosure may be implemented by a special-purpose hardware logic circuit. Alternatively, the apparatus and method described in the present disclosure may be implemented by one or more special-purpose computers configured by combining a processor executing a computer program with one or more hardware logic circuits. Furthermore, the computer program may be stored as instructions executed by a computer on a computer-readable non-transitory tangible recording medium. [Explanation of symbols]

[0057] 1 in-vehicle communication system 1, 10 gateway device, 20 central ECU (data master device), 30 end ECU (end device), 30a end ECU (end device, collection request device), 30b end ECU (end device, collection destination device), 30c end ECU (end device, collection destination device), 30d end ECU (end device, distribution request device), 30e end ECU (end device, distribution destination device), 30f end ECU (end device, distribution destination device), 101 collection target information receiving unit, 102 data collection unit, 103 packing unit, 104 packed data transmitting unit, 105 distribution target information receiving unit, 106 packed data receiving unit, 107 unpacking unit, 108 data distribution unit

Claims

1. A gateway device that relays data communicated between terminal devices (30, 30a to 30c) connected to different networks of a vehicle, a collection target information receiving unit (101) that receives, in response to a request from a collection requesting device (30a) that is the end device requesting data collection, collection target information transmitted from a data master device (20) that transmits collection target information indicating the end device that is the collection destination of the data requested by the collection requesting device; a data collection unit (102) that collects data requested by the collection requesting device from collection destination devices (30b, 30c), which are end devices as collection destinations indicated by the collection target information, based on the collection target information received by the collection target information receiving unit; a packing unit (103) that performs packing to combine the data collected by the data collection unit; and a packed data transmitting unit (104) that transmits packed data, which is data packed by the packing unit, to the collection requesting device.

2. A gateway device that relays data communicated between terminal devices (30, 30d to 30f) connected to different networks of a vehicle, a distribution target information receiving unit (105) that receives, in response to a request from a distribution request device (30d) that is the end device requesting data distribution, distribution target information that indicates the end device that is the distribution destination of the data requested by the distribution request device, transmitted from a data master device (20); a packed data receiving unit (106) for receiving packed data transmitted from the distribution request device, the packed data being data obtained by combining and packing data requested to be distributed by the distribution request device; an unpacking unit (107) that performs unpacking by decomposing combined data from the packed data received by the packed data receiving unit; and a data distribution unit (108) that transmits the data unpacked by the unpacking unit to a destination device (30e, 30f) that is the end device as the destination indicated by the distribution target information, based on the distribution target information received by the distribution target information receiving unit.

3. Terminal devices (30, 30a to 30c) connected to different networks of the vehicle; A gateway device (10) according to claim 1; and a data master device (20) that transmits, in response to a request from a collection request device, which is the terminal device requesting the collection of data, collection target information indicating the terminal device from which the data requested by the collection request device is to be collected.

4. Terminal devices (30, 30d to 30f) connected to different networks of the vehicle; A gateway device (10) according to claim 2; and a data master device (20) that, in response to a request from a distribution request device that is the end device requesting data distribution, transmits distribution target information indicating the end device to which the data requested by the distribution request device is to be distributed.

5. 5. The in-vehicle communication system according to claim 3 or 4, An in-vehicle communication system including a plurality of the gateway devices.

Images