Vehicle management system and vehicle management method

Abstract

To perform a setting change in an in-vehicle network with improved reliability.SOLUTION: A vehicle management system comprises: an acquisition section that acquires network information related to an in-vehicle network of a vehicle; a conversion section that performs a conversion process to convert the network information acquired by the acquisition section into setting information required a configuration performed by a Centralized Network Configuration in accordance with an IEEE 802.1Qcc standard; and a notification section that performs a notification process to notify a Centralized User Configuration, also in accordance with the IEEE 802.1Qcc standard, of the setting information converted by the conversion section.SELECTED DRAWING: Figure 3

Description

Technical Field

[0001] The present disclosure relates to a vehicle management system and a vehicle management method.

Background Art

[0002] Techniques for changing the configuration of an in-vehicle network have been developed. For example, Patent Document 1 (International Publication No. 2020 / 145334) discloses the following technique. That is, a vehicle control device controls a plurality of repeaters based on a control scenario in which the state of a vehicle in which a vehicle network composed of a plurality of repeaters is built inside is associated with the control content set for each of the plurality of repeaters.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In recent years, the development of vehicles capable of dynamically changing the configuration of an in-vehicle network using SDN (Software Defined Network) technology has been underway. Here, the IEEE (registered trademark) 802.1Qcc standard defines a method for dynamically performing such configuration changes.

[0005] When dynamically changing the configuration of an in-vehicle network in accordance with the IEEE 802.1Qcc standard, there is a possibility that a device that cannot communicate in accordance with the standard is included in the in-vehicle network. In this case, there is a problem that it is difficult to change the configuration of the in-vehicle network.

[0006] The present disclosure has been made to solve the above-described problems, and an object thereof is to provide a vehicle management system and a vehicle management method capable of more reliably changing the settings of an in-vehicle network.

Means for Solving the Problems

[0007] The vehicle management system of the present disclosure includes an acquisition unit that acquires network information regarding an in-vehicle network in a vehicle, a conversion unit that performs a conversion process of converting the network information acquired by the acquisition unit into setting information necessary for settings performed by Centralized Network Configuration according to the IEEE802.1Qcc standard, and a notification unit that performs a notification process of notifying the setting information converted by the conversion unit to Centralized User Configuration according to the IEEE802.1Qcc standard.

[0008] One aspect of the present disclosure can 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 steps of such characteristic processing. Further, one aspect of the present disclosure can be realized as a semiconductor integrated circuit that realizes part or all of the vehicle management system.

Effects of the Invention

[0009] According to the present disclosure, it is possible to more reliably change the settings of the in-vehicle network.

Brief Description of the Drawings

[0010]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

[0011] First, the content of the embodiment of the present disclosure will be listed and described. (1) The 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 of converting the network information acquired by the acquisition unit into setting information necessary for settings performed by Centralized Network Configuration according to the IEEE802.1Qcc standard, and a notification unit that performs a notification process of notifying the setting information converted by the conversion unit to Centralized User Configuration according to the IEEE802.1Qcc standard.

[0012] In the IEEE802.1Qcc standard, a method for Centralized Network Configuration (hereinafter also referred to as "CNC") to perform settings in a network is defined. In this method, Centralized User Configuration (hereinafter also referred to as "CUC") collects various information indicating the content of messages and the like from devices such as the transmission source of the message, and creates setting information necessary for the settings performed by CNC based on the various information. As described above, by converting the acquired information related to the in-vehicle network into setting information and notifying the setting information to CUC, for example, even when a device such as the transmission source of the above message does not have a function to communicate with CUC according to the above standard, the setting information can be provided to CNC, so that the setting of the in-vehicle network can be changed according to the setting information. Therefore, the setting change of the in-vehicle network can be performed more reliably.

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

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

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

[0016] With such a configuration, the acquired network information can be converted into appropriate setting information according to the information of the functional unit constituting the in-vehicle network.

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

[0018] With such a configuration, information regarding the in-vehicle network can be easily acquired.

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

[0020] In the IEEE802.1Qcc standard, it is stipulated that the CNC performs the setting of 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, in the CNC, the process of converting the setting information given from the CUC into UNI information becomes unnecessary, so the setting change of the relay device can be easily performed.

[0021] (6) In any one of the above (1) to (5), the network information may include information of services provided in the in-vehicle network, and the conversion unit may perform the conversion process using correspondence information indicating the correspondence between the services and the User Network Interface information.

[0022] With such a configuration, information regarding the in-vehicle network can be easily converted into setting information.

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

[0024] With such a configuration, for example, when the CUC determines whether it is necessary to change the setting of the in-vehicle network in the CNC, the setting information can be more reliably notified to the CUC in response to a request from the CUC.

[0025] (8) In any one 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 when the change is detected by the detection unit, the notification unit may perform the notification process.

[0026] With such a configuration, it is possible to easily grasp the timing at which the setting information should be notified to the CUC.

[0027] (9) The vehicle management method according to an embodiment of the present disclosure is a vehicle management method in a vehicle management system, and includes a step of acquiring network information regarding an in-vehicle network in a vehicle, 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 the converted setting information to a Centralized User Configuration conforming to the IEEE802.1Qcc standard.

[0028] In the IEEE802.1Qcc standard, a method for the CNC to perform settings in the network is defined. In this method, the CUC collects various information indicating the content of the message and the like from the device of the message sender, etc., and creates setting information required for the settings performed by the CNC based on the various information. As described above, by converting the acquired information about the in-vehicle network into setting information and notifying the CUC of the setting information, for example, even when the device of the message sender, etc. does not have a function to communicate with the CUC according to the above standard, the setting information can be provided to the CNC, so that the setting of the in-vehicle network can be changed according to the setting information. Therefore, the setting change of the in-vehicle network can be performed more reliably.

[0029] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. In the drawings, the same or corresponding parts are denoted by the same reference numerals and their description will not be repeated. Also, at least a part of the embodiments described below may be arbitrarily combined.

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

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

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

[0033] In the example shown in FIG. 2, the vehicle management system 301 includes relay devices 101A, 101B, and 101C, which are relay devices 101, and in-vehicle devices 202A, 202B, and 202C, which are in-vehicle devices 202. The relay device 101 and the in-vehicle device 202 constitute an in-vehicle network 401.

[0034] 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 ECU for autonomous driving, a body control ECU, a steering control ECU, a brake control ECU, and the like. Note that the in-vehicle device 202 is not limited to an in-vehicle ECU, and may be an OTA (Over The Air) master, a sensor, a navigation device, a human machine interface, a camera, or the like.

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

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

[0037] In the example shown in FIG. 2, the in-vehicle devices 202A, 202B, and 202C are respectively connected to the relay devices 101A, 101B, and 101C via Ethernet cables 11A, 11B, and 11C, which are Ethernet cables 11. The relay device 101A is connected to the relay device 101B via an Ethernet cable 11D, which is an Ethernet cable 11. The relay device 101B is connected to the relay device 101C via an Ethernet cable 11E, which is an Ethernet cable 11.

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

[0039] Each relay device 101 and each in-vehicle device 202 generate a frame including various information described later and transmit it to another in-vehicle device 202 or another relay device 101.

[0040] Each relay device 101 and each in-vehicle device 202 provide various services in the in-vehicle network 401 in the vehicle 1 by communicating with each other.

[0041] Specifically, in the in-vehicle network 401, a lighting control service for controlling the lighting timing of the headlights of the vehicle 1, a peripheral monitoring service for monitoring the periphery of the vehicle 1, and a software update service for updating various software used in the in-vehicle network 401 by OTA are executed.

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

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

[0044] [Relay Device] FIG. 3 is a diagram showing an example of the configuration of the relay device according to an embodiment of the present disclosure. FIG. 3 shows the configuration of the relay device 101B shown in FIG. 2.

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

[0046] The relay unit 21 performs a relay process of relaying frames transmitted and received between in-vehicle devices 202. More specifically, for example, the storage unit 27 stores an address table showing 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.

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

[0048] [Description of the Problem] In recent years, the development of vehicles called SDV (Software Defined Vehicle) has been underway. Specifically, an SDV is a vehicle capable of dynamically changing the configuration settings of an in-vehicle network using SDN technology.

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

[0050] FIG. 4 is a diagram showing an example of the configuration of a new network in a vehicle management system according to an embodiment of the present disclosure. FIG. 4 shows the configuration of the in-vehicle network 401 in which an in-vehicle device 202D is newly added to the in-vehicle network 401 shown in FIG. 2.

[0051] Referring to FIG. 4, the in-vehicle device 202D is connected to the relay device 101B via an Ethernet cable 11F which is, for example, the Ethernet cable 11. Thus, when the in-vehicle device 202D is added, it is necessary to change the settings of the in-vehicle network 401. In the IEEE802.1Qcc standard, a "fully centralized model" is defined as an example of a method for dynamically performing such a setting change.

[0052] FIG. 5 is a diagram showing the fully centralized model defined in the IEEE802.1Qcc standard.

[0053] Referring to FIG. 5, Bridge 601 is a device that relays messages exchanged between Talker 602 and Listener 603. Talker 602 is the device that is the source of the message. Listener 603 is the device that is the destination of the message. CUC 605 performs the settings of each of Talker 602 and Listener 603.

[0054] CNC 604 performs the settings of Bridge 601. Specifically, CUC 605 creates the UNI information necessary for the settings performed by CNC 604 by collecting information for identifying each of Talker 602 and Listener 603, as well as information indicating the content of the messages from Talker 602 and Listener 603.

[0055] Then, CUC605 notifies the created UNI information to CNC604. CNC604 creates management information for changing the settings of Bridge601. Specifically, for example, CNC604 creates management information based on the UNI information notified from CUC605.

[0056] Then, CNC604 performs the process indicated by arrow F3, specifically, creates a frame conforming to a protocol such as SNMP (Simple Network Management Protocol) or NETCONF (Network Configuration Protocol), and includes the created management information in the frame and transmits it to each Bridge601. Each Bridge601 makes various setting changes according to the management information received from CNC604. Specifically, each Bridge601 changes the setting of the delay tolerance time of the message to be relayed, etc., according to the management information.

[0057] In the IEEE802.1Qcc standard, the method of the process indicated by arrow F1, specifically, the method by which CUC605 collects various information from Talker602 and Listener603, is not specified. Also, in the IEEE802.1Qcc standard, the method of the process indicated by arrow F2, the process by which CUC605 makes settings for Talker602 and Listener603, is not specified. Therefore, for example, a method in which Talker602 and Listener603 transmit various information to CUC605 in response to a request from CUC605 can be considered.

[0058] Here, in the in-vehicle network 401 shown in FIG. 4, that is, in the new network, the in-vehicle devices 202A, 202B, 202C, 202D correspond to Talker602 or Listener603.

[0059] In the transitional period of the popularization of SDVs, among the plurality of in-vehicle devices 202 that make up the in-vehicle network 401, there may be an in-vehicle device 202 that cannot respond to requests 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.

[0060] Therefore, in the vehicle management system 301 according to the embodiment of the present disclosure, the above problems are solved by the following configuration and operation.

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

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

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

[0064] More specifically, for example, the network information N1 shows 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.

[0065] Specifically, "valid" in the "discrimination flag" indicates that the service registered in the network information N1 is provided in the new network. "Invalid" in the "discrimination flag" indicates that the service registered in the network information N1 is not provided in the new network.

[0066] In the network information N1 shown in FIG. 6, the discrimination flags for "Service A" and "Service C" are "valid", and the discrimination flag for "Service B" is "invalid".

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

[0068] Referring again to FIGS. 1 and 2, here, the in-vehicle device 202B is a TCU. Hereinafter, the in-vehicle device 202B is also referred to as the TCU202B.

[0069] The TCU202B is capable of communicating with the server 151. The TCU202B can communicate with the server 151, for example, via the radio base station device 161.

[0070] More specifically, the TCU202B can perform wireless communication with the radio base station device 161 in accordance with a communication standard such as LTE (Long Term Evolution) (registered trademark) or 5G.

[0071] Specifically, when the radio base station device 161 receives an IP packet from the server 151 via the external network 170, the radio base station device 161 includes the received IP packet in a radio signal and transmits the radio signal to the TCU202B.

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

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

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

[0075] 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.

[0076] For example, the detection unit 22 detects a change in the configuration of the in-vehicle network 401. More specifically, for example, when the detection unit 22 receives the network information N1 from the relay unit 21, it recognizes that there has been a change in the configuration of the in-vehicle network 401.

[0077] When the detection unit 22 detects a change in the configuration of the in-vehicle network 401, it outputs a service notification indicating a service in which the discrimination flag is "valid" in the network information N1 received from the relay unit 23 to the conversion unit 23. Here, as described above, in the network information N1 shown in FIG. 6, the services in which the discrimination flag is "valid" are "Service A" and "Service C". Therefore, the services indicated by the service notification are Service A and Service C.

[0078] Referring again to FIGS. 3 and 5, in this example, the management unit 25 and the setting unit 26 respectively have the functions of the CUC605 and the CNC604.

[0079] (Conversion unit) The conversion unit 23 performs a conversion process of converting the network information N1 acquired by the relay unit 21 into setting information necessary for the settings performed by the CNC604 conforming to the IEEE802.1Qcc standard.

[0080] For example, the setting information is UNI information used between the CUC605 and the CNC604.

[0081] FIG. 7 is a diagram showing the content of the UNI information defined in IEEE802.1Qcc.

[0082] 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.

[0083] The message ID indicates identification information for identifying the UNI information. The message rank indicates the importance of the message. The end station I / F (interface) indicates the I / F between the Talker602 and the Listener603, for example, the port number of the communication port 51 to which the Listener603 is connected. The data frame specification indicates the source MAC address, the destination MAC address, etc. The traffic specification indicates the interval for transmitting the message, the frame size, etc.

[0084] In FIG. 7, the message ID, the message rank, the data frame specification, and the traffic specification are information regarding the Talker602. The message ID and the end station I / F are information regarding the Listener603.

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

[0086] Referring to FIGS. 3 and 8, the storage unit 27 stores a correspondence table Tb1 showing the correspondence between services and UNI information, and a plurality of UNI information. The correspondence table Tb1 is an example of correspondence information.

[0087] 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. The UNI information corresponding to service C is UNI information U3.

[0088] Among UNI information U1, UNI information U2, and UNI information U3, 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 from each other.

[0089] For example, the conversion unit 23 performs conversion processing using the correspondence table Tb1. More specifically, for example, when the conversion unit 23 receives a service notification from the detection unit 22, the conversion unit 23 reads out the correspondence table Tb1 in the storage unit 27. Then, the conversion unit 23 specifies 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 conversion unit 23 acquires the UNI information corresponding to the service valid in the in-vehicle network 401.

[0090] Here, 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 specifies UNI information U1 and UNI information U3 as the UNI information corresponding to service A and service C indicated by the service notification received from the detection unit 22, respectively.

[0091] (Notification unit) Referring again to FIGS. 3 and 4, the notification unit 24 performs a notification process of notifying the CUC605, which conforms to the IEEE802.1Qcc standard, i.e., the management unit 25, of the setting information converted by the conversion unit 23.

[0092] 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.

[0093] Specifically, for example, when the conversion unit 23 performs the above conversion process by receiving a service notification from the detection unit 22, the conversion unit 23 acquires the UNI information specified in the conversion process from the storage unit 27. Then, the conversion unit 23 outputs the acquired UNI information to the notification unit 24.

[0094] When the notification unit 24 receives the UNI information from the conversion unit 23, the notification unit 24 outputs the UNI information to the management unit 25 corresponding to the CUC605.

[0095] As the CUC605, the management unit 25 outputs the UNI information notified from the notification unit 24 to the setting unit 26 corresponding to the CNC604. Also, as the CUC605, the management unit 25 performs a transmission process S1 of transmitting the UNI information to each in-vehicle device 202 corresponding to the Talker602 or Listener603 shown in FIG. 5 via the relay unit 21. The transmission process S1 is indicated by the arrow F2 in FIG. 5.

[0096] When each in-vehicle device 202 receives the UNI information from the relay device 101B, the in-vehicle device 202 makes various setting changes according to the UNI information.

[0097] (Setting unit) For example, as the CNC604, the setting unit 26 creates management information for making various setting changes to each relay device 101.

[0098] Specifically, for example, when the setting unit 26 receives UNI information from the management unit 25, as CNC604, it creates management information based on the UNI information. Then, the setting unit 26 makes various setting changes to its own relay device 101B according to the created management information. When the setting changes are completed, the setting unit 26 outputs a completion response to the management unit 25.

[0099] Also, when the setting unit 26 creates management information, as CNC604, it performs a transmission process S2 of transmitting the management information to relay devices 101A and 101C via the relay unit 21. The transmission process S2 is indicated by the arrow F3 in FIG. 5.

[0100] When relay devices 101A and 101C receive management information from relay device 101B, they make various setting changes according to the management information.

[0101] As described above, regarding the method of the process in which CUC605 collects various information from Talker602 and Listener603, indicated by the arrow F1 in FIG. 5, it is not defined in IEEE802.1Qcc.

[0102] On the other hand, in the vehicle management system 301, the relay unit 21 acquires network information N1 from the server 151, and the notification unit 24 performs the above notification process, so that the setting unit 26 can make various setting changes to the relay device 101B without collecting various information necessary for generating UNI information from Talker602 and Listener603. Also, when the management unit 25 performs the transmission process S1 and the setting unit 26 performs the transmission process S2, various setting changes can be made in each in-vehicle device 202 and relay devices 101A and 101C. Therefore, the setting changes of the in-vehicle network 401 can be performed more reliably.

[0103] [Operation flow] FIG. 9 is a flowchart defining the operation procedure when the relay device according to the embodiment of the present disclosure performs the conversion process.

[0104] 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). When the network information N1 is received (YES in step S101), the relay device 101B detects a change in the configuration of the in-vehicle network 401 (step S102).

[0105] Next, the relay device 101B performs a conversion process of converting the network information N1 from the server 151 into UNI information required for the settings performed by the CNC604 according to the IEEE802.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).

[0106] Next, the relay device 101B performs a notification process of notifying the converted UNI information to the CUC605 according to the IEEE802.1Qcc standard. For example, as described above, in the relay device 101B, the notification unit 24 notifies the UNI information converted by the conversion unit 23 to the management unit 25 corresponding to the CUC605 (step S104).

[0107] Next, the management unit 25 outputs the UNI information from the notification unit 24 as the CUC605 to the setting unit 26 corresponding to the CNC604 (step S105).

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

[0109] Next, the setting unit 26 performs various setting changes of its own relay device 101B according to the created management information (step S107).

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

[0111] Next, the management unit 25 transmits the UNI information as CUC605 to each in-vehicle device 202 via the relay unit 21 (step S109), and waits for the arrival of new network information N1 (NО in step S101). Note that the processes from step S107 to step S109 may be executed in a swapped order or in parallel.

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

[0113] Referring to FIG. 10, first, the server 151 transmits network information N1 to the relay device 101B. For example, as described above, when the network information N1 is registered by the user in its own storage unit, the server 151 transmits the network information N1 to the relay device 101B via the external network 170 and the radio base station device 161 (step S201).

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

[0115] Next, the relay device 101B performs a conversion process of converting the network information N1 received from the server 151 into UNI information necessary for the setting performed by the CNC604. 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).

[0116] Next, in the relay device 101B, the conversion unit 23 performs a notification process of notifying the converted UNI information to the management unit 25 corresponding to the CUC605 (step S204).

[0117] Next, in the relay device 101B, the management unit 25 outputs the UNI information as the CUC605 to the setting unit 26 corresponding to the CNC604 (step S205).

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

[0119] Next, the setting unit 26 makes various setting changes to its own relay device 101B according to the created management information (step S207).

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

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

[0122] Next, the relay devices 101A and 101C make various setting changes according to the management information received from the relay device 101B (step S210).

[0123] Also, each in-vehicle device 202 makes various setting changes according to the UNI information received from the relay device 101B (step S211).

[0124] In the vehicle management system 301 according to the embodiment of the present disclosure, although the relay device 101B is configured to acquire the network information N1 from the server 151, the present disclosure is not limited thereto. 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 in 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.

[0125] Also, in the vehicle management system 301 according to the embodiment of the present disclosure, although the relay device 101B is configured to change the settings of the in-vehicle network 401 when an in-vehicle device 202 is added in the in-vehicle network 401, the present disclosure is not limited thereto. The relay device 101B may be configured to perform the setting change when other events occur, such as deletion of the in-vehicle device 202 in the in-vehicle network 401 and update of various software used in the in-vehicle network 401.

[0126] Also, in the vehicle management system 301 according to the embodiment of the present disclosure, although the conversion unit 23 in the relay device 101B is configured to convert the network information N1 from the server 151 into UNI information defined in the IEEE802.1Qcc standard in the conversion process, the present disclosure is not limited thereto. The conversion unit 23 may be configured to convert the network information N1 into related information that is the source of the UNI information in the conversion process. In this case, the conversion unit 23 converts the related information into UNI information in another unit other than the conversion unit 23, for example.

[0127] Also, in the vehicle management system 301 according to the embodiment of the present disclosure, although the conversion unit 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, the present disclosure is not limited thereto. The conversion unit 23 may be configured to create UNI information based on the content of the network information N1 from the server 151 without using the correspondence table Tb1.

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

[0129] Referring to FIG. 11, in Modification Example 1, the server 151 holds network information N2 instead of the network information N1 shown in FIG. 6.

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

[0131] In the network information N2 shown in FIG. 11, the version of the software incorporated in the in-vehicle device 202 with the device ID "D001" is "1.00". The version of the software incorporated in the in-vehicle device 202 with the device ID "D002" is "2.00". The version of the software incorporated in the in-vehicle device 202 with the device ID "D003" is "1.01". That is, the network information N2 includes a device ID group composed of a plurality of device IDs and a version information group composed of a plurality of version information.

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

[0133] Referring to FIGS. 1 and 4 again, when the network information N2 is registered by the user in its own storage unit, the server 151 creates an IP packet that includes the network information N2 and includes its own IP address and the IP address of the relay device 101B as the source IP address and the destination IP address, respectively. Then, the server 151 transmits the created IP packet to the relay device 101B in the vehicle management system 301 via the external network 170 and the radio base station device 161.

[0134] Referring to FIG. 3 again, in the relay device 101B, when the relay unit 21 receives the network information N2 from the server 151, it outputs the received network information N2 to the detection unit 22.

[0135] When the detection unit 22 receives the network information N2 from the relay unit 21, it 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.

[0136] For example, the storage unit 27 stores a management table indicating the correspondence between the device ID group and the version information group and the UNI information.

[0137] When the conversion unit 23 receives the network information N2 from the detection unit 22, it reads out 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.

[0138] For example, the storage unit 27 further stores a plurality of UNI information. Among the plurality of UNI information, 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 from each other.

[0139] 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.

[0140] [Modification Example 2] In the relay device 101B, it was assumed that when the detection unit 22 detects a change in the configuration of the in-vehicle network 401, the notification unit 24 notifies the management unit 25 corresponding to the CUC605 of the setting information, but the present invention is not limited to this. The notification unit 24 may be configured to perform a notification process when a request for setting information is received from the management unit 25.

[0141] FIG. 12 is a diagram showing the configuration of Modification Example 2 of the relay device according to the embodiment of the present disclosure. Referring to FIG. 12, in Modification Example 2, the 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.

[0142] The management unit 251 detects the addition of the in-vehicle device 202 to the in-vehicle network 401. Here, the management unit 251 detects the addition of the in-vehicle device 202D shown in FIG. 4.

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

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

[0145] For example, when the authentication of the in-vehicle device 202D is successful, the management unit 251 transmits authentication success information indicating that the authentication is successful to the in-vehicle device 202D via the relay unit 211.

[0146] Also, for example, when the authentication of the in-vehicle device 202D is successful, the management unit 251 outputs, as CUC605, request information R1 for requesting setting information to the notification unit 24.

[0147] Note that the management unit 251 may be configured to broadcast, for example, periodically, a search message for detecting the addition of the in-vehicle device 202 via the relay unit 211. In this case, the in-vehicle device 202 added to the in-vehicle network 401 receives the search message and transmits connection request information as a response to the received search message.

[0148] For example, when the notification unit 24 receives the request information R1 from CUC605, that is, the management unit 251, it performs a notification process of notifying the management unit 251 of the setting information.

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

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

[0151] When the relay unit 211 receives the request information R2 from the notification unit, it transmits the request information R2 including the vehicle ID stored in the storage unit 27 to the server 151 via the TCU202B.

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

[0153] When the server 151 receives the request information R2 from the relay device 101B, it acquires 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 acquired network information N1 to the relay device 101B via the external network 170 and the radio base station device 161.

[0154] In the relay device 101B, the conversion unit 23 performs a conversion process of converting the network information N1 from the server 151 into setting information required for the settings performed by the CNC604.

[0155] More specifically, for example, when the relay unit 211 receives the network information N1 from the server 151, it outputs a service notification indicating a service in which the discrimination flag is "valid" in the received network information N1 to the conversion unit 23.

[0156] When the conversion unit 23 receives the service notification from the relay unit 211, it performs the above-described 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.

[0157] When the notification unit 24 receives the UNI information from the conversion unit 23, it notifies the management unit 251 corresponding to the CUC605 of the UNI information.

[0158] [Modification Example 3] In the vehicle management system 301 according to the embodiment of the present disclosure, although 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 CUC605, and the setting unit 26 corresponding to the CNC604, the present disclosure is not limited thereto. 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.

[0159] FIG. 13 is a diagram showing a configuration of a modification example 3 of the relay device according to the embodiment of the present disclosure. Referring to FIG. 13, in the modification example 3, the 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 shown in FIG. 3.

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

[0161] FIG. 14 is a diagram showing a configuration of a modification example 3 of the in-vehicle device according to the embodiment of the present disclosure. Referring to FIG. 14, the 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 realized by a processing circuit including, for example, one or a plurality of processors. The storage unit 32 is, for example, a non-volatile memory included in the above processing circuit.

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

[0163] The conversion unit 23 converts the network information N1 from the relay device 101B into UNI information by performing the above-described conversion process.

[0164] Specifically, for example, the storage unit 32 stores the correspondence table Tb1 shown in FIG. 8. When the conversion unit 23 receives the network information N1 from the communication unit 31, it refers to the correspondence table Tb1 in the storage unit 32 to convert the network information N1 into UNI information. Then, the conversion unit 23 outputs the UNI information to the notification unit 24.

[0165] When the notification unit 24 receives the UNI information from the conversion unit 23, it performs a notification process of notifying the UNI information to the management unit 25 corresponding to the CUC605.

[0166] For example, when the management unit 25 receives the UNI information from the management unit 25, it makes various setting changes to its own in-vehicle device 202D as the CUC605.

[0167] Also, for example, the management unit 25, as the CUC605, transmits the UNI information notified from the notification unit 24 to another in-vehicle device 202 different from its own in-vehicle device 202D via the communication unit 31.

[0168] When another in-vehicle device 202 receives the UNI information from the in-vehicle device 202D, it makes various setting changes according to the UNI information.

[0169] Also, for example, the management unit 25, as the CUC605, outputs the UNI information notified from the notification unit 24 to the setting unit 26 corresponding to the CNC604.

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

[0171] When each relay device 101 receives the management information from the in-vehicle device 202D, it makes various setting changes according to the received management information.

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

[0173] The above embodiments should be considered to be illustrative in all respects and not restrictive. The scope of the present invention is indicated by the scope of claims rather than the above description, and it is intended that all modifications within the meaning and scope equivalent to the scope of claims are included.

[0174] Each process (each function) of the above-described embodiment is realized by a processing circuit including one or more processors. The processing circuit may be configured by, in addition to the one or more processors, an integrated circuit in which one or more memories, various analog circuits, and various digital circuits are combined. The one or more memories store a program (instruction) for causing the one or more processors to execute each process. The one or more processors may execute each process according to the program read from the one or more memories, or may execute each process according to a logic circuit designed in advance to execute each process. The processor may be various processors suitable for controlling a computer, 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 plurality of physically separated processors may cooperate with each other to execute each process. For example, the processors mounted on each of a plurality of physically separated computers may cooperate with each other via a network such as a LAN (Local Area Network), a WAN (Wide Area Network), and the Internet to execute each process. The program may be installed in the memory via the network from an external server device or the like, or may be distributed in a state stored in a recording medium such as a CD-ROM (Compact Disc Read Only Memory), a DVD-ROM (Digital Versatile Disk Read Only Memory), and a semiconductor memory, and may be installed in the memory from the recording medium.

[0175] The above description includes the features appended below. [Appendix 1] An acquisition unit that acquires network information related to an in-vehicle network in a vehicle, and A conversion unit that performs a conversion process of converting the network information acquired by the acquisition unit into setting information necessary for settings performed by Centralized Network Configuration according to the IEEE802.1Qcc standard, and a notification unit that performs a notification process of notifying the Centralized User Configuration according to the IEEE802.1Qcc standard of the setting information converted by the conversion unit, wherein the network information indicates a correspondence relationship between services provided in the in-vehicle network and discrimination information indicating whether or not the services are valid in the in-vehicle network, The conversion unit acquires the setting information corresponding to the service that is valid in the in-vehicle network in the conversion process. A vehicle management system.

[0176] [Appendix 2] Comprising a processing circuit, The processing circuit, acquires network information related to an in-vehicle network in a vehicle, performs a conversion process of converting the acquired network information into setting information necessary for settings performed by Centralized Network Configuration according to the IEEE802.1Qcc standard, and performs a notification process of notifying the Centralized User Configuration according to the IEEE802.1Qcc standard of the converted setting information. A vehicle management system.

[0177] [Appendix 3] A vehicle management program used in a vehicle management system, causing a computer to, an acquisition unit that acquires network information related to an in-vehicle network in a vehicle, A conversion unit that performs a conversion process of converting the network information acquired by the acquisition unit into setting information necessary for settings performed by Centralized Network Configuration according to the IEEE802.1Qcc standard, A notification unit that performs a notification process of notifying the Centralized User Configuration according to the IEEE802.1Qcc standard of the setting information converted by the conversion unit, A vehicle management program for functioning as such.

Explanation of symbols

[0178] 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 On-vehicle device 301 Vehicle management system 401 On-vehicle network 501 Communication system 601 Bridge 602 Talker 603 Listener 604 CNC 605 CUC N1, N2 Network information Tb1 Correspondence table

Claims

1. An acquisition unit that acquires network information related to an in-vehicle network in a vehicle; A conversion unit that performs a conversion process of converting the network information acquired by the acquisition unit into setting information necessary for settings performed by a Centralized Network Configuration according to the IEEE 802.1Qcc standard; A vehicle management system comprising: a notification unit that performs a notification process of notifying the setting information converted by the conversion unit to a Centralized User Configuration according to the IEEE 802.1Qcc standard.

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

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

4. The vehicle management system according to claim 1 or 2, wherein the acquisition unit acquires the network information from an external device outside the vehicle.

5. The vehicle management system according to claim 1 or 2, wherein the setting information is User Network Interface information used between the Centralized User Configuration and the Centralized Network Configuration.

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

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

8. The vehicle management system further includes: A detection unit that detects a change in the configuration of the in-vehicle network, The vehicle management system according to claim 1 or 2, wherein the notification unit performs the notification process when the change is detected by the detection unit.

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

Images