Management device, in-vehicle device, management method, and management program

Abstract

A management device is provided with: a reception unit that receives vehicle identification information for identifying a vehicle from an in-vehicle device mounted on the vehicle; a setting unit that performs a setting process for setting a computer program corresponding to the vehicle identification information received by the receiving unit as a first computer program for processing vehicle information related to the vehicle in the management device; and an update request unit that performs an update request process for transmitting update request information for requesting an update to a second computer program corresponding to the vehicle identification information received by the receiving unit to the in-vehicle device. The second computer program is used for the vehicle-mounted device to acquire the vehicle information and transmit the acquired vehicle information to the management device so as to provide the acquired vehicle information to the first computer program set by the setting unit.

Description

Technical Field

[0001] The present disclosure relates to a management device, an on-vehicle device, a management method, and a management program. This application claims priority based on Japanese application No. 2022-192764 filed on December 1, 2022, and all the contents described in the Japanese application are hereby incorporated by reference. Background Art

[0002] A system has been developed that includes a management device for collecting vehicle information related to the vehicle from an on-board device mounted on the vehicle. For example, in International Publication No. 2020 / 049379 (Patent Document 1), the following technology is disclosed. That is, an information collection device, together with a ground system, constitutes a train equipment management system that manages the usage history of equipment installed on a train, wherein the information collection device is characterized in that it includes: a vehicle information collection unit that collects individual identification numbers and first operating information, wherein the individual identification number is inherently attached to each device installed on the train as a management object, and is used to identify the device, wherein the first operating information indicates the operating status of each device; and a train comprehensive management device that collects second operating information indicating the operating status when controlling each device, the individual identification number of each device, operating information including the first operating information and the second operating information, identifying the vehicle number of the vehicle on which each device is installed, and identifying the train's marshaling number and sending the control to the ground system via a communication device.

[0003] Prior art literature

[0004] Patent Literature

[0005] Patent Document 1: International Publication No. 2020 / 049379

[0006] Patent Document 2: Japanese Patent Application Publication No. 2019-117493 Summary of the invention

[0007] The management device disclosed in the present invention is a management device as follows, which comprises: a receiving unit, which receives vehicle identification information for identifying the vehicle from a vehicle-mounted device mounted on the vehicle; a setting unit, which performs setting processing of setting a computer program corresponding to the vehicle identification information received by the receiving unit as a first computer program, and the first computer program is used to process vehicle information related to the vehicle in the management device; and an update request unit, which performs update request processing of sending update request information to the vehicle-mounted device, and the update request information is used to request an update to a second computer program corresponding to the vehicle identification information received by the receiving unit, and the second computer program is used for the vehicle-mounted device to obtain the vehicle information and send the acquired vehicle information to the management device to provide it to the first computer program set by the setting unit. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Figure 1 It is a diagram showing the structure of a communication system involved in an embodiment of the present disclosure.

[0009] Figure 2 It is a diagram showing the configuration of a vehicle-mounted device according to an embodiment of the present disclosure.

[0010] Figure 3 It is a diagram showing the structure of a server involved in an embodiment of the present disclosure.

[0011] Figure 4 This is a diagram showing an example of a setting status table stored in the server according to the embodiment of the present disclosure.

[0012] Figure 5 This is a diagram showing an example of a contact table stored in a server according to an embodiment of the present disclosure.

[0013] Figure 6 This is a diagram showing an example of a management table stored in the server according to the embodiment of the present disclosure.

[0014] Figure 7 This is a diagram showing an example of a contact table updated by the server according to the embodiment of the present disclosure.

[0015] Figure 8 This is a diagram showing an example of a setting status table after being updated by the server according to the embodiment of the present disclosure.

[0016] Fig. 9 This is a diagram showing another example of the setting status table after being updated by the server according to the embodiment of the present disclosure.

[0017] Fig.10This is a flowchart that defines the operation procedure of setting processing and updating processing performed by the server according to the embodiment of the present disclosure.

[0018] Fig.11 This is a flowchart that defines the operation procedure of processing performed by the vehicle-mounted device according to the embodiment of the present disclosure.

[0019] Fig.12 This is a diagram showing an example of a sequence of processes of a server, an in-vehicle device, and a terminal device in a communication system according to an embodiment of the present disclosure.

[0020] Fig.13 This is a diagram showing another example of the sequence of processes of the server, the in-vehicle device, and the terminal device in the communication system according to the embodiment of the present disclosure. DETAILED DESCRIPTION

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

[0022] By adding a vehicle-mounted device after the vehicle leaves the factory, various functions can be added to the vehicle. In addition, for example, the user of the vehicle sometimes changes the object of the vehicle-mounted device.

[0023] Since there are many vehicles to which the vehicle-mounted device is installed and vehicles to which the vehicle-mounted device is newly installed, it is not easy to maintain compatibility as a system so as to be able to collect vehicle information. In addition, since the vehicle-mounted device can be retrofitted to various vehicles, management such as associating the vehicle-mounted device, the vehicle, and the user of the vehicle becomes complicated.

[0024] The present disclosure is made to solve the above-mentioned technical problems, and its purpose is to provide a management device, an on-board device, a management method, and a management program that can more reliably collect vehicle information of a mounted object from an on-board device.

[0025] <Effects of the Present Disclosure>

[0026] According to the present disclosure, it is possible to more reliably collect vehicle information of a mounted object from the vehicle-mounted device.

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

[0028] Hereinafter, embodiments of the present disclosure will be described by summarizing them.

[0029] (1) The management device involved in the embodiment of the present disclosure is a management device as follows, which comprises: a receiving unit, which receives vehicle identification information for identifying the vehicle from a vehicle-mounted device installed in the vehicle; a setting unit, which performs setting processing of setting a computer program corresponding to the vehicle identification information received by the receiving unit as a first computer program, and the first computer program is used to process vehicle information related to the vehicle in the management device; and an update request unit, which performs update request processing of sending update request information to the vehicle-mounted device, and the update request information is used to request an update to a second computer program corresponding to the vehicle identification information received by the receiving unit, and the second computer program is used for the vehicle-mounted device to obtain the vehicle information and send the acquired vehicle information to the management device to provide it to the first computer program set by the setting unit.

[0030] In this way, according to the structure in which the first computer program corresponding to the vehicle identification information from the vehicle is set in the management device, and the update request information for requesting to update to the second computer program corresponding to the vehicle identification information is sent to the vehicle-mounted device, even when the vehicle-mounted device is installed after the vehicle leaves the factory and the object of the vehicle-mounted device is changed, the vehicle information can be obtained and sent in the vehicle-mounted device, and the vehicle information received from the vehicle-mounted device can be processed in the management device. Therefore, the vehicle information of the object of installation can be collected from the vehicle-mounted device more reliably.

[0031] (2) In the above (1), the receiving unit may also receive change identification information, wherein the change identification information is the vehicle identification information for identifying the vehicle equipped with the vehicle-mounted device and is sent from the vehicle-mounted device whose carrying object has been changed. The setting unit may also set the computer program corresponding to the change identification information as a third computer program for processing vehicle information related to the vehicle equipped with the vehicle-mounted device in the management device. The update request unit may also send the update request information for requesting an update to a fourth computer program corresponding to the change identification information to the vehicle-mounted device, wherein the fourth computer program is used for the vehicle-mounted device to obtain the vehicle information and send the obtained vehicle information to the management device to provide it to the sending processing of the third computer program set by the setting unit.

[0032] According to such a configuration, even when the vehicle to which the vehicle-mounted device is to be mounted is changed, vehicle information of the new vehicle to which the vehicle-mounted device is to be mounted can be collected more reliably from the vehicle-mounted device.

[0033] (3) In the above (2), the setting unit may also set the computer program corresponding to the change identification information to the third computer program when the structure of the in-vehicle network in the vehicle before the change of the mounting object, i.e., the network before the change, is different from the structure of the in-vehicle network in the vehicle after the change of the mounting object, i.e., the network after the change, and the update request unit may also send the update request information for requesting an update to the fourth computer program corresponding to the change identification information to the vehicle-mounted device when the structure of the network before the change is different from the structure of the network after the change.

[0034] According to such a configuration, even when the configuration of the vehicle network in the vehicle that is the new installation target of the vehicle-mounted device is different from the configuration of the vehicle network in the vehicle before the installation target of the vehicle-mounted device was changed, vehicle information of the new installation target can be collected more reliably from the vehicle-mounted device.

[0035] (4) In any one of the above (1) to (3), the management device may also include a sending unit, and when the setting processing of the setting unit is completed and the receiving unit receives update completion information from the vehicle-mounted device indicating that the update to the second computer program has been completed, the sending unit sends permission information to the vehicle-mounted device indicating that the vehicle-mounted device is allowed to execute the sending processing.

[0036] According to such a configuration, after confirming that the update to the second computer program has been completed, desired vehicle information can be reliably transmitted from the vehicle-mounted device to the management device, and vehicle information of appropriate content can be processed in the management device.

[0037] (5) In any one of the above (1) to (4), the receiving unit may also receive device identification information for identifying the vehicle-mounted device from the vehicle-mounted device, and the management device may also further include: a storage unit for storing user corresponding information and device corresponding information, the user corresponding information indicating the correspondence between the user identification information for identifying the user of the vehicle and the vehicle identification information, and the device corresponding information indicating the correspondence between the device identification information and the vehicle identification information; and a sending unit for sending, based on the user corresponding information in the storage unit, mounting information indicating that the vehicle-mounted device having the receiving identification information has been mounted on the vehicle to the user identified by the user identification information corresponding to the vehicle identification information received by the receiving unit, when the device identification information received by the receiving unit, i.e., the receiving identification information, is not registered in the device corresponding information.

[0038] According to such a configuration, the installation of the vehicle-mounted device indicated by the installation information from the management device can be confirmed by the user of the vehicle to which the vehicle-mounted device is to be installed, thereby improving safety.

[0039] (6) In the above (5), the setting unit may perform the setting process when the receiving unit receives consent information indicating consent for the vehicle-mounted device having the receiving identification information to be connected to the vehicle as response information from the user regarding the mounted information, or the update request unit may perform the update request process when the receiving unit receives the consent information.

[0040] According to such a configuration, the first program can be set and the second program can be updated for the vehicle-mounted device approved by the user of the vehicle to collect vehicle information of the vehicle, thereby further improving safety.

[0041] (7) In any one of the above (1) to (6), the receiving unit may also receive device identification information for identifying the vehicle-mounted device from the vehicle-mounted device, and the management device may also have a storage unit, which stores device corresponding information indicating the correspondence between the device identification information and the vehicle identification information. It may also be that when the device identification information received by the receiving unit, i.e., the received identification information, is not registered in the device corresponding information, the setting unit performs the setting processing, and it may also be that when the received identification information is not registered in the device corresponding information, the update request unit performs the update request processing.

[0042] According to such a configuration, it is possible to suppress repeated setting of the first computer program and updating of the second computer program for each of the vehicle-mounted devices that have been mounted on the vehicle and for which the second computer program has been updated.

[0043] (8) The vehicle-mounted device involved in the embodiment of the present disclosure sends and receives information with the above-mentioned management device in any one of the above (1) to (7), and the vehicle-mounted device comprises: an acquisition unit, which acquires the vehicle identification information used to identify the vehicle equipped with the vehicle-mounted device; an update unit, which updates the computer program stored in the vehicle-mounted device for performing the sending process to the second computer program corresponding to the vehicle identification information acquired by the acquisition unit based on the update request information received from the management device; and a sending processing unit, which performs the sending process by executing the second computer program, and when the update unit completes the update process, sends update completion information to the management device.

[0044] According to such a structure, even when the vehicle is equipped with the vehicle-mounted device after leaving the factory or when the object to be equipped with the vehicle-mounted device is changed, the vehicle information can be acquired and sent in the vehicle-mounted device. Therefore, the vehicle information of the object to be equipped can be collected more reliably from the vehicle-mounted device. In addition, it is possible to easily confirm in the management device that the update of the second computer program has been completed.

[0045] (9) The vehicle-mounted device involved in the embodiment of the present disclosure is installed on a vehicle and sends and receives information with a management device. The vehicle-mounted device comprises: an acquisition unit, which acquires vehicle identification information for identifying the vehicle on which the vehicle-mounted device is installed; an update unit, which performs update processing based on update request information received from the management device, the update request information requests updating of a computer program used by the vehicle-mounted device to perform a sending processing for acquiring vehicle information related to the vehicle and sending it to the management device, the update processing updates the computer program stored in the vehicle-mounted device to a new computer program for performing the sending processing corresponding to the vehicle identification information acquired by the acquisition unit; and a sending processing unit, which performs the sending processing by executing the updated computer program, and when the update processing is completed, the update unit sends update completion information to the management device.

[0046] According to such a structure, even when the vehicle is equipped with an onboard device after leaving the factory or when the object to be equipped with the onboard device is changed, vehicle information can be acquired and sent in the onboard device. Therefore, the vehicle information of the object to be equipped can be collected more reliably from the onboard device. In addition, the completion of the update of the computer program can be easily confirmed in the management device.

[0047] (10) The management method involved in the embodiment of the present disclosure is a management method in a management device, and the management method includes the following steps: receiving vehicle identification information for identifying the vehicle from a vehicle-mounted device installed in the vehicle; performing setting processing to set a computer program corresponding to the received vehicle identification information as a first computer program, and the first computer program is used to process vehicle information related to the vehicle in the management device; and performing update request processing to send update request information to the vehicle-mounted device, and the update request information is used to request an update to a second computer program corresponding to the received vehicle identification information, and the second computer program is used for the vehicle-mounted device to obtain the vehicle information and send the acquired vehicle information to the management device to provide it to the first computer program set in the management device.

[0048] In this way, according to the structure in which the first computer program corresponding to the vehicle identification information from the vehicle is set in the management device, and the update request information for requesting to update to the second computer program corresponding to the vehicle identification information is sent to the vehicle-mounted device, even when the vehicle-mounted device is installed after the vehicle leaves the factory and the object of the vehicle-mounted device is changed, the vehicle information can be obtained and sent in the vehicle-mounted device, and the vehicle information received from the vehicle-mounted device can be processed in the management device. Therefore, the vehicle information of the object of installation can be collected from the vehicle-mounted device more reliably.

[0049] (11) The management program involved in the embodiment of the present disclosure is used in a management device, and the management program is a program for causing a computer to function as a receiving unit, a setting unit, and an update request unit, the receiving unit receiving vehicle identification information for identifying the vehicle from a vehicle-mounted device mounted on the vehicle, the setting unit performing setting processing for setting a computer program corresponding to the vehicle identification information received by the receiving unit as a first computer program, the first computer program being used to process vehicle information related to the vehicle in the management device, the update request unit performing update request processing for sending update request information to the vehicle-mounted device, the update request information being used to request an update to a second computer program corresponding to the vehicle identification information received by the receiving unit, the second computer program being used for the vehicle-mounted device to obtain the vehicle information and send the obtained vehicle information to the management device to provide it to the first computer program set by the setting unit.

[0050] In this way, according to the structure in which the first computer program corresponding to the vehicle identification information from the vehicle is set in the management device, and the update request information for requesting to update to the second computer program corresponding to the vehicle identification information is sent to the vehicle-mounted device, even when the vehicle-mounted device is installed after the vehicle leaves the factory and the object of the vehicle-mounted device is changed, the vehicle information can be obtained and sent in the vehicle-mounted device, and the vehicle information received from the vehicle-mounted device can be processed in the management device. Therefore, the vehicle information of the object of installation can be collected from the vehicle-mounted device more reliably.

[0051] One aspect of the present disclosure can be realized not only as a management device including such a characteristic processing unit but also as a semiconductor integrated circuit realizing a part or all of the management device, or as a system including the management device.

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

[0053] The following is an explanation of the embodiments of the present disclosure using the accompanying drawings. It should be noted that the same or corresponding parts in the drawings are marked with the same reference numerals, and their descriptions are not repeated. In addition, at least a part of the embodiments described below can also be arbitrarily combined.

[0054] [Communication System]

[0055] Figure 1 1 is a diagram showing a configuration of a communication system according to an embodiment of the present disclosure. Figure 1 The communication system 501 includes a server 101, one or more vehicle-mounted devices 201, and one or more terminal devices 301. The server 101 and each vehicle-mounted device 201 transmit and receive information via an external network 151 such as the Internet. The server 101 and each terminal device 301 transmit and receive information via an external network 151 such as the Internet. The vehicle-mounted device 201 is mounted on the vehicle 1. The server 101 is an example of a management device.

[0056] The server 101 and the terminal device 301 are used, for example, by a company or an individual who manages the operation of the vehicle 1. The terminal device 301 is, for example, a communication terminal device such as a smartphone or a tablet.

[0057] The server 101 receives vehicle information related to the corresponding vehicle 1 from one or more vehicle-mounted devices 201 .

[0058] The server 101 performs an analysis process for analyzing the vehicle information received from the vehicle-mounted device 201. Specifically, the server 101 performs the analysis process by executing a server-side program for processing the vehicle information.

[0059] The terminal device 301 receives input of various information from the user of the vehicle 1 and transmits the received information to the vehicle-mounted device 201. The terminal device 301 may transmit various information received from the user of the vehicle 1 to the server 101 via the external network 151.

[0060] [In-vehicle device]

[0061] Figure 2 2 is a diagram showing a configuration of a vehicle-mounted device according to an embodiment of the present disclosure. Figure 2 The in-vehicle device 201 is connected to a plurality of in-vehicle devices 211 via a CAN bus 51 conforming to the CAN (Controller Area Network) (registered trademark) standard, for example.

[0062] The in-vehicle equipment 211 includes, for example, an automatic driving ECU (Electronic Control Unit), an engine ECU, a door lock ECU, a TCU (Telematics Communication Unit), a sensor, a navigation device, a human-machine interface, and a camera.

[0063] exist Figure 2 In the illustrated example, the in-vehicle device 201 is connected to a plurality of in-vehicle devices 211 , namely, in-vehicle devices 211A and 211B.

[0064] The vehicle-mounted device 201 includes a first communication unit 11, a setting processing unit 12, a second communication unit 13, an acquisition unit 14, and a storage unit 15. The first communication unit 11 includes a receiving unit 21, a transmission processing unit 22, and an updating unit 23. Part or all of the first communication unit 11, the setting processing unit 12, the second communication unit 13, and the acquisition unit 14 are implemented, for example, by a processing circuit (Circuitry) including one or more processors. The storage unit 15 is, for example, a non-volatile memory included in the above-mentioned processing circuit.

[0065] (First Communications Department)

[0066] The first communication unit 11 communicates with the server 101 via the external network 151 by wirelessly communicating with a wireless base station (not shown) according to a communication method such as WiFi (registered trademark), LTE (Long Term Evolution) (registered trademark) or 5G. It should be noted that the first communication unit 11 is not limited to a structure that communicates with the server 101 through a wireless base station and an external network 151, and may also be a structure that communicates with the server 101 through a wired line. In addition, the first communication unit 11 may also be a structure that further communicates with the server 101 through other vehicle-mounted devices.

[0067] The transmission processing unit 22 in the first communication unit 11 performs a transmission process of acquiring vehicle information related to the vehicle 1 and transmitting the acquired vehicle information to the server 101. The vehicle information includes information related to the travel of the vehicle 1, for example.

[0068] Specifically, the transmission processing unit 22 obtains, for example, the position information and vehicle speed information of the vehicle 1. It should be noted that the vehicle information is not limited to the position information and vehicle speed information, but may also be driving control information such as braking operation and steering operation in the vehicle 1. In addition, the vehicle information is not limited to information related to the travel of the vehicle 1, but may also be information representing an image captured by a camera mounted on the vehicle 1, and information representing measurement results of a sensor mounted on the vehicle 1.

[0069] The transmission processing unit 22 communicates with one or more in-vehicle devices 211 according to the CAN standard, for example.

[0070] exist Figure 2 In the example shown, the transmission processing unit 22 is connected to the vehicle-mounted devices 211A and 211B respectively via two CAN buses 51, namely, CAN buses 51A and 51B. It should be noted that the vehicle-mounted device 201 is not limited to the structure in which two CAN buses 51 are connected to the transmission processing unit 22, and any structure in which one or more CAN buses 51 are connected may be used.

[0071] In addition, the vehicle-mounted device 201 and each vehicle-mounted equipment 211 are not limited to communicating in accordance with the CAN standard, but can also be a structure that communicates in accordance with standards such as CAN FD (CAN with Flexible Data Rate), Ethernet (registered trademark), FlexRay (registered trademark), MOST (Media Oritend System Transport) (registered trademark) and LIN (Local Interconnect Network).

[0072] The in-vehicle device 211 transmits its own vehicle information to the in-vehicle apparatus 201. The vehicle information transmitted from each in-vehicle device 211 via the CAN bus 51 is carried in a CAN frame to which a CAN-ID (Identifier) ​​indicating the type of data and the like is added.

[0073] The storage unit 15 stores a vehicle-side program for causing the vehicle-mounted device 201 to perform a transmission process. The transmission processing unit 22 executes the vehicle-side program stored in the storage unit 15 to perform the transmission process.

[0074] (Settings Processing Unit)

[0075] The setting processing unit 12 performs data setting processing related to the transmission of vehicle information. For example, as the data setting processing, the setting processing unit 12 sets the type of vehicle information to be transmitted to the server 101.

[0076] Hereinafter, an example will be described in which the setting processing unit 12 sets the vehicle-mounted device 201 thereof to transmit the vehicle information of the vehicle-mounted device 211A to the server 101. Here, it is assumed that the CAN-ID of the CAN frame carrying the vehicle information of the vehicle-mounted device 211A is "001".

[0077] When the transmission processing unit 22 is periodically or irregularly acquiring vehicle information transmitted from the in-vehicle device 211A, the setting processing unit 12 sets the transmission processing unit 22 to transmit the vehicle information included in the CAN frame having the CAN-ID “001” to the server 101 .

[0078] On the other hand, when the transmission processing unit 22 does not obtain the vehicle information from the vehicle-mounted device 211A, the setting processing unit 12 requests the vehicle-mounted device 211A to send the vehicle information via the transmission processing unit 22 as a data setting process. The vehicle-mounted device 211A receives the request from the vehicle-mounted device 201 and periodically or irregularly sends the CAN frame with the CAN-ID "001" to the vehicle-mounted device 201. In addition, the setting processing unit 12 sets the transmission processing unit 22 to send the vehicle information included in the CAN frame with the CAN-ID "001" to the server 101.

[0079] (Second Communications Department)

[0080] The second communication unit 13 communicates with the terminal device 301 in accordance with a USB (Universal Serial Bus) communication method, for example. It should be noted that the second communication unit 13 and the terminal device 301 may also be configured to perform wireless communication in accordance with standards such as Bluetooth (registered trademark).

[0081] The second communication unit 13 transmits the vehicle information to the terminal device 301. More specifically, the transmission processing unit 22 transmits the acquired vehicle information to the server 101 as described above, and outputs the vehicle information to the second communication unit 13. The second communication unit 13 transmits the vehicle information received from the transmission processing unit 22 to the terminal device 301.

[0082] [server]

[0083] Figure 3 2 is a diagram showing the configuration of a server according to an embodiment of the present disclosure. Figure 3 The server 101 includes a communication unit 31, an analysis unit 32, a processing unit 33, a setting unit 34, and a storage unit 35. The communication unit 31 includes a receiving unit 41, an update request unit 42, and a sending unit 43. Part or all of the communication unit 31, the analysis unit 32, the processing unit 33, and the setting unit 34 are implemented by, for example, a processing circuit including one or more processors. The storage unit 35 is, for example, a non-volatile memory included in the above-mentioned processing circuit.

[0084] The receiving unit 41 receives the vehicle information from the vehicle-mounted device 201. The receiving unit 41 stores the vehicle information received from the vehicle-mounted device 201 in the storage unit 35.

[0085] The analysis unit 32 executes the server-side program to perform analysis processing of the vehicle information received from the vehicle-mounted device 201. For example, the analysis unit 32 performs various analyses such as detecting abnormalities related to the vehicle 1 based on the vehicle information received from the vehicle-mounted device 201.

[0086] [Explanation of technical issues]

[0087] By adding a vehicle-mounted device after the vehicle leaves the factory, various functions can be added to the vehicle. In addition, for example, the user of the vehicle sometimes changes the object of the vehicle-mounted device.

[0088] There are many types of vehicles that are equipped with on-board devices and vehicles that are newly installed. For example, the structure of the on-board network may be different between vehicles. Specifically, depending on the type of vehicle, the type of on-board equipment installed and the type of communication standard used to send and receive information between on-board devices may be different. For this reason, after the on-board device is installed in the vehicle, it may not be able to obtain vehicle information even if the vehicle-side program stored in the device is executed. In this case, the server cannot collect vehicle information from the on-board device and cannot continue to analyze and process the vehicle information. In other words, it is not easy to maintain compatibility as a system so that vehicle information can be collected.

[0089] Furthermore, in the server, since the in-vehicle device can be retrofitted to various vehicles, management such as associating the in-vehicle device, the vehicle, and the user of the vehicle becomes complicated.

[0090] In this regard, the communication system 501 involved in the embodiment of the present disclosure solves such technical problems through the following structure and operation.

[0091] [In-vehicle device]

[0092] Refer again Figure 2 The acquisition unit 14 in the vehicle-mounted device 201 periodically or irregularly acquires device identification information (hereinafter also referred to as "vehicle-mounted device ID") for identifying the vehicle-mounted device 201 itself. For example, when the vehicle-mounted device 201 itself is started by switching the ignition power of the vehicle 1 from the off state to the on state, the acquisition unit 14 acquires the vehicle-mounted device ID stored in the storage unit 15. The acquisition unit 14 outputs the acquired vehicle-mounted device ID to the transmission processing unit 22. The vehicle-mounted device ID is an ID inherent to each vehicle-mounted device 201.

[0093] The acquisition unit 14 acquires vehicle identification information (hereinafter also referred to as “vehicle ID”) for identifying the vehicle 1 on which the vehicle-mounted device 201 is mounted, regularly or irregularly. The vehicle ID is an ID unique to each vehicle 1 .

[0094] More specifically, the vehicle 1 includes a vehicle ID storage unit 212 that stores its own vehicle ID. For example, when the ignition power of the vehicle 1 is switched from an OFF state to an ON state to start the vehicle-mounted device 201, the acquisition unit 14 acquires the vehicle ID stored in the vehicle ID storage unit 212. The acquisition unit 14 outputs the acquired vehicle ID to the transmission processing unit 22.

[0095] The transmission processing unit 22 transmits the ID acquisition information including the vehicle-mounted device ID and the vehicle ID received from the acquisition unit 14 to the server 101. It should be noted that the vehicle ID may be pre-registered in the storage unit 15 of the vehicle-mounted device 201 by, for example, a dealer. In this case, when the vehicle-mounted device 201 is activated, the acquisition unit 14 acquires the vehicle ID stored in the storage unit 15.

[0096] [server]

[0097] Refer again Figure 3 , the receiving unit 41 receives the ID acquisition information from the vehicle-mounted device 201. That is, the receiving unit 41 receives the vehicle-mounted device ID and the vehicle ID from the vehicle-mounted device 201. The receiving unit 41 stores the received ID acquisition information in the storage unit 35, and outputs a notification to the processing unit 33 indicating that the ID acquisition information has been received.

[0098] The storage unit 35 stores a setting status table Tb10 including device correspondence information indicating a correspondence relationship between the vehicle-mounted device ID and the vehicle ID.

[0099] Figure 4 This is a diagram showing an example of a setting status table stored in the server according to the embodiment of the present disclosure.

[0100] exist Figure 4 In the setting status table Tb10 shown, the vehicle ID corresponding to the vehicle-mounted device ID "R1" is "V1", the vehicle ID corresponding to the vehicle-mounted device ID "R2" is "V2", and the vehicle ID corresponding to the vehicle-mounted device ID "R3" is "V3".

[0101] When the processing unit 33 receives a notification from the receiving unit 41 that the ID acquisition information has been received, it refers to the setting status table Tb10 and the ID acquisition information stored in the storage unit 35. Then, the processing unit 33 performs an ID confirmation process to confirm whether the vehicle-mounted device ID included in the ID acquisition information, that is, the vehicle-mounted device ID received by the receiving unit 41 (hereinafter also referred to as "received identification information") is registered in the setting status table Tb10.

[0102] Here, the processing unit 33 checks in the ID confirmation process whether the correspondence relationship between the received identification information and the vehicle ID (hereinafter also referred to as “ID correspondence relationship”) is registered in the setting status table Tb10. Then, the processing unit 33 notifies the transmission unit 43 of the confirmation result.

[0103] (Request for user information)

[0104] Reference Figure 2 and Figure 3 When the sending unit 43 receives a notification from the processing unit 33 indicating that the ID correspondence is not registered in the setting status table Tb10, it sends an information request notification for requesting user information related to the user of the vehicle 1 to the vehicle-mounted device 201. The user information includes, for example, user identification information (hereinafter also referred to as "user ID") for identifying the user of the vehicle 1, information indicating a method of contacting the user, and a contact address of the user.

[0105] (Sending of user information)

[0106] In the vehicle-mounted device 201 , upon receiving the information request notification from the server 101 , the receiving unit 21 outputs a notification to the effect that the information request notification has been received to the second communication unit 13 .

[0107] Upon receiving the notification from the receiving unit 21 indicating that the information request notification has been received, the second communication unit 13 transmits transmission request information indicating a request to transmit the user information to the vehicle-mounted device 201 to the terminal device 301 .

[0108] When receiving the transmission request information from the in-vehicle device 201 , the terminal device 301 transmits the user information to the in-vehicle device 201 .

[0109] More specifically, for example, when the terminal device 301 receives the transmission request information from the vehicle-mounted device 201 , it prompts the user of the vehicle 1 to input the user information. Then, when the terminal device 301 accepts the input of the user information from the user of the vehicle 1 , it transmits the accepted user information to the vehicle-mounted device 201 .

[0110] The second communication unit 13 outputs the received user information to the transmission processing unit 22. Then, the transmission processing unit 22 transmits the user information received from the second communication unit 13 to the server 101.

[0111] In the server 101 , upon receiving the user information from the vehicle-mounted device 201 , the receiving unit 41 stores the received user information in the storage unit 35 and outputs a notification to the effect that the user information has been received to the processing unit 33 .

[0112] When the processing unit 33 receives a notification from the receiving unit 41 indicating that the user information has been received, it performs a user registration process based on the user information and ID acquisition information stored in the storage unit 35 to register the user ID included in the user information and the vehicle ID included in the ID acquisition information in the setting status table Tb10 in correspondence with each other.

[0113] (Contact Form)

[0114] When the processing unit 33 receives a notification from the receiving unit 41 that the user information has been received, it performs a table update process of updating the contact table Tb20 indicating the correspondence between the user information and the vehicle ID included in the ID acquisition information based on the user information and the ID acquisition information stored in the storage unit 35. The contact table Tb20 includes user correspondence information indicating the correspondence between the user ID and the vehicle ID.

[0115] Figure 5 This is a diagram showing an example of a contact table stored in a server according to an embodiment of the present disclosure.

[0116] exist Figure 5 In the contact table Tb20 shown, the user information corresponding to the vehicle ID "V1" includes the user ID "U1", the contact method "email" and the contact address. The user information corresponding to the vehicle ID "V2" includes the user ID "U2", the contact method "telephone" and the contact address. The user information corresponding to the vehicle ID "V3" includes the user ID "U3", the contact method "email" and the contact address. It should be noted that the contact table Tb20 may also be pre-registered in the storage unit 35 by, for example, a dealer or the like.

[0117] When the table update process is completed, the processing unit 33 outputs a notification to the effect that the contact table Tb20 has been updated to the transmitting unit 43. On the other hand, when the ID correspondence is registered in the setting status table Tb10, the processing unit 33 does not perform the user registration process and the table update process.

[0118] (Information)

[0119] Reference Figure 3 and Figure 5 When the received identification information is not registered in the setting status table Tb10, the sending unit 43 sends the mounting information indicating that the vehicle-mounted device 201 having the received identification information has been mounted on the vehicle 1 to the user identified by the user ID corresponding to the vehicle ID received by the receiving unit 41 based on the user corresponding information in the storage unit 35.

[0120] More specifically, when the sending unit 43 receives a notification from the processing unit 33 that the contact table Tb20 has been updated, it refers to the contact table Tb20 and the ID acquisition information stored in the storage unit 35 to determine the user ID corresponding to the vehicle ID included in the ID acquisition information. That is, when the ID correspondence relationship is not registered in the setting status table Tb10, the sending unit 43 refers to the contact table Tb20 and the ID acquisition information stored in the storage unit 35 to determine the user ID corresponding to the vehicle ID included in the ID acquisition information. Then, the sending unit 43 sends the mounting information to the user having the determined user ID through the contact method corresponding to the user ID included in the contact table Tb20.

[0121] When the user receives the mounting information from the server 101, the user determines whether to agree to the connection between the vehicle-mounted device 201 indicated in the mounting information and the vehicle 1. Then, when the terminal device 301 receives the input of the consent information from the user, it transmits the received consent information to the vehicle-mounted device 201.

[0122] Refer again Figure 2 In the vehicle-mounted device 201, when the second communication unit 13 receives the consent information from the terminal device 301, the second communication unit 13 outputs the received consent information to the transmission processing unit 22. The transmission processing unit 22 transmits the consent information received from the second communication unit 13 to the server 101.

[0123] Refer again Figure 3 In the server 101, if the receiving unit 41 receives consent information from the user indicating consent to the connection between the vehicle-mounted device 201 having receiving identification information and the vehicle 1 as response information from the user regarding the mounted information, a notification indicating that the consent information has been received (hereinafter also referred to as "consent reception notification") is output to the processing unit 33, the setting unit 34 and the update request unit 42.

[0124] When receiving the reception approval notification from the receiving unit 41, the processing unit 33 refers to the setting status table Tb10 and the ID acquisition information stored in the storage unit 35. Then, the processing unit 33 checks whether the vehicle-mounted device ID included in the ID acquisition information, that is, the reception identification information, is registered in the setting status table Tb10.

[0125] When the received identification information is registered in the setting status table Tb10, the processing unit 33 determines that the vehicle-mounted device 201 having the received identification information has been changed to the vehicle 1 having the vehicle ID received by the receiving unit 41. That is, the processing unit 33 determines that the vehicle ID received by the receiving unit 41 is the vehicle ID of the vehicle 1 on which the vehicle-mounted device 201 is mounted, which is sent from the vehicle-mounted device 201 whose mounting target has been changed (hereinafter, also referred to as "changed identification information").

[0126] On the other hand, when the reception identification information is not registered in the setting status table Tb10, the processing unit 33 determines that the vehicle-mounted device 201 having the reception identification information has not been changed but is mounted on the vehicle for the first time.

[0127] Here, it is assumed that the processing unit 33 confirms that the received identification information is not registered in the setting status table Tb10. The processing unit 33 notifies the setting unit 34 and the update request unit 42 of the confirmation result.

[0128] (Settings)

[0129] When the setting unit 34 receives a notification of receiving consent from the receiving unit 41 and a notification (hereinafter also referred to as "non-registration notification") from the processing unit 33 that the receiving identification information is not registered in the setting status table Tb10, the setting unit 34 selects a server-side program to be executed corresponding to the vehicle type determined by the vehicle ID received by the receiving unit 41 from the plurality of server-side programs. That is, when the receiving unit 41 receives the consent information and the receiving identification information is not registered in the setting status table Tb10, the setting unit 34 performs a setting process of setting the computer program corresponding to the vehicle type determined by the vehicle ID received by the receiving unit 41 as the server-side program.

[0130] For example, the setting unit 34 uses a management table Tb30 including a correspondence relationship between a vehicle ID and a server-side program in the setting process. The management table Tb30 is stored in the storage unit 35 .

[0131] Figure 6 This is a diagram showing an example of a management table stored in the server according to the embodiment of the present disclosure.

[0132] exist Figure 6 In the management table Tb30 shown, the server-side program corresponding to the vehicle type "AAA" determined by the vehicle ID "V1" and the server-side program corresponding to the vehicle type "FFF" determined by the vehicle ID "V6" are "spg-1". In addition, the server-side program corresponding to the vehicle type "BBB" determined by the vehicle ID "V2" and the server-side program corresponding to the vehicle type "EEE" determined by the vehicle ID "V5" are "spg-2". In addition, the server-side program corresponding to the vehicle type "CCC" determined by the vehicle ID "V3" is "spg-3", and the server-side program corresponding to the vehicle type "DDD" determined by the vehicle ID "V4" is "spg-4". The server-side programs "spg-1", "spg-2", "spg-3", and "spg-4" are examples of the first computer program.

[0133] Reference Figure 3 and Figure 6If the setting unit 34 receives a notification of acceptance of reception from the receiving unit 41 and a notification of non-registration from the processing unit 33, it refers to the management table Tb30 and ID acquisition information stored in the storage unit 35 to determine the server-side program corresponding to the vehicle ID included in the ID acquisition information.

[0134] The setting unit 34 determines the determined server-side program as a computer program for processing vehicle information related to the vehicle 1 of the model determined by the vehicle ID received by the receiving unit 41. Then, the setting unit 34 registers the determined server-side program in the corresponding manner to the vehicle ID received by the receiving unit 41. Figure 4 In the setting status table Tb10 shown.

[0135] For example, Figure 4 As shown, the server-side program "spg-1" corresponds to the vehicle ID "V1", the server-side program "spg-2" corresponds to the vehicle ID "V2", and the server-side program "spg-3" corresponds to the vehicle ID "V3". Figure 4 The "vehicle side procedure" shown will be described below.

[0136] When the setting process is completed, the setting unit 34 outputs setting completion information to the transmission unit 43 .

[0137] (Update Request Section)

[0138] When the receiving unit 41 receives the consent information and the received identification information is not registered in the setting status table Tb10, the update request unit 42 performs update request processing to send the update request information to the vehicle-mounted device 201. The update request information is used to request an update to a computer program corresponding to the vehicle ID received by the receiving unit 41, that is, a vehicle-side program used for sending processing.

[0139] More specifically, upon receiving a notification of acceptance of reception from the receiving unit 41 and receiving a notification from the processing unit 33 that the reception identification information is not registered in the setting status table Tb10 , the setting unit 34 performs update request processing.

[0140] Here, the management table Tb30 in the storage unit 35 includes a correspondence relationship between the vehicle ID and the vehicle-side program.

[0141] exist Figure 6In the management table Tb30 shown, the vehicle-side program corresponding to the vehicle IDs "V1" and "V6" is "vpg-1", the vehicle-side program corresponding to the vehicle IDs "V2" and "V5" is "vpg-2", the vehicle-side program corresponding to the vehicle ID "V3" is "vpg-3", and the vehicle-side program corresponding to the vehicle ID "V4" is "vpg-4". The vehicle-side programs "vpg-1", "vpg-2", "vpg-3", and "vpg-4" are examples of the second computer program.

[0142] Upon receiving the acceptance notification from the receiving unit 41 and the non-registration notification from the processing unit 33 , the update request unit 42 refers to the management table Tb30 and the ID acquisition information stored in the storage unit 35 to identify the vehicle-side program corresponding to the vehicle ID included in the ID acquisition information.

[0143] Then, the update request unit 42 sends update request information including, for example, a URL (Uniform Resource Locater) indicating a download source of the determined vehicle-side program to the vehicle-mounted device 201. It should be noted that the update request information may also include a vehicle-side program corresponding to the vehicle ID received by the receiving unit 41 instead of including the above-mentioned URL.

[0144] Furthermore, the update request unit 42 registers the identified vehicle-side program in the setting status table Tb10 in association with the vehicle ID received by the receiving unit 41 .

[0145] For example, Figure 4 As shown, the vehicle-side program "vpg-1" corresponds to the vehicle ID "V1", the vehicle-side program "vpg-2" corresponds to the vehicle ID "V2", and the vehicle-side program "vpg-3" corresponds to the vehicle ID "V3".

[0146] (Update process performed by the vehicle-mounted device)

[0147] Refer again Figure 2 The update unit 23 in the vehicle-mounted device 201 performs update processing to update the vehicle-side program stored in the vehicle-mounted device 201 to a new vehicle-side program (hereinafter also referred to as an "update program") corresponding to the vehicle ID acquired by the acquisition unit 14 based on the update request information received from the server 101.

[0148] More specifically, upon receiving the update request information from the server 101 , the receiving unit 21 outputs the received update request information to the updating unit 23 .

[0149] Upon receiving the update request information from the receiving unit 21 , the update unit 23 outputs download request information for requesting download of the update program to the receiving unit 21 .

[0150] When receiving the download request information from the update unit 23, the receiving unit 21 accesses the URL included in the update request information received from the server 101 to download the update program.

[0151] When the update process is completed, the update unit 23 sends update completion information to the server 101. More specifically, the receiving unit 21 outputs a notification to the effect that the update program has been downloaded to the update unit 23. Upon receiving the notification from the receiving unit 21, the update unit 23 sends the update completion information to the server 101. In addition, the receiving unit 21 stores the downloaded update program in the storage unit 15.

[0152] Refer again Figure 3 In the server 101 , when the receiving unit 41 receives the update completion information from the vehicle-mounted device 201 , it outputs a notification to the effect that the update completion information has been received to the sending unit 43 .

[0153] When the sending unit 43 receives the setting completion information from the setting unit 34 and receives the notification that the update completion information has been received from the receiving unit 41, the sending unit 43 sends the permission information indicating that the vehicle-mounted device 201 is allowed to execute the sending process to the vehicle-mounted device 201. That is, when the setting process of the setting unit 34 is completed and the receiving unit 41 receives the update completion information from the vehicle-mounted device 201, the sending unit 43 sends the permission information to the vehicle-mounted device 201.

[0154] Refer again Figure 2 When the receiving unit 21 receives the permission information from the server 101, it outputs a notification to the effect that the permission information has been received to the transmission processing unit 22. When the transmission processing unit 22 receives the notification to the effect that the permission information has been received from the receiving unit 21, it reads out the updated vehicle-side program, i.e., the update program, stored in the storage unit 15. The transmission processing unit 22 performs the transmission processing by executing the read update program.

[0155] [When the vehicle-mounted device is changed]

[0156] The following describes in detail the setting process and update request process performed by the server 101 when the mounted object of the vehicle-mounted device 201 is changed. Here, the case where the mounted object of the vehicle-mounted device 201 with the vehicle-mounted device ID "R2" is changed from the vehicle 1 with the vehicle ID "V2" to the vehicle 1 with the vehicle ID "V4" is described as a specific example 1.

[0157] (Specific example 1)

[0158] Refer again Figure 2 and Figure 3The acquisition unit 14 in the vehicle-mounted device 201 periodically or irregularly acquires its own vehicle-mounted device ID and the vehicle ID of the vehicle 1 that is a new mounting target (hereinafter also referred to as a “changed vehicle”).

[0159] The acquisition unit 14 outputs ID acquisition information including its own vehicle-mounted device ID and the vehicle ID of the changed vehicle to the transmission processing unit 22. The transmission processing unit 22 transmits the ID acquisition information received from the acquisition unit 14 to the server 101.

[0160] In the server 101 , the receiving unit 41 stores the ID acquisition information received from the vehicle-mounted device 201 in the storage unit 35 , and outputs a notification to the effect that the ID acquisition information has been received to the processing unit 33 .

[0161] When receiving the notification from the receiving unit 41 that the ID acquisition information has been received, the processing unit 33 performs the above-mentioned “ID confirmation processing”.

[0162] Then, in the ID confirmation process, when the ID correspondence is not registered in the setting status table Tb10, the processing unit 33 transmits the above-mentioned “information request notification” to the vehicle-mounted device 201.

[0163] When the in-vehicle device 201 receives the information request notification from the server 101 , it acquires the above-mentioned “user information” from the terminal device 301 and transmits it to the server 101 .

[0164] In the server 101 , upon receiving a notification from the receiving unit 41 that the user information has been received, the processing unit 33 performs a process of updating the above-mentioned “contact table Tb20 ”.

[0165] Furthermore, upon receiving a notification from the receiving unit 41 that the user information has been received, the processing unit 33 updates the contact table Tb20 based on the user information and ID acquisition information stored in the storage unit 35 .

[0166] Figure 7 This is a diagram showing an example of a contact table updated by the server according to the embodiment of the present disclosure.

[0167] exist Figure 7 In the updated contact table Tb20 shown in FIG. 1 , the user information corresponding to the vehicle ID “V4” of the changed vehicle includes the user ID “U2”, the contact method “telephone” and the contact address. Figure 7 In the example shown, the user ID “U2” of the user of the vehicle after the change is the same as the user of the vehicle 1 having the vehicle ID “V2” before the installation target of the vehicle-mounted device 201 is changed.

[0168] Furthermore, upon receiving a notification from the receiving unit 41 that the user information has been received, the processing unit 33 performs the above-mentioned “user registration process” to update the setting status table Tb10 stored in the storage unit 35 .

[0169] Figure 8 This is a diagram showing an example of a setting status table after being updated by the server according to the embodiment of the present disclosure.

[0170] like Figure 8 As shown, the processing unit 33 associates the vehicle ID “V4” with the user ID “U2”. That is, the processing unit 33 changes the vehicle ID corresponding to the user ID “U2” from “V2” to “V4” in the setting status table Tb10.

[0171] It should be noted that, when the ID correspondence is not registered in the setting status table Tb10, the processing unit 33 may also perform a process of outputting invalid information to the sending unit 43 in addition to the user registration process and the contact table update process, and the invalid information request invalidates the sending process of the vehicle-mounted device 201, that is, the function of acquiring and sending vehicle information. The sending unit 43 sends the invalid information received from the processing unit 33 to the vehicle-mounted device 201.

[0172] Refer again Figure 3 If the sending unit 43 receives a notification from the processing unit 33 that the contact table Tb20 has been updated and a notification that the ID correspondence has not been registered in the setting status table Tb10, it sends the installation information indicating that the vehicle-mounted device 201 with receiving identification information has been installed in the changed vehicle to the user identified by the user ID corresponding to the vehicle ID received by the receiving unit 41.

[0173] When receiving the above-mentioned “consent information” from the user as response information from the user to the installed information, the receiving unit 41 outputs a consent reception notification to the processing unit 33 , the setting unit 34 , and the update requesting unit 42 .

[0174] When the processing unit 33 receives the reception approval notification from the receiving unit 41, it refers to the ID acquisition information stored in the storage unit 35 to confirm whether the vehicle-mounted device ID included in the ID acquisition information, that is, the reception identification information, is registered in the setting status table Tb10. Here, it is assumed that the processing unit 33 confirms that the reception identification information is registered in the setting status table Tb10.

[0175] When the received identification information is registered in the setting status table Tb10, the processing unit 33 performs a network confirmation process to confirm whether the structure of the vehicle network in the vehicle 1 before the change of the mounting object (hereinafter also referred to as the "pre-change network") is the same as the structure of the vehicle network in the vehicle 1 after the change of the mounting object (hereinafter also referred to as the "post-change network") .

[0176] For example, the management table Tb30 in the storage unit 35 includes a correspondence relationship between the configuration of the in-vehicle network in the vehicle 1 and the vehicle ID.

[0177] exist Figure 6 In the management table Tb30 shown, the vehicle IDs corresponding to the structure "N1" of the vehicle network are "V1" and "V6", the vehicle IDs corresponding to the structure "N2" of the vehicle network are "V2" and "V5", the vehicle ID corresponding to the structure "N3" of the vehicle network is "V3", and the vehicle ID corresponding to the structure "N4" of the vehicle network is "V4".

[0178] Reference Figure 3 and Figure 6 When the received identification information is registered in the setting status table Tb10, the processing unit 33 refers to the setting status table Tb10 stored in the storage unit 35 to determine the vehicle ID corresponding to the received identification information (hereinafter also referred to as the "registered vehicle ID").

[0179] Then, the processing unit 33 refers to the management table Tb30 stored in the storage unit 35 to confirm whether the structure of the network before the change corresponding to the vehicle ID before the vehicle-mounted device 201 is changed and the structure of the network after the change corresponding to the change identification information are the same. The processing unit 33 notifies the setting unit 34 and the update request unit 42 of the confirmation result.

[0180] The setting unit 34 performs setting processing when receiving a notification from the processing unit 33 that the network structure before the change is different from the network structure after the change. That is, when the network structure before the change is different from the network structure after the change, the setting unit 34 sets the computer program corresponding to the vehicle model determined based on the change identification information as a server-side program for processing vehicle information related to the vehicle 1 equipped with the vehicle-mounted device 201 in the server 101.

[0181] Here, the structure of the vehicle network in the vehicle 1 of the vehicle ID "V2" before the installation object of the vehicle-mounted device 201 is changed is "N2", while the structure of the vehicle network in the vehicle 1 of the vehicle ID "V4" after the installation object is changed is "N4". That is, the structure of the network before the change is different from the structure of the network after the change. In this case, the setting unit 34 refers to the management table Tb30 stored in the storage unit 35 and sets the server-side program "spg-4" corresponding to the vehicle type "DDD" determined by the vehicle ID "V4" as the server-side program. The server-side program "spg-4" is an example of a third computer program.

[0182] Then, the setting unit 34 registers the determined server-side program in the setting status table Tb10 in correspondence with the change identification information. Figure 8 As shown, the setting unit 34 registers the server-side program "spg-4" in association with the vehicle ID "V4".

[0183] On the other hand, when receiving a notification from the processing unit 33 that the configuration of the network before the change is the same as the configuration of the network after the change, the setting unit 34 does not perform the setting process.

[0184] The update request unit 42 performs update request processing when receiving a notification from the processing unit 33 that the network structure before the change is different from the network structure after the change. That is, when the network structure before the change is different from the network structure after the change, the update request unit 42 sends update request information for requesting an update to a new vehicle-side program corresponding to the change identification information to the vehicle-mounted device 201.

[0185] Here, the update request unit 42 refers to the management table Tb30 stored in the storage unit 35, and sends update request information for requesting update to the vehicle-side program "vpg-4" corresponding to the vehicle ID "V4" to the vehicle-mounted device 201. Figure 6 As shown, the update request unit 42 registers the vehicle-side program “vpg-4” in association with the vehicle ID “V4.” The vehicle-side program “vpg-4” is an example of a fourth computer program.

[0186] On the other hand, when the update request unit 42 receives a notification from the processing unit 33 that the configuration of the network before the change is the same as the configuration of the network after the change, the update request unit 42 does not perform the update request process.

[0187] (Specific example 2)

[0188] If the setting unit 34 receives a notification from the processing unit 33 that the network structure before the change is the same as the network structure after the change, the setting unit 34 does not perform the setting process. The following is an example of a case where the vehicle 1 with the vehicle ID "V2" is changed to the vehicle 1 with the vehicle ID "V5".

[0189] As mentioned above, in Figure 6 In the management table Tb30 shown, the server-side program corresponding to the vehicle type "BBB" specified by the vehicle ID "V2" and the server-side program corresponding to the vehicle type "FFF" specified by the vehicle ID "V5" are "spg-2".

[0190] Fig. 9 It is a diagram showing another example of the setting status table after update according to the embodiment of the present disclosure.

[0191] exist Fig. 9 In the setting status table Tb10 shown in FIG. 1 , the setting unit 34 maintains "spg-2" which is the same as the server-side program corresponding to the vehicle ID "V2" as the server-side program corresponding to the vehicle ID "V5". That is, even if the mounted object of the vehicle-mounted device 201 whose vehicle-mounted device ID is "R2" is changed, the setting unit 34 maintains the server-side program for processing the vehicle information received from the vehicle-mounted device 201 without changing it.

[0192] Furthermore, when the update request unit 42 receives a notification from the processing unit 33 that the configuration of the network before the change is the same as the configuration of the network after the change, the update request unit 42 does not perform the update request process.

[0193] In more detail, Fig. 9 In the setting status table Tb10 shown in FIG. 1 , the update request unit 42 maintains the same "vpg-2" as the vehicle-side program corresponding to the vehicle ID "V2" as the server-side program corresponding to the vehicle ID "V5". That is, even when the mounted object of the vehicle-mounted device 201 whose vehicle-mounted device ID is "R2" is changed, the update request unit 42 maintains the vehicle-side program for processing the vehicle information received from the vehicle-mounted device 201 without changing it.

[0194] [Action flow]

[0195] Fig.10 This is a flowchart that defines the operation procedure of processing performed by the vehicle-mounted device according to the embodiment of the present disclosure.

[0196] Reference Fig.10 First, when the ignition power of the vehicle 1 is switched from the off state to the on state, the vehicle-mounted device 201 is started (step S101).

[0197] Next, the vehicle-mounted device 201 acquires the vehicle ID from the vehicle 1 (step S102 ).

[0198] Next, the in-vehicle device 201 transmits ID acquisition information including its own in-vehicle device ID and the acquired vehicle ID to the server 101 (step S103 ).

[0199] Next, when the vehicle-mounted device 201 receives update request information from the server 101 ("Yes" in step S104), it updates the vehicle-side program to a new vehicle-side program corresponding to the acquired vehicle ID based on the update request information (step S105).

[0200] Next, the in-vehicle device 201 transmits update completion information to the server 101 (step S106).

[0201] Next, the vehicle-mounted device 201 waits for the execution of the transmission process ("No" in step S107) until the permission information for allowing the execution of the transmission process is received from the server 101, and when the permission information is received ("Yes" in step S107), the transmission process is performed until the ignition power is switched from the on state to the off state ("No" in step S109). For example, as described above, the vehicle-mounted device 201 acquires the vehicle information from the vehicle-mounted device 211 by executing the updated vehicle-side program, and sends the acquired vehicle information to the server 101 (step S108).

[0202] Then, when the ignition power is switched from the OFF state to the ON state (YES in step S109 ), the vehicle-mounted device 201 stops the transmission process (step S110 ).

[0203] Fig.11 This is a flowchart showing the operation procedure of setting processing and update request processing performed by the server according to the embodiment of the present disclosure.

[0204] Reference Fig.11 First, the server 101 receives ID acquisition information including the vehicle-mounted device ID and the vehicle ID from the vehicle-mounted device 201 (step S201).

[0205] Next, when the ID correspondence between the vehicle-mounted device ID and the vehicle ID included in the received ID acquisition information is not registered in the setting status table Tb10 ("No" in step S202), the server 101 updates the contact table Tb20 indicating the correspondence between the vehicle ID and the user information. For example, as described above, the server 101 sends an information request notification for requesting user information to the vehicle-mounted device 201. Then, the server 101 updates the contact table Tb20 based on the user information received from the vehicle-mounted device 201 (step S203).

[0206] Next, the server 101 sends the mounting information to the user, indicating that the vehicle-mounted device 201 having the vehicle-mounted device ID included in the received ID acquisition information, i.e., the received identification information, is mounted on the vehicle 1. For example, as described above, the server 101 refers to the contact table Tb20 in the storage unit 35, and sends the mounting information to the user identified by the user ID corresponding to the vehicle ID included in the received ID acquisition information (step S204).

[0207] Next, when receiving the consent information as the response information from the user to the deployment information (YES in step S205 ), the server 101 checks whether the received identification information is registered in the setting status table Tb10 (step S206 ).

[0208] Next, when the received identification information is registered in the setting status table Tb10 (YES in step S206 ), the server 101 confirms whether the configuration of the network before the change is the same as the configuration of the network after the change (step S207 ).

[0209] Next, if the network structure before the change is different from the network structure after the change ("No" in step S207), the server 101 performs setting processing. For example, as described above, the server 101 sets the computer program corresponding to the vehicle model determined by the change identification information as the server-side program (step S208).

[0210] Next, the server 101 performs update request processing. For example, as described above, the server 101 sends update request information requesting update to a new vehicle-side program corresponding to the changed identification information to the vehicle-mounted device 201 (step S209). It should be noted that step S208 and step S209 can be executed in reverse order or in parallel.

[0211] Next, when receiving the update completion information from the in-vehicle device 201 (YES in step S210 ), the server 101 transmits permission information to the in-vehicle device 201 (step S211 ).

[0212] On the other hand, when the received identification information is not registered in the setting status table Tb10 ("No" in step S206), the server 101 performs setting processing. For example, as described above, the server 101 sets the computer program corresponding to the vehicle model determined by the vehicle ID included in the received ID acquisition information as the server-side program (step S208).

[0213] Next, the server 101 performs update request processing. For example, as described above, the server 101 transmits update request information requesting update to a new vehicle-side program corresponding to the vehicle ID included in the received ID acquisition information to the vehicle-mounted device 201 (step S209).

[0214] In addition, when the ID correspondence is registered in the setting status table Tb10 ("Yes" in step S202), when the consent information cannot be received even after a certain period of time ("No" in step S205), and when the structure of the network before the change is the same as the structure of the network after the change ("Yes" in step S207), the server 101 does not perform setting processing and update request processing.

[0215] Fig.12 This is a diagram showing an example of a sequence of processes of a server, an in-vehicle device, and a terminal device in a communication system according to an embodiment of the present disclosure.

[0216] Reference Fig.12 First, when the ignition power source 72 of the vehicle 1 is switched from the off state to the on state, the vehicle-mounted device 201 is started and acquires the vehicle ID of the vehicle 1 from the vehicle 1 on which the vehicle 1 is mounted (step S301).

[0217] Next, the in-vehicle device 201 transmits ID acquisition information including its own in-vehicle device ID and the acquired vehicle ID to the server 101 (step S302 ).

[0218] Next, the server 101 performs ID confirmation processing based on the ID acquisition information received from the vehicle-mounted device 201. For example, as described above, the server 101 confirms whether the ID correspondence relationship between the vehicle-mounted device ID and the vehicle ID included in the received ID acquisition information is registered in the setting status table Tb10. Here, it is assumed that the ID correspondence relationship is not registered in the setting status table Tb10 (step S303).

[0219] Next, the server 101 transmits an information request notification for requesting user information related to the user of the vehicle 1 to the vehicle-mounted device 201 (step S304 ).

[0220] Next, when the in-vehicle device 201 receives a notification from the server 101 indicating that the information request notification has been received, it transmits transmission request information indicating a request to transmit user information to the in-vehicle device 201 to the terminal device 301 (step S305).

[0221] Next, the terminal device 301 transmits the user information to the in-vehicle device 201 in response to the information request notification received from the in-vehicle device 201 (step S306).

[0222] Next, the in-vehicle device 201 transmits the user information received from the terminal device 301 to the server 101 (step S307).

[0223] Next, the server 101 updates the contact table Tb20 based on the user information and ID acquisition information received from the vehicle-mounted device 201 (step S308 ).

[0224] Next, the server 101 sends the installation information indicating that the vehicle-mounted device 201 having the vehicle-mounted device ID included in the received ID acquisition information, i.e., receiving the identification information, has been installed on the vehicle 1 to the user identified by the user ID corresponding to the vehicle ID included in the received ID acquisition information (step S309).

[0225] Next, the user transmits consent information indicating consent to the connection between the vehicle-mounted device 201 that receives the identification information and the vehicle 1 to the server 101 as response information corresponding to the mounting information received from the server 101 (step S310 ).

[0226] Next, the server 101 confirms whether the received identification information is registered in the setting status table Tb10. Here, it is assumed that the server 101 confirms that the vehicle-mounted device ID included in the ID acquisition information is not registered in the setting status table Tb10 (step S311).

[0227] Next, the server 101 performs a setting process of setting a computer program corresponding to the vehicle model specified by the vehicle ID included in the received ID acquisition information as a server-side program (step S312 ).

[0228] Next, the server 101 performs an update request process (step S313) of sending update request information for requesting to update the new vehicle-side program corresponding to the vehicle ID included in the received ID acquisition information to the vehicle-mounted device 201. It should be noted that step S312 and step S313 can be executed in reverse order or in parallel.

[0229] Next, the vehicle-mounted device 201 performs an update process to update the vehicle-side program stored in the vehicle-side device 201 to a new vehicle-side program corresponding to the acquired vehicle ID based on the update request information received from the server 101 (step S314 ).

[0230] Next, when the update process is completed, the vehicle-mounted device 201 transmits update completion information to the server 101 (step S315).

[0231] Next, when the setting process is completed and the update completion information is received from the vehicle-mounted device 201, the server 101 transmits permission information indicating that the vehicle-mounted device 201 is permitted to execute the transmission process to the vehicle-mounted device 201 (step S316).

[0232] Next, when receiving the permission information from the server 101, the vehicle-mounted device 201 performs the transmission process by executing the updated vehicle-side program (step S317).

[0233] Fig.13 This is a diagram showing another example of the sequence of processes of the server, the in-vehicle device, and the terminal device in the communication system according to the embodiment of the present disclosure.

[0234] Fig.13 The processing of steps S401 to S410 shown in FIG. Fig.12 The processes from step S301 to step S310 shown are the same.

[0235] Next, the server 101 confirms whether the received identification information is registered in the setting status table Tb10. Here, it is assumed that the server 101 confirms that the received identification information is registered in the setting status table Tb10 (step S411).

[0236] Next, the server 101 confirms whether the network configuration before the change is the same as the network configuration after the change. For example, as described above, it is assumed that the server 101 refers to the management table Tb30 and confirms that the network configuration before the change is different from the network configuration after the change (step S412).

[0237] Next, the server 101 performs a setting process of setting a computer program corresponding to the vehicle model specified by the vehicle ID included in the received ID acquisition information as a server-side program (step S413 ).

[0238] Next, the server 101 performs an update request process (step S414) of sending update request information for requesting to update to a new vehicle-side program corresponding to the vehicle ID included in the received ID acquisition information to the vehicle-mounted device 201. It should be noted that step S413 and step S414 can be executed in reverse order or in parallel.

[0239] Fig.13 The processing of steps S415 to S418 shown in FIG. Fig.12 The processes from step S314 to step S317 shown are the same.

[0240] It should be noted that, in the server 101 involved in the embodiment of the present disclosure, a structure is adopted in which the sending unit 43 sends the carrying information to the user identified by the user ID corresponding to the vehicle ID included in the ID acquisition information, but it is not limited to this. The sending unit 43 may also be a structure that does not send the carrying information to the user. In this case, if the setting unit 34 receives a notification from the processing unit 33 that the ID correspondence is not registered in the setting status table Tb10, the setting process is performed. In addition, if the update request unit 42 receives a notification from the processing unit 33 that the ID correspondence is not registered in the setting status table Tb10, the update request process is performed.

[0241] In addition, in the server 101 involved in the embodiment of the present disclosure, a configuration is adopted in which the sending unit 43 sends the permission information to the vehicle-mounted device 201 when the setting process of the setting unit 34 is completed and the receiving unit 41 receives the update completion information from the vehicle-mounted device 201, but the present invention is not limited to this. For example, the following configuration may be adopted: the sending unit 43 does not send the permission information, and when the vehicle-mounted device 201 completes the update of the second computer program, the update completion information is not sent and the sending process is started.

[0242] In addition, part or all of the functions of the server 101 according to the embodiment of the present disclosure may be provided by cloud computing. That is, the server 101 according to the embodiment of the present disclosure may be a cloud server composed of a plurality of servers.

[0243] It should be considered that the above embodiments are illustrative in all aspects and not restrictive. The scope of the present invention is shown by the claims rather than the above description, and is intended to include all changes within the meaning and scope equivalent to the claims.

[0244] Each process (function) of the above-mentioned embodiment is implemented by a processing circuit including one or more processors. The above-mentioned processing circuit can also be composed of an integrated circuit that is combined with one or more memories, various analog circuits, various digital circuits, etc. in addition to the above-mentioned one or more processors. The above-mentioned one or more memories store computer programs (commands) that enable the above-mentioned one or more processors to perform the above-mentioned processes. The above-mentioned one or more processors can perform the above-mentioned processes according to the above-mentioned computer programs read from the above-mentioned one or more memories, or they can perform the above-mentioned processes according to the logic circuits pre-designed to perform the above-mentioned processes. The above-mentioned processor can be a CPU (Central Processing Unit: Central Processing Unit), GPU (Graphics Processing Unit: Graphics Processing Unit), DSP (Digital Signal Processor: Digital Signal Processor), FPGA (Field Programmable Gate Array: Field Programmable Gate Array) and ASIC (Application Specific Integrated Circuit: Application Specific Integrated Circuit) and other various processors suitable for computer control. It should be noted that the above-mentioned multiple processors separated physically can also cooperate with each other to perform the above-mentioned processes. For example, the processors installed in each of the physically separated computers may cooperate with each other to perform the above-mentioned processes via a network such as a LAN (Local Area Network), a WAN (Wide Area Network), and the Internet. The computer program may be installed in the memory from an external server device or the like via the network, or may be circulated in a state stored in a recording medium such as a CD-ROM (Compact Disc Read Only Memory), a DVD-ROM (Digital Versatile Disk Read Only Memory), and a semiconductor memory, and installed in the memory from the recording medium.

[0245] The above description includes the following additional features.

[0246] [Note 1]

[0247] A management device, comprising:

[0248] a receiving unit that receives vehicle identification information for identifying the vehicle from an on-vehicle device mounted on the vehicle;

[0249] a setting unit that performs setting processing of setting a computer program corresponding to a vehicle type determined based on the vehicle identification information received by the receiving unit as a first computer program for processing vehicle information related to the vehicle in the management device; and

[0250] an update request unit for performing update request processing of sending update request information for requesting update to a second computer program to the vehicle-mounted device, wherein the second computer program is a computer program corresponding to the vehicle identification information received by the receiving unit and is used for the vehicle-mounted device to perform transmission processing for acquiring the vehicle information and transmitting the information to the management device,

[0251] The receiving unit further receives device identification information for identifying the vehicle-mounted device from the vehicle-mounted device,

[0252] The management device further includes a storage unit that stores device correspondence information indicating a correspondence relationship between the device identification information and the vehicle identification information.

[0253] When the device identification information is registered in the device corresponding information, the processing unit determines that the mounted object of the vehicle-mounted device having the device identification information is changed to the vehicle having the vehicle identification information received by the receiving unit,

[0254] When the device identification information is not registered in the device correspondence information, the processing unit determines that the vehicle-mounted device having the device identification information is mounted on the vehicle for the first time.

[0255] [Note 2]

[0256] A management device, comprising a processing circuit,

[0257] The processing circuit receives vehicle identification information for identifying the vehicle from an on-board device mounted on the vehicle, performs setting processing of setting a computer program corresponding to a vehicle type determined according to the received vehicle identification information as a first computer program for processing vehicle information related to the vehicle in the management device, and performs update request processing of sending update request information for requesting an update to a second computer program to the on-board device, wherein the second computer program is a computer program corresponding to the received vehicle identification information, and is used for the on-board device to obtain the vehicle information and send it to the management device.

[0258] [Note 3]

[0259] A vehicle-mounted device is mounted on a vehicle and transmits and receives information with a management device.

[0260] The vehicle-mounted device comprises a processing circuit,

[0261] The processing circuit acquires vehicle identification information for identifying the vehicle equipped with the vehicle-mounted device, updates update request information of a computer program used by the vehicle-mounted device to acquire vehicle information related to the vehicle and send it to the management device based on a request received from the management device, performs update processing to update the computer program stored in the vehicle-mounted device to a new computer program for performing the sending processing corresponding to the acquired vehicle identification information, and performs the sending processing by executing the updated computer program. When the update processing is completed, the processing circuit sends update completion information to the management device.

[0262] Description of Reference Numerals

[0263] 1 vehicle; 11 first communication unit; 12 setting processing unit; 13 second communication unit; 14 acquisition unit; 15, 35 storage unit; 21 receiving unit; 22 sending processing unit; 23 updating unit; 31 communication unit; 32 analysis unit; 33 processing unit; 34 setting unit; 41 receiving unit; 42 update request unit; 43 sending unit; 51, 51A, 51B CAN bus; 101 server; 151 external network; 201 vehicle-mounted device; 211, 211A, 211B vehicle-mounted equipment; 212 vehicle ID storage unit; 301 terminal device; 501 communication system; Tb10 setting status table; Tb20 management table; Tb30 contact table.

Claims

1. A management device comprising: a receiving unit that receives vehicle identification information for identifying the vehicle from an on-vehicle device mounted on the vehicle; a setting unit that performs setting processing of setting a computer program corresponding to the vehicle identification information received by the receiving unit as a first computer program for processing vehicle information related to the vehicle in the management device; and An update request unit performs update request processing of sending update request information to the vehicle-mounted device, wherein the update request information is used to request an update to a second computer program corresponding to the vehicle identification information received by the receiving unit, and the second computer program is used for the vehicle-mounted device to obtain the vehicle information and send the acquired vehicle information to the management device to provide to the first computer program set by the setting unit.

2. The management device according to claim 1, wherein: The receiving unit receives the changed identification information, wherein the changed identification information is the vehicle identification information for identifying the vehicle on which the vehicle-mounted device is mounted and is transmitted from the vehicle-mounted device whose mounted object is changed. The setting unit sets the computer program corresponding to the change identification information as a third computer program for processing vehicle information related to the vehicle equipped with the vehicle-mounted device in the management device, The update request unit sends the update request information for requesting an update to a fourth computer program corresponding to the changed identification information to the vehicle-mounted device, and the fourth computer program is used by the vehicle-mounted device to obtain the vehicle information and send the acquired vehicle information to the management device to provide it to the sending processing of the third computer program set by the setting unit.

3. The management device according to claim 2, wherein: The setting unit sets the computer program corresponding to the change identification information as the third computer program when the structure of the vehicle network in the vehicle before the installation object is changed, that is, the pre-change network, is different from the structure of the vehicle network in the vehicle after the installation object is changed, that is, the post-change network. The update request unit transmits the update request information for requesting update of the fourth computer program to correspond to the change identification information to the in-vehicle device when the configuration of the network before the change is different from the configuration of the network after the change.

4. The management device according to any one of claims 1 to 3, wherein: The management device also includes a sending unit. When the setting processing of the setting unit is completed and the receiving unit receives update completion information from the vehicle-mounted device indicating that the update to the second computer program has been completed, the sending unit sends permission information to the vehicle-mounted device indicating that the vehicle-mounted device is allowed to execute the sending processing.

5. The management device according to any one of claims 1 to 4, wherein: The receiving unit further receives device identification information for identifying the vehicle-mounted device from the vehicle-mounted device, The management device also has: a storage unit storing user corresponding information and device corresponding information, wherein the user corresponding information indicates a corresponding relationship between user identification information for identifying a user of the vehicle and the vehicle identification information, and the device corresponding information indicates a corresponding relationship between the device identification information and the vehicle identification information; as well as A sending unit, in a case where the device identification information received by the receiving unit, i.e., the receiving identification information, is not registered in the device corresponding information, the sending unit sends mounting information indicating that the vehicle-mounted device having the receiving identification information has been mounted on the vehicle to the user identified by the user identification information corresponding to the vehicle identification information received by the receiving unit based on the user corresponding information in the storage unit.

6. The management device according to claim 5, wherein: When the receiving unit receives, as response information from the user regarding the mounting information, consent information indicating consent for the vehicle-mounted device having the reception identification information to be connected to the vehicle, the setting unit performs the setting process, When the receiving unit receives the consent information, the update request unit performs the update request process.

7. The management device according to any one of claims 1 to 6, wherein: The receiving unit further receives device identification information for identifying the vehicle-mounted device from the vehicle-mounted device, The management device further includes a storage unit that stores device correspondence information indicating a correspondence relationship between the device identification information and the vehicle identification information. When the device identification information received by the receiving unit, that is, the reception identification information, is not registered in the device corresponding information, the setting unit performs the setting process, The update request unit performs the update request process when the reception identification information is not registered in the device correspondence information.

8. An in-vehicle device for transmitting and receiving information with the management device according to any one of claims 1 to 7, the in-vehicle device comprising: an acquisition unit, which acquires the vehicle identification information for identifying the vehicle on which the vehicle-mounted device is mounted; an updating unit that performs an updating process of updating the computer program for performing the sending process stored in the vehicle-mounted device to the second computer program corresponding to the vehicle identification information acquired by the acquiring unit based on the update request information received from the management device; and a transmission processing unit that performs the transmission processing by executing the second computer program, When the update process is completed, the update unit transmits update completion information to the management device.

9. A vehicle-mounted device, mounted on a vehicle and configured to send and receive information with a management device, the vehicle-mounted device comprising: an acquisition unit, which acquires vehicle identification information for identifying the vehicle on which the vehicle-mounted device is mounted; an updating unit that performs an updating process based on update request information received from the management device, the update request information requesting an update of a computer program used by the vehicle-mounted device to perform a sending process of acquiring vehicle information related to the vehicle and sending the information to the management device, the updating process updating the computer program stored in the vehicle-mounted device to a new computer program used to perform the sending process corresponding to the vehicle identification information acquired by the acquiring unit; and a transmission processing unit that performs the transmission processing by executing the updated computer program, When the update process is completed, the update unit transmits update completion information to the management device.

10. A management method is a management method in a management device, the management method comprising the following steps: receiving vehicle identification information for identifying the vehicle from an onboard device mounted on the vehicle; performing a setting process of setting a computer program corresponding to the received vehicle identification information as a first computer program for processing vehicle information related to the vehicle in the management device; as well as An update request process is performed to send update request information to the vehicle-mounted device, wherein the update request information is used to request an update to a second computer program corresponding to the received vehicle identification information, and the second computer program is used by the vehicle-mounted device to obtain the vehicle information and send the obtained vehicle information to the management device to provide it to the first computer program set in the management device.

11. A management program, used in a management device, The management program is used to make the computer function as a receiving unit, a setting unit, and an update request unit. The receiving unit receives vehicle identification information for identifying the vehicle from an on-vehicle device mounted on the vehicle, The setting unit performs setting processing of setting a computer program corresponding to the vehicle identification information received by the receiving unit as a first computer program for processing vehicle information related to the vehicle in the management device, The update request unit performs update request processing by sending update request information to the vehicle-mounted device, and the update request information is used to request an update to a second computer program corresponding to the vehicle identification information received by the receiving unit, and the second computer program is used by the vehicle-mounted device to obtain the vehicle information and send the acquired vehicle information to the management device to provide it to the first computer program set by the setting unit.

Images