In-vehicle network management system, management device, and management program

Abstract

A vehicle-mounted network management system includes a relay unit that performs relay processing of messages in a vehicle-mounted network; an acquisition unit that acquires software configuration information indicating a correspondence relationship between a plurality of software operating in the vehicle-mounted network and a plurality of vehicle-mounted devices respectively equipped with the plurality of software; and a selection unit that selects a setting of the relay processing in the relay unit based on the software configuration information acquired by the acquisition unit.

Description

Technical Field

[0001] This disclosure relates to vehicle network management systems, management devices, and management programs.

[0002] This application claims priority based on Japanese Application No. 2023-192673, filed on November 13, 2023, and incorporates all of its disclosures herein. Background Technology

[0003] Patent Document 1 (International Publication No. 2020 / 179123) discloses a management device as follows. That is, the management device comprises: a detection unit that detects the addition of a function unit to a network including one or more vehicle-mounted function units; an acquisition unit that acquires function unit information, including information related to the network configuration of the added function unit (i.e., the new function unit) detected by the detection unit and the layer below the application layer of the vehicle-mounted function unit; and a generation unit that, based on the function unit information acquired by the acquisition unit, generates configuration information of the network, i.e., a new network, further including the new function unit.

[0004] Existing technical documents

[0005] Patent documents

[0006] Patent Document 1: International Publication No. 2020 / 179123 Summary of the Invention

[0007] The vehicle network management system disclosed herein includes: a relay unit for relaying packets in the vehicle network; an acquisition unit for acquiring software configuration information, which indicates the correspondence between multiple software programs running in the vehicle network and multiple vehicle devices respectively equipped with the multiple software programs; and a selection unit for selecting the relay processing settings in the relay unit based on the software configuration information acquired by the acquisition unit.

[0008] One aspect of this disclosure can be implemented not only as an in-vehicle network management system with such a processing unit, but also as a management method with such processing as a step.

[0009] One embodiment of this disclosure can be implemented not only as a management device with such a characteristic processing unit, but also as a management method that takes the characteristic processing as a step, or as a program for causing a computer to execute the step. Furthermore, one embodiment of this disclosure can be implemented as a semiconductor integrated circuit that is part or all of the implementation of the management device. Attached Figure Description

[0010] Figure 1This is a diagram illustrating an example of the configuration of an in-vehicle network management system according to an embodiment of this disclosure.

[0011] Figure 2 This is a diagram illustrating an example of an in-vehicle network according to an embodiment of the present disclosure.

[0012] Figure 3 This is a diagram illustrating an example of an in-vehicle network according to an embodiment of the present disclosure.

[0013] Figure 4 This is a diagram illustrating the configuration of a relay device according to an embodiment of the present disclosure.

[0014] Figure 5 This diagram illustrates an example of an address mapping table stored in the storage unit of a relay device according to an embodiment of the present disclosure.

[0015] Figure 6 This diagram illustrates an example of a topology mapping table stored in the storage unit of a relay device according to an embodiment of the present disclosure.

[0016] Figure 7 This is a diagram illustrating the configuration of a relay device according to an embodiment of the present disclosure.

[0017] Figure 8 This is a diagram illustrating an example of a software configuration table generated by the aggregation unit in a relay device according to an embodiment of the present disclosure.

[0018] Figure 9 This is a diagram showing an example of an updated software configuration table of the aggregation unit in a relay device according to an embodiment of the present disclosure.

[0019] Figure 10 This is a diagram showing an example of a setting table selected by the relay management unit in the relay device according to an embodiment of the present disclosure.

[0020] Figure 11 This is a diagram illustrating an example of an in-vehicle network according to an embodiment of the present disclosure.

[0021] Figure 12 This is a diagram showing an example of an updated topology mapping table for a collection section in a relay device according to an embodiment of the present disclosure.

[0022] Figure 13 This is a diagram showing an example of an updated software configuration table of the aggregation unit in a relay device according to an embodiment of the present disclosure.

[0023] Figure 14 This diagram illustrates an example of the timing of a change in the relay processing settings in an embodiment of the present disclosure's vehicle network management system.

[0024] Figure 15This diagram illustrates an example of the timing of a change in the relay processing settings in an embodiment of the present disclosure's vehicle network management system. Detailed Implementation

[0025] In recent years, with the increasing popularity of car sharing and the expectation of improved processing power for in-vehicle devices, there has been a demand for customizing in-vehicle networks by adding applications. This necessitates technologies that can add or remove various applications from the in-vehicle network based on user needs.

[0026] [The problem this disclosure aims to solve]

[0027] This technology, which exceeds the technology described in Patent Document 1, is intended to enable the proper setting of message relay processing in vehicular networks.

[0028] The purpose of this disclosure is to provide an in-vehicle network management system, management device, and management program that can appropriately configure the relay processing of messages in an in-vehicle network.

[0029] [The Effects of This Disclosure]

[0030] According to this disclosure, it is possible to appropriately configure the relay processing of messages in the vehicular network.

[0031] [Description of embodiments of this disclosure]

[0032] First, the contents of the embodiments of this disclosure will be described.

[0033] (1) The vehicle network management system according to the present disclosure includes: a relay unit for relaying packets in the vehicle network; an acquisition unit for acquiring software configuration information, which indicates the correspondence between multiple software running in the vehicle network and multiple vehicle devices respectively equipped with the multiple software; and a selection unit for selecting the relay processing settings in the relay unit based on the software configuration information acquired by the acquisition unit.

[0034] This configuration allows for the selection of relay processing settings based on the correspondence between the software and the vehicle-mounted device running the software. Therefore, it enables the configuration of relay processing for relaying packets destined for the software to the node where the software is running. Consequently, appropriate settings for packet relay processing within the vehicle network can be implemented.

[0035] (2) In (1) above, the selection unit may also select the relay processing settings based on topology information representing the topology of the vehicle network.

[0036] With this configuration, the relay processing settings can be selected based on the topology of the vehicular network. Therefore, in a vehicular network with multiple relay devices, the relay processing settings for packets can be appropriately configured.

[0037] (3) In (2) above, the vehicle network management system may also include a storage unit for storing the topology information, and the selection unit may select the relay processing settings based on the topology information in the storage unit.

[0038] With this configuration, for example, when the topology of the vehicle network changes, it is not necessary to obtain information about all nodes in the changed vehicle network. The topology information of the changed vehicle network can be generated based on the topology information in the storage unit and the information of the changed nodes. Furthermore, the relay processing settings in the changed vehicle network can be selected based on the generated topology information.

[0039] (4) In (2) above, the selection unit may also select the relay processing settings based on the topology information obtained from a functional unit that is different from the functional unit that provides the software configuration information.

[0040] With such a configuration, for example in a vehicular network with multiple relay devices, topology information is generated in a relay device where a change in connection nodes has occurred. Based on the topology information obtained from the relay device, the relay processing of messages can be set appropriately.

[0041] (5) In any of (1) to (4) above, the acquisition unit may generate the software configuration information based on the information of the sending source of the message containing the identification information of the software, i.e., the first message, and the identification information contained in the first message.

[0042] Based on this configuration, software configuration information can be generated without obtaining the identification information of the vehicle-mounted device carrying the software from the software itself, but based on the correspondence between the sending source of the first message and the identification information of the software contained in the first message.

[0043] (6) In any of (1) to (4) above, the acquisition unit may generate the software configuration information based on the message containing functional information sent by the software, i.e., the second message, whereby the functional information represents the correspondence between the identification information of the software and the vehicle-mounted device equipped with the software.

[0044] Based on this structure, software configuration information can be generated through simple processing based on the information contained in the second message.

[0045] (7) The management device according to the embodiments of the present disclosure includes: an acquisition unit that acquires software configuration information, the software configuration information indicating the correspondence between multiple software running in the vehicle network and multiple vehicle devices respectively equipped with the multiple software; and a selection unit that selects the setting for relay processing of packets in the vehicle network based on the software configuration information acquired by the acquisition unit.

[0046] This configuration allows for the selection of relay processing settings based on the correspondence between the software and the vehicle-mounted device equipped with the software. Therefore, it enables the configuration of relay processing to relay packets destined for the software to the node where the software is running. Consequently, appropriate settings for packet relay processing within the vehicle network can be implemented.

[0047] (8) The management program of the embodiments of the present disclosure is a management program used in a management device, wherein the management program is used to enable a computer to function as the following components: an acquisition unit that acquires software configuration information, which indicates the correspondence between multiple software running in the vehicle network and multiple vehicle devices respectively equipped with the multiple software; and a selection unit that selects the setting for relay processing of packets in the vehicle network based on the software configuration information acquired by the acquisition unit.

[0048] This configuration allows for the selection of relay processing settings based on the correspondence between the software and the vehicle-mounted device running the software. Therefore, it enables the configuration of relay processing for relaying packets destined for the software to the node where the software is running. Consequently, appropriate settings for packet relay processing within the vehicle network can be implemented.

[0049] The embodiments of this disclosure will now be described using the accompanying drawings. It should be noted that identical or equivalent parts in the drawings are labeled with the same reference numerals, and their descriptions will not be repeated. Furthermore, at least some of the embodiments described below may be combined arbitrarily.

[0050] [Composition and Basic Movements]

[0051] Figure 1 This is a diagram illustrating an example of the configuration of an in-vehicle network management system according to an embodiment of the present disclosure. (Refer to...) Figure 1 The vehicle network management system 301 includes relay devices 101 and 102, and vehicle ECUs 111A, 111B, 111C, and 111D, which are vehicle ECUs (Electronic Control Units) 111. The vehicle ECU 111 is an example of a vehicle device. The relay device 101 is an example of a management device. The vehicle ECU 111 and the relay devices 101 and 102 constitute the vehicle network 31.

[0052] Vehicle-mounted ECUs include, for example, TCUs (Telematics Communication Units), autonomous driving ECUs, engine ECUs, sensors, navigation devices, human-machine interfaces, and cameras.

[0053] Each vehicle ECU 111 is equipped with an application program 112 as software. More specifically, as application programs 112, application program 112A is equipped on vehicle ECU 111A, application program 112B is equipped on vehicle ECU 111B, application program 112C is equipped on vehicle ECU 111C, and application program 112D is equipped on vehicle ECU 111D.

[0054] Application 112 generates messages containing various data, for example, by performing application-layer processing. For instance, application 112 in the vehicle ECU 111, which is a temperature sensor, generates messages containing temperature data representing the outside temperature of the vehicle at predetermined intervals. Application 112 sends the generated messages to another application 112 via at least one of relay devices 101 and 102.

[0055] Repeater 101 has communication ports PA1, PA2, and PA3 as communication ports PA. Repeater 102 has communication ports PB1, PB2, PB3, and PB4 as communication ports PB. Communication ports PA and PB are terminals capable of connecting to Ethernet (registered trademark) cables 32. Communication port PA3 in repeater 101 and communication port PB1 in repeater 102 are connected via Ethernet cable 32.

[0056] The vehicle ECU 111 is connected to relay device 101 or relay device 102 via Ethernet cable 32. More specifically, vehicle ECUs 111A and 111B are connected to communication ports PA1 and PA2 in relay device 101 via Ethernet cable 32, respectively. Vehicle ECUs 111C and 111D are connected to communication ports PB2 and PB3 of relay device 102 via Ethernet cable 32, respectively.

[0057] Relay devices 101 and 102 are, for example, gateway devices, capable of relaying messages between multiple applications 112. Relay devices 101 and 102 perform relay processing of messages exchanged between applications 112 according to Ethernet communication standards.

[0058] It should be noted that the in-vehicle network 31 is not limited to the relay of messages according to the Ethernet communication standard. For example, it can also be constructed according to communication standards such as CAN (Controller Area Network) (registered trademark), FlexRay (registered trademark), MOST (Media Oriented Systems Transport) (registered trademark), and LIN (Local Interconnect Network).

[0059] Furthermore, the vehicle network management system 301 is not limited to having four vehicle ECUs 111, but may also have one, two, three, or five or more vehicle ECUs 111. Additionally, the vehicle network management system 301 is not limited to having one application program 112 mounted on one vehicle ECU 111, but may also have two or more application programs 112 mounted on one vehicle ECU 111.

[0060] Furthermore, the vehicle network management system 301 is not limited to having a single relay device 101, but may also have multiple relay devices 101. Additionally, the vehicle network management system 301 is not limited to having a single relay device 102, but may also have multiple relay devices 102.

[0061] [Topic]

[0062] Figure 2 This is a diagram illustrating an example of an in-vehicle network according to an embodiment of the present disclosure. Figure 2 It shows the relationship with Figure 1 The in-vehicle network 31 shown is different from the in-vehicle network 31A, which also includes an application 112E as an application 112 in the in-vehicle ECU 111B. In the in-vehicle network 31A, when the relay device 101 receives a message destined for the application 112E from the application 112A via the communication port PA1, it sends the received message to the application 112E via the communication port PA2.

[0063] Figure 3 This is a diagram illustrating an example of an in-vehicle network according to an embodiment of the present disclosure. Figure 3 It shows the relationship with Figure 1The in-vehicle network 31 shown also includes an application 112E, which is an application 112, in the in-vehicle ECU 111C. In the in-vehicle network 31B, when the relay device 101 receives a message destined for the application 112E from the application 112A via the communication port PA1, it sends the received message to the application 112E via the communication port PA3 and the relay device 102.

[0064] For example, in conventional vehicle communication systems, the relay device maintains configuration information representing a list of applications 112 running in the vehicle network. However, sometimes it is not possible to properly configure message relay processing based on this configuration information. Specifically, in Figure 2 and Figure 3 The application program 112 running in the vehicular networks 31A and 31B shown is the same, so it is impossible to distinguish between vehicular networks 31A and 31B based on the configuration information. Therefore, in conventional vehicular communication systems, it is impossible to properly configure the relay processing of messages in vehicular networks 31A and 31B based on the configuration information.

[0065] Therefore, the vehicle network management system 301 of the present disclosure solves the above-mentioned problems through the following configuration.

[0066] (Relay device)

[0067] Figure 4 This is a diagram illustrating the configuration of a relay device according to an embodiment of this disclosure. (Refer to...) Figure 4 The relay device 101 includes a relay section 11, a collection section 12, a relay management section 13, and a storage section 14. The collection section 12 is an example of an acquisition section and also an example of a functional section. The relay management section 13 is an example of a selection section. Part or all of the relay section 11, the collection section 12, and the relay management section 13 are implemented, for example, by a processing circuit including one or more processors. The storage section 14 is, for example, a non-volatile memory included in the aforementioned processing circuit.

[0068] The relay device 101 is configured to perform message relay processing. The following describes... Figure 1 The relay processing settings in the vehicular network 31 shown will be explained.

[0069] Figure 5 This diagram illustrates an example of an address mapping table stored in the storage unit of a relay device according to an embodiment of the present disclosure. (Refer to...) Figure 5The storage unit 14 stores an address mapping table T1 that represents the correspondence between the IP addresses of the vehicle ECUs 111 and the ECUIDs that serve as the IDs of the vehicle ECUs 111. The ECUIDs of the vehicle ECUs 111A, 111B, 111C, and 111D are "ecu001", "ecu002", "ecu003", and "ecu004", respectively. For example, in addition to the records of the IP addresses and ECUIDs of the vehicle ECUs 111A, 111B, 111C, and 111D, the address mapping table T1 also includes records of the IP addresses and ECUIDs of vehicle ECUs 111 that can be added to the vehicle network 31. It should be noted that the storage unit 14 may also be configured to store an address mapping table T1 that represents the correspondence between the MAC addresses of the vehicle ECUs 111 or identifiers in protocols above the transport layer and the ECUIDs that serve as the IDs of the vehicle ECUs 111.

[0070] Figure 6 This diagram illustrates an example of a topology mapping table stored in the storage unit of a relay device according to an embodiment of this disclosure. (See also...) Figure 6 The storage unit 14 stores a topology mapping table T2, which represents the correspondence between the IDs of relay devices 101 and 102 (relay device IDs), the IDs of communication ports PA and PB (port IDs), and the IDs of devices connected to communication ports PA and PB (connection node IDs). Topology mapping table T2 is an example of topology information representing the topology of the vehicular network 31. The relay device IDs of relay devices 101 and 102 are set to "esw001" and "esw002", respectively. Furthermore, the port IDs of communication ports PA1, PA2, PA3, PB1, PB2, PB3, and PB4 are set to "A1", "A2", "A3", "B1", "B2", "B3", and "B4", respectively.

[0071] For example, address mapping table T1 and topology mapping table T2 are pre-stored in storage unit 14 by the manufacturer of relay device 101. Address mapping table T1 can be updated by the manufacturer or user of relay device 101. Whenever the topology of the vehicle network 31 changes, aggregation unit 12 updates topology mapping table T2. The updating of topology mapping table T2 by aggregation unit 12 will be described later.

[0072] Figure 7 This is a diagram illustrating the configuration of a relay device according to an embodiment of this disclosure. (Refer to...) Figure 7 The relay device 102 includes a relay section 21, a collection section 22, and a storage section 24. The collection section 22 is an example of a functional section. Part or all of the relay section 21 and the collection section 22 are implemented, for example, by a processing circuit including one or more processors. The storage section 24 is, for example, a non-volatile memory included in the aforementioned processing circuit.

[0073] Similar to storage unit 14, storage unit 24 stores an address mapping table T1 and a topology mapping table T2. It should be noted that storage unit 24 may not store the topology mapping table T2.

[0074] Reference Figure 4 and Figure 7 Relay units 11 and 21 perform relay processing of messages in the vehicle network 31. More specifically, relay unit 11 in relay device 101 receives messages from vehicle ECU 111 or relay device 102 via communication port PA and performs relay processing of the received messages. Relay unit 21 in relay device 102 receives messages from vehicle ECU 111 or relay device 101 via communication port PB and performs relay processing of the received messages.

[0075] Figure 8 This is a diagram illustrating an example of a software configuration table generated by the aggregation unit in a relay device according to an embodiment of the present disclosure. Software configuration table T3 is an example of software configuration information. The application IDs of applications 112A, 112B, 112C, and 112D are “func001”, “func002”, “func003”, and “func004”, respectively.

[0076] Reference Figure 8 The aggregation unit 12 generates a software configuration table T3 that represents the correspondence between multiple applications 112 running in the vehicle network 31 and multiple vehicle ECUs 111 that are respectively equipped with the multiple applications 112. That is, the aggregation unit 12 generates a software configuration table T3 that represents the correspondence between the ID of the application 112 (i.e., the application ID) and the ECUID of the vehicle ECU 111 equipped with the application 112. The application ID is an example of software identification information.

[0077] For example, when the vehicular network 31 is put into use, the application 112 sends an identification message to the relay device 101 as a message including the application ID. The identification message is an example of the first message.

[0078] The aggregation unit 12 generates a software configuration table T3 based on information indicating the source of the identification message and the application ID contained in the identification message.

[0079] More specifically, the aggregation unit 12 receives identification messages from applications 112A and 112B via the relay unit 11, and obtains the IP address and application ID of the sending source from the received identification messages. Furthermore, the aggregation unit 12 receives identification messages from applications 112C and 112D via the relay device 102 and the relay unit 11, and obtains the IP address and application ID of the sending source from the received identification messages.

[0080] The aggregation unit 12 generates a software configuration table T3 based on the IP address and application ID obtained from the identification message and the correspondence between the IP address and ECUID shown in the address correspondence table T1 in the storage unit 14. The aggregation unit 12 stores the generated software configuration table T3 in the storage unit 14. In addition, the aggregation unit 12 outputs the generated software configuration table T3 to the relay management unit 13.

[0081] The relay management unit 13 selects the relay processing settings in the relay unit 11 based on the software configuration table T3 generated by the collection unit 12. For example, the relay management unit 13 also selects the relay processing settings in the relay unit 11 based on the topology mapping table T2 in the storage unit 14. For example, as a selection of relay processing settings, the relay management unit 13 selects the mapping relationship between the message type, the receiving port ID, and the sending port ID.

[0082] More specifically, the storage unit 14 stores a configuration table T4 that represents the correspondence between message types, receiving port IDs, and sending port IDs. For example, the storage unit 14 stores multiple configuration tables T4 with different settings for relay processing.

[0083] The relay management unit 13 receives the software configuration table T3 from the collection unit 12. Based on the received software configuration table T3 and the topology correspondence table T2 in the storage unit 14, it selects a configuration table T4 from the multiple configuration tables T4 in the storage unit 14 that represents the configuration content to be used in the relay processing of the relay unit 11 in the vehicle network 31. The relay management unit 13 outputs the selected configuration table T4 to the relay unit 11.

[0084] The relay unit 11 receives the configuration table T4 from the relay management unit 13 and performs relay processing according to the received configuration table T4.

[0085] Furthermore, the relay management unit 13 selects a setting table T4 from multiple setting tables T4 in the storage unit 14 based on the software configuration table T3 and the topology correspondence table T2. This setting table T4 represents the settings that should be used for relay processing of the relay device 102 in the vehicle network 31. The relay management unit 13 then sends the selected setting table T4 to the relay device 102 via the relay unit 11.

[0086] The relay unit 21 in the relay device 102 receives the setting table T4 from the relay device 101 and performs relay processing according to the received setting table T4.

[0087] (Setting changes 1 when the application is added)

[0088] By installing application 112E in the vehicle ECU111B, in Figure 1 The vehicle network 31 shown has changed to Figure 2In the case of the vehicle network 31A shown, in order to properly perform relay processing of messages sent and received between application 112E and other applications 112, it is necessary to change the relay processing settings. The following explains the relay processing setting changes when application 112E is installed in the vehicle ECU 111B.

[0089] When application 112E is installed on the vehicle ECU 111B, it sends a message, i.e., an identification message, containing the application ID of application 112E to relay device 101.

[0090] The aggregation unit 12 receives identification messages from the application program 112E via the relay unit 11, and obtains the IP address and application ID of the sending source from the received identification messages. Based on the obtained IP address and application ID, and the correspondence between IP address and ECUID shown in the address mapping table T1 in the storage unit 14, the aggregation unit 12 performs an update process to update the software configuration table T3 in the storage unit 14. More specifically, in the update process, the aggregation unit 12 establishes a correspondence between the obtained application ID and ECUID based on the address mapping table T1, and appends the correspondence between the application ID and the ECUID to the software configuration table T3.

[0091] Figure 9 This is a diagram showing an example of an updated software configuration table for the aggregation unit in a relay device according to an embodiment of this disclosure. The application ID of application program 112E is "func005".

[0092] Reference Figure 9 During the update process, the aggregation unit 12 establishes a correspondence between the application ID of the application program 112E ("func005") and the ECUID of the vehicle ECU 111B ("ecu002") based on the address mapping table T1, and appends the correspondence between "func005" and "ecu002" to the software configuration table T3 in the storage unit 14. The aggregation unit 12 saves the updated software configuration table T3 in the storage unit 14. Additionally, the aggregation unit 12 outputs the updated software configuration table T3 to the relay management unit 13.

[0093] The relay management unit 13 receives the software configuration table T3 from the collection unit 12. Based on the received software configuration table T3 and topology correspondence table T2, it selects the configuration table T4 from the multiple configuration tables T4 in the storage unit 14 that represents the configuration content to be used for relay processing of the relay unit 11 in the vehicle network 31A.

[0094] Figure 10This diagram illustrates an example of a setting table selected by the relay management unit in a relay device according to an embodiment of this disclosure. Message AE is a message sent by application 112A to application 112E. Message EA is a message sent by application 112E to application 112A. Message CE is a message sent by application 112C to application 112E. Message EC is a message sent by application 112E to application 112C. Message DE is a message sent by application 112D to application 112E. Message ED is a message sent by application 112E to application 112D.

[0095] For example, the relay management unit 13 selects a configuration table T4 containing records of the receiving port ID and sending port ID of messages EA, EC, ED whose source is application 112E, and records of the receiving port ID and sending port ID of messages AE, CE, DE sent to application 112E, as the configuration table T4 representing the relay processing settings of the relay unit 11 in the vehicle network 31A. The relay management unit 13 outputs a configuration change request containing the selected configuration table T4 to the relay unit 11.

[0096] The relay unit 11 receives a setting change request from the relay management unit 13 and changes the relay processing settings according to the setting table T4 included in the received setting change request.

[0097] Furthermore, the relay management unit 13 selects a setting table T4 from multiple setting tables T4 in the storage unit 14 based on the software configuration table T3 and the topology correspondence table T2. This setting table T4 represents the settings to be used for relay processing of the relay device 102 in the vehicular network 31A. For example, the relay management unit 13 selects a setting table T4 that includes records of the receive port ID and send port ID of messages EA, EC, ED whose source is application 112E, and records of the receive port ID and send port ID of messages AE, CE, DE sent to application 112E, as the setting table T4 representing the settings for relay processing of the relay device 102 in the vehicular network 31A. The relay management unit 13 sends a setting change request containing the selected setting table T4 to the relay device 102 via the relay unit 11.

[0098] The relay unit 21 in the relay device 102 receives a setting change request from the relay device 101 and changes the relay processing settings according to the setting table T4 included in the received setting change request.

[0099] (Setting changes 2 when the application is added)

[0100] Figure 11 This is a diagram illustrating an example of an in-vehicle network according to an embodiment of this disclosure. Figure 1Compared to the vehicle network 31 shown, Figure 11 The vehicle ECU 111E is shown connected to the vehicle network 31C via Ethernet cable 32 to communication port PB4 in relay device 102. Application 112E is mounted on vehicle ECU 111E.

[0101] The vehicle is connected to the relay device 102 via the on-board ECU 111E. Figure 1 The vehicle network 31 shown has changed to Figure 11 In the case of the vehicle network 31C shown, in order to properly perform relay processing of messages sent and received between application 112E and other applications 112, it is necessary to change the relay processing settings. The following describes the relay processing setting changes when the vehicle ECU 111E is newly connected to the relay device 102.

[0102] When the vehicle ECU 111E is connected to the relay device 102, the application 112E sends an identification message including the application ID of the application 112E to the relay device 102.

[0103] Refer again Figure 7 The aggregation unit 22 in the relay device 102 generates a topology mapping table T2 representing the topology of the vehicle network 31C. More specifically, the aggregation unit 22 receives an identification message from the application program 112E via the relay unit 21 and obtains the IP address of the sending source from the received identification message. The aggregation unit 22 refers to the address mapping table T1 in the storage unit 24 to determine the ECUID corresponding to the IP address obtained from the identification message. Based on the determined ECUID, the aggregation unit 22 performs an update process to update the topology mapping table T2 in the storage unit 24.

[0104] Figure 12 This diagram shows an example of an updated topology mapping table for the aggregation section in a relay device according to an embodiment of this disclosure. The ECUID of the vehicle-mounted ECU 111E is set to "ecu005". (See reference...) Figure 12 During the update process, the collection unit 22 is in the storage unit 14 Figure 6 The topology mapping table T2 shown is appended with the correspondence between "B4" and "ecu005". "B4" is the port ID of the communication port PB4 through which the identification message passes, and "ecu005" is the ECUID corresponding to the IP address obtained from the identification message. The aggregation unit 22 stores the updated topology mapping table T2 in the storage unit 14.

[0105] The aggregation unit 22 sends the updated topology mapping table T2 and the identification message received from the application program 112E to the relay device 101 via the relay unit 21. It should be noted that if the storage unit 24 does not pre-store the topology mapping table T2, the aggregation unit 22 sends information indicating the correspondence between "B4" and "ecu005" to the relay device 101 instead of the updated topology mapping table T2. "B4" is the port ID of the communication port PB4 through which the identification message passes, and "ecu005" is the ECUID corresponding to the IP address obtained from the identification message.

[0106] Refer again Figure 4 The collection unit 12 in the relay device 101 receives the topology mapping table T2 and the identification message from the relay device 102 via the relay unit 11. The collection unit 12 performs an update process to update the topology mapping table T2 in the storage unit 14 to the received topology mapping table T2.

[0107] Additionally, the aggregation unit 12 in the relay device 101 obtains the IP address and application ID of the sending source from the received identification message. Based on the obtained IP address and application ID, and the correspondence between IP address and ECUID shown in the address correspondence table in the storage unit 14, the aggregation unit 12 performs update processing on the software configuration table T3 in the storage unit 14.

[0108] Figure 13 This is a diagram illustrating an example of an updated software configuration table for the aggregation unit in a relay device according to an embodiment of this disclosure. (Refer to...) Figure 13 During the update process, the aggregation unit 12 establishes a correspondence between the application ID of the application program 112E ("func005") and the ECU ID of the vehicle ECU 111E ("ecu005") based on the address mapping table T1, and stores the corresponding information in the storage unit 14. Figure 8 The software configuration table T3 shown is appended with the correspondence between "func005" and "ecu005". The collection unit 12 saves the updated software configuration table T3 in the storage unit 14. In addition, the collection unit 12 outputs the updated software configuration table T3 to the relay management unit 13.

[0109] The relay management unit 13 also selects relay processing settings based on the topology correspondence table T2 obtained from the software configuration table T3, which is different from the functional unit providing the source. More specifically, the relay management unit 13 receives the software configuration table T3 from the collection unit 12, and based on the received software configuration table T3 and topology correspondence table T2, selects a setting table T4 from multiple setting tables T4 in the storage unit 14 that represents the settings to be used for relay processing of the relay unit 11 in the vehicle network 31C. For example, the relay management unit 13 selects a setting table T4 that includes records of the receive port ID and send port ID of messages EA, EC, ED whose source is application 112E, and records of the receive port ID and send port ID of messages AE, CE, DE sent to application 112E, as the setting table T4 representing the relay processing settings of the relay unit 11 in the vehicle network 31C. The relay management unit 13 outputs a setting change request containing the selected setting table T4 to the relay unit 11.

[0110] The relay unit 11 receives a setting change request from the relay management unit 13 and changes the relay processing settings according to the setting table T4 included in the received setting change request.

[0111] Furthermore, based on the software configuration table T3 and the topology correspondence table T2, the relay management unit 13 selects a configuration table T4 from multiple configuration tables T4 in the storage unit 14 that represents the configuration content to be used in the relay processing of the relay device 102 in the vehicular network 31C. For example, the relay management unit 13 selects a configuration table T4 that includes records of the receive port ID and send port ID of messages EA, EC, ED whose source is application 112E, and records of the receive port ID and send port ID of messages AE, CE, DE sent to application 112E, as the configuration table T4 representing the configuration content of the relay processing of the relay device 102 in the vehicular network 31C. The relay management unit 13 sends a configuration change request containing the selected configuration table T4 to the relay device 102 via the relay unit 11.

[0112] The relay unit 21 in the relay device 102 receives a setting change request from the relay device 101 and changes the relay processing settings according to the setting table T4 included in the received setting change request.

[0113] [Execution process]

[0114] Figure 14 This diagram illustrates an example of the timing of a change in the relay processing settings in an embodiment of the present disclosure's vehicle network management system. Figure 14 This indicates the timing of the setting changes in "Setting changes 1 when an application was added" mentioned above.

[0115] refer to Figure 14First, when the application 112E is installed on the vehicle ECU 111B, it sends an identification message including the application ID of the application 112E to the relay device 101 (step S11).

[0116] Next, the collection unit 12 obtains the IP address and application ID of the sending source from the received identification message and performs update processing on the software configuration table T3 in the update storage unit 14 (step S12).

[0117] Next, the collection unit 12 outputs the updated software configuration table T3 to the relay management unit 13 (step S13).

[0118] Next, the relay management unit 13 selects the setting table T4 (step S14) which represents the setting content to be used in the relay processing of the relay unit 11 in the vehicle network 31A, based on the software configuration table T3 received from the collection unit 12 and the topology correspondence table T2 in the storage unit 14.

[0119] Next, the relay management unit 13 outputs a setting change request containing the selected setting table T4 to the relay unit 11 (step S15).

[0120] Next, the relay unit 11 changes the relay processing settings according to the setting table T4 included in the setting change request received from the relay management unit 13 (step S16).

[0121] Next, the relay management unit 13 selects the setting table T4, which represents the setting content to be used in the relay processing of the relay device 102 in the vehicle network 31A, based on the software configuration table T3 and the topology correspondence table T2 (step S17).

[0122] Next, the relay management unit 13 sends a setting change request containing the selected setting table T4 to the relay device 102 via the relay unit 11 (step S18).

[0123] Next, the relay unit 21 in the relay device 102 changes the relay processing settings according to the setting table T4 included in the setting change request received from the relay device 102 (step S19).

[0124] Figure 15 This diagram illustrates an example of the timing of a change in the relay processing settings in an embodiment of the present disclosure's vehicle network management system. Figure 15 This indicates the timing of the setting changes in "Setting changes 2 when an application is added" mentioned above.

[0125] Reference Figure 15 First, when the vehicle ECU 111E is connected to the relay device 102, the application 112E sends an identification message including the application ID of the application 112E to the relay device 102 (step S21).

[0126] Next, the collection unit 22 in the relay device 102 obtains the IP address of the sending source from the received identification message, and performs an update process (step S22) to update the topology correspondence table T2 in the storage unit 24 based on the obtained IP address and address correspondence table T1.

[0127] Then, the aggregation unit 22 sends the updated topology correspondence table T2 and the identification message received from the application program 112E to the relay device 101 (step S23).

[0128] Next, the collection unit 12 in the relay device 101 performs an update process (step S24) to update the topology correspondence table T2 in the storage unit 14 to the topology correspondence table T2 received from the collection unit 22.

[0129] Furthermore, the collection unit 12 in the relay device 101 obtains the IP address and application ID of the sending source from the received identification message, and performs update processing on the software configuration table T3 in the storage unit 14 based on the obtained IP address and application ID and the correspondence between IP address and ECUID shown in the address correspondence table in the storage unit 14 (step S25).

[0130] Next, the collection unit 12 outputs the updated software configuration table T3 to the relay management unit 13 (step S26).

[0131] Next, the relay management unit 13 selects the setting table T4, which represents the setting content to be used in the relay processing of the relay unit 11 in the vehicle network 31C, based on the software configuration table T3 received from the collection unit 12 and the topology correspondence table T2 in the storage unit 14 (step S27).

[0132] Next, the relay management unit 13 outputs a setting change request containing the selected setting table T4 to the relay unit 11 (step S28).

[0133] Next, the relay unit 11 changes the relay processing settings according to the setting table T4 included in the setting change request received from the relay management unit 13 (step S29).

[0134] Next, the relay management unit 13 selects the setting table T4, which represents the setting content to be used in the relay processing of the relay device 102 in the vehicle network 31C, based on the software configuration table T3 and the topology correspondence table T2 (step S30).

[0135] Next, the relay management unit 13 sends a setting change request containing the selected setting table T4 to the relay device 102 via the relay unit 11 (step S31).

[0136] Next, the relay unit 21 in the relay device 102 changes the relay processing settings according to the setting table T4 included in the setting change request received from the relay device 102 (step S32).

[0137] It should be noted that in the vehicle network management system 301 of the embodiments of this disclosure, the aggregation unit 12 in the relay device 101 generates the software configuration table T3 based on the IP address of the sending source of the identification message and the application ID contained in the identification message, but is not limited to this. For example, the application 112 sends a function information message to the relay device 101. This function information message is a message that includes function information indicating the correspondence between the application ID of the application 112 and the ECUID of the vehicle ECU 111 equipped with the application 112. The function information message is an example of a second message. In this case, the aggregation unit 12 receives the function information messages from each application 112 via the relay unit 11, and generates the software configuration table T3 based on the function information contained in the received function information messages.

[0138] Furthermore, in the vehicle network management system 301 of the present disclosure, the aggregation unit 12 and the relay management unit 13 are configured to be located in the relay device 101, but this is not a limitation. At least one of the aggregation unit 12 and the relay management unit 13 may also be located in a device different from the relay device 101.

[0139] Furthermore, in the vehicle network management system 301 of the embodiments of this disclosure, the aggregation unit 12 in the relay device 101 is configured to store the generated address mapping table T1 and topology mapping table T2 in the storage unit 14, but it is not limited to this. The aggregation unit 12 may also not store the address mapping table T1 and topology mapping table T2 in the storage unit 14. In this case, whenever it is necessary to change the relay processing settings due to the application 112 being added to the vehicle network 31, the aggregation unit 12 obtains the IP address and ECUID of each vehicle ECU 111 by communicating with each vehicle ECU 111 via the relay unit 11, and generates the address mapping table T1 and topology mapping table T2 based on the obtained IP address and ECUID.

[0140] Furthermore, in the vehicle network management system 301 of this disclosure, the aggregation unit 22 in the relay device 102 is configured to perform update processing of the address mapping table T1 and the topology mapping table T2 when the vehicle ECU 111E is newly connected to the relay device 102, but it is not limited to this. When the vehicle ECU 111E is newly connected to the relay device 102, the aggregation unit 12 in the relay device 101 can perform the update processing of the address mapping table T1 and the topology mapping table T2 in place of the aggregation unit 22.

[0141] Furthermore, in the vehicle network management system 301 of the embodiments of this disclosure, the relay management unit 13 in the relay device 101 is configured to select relay processing settings based on the software configuration table T3 and the topology correspondence table T2 in the storage unit 14, but it is not limited to this. For example, the relay management unit 13 may also select relay processing settings based on the software configuration table T3 instead of using the topology correspondence table T2.

[0142] Furthermore, in the vehicle network management system 301 of the embodiments of this disclosure, the relay management unit 13 in the relay device 101 is configured to select the correspondence between the message type, the receiving port ID, and the sending port ID as the setting for relay processing, but it is not limited to this. For example, in order to set the upper limit of the frequency band in the vehicle network 31, the relay management unit 13 may also be configured to select the correspondence between the message type and the communication frequency band or priority instead of the message path selection.

[0143] The above embodiments should be considered illustrative and not restrictive in all respects. The scope of this disclosure is defined not by the foregoing description but by the claims, and is intended to include all modifications within the meaning and scope equivalent to the claims.

[0144] Each process (function) in the above-described embodiments is implemented by a processing circuit including one or more processors. Besides the one or more processors, the processing circuit may also be composed of an integrated circuit combining one or more memories, various analog circuits, and various digital circuits. The one or more memories store programs (commands) that cause the one or more processors to execute the above processes. The one or more processors may execute the above processes according to the programs read from the one or more memories, or they may execute the above processes according to logic circuits designed to pre-execute the above processes. The processors may be various processors suitable for computer control, such as CPUs (Central Processing Units), GPUs (Graphics Processing Units), DSPs (Digital Signal Processors), FPGAs (Field Programmable Gate Arrays), and ASICs (Application Specific Integrated Circuits). It should be noted that physically separate processors may also cooperate to execute the above processes. For example, the processors located on multiple physically separate computers can also cooperate with each other via networks such as LAN (Local Area Network), WAN (Wide Area Network), and the Internet to execute the aforementioned processes. The programs can be installed into the memory from external server devices via the aforementioned network, or they can be transferred from recording media such as CD-ROM (Compact Disc Read Only Memory), DVD-ROM (Digital Versatile Disk Read Only Memory), and semiconductor memory, and installed into the memory.

[0145] The above description includes the following features.

[0146] [Postscript 1]

[0147] One management method is a management method in an in-vehicle network management system, wherein, The vehicle network management system includes a relay unit for relaying packets within the vehicle network. The management method includes the following steps: Obtain software configuration information representing the correspondence between multiple software programs running in the vehicle network and multiple vehicle devices respectively equipped with the multiple software programs; and Based on the obtained software configuration information, the settings for the relay processing in the relay unit are selected.

[0148] [Postscript 2]

[0149] A management method, which is a management method in a management device, includes the following steps: Obtain software configuration information representing the correspondence between multiple software programs running in the vehicle network and multiple vehicle devices respectively equipped with said multiple software programs; and Based on the obtained software configuration information, the settings for relay processing of messages in the vehicle network are selected.

[0150] [Postscript 3]

[0151] A management device, wherein, Equipped with processing circuitry, The processing circuit acquires software configuration information that represents the correspondence between multiple software programs running in the vehicle network and multiple vehicle devices that are equipped with the multiple software programs. The processing circuit selects the relay processing settings for packets in the vehicular network based on the obtained software configuration information.

[0152] [Explanation of reference numerals in the attached figures]

[0153] 11th Relay Unit

[0154] 12 Collections

[0155] 13 Relay Management Department

[0156] 14 Storage Section

[0157] 21 Relay Unit

[0158] 22nd Assembly Department

[0159] 24 Storage Units

[0160] 31, 31A, 31B, 31C vehicle-mounted networks

[0161] 32 Ethernet cable

[0162] 101 and 102 relay devices

[0163] 111, 111A, 111B, 111C, 111D, 111E Vehicle ECU

[0164] Applications 112, 112A, 112B, 112C, 112D, and 112E

[0165] 301 Vehicle Network Management System

[0166] Communication ports PA, PA1, PA2, PA3, PB, PB1, PB2, PB3, PB4

[0167] T1 Address Mapping Table

[0168] T2 Topology Correspondence Table

[0169] T3 Software Components Table

[0170] T4 settings table.

Claims

1. A vehicle-mounted network management system, comprising: The relay unit performs relay processing of packets in the vehicle network; The acquisition unit acquires software configuration information, which indicates the correspondence between multiple software programs running in the vehicle network and multiple vehicle-mounted devices respectively equipped with the multiple software programs; and The selection unit, based on the software configuration information obtained by the acquisition unit, selects the relay processing settings in the relay unit. The selection unit selects the relay processing settings for relaying the messages sent and received between the multiple software programs based on the software configuration information.

2. The vehicle network management system according to claim 1, wherein, The selection unit also selects the relay processing settings based on topology information representing the topology of the vehicular network.

3. The vehicle network management system according to claim 2, wherein, The vehicle network management system also includes a storage unit for storing the topology information. The selection unit also selects the relay processing settings based on the topology information in the storage unit.

4. The vehicle network management system according to claim 2, wherein, The selection unit also selects the relay processing settings based on the topology information obtained from a functional unit that is different from the functional unit that provides the software configuration information.

5. The vehicle network management system according to any one of claims 1 to 4, wherein, The acquisition unit generates the software configuration information based on information indicating the sending source of the message containing the identification information of the software, namely the first message, and the identification information contained in the first message.

6. The vehicle network management system according to any one of claims 1 to 4, wherein, The acquisition unit generates software configuration information based on the second message, which contains functional information sent by the software. The functional information represents the correspondence between the software's identification information and the vehicle-mounted device equipped with the software.

7. A management device comprising: The acquisition unit acquires software configuration information, which indicates the correspondence between multiple software programs running in the vehicle network and multiple vehicle devices each equipped with said multiple software programs; and The selection unit, based on the software configuration information obtained by the acquisition unit, selects the relay processing settings for packets in the vehicular network. The selection unit selects the relay processing settings for relaying the messages sent and received between the multiple software programs based on the software configuration information.

8. A computer program product comprising a management program for use in a management device, wherein, The management program is used to enable the computer to function as the following components: The acquisition unit acquires software configuration information, which indicates the correspondence between multiple software programs running in the vehicle network and multiple vehicle devices that are equipped with the multiple software programs respectively. and The selection unit, based on the software configuration information obtained by the acquisition unit, selects the relay processing settings for packets in the vehicular network. The selection unit selects the relay processing settings for relaying the messages sent and received between the multiple software programs based on the software configuration information.

Images