Management device, identification information distribution method of vehicle-mounted device, and vehicle-mounted system

Abstract

A management device for assigning identification information to an on-board device connected to an on-board network comprises: a receiving unit, which receives a request frame for assigning identification information including a unique ID of the on-board device from the on-board device; a generating unit, which generates a response frame, wherein the response frame includes the identification information assigned to the request frame received by the receiving unit; and a sending unit, which sends the response frame generated by the generating unit to the on-board device that is the sending source of the request frame.

Description

Technical Field

[0001] The present disclosure relates to a management device, a method for allocating identification information of an on-board device, an on-board system, and a data structure. This application claims priority based on Japanese application No. 2020-007269 filed on January 21, 2020, and all the contents described in the Japanese application are cited by reference. Background Art

[0002] A unique identification number is assigned to each vehicle-mounted device connected to the vehicle-mounted network. In vehicle-mounted network communication protocols such as CAN (Controller Area Network) and FlexRay, CAN ID, frame ID, etc. are used as identification information of the vehicle-mounted device.

[0003] The identification information must be uniquely identified in the vehicle-mounted network. For example, when an in-vehicle device is added to the vehicle-mounted network, identification information must be assigned to the added in-vehicle device so as to avoid duplication with other in-vehicle devices.

[0004] Patent document 1 discloses a method for dynamically assigning identification numbers to ECUs (Electronic Control Units) in an in-vehicle network. In the method disclosed in Patent document 1, each ECU stores a common number table in which a plurality of integer numbers are registered, determines a number from the common number table, and sends the determined number and the unique ID of the ECU to the management ECU. The management ECU determines whether there are duplicate numbers sent by each ECU. If there are no duplicate numbers, the sent number is assigned as the identification number of each ECU. If there are duplicate numbers, the number is assigned to the ECU with the smallest unique ID. The ECU whose unique ID is not the smallest determines a number again from the common number table and sends it to the management ECU.

[0005] Prior Art Literature

[0006] Patent Literature

[0007] Patent Document 1: Japanese Patent Application Publication No. 2012-222527 Summary of the invention

[0008] A method for allocating identification information to a vehicle-mounted device according to one embodiment of the present invention, wherein the vehicle-mounted device is connected to a vehicle-mounted network, and the method for allocating identification information to the vehicle-mounted device comprises the following steps: a management device connected to the vehicle-mounted network receives a request frame containing identification information assigned to a unique ID of the vehicle-mounted device from the vehicle-mounted device; the management device generates a response frame, wherein the response frame contains identification information allocated to the received request frame; and the management device sends the generated response frame to the vehicle-mounted device that is the sending source of the request frame.

[0009] A vehicle-mounted system of one embodiment of the present invention comprises: a management device, connected to a vehicle-mounted network; and a vehicle-mounted device, connected to the vehicle-mounted network, the vehicle-mounted device including a first sending unit, which sends a request frame with identification information including a unique ID of the vehicle-mounted device, the management device including: a second receiving unit, which receives the request frame sent from the vehicle-mounted device; a generating unit, which generates a response frame, the response frame including identification information assigned to the request frame received by the second receiving unit; a second sending unit, which sends the response frame generated by the generating unit to the vehicle-mounted device that is the sending source of the request frame, the vehicle-mounted device also including: a first receiving unit, which receives the response frame sent from the management device; and a setting unit, which sets the identification information included in the response frame received by the first receiving unit as the identification information of this device.

[0010] A data structure of a scheme of the present invention is used in a request frame, wherein the request frame is used for a vehicle-mounted device connected to a vehicle-mounted network to request the allocation of identification information, wherein the data structure includes an ID area and a data area, wherein the ID area stores common identification information in the vehicle-mounted network, and the data area stores a unique ID of the vehicle-mounted device requesting the allocation of identification information and the number of requests for the identification information.

[0011] The data structure of another scheme of the present disclosure is used in a response frame, which is used to respond to a request for allocation of identification information made by a vehicle-mounted device connected to a vehicle-mounted network, wherein the data structure includes an ID area and a data area, wherein the common identification information in the vehicle-mounted network is stored in the ID area, the inherent ID of the vehicle-mounted device requesting the allocation of identification information and the identification information allocated to the vehicle-mounted device are stored in the data area, and the number of identification information requested from the vehicle-mounted device is stored in the data area.

[0012] The present disclosure can be implemented not only as a management device having the characteristic structure as described above, but also as a method for assigning identification information to an onboard device that sets the characteristic processing in the management device as steps, or as a computer program for causing a computer to execute the above steps. A part or all of the management device can be implemented as a semiconductor integrated circuit or as an onboard system including the management device. In addition, the present disclosure can also be implemented as a data structure used in the above-mentioned method for assigning identification information to an onboard device. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Figure 1 This is a schematic diagram for explaining an example of an identification information management system according to an embodiment.

[0014] Figure 2 This is a block diagram showing an example of the configuration of the vehicle-mounted system according to the embodiment.

[0015] Figure 3 This is a block diagram showing an example of the configuration of a management device according to an embodiment.

[0016] Figure 4 This is a diagram showing an example of the structure of a relay table.

[0017] Figure 5 This is a block diagram showing an example of the configuration of the vehicle-mounted device according to the embodiment.

[0018] Figure 6 This is a block diagram showing an example of the structure of a server according to an embodiment.

[0019] Figure 7 This is a functional block diagram showing an example of the functions of the vehicle-mounted device according to the embodiment.

[0020] Figure 8 This is a diagram showing the frame format of CAN.

[0021] Fig. 9 This is a schematic diagram showing an example of a request frame according to an embodiment.

[0022] Fig.10 This is a functional block diagram showing an example of the functions of the management device according to the embodiment.

[0023] Fig.11 This is a diagram showing an example of the structure of a channel management table.

[0024] Fig.12 This is a diagram showing an example of the structure of an ID database.

[0025] Fig.13 This is a schematic diagram showing an example of a normal response frame according to an embodiment.

[0026] Fig.14 It is a schematic diagram showing an example of an abnormal response frame according to an embodiment.

[0027] Fig.15 This is a flowchart showing an example of the procedure of the communication setting process of the vehicle-mounted device according to the embodiment.

[0028] Fig.16 This is a flowchart showing an example of the procedure of the communication management process of the management device according to the embodiment.

[0029] Fig.17 This is a functional block diagram showing a modified example of the functions of the management device according to the embodiment. DETAILED DESCRIPTION

[0030] <Problems to be Solved by the Present Disclosure>

[0031] In the method disclosed in Patent Document 1, if more ECUs request the assignment of identification numbers at the same time, the possibility of number duplication increases. That is, the ECU cannot determine which number is determined by other ECUs, so it is considered that the same number is determined between multiple ECUs. If the number is repeated, the ECU whose inherent ID is not the smallest needs to request the assignment of the number again, so the time required for number assignment increases. In addition, it is also possible to consider the situation where one ECU requests the assignment of multiple identification numbers. In this case, since the possibility of number duplication increases, it is also considered that the time required for number assignment increases.

[0032] <Effects of the Present Disclosure>

[0033] According to the present disclosure, when a plurality of vehicle-mounted devices simultaneously request allocation of identification information or a single vehicle-mounted device requests allocation of a plurality of identification information, an increase in the time required for allocation of identification numbers can be suppressed.

[0034] <Overview of Embodiments of the Present Disclosure>

[0035] Hereinafter, the outline of the embodiments of the present disclosure will be described.

[0036] (1) The management device of this embodiment assigns identification information to an on-board device connected to an on-board network, wherein the management device includes: a receiving unit that receives a request frame for assigning identification information including a unique ID of the on-board device from the on-board device; a generating unit that generates a response frame including identification information assigned to the request frame received by the receiving unit; and a transmitting unit that transmits the response frame generated by the generating unit to the on-board device that is the source of the request frame. Thus, based on the request frame transmitted from the on-board device, a device different from the on-board device can assign identification information between the on-board devices without duplication. That is, the device that assigns identification information can determine the identification information assigned to each on-board device, and thus the identification information assigned to one on-board device can be not assigned to other on-board devices. Therefore, in the case where multiple on-board devices simultaneously request the assignment of identification information or one on-board device requests the assignment of multiple identification information, the increase in the time required for the assignment of identification numbers can be suppressed.

[0037] (2) In the management device of this embodiment, the request frame may further include the number of pieces of identification information requested, and the response frame may include the number of pieces of identification information that are different from each other. This allows a plurality of pieces of identification information to be assigned to one vehicle-mounted device.

[0038] (3) In the management device of the present embodiment, the response frame may include a normal response frame and an abnormal response frame, the generation unit may generate the normal response frame when the identification information is assigned, and the normal response frame includes the assigned identification information, the generation unit may generate the abnormal response frame when the identification information is not assigned, and the abnormal response frame does not include the identification information, and the sending unit may send the normal response frame or the abnormal response frame generated by the generation unit to the vehicle-mounted device of the sending source. Thus, when the vehicle-mounted device receives the normal response frame, the vehicle-mounted device can obtain the identification information included in the normal response frame. When the vehicle-mounted device receives the abnormal response frame, the vehicle-mounted device does not obtain the identification information and can perform necessary measures such as sending the request frame again.

[0039] (4) The management device of this embodiment may further include: a storage unit storing a correspondence table indicating the correspondence between the unique ID of the vehicle-mounted device and the channel of the network bus connected to the vehicle-mounted device; and a connection state determination unit determining whether the correspondence between the unique ID included in the request frame received by the receiving unit and the channel of the network bus transmitting the request frame is consistent with the correspondence indicated by the correspondence table, and when the connection state determination unit determines that the correspondence between the unique ID included in the request frame and the channel transmitting the request frame is consistent with the correspondence indicated by the table, the generation unit generates the normal response frame, and when the connection state determination unit determines that the correspondence between the unique ID included in the request frame and the channel transmitting the request frame is inconsistent with the correspondence indicated by the table, the generation unit generates the abnormal response frame. Thus, when the vehicle-mounted device is not connected to the correct channel, identification information is not allocated to the vehicle-mounted device, and the abnormal connection can be notified by sending the abnormal response frame.

[0040] (5) In the management device of the present embodiment, the request frame may include common identification information, which is common identification information in the vehicle network and is identification information dedicated to the allocation of identification information. An area for storing the identification information of the vehicle-mounted device is set in the frame specified by the vehicle network protocol, but the vehicle-mounted device before the identification information is allocated does not have the identification information to be stored. Therefore, by storing the common identification information in the request frame, the identification information of the vehicle-mounted device is not required, and the vehicle-mounted device such as the management device that receives the request frame can recognize the frame as a frame used in the allocation of identification information.

[0041] (6) In the management device of this embodiment, the request frame may further include a request-specific identifier of the identification information. This allows an on-vehicle device such as the management device that receives the request frame to distinguish between the request frame and the response frame.

[0042] (7) In the management device of this embodiment, the response frame may include the common identification information. This allows the vehicle-mounted device that has received the response frame to recognize the frame as a frame used for allocating identification information.

[0043] (8) In the management device of this embodiment, the response frame may further include an identifier specific to the response to the request for the identification information. This allows the vehicle-mounted device that receives the response frame to distinguish between the request frame and the response frame.

[0044] (9) The management device of this embodiment may further include an assigning unit that assigns identification information to the request frame received by the receiving unit. In this way, the management device can assign identification information to the request frame without inquiring an external device.

[0045] (10) The method for allocating identification information of an on-board device of the present embodiment, the on-board device is connected to an on-board network, and the method for allocating identification information of the on-board device includes the following steps: a management device connected to the on-board network receives a request frame for assigning identification information including a unique ID of the on-board device from the on-board device; the management device generates a response frame including identification information allocated to the received request frame; and the management device transmits the generated response frame to the on-board device that is the source of the request frame. Thus, according to the request frame transmitted from the on-board device, a device different from the on-board device can allocate identification information between the on-board devices without duplication. That is, the device for allocating identification information can determine the identification information allocated to each on-board device, and thus the identification information allocated to one on-board device can be not allocated to other on-board devices. Therefore, in the case where a plurality of on-board devices simultaneously request the allocation of identification information or a single on-board device requests the allocation of a plurality of identification information, an increase in the time required for the allocation of identification numbers can be suppressed.

[0046] (11) The vehicle-mounted system of this embodiment comprises: a management device connected to a vehicle-mounted network; and a vehicle-mounted device connected to the vehicle-mounted network, the vehicle-mounted device including a first transmission unit that transmits a request frame including identification information assigned to a unique ID of the vehicle-mounted device, the management device including a second reception unit that receives the request frame transmitted from the vehicle-mounted device; a generation unit that generates a response frame including identification information assigned to the request frame received by the second reception unit; the second transmission unit that transmits the response frame generated by the generation unit to the vehicle-mounted device that is the transmission source of the request frame, the vehicle-mounted device further including a first reception unit that receives the response frame transmitted from the management device; and a setting unit that sets the identification information included in the response frame received by the first reception unit as the identification information of the device. Thus, according to the request frame transmitted from the vehicle-mounted device, a device different from the vehicle-mounted device can allocate identification information between the vehicle-mounted devices without duplication. That is, the device for allocating identification information can determine the identification information to be allocated to each vehicle-mounted device, so that the identification information allocated to one vehicle-mounted device can be not allocated to other vehicle-mounted devices. Therefore, when multiple vehicle-mounted devices simultaneously request the allocation of identification information or one vehicle-mounted device requests the allocation of multiple identification information, the increase in the time required for the allocation of identification numbers can be suppressed.

[0047] (12) The data structure of the present embodiment is used in a request frame, which is used for an on-board device connected to an on-board network to request the allocation of identification information, wherein the data structure includes an ID area and a data area, wherein the ID area stores common identification information in the on-board network, and the data area stores the unique ID of the on-board device requesting the allocation of identification information and the requested number of the identification information. As a result, an on-board device such as a management device that receives the request frame can recognize the frame as a request frame and can determine the required number of identification information. Therefore, the required number of identification information can be assigned to the on-board device that sent the request frame.

[0048] (13) The data structure of this embodiment is used in a response frame for responding to a request for allocation of identification information made by an on-board device connected to an on-board network, wherein the data structure includes an ID area and a data area, wherein the ID area stores common identification information in the on-board network, the data area stores the unique ID of the on-board device requesting allocation of identification information and the identification information allocated to the on-board device, and the data area stores the number of identification information requested from the on-board device. Thus, the on-board device that receives the response frame can recognize the frame as a response frame, and can also assign one or more identification information to one on-board device at a time.

[0049] <Details of Embodiments of the Present Disclosure>

[0050] Hereinafter, details of the embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be noted that at least a part of the embodiments described below may be arbitrarily combined.

[0051] [1. Identification Information Management System]

[0052] The identification information management system of the present embodiment is a system for managing the identification information of the vehicle-mounted device connected to the vehicle-mounted network mounted on the vehicle. The identification information is used in the vehicle-mounted network to identify each vehicle-mounted device (node). For example, in a CAN bus network, the CAN ID is the identification information. In the present embodiment, the CAN ID is set as the identification information. It should be noted that the identification information is not limited to the CAN ID. For example, in FlexRay, the ID of the vehicle-mounted device included in the frame ID is the identification information, and in LIN (Local Interconnect Network), the ID of the vehicle-mounted device included in the PID (Protected Identifier) ​​field of the header is the identification information.

[0053] Figure 1 This is a schematic diagram for explaining an example of the identification information management system according to the present embodiment.

[0054] The identification information management system 100 includes a plurality of vehicles 10 and a server 40. The vehicle 10 is equipped with a wireless communication device (an external communication device 202 described later) and can perform wireless communication with a base station 20 (or a roadside device). The base station 20 is connected to the Internet 30, and the server 40 is also connected to the Internet 30. The vehicle 10 can perform data communication with the server 40.

[0055] The server 40 has a database (ID database 406. Figure 5 ), and the CAN ID assigned to each vehicle-mounted device is stored for each vehicle 10. When a vehicle 10 needs to assign a CAN ID to a new vehicle-mounted device such as connecting a new vehicle-mounted device to the vehicle network, the vehicle 10 requests the server 40 to assign a CAN ID. The server 40 assigns a CAN ID to the vehicle-mounted device according to the request and registers the CAN ID in the database. The server 40 sends the assigned CAN ID to the vehicle 10 of the request source. In this way, the CAN ID of the vehicle-mounted device of each vehicle 10 is managed.

[0056] [2. In-vehicle system]

[0057] Figure 2 This is a block diagram showing an example of the configuration of the vehicle-mounted system according to the present embodiment.

[0058] The vehicle-mounted system 200 includes, for example, vehicle-mounted devices 201_1, 201_2, 201_3, ..., a management device 300, and an off-vehicle communication device 202. In the following description, the vehicle-mounted devices 201_1, 201_2, 201_3, ... are also collectively referred to as the vehicle-mounted device 201.

[0059] The vehicle-mounted devices 201 include control devices for the powertrain and drivetrain such as an engine control device, an inverter control device, a steering control device, a brake control device, and control devices for in-vehicle equipment such as an air-conditioning control device, a navigation device, a display device, an interior light control device, and an electric window control device.

[0060] The vehicle-mounted devices 201 are respectively connected to the vehicle-mounted network 400. The vehicle-mounted network 400 includes a plurality of CAN buses. A CAN bus is an independent data transmission path and a communication channel. Figure 2 In the example shown, the vehicle network 400 has six channels 400_1, 400_2, 400_3, 400_4, 400_5, and 400_6. The vehicle device 201 is connected to at least one of the channels 400_1, 400_2, 400_3, 400_4, 400_5, and 400_6. Figure 2 In the example shown, the vehicle-mounted device 201_1 is connected to channels 400_1 and 400_2, the vehicle-mounted device 201_2 is connected to channels 400_2 and 400_3, the vehicle-mounted device 201_3 is connected to channels 400_1, 400_2, 400_3, and 400_4, the vehicle-mounted device 201_4 is connected to channels 400_3 and 400_4, the vehicle-mounted device 201_5 is connected to channels 400_2 and 400_4, and the vehicle-mounted devices 201_6, 201_7, and 201_8 are connected to channels 400_5 and 400_6, respectively.

[0061] The management device 300 receives the request frame from the vehicle-mounted device 201 and requests the server 40 to allocate a CAN ID. When the CAN ID is notified from the server 40, the management device 300 generates a response frame including the allocated CAN ID and transmits it to the vehicle-mounted device 201 of the request source. That is, the management device 300 mediates between the vehicle-mounted device 201 and the server 40.

[0062] The management device 300 is connected to each channel 400_1, 400_2, and 400_3 of the vehicle network 400. The management device 300 is a relay device that relays the communication between the vehicle devices 201 connected to different channels. In addition, when the management device 300 receives a request frame from the vehicle device 201, it performs a connection state determination process, which determines whether the channel connected to the vehicle device 201 of the sending source is consistent with the channel to which the vehicle device 201 should be connected. When the connection state is normal, that is, when the vehicle device 201 is connected to the correct channel, the management device 300 generates a normal response frame including the assigned CAN ID, and sends the normal response frame to the vehicle device 201 of the request frame sending source. On the other hand, when the vehicle device 201 is not connected to the correct channel, the management device 300 generates an abnormal response frame that does not include the CAN ID, and sends the abnormal response frame to the vehicle device 201 of the request frame sending source.

[0063] The management device 300 is connected to an external vehicle communication device 202. The external vehicle communication device 202 is capable of wireless communication. The external vehicle communication device 202 communicates with an external vehicle device, such as a terminal, a server 40, etc., via the base station 20 by wireless.

[0064] The management device 300 is connected to the central device 203. The central device 203 has a user interface, that is, an input unit such as a touch sensor, a switch, and a microphone, and an output unit such as a monitor and a speaker. When notifying a user of an abnormality, the management device 300 sends an output command to the central device 203. In response, the central device 203 outputs a screen or sound.

[0065] [3. Structure of management device]

[0066] Figure 3 300 is a block diagram showing an example of the configuration of the management device of the present embodiment. In a specific example, the management device 300 includes a processor 301 , a non-transitory memory 302 , a temporary memory 303 , and a communication interface 304 .

[0067] The temporary memory 303 is, for example, a volatile memory such as SRAM (Static Random Access Memory) and DRAM (Dynamic Random Access Memory). The non-temporary memory 302 is, for example, a non-volatile memory such as a flash memory, a hard disk, or a ROM (Read Only Memory). The non-temporary memory 302 stores a communication management program 305 as a computer program and data used for the execution of the communication management program 305. The management device 300 is configured with a computer, and the various functions of the management device 300 are performed as follows: the communication management program 305 as a computer program stored in the storage device of the computer is executed by the processor 301 as a CPU. The communication management program 305 can be stored in a recording medium such as a flash memory, a ROM, or a CD-ROM. The processor 301 executes the communication management program 305 to perform the communication management processing described later.

[0068] It should be noted that the processor 301 is not limited to a CPU. The processor 301 may also be a hardware logic circuit such as an ASIC (Application Specific Integrated Circuit), a gate array, or an FPGA (Field Programmable Gate Array). In this case, the hardware logic circuit is configured to be able to perform the same processing as the communication management program 305.

[0069] The non-transitory memory 302 includes a relay table 306 and a channel management table 307. The relay table 306 is a table for managing channels used for each CAN ID. Figure 4 306 is a diagram showing an example of the structure of the relay table 306. For example, in the relay table 306, the CAN ID and the channel used for sending and receiving frames are associated with each other. Figure 4In , "r" indicates the channel used by the management device 300 to receive frames, and "s" indicates the channel used to send frames from the management device 300 to the vehicle-mounted device 201. That is, the receiving channel for frames with CAN ID "100" as the transmission source is numbered "0", and the sending channels for frames with CAN ID "100" as the destination are numbered "2" and "3". Similarly, the receiving channel for frames with CAN ID "110" as the transmission source is numbered "0", and the sending channels for frames with CAN ID "110" as the destination are numbered "1" and "2". The receiving channel for frames with CAN IDs "200" and "250" as the transmission source is numbered "1", and the sending channel for frames with CAN IDs "200" and "250" as the destination is numbered "2". The reception channel number of the frame with CAN ID "300" as the transmission source is "2", and the transmission channel number of the frame with CAN ID "300" as the destination is "4".

[0070] The relay table 306 is used in relaying communications between the vehicle-mounted device 201 and other devices (e.g., other vehicle-mounted devices 201 or devices outside the vehicle 10). For example, a situation in which a CAN frame with CAN ID "100" is sent from one vehicle-mounted device 201 to another vehicle-mounted device 201 can be imagined. In this CAN frame, CAN ID "100" is included in the destination. The management device 300 receives the CAN frame through channel "0" and extracts the CAN ID "100" of the destination from the CAN frame. The management device 300 refers to the relay table 306, determines that the number of the channel for sending CAN ID "100" is "2" and "3", and sends the CAN frame to the selected channel.

[0071] The channel management table 307 is used in the above-mentioned connection state determination process. The channel management table 307 is a correspondence table showing the correspondence between the device ID of the vehicle-mounted device 201 and the channel to which the vehicle-mounted device 201 should be connected. Here, the "device ID" is unique identification information assigned to each vehicle-mounted device 201, such as the serial number, MAC address, etc. of the vehicle-mounted device 201. The channel management table 307 will be described later.

[0072] The communication interface 304 is connected to the communication lines connected to the channels 400_1 , 400_2 , and 400_3 of the in-vehicle network 400 , the external communication device 202 , and the central device 203 .

[0073] [4. Structure of the vehicle-mounted device]

[0074] Figure 52 is a block diagram showing an example of the configuration of the vehicle-mounted device of the present embodiment. In a specific example, the vehicle-mounted device 201 includes a processor 211 , a non-transitory memory 212 , a temporary memory 213 , and a communication interface 214 .

[0075] The non-transitory memory 212 stores a communication setting program 215 as a computer program and data used for the execution of the communication setting program 215. The vehicle-mounted device 201 is configured with a computer, and the function related to the setting of the CAN ID of the vehicle-mounted device 201 is performed as follows: the communication setting program 215 as a computer program stored in the storage device of the computer is executed by the processor 211 as the CPU. The communication setting program 215 can be stored in a recording medium such as a flash memory, ROM, CD-ROM, etc. The processor 211 executes the communication setting program 215 and performs the communication setting process described later. In addition, the device ID 216 of this device is stored in the non-transitory memory 212.

[0076] It should be noted that the processor 211 is not limited to a CPU. The processor 211 may be a hardware logic circuit such as an ASIC, a gate array, or an FPGA. In this case, the hardware logic circuit is configured to be able to execute the same processing as the communication setting program 215 .

[0077] The communication interface 214 is connected to one or more of the channels 400_1 , 400_2 , and 400_3 of the vehicle network 400 .

[0078] [5. Server structure]

[0079] Figure 6 4 is a block diagram showing an example of the configuration of a server according to the present embodiment. In a specific example, the server 40 includes a processor 401 , a non-transitory memory 402 , a temporary memory 403 , and a communication interface 404 .

[0080] The non-transitory memory 402 stores an ID allocation program 405 as a computer program and data used for the execution of the ID allocation program 405. The server 40 is configured with a computer, and the function related to the allocation of the CAN ID for the server vehicle-mounted device 201 is performed as follows: the ID allocation program 405 as a computer program stored in the storage device of the computer is executed by the processor 401 as a CPU. The ID allocation program 405 can be stored in a recording medium such as a flash memory, ROM, CD-ROM, etc. The processor 401 executes the ID allocation program 405 to perform the ID allocation process described later.

[0081] The non-transitory memory 402 is provided with an ID database (hereinafter referred to as "IDDB") 406. The IDDB 406 is used in the ID allocation process. The IDDB 406 is a database for managing the CAN ID allocated to the vehicle-mounted device 201 for each vehicle 10. The IDDB 406 will be described later.

[0082] [6. Functions of the vehicle-mounted device]

[0083] Next, the function related to the setting of the CAN ID of the vehicle-mounted device 201 will be described. Figure 7 201 is a functional block diagram showing an example of the functions of the vehicle-mounted device of this embodiment. The vehicle-mounted device 201 has the functions of a first transmission unit 221 , a first reception unit 222 , a request frame generation unit 223 , and a setting unit 224 .

[0084] The request frame generation unit 223 generates a request frame for assigning a CAN ID. For example, when a new vehicle-mounted device 201 is connected to the vehicle-mounted network 400, when the vehicle-mounted system 200 is started, the vehicle-mounted device 201 requests the management device 300 to assign a CAN ID. At this time, a request frame is generated and sent to the management device 300. The request frame generation unit 223 is mainly implemented by the processor 211.

[0085] Figure 8 This is a diagram showing the frame format of CAN. Figure 8 The figure shows the data frame structure of the standard format of CAN. The upper line in the figure represents recessive, and the lower line represents dominant. Figure 8 As shown, the CAN data frame includes SOF (Start Of Frame), CAN ID, RTR (Remote transmission Request), control field, data field, CRC (Cyclic Redundancy Check) sequence, CRC delimiter, ACK (Acknowledgement) time slot, ACK delimiter, and EOF (End Of Frame). SOF indicates the start of the frame. CAN ID is used to identify the vehicle-mounted device 201 and the type of frame. RTR is used to identify data frames and remote frames. In the case of data frames, RTR is dominant. The control field stores information used for communication control. The data field stores actual data (payload) of up to 8 bits. The CRC sequence and CRC delimiter are collectively referred to as the CRC field, and a type of error detection symbol is stored in the CRC field. The ACK time slot and ACK delimiter are collectively referred to as the ACK field, and the ACK field stores information indicating whether the CRC field part can be received normally. EOF indicates the end of the frame.

[0086] Fig. 9: is a schematic diagram showing an example of a request frame of the present embodiment. A common ID (e.g., 0x6FF) is stored in the CAN ID field of the frame related to the allocation of the CAN ID. The common ID is used to identify the frames (request frames and response frames) related to the allocation of the CAN ID. The common ID is information shared by the vehicle network 400. That is, all the vehicle-mounted devices 201 and the management device 300 connected to the vehicle network 400 use one common ID when sending and receiving frames related to the allocation of the CAN ID. The device that receives the request frame recognizes that the frame is a frame related to the allocation of the CAN ID by referring to the common ID in the CAN ID field.

[0087] The data field of the request frame contains data of "device ID" and "number of requested IDs". The CAN ID assigned to one vehicle-mounted device 201 is not limited to one, and there may be multiple CAN IDs. The number of requested IDs is the number of CAN IDs requested by the vehicle-mounted device 201. The end of the data field of the request frame contains an identifier indicating that the frame is a request frame, that is, an identifier dedicated to the request of the CAN ID (in Fig. 9 In the example of CAN FD, the identifier is "00"). The device that receives the request frame identifies the frame as a request frame by referring to the identifier. It should be noted that an example of a request frame in CAN is described here, but the request frame can also be applied to CAN FD. In this case, the CAN ID field in the CAN FD frame format stores the common ID, and the "device ID" and "number of request IDs" are stored in the data field.

[0088] Refer again Figure 7 The first transmission unit 221 transmits the request frame generated by the request frame generation unit 223 via the CAN bus (channel) connected to the vehicle-mounted device 201. The first transmission unit 221 is mainly implemented by the communication interface 214.

[0089] The management device 300 transmits a response frame to the request frame. The first receiving unit 222 receives the response frame via the CAN bus (channel) connected to the vehicle-mounted device 201. The first receiving unit 222 is mainly implemented by the communication interface 214.

[0090] When the response frame received by the first receiving unit 222 is a normal response frame, the setting unit 224 sets the CAN ID included in the normal response frame as the CAN ID of the own device. The CAN ID of the own device is stored in the non-transitory memory 212, for example. In subsequent communications in the vehicle network 400, the CAN ID is used as information for identifying the vehicle-mounted device 201. The setting unit 224 is mainly implemented by the processor 211.

[0091] [7. Functions of the management device]

[0092] Next, a function related to the assignment of the CAN ID of the in-vehicle device 201 by the management device 300 will be described. Fig.10 The management device 300 has the functions of a second receiving unit 311 , a connection state determination unit 312 , an ID inquiry unit 313 , a response frame generation unit 314 , a second sending unit 315 , and an output instruction unit 316 .

[0093] The second receiving unit 311 receives the request frame transmitted from the vehicle-mounted device 201 via the CAN bus (channel). The second receiving unit 311 is mainly implemented by the communication interface 304.

[0094] The connection state determination unit 312 determines whether the correspondence between the unique ID included in the request frame received by the second reception unit 311 and the channel through which the request frame is transmitted matches the correspondence indicated in the channel management table 307 .

[0095] Fig.11 307 is a diagram showing an example of the structure of the channel management table. The channel management table 307 is a table that stores the channel numbers of the in-vehicle network 400 in correspondence with the range of device IDs. Fig.11 In , the device ID is represented by a hexadecimal number. Fig.11 In the example shown, the range of device IDs from "0x00" to "0x2F" corresponds to channel "0". That is, the connection destination of the vehicle-mounted device 201 with device IDs from "0x00" to "0x2F" is channel "0". Similarly, the range of device IDs from "0x30" to "0x5F" corresponds to channel "1". The range of device IDs from "0x60" to "0x8F" corresponds to channel "2". The range of device IDs from "0x90" to "0xBF" corresponds to channel "3". The range of device IDs from "0xC0" to "0xEF" corresponds to channel "4".

[0096] Refer again Fig.10. The connection status determination unit 312 queries the channel management table 307 for the device ID included in the request frame and the number of the channel that transmitted the request frame. That is, the connection status determination unit 312 determines the range of the device ID corresponding to the number of the channel that transmitted the request frame through the channel management table 307, and determines whether the device ID included in the request frame is included in the determined range of the device ID. In the case where the device ID included in the request frame is within the range of the determined device ID, the connection status determination unit 312 determines that the vehicle-mounted device 201 that is the source of the request frame is connected to an appropriate channel. On the other hand, in the case where the device ID included in the request frame deviates from the range of the determined device ID, the connection status determination unit 312 determines that the vehicle-mounted device 201 that is the source of the request frame is connected to an inappropriate channel. The connection status determination unit 312 is mainly implemented by the processor 301.

[0097] When the device ID included in the request frame is within the range of the determined device ID, the ID inquiry unit 313 requests the server 40 to allocate a CAN ID. More specifically, the ID inquiry unit 313 requests the allocation of CAN IDs of the number of requested IDs included in the request frame. The request includes the device ID of the vehicle-mounted device 201 that is the source of the request frame and the number of requested IDs. When the server 40 accepts the request for allocation of CAN IDs, it allocates the number of CAN IDs of the requested IDs.

[0098] The ID allocation process performed by the server 40 will be described. Fig.12 406 is a diagram showing an example of the structure of the IDDB 406. The IDDB 406 stores the CAN ID and the device ID in correspondence. In addition, the IDDB 406 stores the number of the channel used for each CAN ID. Fig.12 In the example shown, "r" indicates a channel (receiving channel) used by the management device 300 to receive frames, and "s" indicates a channel (transmitting channel) used to transmit frames from the management device 300 to the vehicle-mounted device 201. Fig.12 The IDDB406 shown indicates that when a CAN ID is assigned to a certain vehicle-mounted device 201, the management device 300 uses the CANID to communicate, from which channel (receiving channel) to which channel (transmitting channel) the frame is relayed. When a CAN ID is assigned to a device ID, the CAN ID, the device ID, the numbers of the transmitting channel and the receiving channel are stored in correspondence with each other in the IDDB406. Fig.12In the example, for CAN ID "100", the device ID "0x10" is registered, and the receiving channel "0" and the sending channels "2" and "3" are registered. For CAN ID "200", the device ID "0x40" is registered, and the receiving channel "1" and the sending channel "2" are registered. For CAN ID "250", the device ID "0x50" is registered, and the receiving channel "1" and the sending channel "2" are registered. For CAN ID "300", the device ID "0x70" is registered, and the receiving channel "2" and the sending channel "4" are registered.

[0099] The device ID to which the CAN ID is not assigned is not registered in the IDDB 406. When the device ID corresponding to the CAN ID does not exist, the device ID corresponding to the CAN ID is set to blank. Fig.12 In the example, since the device ID corresponding to the CAN ID "210" does not exist, the device ID for the CAN ID "210" is set to blank.

[0100] Regarding the channel number, for a CAN ID not assigned to a device ID (i.e., an unused CAN ID), there are cases where the sending channel number and the receiving channel number are not registered and cases where the sending channel number and the receiving channel number are registered. When a new vehicle-mounted device 201 is connected to the vehicle-mounted network 400, the channel used by the management device 300 is determined by the following two examples.

[0101] (1) Dynamically determine a channel in consideration of the usage status of the channel in the in-vehicle network 400 (hereinafter referred to as “dynamic channel determination”).

[0102] (2) From the viewpoint of suppressing uneven load on the CAN bus, a channel is determined in advance for the CAN ID (hereinafter referred to as "static channel determination").

[0103] In a specific example, it is determined which of the dynamic channel determination and the static channel determination is used for each CAN ID. However, the present invention is not limited thereto, and either the dynamic channel determination or the static channel determination may be used for all CAN IDs.

[0104] When dynamic channel determination is used, in the IDDB 406, for a CAN ID whose device ID is blank (that is, in a record whose device ID is blank), the transmission channel number and the reception channel number are not registered. Fig.12In the example, the transmission channel and the receiving channel corresponding to the CAN ID "210" are not registered. In the dynamic channel determination, the new (i.e., CAN ID is not assigned) vehicle-mounted device 201 sends a request frame to the management device 300, and the management device 300 that receives the request frame determines the channel used in the communication related to the vehicle-mounted device 201 (communication with the vehicle-mounted device 201 as the destination or the transmission source) based on the usage status of the channels in the vehicle network 400 (the number of vehicle-mounted devices 201 connected in each channel, etc.). The management device 300 notifies the server 40 of the number of the determined channel together with the device ID of the vehicle-mounted device 201. The server 40 assigns a CAN ID to the vehicle-mounted device 201, and registers the device ID, the receiving channel number, and the transmitting channel number in correspondence with the CAN ID in the IDDB406.

[0105] On the other hand, when static channel determination is used, the transmission channel number and the reception channel number are registered in advance in the IDDB 406 for the CAN ID whose device ID becomes blank. Fig.12 In the example, the sending channel number "1" and the receiving channel number "3" are predetermined for the CAN ID "350", and in the record of the CAN ID "350", the value of the channel "1" is set to "r", and the value of the channel "3" is set to "s". In the static channel determination, the management device 300 that receives the request frame from the new vehicle-mounted device 201 requests the CAN ID of the vehicle-mounted device 201 from the server 40, and also requests the allocation of the channel. The server 40 allocates a CAN ID to the vehicle-mounted device 201, and registers the device ID in correspondence with the allocated CAN ID in the IDDB406. In addition, the server 40 refers to the IDDB406, determines the receiving channel number and the sending channel number predetermined for the allocated CAN ID, and sends the determined receiving channel number and the sending channel number to the management device 300.

[0106] Refer again Fig.10 The ID inquiry unit 313 receives the notification of the CAN ID transmitted from the server 40 . The ID inquiry unit 313 is mainly implemented by the communication interface 304 .

[0107] The response frame generation unit 314 generates a response frame (a normal response frame or an abnormal response frame), wherein the response frame includes the CAN ID assigned to the request frame received by the second receiving unit 311, that is, the CAN ID notified from the server 40. Specifically, the response frame generation unit 314 generates a normal response frame including the CAN ID assigned by the server 40 when the device ID included in the request frame is within the range of the determined device ID, and generates an abnormal response frame not including the CAN ID when the device ID included in the request frame deviates from the range of the determined device ID. The response frame generation unit 314 is mainly implemented by the processor 301.

[0108] Fig.13 : is a schematic diagram showing an example of a normal response frame of the present embodiment. The CAN ID field of the normal response frame stores the common ID. The data field of the normal response frame contains the data of the "device ID" and the assigned "CAN ID". Specifically, the number of assigned CAN IDs is stored in the data field. The end of the data field of the normal response frame contains an identifier indicating that the frame is a normal response frame, that is, a notification-specific identifier of the assigned CAN ID (in Fig.13 In the example, it is "01"). The device that has received the normal response frame recognizes that the frame is a normal response frame by referring to the identifier.

[0109] Fig.14 : is a schematic diagram showing an example of an abnormal response frame of the present embodiment. The common ID is stored in the CAN ID field of the abnormal response frame. The data field of the abnormal response frame contains data of the "device ID". That is, the data field of the abnormal response frame does not contain the CAN ID. The end of the data field of the abnormal response frame contains an identifier indicating that the frame is an abnormal response frame, that is, a notification-specific identifier for which the CAN ID is not allocated (in Fig.14 In the example of "FF", the device that has received the abnormal response frame recognizes that the frame is an abnormal response frame by referring to the identifier.

[0110] Refer again Fig.10 The second transmitting unit 315 transmits the response frame (normal response frame or abnormal response frame) generated by the response frame generating unit 314 through the CAN bus (channel) connected to the vehicle-mounted device 201 that is the source of the CAN ID request. The second transmitting unit 315 is mainly implemented by the communication interface 304.

[0111] When the device ID included in the request frame is out of the range of the determined device ID, the output instruction unit 316 sends an error output instruction to the central device 203. The central device 203 (see Figure 2) When an error output instruction is received, error output is executed. Error output is, for example, display of error information, sound output of error information, output of buzzer sound, etc. The output instruction unit 316 is mainly implemented by the communication interface 304.

[0112] [8. Operation of the vehicle system]

[0113] The operation of the vehicle-mounted system according to this embodiment will be described. Fig.15 is a flowchart showing an example of the sequence of the communication setting process of the vehicle-mounted device 201 according to the present embodiment. Fig.16 This is a flowchart showing an example of the procedure of the communication management process of the management device 300 according to the present embodiment.

[0114] Reference Fig.15 The processor 211 of the vehicle-mounted device 201, for example, when the vehicle-mounted device 201 is started or when the vehicle-mounted device 201 is detected to be connected to the vehicle-mounted network 400, causes the communication setting program 215 (see Figure 5 ) is started. As a result, the processor 211 starts the communication setting process. In the communication setting process, the processor 211 first determines whether the CAN ID has been set for the device (step S101). In this process, for example, by determining whether the CAN ID is stored in the non-temporary memory 212, it is determined whether the CAN ID has been set.

[0115] If the CAN ID has been set ("Yes" in step S101), the processor 211 ends the communication setting process. On the other hand, if the CAN ID has not been set ("No" in step S101), the processor 211 reads the device ID 216 from the non-transitory memory 212 (step S102). In addition, the processor 211 generates a request frame including the read device ID 216 (step S103). Next, the processor 211 sends the generated request frame to the communication interface 214 through the channel connected to the vehicle-mounted device 201 (step S104).

[0116] Reference Fig.16 When the in-vehicle device 201 is started, for example, the processor 301 of the management device 300 causes the communication management program 305 (see Figure 3 ) is started. As a result, the processor 301 starts the communication management process. In the communication management process, the management device 300 receives a request frame transmitted from the vehicle-mounted device 201 (step S201).

[0117] Next, the processor 301 performs connection status determination processing (step S202). That is, the processor 301 determines whether the correspondence between the device ID of the vehicle-mounted device 201 that is the transmission source of the request frame and the channel connected to the vehicle-mounted device 201 is consistent with the correspondence between the device ID and the channel registered in the channel management table 307. In this processing, if the correspondence between the device ID of the vehicle-mounted device 201 that is the transmission source of the request frame and the channel connected to the vehicle-mounted device 201 is consistent with the correspondence between the device ID and the channel registered in the channel management table 307, it is determined that there is no abnormality in the device ID, and if it is inconsistent with the correspondence between the device ID and the channel registered in the channel management table 307, it is determined that there is an abnormality in the device ID.

[0118] If the result of the connection status determination process is that there is no abnormality in the device ID ("Yes" in step S202), the processor 301 sends a request for a CAN ID to the server 40 (step S203). The server 40 allocates a CAN ID to the device ID in accordance with the request, and notifies the management device 300 of the allocated CAN ID. The management device 300 receives the notification of the allocated CAN ID from the server 40 (step S204).

[0119] Here, when the above-mentioned dynamic channel determination is used, the management device 300 determines the channel used for communication related to the new vehicle-mounted device 201 based on the channel usage status in the vehicle-mounted network 400. The management device 300 notifies the server 40 of the number of the determined channel in the request for the CAN ID of the server 40. The server 40 allocates a CAN ID to the vehicle-mounted device 201, and registers the device ID, the reception channel number, and the transmission channel number in the IDDB 406 in correspondence with the CAN ID.

[0120] When static channel determination is used, the management device 300 requests the server 40 for the CAN ID of the new vehicle-mounted device 201 and also requests the allocation of a channel. The server 40 allocates a CAN ID to the vehicle-mounted device 201, and registers the device ID in correspondence with the allocated CAN ID in the IDDB 406. In addition, the server 40 refers to the IDDB 406 and sends the reception channel number and the transmission channel number predetermined for the allocated CAN ID to the management device 300.

[0121] The processor 301 generates a normal response frame including the received CAN ID (step S205). The processor 301 sends the generated normal response frame to the communication interface 214 through the channel connected to the vehicle-mounted device 201 of the transmission target (step S206). In addition, the processor 301 registers the CAN ID assigned to the vehicle-mounted device 201 in the relay table 306 (step S207).

[0122] When dynamic channel determination is used, the processor 301 registers the determined transmission channel number and reception channel number in correspondence with the CAN ID when registering the CAN ID to the relay table 306. When static channel determination is used, the processor 301 registers the transmission channel number and reception channel number notified from the server 40 in correspondence with the CAN ID when registering the CAN ID to the relay table 306. The communication management process ends as described above.

[0123] On the other hand, if the result of the connection state determination process is that the device ID is abnormal ("No" in step S202), the processor 301 generates an abnormal response frame (step S208). The processor 301 sends the generated abnormal response frame to the communication interface 214 through the channel connected to the vehicle-mounted device 201 of the transmission target (step S209). In addition, the processor 301 sends an error output instruction to the communication interface 214 for the central device 203 (step S210). The above communication management process ends.

[0124] Refer again Fig.15 . The vehicle-mounted device 201, which is the transmission source of the request frame, receives the response frame (normal response frame or abnormal response frame) transmitted from the management device 300 (step S105). The processor 211 determines whether the received response frame is a normal response frame or an abnormal response frame (step S106). That is, the processor 211 determines whether the device ID has an abnormality or not. In the case where the received frame is an abnormal response frame ("No" in step S106), the processor 211 terminates the communication setting process.

[0125] On the other hand, if the received frame is a normal response frame (YES in step S106), processor 211 sets the CAN ID included in the received normal response frame as the CAN ID of the own device (step S107). The communication setting process ends as described above.

[0126] [9. Modifications]

[0127] It should be noted that the structure of the management device 300 is not limited to the structure of the management device 300 of the above-mentioned embodiment. For example, the management device 300 may also have the function of the server 40. That is, the management device 300 may also allocate a CAN ID to the vehicle-mounted device 201 that has sent the request frame. In this case, the server 40 may be omitted. Fig.17 This is a functional block diagram showing a modified example of the functions of the management device according to the embodiment. Fig.17 The management device 300 shown has a function of an allocating unit 320 instead of the ID inquiry unit 313. The allocating unit 320 allocates a CAN ID to the request frame received by the second receiving unit 311. In a specific example, the allocating unit 320 performs the same ID allocation process as the server 20 described above.

[0128] Although the management device 300 has described a configuration in which the error output command is sent to the central device 203 when the correspondence relationship between the device ID of the vehicle-mounted device 201 that is the transmission source of the request frame and the channel to which the request frame is transmitted does not match the correspondence relationship defined in the channel management table 307, the present invention is not limited to this. When the correspondence relationship between the device ID of the vehicle-mounted device 201 that is the transmission source of the request frame and the channel to which the request frame is transmitted does not match the correspondence relationship defined in the channel management table 307, the management device 300 may also perform an error output such as display of an error message, sound output of an error message, output of a buzzer sound, etc.

[0129] A common ID is stored in the CAN ID field of each of the request frame and the response frame, but this is not limited to this. The information stored in the CAN ID field may be different in the request frame and the response frame. For example, the first common ID may be stored in the CAN ID field of the request frame, and the second common ID may be stored in the CAN ID field of the response frame (however, the first common ID and the second common ID are different from each other). Here, the first common ID and the second common ID may also be common information in the vehicle network 400, respectively. That is, all the vehicle-mounted devices 201 and the management device 300 connected to the vehicle network 400 use the first common ID in the transmission and reception of the request frame, and use the second common ID in the transmission and reception of the response frame. The device that receives the request frame identifies the frame as a request frame by referring to the first common ID in the CAN ID field, and the device that receives the response frame identifies the frame as a response frame by referring to the second common ID in the CAN ID field.

[0130] Although the structure of assigning CAN ID to the request frame is described, it is not limited to this. Instead of CANID, an extended ID defined in the extended format of the CAN frame may be used. In this case, the device ID is not stored in the data field of the request frame, and the extended ID is statically set to identify the vehicle-mounted device and the request frame. For example, the device ID is set for the extended ID, or a different ID is set for each vehicle-mounted device represented as a request frame for the CAN ID and the extended ID. Thus, without referring to the data field, it is possible to identify which vehicle-mounted device the request frame is from from the CAN ID and the extended ID.

[0131] [10. Effect]

[0132] As described above, the vehicle-mounted system 200 includes the management device 300 connected to the vehicle-mounted network 400, and the vehicle-mounted device 201 connected to the vehicle-mounted network 400. The vehicle-mounted device 201 includes a first transmitting unit 221, a first receiving unit 222, and a setting unit 224. The management device 300 includes a second receiving unit 311, a response frame generating unit 314, and a second transmitting unit 315. The first transmitting unit 221 transmits a request frame assigned with a CAN ID including the device ID (unique ID) of the vehicle-mounted device 201. The second receiving unit 311 receives the request frame transmitted from the vehicle-mounted device 201. The response frame generating unit 314 generates a response frame including the CAN ID assigned to the request frame received by the second receiving unit 311. The second transmitting unit 315 transmits the response frame generated by the response frame generating unit 314 to the vehicle-mounted device 201 which is the transmission source of the request frame. The first receiving unit 222 receives the response frame transmitted from the management device 300. The setting unit 224 sets the CAN ID included in the response frame received by the first receiving unit 222 as the CAN ID of the own device. Thus, based on the request frame sent from the vehicle-mounted device 201, the server 40, which is a device different from the vehicle-mounted device 201, can allocate CAN IDs between the vehicle-mounted devices 201 without duplication. That is, the server 40 can determine the CAN ID allocated to each vehicle-mounted device 201, so it is possible to avoid allocating the CAN ID allocated to one vehicle-mounted device 201 to other vehicle-mounted devices 201. Therefore, in the case where a plurality of vehicle-mounted devices 201 request the allocation of CAN IDs at the same time or a single vehicle-mounted device 201 requests the allocation of a plurality of CAN IDs, it is possible to suppress the increase in the time required for the allocation of CAN IDs.

[0133] The request frame may further include the number of requested CAN IDs (request ID number). The response frame may include CAN IDs that are different from the request ID number. In this way, multiple CAN IDs can be assigned to one vehicle-mounted device 201.

[0134] The response frame may also include a normal response frame and an abnormal response frame. When a CAN ID is assigned, the response frame generation unit 314 may also generate a normal response frame including the assigned CAN ID. When a CAN ID is not assigned, the response frame generation unit 314 may also generate an abnormal response frame that does not include the CAN ID. The second sending unit 315 may also send the normal response frame or the abnormal response frame generated by the response frame generation unit 314 to the vehicle-mounted device 201 of the sending source. Thus, when the vehicle-mounted device 201 receives the normal response frame, the vehicle-mounted device 201 can obtain the CAN ID included in the normal response frame. When the vehicle-mounted device 201 receives the abnormal response frame, the vehicle-mounted device 201 does not obtain the CAN ID and can perform necessary measures such as sending the request frame again.

[0135] The management device 300 may further include a non-transitory memory 302 and a connection state determination unit 312. The non-transitory memory 302 stores a channel management table 307 indicating the correspondence between the device ID of the vehicle-mounted device 201 and the channel of the CAN bus connected to the vehicle-mounted device 201. The connection state determination unit 312 determines whether the correspondence between the device ID included in the request frame received by the second receiving unit 311 and the channel to which the request frame is transmitted is consistent with the correspondence indicated in the channel management table 307. The response frame generation unit 314 generates a normal response frame when the connection state determination unit 312 determines that the correspondence between the device ID included in the request frame and the channel to which the request frame is transmitted is consistent with the correspondence indicated in the channel management table 307. The response frame generation unit 314 may generate an abnormal response frame when the connection state determination unit 312 determines that the correspondence between the device ID included in the request frame and the channel to which the request frame is transmitted is inconsistent with the correspondence indicated in the channel management table 307. Thus, when the in-vehicle device 201 is not connected to the correct channel, the CAN ID is not allocated to the in-vehicle device 201, and the abnormality response frame is transmitted to notify the abnormality of the connection.

[0136] The request frame may also include a common ID, which is identification information shared in the vehicle network 400 and is identification information dedicated to the allocation of the CAN ID. An area for storing the CAN ID of the vehicle-mounted device 201 is provided in the CAN frame, but the vehicle-mounted device 201 does not have a CAN ID to be stored before the CAN ID is allocated. Therefore, by storing the common ID in the request frame, the CAN ID of the vehicle-mounted device 201 is not required, and the vehicle-mounted device such as the management device 300 that receives the request frame can recognize the frame as a frame used for the allocation of the CAN ID.

[0137] The request frame may further include a request-specific identifier of the CAN ID. This allows the in-vehicle device such as the management device 300 that receives the request frame to distinguish between the request frame and the response frame.

[0138] The response frame may include the common ID. Thus, the vehicle-mounted device 201 that has received the response frame can recognize the frame as a frame used for allocating the CAN ID.

[0139] The response frame may further include an identifier specific to the response to the request of the CAN ID. Thus, the vehicle-mounted device 201 that has received the response frame can distinguish between the request frame and the response frame.

[0140] The management device 300 may further include an allocating unit that allocates a CAN ID to the request frame received by the second receiving unit 311. Thus, the management device 300 can allocate a CAN ID to the request frame without inquiring an external device such as a server.

[0141] The data structure used in the request frame includes a CAN ID area and a data area. The CAN ID area stores the common ID in the vehicle network 400. The data area stores the device ID of the vehicle-mounted device 201 requesting the allocation of the CAN ID and the requested number of CAN IDs. As a result, the vehicle-mounted device such as the management device 300 that receives the request frame can recognize the frame as a request frame and can also determine the number of CAN IDs required. Therefore, the required number of CAN IDs can be assigned to the vehicle-mounted device 201 that sent the request frame.

[0142] The data structure used in the response frame includes a CAN ID area and a data area. The CAN ID area stores the common ID in the vehicle network 400. The data area stores the device ID of the vehicle-mounted device 201 requesting the allocation of the CAN ID and the CAN ID allocated to the vehicle-mounted device 201. The data area stores the number of CAN IDs requested from the vehicle-mounted device 201. Thus, the vehicle-mounted device 201 that receives the response frame can recognize the frame as a response frame, and one or more CAN IDs can be assigned to one vehicle-mounted device 201 at a time.

[0143] [11.Supplement]

[0144] The embodiments disclosed this time are illustrative in all points and are not restrictive. The scope of rights of the present disclosure is disclosed by the claims rather than the above-mentioned embodiments, and includes all modifications within the meaning equivalent to the claims and the scope thereof.

[0145] Description of symbols

[0146] 10 Vehicles

[0147] 20 Base Stations

[0148] 30 Internet

[0149] 40 Servers

[0150] 100 Identification Information Management System

[0151] 200 Car System

[0152] 201, 201_1, 201_2, 201_3, 201_4, 201_5, 201_6, 201_7 Vehicle-mounted devices

[0153] 202 External communication device

[0154] 203 Central Device

[0155] 211 processor

[0156] 212 Non-transitory memory

[0157] 213 Temporary Memory

[0158] 214 Communication Interface

[0159] 215 Communication Setting Procedure

[0160] 216 Device ID

[0161] 221 First Sending Department

[0162] 222 First receiving unit

[0163] 223 Request frame generation unit

[0164] 224 Setting Department

[0165] 300 Management Device

[0166] 301 Processor

[0167] 302 Non-transitory storage

[0168] 303 Temporary storage

[0169] 304 Communication Interface

[0170] 305 Communication Manager

[0171] 306 Relay Table

[0172] 307 Channel Management Table

[0173] 311 Second Receiving Unit

[0174] 312 Connection status determination unit

[0175] 313 ID Inquiry Department

[0176] 314 Response frame generation unit

[0177] 315 Second Sending Department

[0178] 316 Output command unit

[0179] 320 Distribution Department

[0180] 400 In-vehicle network

[0181] 400_1, 400_2, 400_3 channels

[0182] 401 Processor

[0183] 402 Non-transient storage

[0184] 403 Temporary Storage

[0185] 404 Communication Interface

[0186] 405 Program

[0187] 406 ID database.

Claims

1. A management device that assigns identification information to an in-vehicle device connected to an in-vehicle network, wherein: The management device comprises: a receiving unit that receives, from the on-board device, a request frame for providing identification information including a unique ID of the on-board device; a generating unit that generates a response frame including identification information assigned to the request frame received by the receiving unit; and a sending unit that sends the response frame generated by the generating unit to the vehicle-mounted device that is a sending source of the request frame, The response frame includes a normal response frame and an abnormal response frame. The generating unit generates the normal response frame when the identification information is assigned, and the normal response frame includes the assigned identification information. The generating unit generates the abnormal response frame when the identification information is not assigned, and the abnormal response frame does not include the identification information. The transmitting unit transmits the normal response frame or the abnormal response frame generated by the generating unit to the vehicle-mounted device as the transmission source, The management device also has: a storage unit storing a correspondence table indicating a correspondence between a unique ID of an onboard device and a channel of a network bus connecting the onboard device; and a connection state determination unit for determining whether a correspondence between the unique ID included in the request frame received by the receiving unit and a channel of the network bus that transmits the request frame is consistent with a correspondence represented by the correspondence table, When the connection state determination unit determines that the correspondence between the unique ID included in the request frame and the channel through which the request frame is transmitted is consistent with the correspondence represented by the table, the generation unit generates the normal response frame, The generation unit generates the abnormal response frame when the connection state determination unit determines that the correspondence relationship between the unique ID included in the request frame and the channel through which the request frame is transmitted does not match the correspondence relationship indicated by the table.

2. The management device according to claim 1, wherein: The request frame also includes the number of requested identification information. The response frame includes the number of identification information that are different from each other.

3. The management device according to claim 1 or 2, wherein: The request frame includes common identification information, which is common identification information in the in-vehicle network and is identification information dedicated to the allocation of identification information.

4. The management device according to claim 3, wherein: The request frame further includes an identifier specific to the request of the identification information.

5. The management device according to claim 3, wherein: The response frame includes the common identification information.

6. The management device according to claim 5, wherein: The response frame further includes an identifier specific to the response to the request for the identification information.

7. The management device according to claim 1 or 2, wherein: The management device further includes an allocating unit configured to allocate identification information to the request frame received by the receiving unit.

8. A method for distributing identification information of an on-board device, wherein the on-board device is connected to an on-board network, and the method for distributing identification information of the on-board device comprises the following steps: The management device connected to the in-vehicle network receives a request frame for providing identification information including a unique ID of the in-vehicle device from the in-vehicle device; The management device generates a response frame, the response frame including identification information assigned to the received request frame; and The management device transmits the generated response frame to the vehicle-mounted device that is the transmission source of the request frame, The response frame includes a normal response frame and an abnormal response frame. The generating step generates the normal response frame when the identification information is assigned, and the normal response frame includes the assigned identification information. The generating step generates the abnormal response frame without the identification information being assigned, the abnormal response frame not including the identification information, The sending step sends the normal response frame or the abnormal response frame generated by the generating step to the vehicle-mounted device of the sending source, The management device also has: a storage unit storing a correspondence table indicating a correspondence between a unique ID of an onboard device and a channel of a network bus connecting the onboard device; and a connection status determination unit for determining whether the correspondence between the unique ID included in the request frame received in the receiving step and the channel of the network bus that transmits the request frame is consistent with the correspondence represented by the correspondence table, When the connection state determination unit determines that the correspondence between the unique ID included in the request frame and the channel through which the request frame is transmitted is consistent with the correspondence represented by the table, the generating step generates the normal response frame. The generating step generates the abnormal response frame when the connection state determining unit determines that the correspondence relationship between the unique ID included in the request frame and the channel through which the request frame is transmitted does not match the correspondence relationship indicated by the table.

9. A vehicle-mounted system comprising: A management device connected to the vehicle network; and An in-vehicle device connected to the in-vehicle network, The vehicle-mounted device includes a first transmitting unit that transmits a request frame for providing identification information including a unique ID of the vehicle-mounted device. The management device comprises: a second receiving unit, receiving the request frame sent from the vehicle-mounted device; a generating unit that generates a response frame, the response frame including identification information assigned to the request frame received by the second receiving unit; and a second transmitting unit, which transmits the response frame generated by the generating unit to the vehicle-mounted device which is a transmission source of the request frame; The vehicle-mounted device further comprises: a first receiving unit, receiving the response frame sent from the management device; and a setting unit that sets the identification information included in the response frame received by the first receiving unit as the identification information of the own device, The response frame includes a normal response frame and an abnormal response frame. The generating unit generates the normal response frame when the identification information is assigned, and the normal response frame includes the assigned identification information. The generating unit generates the abnormal response frame when the identification information is not assigned, and the abnormal response frame does not include the identification information. The second transmitting unit transmits the normal response frame or the abnormal response frame generated by the generating unit to the vehicle-mounted device of the transmission source, The management device also has: a storage unit storing a correspondence table indicating a correspondence between a unique ID of an onboard device and a channel of a network bus connecting the onboard device; and a connection status determination unit for determining whether a correspondence between the unique ID included in the request frame received by the second receiving unit and a channel of the network bus that transmits the request frame is consistent with a correspondence represented by the correspondence table, When the connection state determination unit determines that the correspondence between the unique ID included in the request frame and the channel through which the request frame is transmitted is consistent with the correspondence represented by the table, the generation unit generates the normal response frame, The generation unit generates the abnormal response frame when the connection state determination unit determines that the correspondence relationship between the unique ID included in the request frame and the channel through which the request frame is transmitted does not match the correspondence relationship indicated by the table.

Images