On-vehicle management device, management method, and management program
The in-vehicle management device uses a monitoring and judgment unit with correspondence information to differentiate between intentional removal and abnormalities, improving monitoring efficiency and reducing processing loads by excluding removable devices from monitoring targets.
Patent Information
- Application Number
- JP2024016343
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-02-06
- Publication Date
- 2025-08-19
AI Technical Summary
In-vehicle management devices face challenges in distinguishing between intentional removal of on-board equipment by users and actual abnormalities, leading to unnecessary processing loads due to erroneous fail-safe and diagnostic actions.
An in-vehicle management device equipped with a monitoring and judgment unit that utilizes correspondence information to determine whether a connected device is a monitoring target, preventing erroneous abnormality detection by registering removable devices as non-targets for monitoring.
This approach enhances the efficiency of in-vehicle device monitoring by reducing processing loads and preventing unnecessary diagnostic and fail-safe actions, ensuring accurate monitoring of in-vehicle equipment.
Smart Images

Figure 2025121112000001_ABST
Abstract
Description
[Technical Field]
[0001] The present disclosure relates to an in-vehicle management device, a management method, and a management program. [Background technology]
[0002] There is a demand for technology that enables retrofitting of in-vehicle devices to vehicles according to user needs. For example, Patent Document 1 (JP 2020-083165 A) discloses the following in-vehicle system. That is, the in-vehicle system includes a power supply box provided in a vehicle and having multiple device connectors and a control unit that supplies power received from a power source to the multiple device connectors, and a switch in the power supply box that switches between blocking and allowing power supply to the multiple device connectors. When power supply to the device connectors is allowed by the switch, the control unit executes a connection target confirmation process that identifies the type of connection target device connected to the device connector and specifies the position of the device connector to which the connection target device is connected. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] Japanese Patent Publication No. 2020-083165 Summary of the Invention [Problem to be solved by the invention]
[0004] In some cases, a management device is provided in an in-vehicle network to monitor the status of in-vehicle devices. For example, if the management device determines that an abnormality has occurred in the in-vehicle device, the management device performs a fail-safe process to stop the power supply to the in-vehicle device and a diagnostic process to diagnose a malfunction of the in-vehicle device.
[0005] In this case, it is considered that the on-board equipment retrofitted to the vehicle is likely to be removed from the vehicle at the user's convenience. In this case, it is difficult for the management device to determine that the on-board equipment has been intentionally removed by the user, and the management device may mistakenly determine that an abnormality has occurred in the on-board equipment. Therefore, there is a problem that the management device performs unnecessary processes such as fail-safe processing and diagnostic processing, which increases the processing load.
[0006] The present disclosure has been made to solve the above-mentioned problems, and its purpose is to provide an in-vehicle management device, management method, and management program that can more efficiently perform monitoring processing of in-vehicle equipment in an in-vehicle network. [Means for solving the problem]
[0007] The vehicle management device disclosed herein is an in-vehicle management device used in an in-vehicle system equipped with multiple in-vehicle devices, and is equipped with a monitoring and judgment unit that performs judgment processing to determine whether a connected device, which is an in-vehicle device connected to its own in-vehicle management device, is a monitoring target, and a memory unit that stores correspondence information that indicates the correspondence between information about the connected device and discrimination information that indicates whether the connected device is a monitoring target, and the monitoring and judgment unit performs the judgment processing using the correspondence information stored in the memory unit.
[0008] One aspect of the present disclosure can be realized not only as an on-board management device equipped with such a characteristic processing unit, but also as a semiconductor integrated circuit that realizes part or all of the on-board management device, or as a system that includes the on-board management device. [Effects of the Invention]
[0009] According to the present disclosure, monitoring of in-vehicle devices in an in-vehicle network can be performed more efficiently. [Brief explanation of the drawings]
[0010] [Figure 1]FIG. 1 is a diagram illustrating an example of a configuration of an in-vehicle system according to an embodiment of the present disclosure. [Figure 2] FIG. 2 is a diagram illustrating an example of a configuration of a new network in an in-vehicle system according to an embodiment of the present disclosure. [Figure 3] FIG. 3 is a diagram illustrating an example of the configuration of the vehicle-mounted relay device according to the embodiment of the present disclosure. [Figure 4] FIG. 4 is a diagram illustrating an example of a determination table stored in the vehicle-mounted relay device according to the embodiment of the present disclosure. [Figure 5] FIG. 5 is a diagram illustrating an example of a determination table stored in the vehicle-mounted relay device according to the embodiment of the present disclosure. [Figure 6] FIG. 6 is a diagram illustrating an example of a determination table stored by the vehicle-mounted relay device according to the embodiment of the present disclosure. [Figure 7] FIG. 7 is a diagram illustrating an example of a determination table stored in the vehicle-mounted relay device according to the embodiment of the present disclosure. [Figure 8] FIG. 8 is a diagram illustrating an example of a determination table stored by the vehicle-mounted relay device according to the embodiment of the present disclosure. [Figure 9] FIG. 9 is a diagram illustrating an example of a monitoring target table stored by the vehicle-mounted relay device according to the embodiment of the present disclosure. [Figure 10] FIG. 10 is a diagram for explaining an example of a determination process by the monitoring and determining unit in the vehicle-mounted relay device according to the embodiment of the present disclosure. [Figure 11] FIG. 11 is a flowchart defining an example of an operation procedure when the vehicle-mounted relay device according to the embodiment of the present disclosure performs a determination process. [Figure 12] FIG. 12 is a flowchart defining an example of an operation procedure when the vehicle-mounted relay device according to the embodiment of the present disclosure performs a determination process. [Figure 13] FIG. 13 is a flowchart defining an example of an operation procedure when the vehicle-mounted relay device according to the embodiment of the present disclosure performs a determination process. [Figure 14]FIG. 14 is a flowchart defining an example of an operation procedure when the vehicle-mounted relay device according to the embodiment of the present disclosure performs processing to create or update a judgment table. DETAILED DESCRIPTION OF THE INVENTION
[0011] First, the contents of the embodiments of the present disclosure will be listed and described. (1) An in-vehicle management device according to an embodiment of the present disclosure is an in-vehicle management device used in an in-vehicle system equipped with a plurality of in-vehicle devices, and includes a monitoring and judgment unit that performs a judgment process to determine whether a connected device, which is an in-vehicle device connected to the in-vehicle management device, is a target for monitoring, and a memory unit that stores correspondence information indicating the correspondence between information about the connected device and discrimination information indicating whether the connected device is a target for monitoring, and the monitoring and judgment unit performs the judgment process using the correspondence information stored in the memory unit.
[0012] With this configuration, by registering in the correspondence information on in-vehicle devices that may be subject to erroneous abnormality detection by the device that performs the monitoring process for the in-vehicle devices, such as in-vehicle devices that are retrofitted to the vehicle, as devices that are not subject to the monitoring process, it is possible to prevent erroneous abnormality detection and reduce the processing load, thereby making it possible to more efficiently monitor the in-vehicle devices in the in-vehicle network.
[0013] (2) In the above (1), the connected device may be connected to the in-vehicle management device via a USB interface, and the information about the connected device may include information indicating a device class of the connected device.
[0014] With this configuration, when an in-vehicle device is connected to an in-vehicle management device via a USB (Universal Serial Bus) interface, it is possible to easily determine whether the in-vehicle device is a target for monitoring by checking the device class of the in-vehicle device and referring to the correspondence information.
[0015] (3) In the above (1) or (2), the vehicle management device may further include a communication unit that receives a message conforming to SOME / IP from the connected device and acquires a service ID contained in the message, and the information about the connected device may include the service ID.
[0016] With this configuration, when messages conforming to SOME / IP (Scalable service-Oriented Middleware over IP) are sent and received between in-vehicle devices, it is possible to easily determine whether the in-vehicle device is a target for monitoring by checking the service ID contained in the message and referring to the corresponding information.
[0017] (4) In any of the above (1) to (3), the information about the connected device may include information specific to the connected device.
[0018] With this configuration, for example, by checking the unique information of the on-board equipment connected to the on-board management device and referring to the correspondence information, it is possible to easily determine whether the on-board equipment is a target for monitoring.
[0019] (5) In any of (1) to (4) above, the vehicle management device may further include a physical port to which the connected device is connected and a relay unit that relays frames transmitted and received between the vehicle devices, and the information about the connected device may include information indicating the physical port.
[0020] With this configuration, by checking the physical port to which the in-vehicle device is connected and referring to the correspondence information, it is possible to easily determine whether or not the in-vehicle device is a monitoring target.
[0021] (6) In any one of the above (1) to (5), the information about the connected device may include information indicating the type of the connected device with which the in-vehicle management device communicates.
[0022] With this configuration, by checking the type of on-board device that is the communication partner of the on-board management device and referring to the correspondence information, it is possible to easily determine whether or not the on-board device is a monitoring target.
[0023] (7) In any one of the above (1) to (6), the information about the connected devices may include information about the topology of the in-vehicle system.
[0024] With this configuration, for example, by checking information regarding the topology of the in-vehicle system and referring to the correspondence information, it is possible to easily determine whether or not an in-vehicle device connected to the in-vehicle management device is a target for monitoring.
[0025] (8) In any of (1) to (7) above, the vehicle management device may further include a management unit that creates or updates the correspondence information based on information obtained from outside the vehicle management device, and the monitoring and judgment unit may perform the judgment process using the correspondence information created or updated by the management unit.
[0026] With this configuration, for example, the correspondence information can be easily created or updated using information acquired from outside after the vehicle has been shipped.
[0027] (9) In the above (8), the memory unit may further store monitoring target information indicating the connected device that is the monitoring target, the management unit may not need to update the monitoring target information, and the monitoring judgment unit may use the monitoring target information stored in the memory unit in preference to the corresponding information stored in the memory unit in the judgment process.
[0028] With this configuration, when it is necessary to monitor in-vehicle equipment corresponding to a certain service in order to provide that service on an in-vehicle network, the information to be monitored can be referenced regardless of the content of the corresponding information, thereby preventing the overlooking of in-vehicle equipment that should be monitored.
[0029] (10) In the above (9), the connected device that is the monitoring target in the monitoring target information may include the in-vehicle device that can be removed by a user of the vehicle in which the in-vehicle system is installed.
[0030] When an on-board device is removed by a vehicle user, there is a possibility that an abnormality may be erroneously detected in the on-board device. However, even if the on-board device is removable, monitoring may be required depending on the use of the on-board device. As described above, by configuring the on-board device that is removable and should be monitored to be registered in the monitoring target information, it is possible to more reliably prevent the on-board device from being overlooked.
[0031] (11) In any of (1) to (10) above, the connected device that is not a monitored object in the correspondence information may be an in-vehicle device that can be removed by a user of a vehicle in which the in-vehicle system is installed.
[0032] When an on-board device is removed by a vehicle user, it may be erroneously detected that an abnormality has occurred in the on-board device. If fail-safe processing, diagnostic processing, etc. are performed in response to this abnormality detection, the processing load increases. With the above configuration, it is possible to determine that on-board devices that can be removed by the vehicle user are not subject to monitoring processing, thereby more reliably reducing the processing load.
[0033] (12) In any one of (1) to (11) above, the vehicle-mounted management device may further include a relay unit that relays frames transmitted and received between the vehicle-mounted devices.
[0034] With this configuration, information about the in-vehicle device, which is necessary to determine whether the in-vehicle device is a target for monitoring, can be easily obtained from the frame to be relayed.
[0035] (13) A management method according to an embodiment of the present disclosure is used in an in-vehicle system having a plurality of in-vehicle devices, and is a management method in an in-vehicle management device having a memory unit, and includes a step of performing a judgment process to determine whether a connected device, which is the in-vehicle device connected to the in-vehicle management device, is a monitoring target, wherein the memory unit stores correspondence information indicating a correspondence between information regarding the connected device and discrimination information indicating whether the connected device is a monitoring target, and in the step of performing the judgment process, the judgment process is performed using the correspondence information stored in the memory unit.
[0036] By using this method, by registering in the correspondence information on in-vehicle devices that may be subject to erroneous abnormality detection by a device that performs monitoring processing on in-vehicle devices, such as in-vehicle devices that are retrofitted to a vehicle, as devices that are not subject to monitoring processing, it is possible to prevent erroneous abnormality detection and reduce the processing load, thereby making it possible to more efficiently monitor in-vehicle devices in an in-vehicle network.
[0037] (14) A management program according to an embodiment of the present disclosure is a management program used in an in-vehicle system having a plurality of in-vehicle devices and used in an in-vehicle management device having a memory unit, and is a program for causing a computer to function as a monitoring and judgment unit that performs judgment processing to determine whether a connected device, which is an in-vehicle device connected to its own in-vehicle management device, is a monitoring target, and the memory unit stores correspondence information indicating the correspondence between information about the connected device and discrimination information indicating whether the connected device is a monitoring target, and the monitoring and judgment unit performs the judgment processing using the correspondence information stored in the memory unit.
[0038] With this configuration, by registering in the correspondence information on in-vehicle devices that may be subject to erroneous abnormality detection by the device that performs the monitoring process for the in-vehicle devices, such as in-vehicle devices that are retrofitted to the vehicle, as devices that are not subject to the monitoring process, it is possible to prevent erroneous abnormality detection and reduce the processing load, thereby making it possible to more efficiently monitor the in-vehicle devices in the in-vehicle network.
[0039] 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.
[0040] [In-vehicle system] 1 is a diagram illustrating an example of the configuration of an in-vehicle system according to an embodiment of the present disclosure. Referring to FIG. 1, the in-vehicle system 301 includes an in-vehicle relay device 101 and a plurality of in-vehicle devices 201. The in-vehicle system 301 is mounted on a vehicle 1. The in-vehicle relay device 101 is an example of an in-vehicle management device.
[0041] In the example shown in FIG. 1, the in-vehicle system 301 includes the in-vehicle device 201, which is in-vehicle devices 201A and 201B.
[0042] The vehicle-mounted relay device 101 and the plurality of vehicle-mounted devices 201 constitute a vehicle-mounted network 401. Each vehicle-mounted device 201 is connected to the vehicle-mounted relay device 101 via an Ethernet (registered trademark) cable 11, for example.
[0043] More specifically, the vehicle-mounted relay device 101 has a plurality of communication ports 20. In the example shown in Fig. 1, the vehicle-mounted relay device 101 has communication ports 20A, 20B, 20C, and 20D, which are communication ports 20. The communication ports 20 are an example of physical ports.
[0044] The communication ports 20A and 20B are connectors to which, for example, an Ethernet cable 11 can be connected. The in-vehicle devices 201A and 201B are connected to the communication ports 20A and 20B via the Ethernet cable 11, respectively.
[0045] A unique port number is assigned to each communication port 20. Here, the port numbers of the communication ports 20A, 20B, 20C, and 20D are P1, P2, P3, and P4, respectively.
[0046] The vehicle-mounted relay device 101 is not limited to a configuration having four communication ports 20, but may be a configuration having one, two, three, five or more communication ports 20.
[0047] The in-vehicle devices 201 include an in-vehicle ECU (Electronic Control Unit), a sensor, a LiDAR (Light Detection and Ranging), an ADAS (Advanced Driving Assistant System), an actuator, a motor, a navigation device, a human-machine interface, a user PC (Personal Computer), and a camera. The in-vehicle ECUs include an autonomous driving ECU, an engine ECU, a steering ECU, a brake ECU, and a TCU (Telematics Communication Unit). The user PC is a PC used by a user such as the driver of the vehicle 1.
[0048] 1, the in-vehicle device 201A is a navigation device, and will hereinafter also be referred to as the navigation device 201A.
[0049] The in-vehicle relay device 101 is used in an in-vehicle system 301 including a plurality of in-vehicle devices 201. The in-vehicle relay device 101 is, for example, a gateway device. The in-vehicle relay device 101 can relay data between the plurality of in-vehicle devices 201 connected thereto.
[0050] Each in-vehicle device 201 transmits frames including various information, which will be described later, such as information for assisting the autonomous driving performed by the vehicle 1 and information used for entertainment, to other in-vehicle devices 201 via the in-vehicle repeater 101. The in-vehicle repeater 101 relays frames received from one in-vehicle device 201 to other in-vehicle devices 201. The in-vehicle repeater 101 also creates frames including the above-mentioned various information and transmits the created frames to the destination in-vehicle devices 201.
[0051] The vehicle-mounted relay device 101 and each vehicle-mounted device 201 communicate with each other to provide various services to the vehicle 1.
[0052] Specifically, services such as updating various software used in the in-vehicle network 401 over the air (OTA), monitoring the surroundings of the vehicle 1, and detecting malfunctions in the vehicle 1 are executed.
[0053] In the in-vehicle network 401, the message M is transmitted and received in accordance with, for example, SOME / IP, which is a protocol of the application layer of the Ethernet protocol suite. More specifically, the in-vehicle device 201 (hereinafter also referred to as "Ethernet device") connected to the in-vehicle relay device 101 via the Ethernet cable 11 stores the message M, which stores various information, in one or more frames, and transmits the frames to other Ethernet devices via the in-vehicle relay device 101 in accordance with SOME / IP. For example, the message M includes a service ID (Identifier).
[0054] Hereinafter, the in-vehicle device 201 newly added to the in-vehicle network 401 will also be referred to as an "additional device." Also, the in-vehicle network 401 including the additional device will also be referred to as a "new network."
[0055] Fig. 2 is a diagram illustrating an example of the configuration of a new network in an in-vehicle system according to an embodiment of the present disclosure. Fig. 2 illustrates the configuration of an in-vehicle network 401 in which new in-vehicle devices 201C and 201D are added to the in-vehicle network 401 illustrated in Fig. 1. That is, the in-vehicle devices 201C and 201D are examples of added devices.
[0056] Referring to FIG. 2, an in-vehicle device 201C is connected to an in-vehicle relay device 101 via an Ethernet cable 11, for example.
[0057] More specifically, for example, the communication port 20C is a connector to which an Ethernet cable 11 can be connected. The in-vehicle device 201C is connected to the communication port 20C via the Ethernet cable 11.
[0058] The in-vehicle device 201D is connected to the in-vehicle relay device 101 via, for example, a USB interface.
[0059] More specifically, the communication port 20D is a connector that can connect to a USB cable 12 that conforms to the USB (registered trademark) standard. The in-vehicle device 201D is connected to the communication port 20D via the USB cable 12.
[0060] In addition, in the in-vehicle network 401, the in-vehicle device 201 may be configured to be connected to the in-vehicle relay device 101 via a bus that complies with communication standards such as CAN (Controller Area Network) (registered trademark), 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), rather than via an Ethernet cable 11 or a USB cable 12.
[0061] [In-vehicle relay device] 3 is a diagram illustrating an example of the configuration of an in-vehicle relay device according to an embodiment of the present disclosure. Referring to FIG. 3, the in-vehicle relay device 101 includes a relay unit 21, a processing unit 22, and a storage unit 23. The processing unit 22 includes a detection unit 31, a monitoring processing unit 32, a monitoring determination unit 33, and a management unit 34. One or both of the relay unit 21 and the processing unit 22 are realized, for example, by a processing circuit including one or more processors. The storage unit 23 is, for example, a non-volatile memory included in the processing circuit. The relay unit 21 is an example of a communication unit.
[0062] (Relay section) For example, the relay unit 21 performs a relay process of relaying frames transmitted and received between the in-vehicle devices 201. More specifically, when the relay unit 21 receives a frame from a certain in-vehicle device 201, it transmits the received frame to the in-vehicle device 201 of the destination.
[0063] The storage unit 23 stores an address table indicating the correspondence between the port numbers of the communication ports 20 and the MAC (Media Access Control) addresses of the in-vehicle devices 201 connected to the communication ports 20. The relay unit 21 performs relay processing using the address table in the storage unit 23.
[0064] Furthermore, when the relay unit 21 receives a frame addressed to its own in-vehicle relay device 101 from an in-vehicle device 201 , it outputs the received frame to the processing unit 22 .
[0065] The processing unit 22 creates a frame addressed to the in-vehicle device 201, and outputs the created frame to the relay unit 21. Upon receiving the frame from the processing unit 22, the relay unit 21 transmits the frame to the in-vehicle device 201 as the destination.
[0066] (Detection unit) The detection unit 31 performs a detection process to detect the in-vehicle device 201 (hereinafter also referred to as a "connected device") connected to the in-vehicle relay device 101. The detection unit 31 performs the detection process, for example, periodically, while the in-vehicle relay device 101 is activated.
[0067] More specifically, the in-vehicle relay device 101 is activated when the ignition power of the vehicle 1 is switched from an off state to an on state. For example, the detection unit 31 broadcasts a search message for detecting a connected device via the relay unit 21 every time a processing timing T arrives after the in-vehicle relay device 101 is activated.
[0068] When the connected device receives a search message from the vehicle-mounted relay device 101, the connected device transmits to the vehicle-mounted relay device 101 a response message in response to the received search message.
[0069] In the vehicle-mounted relay device 101, when the relay unit 21 receives a response message from a connected device via the communication port 20, it outputs to the detection unit 31 a reception notification N1 indicating the port number of the communication port 20 through which the response message has passed.
[0070] When the detection unit 31 receives the reception notification N1 from the relay unit 21, the detection unit 31 checks the port number indicated in the reception notification N1. Then, the detection unit 31 determines that the in-vehicle device 201 is connected to the communication port 20 of that port number. In other words, the detection unit 31 detects the in-vehicle device 201 as a connected device.
[0071] Then, the detection unit 31 outputs detection result information indicating the port numbers corresponding to each of one or more connected devices detected during a period P from when the search message was broadcast until the arrival of the next processing timing T to the monitoring and determination unit 33. Below, a case will be described in which the detection unit 31 detects multiple connected devices during the period P and outputs detection result information indicating multiple port numbers corresponding to the multiple connected devices to the monitoring and determination unit 33.
[0072] (Monitoring processing unit) The monitoring processor 32 performs monitoring processing to monitor connected devices. More specifically, for example, the monitoring processor 32 transmits a predetermined frame for monitoring processing (hereinafter also referred to as a "monitoring frame") to the connected devices. Then, the monitoring processor 32 monitors responses from the connected devices to the monitoring frame.
[0073] Specifically, the monitoring processing unit 32 transmits a monitoring frame to the connected device via the relay unit 21, for example, periodically.
[0074] When the connected device receives the monitoring frame from the vehicle-mounted relay device 101 , it transmits a response frame to the vehicle-mounted relay device 101 .
[0075] In the vehicle-mounted relay device 101, the monitoring processing unit 32 determines that the state of the connected device is normal when it receives a response frame from the connected device via the relay unit 21. On the other hand, when the response frame from the connected device does not arrive, the monitoring processing unit 32 determines that an abnormality has occurred in the connected device.
[0076] When the monitoring processing unit 32 determines that an abnormality has occurred in a connected device, it performs fail-safe processing, diagnostic processing, etc. The fail-safe processing is processing to stop the supply of power to the connected device in which the abnormality has occurred, and processing to have another connected device take over the service performed by the connected device in which the abnormality has occurred. The diagnostic processing is processing to diagnose a malfunction of the connected device, for example.
[0077] The monitoring processing unit 32 is not limited to a configuration that monitors responses from connected devices to monitoring frames, but may be a configuration that monitors the connection state between its own vehicle-mounted relay device 101 and connected devices.
[0078] (decision table) 4 to 8 are diagrams showing examples of determination tables stored in the vehicle-mounted relay device according to the embodiment of the present disclosure.
[0079] 4 to 8, the storage unit 23 stores a judgment table Tb1 indicating a correspondence relationship between information about a connected device (hereinafter also referred to as "connected device information") and discrimination information (hereinafter also referred to as "discrimination flag") indicating whether the connected device is a monitoring target of the monitoring processing unit 32. The judgment table Tb1 is an example of the correspondence information.
[0080] For example, the connected devices that are not monitored by the monitoring processing unit 32 in the judgment table Tb1 are in-vehicle devices 201 that can be removed by the user of the vehicle 1. In other words, the connected devices that are monitored by the monitoring processing unit 32 in the judgment table Tb1 are in-vehicle devices 201 that cannot be removed by the user.
[0081] For example, the storage unit 23 stores judgment tables Tb11, Tb12, Tb13, and Tb14, which are judgment table Tb1.
[0082] 4, 5, 6, 7, and 8 show judgment tables Tb11, Tb12, Tb13, Tb14, and Tb15, respectively.
[0083] In the judgment tables Tb11, Tb12, Tb13, Tb14, and Tb15, a judgment flag of "1" indicates that the connected device is a target of monitoring by the monitoring processing unit 32. A judgment flag of "0" indicates that the connected device is not a target of monitoring by the monitoring processing unit 32.
[0084] (Monitoring Judgment Department) The monitoring determination unit 33 performs a determination process using a determination table Tb1 stored in the storage unit 23 to determine whether each connected device is a target for monitoring by the monitoring processing unit 32 or not.
[0085] More specifically, for example, the monitoring and determining unit 33 performs a determination process for each connected device in accordance with a determination table Tb1 in the storage unit 23.
[0086] For example, the monitoring and determining unit 33 performs the determination process by referring to the determination tables Tb11, Tb12, Tb13, Tb14, and Tb15 in this order.
[0087] For example, in the determination table Tb11 shown in FIG. 4, the connected device information is information indicating the type of the connected device with which the vehicle-mounted relay device 101 communicates (hereinafter also referred to as "type information").
[0088] In the judgment table Tb11, the discrimination flag corresponding to the type of connected device "ADAS" is "1." The discrimination flag corresponding to the type of connected device "TCU" is "1." The discrimination flag corresponding to the type of connected device "user PC" is "0."
[0089] For example, a storage unit (not shown) in the connected device stores identification information (hereinafter also referred to as "type ID") for identifying the type of the connected device itself.
[0090] In the vehicle-mounted relay device 101, when the monitoring and judgment unit 33 receives detection result information from the detection unit 31, it transmits request information R11 requesting the transmission of a type ID to multiple connected devices corresponding to the multiple port numbers indicated in the detection result information via the relay unit 21.
[0091] When the connection device receives the request information R11 from the in-vehicle relay device 101, the connection device transmits the type ID stored in the storage unit to the in-vehicle relay device 101 as a response to the request information R11.
[0092] In the vehicle-mounted relay device 101, when the relay unit 21 receives a type ID from a connected device, it outputs a reception notification N2 indicating the received type ID and the port number of the communication port 20 through which the type ID passed to the monitoring and judgment unit 33 and the management unit 34.
[0093] For example, the storage unit 23 stores a type table indicating the correspondence between type IDs and the types of connected devices.
[0094] For example, when the monitoring determination unit 33 receives a reception notification N2 from the relay unit 21 during a period Q1 from when the request information R11 is transmitted until a predetermined time has elapsed, the monitoring determination unit 33 identifies the type of connected device corresponding to the type ID indicated in the reception notification N2 by referring to the type table in the storage unit 23. Then, the monitoring determination unit 33 checks the determination flag corresponding to the identified type of connected device by referring to the determination table Tb11 in the storage unit 23.
[0095] If the determination flag corresponding to the type of the identified connected device is "1", the monitoring determination unit 33 determines that the connected device connected to the communication port 20 having the port number indicated in the reception notification N2 received from the relay unit 21 is to be monitored. Then, the monitoring determination unit 33 outputs port number information C1 indicating the port number to the monitoring processing unit 32.
[0096] When the monitoring processing unit 32 receives the port number information C1 from the monitoring determining unit 33, it performs monitoring processing on the connected device connected to the communication port 20 with the port number indicated by the port number information C1.
[0097] On the other hand, if the determination flag corresponding to the identified type of connected device is "zero," the monitoring and determining unit 33 performs a determination process for the connected device using the determination table Tb12 shown in FIG.
[0098] Furthermore, if there is a connected device for which the type ID has not arrived during the period Q1, the monitoring and determination unit 33 performs a determination process for that connected device using the determination table Tb12. The connected device is an in-vehicle device 201 for which the monitoring and determination unit 33 has not performed a determination process using the determination table Tb11.
[0099] For example, in the determination table Tb12 shown in FIG. 5, the connected device information is the service ID included in the message M according to SOME / IP sent from the connected device.
[0100] In the determination table Tb12, the determination flag corresponding to the service ID "01" is "1." The determination flag corresponding to the service ID "02" is "1." The determination flag corresponding to the service ID "03" is "0."
[0101] When performing judgment processing using judgment table Tb12, monitoring judgment unit 33 transmits request information R12 to request the transmission of message M including the service ID via relay unit 21 to a connected device of a type corresponding to judgment flag "zero" or to a connected device from which the type ID did not arrive during period Q1.
[0102] For example, the storage unit in the connection device stores the service ID included in the message M sent from the connection device itself.
[0103] When the connection device receives the request information R12 from the in-vehicle relay device 101, the connection device transmits a message M including the service ID stored in the storage unit to the in-vehicle relay device 101 as a response to the request information R12.
[0104] For example, when relay unit 21 receives message M from a connected device, it acquires the service ID included in the received message M. Then, relay unit 21 outputs to monitoring determination unit 33 a reception notification N3 indicating the acquired service ID and the port number of communication port 20 through which message M including the service ID passed.
[0105] For example, when the monitoring and judgment unit 33 receives a reception notification N3 from the relay unit 21 during the period Q2 from when the request information R12 is sent until a predetermined time has elapsed, the monitoring and judgment unit 33 checks the discrimination flag corresponding to the service ID indicated in the reception notification N3 by referring to the judgment table Tb12 in the memory unit 23.
[0106] If the determination flag corresponding to the service ID indicated in the reception notification N3 received from the relay unit 21 is "1", the monitoring determination unit 33 determines that the connected device connected to the communication port 20 having the port number indicated in the reception notification N3 is to be monitored. Then, the monitoring determination unit 33 outputs port number information C2 indicating the port number to the monitoring processing unit 32.
[0107] When the monitoring processing unit 32 receives the port number information C2 from the monitoring determination unit 33, it performs monitoring processing on the connected device connected to the communication port 20 with the port number indicated by the port number information C2.
[0108] On the other hand, if the determination flag corresponding to the service ID indicated in the reception notification N3 received from the relay unit 21 is "zero", the monitoring determination unit 33 performs a determination process for the connected device using the determination table Tb13 shown in FIG.
[0109] Furthermore, if there is a connected device for which the message M has not arrived during the period Q2, the monitoring and determination unit 33 performs a determination process for that connected device using the determination table Tb13. The connected device is an in-vehicle device 201 for which the monitoring and determination unit 33 has not performed a determination process using the determination table Tb12.
[0110] For example, in the judgment table Tb13 shown in FIG. 6, the connected device information is information indicating the device class of the connected device (hereinafter also referred to as "device class information").
[0111] In the judgment table Tb13, the discrimination flag corresponding to the device class "Human Interface Device" of the connected device is "0." The discrimination flag corresponding to the device class "Mass Storage" of the connected device is "1." The discrimination flag corresponding to the device class "Audio" of the connected device is "0."
[0112] When performing judgment processing using judgment table Tb13, monitoring judgment unit 33 transmits request information R13 for requesting the transmission of device class information via relay unit 21 to a connected device that transmits message M including a service ID corresponding to judgment flag "zero", or to a connected device to which message M did not arrive during period Q2.
[0113] For example, a storage unit in a connected device stores device class information indicating the device class of the connected device itself.
[0114] When the connected device receives the request information R13 from the in-vehicle relay device 101, the connected device transmits the device class information stored in the storage unit to the in-vehicle relay device 101 as a response to the request information R13.
[0115] In the vehicle-mounted relay device 101, when the relay unit 21 receives device class information from a connected device, it outputs to the monitoring and judgment unit 33 a reception notification N4 indicating the device class indicated by the received device class information and the port number of the communication port 20 through which the device class information passed.
[0116] For example, when the monitoring judgment unit 33 receives a reception notification N4 from the relay unit 21 during the period Q3 from when the request information R13 is sent until a predetermined time has elapsed, the monitoring judgment unit 33 checks the discrimination flag corresponding to the device class indicated by the reception notification N4 by referring to the judgment table Tb13 in the memory unit 23.
[0117] If the determination flag corresponding to the device class indicated in the reception notification N4 received from the relay unit 21 is "1", the monitoring determination unit 33 determines that the connected device connected to the communication port 20 having the port number indicated in the reception notification N4 is to be monitored. Then, the monitoring determination unit 33 outputs port number information C3 indicating the port number to the monitoring processing unit 32.
[0118] When the monitoring processing unit 32 receives the port number information C3 from the monitoring determination unit 33, it performs monitoring processing on the connected device connected to the communication port 20 with the port number indicated by the port number information C3.
[0119] On the other hand, if the determination flag corresponding to the device class indicated by the reception notification N4 received from the relay unit 21 is "zero", the monitoring determination unit 33 performs a determination process for the connected device using the determination table Tb14 shown in FIG.
[0120] Furthermore, if there is a connected device for which device class information has not arrived during period Q3, the monitoring determination unit 33 performs a determination process for that connected device using the determination table Tb14. The connected device is an in-vehicle device 201 for which the monitoring determination unit 33 has not performed a monitoring process using the determination table Tb13.
[0121] For example, in the judgment table Tb14 shown in Fig. 7, the connected device information is topology information related to the topology of the in-vehicle system 301. For example, the topology information is information for determining the topology of the in-vehicle network 401. In the example shown in Fig. 7, the topology information is unique information of the connected device, specifically, serial number information indicating the serial number of the connected device.
[0122] In the judgment table Tb14, the discrimination flag corresponding to the connected device serial number "AAA" is "1." The discrimination flag corresponding to the connected device serial number "BBB" is "0." The discrimination flag corresponding to the connected device serial number "CCC" is "1."
[0123] The unique information of the connected device registered in the judgment table Tb14 is not limited to the serial number information, but may be other information such as information indicating the product number of the connected device.
[0124] When performing judgment processing using the judgment table Tb14, the monitoring judgment unit 33 transmits request information R14 for requesting the transmission of manufacturing number information via the relay unit 21 to a connected device of a device class corresponding to the judgment flag "zero" or to a connected device for which device class information did not arrive during the period Q3.
[0125] For example, the storage unit in the connected device stores serial number information indicating the serial number of the connected device itself.
[0126] When the connected device receives the request information R14 from the in-vehicle relay device 101, the connected device transmits the serial number information stored in the storage unit to the in-vehicle relay device 101 as a response to the request information R14.
[0127] In the vehicle-mounted relay device 101, when the relay unit 21 receives serial number information from a connected device, it outputs to the monitoring and judgment unit 33 a reception notification N5 indicating the serial number indicated by the received serial number information and the port number of the communication port 20 through which the serial number information passed.
[0128] For example, when the monitoring and judgment unit 33 receives a reception notification N5 from the relay unit 21 during the period Q4 from when the request information R14 is sent until a predetermined time has elapsed, the monitoring and judgment unit 33 checks the discrimination flag corresponding to the manufacturing number indicated in the reception notification N5 by referring to the judgment table Tb14 in the memory unit 23.
[0129] If the determination flag corresponding to the serial number indicated in the reception notification N5 received from the relay unit 21 is "1", the monitoring determination unit 33 determines that the connected device connected to the communication port 20 having the port number indicated in the reception notification N5 is to be monitored. Then, the monitoring determination unit 33 outputs port number information C4 indicating the port number to the monitoring processing unit 32.
[0130] When the monitoring processing unit 32 receives the port number information C4 from the monitoring determination unit 33, it performs monitoring processing on the connected device connected to the communication port 20 with the port number indicated by the port number information C4.
[0131] On the other hand, if the determination flag corresponding to the serial number indicated in the reception notification N5 received from the relay unit 21 is "zero", the monitoring determination unit 33 performs a determination process for the connected device using the determination table Tb15 shown in FIG.
[0132] Furthermore, if there is a connected device for which serial number information has not arrived during period Q4, the monitoring and determination unit 33 performs a determination process for that connected device using the determination table Tb15. The connected device is an in-vehicle device 201 for which the monitoring and determination unit 33 has not performed a determination process using the determination table Tb14.
[0133] For example, in the judgment table Tb15, the connected device information is topology information different from the topology information in the judgment table Tb14 shown in Fig. 7. In the example shown in Fig. 8, the topology information in the judgment table Tb15 is information indicating the communication port 20, specifically, the port number of the communication port 20.
[0134] In the judgment table Tb15, the discrimination flag corresponding to port number "P1" is "zero." The discrimination flag corresponding to port number "P2" is "zero." The discrimination flag corresponding to port number "P3" is "1." The discrimination flag corresponding to port number "P4" is "1."
[0135] When the discrimination flag corresponding to the manufacturing number indicated in the reception notification N5 received from the relay unit 21 is "zero", the monitoring judgment unit 33 checks the discrimination flag corresponding to the port number indicated in the reception notification N5 by referring to the judgment table Tb15 in the memory unit 23.
[0136] In addition, if there is a connected device for which manufacturing number information has not arrived during period Q4, the monitoring and judgment unit 33 refers to the judgment table Tb15 in the memory unit 23 to check the judgment flag corresponding to the port number of the communication port 20 (hereinafter also referred to as the ``non-arrival port'') to which the connected device is connected.
[0137] If the determination flag corresponding to the port number indicated in the reception notification N5 received from the relay unit 21 or the determination flag corresponding to the port number of the non-arrival port is "1", the monitoring determination unit 33 determines that the connected device connected to the communication port 20 of that port number is to be monitored. Then, the monitoring determination unit 33 outputs port number information C5 indicating that port number to the monitoring processing unit 32.
[0138] When the monitoring processing unit 32 receives the port number information C5 from the monitoring determination unit 33, it performs monitoring processing on the connected device connected to the communication port 20 with the port number indicated by the port number information C5.
[0139] On the other hand, if the discrimination flag corresponding to the port number indicated in the reception notification N5 received from the relay unit 21 or the discrimination flag corresponding to the port number of the port that has not yet arrived is "zero", the monitoring judgment unit 33 determines that the connected device connected to the communication port 20 of that port number is not to be monitored.
[0140] Each of the periods Q1, Q2, Q3, and Q4 is, for example, shorter than the interval between processing times T. The sum of the periods Q1, Q2, Q3, and Q4 is, for example, shorter than the interval between processing times T.
[0141] For example, the monitoring and determining unit 33 does not perform the determination process on connected devices that have already been detected by the detecting unit 31, but performs the determination process on connected devices that are newly detected by the detecting unit 31.
[0142] More specifically, for example, when the monitoring judgment unit 33 judges that a connected device is to be monitored through a judgment process using the judgment table Tb1 as described above, the judgment result is stored in the memory unit 23 in association with the port number of the communication port 20 to which the connected device is connected.
[0143] Furthermore, when the monitoring judgment unit 33 judges that the connected device is not a monitoring target through the judgment process using each judgment table Tb1 as described above, the judgment result is stored in the memory unit 23 in association with the port number of the communication port 20 to which the connected device is connected.
[0144] Then, every time the monitoring and determining unit 33 receives detection result information from the detecting unit 31, it checks whether or not the determination result corresponding to the port number indicated by the detection result information is stored in the storage unit 23.
[0145] For example, if the judgment result corresponding to the port number indicated by the detection result information received from the detection unit 31 has already been stored in the storage unit 23, the monitoring and determination unit 33 does not perform the judgment process. On the other hand, if the judgment result corresponding to the port number indicated by the detection result information received from the detection unit 31 has not yet been stored in the storage unit 23, the monitoring and determination unit 33 performs the judgment process.
[0146] The monitoring and determining unit 33 is not limited to a configuration in which it performs the determination process by referring to each determination table Tb1 in the above order, but may be configured to perform the determination process by changing the order in which it refers to each determination table Tb1. Also, the monitoring and determining unit 33 may be configured to perform the determination process by referring to any one or more of the determination tables Tb1.
[0147] Furthermore, the storage unit 23 may be configured not to store any one or more of the judgment tables Tb11, Tb12, Tb13, Tb14, and Tb15.
[0148] (Monitored table) FIG. 9 is a diagram illustrating an example of a monitoring target table stored by the vehicle-mounted relay device according to the embodiment of the present disclosure.
[0149] 9, for example, the storage unit 23 stores a monitoring target table Tb2 that indicates connected devices (hereinafter also referred to as "monitored devices") that are targets of monitoring by the monitoring processing unit 32. The monitoring target table Tb2 is registered in the storage unit 23 by the manufacturer of the vehicle 1, for example, when the vehicle 1 is shipped. The monitoring target table Tb2 is an example of monitoring target information.
[0150] For example, the monitoring target table Tb2 indicates a combination of the serial number of the monitoring target device and the type of the monitoring target device.
[0151] 9, in the monitoring target table Tb2, connected devices used in the autonomous driving performed by the vehicle 1 are registered as monitoring target devices. For example, the monitoring target device is an in-vehicle device 201 that can be removed by the user of the vehicle 1.
[0152] Specifically, for example, the monitored devices registered in the monitored device table Tb2 are a "camera" with serial number "DDD" or "EEE", a "millimeter wave radar" with serial number "FFF", and a "LiDAR" with serial number "GGG".
[0153] In addition, the memory unit 23 is not limited to a configuration in which a monitored object table Tb2 indicating four monitored objects is stored, but may be configured to store a monitored object table Tb2 indicating one, two, three, or five or more monitored objects.
[0154] For example, in the determination process, the monitoring determination unit 33 uses the monitoring target table Tb2 stored in the storage unit 23 in preference to the determination table Tb1 stored in the storage unit 23.
[0155] More specifically, for example, when the monitoring judgment unit 33 judges using the judgment table Tb1 that the connected device is not a monitoring target, it transmits request information R21 to the connected device via the relay unit 21 to request the transmission of serial number information indicating the serial number of the connected device.
[0156] When the connected device receives the request information R21 from the in-vehicle relay device 101, the connected device transmits the serial number information stored in the storage unit to the in-vehicle relay device 101 as a response to the request information R21.
[0157] When the monitoring judgment unit 33 in the vehicle-mounted relay device 101 receives manufacturing number information from a connected device via the relay unit 21, it checks whether the manufacturing number indicated in the received manufacturing number information is registered by referring to the monitoring target table Tb2 in the memory unit 23.
[0158] If the serial number indicated by the serial number information received from the connected device is not registered in the monitoring target table Tb2, the monitoring determination unit 33 determines not to perform monitoring processing for the connected device.
[0159] On the other hand, if the serial number indicated by the serial number information received from the connected device is registered in the monitoring target table Tb2, the monitoring determination unit 33 decides to perform monitoring processing for the connected device. In this case, the monitoring determination unit 33 updates the determination result for the connected device stored in the storage unit 23, i.e., the determination result indicating that the connected device is not a monitoring target, to a determination result indicating that the connected device is a monitoring target.
[0160] In addition, the monitoring judgment unit 33 is not limited to a configuration in which judgment processing is performed by referring to the judgment table Tb1 and the monitored target table Tb2 in this order, but may also be configured to perform judgment processing by changing the order in which the judgment table Tb1 and the monitored target table Tb2 are referred to.
[0161] 10 is a diagram illustrating an example of a determination process by a monitoring determination unit in an in-vehicle relay device according to an embodiment of the present disclosure. In the example illustrated in FIG. 10, the in-vehicle device 201C is a millimeter-wave radar with a serial number "FFF," and the in-vehicle device 201D is a user PC. Hereinafter, the in-vehicle device 201C is also referred to as the millimeter-wave radar 201C, and the in-vehicle device 201D is also referred to as the user PC 201D. In addition, the following describes a case in which the monitoring determination unit 33 performs a determination process by referring to the determination table Tb15 illustrated in FIG. 8, and then refers to the monitoring target table Tb2 illustrated in FIG. 9.
[0162] 8, the determination flag corresponding to the communication port 20A with port number "P1" and the determination flag corresponding to the communication port 20B with port number "P2" are registered as "1." Therefore, the monitoring determination unit 33 determines that the in-vehicle device 201A connected to the communication port 20A and the in-vehicle device 201B connected to the communication port 20B are to be monitored.
[0163] 8, the determination flag corresponding to the communication port 20C with port number "P3" and the determination flag corresponding to the communication port 20D with port number "P4" are registered as "zero." That is, in the determination table Tb14, the millimeter wave radar 201C connected to the communication port 20C and the user PC 201D connected to the communication port 20D are registered as connected devices that are not to be monitored by the monitoring processing unit 32.
[0164] 9, the millimeter-wave radar 201C with the serial number "FFF" is registered as a monitoring target of the monitoring processing unit 32. Therefore, the monitoring determination unit 33 determines that the millimeter-wave radar 201C is a monitoring target.
[0165] On the other hand, the user PC 201D is not registered in the monitoring target table Tb2, so the monitoring determination unit 33 determines that the user PC 201D is not a monitoring target.
[0166] 10, the dashed double-headed arrow indicates a state in which the user PC 201D is not connected to the in-vehicle relay device 101. The monitoring determination unit 33 determines that the user PC 201D is not a monitoring target, and therefore does not determine that an abnormality has occurred in the user PC 201D even if the user PC 201D is removed from the vehicle 1. In other words, even if the user PC 201D is removed from the vehicle 1, the monitoring processing unit 32 does not perform fail-safe processing and diagnostic processing in the in-vehicle relay device 101, thereby reducing the processing load.
[0167] (Management Department) 2 and 3 again, for example, the management unit 34 creates or updates the judgment table Tb1 based on information acquired from outside the vehicle-mounted relay device 101. The following describes a case where the management unit 34 creates or updates the judgment table Tb11 based on information acquired from the navigation device 201A.
[0168] More specifically, for example, when the management unit 34 receives the first reception notification N2 from the relay unit 21 after its own vehicle-mounted relay device 101 has been started up, it identifies the type of connected device corresponding to the type ID indicated in the reception notification N2 by referring to the type table in the memory unit 23.
[0169] Then, the management unit 34 transmits type information indicating the type of the identified connected device to the navigation device 201A.
[0170] The navigation device 201A outputs the received type information when it receives the type information from the vehicle-mounted relay device 101. For example, the navigation device 201A displays the content of the received type information on its own display unit.
[0171] For example, the navigation device 201A accepts information input by the user of the vehicle 1 and transmits the accepted information to the in-vehicle relay device 101. Specifically, for example, the information accepted as input by the navigation device 201A is device discrimination information indicating whether or not the type of connected device indicated by the type information displayed on the display unit of the navigation device 201A is the retrofitted in-vehicle device 201.
[0172] In the vehicle-mounted relay device 101, when the management unit 34 receives the device discrimination information from the navigation device 201A via the relay unit 21, the management unit 34 checks the content indicated by the received device discrimination information.
[0173] For example, if the equipment discrimination information received from the navigation device 201A indicates that the in-vehicle equipment 201 is not a retrofitted in-vehicle equipment, the management unit 34 creates a judgment table Tb11 in which the type of the in-vehicle equipment 201 is associated with a discrimination flag "1".
[0174] Alternatively, for example, if the management unit 34 determines that the device discrimination information received from the navigation device 201A indicates that the in-vehicle device 201 is a retrofitted in-vehicle device, the management unit 34 creates a judgment table Tb11 in which the type of the in-vehicle device 201 is associated with a discrimination flag of "zero."
[0175] After creating the judgment table Tb11, the management unit 34 stores the created judgment table Tb11 in the storage unit 23.
[0176] For example, the management unit 34 updates the judgment table Tb11, but does not update the monitoring target table Tb2 shown in FIG.
[0177] More specifically, for example, after creating the judgment table Tb1, the management unit 34 transmits type information to the navigation device 201A as described above each time it receives a reception notification N2 from the relay unit 21. Then, when the management unit 34 receives device identification information from the navigation device 201A via the relay unit 21, it updates the judgment table Tb11 in the storage unit 23 based on the received device identification information.
[0178] The management unit 34 is not limited to a configuration in which it creates or updates the judgment table Tb1 based on information acquired from the navigation device 201A, but may also be configured to create or update the judgment table Tb1 based on information acquired from other devices such as diagnostic tools used in dealerships, etc.
[0179] 11 to 13 are flowcharts defining an example of an operation procedure when the vehicle-mounted relay device according to the embodiment of the present disclosure performs a determination process.
[0180] 11 to 13, first, the vehicle-mounted relay device 101, in an activated state, waits for the arrival of processing timing T of the detection processing for detecting a connected device (NO in step S101).
[0181] Then, when the processing timing T arrives (YES in step S101), the in-vehicle relay device 101 performs the detection process. For example, as described above, the in-vehicle relay device 101 broadcasts a search message to detect a connected device and waits for a response message to arrive from the connected device. Then, when the in-vehicle relay device 101 receives the response message, it detects the in-vehicle device 201 connected to the communication port 20 through which the response message passed as the connected device (step S102).
[0182] Next, the vehicle-mounted relay device 101 transmits request information R11 for requesting transmission of a type ID to the connected device (step S103), and waits for arrival of a type ID from the connected device (NO in step S104).
[0183] Next, when the in-vehicle relay device 101 receives a type ID from a certain connected device (YES in step S104), it determines whether or not the connected device is a monitoring target. For example, as described above, the in-vehicle relay device 101 identifies the type of connected device corresponding to the received type ID by referring to the type table in the storage unit 23. Then, the in-vehicle relay device 101 checks whether or not the determination flag corresponding to the identified type is "1" by referring to the determination table Tb11 in the storage unit 23 (step S105).
[0184] Then, if the discrimination flag corresponding to the identified type is not "1" (NO in step S105), the vehicle-mounted relay device 101 transmits request information R12 to the connected device to request the transmission of the service ID (step S106), and waits for the arrival of the service ID from the connected device (NO in step S107).
[0185] Next, when the in-vehicle relay device 101 receives a service ID from a certain connected device (YES in step S107), it determines whether or not the connected device is a monitoring target. For example, as described above, the in-vehicle relay device 101 checks whether or not the determination flag corresponding to the service ID received from the connected device is "1" by referring to the determination table Tb12 in the storage unit 23 (step S108).
[0186] If the determination flag corresponding to the service ID received from a certain connected device is not "1" (NO in step S108), the vehicle-mounted relay device 101 transmits request information R13 to the connected device to request transmission of device class information indicating the device class of the connected device (step S109), and waits for the arrival of device class information from the connected device (NO in step S110).
[0187] Next, when the in-vehicle relay device 101 receives device class information from a certain connected device (YES in step S110), it determines whether or not the connected device is a monitoring target. For example, as described above, the in-vehicle relay device 101 refers to the determination table Tb13 in the storage unit 23 to check whether or not the determination flag corresponding to the device class indicated by the device class information received from the connected device is "1" (step S111).
[0188] If the discrimination flag corresponding to the device class indicated by the device class information received from a certain connected device is not "1" (NO in step S111), the vehicle-mounted relay device 101 transmits request information R14 to the connected device requesting the transmission of serial number information indicating the serial number of the connected device (step S112), and waits for the arrival of serial number information from the connected device (NO in step S113).
[0189] Next, when the in-vehicle relay device 101 receives serial number information from a certain connected device (YES in step S113), it determines whether or not the connected device is a monitoring target. For example, as described above, the in-vehicle relay device 101 refers to the determination table Tb14 in the storage unit 23 to check whether or not the determination flag corresponding to the serial number indicated by the serial number information received from the connected device is "1" (step S114).
[0190] Then, if the discrimination flag corresponding to the serial number indicated by the serial number information received from a certain connected device is not "1" (NO in step S114), the vehicle-mounted relay device 101 checks whether the discrimination flag corresponding to the port number of the communication port 20 to which the connected device is connected is "1" by referring to the judgment table Tb15 in the memory unit 23 (step S115).
[0191] Then, if the port number discrimination flag of the communication port 20 to which the connected device is connected is not "1" (NO in step S115), the vehicle-mounted relay device 101 checks whether the connected device is a monitored device registered in the monitored device table Tb2 in the memory unit 23 (step S116).
[0192] If the connected device is not a monitored device (NO in step S116), the vehicle-mounted relay device 101 decides not to perform monitoring processing of the connected device (step S117) and waits for the arrival of the next processing timing T (NO in step S101).
[0193] On the other hand, if the vehicle-mounted relay device 101 determines that the connected device is a monitoring target by referring to each judgment table Tb1 or monitoring target table Tb2 (YES in step S105, YES in step S108, YES in step S111, YES in step S114, YES in step S115, or YES in step S116), it decides to perform monitoring processing (step S118).
[0194] Next, the vehicle-mounted relay device 101 performs a monitoring process (step S119) to check whether or not an abnormality has occurred in the connected device (step S120).
[0195] If the in-vehicle relay device 101 determines that an abnormality has occurred in the connected device (YES in step S120), the in-vehicle relay device 101 performs fail-safe processing. For example, the in-vehicle relay device 101 performs processing such as stopping the power supply to the connected device as fail-safe processing (step S121).
[0196] Next, the vehicle-mounted relay device 101 performs a diagnostic process to diagnose a failure of the connected device (step S122), and waits for the arrival of the next processing timing T (NO in step S101). Note that steps S121 and S122 may be executed in reverse order or in parallel.
[0197] Furthermore, if the vehicle-mounted relay device 101 determines that no abnormality has occurred in the connected device (NO in step S120), it waits for the next processing timing T to arrive (NO in step S101).
[0198] 14 is a flowchart illustrating an example of an operation procedure when the in-vehicle relay device according to the embodiment of the present disclosure performs a process of creating or updating a judgment table Tb11. FIG. 14 illustrates an operation when the in-vehicle relay device 101 creates or updates the judgment table Tb11.
[0199] Referring to FIG. 14, first, the processes from step S201 to step S204 are similar to the processes from step S101 to step S104 shown in FIG.
[0200] Next, when the in-vehicle relay device 101 receives the type ID from the connected device (YES in step S204), it refers to the type table in the storage unit 23 to identify the type of the connected device corresponding to the received type ID (step S205).
[0201] Next, the vehicle-mounted relay device 101 transmits type information indicating the type of the identified connected device to the navigation device 201A (step S206).
[0202] Next, the vehicle-mounted relay device 101 waits for the arrival of device identification information from the navigation device 201A (NO in step S207).
[0203] Then, when the vehicle-mounted relay device 101 receives the device discrimination information from the navigation device 201A (YES in step S207), it creates or updates the judgment table Tb11 (step S208) and waits for the next processing timing T to arrive (NO in step S201).
[0204] In the in-vehicle relay device 101 according to the embodiment of the present disclosure, the storage unit 23 is configured to store a plurality of judgment tables Tb1, namely, judgment tables Tb11, Tb12, Tb13, Tb14, and Tb15. However, this is not limited to this. The storage unit 23 may be configured to store a judgment table Tb1 in which connected device information different from the connected device information described above is registered. Furthermore, the storage unit 23 may be configured to store a judgment table Tb1 in which the different connected device information is registered, instead of some or all of the plurality of judgment tables Tb1, or in addition to the plurality of judgment tables Tb1.
[0205] In addition, in the in-vehicle system 301 according to the embodiment of the present disclosure, the in-vehicle relay device 101 is configured to include the monitoring processing unit 32 that performs monitoring processing of connected devices, but this is not limited to this. A device other than the in-vehicle relay device 101 in the in-vehicle network 401 may be configured to include the monitoring processing unit 32.
[0206] Furthermore, in the in-vehicle system 301 according to the embodiment of the present disclosure, the in-vehicle relay device 101 is configured to include the management unit 34 that creates or updates the judgment table Tb1, but this is not limited to this. The in-vehicle relay device 101 may be configured not to include the management unit 34. In this case, the judgment table Tb1 is registered in the memory unit 23 by the manufacturer of the vehicle 1, for example, when the vehicle 1 is shipped.
[0207] Furthermore, in the in-vehicle relay device 101 according to the embodiment of the present disclosure, the monitoring determination unit 33 is configured to use the monitoring target table Tb2 stored in the memory unit 23 in priority to the judgment table Tb1 stored in the memory unit 23 in the judgment process, but this is not limited to this. The monitoring determination unit 33 may be configured to perform judgment processing using the judgment table Tb1 without using the monitoring target table Tb2. In this case, the memory unit 23 does not store the monitoring target table Tb2, but stores the judgment table Tb1.
[0208] Furthermore, in the in-vehicle relay device 101 according to the embodiment of the present disclosure, the monitored devices registered in the monitored device table Tb2 stored in the storage unit 23 are the in-vehicle devices 201 that can be removed by the user of the vehicle 1, but this is not limited to this. The monitored device table Tb2 may be configured so that the in-vehicle devices 201 that cannot be removed by the user are registered as monitored devices, or both the removable in-vehicle devices 201 and the non-removable in-vehicle devices 201 are registered as monitored devices.
[0209] Furthermore, in the in-vehicle relay device 101 according to the embodiment of the present disclosure, the judgment table Tb1 stored in the storage unit 23 is configured such that the in-vehicle devices 201 that can be removed by the user of the vehicle 1 are registered as connected devices that are not subject to monitoring, but this is not limited to this. The judgment table Tb1 may be configured such that the in-vehicle devices 201 that cannot be removed by the user are registered as connected devices that are not subject to monitoring, or such that both the removable in-vehicle devices 201 and the non-removable in-vehicle devices 201 are registered as connected devices that are not subject to monitoring.
[0210] Furthermore, in the in-vehicle system 301 according to the embodiment of the present disclosure, the in-vehicle relay device 101 is configured to include the detection unit 31, the monitoring processing unit 32, the monitoring determination unit 33, the management unit 34, and the storage unit 23, but this is not limited to this. A device other than the in-vehicle relay device 101 in the in-vehicle network 401 may be configured to include at least the monitoring determination unit 33 and the storage unit 23 among the units other than the relay unit 21 in the in-vehicle relay device 101.
[0211] 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.
[0212] 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 programs read from the one or more memories, or according to logic circuits pre-designed to execute each of the processes. The processor may be 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 separate processors may execute each of the processes in cooperation with each other. For example, the processors mounted on a plurality of physically separated computers may cooperate with each other to execute the above processes via a network such as a LAN (Local Area Network), a WAN (Wide Area Network), the Internet, etc. 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 installed into the memory from the recording medium.
[0213] The above description includes the following additional features. [Appendix 1] An in-vehicle management device used in an in-vehicle system including a plurality of in-vehicle devices, processing circuitry and a memory; The processing circuitry performing a determination process to determine whether or not the connected device, which is the on-board device connected to the on-board management device of the own, is a monitoring target; the memory stores correspondence information indicating a correspondence relationship between information about the connected device and determination information indicating whether the connected device is a monitoring target; The processing circuit performs the determination process using the correspondence information stored in the memory. [Explanation of symbols]
[0214] 1 vehicle 11 Ethernet cable 12 USB cable 20, 20A, 20B, 20C, 20D communication port 21 Relay Section 22 Processing section 23 Memory section 31 Detection unit 32 Monitoring processing unit 33 Monitoring and Judgment Department 34 Management Department 101 Vehicle relay device 201,201A,201B,201C,201D Vehicle equipment 301 In-Vehicle Systems 401 In-Vehicle Network Tb1,Tb11,Tb12,Tb13,Tb14 decision table Tb2 monitored table
Claims
1. An in-vehicle management device used in an in-vehicle system including a plurality of in-vehicle devices, a monitoring and determining unit that performs a determination process to determine whether a connected device, which is the on-board device connected to the on-board management device itself, is a monitoring target; a storage unit that stores correspondence information indicating a correspondence relationship between information about the connected device and determination information indicating whether the connected device is a monitoring target; The monitoring and determining unit performs the determination process using the correspondence information stored in the storage unit.
2. the connection device is connected to the in-vehicle management device via a USB interface, The in-vehicle management device according to claim 1 , wherein the information about the connected device includes information indicating a device class of the connected device.
3. The in-vehicle management device further a communication unit that receives a message conforming to SOME / IP from the connected device and acquires a service ID included in the message; The in-vehicle management device according to claim 1 , wherein the information about the connected device includes the service ID.
4. The in-vehicle management device according to claim 1 , wherein the information about the connected device includes information specific to the connected device.
5. The in-vehicle management device further a physical port to which the connection device is connected; a relay unit that relays frames transmitted and received between the in-vehicle devices, The in-vehicle management device according to claim 1 , wherein the information about the connected device includes information indicating the physical port.
6. 3. The on-board management device according to claim 1, wherein the information about the connected device includes information indicating a type of the connected device with which the on-board management device communicates.
7. 3. The in-vehicle management device according to claim 1, wherein the information about the connected devices includes information about a topology of the in-vehicle system.
8. The in-vehicle management device further a management unit that creates or updates the correspondence information based on information acquired from outside the vehicle-mounted management device; The in-vehicle management device according to claim 1 , wherein the monitoring and determining unit performs the determination process using the correspondence information created or updated by the management unit.
9. The storage unit further stores monitoring target information indicating the connected device that is the monitoring target, The management unit does not update the monitoring target information, The vehicle-mounted management device according to claim 8 , wherein the monitoring determination unit uses the monitoring target information stored in the storage unit in priority to the corresponding information stored in the storage unit in the determination process.
10. The in-vehicle management device according to claim 9 , wherein the connected devices that are the monitoring targets in the monitoring target information include the in-vehicle devices that are removable by a user of a vehicle in which the in-vehicle system is installed.
11. 3. The in-vehicle management device according to claim 1, wherein the connected devices that are not the monitoring targets in the correspondence information are the in-vehicle devices that can be removed by a user of a vehicle in which the in-vehicle system is installed.
12. The in-vehicle management device further 3. The vehicle-mounted management device according to claim 1, further comprising a relay unit that relays frames transmitted and received between the vehicle-mounted devices.
13. A management method for an in-vehicle management device that is used in an in-vehicle system that includes a plurality of in-vehicle devices and that includes a storage unit, comprising: a step of performing a determination process to determine whether a connected device, which is the on-board device connected to the on-board management device, is a monitoring target; the storage unit stores correspondence information indicating a correspondence relationship between information about the connected device and determination information indicating whether the connected device is the monitoring target; A management method, wherein in the step of performing the determination process, the determination process is performed using the correspondence information stored in the storage unit.
14. A management program used in an in-vehicle system including a plurality of in-vehicle devices, the management program being used in an in-vehicle management device including a storage unit, Computer, a monitoring and determining unit that performs a determination process to determine whether a connected device, which is the on-board device connected to the on-board management device itself, is a monitoring target; It is a program to function as the storage unit stores correspondence information indicating a correspondence relationship between information about the connected device and determination information indicating whether the connected device is the monitoring target; The monitoring and determining unit performs the determination process using the correspondence information stored in the storage unit.
Citation Information
Patent Citations
On-vehicle system
JP2020083165A