Vehicle management system and vehicle management method

Abstract

This vehicle management system includes: an acquiring unit that acquires network information relating to a vehicle-mounted network in a vehicle; a converting unit that performs conversion processing for converting the network information acquired by the acquiring unit into setting information necessary for setting performed by centralized network configurations that comply with the IEEE 802.1Qcc standard; and a notifying unit that performs notification processing for notifying a centralized user configuration that complies with the IEEE 802.1Qcc standard of the setting information converted by the converting unit.

Description

Vehicle management system and vehicle management method

[0001] This application claims priority based on Japanese Patent Application No. 2023-214355, filed December 20, 2023, the disclosure of which is incorporated herein in its entirety by reference.

[0002] Patent Document 1 (WO 2020 / 145334) discloses the following technology: That is, a vehicle control device controls a plurality of repeaters based on a control scenario that associates the state of a vehicle in which a vehicle network made up of a plurality of repeaters is built with control content to be set for each of the plurality of repeaters.

[0003] International Publication No. 2020 / 145334

[0004] The vehicle management system of the present disclosure includes an acquisition unit that acquires network information related to an in-vehicle network in a vehicle, a conversion unit that performs a conversion process that converts the network information acquired by the acquisition unit into setting information required for setting by a Centralized Network Configuration that complies with the IEEE802.1Qcc standard, and a notification unit that performs a notification process that notifies a Centralized User Configuration that complies with the IEEE802.1Qcc standard of the setting information converted by the conversion unit.

[0005] One aspect of the present disclosure may be realized not only as a vehicle management system including such a characteristic processing unit, but also as a program for causing a computer to execute the steps of such characteristic processing, or as a semiconductor integrated circuit that realizes part or all of the vehicle management system.

[0006] FIG. 1 is a diagram illustrating an example of a configuration of a communication system according to an embodiment of the present disclosure. FIG. 2 is a diagram illustrating an example of a configuration of a vehicle management system according to an embodiment of the present disclosure. FIG. 3 is a diagram illustrating an example of a configuration of a relay device according to an embodiment of the present disclosure. FIG. 4 is a diagram illustrating an example of a configuration of a new network in a vehicle management system according to an embodiment of the present disclosure. FIG. 5 is a diagram illustrating a fully centralized model defined in the IEEE 802.1Qcc standard. FIG. 6 is a diagram illustrating an example of network information held by a server according to an embodiment of the present disclosure. FIG. 7 is a diagram illustrating the contents of UNI information defined in IEEE 802.1Qcc. FIG. 8 is a diagram illustrating an example of a correspondence table stored by a relay device according to an embodiment of the present disclosure. FIG. 9 is a flowchart defining an operation procedure when a relay device according to an embodiment of the present disclosure performs a conversion process. FIG. 10 is a diagram illustrating an example of a processing sequence of a server, a relay device, and an in-vehicle device in a communication system according to an embodiment of the present disclosure. FIG. 11 is a diagram illustrating an example of network information held by a first variation of a server according to an embodiment of the present disclosure. FIG. 12 is a diagram illustrating a second variation of a relay device according to an embodiment of the present disclosure. Fig. 13 is a diagram illustrating a configuration of a relay device according to a third modification of the embodiment of the present disclosure. Fig. 14 is a diagram illustrating a configuration of an in-vehicle device according to a third modification of the embodiment of the present disclosure.

[0007] Technologies for changing the configuration of in-vehicle networks have been developed.

[0008] [Problem to be Solved by the Present Disclosure] In recent years, development of vehicles that can dynamically change the configuration of an in-vehicle network using SDN (Software Defined Network) technology has been progressing. Here, the IEEE (registered trademark) 802.1Qcc standard specifies a method for dynamically changing the configuration.

[0009] When dynamically changing the settings of an in-vehicle network in accordance with the IEEE 802.1Qcc standard, there is a possibility that the in-vehicle network may include a device that cannot communicate in accordance with the standard, which poses a problem that it is difficult to change the settings of the in-vehicle network.

[0010] The present disclosure has been made to solve the above-mentioned problems, and its purpose is to provide a vehicle management system and a vehicle management method that can more reliably change the settings of an in-vehicle network.

[0011] [Effects of the Present Disclosure] According to the present disclosure, it is possible to more reliably change the settings of an in-vehicle network.

[0012] [Description of Embodiments of the Present Disclosure] First, the contents of the embodiments of the present disclosure will be listed and described. (1) A vehicle management system according to an embodiment of the present disclosure includes an acquisition unit that acquires network information related to an in-vehicle network in a vehicle, a conversion unit that performs a conversion process that converts the network information acquired by the acquisition unit into setting information required for setting by a Centralized Network Configuration that complies with the IEEE 802.1Qcc standard, and a notification unit that performs a notification process that notifies a Centralized User Configuration that complies with the IEEE 802.1Qcc standard of the setting information converted by the conversion unit.

[0013] The IEEE 802.1Qcc standard specifies a method in which a Centralized Network Configuration (hereinafter also referred to as "CNC") configures a network. In this method, a Centralized User Configuration (hereinafter also referred to as "CUC") collects various information indicating the contents of a message from a device or the like that has transmitted the message, and creates configuration information necessary for the CNC to perform the configuration based on the various information. As described above, by converting the acquired information about the in-vehicle network into configuration information and notifying the CUC of the configuration information, even if the device or the like that has transmitted the message does not have the function of communicating with the CUC in accordance with the standard, the configuration information can be provided to the CNC, and the in-vehicle network configuration can be changed according to the configuration information. This allows for more reliable configuration changes to be made to the in-vehicle network.

[0014] (2) In the above (1), the network information may include information about services provided in the in-vehicle network.

[0015] With this configuration, the acquired network information can be converted into appropriate setting information according to the type of service provided in the in-vehicle network.

[0016] (3) In the above (1) or (2), the in-vehicle network may include a functional unit that provides a service in the in-vehicle network, and the network information may include information about the functional unit.

[0017] With this configuration, the acquired network information can be converted into appropriate setting information according to the information of the functional units that make up the in-vehicle network.

[0018] (4) In any one of (1) to (3) above, the acquisition unit may acquire the network information from an external device outside the vehicle.

[0019] With this configuration, information about the in-vehicle network can be easily obtained.

[0020] (5) In any one of (1) to (4) above, the setting information may be User Network Interface information used between the Centralized User Configuration and the Centralized Network Configuration.

[0021] The IEEE 802.1Qcc standard specifies that the CNC configures the relay device that relays messages exchanged between the Talker and the Listener using management information based on User Network Interface information (hereinafter also referred to as "UNI information"). With the above configuration, the CNC does not need to convert the configuration information provided by the CUC into UNI information, making it easy to change the settings of the relay device.

[0022] (6) In the above (5), the network information may include information on services provided in the in-vehicle network, and the conversion unit may perform the conversion process using correspondence information indicating a correspondence relationship between the services and the User Network Interface information.

[0023] With this configuration, information about the in-vehicle network can be easily converted into setting information.

[0024] (7) In any one of (1) to (6) above, the notification unit may perform the notification process when request information for requesting the setting information is received from the Centralized User Configuration.

[0025] With this configuration, for example, when the CUC determines whether or not the settings of the in-vehicle network in the CNC need to be changed, the setting information can be more reliably notified to the CUC in response to a request from the CUC.

[0026] (8) In any of (1) to (6) above, the vehicle management system may further include a detection unit that detects a change in the configuration of the in-vehicle network, and the notification unit may perform the notification process when the change is detected by the detection unit.

[0027] With this configuration, it is possible to easily grasp the timing when the setting information should be notified to the CUC.

[0028] (9) A vehicle management method according to an embodiment of the present disclosure is a vehicle management method in a vehicle management system, and includes the steps of acquiring network information related to an in-vehicle network in a vehicle, performing a conversion process of converting the acquired network information into setting information required for settings performed by a Centralized Network Configuration conforming to the IEEE 802.1Qcc standard, and performing a notification process of notifying a Centralized User Configuration conforming to the IEEE 802.1Qcc standard of the converted setting information.

[0029] The IEEE 802.1Qcc standard specifies a method by which a CNC configures a network. In this method, the CUC collects various information indicating the contents of a message from the device that sent the message and creates the configuration information required for the CNC to perform the configuration based on the various information. As described above, by converting the acquired information about the in-vehicle network into configuration information and notifying the CUC of the configuration information, even if the device that sent the message does not have the function to communicate with the CUC in accordance with the standard, the configuration information can be provided to the CNC, allowing the in-vehicle network configuration to be changed in accordance with the configuration information. This allows for more reliable configuration changes to be made to the in-vehicle network.

[0030] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. In the drawings, identical or corresponding parts are designated by the same reference numerals, and their description will not be repeated. Furthermore, at least some of the embodiments described below may be combined in any manner.

[0031] [Vehicle Management System] Fig. 1 is a diagram illustrating an example of a configuration of a communication system according to an embodiment of the present disclosure. Referring to Fig. 1, a communication system 501 includes a server 151 and one or more vehicle management systems 301. The vehicle management system 301 is mounted on a vehicle 1.

[0032] The server 151 is used by, for example, a business operator or an individual (hereinafter collectively referred to as a user) that manages the operation of the vehicle 1. The server 151 is an example of an external device outside the vehicle 1.

[0033] 2 is a diagram illustrating an example of a configuration of a vehicle management system according to an embodiment of the present disclosure. Referring to FIG. 2, a vehicle management system 301 includes a plurality of relay devices 101 and a plurality of in-vehicle devices 202. The in-vehicle devices 202 are an example of a functional unit.

[0034] 2 , the vehicle management system 301 includes relay devices 101A, 101B, and 101C that are relay devices 101, and in-vehicle devices 202A, 202B, and 202C that are in-vehicle devices 202. The relay devices 101 and the in-vehicle devices 202 configure an in-vehicle network 401.

[0035] The in-vehicle device 202 is, for example, an in-vehicle ECU (Electronic Control Unit). Specifically, the in-vehicle device 202 is a TCU (Telematics Communication Unit), an engine ECU, an autonomous driving ECU, a body control ECU, a steering control ECU, a brake control ECU, etc. Note that the in-vehicle device 202 is not limited to an in-vehicle ECU, and may also be an OTA (Over The Air) master, a sensor, a navigation device, a human-machine interface, a camera, etc.

[0036] In an in-vehicle network 401 installed in a vehicle 1, an in-vehicle device 202 is connected to a relay device 101 via, for example, an Ethernet (registered trademark) cable 11.

[0037] More specifically, each relay device 101 includes a plurality of communication ports 51. The communication ports 51 are terminals to which, for example, Ethernet cables 11 can be connected. Each relay device 101 and each in-vehicle device 202 is connected to other relay devices 101 or in-vehicle devices 202 via the communication ports 51 and the Ethernet cables 11.

[0038] 2, on-board device 202A, on-board device 202B, and on-board device 202C are connected to relay device 101A, relay device 101B, and relay device 101C, respectively, via Ethernet cables 11A, 11B, and 11C, which are the Ethernet cable 11. Relay device 101A is connected to relay device 101B via Ethernet cable 11D, which is the Ethernet cable 11. Relay device 101B is connected to relay device 101C via Ethernet cable 11E, which is the Ethernet cable 11.

[0039] The relay device 101 is, for example, a switch device. More specifically, the relay device 101 relays information exchanged between the in-vehicle devices 202 connected via the Ethernet cable 11 in accordance with, for example, the Ethernet communication standard.

[0040] Each relay device 101 and each in-vehicle device 202 generates a frame including various information described later, and transmits it to another in-vehicle device 202 or another relay device 101 .

[0041] Each relay device 101 and each in-vehicle device 202 communicates with each other to provide various services in the in-vehicle network 401 in the vehicle 1 .

[0042] Specifically, the in-vehicle network 401 executes a lighting control service that controls the timing of turning on the headlights of the vehicle 1, a surrounding monitoring service that monitors the surroundings of the vehicle 1, and a software update service that updates various software used in the in-vehicle network 401 via OTA.

[0043] Note that the vehicle management system 301 is not limited to a configuration in which frames are relayed in accordance with the Ethernet communication standard, and may be configured to relay frames in accordance with a communication standard such as CAN (Controller Area Network), CAN FD (CAN with Flexible Data Rate), FlexRay (registered trademark), MOST (Media Oriented System Transport) (registered trademark), LIN (Local Interconnect Network), and CXPI (Clock Extension Peripheral Interface) (registered trademark).

[0044] Furthermore, the vehicle management system 301 is not limited to a configuration including a plurality of relay devices 101 , and may be a configuration including a single relay device 101 .

[0045] [Relay Device] Fig. 3 is a diagram illustrating an example of the configuration of a relay device according to an embodiment of the present disclosure. Fig. 3 illustrates the configuration of the relay device 101B illustrated in Fig. 2 .

[0046] 3, relay device 101B includes relay unit 21, detection unit 22, conversion unit 23, notification unit 24, management unit 25, setting unit 26, and storage unit 27. Some or all of relay unit 21, detection unit 22, conversion unit 23, notification unit 24, management unit 25, and setting unit 26 are realized by, for example, a processing circuit including one or more processors. Storage unit 27 is, for example, a non-volatile memory included in the processing circuit. Relay unit 21 is an example of an acquisition unit.

[0047] The relay unit 21 performs a relay process of relaying frames transmitted and received between the in-vehicle devices 202. More specifically, for example, the storage unit 27 stores an address table indicating the correspondence between the source MAC (Media Access Control) address and the destination MAC address included in the frame and the port number of the communication port 51.

[0048] When relay unit 21 receives a frame from in-vehicle device 202B or relay device 101A, 101C, relay unit 21 identifies the port number corresponding to the source MAC address and destination MAC address included in the received frame by referring to the address table in storage unit 27. Then, relay unit 21 transmits the frame to in-vehicle device 202B or relay device 101A, 101C connected to communication port 51 of the identified port number.

[0049] [Description of the Problem] In recent years, development of vehicles called SDVs (Software Defined Vehicles) has been progressing. Specifically, SDVs are vehicles that can dynamically change the configuration of their in-vehicle networks using SDN technology.

[0050] For example, an in-vehicle device 202 may be added to the in-vehicle network 401 shown in Fig. 2. Hereinafter, the in-vehicle network 401 including the in-vehicle device 202 newly added to the in-vehicle network 401 will also be referred to as a "new network."

[0051] 4 is a diagram illustrating an example of a configuration of a new network in a vehicle management system according to an embodiment of the present disclosure, in which a new in-vehicle device 202D is added to the in-vehicle network 401 illustrated in FIG.

[0052] 4, the in-vehicle device 202D is connected to the relay device 101B via, for example, an Ethernet cable 11F, which is the Ethernet cable 11. When the in-vehicle device 202D is added in this way, it is necessary to change the settings of the in-vehicle network 401. The IEEE 802.1Qcc standard defines a "fully centralized model" as an example of a method for dynamically changing the settings.

[0053] FIG. 5 is a diagram showing a fully centralized model defined in the IEEE 802.1Qcc standard.

[0054] 5, a Bridge 601 is a device that relays messages exchanged between a Talker 602 and a Listener 603. The Talker 602 is a device that transmits messages. The Listener 603 is a device that receives messages. The CUC 605 configures each of the Talker 602 and the Listener 603.

[0055] The CNC 604 configures the Bridge 601. Specifically, the CUC 605 creates UNI information required for the configuration performed by the CNC 604 by collecting information for identifying each of the Talker 602 and the Listener 603, and information indicating the contents of messages from the Talker 602 and the Listener 603.

[0056] Then, the CUC 605 notifies the CNC 604 of the created UNI information. The CNC 604 creates management information for changing the settings of the Bridge 601. Specifically, for example, the CNC 604 creates the management information based on the UNI information notified by the CUC 605.

[0057] The CNC 604 then performs the process indicated by arrow F3, specifically, creates a frame that complies with a protocol such as SNMP (Simple Network Management Protocol) or NETCONF (Network Configuration Protocol), and transmits the created management information included in the frame to each Bridge 601. Each Bridge 601 changes various settings in accordance with the management information received from the CNC 604. Specifically, each Bridge 601 changes settings such as the allowable delay time for messages to be relayed in accordance with the management information.

[0058] The IEEE 802.1Qcc standard does not prescribe the process indicated by arrow F1, specifically, the process method by which the CUC 605 collects various information from the Talker 602 and the Listener 603. Furthermore, the IEEE 802.1Qcc standard does not prescribe the process indicated by arrow F2, that is, the process method by which the CUC 605 configures the Talker 602 and the Listener 603. Therefore, for example, a method is conceivable in which the Talker 602 and the Listener 603 transmit various information to the CUC 605 in response to a request from the CUC 605.

[0059] In the in-vehicle network 401 shown in FIG. 4, that is, the new network, the in-vehicle devices 202A, 202B, 202C, and 202D correspond to the Talker 602 or the Listener 603.

[0060] In the transitional period of the spread of SDV, there is a possibility that the in-vehicle devices 202 constituting the in-vehicle network 401 may include an in-vehicle device 202 that cannot respond to a request from the CUC 605. In this case, there is a problem that it is difficult to change the settings of the in-vehicle network 401.

[0061] Therefore, the vehicle management system 301 according to the embodiment of the present disclosure solves the above problem by the following configuration and operation.

[0062] [Network Information] Referring again to FIGS. 1 and 2, the server 151 holds network information N1 relating to the in-vehicle network 401.

[0063] FIG. 6 is a diagram illustrating an example of network information held by a server according to an embodiment of the present disclosure.

[0064] 6, for example, network information N1 includes information on services provided in in-vehicle network 401. Here, for example, network information N1 includes information on services provided in the new network shown in FIG.

[0065] More specifically, for example, the network information N1 indicates the correspondence between a service and discrimination information (hereinafter also referred to as a "discrimination flag") indicating whether the service is provided in the in-vehicle network 401.

[0066] Specifically, the "valid" in the "determination flag" indicates that the service registered in the network information N1 is provided in the new network. The "invalid" in the "determination flag" indicates that the service registered in the network information N1 is not provided in the new network.

[0067] In the network information N1 shown in FIG. 6, the discrimination flags for "service A" and "service C" are "enabled," and the discrimination flag for "service B" is "disabled."

[0068] The network information N1 is registered by the user in a storage unit (not shown) of the server 151, for example.

[0069] 1 and 2, the in-vehicle device 202B is a TCU, and will be hereinafter also referred to as a TCU 202B.

[0070] The TCU 202B is capable of communicating with the server 151. The TCU 202B is capable of communicating with the server 151 via the wireless base station device 161, for example.

[0071] More specifically, the TCU 202B is capable of wireless communication with the wireless base station device 161 in accordance with a communication standard such as LTE (Long Term Evolution) (registered trademark) or 5G.

[0072] Specifically, when the wireless base station device 161 receives an IP packet from the server 151 via the external network 170, the wireless base station device 161 transmits the received IP packet in a wireless signal to the TCU 202B.

[0073] For example, when TCU202B receives a radio signal including an IP packet from server 151 from radio base station device 161, it acquires the IP packet from the received radio signal, stores the acquired IP packet in a frame, and transmits it to relay device 101B.

[0074] Here, when the user registers network information N1 in its storage unit, server 151 creates an IP packet that includes network information N1 and includes its own IP address and the IP address of relay device 101B as the source IP address and destination IP address, respectively. Server 151 then transmits the created IP packet to relay device 101B in vehicle management system 301 via external network 170 and wireless base station device 161. Note that network information N1 may be updated by the user. In this case, when the network information N1 in the storage unit is updated, server 151 transmits the updated network information N1 to relay device 101B.

[0075] [Relay Device] Referring again to FIGS. 1 to 3, in relay device 101B, relay unit 21 acquires network information N1.

[0076] More specifically, for example, the relay unit 21 acquires the network information N1 from the server 151. Specifically, for example, the relay unit 21 receives the network information N1 from the server 151 via the TCU 202B. Then, the relay unit 21 outputs the received network information N1 to the detection unit 22.

[0077] For example, the detection unit 22 detects a change in the configuration of the in-vehicle network 401. More specifically, for example, the detection unit 22 receives the network information N1 from the relay unit 21 and thereby recognizes that a change in the configuration of the in-vehicle network 401 has occurred.

[0078] When the detection unit 22 detects a change in the configuration of the in-vehicle network 401, the detection unit 22 outputs a service notification indicating services whose discrimination flags are "enabled" in the network information N1 received from the relay unit 21 to the conversion unit 23. Here, as described above, in the network information N1 shown in FIG. 6, the services whose discrimination flags are "enabled" are "service A" and "service C." Therefore, the services indicated in the service notification are service A and service C.

[0079] Referring again to FIGS. 3 and 5, in this example, the management unit 25 and the setting unit 26 have the functions of the CUC 605 and the CNC 604, respectively.

[0080] (Conversion Unit) The conversion unit 23 performs a conversion process to convert the network information N1 acquired by the relay unit 21 into setting information required for setting by the CNC 604 in accordance with the IEEE802.1Qcc standard.

[0081] For example, the setting information is UNI information used between the CUC 605 and the CNC 604 .

[0082] FIG. 7 is a diagram showing the contents of the UNI information defined in IEEE 802.1Qcc.

[0083] Referring to FIG. 7, the UNI information includes a message ID (Identifier), a message rank, an end station I / F, a data frame specification, and a traffic specification as parameters.

[0084] The message ID indicates identification information for identifying UNI information. The message rank indicates the importance of the message. The end station I / F (interface) indicates the I / F between the Talker 602 and the Listener 603, for example, the port number of the communication port 51 to which the Listener 603 is connected. The data frame specifications indicate the source MAC address, the destination MAC address, etc. The traffic specifications indicate the interval at which messages are sent, the frame size, etc.

[0085] 7, the message ID, message rank, data frame specification, and traffic specification are information relating to the Talker 602. The message ID and end station I / F are information relating to the Listener 603.

[0086] FIG. 8 is a diagram illustrating an example of a correspondence table stored in a relay device according to an embodiment of the present disclosure.

[0087] 3 and 8, the storage unit 27 stores a correspondence table Tb1 indicating the correspondence between services and UNI information, and a plurality of pieces of UNI information. The correspondence table Tb1 is an example of correspondence information.

[0088] In the correspondence table Tb1 shown in Fig. 8, the UNI information corresponding to service A is UNI information U1, the UNI information corresponding to service B is UNI information U2, and the UNI information corresponding to service C is UNI information U3.

[0089] At least one of the message ID, message rank, end station I / F, data frame specification, and traffic specification shown in FIG. 7 is different between the UNI information U1, UNI information U2, and UNI information U3.

[0090] For example, the converter 23 performs the conversion process using the correspondence table Tb1. More specifically, for example, when the converter 23 receives a service notification from the detector 22, the converter 23 reads the correspondence table Tb1 from the storage unit 27. Then, the converter 23 identifies the UNI information corresponding to the service indicated by the service notification by referring to the correspondence table Tb1. That is, in the conversion process, the converter 23 acquires the UNI information corresponding to the service that is valid in the in-vehicle network 401.

[0091] As described above, the services indicated by the service information from the detection unit 22 are service A and service C. Therefore, the conversion unit 23 identifies the UNI information U1 and UNI information U3 as the UNI information corresponding to service A and service C, respectively, indicated by the service notification received from the detection unit 22.

[0092] (Notification Unit) Referring again to FIGS. 3 and 4, notification unit 24 performs notification processing to notify CUC 605 conforming to the IEEE802.1Qcc standard, that is, management unit 25, of the setting information converted by conversion unit 23.

[0093] For example, when the detection unit 22 detects a change in the configuration of the in-vehicle network 401, the notification unit 24 performs a notification process.

[0094] Specifically, for example, when the converter 23 performs the conversion process in response to receiving a service notification from the detector 22, the converter 23 acquires the UNI information identified in the conversion process from the storage unit 27. Then, the converter 23 outputs the acquired UNI information to the notifier 24.

[0095] When the notification unit 24 receives the UNI information from the conversion unit 23 , it outputs the UNI information to the management unit 25 , which corresponds to the CUC 605 .

[0096] The management unit 25, functioning as the CUC 605, outputs the UNI information notified by the notification unit 24 to the setting unit 26, which corresponds to the CNC 604. Furthermore, the management unit 25, functioning as the CUC 605, performs a transmission process S1 in which the management unit 25 transmits the UNI information to each in-vehicle device 202, which corresponds to the Talker 602 or the Listener 603 shown in Fig. 5, via the relay unit 21. The transmission process S1 is indicated by an arrow F2 in Fig. 5.

[0097] When each in-vehicle device 202 receives the UNI information from the relay device 101B, it changes various settings in accordance with the UNI information.

[0098] (Setting Unit) For example, the setting unit 26 serves as the CNC 604 and creates management information for changing various settings of each relay device 101 .

[0099] Specifically, for example, when setting unit 26 receives UNI information from management unit 25, setting unit 26 creates management information based on the UNI information as CNC 604. Then, setting unit 26 changes various settings of its own relay device 101B in accordance with the created management information. When the setting changes are completed, setting unit 26 outputs a completion response to management unit 25.

[0100] After creating the management information, the setting unit 26 performs a transmission process S2 as the CNC 604 to transmit the management information to the relay devices 101A and 101C via the relay unit 21. The transmission process S2 is indicated by an arrow F3 in FIG.

[0101] When the relay devices 101A and 101C receive the management information from the relay device 101B, they change various settings in accordance with the management information.

[0102] As described above, the method of processing by the CUC 605 to collect various types of information from the Talker 602 and the Listener 603, as indicated by the arrow F1 in FIG. 5, is not specified in IEEE 802.1Qcc.

[0103] On the other hand, in the vehicle management system 301, the relay unit 21 acquires the network information N1 from the server 151, and the notification unit 24 performs the notification process, so that the setting unit 26 can change various settings of the relay device 101B without collecting various information required for generating UNI information from the Talker 602 and the Listener 603. Also, the management unit 25 performs the transmission process S1, and the setting unit 26 performs the transmission process S2, so that various settings can be changed in each in-vehicle device 202 and the relay devices 101A and 101C. Therefore, the setting change of the in-vehicle network 401 can be more reliably performed.

[0104] [Operation Flow] FIG. 9 is a flowchart defining an operation procedure when a relay device according to an embodiment of the present disclosure performs conversion processing.

[0105] Referring to FIG. 9, first, the relay device 101B waits for the arrival of the network information N1 from the server 151 (NO in step S101), and upon receiving the network information N1 (YES in step S101), detects a change in the configuration of the in-vehicle network 401 (step S102).

[0106] Next, the relay device 101B performs a conversion process to convert the network information N1 from the server 151 into UNI information required for setting by the CNC 604 in accordance with the IEEE 802.1Qcc standard. For example, as described above, in the relay device 101B, the conversion unit 23 performs the conversion process using the correspondence table Tb1 (step S103).

[0107] Next, the relay device 101B performs a notification process to notify the converted UNI information to the CUC 605 that complies with the IEEE 802.1Qcc standard. For example, as described above, in the relay device 101B, the notification unit 24 notifies the management unit 25, which corresponds to the CUC 605, of the UNI information converted by the conversion unit 23 (step S104).

[0108] Next, the management unit 25, functioning as the CUC 605, outputs the UNI information from the notification unit 24 to the setting unit 26, which corresponds to the CNC 604 (step S105).

[0109] Next, the setting unit 26, as the CNC 604, creates management information for changing various settings of each relay device 101. For example, as described above, the setting unit 26 creates the management information based on the UNI information received from the management unit 25 (step S106).

[0110] Next, the setting unit 26 changes various settings of its own relay device 101B in accordance with the created management information (step S107).

[0111] Next, the setting unit 26, functioning as the CNC 604, transmits the created management information to the relay devices 101A and 101C via the relay unit 21 (step S108).

[0112] Next, the management unit 25, as the CUC 605, transmits the UNI information to each in-vehicle device 202 via the relay unit 21 (step S109), and waits for the arrival of new network information N1 (NO in step S101). Note that the processing from step S107 to step S109 may be executed in a reverse order or in parallel.

[0113] FIG. 10 is a diagram illustrating an example of a processing sequence of the server, the relay device, and the in-vehicle device in the communication system according to the embodiment of the present disclosure.

[0114] 10 , first, server 151 transmits network information N1 to relay device 101B. For example, as described above, when a user registers network information N1 in its own storage unit, server 151 transmits network information N1 to relay device 101B via external network 170 and wireless base station device 161 (step S201).

[0115] Next, the relay device 101B receives the network information N1 from the server 151 and thereby detects a change in the configuration of the in-vehicle network 401 (step S202).

[0116] Next, the relay device 101B performs a conversion process to convert the network information N1 received from the server 151 into UNI information required for the setting performed by the CNC 604. For example, as described above, the conversion unit 23 in the relay device 101B performs the conversion process using the correspondence table Tb1 (step S203).

[0117] Next, in the relay device 101B, the conversion unit 23 performs a notification process to notify the management unit 25, which corresponds to the CUC 605, of the converted UNI information (step S204).

[0118] Next, in the relay device 101B, the management unit 25 functions as the CUC 605 and outputs the UNI information to the setting unit 26, which corresponds to the CNC 604 (step S205).

[0119] Next, the setting unit 26, as the CNC 604, creates management information for changing various settings of each relay device 101. For example, as described above, the setting unit 26 creates the management information based on the UNI information received from the management unit 25 (step S206).

[0120] Next, the setting unit 26 changes various settings of the relay device 101B itself in accordance with the created management information (step S207).

[0121] Next, the setting unit 26, functioning as the CNC 604, transmits the created management information to the relay devices 101A and 101C (step S208).

[0122] Next, the management unit 25 transmits the UNI information to each in-vehicle device 202 as the CUC 605 (step S209). Note that the processing from step S207 to step S209 may be executed in a different order or in parallel.

[0123] Next, the relay devices 101A and 101C change various settings in accordance with the management information received from the relay device 101B (step S210).

[0124] Furthermore, each in-vehicle device 202 changes various settings in accordance with the UNI information received from the relay device 101B (step S211).

[0125] In the vehicle management system 301 according to the embodiment of the present disclosure, the relay device 101B is configured to acquire the network information N1 from the server 151, but this is not limited to this. When an in-vehicle device 202 is added to the in-vehicle network 401 after the vehicle 1 is shipped, a dealer or the like may register the network information N1 in the storage unit 27 of the relay device 101B. In this case, in the relay device 101B, the relay unit 21 acquires the network information N1 from the storage unit 27.

[0126] In the vehicle management system 301 according to the embodiment of the present disclosure, the relay device 101B is configured to change the settings of the in-vehicle network 401 when an in-vehicle device 202 is added to the in-vehicle network 401, but this is not limiting. The relay device 101B may also be configured to change the settings when another event occurs, such as when an in-vehicle device 202 is removed from the in-vehicle network 401 or when various software used in the in-vehicle network 401 is updated.

[0127] In the vehicle management system 301 according to the embodiment of the present disclosure, the converter 23 in the relay device 101B is configured to convert the network information N1 from the server 151 into UNI information defined in the IEEE 802.1Qcc standard during the conversion process. However, this is not limiting. The converter 23 may also be configured to convert the network information N1 into related information that is the source of the UNI information during the conversion process. In this case, the converter 23 converts the related information into UNI information in, for example, a unit other than the converter 23.

[0128] In the vehicle management system 301 according to the embodiment of the present disclosure, the converter 23 in the relay device 101B is configured to perform a conversion process of converting the network information N1 into UNI information using the correspondence table Tb1, but this is not limited to this. The converter 23 may be configured to create UNI information based on the contents of the network information N1 from the server 151 without using the correspondence table Tb1.

[0129] [Modification 1] FIG. 11 is a diagram illustrating an example of network information held by modification 1 of the server according to the embodiment of the present disclosure.

[0130] 11, in the first modification, the server 151 holds network information N2 instead of the network information N1 shown in FIG.

[0131] For example, the network information N2 includes information about the in-vehicle device 202. Specifically, for example, the network information N2 indicates the correspondence between identification information for identifying the in-vehicle device 202 (hereinafter also referred to as "device ID") and the version of software (hereinafter also referred to as "version information") installed in the in-vehicle device 202. The device ID is an ID unique to each in-vehicle device 202.

[0132] In the network information N2 shown in Figure 11, the version of the software installed in the in-vehicle device 202 with device ID "D001" is "1.00". The version of the software installed in the in-vehicle device 202 with device ID "D002" is "2.00". The version of the software installed in the in-vehicle device 202 with device ID "D003" is "1.01". In other words, the network information N2 includes a device ID group consisting of multiple device IDs and a version information group consisting of multiple version information.

[0133] The network information N2 is not limited to a configuration that indicates the correspondence between the device ID and the version information, but may be a configuration that indicates the correspondence between the device ID and the hardware information of the in-vehicle device 202, for example.

[0134] 1 and 4, when the user registers network information N2 in its storage unit, server 151 creates an IP packet that includes network information N2 and also includes its own IP address and the IP address of relay device 101B as the source IP address and destination IP address, respectively. Server 151 then transmits the created IP packet to relay device 101B in vehicle management system 301 via external network 170 and wireless base station device 161.

[0135] Referring back to FIG. 3, in relay device 101B, upon receiving network information N2 from server 151, relay unit 21 outputs the received network information N2 to detection unit 22.

[0136] Upon receiving the network information N2 from the relay unit 21, the detection unit 22 detects a change in the configuration of the in-vehicle network 401. Then, the detection unit 22 outputs the network information N2 received from the relay unit 21 to the conversion unit 23.

[0137] For example, the storage unit 27 stores a management table showing the correspondence between device ID groups and version information groups and UNI information.

[0138] When the conversion unit 23 receives the network information N2 from the detection unit 22, it reads the management table in the storage unit 27. Then, by referring to the management table, the conversion unit 23 identifies the UNI information corresponding to the device ID group and the version information group included in the network information N2.

[0139] For example, the storage unit 27 further stores a plurality of pieces of UNI information, which differ from each other in at least one of the message ID, message rank, end station I / F, data frame specification, and traffic specification shown in FIG.

[0140] When the conversion unit 23 identifies the UNI information, it acquires the UNI information from the storage unit 27. Then, the conversion unit 23 outputs the acquired UNI information to the notification unit 24.

[0141] [Modification 2] In the relay device 101B, the notification unit 24 is configured to notify the management unit 25 corresponding to the CUC 605 of the setting information when the detection unit 22 detects a change in the configuration of the in-vehicle network 401. However, this is not limited to this. The notification unit 24 may be configured to perform notification processing when the management unit 25 requests setting information.

[0142] 12 is a diagram illustrating a configuration of a relay device according to a second modification of the present disclosure. Referring to FIG. 12, in the second modification, a relay device 101B includes a relay unit 211 and a management unit 251 instead of the relay unit 21 and the management unit 25 shown in FIG. 3, and does not include the detection unit 22 shown in FIG. 3.

[0143] The management unit 251 detects the addition of an in-vehicle device 202 to the in-vehicle network 401. In this example, the management unit 251 detects the addition of an in-vehicle device 202D shown in FIG.

[0144] More specifically, for example, when the in-vehicle device 202D is connected to the communication port 51 of the relay device 101B, the in-vehicle device 202D transmits connection request information for requesting a communication connection in the in-vehicle network 401 to the relay device 101B.

[0145] When the management unit 251 receives the connection request information from the in-vehicle device 202D via the relay unit 211, the management unit 251 performs authentication processing for the in-vehicle device 202D using the ID and authentication password included in the connection request information.

[0146] For example, when the management unit 251 has successfully authenticated the in-vehicle device 202D, the management unit 251 transmits authentication success information indicating that the authentication has been successful to the in-vehicle device 202D via the relay unit 211.

[0147] Furthermore, for example, when the management unit 251 has successfully authenticated the in-vehicle device 202D, it outputs, as the CUC 605, request information R1 for requesting setting information to the notification unit 24.

[0148] The management unit 251 may be configured to periodically broadcast a search message via the relay unit 211 to detect the addition of an in-vehicle device 202. In this case, the in-vehicle device 202 added to the in-vehicle network 401 receives the search message and transmits connection request information in response to the received search message.

[0149] For example, when the notification unit 24 receives request information R1 from the CUC 605, that is, the management unit 251, the notification unit 24 performs notification processing to notify the management unit 251 of the setting information.

[0150] More specifically, for example, when the notification unit 24 receives request information R1 from the management unit 251, the notification unit 24 outputs request information R2 for requesting network information N1 to the relay unit 211.

[0151] For example, the storage unit 27 further stores the vehicle ID of the vehicle 1 in which its own relay device 101B is installed.

[0152] When the relay unit 211 receives the request information R2 from the notification unit, the relay unit 211 includes the vehicle ID stored in the memory unit 27 in the request information R2 and transmits the information to the server 151 via the TCU 202B.

[0153] For example, the storage unit in the server 151 stores the network information N1 for each vehicle ID.

[0154] When the server 151 receives the request information R2 from the relay device 101B, the server 151 retrieves the network information N1 corresponding to the vehicle ID included in the received request information R2 from its own storage unit. Then, the server 151 transmits the retrieved network information N1 to the relay device 101B via the external network 170 and the wireless base station device 161.

[0155] In the relay device 101B, the conversion unit 23 performs a conversion process to convert the network information N1 from the server 151 into setting information required for the setting performed by the CNC 604.

[0156] More specifically, for example, when the relay unit 211 receives the network information N1 from the server 151, the relay unit 211 outputs to the conversion unit 23 a service notification indicating the services whose determination flags are "enabled" in the received network information N1.

[0157] When the conversion unit 23 receives a service notification from the relay unit 211, the conversion unit 23 performs the above-mentioned conversion process using the correspondence table Tb1 shown in Fig. 8. Then, the conversion unit 23 outputs the UNI information converted in the conversion process to the notification unit 24.

[0158] When the notification unit 24 receives the UNI information from the conversion unit 23 , it notifies the management unit 251 , which corresponds to the CUC 605 , of the UNI information.

[0159] [Variation 3] In the vehicle management system 301 according to the embodiment of the present disclosure, the relay device 101B is configured to include the detection unit 22, the conversion unit 23, the notification unit 24, the management unit 25 corresponding to the CUC 605, and the setting unit 26 corresponding to the CNC 604. However, this is not limiting. A device other than the relay device 101B in the in-vehicle network 401 may be configured to include some or all of the detection unit 22, the conversion unit 23, the notification unit 24, the management unit 25, and the setting unit 26.

[0160] 13 is a diagram illustrating a configuration of a relay device according to a third modification of the present disclosure. Referring to FIG. 13, in the third modification, a relay device 101B includes a relay unit 21, a detection unit 22, and a storage unit 27. In this example, the relay device 101B does not include the conversion unit 23, the notification unit 24, the management unit 25, and the setting unit 26 illustrated in FIG. 3 .

[0161] In the relay device 101B, when the detection unit 22 receives network information N1 from the relay unit 21 and recognizes that there has been a change in the configuration of the in-vehicle network 401, it transmits the network information N1 to the in-vehicle device 202D via the relay unit 21.

[0162] 14 is a diagram illustrating a configuration of a third variation of an in-vehicle device according to an embodiment of the present disclosure. Referring to FIG. 14 , an in-vehicle device 202D includes a communication unit 31, a conversion unit 23, a notification unit 24, a management unit 25, a setting unit 26, and a storage unit 32. Some or all of the communication unit 31, the conversion unit 23, the notification unit 24, the management unit 25, and the setting unit 26 are implemented by, for example, a processing circuit including one or more processors. The storage unit 32 is, for example, a non-volatile memory included in the processing circuit.

[0163] When the communication unit 31 receives the network information N1 from the relay device 101B, the communication unit 31 outputs the received network information N1 to the conversion unit 23 .

[0164] The conversion unit 23 performs the above-described conversion process to convert the network information N1 from the relay device 101B into UNI information.

[0165] 8 . Upon receiving the network information N1 from the communication unit 31, the conversion unit 23 converts the network information N1 into UNI information by referring to the correspondence table Tb1 in the storage unit 32. The conversion unit 23 then outputs the UNI information to the notification unit 24.

[0166] Upon receiving the UNI information from the conversion unit 23, the notification unit 24 performs notification processing to notify the management unit 25, which corresponds to the CUC 605, of the UNI information.

[0167] For example, when the management unit 25 receives the UNI information from the management unit 25, the management unit 25 acts as the CUC 605 and changes various settings of its own in-vehicle device 202D.

[0168] Furthermore, for example, the management unit 25, as the CUC 605, transmits the UNI information notified by the notification unit 24 via the communication unit 31 to another in-vehicle unit 202 different from the own in-vehicle unit 202D.

[0169] When the other in-vehicle unit 202 receives the UNI information from the in-vehicle unit 202D, it changes various settings in accordance with the UNI information.

[0170] Furthermore, for example, the management unit 25 serves as the CUC 605 and outputs the UNI information notified by the notification unit 24 to the setting unit 26 which corresponds to the CNC 604 .

[0171] For example, when setting unit 26 receives UNI information from management unit 25, setting unit 26 creates the above-mentioned management information based on the UNI information as CNC 604. Then, setting unit 26, as CNC 604, performs a transmission process to transmit the created management information to each relay device 101 via communication unit 31. When the transmission process is completed, setting unit 26 outputs a completion response to management unit 25.

[0172] When each relay device 101 receives the management information from the in-vehicle device 202D, it changes various settings in accordance with the received management information.

[0173] Note that some or all of the detection unit 22, conversion unit 23, notification unit 24, management unit 25, and setting unit 26 may be provided in an external device outside the vehicle 1, for example, in a server 151 shown in FIG. 1 . In this case, the vehicle management system 301 includes the server 151.

[0174] The above-described embodiments should be considered to be illustrative in all respects and not restrictive. The scope of the present invention is defined by the claims, not by the above description, and is intended to include all modifications within the meaning and scope of the claims.

[0175] Each process (each function) in the above-described embodiments is realized by a processing circuit including one or more processors. The processing circuit may be configured as an integrated circuit or the like that combines one or more memories, various analog circuits, and various digital circuits in addition to the one or more processors. The one or more memories store programs (instructions) that cause the one or more processors to execute each of the processes. The one or more processors may execute each of the processes according to the program read from the one or more memories, or may execute each of the processes according to a logic circuit designed in advance to execute each of the processes. The processor may be any of various processors suitable for computer control, such as a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), a DSP (Digital Signal Processor), an FPGA (Field Programmable Gate Array), and an ASIC (Application Specific Integrated Circuit). Note that the physically separated processors may cooperate with each other to execute the processes. For example, the processors installed in the physically separated computers may cooperate with each other via a network such as a LAN (Local Area Network), a WAN (Wide Area Network), or the Internet to execute the processes. The program may be installed into the memory from an external server device or the like via the network, or may be distributed in a state stored on a recording medium such as a CD-ROM (Compact Disc Read Only Memory), a DVD-ROM (Digital Versatile Disc Read Only Memory), or a semiconductor memory, and then installed into the memory from the recording medium.

[0176] The above description includes the following additional features: [Supplementary Note 1] A vehicle management system comprising: an acquisition unit that acquires network information related to an in-vehicle network in a vehicle; a conversion unit that performs a conversion process to convert the network information acquired by the acquisition unit into setting information required for setting by a Centralized Network Configuration that complies with the IEEE 802.1Qcc standard; and a notification unit that performs a notification process to notify a Centralized User Configuration that complies with the IEEE 802.1Qcc standard of the setting information converted by the conversion unit, wherein the network information indicates a correspondence relationship between a service provided in the in-vehicle network and determination information that indicates whether the service is valid in the in-vehicle network, and the conversion unit acquires the setting information corresponding to the service that is valid in the in-vehicle network in the conversion process.

[0177] [Supplementary Note 2] A vehicle management system comprising a processing circuit, wherein the processing circuit acquires network information related to an in-vehicle network in a vehicle, performs a conversion process to convert the acquired network information into setting information required for setting performed by a Centralized Network Configuration conforming to the IEEE802.1Qcc standard, and performs a notification process to notify a Centralized User Configuration conforming to the IEEE802.1Qcc standard of the converted setting information.

[0178] [Supplementary Note 3] A vehicle management program used in a vehicle management system, causing a computer to function as: an acquisition unit that acquires network information related to an in-vehicle network in a vehicle; a conversion unit that performs conversion processing to convert the network information acquired by the acquisition unit into setting information required for setting by a Centralized Network Configuration that complies with the IEEE802.1Qcc standard; and a notification unit that performs notification processing to notify a Centralized User Configuration that complies with the IEEE802.1Qcc standard of the setting information converted by the conversion unit.

[0179] 1 Vehicle 11, 11A, 11B, 11C, 11D, 11E, 11F Ethernet cable 21, 211 Relay unit 22 Detection unit 23 Conversion unit 24 Notification unit 25, 251 Management unit 26 Setting unit 27, 32 Storage unit 31 Communication unit 51, 51A, 51B, 51C, 51D Communication port 101, 101A, 101B, 101C Relay device 151 Server 161 Wireless base station device 170 External network 202, 202A, 202B, 202C, 202D In-vehicle device 301 Vehicle management system 401 In-vehicle network 501 Communication system 601 Bridge 602 Talker 603 Listener 604 CNC 605 CUC N1, N2 network information Tb1 correspondence table

Claims

1. A vehicle management system comprising: an acquisition unit that acquires network information related to an in-vehicle network in a vehicle; a conversion unit that performs a conversion process to convert the network information acquired by the acquisition unit into setting information required for settings performed by a Centralized Network Configuration that complies with the IEEE 802.1Qcc standard; and a notification unit that performs a notification process to notify a Centralized User Configuration that complies with the IEEE 802.1Qcc standard of the setting information converted by the conversion unit.

2. The vehicle management system according to claim 1, wherein the network information includes information on services provided in the in-vehicle network.

3. A vehicle management system according to claim 1 or claim 2, wherein the in-vehicle network includes a functional unit that provides a service in the in-vehicle network, and the network information includes information about the functional unit.

4. A vehicle management system according to any one of claims 1 to 3, wherein the acquisition unit acquires the network information from an external device outside the vehicle.

5. The vehicle management system according to any one of claims 1 to 4, wherein the setting information is User Network Interface information used between the Centralized User Configuration and the Centralized Network Configuration.

6. The vehicle management system according to claim 5, wherein the network information includes information on services provided in the in-vehicle network, and the conversion unit performs the conversion process using correspondence information indicating a correspondence relationship between the services and the User Network Interface information.

7. The vehicle management system according to claim 1, wherein the notification unit performs the notification process when request information for requesting the setting information is received from the Centralized User Configuration.

8. The vehicle management system according to any one of claims 1 to 6, further comprising a detection unit that detects a change in the configuration of the in-vehicle network, and the notification unit performs the notification processing when the change is detected by the detection unit.

9. A vehicle management method in a vehicle management system, comprising: a step of acquiring network information related to an in-vehicle network; a step of performing a conversion process of converting the acquired network information into setting information required for settings performed by a Centralized Network Configuration conforming to the IEEE802.1Qcc standard; and a step of performing a notification process of notifying a Centralized User Configuration conforming to the IEEE802.1Qcc standard of the converted setting information.

Images