Setting device, communication instrument, communication system, setting method, information transmission method, setting program, and information transmission program

Abstract

This setting device comprises: an acquisition unit that acquires setting information of a communication instrument, the setting information including upload destination information relating to a device of an upload destination of data relating to an apparatus to which the communication instrument is retrofitted; and a setting processing unit that performs setting processing for setting the setting information acquired by the acquisition unit in the communication instrument. The device of the upload destination is a device that is different from the setting device and serves as a management entity.

Description

Setting device, communication device, communication system, setting method, information transmission method, setting program, and information transmission program

[0001] The present disclosure relates to a setting device, a communication device, a communication system, a setting method, an information transmission method, a setting program, and an information transmission program. This application claims priority based on Japanese Patent Application No. 2024-197696 filed on November 12, 2024, and incorporates all of its disclosure herein.

[0002] Patent Document 1 (International Publication No. 2020 / 049379) discloses the following technology. That is, an information collection device is an information collection device that constitutes a train equipment management system for managing the usage history of equipment attached to a train together with a ground system. The information collection device includes a vehicle information collection unit that collects an individual identification number for uniquely identifying each device to be managed attached to the train and first operation information indicating the operation state of each device, and second operation information indicating the operation state when controlling each device, the individual identification number of each device, operation information including the first operation information and the second operation information, a car number for identifying the vehicle to which each device is attached, and a formation number for identifying the train, and performs control to collect and transmit to the ground system via a communication device.

[0003] International Publication No. 2020 / 049379, Japanese Patent Application Laid-Open No. 2019-117493

[0004] The setting device of the present disclosure includes an acquisition unit that acquires upload destination information regarding a device to which the communication device is retrofitted and includes setting information of the communication device, and a setting processing unit that performs a setting process for setting the setting information acquired by the acquisition unit in the communication device. The device of the upload destination is a device of a management entity different from the setting device.

[0005] One aspect of the present disclosure can be realized not only as a setting device including such a characteristic processing unit but also as a semiconductor integrated circuit that realizes part or all of the setting device.

[0006] One aspect of this disclosure can be realized not only as a communication device equipped with such characteristic processing units, but also as a semiconductor integrated circuit that implements part or all of the communication device.

[0007] Figure 1 is a diagram showing an example of the configuration of a communication system according to an embodiment of the present disclosure. Figure 2 is a diagram showing an example of the configuration of an in-vehicle device according to an embodiment of the present disclosure. Figure 3 is a diagram showing an example of the configuration of a setting server according to an embodiment of the present disclosure. Figure 4 is a diagram for explaining the user information registration process by the setting server according to an embodiment of the present disclosure. Figure 5 is a diagram schematically showing the processing of each device when an in-vehicle device is retrofitted to a vehicle in the communication system according to an embodiment of the present disclosure. Figure 6 is a diagram showing an example of a correspondence table held by the setting server according to an embodiment of the present disclosure. Figure 7 is a diagram showing an example of an updated correspondence table held by the setting server according to an embodiment of the present disclosure. Figure 8 is a diagram showing an example of the configuration of a vehicle management server according to an embodiment of the present disclosure. Figure 9 is a diagram schematically showing the processing of each device when the vehicle to which the in-vehicle device is installed is changed in the communication system according to an embodiment of the present disclosure. Figure 10 is a diagram showing another example of an updated correspondence table held by the setting server according to an embodiment of the present disclosure. Figure 11 is a flowchart that defines an example of the operation procedure when the setting server according to an embodiment of the present disclosure performs setting processing. Figure 12 is a flowchart showing an example of the operation procedure when the configuration server according to the embodiment of this disclosure performs a deletion process. Figure 13 is a flowchart showing an example of the operation procedure when the in-vehicle device according to the embodiment of this disclosure performs settings related to the upload of vehicle data sets. Figure 14 is a flowchart showing an example of the operation procedure when the in-vehicle device according to the embodiment of this disclosure performs a data transmission process. Figure 15 is a flowchart showing an example of the operation procedure when the in-vehicle device according to the embodiment of this disclosure performs a data transmission process. Figure 16 is a diagram showing an example of the processing sequence of the terminal device, in-vehicle device, configuration server and vehicle management server in the communication system according to the embodiment of this disclosure. Figure 17 is a diagram showing another example of the processing sequence of the terminal device, in-vehicle device and configuration server in the communication system according to the embodiment of this disclosure.

[0008] Conventionally, technologies have been developed to perform various analyses using vehicle information collected from on-board devices installed in the vehicle.

[0009] [Problems this disclosure aims to solve] In recent years, there has been progress in developing technologies that enable communication devices to be retrofitted to vehicles and other equipment, thereby making such equipment function as ICT (Information and Communication Technology) terminals, in other words, connecting them.

[0010] Furthermore, data from devices with added communication equipment may be uploaded to external devices such as servers. In this case, it is undesirable for anyone other than the device's user to possess the data. Therefore, technology is needed to properly manage the ownership of data from devices with added communication equipment.

[0011] This disclosure was made to solve the aforementioned problems, and its purpose is to provide a setting device, a communication device, a communication system, a setting method, an information transmission method, a setting program, and an information transmission program that can appropriately manage the ownership of data of equipment to which a communication device has been retrofitted.

[0012] [Effects of this disclosure] This disclosure allows for proper management of data ownership in devices to which communication equipment has been retrofitted.

[0013] [Description of Embodiments of the Disclosure] First, the contents of the embodiments of the Disclosure will be listed and described. (1) The setting device according to the embodiment of the Disclosure is a setting device comprising: an acquisition unit that acquires setting information of a communication device, including upload destination information of a device to which data relating to a communication device has been retrofitted; and a setting processing unit that performs setting processing for setting the setting information acquired by the acquisition unit on the communication device, wherein the upload destination device is a device under a different management entity than the setting device.

[0014] With this configuration, when a communication device is retrofitted to another device, the configuration device used to set the communication device can use the configuration information, including the upload destination information, to set a device with a different management entity as the upload destination for the device's data. This allows for the setting of an appropriate upload destination for the device's data. Therefore, ownership of data on devices to which communication devices have been retrofitted can be properly managed.

[0015] (2) In (1) above, the acquisition unit may further acquire first identification information for identifying the communication device and second identification information for identifying the device, and the setting processing unit may perform the setting processing using the first identification information and the second identification information acquired by the acquisition unit.

[0016] This configuration allows for more appropriate configuration processing by identifying the target communication device and the equipment to which it is retrofitted using the first and second identification information, respectively, and then setting the data upload destination.

[0017] (3) In the above (2), the setting device may further include a storage unit that holds correspondence information indicating the correspondence between the first identification information, the second identification information, and the upload destination information.

[0018] This configuration makes it easy to manage pairs of communication device identification information, device identification information, and upload destination information, especially when there are multiple communication devices to configure, or multiple devices to which communication devices are connected.

[0019] (4) In the above (3), the setting device may further include an update unit that deletes the correspondence relationship corresponding to the communication device from the correspondence information when the use of the communication device is stopped at the equipment to which the communication device is installed, and a notification unit that notifies the communication device of the suspension of use.

[0020] In this way, when the use of a communication device on a device is stopped, the corresponding relationship for that communication device is removed from the correspondence information, thereby preventing incorrect configuration processing using the correspondence for a communication device that no longer needs to be configured. Furthermore, by notifying the communication device of the discontinuation of use, it is possible to prevent the communication device from mistakenly uploading device data.

[0021] (5) In any of the above (1) to (4), the manufacturer of the setting device may be the same as the manufacturer of the communication device.

[0022] This configuration facilitates the exchange of various types of information between the communication device and the setting device.

[0023] (6) The communication device according to the embodiment of the present disclosure comprises a receiving unit that receives setting information of the communication device from an external device outside the device, including information about a device to which the communication device is retrofitted and to which data is uploaded, and a transmitting unit that transmits the data to the upload destination device based on the setting information received by the receiving unit, wherein the upload destination device is a device under a different management entity than the external device.

[0024] With this configuration, when a communication device is retrofitted to an existing device, the external device that configures the communication device can use configuration information, including upload destination information, to set a device with a different management entity as the upload destination for the device's data. This allows for the setting of an appropriate upload destination for the device's data. Therefore, ownership of data from devices to which communication devices have been retrofitted can be properly managed.

[0025] (7) The communication system according to the embodiment of the present disclosure comprises a communication device that is retrofitted to equipment and a setting device that manages the communication device, wherein the setting device acquires setting information for the communication device, including information about a device to which data relating to the equipment is uploaded, the setting device performs setting processing to set the acquired setting information on the communication device, the communication device transmits the data to the upload destination device based on the setting information, and the upload destination device is a device under a different management entity than the setting device.

[0026] With this configuration, when a communication device is retrofitted to another device, the configuration device used to set the communication device can use the configuration information, including the upload destination information, to set a device with a different management entity as the upload destination for the device's data. This allows for the setting of an appropriate upload destination for the device's data. Therefore, ownership of data on devices to which communication devices have been retrofitted can be properly managed.

[0027] (8) The setting method according to the embodiment of the present disclosure is a setting method for a setting device, comprising the steps of acquiring setting information for a communication device, including upload destination information for a device to which data relating to a communication device has been retrofitted, and performing a setting process to set the acquired setting information on the communication device, wherein the upload destination device is a device under a different management entity than the setting device.

[0028] In this manner, when a communication device is retrofitted to another device, the configuration device used to set up the communication device can use the configuration information, including the upload destination information, to set a device with a different management entity as the upload destination for the device's data. This allows for the setting of an appropriate upload destination for the device's data. Therefore, ownership of data on a device to which a communication device has been retrofitted can be properly managed.

[0029] (9) An information transmission method according to an embodiment of the present disclosure is an information transmission method for a communication device, comprising the steps of: obtaining setting information for the communication device from an external device located outside the device, including information about a device to which data relating to equipment to which the communication device is retrofitted is uploaded; and transmitting the data to the upload destination device based on the obtained setting information, wherein the upload destination device is a device under a different management entity than the external device.

[0030] In this manner, when a communication device is retrofitted to an existing device, an external device that configures the communication device can use configuration information, including upload destination information, to set a device with a different management entity as the upload destination for the device's data. This allows for the setting of an appropriate upload destination for the device's data. Therefore, ownership of data on devices to which communication devices have been retrofitted can be properly managed.

[0031] (10) The setting program according to the embodiment of the present disclosure is a setting program used in a setting device, which causes a computer to function as an acquisition unit that acquires setting information for a communication device, including upload destination information for a device to which data relating to a communication device has been retrofitted, and a setting processing unit that performs setting processing for setting the setting information acquired by the acquisition unit on the communication device, wherein the upload destination device is a device under a different management entity than the setting device.

[0032] With this configuration, when a communication device is retrofitted to another device, the configuration device used to set the communication device can use the configuration information, including the upload destination information, to set a device with a different management entity as the upload destination for the device's data. This allows for the setting of an appropriate upload destination for the device's data. Therefore, ownership of data on devices to which communication devices have been retrofitted can be properly managed.

[0033] (11) The information transmission program according to the embodiment of the present disclosure is an information transmission program used in a communication device, which causes a computer to function as an acquisition unit that acquires setting information of the communication device from an external device outside the device, including information about a device to which data relating to the communication device is retrofitted, is uploaded to the device, and the upload destination device is a device under a different management entity than the external device.

[0034] With this configuration, when a communication device is retrofitted to an existing device, the external device that configures the communication device can use configuration information, including upload destination information, to set a device with a different management entity as the upload destination for the device's data. This allows for the setting of an appropriate upload destination for the device's data. Therefore, ownership of data from devices to which communication devices have been retrofitted can be properly managed.

[0035] Embodiments of this disclosure will be described below with reference to the drawings. In the drawings, the same or corresponding parts are denoted by the same reference numerals, and their descriptions will not be repeated. Furthermore, at least some of the embodiments described below may be combined in any way.

[0036] [Communication System] Figure 1 is a diagram showing an example of the configuration of a communication system according to an embodiment of the present disclosure. Referring to Figure 1, the communication system 501 comprises one or more in-vehicle devices 101, a setting server 151, one or more vehicle management servers 161, and a terminal device 301.

[0037] The on-board device 101 is an example of a communication device retrofitted to a vehicle 1. Specifically, for example, the on-board device 101 is installed directly or via another device to the vehicle 1 after the vehicle 1 has been shipped. The vehicle 1 is an example of equipment to which a communication device is retrofitted.

[0038] The configuration server 151 and the vehicle management server 161 are located outside the vehicle 1. The configuration server 151 is an example of a configuration device and an example of an external device.

[0039] In the example shown in FIG. 1, the vehicle type of the vehicle 1 to which the in-vehicle device 101 is retrofitted is a passenger car. Note that the vehicle type of the vehicle 1 is not limited to a passenger car, and may be any vehicle type such as a truck.

[0040] The vehicle management server 161 collects vehicle data related to the vehicle 1 from the in-vehicle device 101 and analyzes the vehicle data.

[0041] The setting server 151 performs settings related to the upload of vehicle data from the in-vehicle device 101 to the vehicle management server 161.

[0042] For example, the manufacturer of the setting server 151 is the same as the manufacturer of the in-vehicle device 101. Note that the manufacturer of the setting server 151 may be different from the manufacturer of the in-vehicle device 101.

[0043] The vehicle management server 161 is a device of a management entity different from the setting server 151. Specifically, for example, between the vehicle management server 161 and the setting server 151, the owners are different from each other. In the present embodiment, for example, the vehicle management server 161 is a server owned by a user (hereinafter, also referred to as a "sales destination user") such as a manufacturer of the vehicle 1 and a dealer of the vehicle 1, who are the sales destinations of the in-vehicle device 101. On the other hand, the setting server 151 is a server owned by a business operator (hereinafter, also referred to as a "sales source business operator") such as a manufacturer of the in-vehicle device 101, who is the sales source of the in-vehicle device 101.

[0044] Note that between the vehicle management server 161 and the setting server 151, not only the owners but also the operators and the like may be different from each other.

[0045] The terminal device 301 is a device owned by the sales destination user. The terminal device 301 is a communication terminal device such as a notebook PC (Personal Computer) and a tablet.

[0046] The terminal device 301 and the setting server 151 transmit and receive information via an external network 171 such as the Internet.

[0047] [In-Vehicle Device] FIG. 2 is a diagram showing an example of the configuration of an in-vehicle device according to an embodiment of the present disclosure. FIG. 2 shows a state where the in-vehicle device 101 is retrofitted to the vehicle 1.

[0048] Referring to FIG. 2, the in-vehicle device 101 is connected to in-vehicle devices 202A and 202B, which are a plurality of in-vehicle devices 202, via, for example, a CAN (Controller Area Network) bus 51. The in-vehicle device 101 and the plurality of in-vehicle devices 202 constitute an in-vehicle network 401.

[0049] The in-vehicle device 202 is a sensor, an in-vehicle ECU (Electronic Control Unit), a navigation device, a human machine interface, a camera, and the like. The in-vehicle ECU is a TCU (Telematics Communication Unit), an ECU for autonomous driving, an ECU for face authentication, an ECU for door lock, and the like.

[0050] Each in-vehicle device 202 transmits vehicle data to the in-vehicle device 101. Specifically, each in-vehicle device 202 includes the vehicle data and a CAN-ID (Identifier) indicating the type of the vehicle data in a CAN frame and transmits the CAN frame to the in-vehicle device 101. Each in-vehicle device 202 transmits the CAN frame to the in-vehicle device 101, for example, regularly or irregularly.

[0051] The vehicle data is data generated by the in-vehicle device 202, for example, data indicating the measurement result of the in-vehicle device 202 (hereinafter, also referred to as the "transmission source device") that is the transmission source of the vehicle data. Specifically, the vehicle data shows the measurement result of the state of the transmission source device, the measurement result of the state of another in-vehicle device 202 different from the transmission source device, and the measurement result of data related to the running of the vehicle 1 such as the vehicle speed as the measurement result.

[0052] Note that the in-vehicle network 401 is not limited to a configuration in which one CAN bus 51 is provided, and a configuration in which a plurality of CAN buses 51 are provided may be used.

[0053] Furthermore, the in-vehicle device 101 is not limited to being connected to the in-vehicle equipment 202 via the CAN bus 51. It may also be connected to the in-vehicle equipment 202 via transmission lines conforming to other communication standards such as CAN FD (CAN with Flexible Data Rate), Ethernet (registered trademark), FlexRay (registered trademark), MOST (Media Oriented System Transport) (registered trademark), LIN (Local Interconnect Network), and CXPI (Clock Extension Peripheral Interface) (registered trademark).

[0054] The in-vehicle device 101 comprises an in-vehicle communication unit 11, an external communication unit 12, a setting unit 13, a data collection unit 14, and a storage unit 15. Some or all of the in-vehicle communication unit 11, the external communication unit 12, the setting unit 13, and the data collection unit 14 are implemented by a processing circuit (Circuitry) including one or more processors. The storage unit 15 is, for example, a non-volatile memory included in the processing circuit. The external communication unit 12 is an example of a receiving unit and an example of a transmitting unit.

[0055] The in-vehicle communication unit 11 stores vehicle data received from each in-vehicle device 202 in the storage unit 15.

[0056] For example, the external communication unit 12 communicates with the configuration server 151 or the vehicle management server 161 via the external network 171 by wirelessly communicating with a wireless base station device (not shown) according to a communication method such as Wi-Fi (registered trademark), LTE (Long Term Evolution) (registered trademark), or 5G.

[0057] [Configuration Server] Figure 3 shows an example of the configuration of a configuration server according to an embodiment of the present disclosure. The configuration server 151 comprises a communication unit 21, an authentication unit 22, a deletion processing unit 23, a configuration processing unit 24, and a storage unit 25. Some or all of the communication unit 21, the authentication unit 22, the deletion processing unit 23, and the configuration processing unit 24 are implemented, for example, by a processing circuit including one or more processors. The storage unit 25 is, for example, a non-volatile memory included in the processing circuit. The communication unit 21 is an example of an acquisition unit and an example of a notification unit. The deletion processing unit 23 is an example of an update unit.

[0058] (Registration of In-Vehicle Device ID and Sales Destination of In-Vehicle Device 101) For example, the storage unit 25 stores a set W1 of identification information for identifying the in-vehicle device 101 (hereinafter also referred to as "In-Vehicle Device ID") and the sales destination of the in-vehicle device 101. The In-Vehicle Device ID is an example of the first identification information.

[0059] The in-vehicle device ID is a unique ID for the in-vehicle device 101. Set W1 is registered in the storage unit 25 by the customer when the in-vehicle device 101 is retrofitted to the vehicle 1.

[0060] (User Information Registration Process) Figure 4 is a diagram illustrating the user information registration process by the configuration server according to the embodiment of this disclosure.

[0061] Referring to Figures 3 and 4, when the in-vehicle device 101 is retrofitted to the vehicle 1, the terminal device 301 transmits user information, including identification information for identifying the customer (hereinafter also referred to as "User ID") and identification information for identifying the terminal device 301 (hereinafter also referred to as "Terminal ID"), to the configuration server 151 via the external network 171.

[0062] In the configuration server 151, when the communication unit 21 receives user information from the terminal device 301 via the external network 171, it outputs the received user information to the authentication unit 22.

[0063] When the authentication unit 22 receives user information from the communication unit 21, it stores the user information in the storage unit 25. The authentication unit 22 then transmits the authentication information Pa, which will be used in the authentication process C1 of the terminal device 301, to the terminal device 301 that sent the user information via the external network 171.

[0064] Authentication information Pa includes an ID token indicating that the user has approved the sales destination user of the user ID included in the user information, as well as a password, etc.

[0065] When the terminal device 301 receives authentication information Pa from the configuration server 151, it stores the received authentication information Pa in its own storage unit (not shown).

[0066] (Acquisition of setting information) Figure 5 is a schematic diagram showing the processing of each device when an in-vehicle device is retrofitted to a vehicle in a communication system according to an embodiment of the present disclosure. Figure 5 shows the operation of each device when the in-vehicle device 101 is retrofitted to vehicle 1A, which is vehicle 1.

[0067] Referring to Figures 3 and 5, for example, the communication unit 21 obtains the in-vehicle device ID of the in-vehicle device 101 to be configured, identification information for identifying the vehicle 1 to which the in-vehicle device 101 is retrofitted (hereinafter also referred to as the "vehicle ID"), and configuration information for the in-vehicle device 101. For example, the configuration information S includes upload destination information for the device to which vehicle data related to the vehicle 1 is uploaded, and authentication information Pb. The vehicle ID is an example of the second identification information.

[0068] The vehicle ID is a unique ID for vehicle 1. The upload destination information is, for example, information indicating the URL (Uniform Resource Locator) where the vehicle data will be uploaded.

[0069] Authentication information Pb is authentication information used by the vehicle management server 161 in the authentication process of the in-vehicle device 101 that transmits vehicle data. Authentication information Pb includes, for example, a password.

[0070] Hereinafter, the setting information S of the on-board device 101 retrofitted to vehicle 1A will also be referred to as setting information S1.

[0071] The terminal device 301 owned by the customer who purchased vehicle 1A accepts input from the customer regarding the in-vehicle device ID of the in-vehicle device 101 to be configured, the vehicle ID of vehicle 1A, and the configuration information S1.

[0072] For example, terminal device 301 transmits the input in-vehicle device ID, vehicle ID, and configuration information S1, along with the authentication information Pa stored in its own memory and its own terminal ID, as configuration-related information (hereinafter also referred to as "configuration-related information K1") to configuration server 151 via external network 171.

[0073] In the configuration server 151, the communication unit 21 receives configuration-related information K1 from the terminal device 301 via the external network 171. The communication unit 21 then outputs the received configuration-related information K1 to the authentication unit 22.

[0074] The authentication unit 22 performs the authentication process C1 of the terminal device 301 using the authentication information Pa included in the setting-related information K1 received from the communication unit 21.

[0075] If the authentication unit 22 fails to authenticate the terminal device 301, it outputs authentication failure information L1 to the communication unit 21, indicating that authentication failed and the terminal ID included in the setting-related information K1 received from the communication unit 21.

[0076] The communication unit 21 transmits the authentication failure information L1 received from the authentication unit 22 to the terminal device 301 of the terminal ID indicated by the authentication failure information L1 via the external network 171.

[0077] Meanwhile, when the authentication unit 22 successfully authenticates the terminal device 301, it outputs the setting-related information K1 received from the communication unit 21 to the setting processing unit 24.

[0078] (Correspondence Table) Figure 6 shows an example of a correspondence table held by a configuration server according to the embodiment of this disclosure.

[0079] Referring to Figure 6, for example, the storage unit 25 stores a correspondence table Tb that shows the correspondence relationship Q between the in-vehicle device ID, the sales destination of the in-vehicle device 101, the vehicle ID, and the upload destination information as records. The correspondence table Tb is an example of correspondence information.

[0080] In the correspondence table Tb shown in Figure 6, the sales destination of the in-vehicle device 101 with in-vehicle device ID "ID-D1", the vehicle ID of the vehicle 1 on which the in-vehicle device 101 is installed, and the upload destination for the vehicle data of the vehicle 1 are "Company X", "ID-C1", and "https: / / aaa.com / data1", respectively.

[0081] (Setting Processing Unit) The setting processing unit 24 performs setting processing to set the setting information S acquired by the communication unit 21 in the in-vehicle device 101.

[0082] More specifically, for example, the setting processing unit 24 performs setting processing using the in-vehicle device ID and vehicle ID obtained by the communication unit 21.

[0083] Specifically, when the setting processing unit 24 receives setting-related information K1 from the authentication unit 22, it refers to the set W1 in the storage unit 25 to identify the sales destination of the in-vehicle device 101 that corresponds to the in-vehicle device ID included in the setting-related information K1.

[0084] When the configuration processing unit 24 identifies the sales destination of the in-vehicle device 101, it reads the corresponding table Tb in the storage unit 25. The configuration processing unit 24 then performs a registration process to register the in-vehicle device ID, vehicle ID, and upload destination information, as well as the identified sales destination W2 of the in-vehicle device 101, which are included in the configuration-related information K1 received from the authentication unit 22, into the corresponding table Tb.

[0085] Figure 7 shows an example of an updated correspondence table held by the configuration server according to the embodiment of this disclosure.

[0086] Referring to Figure 7, in the updated correspondence table Tb, compared to the correspondence table Tb shown in Figure 6, the sales destination of the in-vehicle device 101 with in-vehicle device ID "ID-D2", the vehicle ID of the vehicle 1 on which the in-vehicle device 101 is installed, and the upload destination for the vehicle data of the vehicle 1 are newly registered. The sales destination of the in-vehicle device 101 with in-vehicle device ID "ID-D2", the vehicle ID of the vehicle 1 on which the in-vehicle device 101 is installed, and the upload destination for the vehicle data of the vehicle 1 are "Company Y", "ID-C2", and "https: / / bbb.com / data2", respectively.

[0087] Once the registration process is complete, the setting processing unit 24 transmits the setting information S1 contained in the setting-related information K1 received from the authentication unit 22 to the vehicle 1 of the vehicle ID contained in the setting-related information K1 via the communication unit 21 and the external network 171.

[0088] Specifically, the setting processing unit 24 outputs to the communication unit 21 a pair U1 of setting information S1 and vehicle ID, which is included in the setting-related information K1 received from the authentication unit 22.

[0089] The communication unit 21 creates an IP packet (hereinafter also referred to as "packet P1") which contains the configuration information S1 for group U1 received from the configuration processing unit 24, and includes the IP address of its own configuration server 151 and the IP address of vehicle 1, which is the vehicle ID for group U1, as the source address and destination IP address, respectively. The communication unit 21 then transmits the created packet P1 to vehicle 1 via the external network 171 and the wireless base station equipment.

[0090] Referring again to Figures 2 and 5, in the in-vehicle device 101, the external communication unit 12 receives setting information S1 from the setting server 151.

[0091] More specifically, when the external communication unit 12 receives packet P1 from the configuration server 151 via the external network 171, it outputs the configuration information S1 contained in the received packet P1 to the configuration unit 13.

[0092] When the setting unit 13 receives setting information S1 from the external communication unit 12, it stores the upload destination information and authentication information Pb included in the setting information S1 in the storage unit 15.

[0093] Then, the setting unit 13 configures the settings related to uploading vehicle data based on the setting information S1 received from the external communication unit 12. Specifically, for example, the setting unit 13 configures the external communication unit 12 to send vehicle data to the upload destination indicated by the upload destination information included in the setting information S1.

[0094] In the example shown in Figure 5, the setting unit 13 configures the external communication unit 12 to send vehicle data to the vehicle management server 161A, which is the vehicle management server 161.

[0095] (Transmission of vehicle data) The collection unit 14 performs collection processing to collect vehicle data to be transmitted to the vehicle management server 161. More specifically, when the processing timing T for the collection processing arrives, the collection unit 14 retrieves multiple vehicle data (hereinafter also referred to as the "vehicle data group") that have been stored in the storage unit 15 by the in-vehicle communication unit 11 during the period from the previous processing timing T to the current processing timing T. The collection unit 14 then outputs the vehicle data group to the external communication unit 12.

[0096] For example, the storage unit 15 stores the vehicle ID of the vehicle 1 to which its on-board device 101 has been retrofitted. This vehicle ID is pre-registered in the storage unit 15 by, for example, the vendor.

[0097] The external communication unit 12 performs data transmission processing to send the vehicle data group collected by the collection unit 14 to the vehicle management server 161A.

[0098] More specifically, for example, the external communication unit 12 transmits the vehicle data group received from the collection unit 14 and vehicle-related information G1, which includes the vehicle ID and authentication information Pb stored in the storage unit 15, to the vehicle management server 161A.

[0099] Specifically, the external communication unit 12 accesses the URL indicated by the upload destination information stored in the storage unit 15 via the wireless base station device and the external network 171, and uploads the vehicle-related information G1 to the vehicle management server 161A.

[0100] (Vehicle Management Server) Figure 8 is a diagram showing an example of the configuration of a vehicle management server according to an embodiment of the present disclosure. Referring to Figure 8, the vehicle management server 161 comprises a communication unit 31, an authentication unit 32, and an analysis unit 33. Some or all of the communication unit 31, the authentication unit 32, and the analysis unit 33 are implemented by a processing circuit including one or more processors, for example.

[0101] The communication unit 31 receives a group of vehicle data from the in-vehicle device 101. The communication unit 31 then outputs the received vehicle-related information G1 to the authentication unit 32.

[0102] When the authentication unit 32 receives vehicle-related information G1 from the communication unit 31, it uses the authentication information Pb contained in the vehicle-related information G1 to perform authentication processing C2 on the in-vehicle device 101 that transmitted the vehicle-related information G1.

[0103] If the authentication unit 32 fails to authenticate the in-vehicle device 101, it outputs authentication failure information L2 to the communication unit 31, indicating that authentication failed and the vehicle ID received from the communication unit 21.

[0104] The communication unit 21 transmits the authentication failure information L2 received from the authentication unit 32 to the vehicle 1 with the vehicle ID indicated by the authentication failure information L2 via the external network 171.

[0105] Meanwhile, if the authentication unit 32 successfully authenticates the in-vehicle device 101, it outputs the vehicle data group included in the vehicle-related information G1 received from the communication unit 31 to the analysis unit 33.

[0106] When the analysis unit 33 receives a group of vehicle data from the authentication unit 32, it performs various analyses based on the vehicle data group, such as fault detection of the in-vehicle equipment 202 and evaluation of the driver's operation of the vehicle 1.

[0107] (Deletion process) Referring again to Figure 3, for example, in the configuration server 151, if the use of the in-vehicle device 101 in the vehicle 1 to which the in-vehicle device 101 is installed is stopped, the deletion process is performed to delete the corresponding relationship Q for the in-vehicle device 101 from the correspondence table Tb.

[0108] More specifically, for example, the terminal device 301 receives a request from the customer to stop using the in-vehicle device 101 in vehicle 1, and to input the in-vehicle device ID of the in-vehicle device 101. Stopping the use of the in-vehicle device 101 in vehicle 1 means removing the in-vehicle device 101 from the in-vehicle network 401 shown in Figure 2, that is, removing the in-vehicle device 101 from vehicle 1, etc.

[0109] When terminal device 301 receives the above input, it sends a usage suspension information indicating that the use of the in-vehicle device 101 will be stopped, along with the input in-vehicle device ID, its own terminal ID, and authentication information Pa, to the configuration server 151 via the external network 171.

[0110] In the configuration server 151, when the communication unit 21 receives service suspension information from the terminal device 301 via the external network 171, it outputs the received service suspension information to the authentication unit 22.

[0111] When the authentication unit 22 receives suspension information from the communication unit 21, it performs authentication processing C1 of the terminal device 301 using the authentication information Pa included in the suspension information.

[0112] If the authentication unit 22 fails to authenticate the terminal device 301, it sends authentication failure information L1 to the terminal device 301 that sent the suspension information via the communication unit 21 and the external network 171.

[0113] Meanwhile, when the authentication unit 22 successfully authenticates the terminal device 301, it outputs the usage suspension information received from the communication unit 21 to the deletion processing unit 23.

[0114] When the deletion processing unit 23 receives the usage suspension information from the authentication unit 22, it reads the correspondence table Tb in the storage unit 25. Then, by referring to the correspondence table Tb in the storage unit 25, the deletion processing unit 23 identifies the vehicle ID and upload destination information that correspond to the in-vehicle device ID included in the usage suspension information.

[0115] When the deletion processing unit 23 identifies the vehicle ID and upload destination information corresponding to the in-vehicle device ID included in the usage suspension information received from the authentication unit 22, it outputs upload suspension information, including the said upload destination information and the said vehicle ID, to the communication unit 21, indicating a request to stop uploading vehicle data.

[0116] Furthermore, the deletion processing unit 23 deletes the record containing the in-vehicle device ID included in the usage suspension information received from the authentication unit 22 from the corresponding table Tb.

[0117] For example, the communication unit 21 performs a notification process to notify the in-vehicle device 101 that its use in the vehicle 1 has been stopped.

[0118] More specifically, for example, the communication unit 21 creates an IP packet (hereinafter also referred to as "packet P2") that contains the upload stop information received from the deletion processing unit 23, and includes the IP address of its own configuration server 151 and the IP address of vehicle 1, which is the vehicle ID included in the upload stop information, as the source address and destination IP address, respectively. The communication unit 21 then transmits the created packet P2 to vehicle 1 via the external network 171 and the wireless base station equipment.

[0119] Referring again to Figure 2, in the in-vehicle device 101, when the external communication unit 12 receives packet P2 from the vehicle management server 161 via the external network 171 and the wireless base station device, it outputs the upload stop information contained in the received packet P2 to the setting unit 13.

[0120] When the setting unit 13 receives upload stop information from the external communication unit 12, it configures the external communication unit 12 not to send the vehicle data group to the upload destination indicated by the upload destination information included in the upload stop information. Specifically, the setting unit 13 deletes the upload destination information and authentication information Pb stored in the storage unit 15.

[0121] [Changing the upload destination of vehicle data] Next, we will explain the data transmission process by the in-vehicle device 101 when the in-vehicle device 101 is retrofitted to a new vehicle 1.

[0122] Figure 9 is a schematic diagram showing the processing of each device in a communication system according to an embodiment of the present disclosure when the vehicle to which the in-vehicle device is installed is changed. Figure 9 shows the operation of each device when the vehicle 1 to which the in-vehicle device 101 is installed is changed from vehicle 1A to vehicle 1B. In the example shown in Figure 9, the customer of vehicle 1B is different from the customer of vehicle 1A. Hereinafter, the setting information S of the in-vehicle device 101 retrofitted to vehicle 1B will also be referred to as setting information S2.

[0123] Referring to Figures 4 and 9, if the installation location of the in-vehicle device 101 is changed from vehicle 1A to vehicle 1B, the terminal device 301 owned by the customer of vehicle 1B transmits user information, including the user ID and terminal ID, to the configuration server 151 via the external network 171.

[0124] When the configuration server 151 receives user information from the terminal device 301 via the external network 171, it stores the received user information in the storage unit 25. Then, the configuration server 151 sends the authentication information Pa to the terminal device 301 that sent the user information via the external network 171.

[0125] When the terminal device 301 receives authentication information Pa from the configuration server 151, it stores the received authentication information Pa in its own storage unit. However, if the customer who sells vehicle 1B is the same as the customer who sells vehicle 1A, the terminal device 301 may be configured not to transmit user information. In other words, the configuration server 151 may be configured not to register user information or transmit authentication information Pa.

[0126] Furthermore, if the installation location of the in-vehicle device 101 is changed from vehicle 1A to vehicle 1B, the terminal device 301 accepts input from the customer of vehicle 1B of the in-vehicle device ID of the in-vehicle device 101, the vehicle ID of vehicle 1B, and the setting information S2. The upload destination information and authentication information Pb included in the setting information S2 are different from the upload destination information and authentication information Pb included in the setting information S1 shown in Figure 5.

[0127] The terminal device 301 then transmits the input in-vehicle device ID, vehicle ID, and configuration information S2, along with the authentication information Pa stored in its own memory and its own terminal ID, as configuration-related information (hereinafter also referred to as "configuration-related information K2") to the configuration server 151 via the external network 171.

[0128] Referring again to Figure 3, in the configuration server 151, when the authentication unit 22 receives configuration-related information K2 from the terminal device 301 via the external network 171 and the communication unit 21, it performs authentication processing C1 of the terminal device 301 using the authentication information Pa contained in the received configuration-related information K2.

[0129] When the authentication unit 22 successfully authenticates the terminal device 301, it outputs the setting-related information K2 received from the terminal device 301 to the setting processing unit 24.

[0130] When the setting processing unit 24 receives setting-related information K2 from the authentication unit 22, it refers to the set W1 in the storage unit 25 to identify the sales destination corresponding to the in-vehicle device ID included in the setting-related information K2.

[0131] The setting processing unit 24 then performs a registration process to register the set of specified sales destinations W2, which are included in the setting-related information K2 received from the authentication unit 22, into the corresponding table Tb.

[0132] Figure 10 shows another example of an updated correspondence table held by a configuration server according to an embodiment of the present disclosure.

[0133] Referring to Figure 10, the updated correspondence table Tb shows changes compared to the correspondence table Tb shown in Figure 7. These changes include the vehicle ID of vehicle 1 equipped with the in-vehicle device 101 with in-vehicle device ID "ID-D2", the sales destination of the in-vehicle device 101, and the upload destination for the vehicle data of vehicle 1. In the example shown in Figure 10, the vehicle ID of vehicle 1 equipped with the in-vehicle device 101 with in-vehicle device ID "ID-D2", the sales destination of the in-vehicle device 101, and the upload destination for the vehicle data of vehicle 1 are "ID-C3", "Company Z", and "https: / / ccc.com / data3", respectively.

[0134] Referring again to Figures 3 and 9, in the setting server 151, once the setting processing unit 24 completes the registration process, it transmits the setting information S2, which is included in the setting-related information K2 received from the authentication unit 22, to the vehicle 1B via the communication unit 21 and the external network 171.

[0135] Specifically, the setting processing unit 24 outputs to the communication unit 21 a pair U2 of setting information S2 and vehicle ID, which is included in the setting-related information K2 received from the authentication unit 22.

[0136] The communication unit 21 creates an IP packet (hereinafter also referred to as "packet P3") which contains the configuration information S2 for group U2 received from the configuration processing unit 24, and includes the IP address of its own configuration server 151 and the IP address of vehicle 1, which is the vehicle ID for group U2, as the source address and destination IP address, respectively. The communication unit 21 then transmits the created packet P3 to vehicle 1 via the external network 171 and the wireless base station equipment.

[0137] Referring to Figures 2 and 9, in the in-vehicle device 101 retrofitted to vehicle 1B, when the external communication unit 12 receives packet P3 from the configuration server 151 via the external network 171, it outputs the configuration information S2 contained in the received packet P3 to the configuration unit 13.

[0138] When the setting unit 13 receives setting information S2 from the external communication unit 12, it stores the setting information S2 in the storage unit 15. Then, the setting unit 13 makes settings related to the upload of the vehicle data group based on the setting information S2. Specifically, for example, the setting unit 13 makes settings so that the external communication unit 12 sends the vehicle data group to the upload destination indicated by the upload destination information contained in the setting information S2.

[0139] In the example shown in Figure 9, the setting unit 13 configures the external communication unit 12 to send the vehicle data group to the vehicle management server 161B, which is the vehicle management server 161. For example, the vehicle management server 161B is a server owned by a different manufacturer than the manufacturer of vehicle 1A. Note that the vehicle management server 161A and the vehicle management server 161B may be servers owned by the same manufacturer. In this case, for example, within the manufacturer of vehicle 1, the department that owns the vehicle management server 161A and the department that owns the vehicle management server 161B are different from each other.

[0140] When the external communication unit 12 receives a group of vehicle data from the collection unit 14, it transmits the group of vehicle data and vehicle-related information G2, which includes the vehicle ID and authentication information Pb stored in the storage unit 15, to the vehicle management server 161B.

[0141] Specifically, the external communication unit 12 accesses the URL indicated by the upload destination information stored in the storage unit 15 via the wireless base station device and the external network 171, and uploads the vehicle-related information G2 to the vehicle management server 161B.

[0142] [Operation Flow] Next, the operation flow of each device in the communication system 501 according to the embodiment of this disclosure will be explained with reference to the drawings.

[0143] Figure 11 is a flowchart that shows an example of the operation procedure when the configuration server according to the embodiment of this disclosure performs configuration processing.

[0144] Referring to Figure 11, first, the configuration server 151 waits for the reception of user information from the terminal device 301 (NO in step ST101).

[0145] Then, when the configuration server 151 receives user information from the terminal device 301 (YES in step ST101), it sends authentication information Pa to the terminal device 301 (step ST102).

[0146] Next, the configuration server 151 awaits the reception of configuration-related information from the terminal device 301. For example, as described above, the configuration-related information includes the in-vehicle device ID of the in-vehicle device 101 to be configured, the vehicle ID of the vehicle 1 to which the in-vehicle device 101 is retrofitted, the configuration information S of the in-vehicle device 101, and the authentication information Pa used in the authentication process C1 (NO in step ST103).

[0147] Next, when the configuration server 151 receives configuration-related information from the terminal device 301 (YES in step ST103), it performs authentication processing C1 on the terminal device 301 using the authentication information Pa included in the received configuration-related information (step ST104).

[0148] Then, if the authentication process C1 is successful (YES in step ST105), the configuration server 151 refers to the set W1 in the storage unit 25 to identify the sales destination of the in-vehicle device 101 that corresponds to the in-vehicle device ID included in the received configuration-related information (step ST106).

[0149] Next, when the configuration server 151 identifies the sales destination of the in-vehicle device 101, it performs a registration process to register the in-vehicle device ID, vehicle ID, and upload destination information included in the received configuration-related information, as well as the identified sales destination of the in-vehicle device 101 (step ST107), into the corresponding table Tb.

[0150] Next, once the configuration server 151 has completed the registration process, it performs a configuration process to set the configuration information S in the in-vehicle device 101. For example, as described above, the configuration server 151 sends the configuration information S included in the received configuration-related information to the in-vehicle device 101 (step ST108).

[0151] On the other hand, if the authentication process C1 fails (NO in step ST105), the configuration server 151 sends authentication failure information L1 to the terminal device 301 that sent the configuration-related information (step ST109), and waits to receive new configuration-related information from the terminal device 301 (NO in step ST103).

[0152] Figure 12 is a flowchart illustrating an example of the operation procedure when the configuration server according to the embodiment of this disclosure performs a deletion process.

[0153] Referring to Figure 12, first, the configuration server 151 waits for the reception of service termination information from the terminal device 301 (NO in step ST201).

[0154] Then, when the configuration server 151 receives information about the suspension of use from the terminal device 301 (YES in step ST201), it performs authentication processing C1 on the terminal device 301 using the authentication information Pa included in the received information about the suspension of use (step ST202).

[0155] Next, if the authentication process C1 is successful (YES in step ST203), the configuration server 151 performs a notification process to notify the in-vehicle device 101 that its use in vehicle 1 has been stopped. For example, as described above, the configuration server 151 refers to the correspondence table Tb in the storage unit 25 to identify the vehicle ID and upload destination information corresponding to the in-vehicle device ID included in the received usage stop information. Then, the configuration server 151 sends upload stop information, which indicates a request to stop uploading the vehicle data group, along with the upload destination information, to vehicle 1 with that vehicle ID (step ST204).

[0156] Next, once the configuration server 151 has completed the notification process, it performs a deletion process to remove the record containing the in-vehicle device ID included in the received service termination information from the corresponding table Tb (step ST205). Steps ST204 and ST205 may be executed in any order or in parallel.

[0157] On the other hand, if the authentication process C1 fails (NO in step ST203), the configuration server 151 sends authentication failure information L1 to the terminal device 301 that sent the suspension information (step ST206), and waits to receive new suspension information from the terminal device 301 (NO in step ST201).

[0158] Figure 13 is a flowchart illustrating an example of the operation procedure when an in-vehicle device according to the embodiment of this disclosure performs settings related to uploading a group of vehicle data.

[0159] Referring to Figure 13, first, the in-vehicle device 101 waits for the reception of setting information S from the setting server 151 (NO in step ST301).

[0160] Then, when the in-vehicle device 101 receives setting information S from the setting server 151 (YES in step ST301), it configures the settings related to uploading the vehicle data group based on the received setting information S (step ST302).

[0161] Figure 14 is a flowchart illustrating an example of the operation procedure when an in-vehicle device according to an embodiment of the present disclosure performs data transmission processing.

[0162] Referring to Figure 14, first, the in-vehicle device 101 receives vehicle data from each in-vehicle device 202 and stores it in the storage unit 15 (step ST401).

[0163] The in-vehicle device 101 stores the new vehicle data received from each in-vehicle device 202 in the storage unit 15 until the processing timing T for the data collection process arrives (NO in step ST402) (step ST401).

[0164] Then, when the processing timing T arrives (YES in step ST402), the in-vehicle device 101 retrieves the vehicle data stored in the storage unit 15 during the period from the previous processing timing T to the current processing timing T (step ST403).

[0165] Next, the in-vehicle device 101 performs a data transmission process to send the extracted vehicle data group and vehicle-related information, including the vehicle ID and authentication information Pb stored in the storage unit 15, to the vehicle management server 161 (step ST404), and receives new vehicle data from each in-vehicle device 202 and stores it in the storage unit 15 (step ST401).

[0166] Figure 15 is a flowchart that shows an example of the operation procedure when the vehicle management server according to the embodiment of this disclosure performs analysis processing.

[0167] Referring to Figure 15, first, the vehicle management server 161 waits to receive vehicle-related information from the in-vehicle device 101 (NO in step ST501).

[0168] Next, the vehicle management server 161 receives vehicle-related information from the in-vehicle device 101 (YES in step ST501), and uses the authentication information Pb contained in the received vehicle-related information to perform the authentication process C2 of the in-vehicle device 101 (step ST502).

[0169] Then, if the authentication process C2 is successful (YES in step ST503), the vehicle management server 161 performs an analysis process to analyze the vehicle data group included in the received vehicle-related information (step ST504), and waits for the reception of new vehicle-related information from the in-vehicle device 101 (NO in step ST501).

[0170] On the other hand, if the authentication process C2 fails, the vehicle management server 161 sends authentication failure information L2 to the in-vehicle device 101, the source of the vehicle-related information (step ST505), and waits to receive new vehicle-related information from the in-vehicle device 101 (NO in step ST501).

[0171] Figure 16 is a diagram showing an example of the processing sequence of a terminal device, an in-vehicle device, a configuration server, and a vehicle management server in a communication system according to an embodiment of the present disclosure.

[0172] Referring to Figure 16, first, the terminal device 301 sends user information to the configuration server 151 (step ST601).

[0173] Next, when the configuration server 151 receives user information from the terminal device 301, it sends authentication information Pa to the terminal device 301 (step ST602).

[0174] Next, the terminal device 301 stores the authentication information Pa received from the configuration server 151 in its own storage unit (step ST603).

[0175] Next, the terminal device 301 sends to the configuration server 151 configuration-related information, which includes the in-vehicle device ID of the in-vehicle device 101 to be configured, the vehicle ID of the vehicle 1 to which the in-vehicle device 101 is retrofitted, and the configuration information S of the in-vehicle device 101, along with the authentication information Pa stored in its own memory (step ST604).

[0176] Next, when the configuration server 151 receives configuration-related information from the terminal device 301, it performs authentication processing C1 on the terminal device 301 using the authentication information Pa included in the received configuration-related information. Here, we assume that authentication processing C1 is successful (step ST605).

[0177] Next, the configuration server 151 refers to the set W1 in the storage unit 25 to identify the sales destination of the in-vehicle device 101 that corresponds to the in-vehicle device ID included in the received configuration-related information (step ST606).

[0178] Next, the configuration server 151 identifies the sales destination of the in-vehicle device 101 and performs a registration process to register the in-vehicle device ID, vehicle ID, and upload destination information included in the in-vehicle device ID contained in the received configuration-related information, as well as the identified sales destination of the in-vehicle device 101 (step ST607), into the corresponding table Tb.

[0179] Next, once the configuration server 151 has completed the registration process, it performs a configuration process to set the configuration information S in the in-vehicle device 101. For example, as described above, the configuration server 151 sends the configuration information S included in the received configuration-related information to the in-vehicle device 101 (step ST608).

[0180] Next, when the in-vehicle device 101 receives configuration information S from the configuration server 151, it configures the settings related to uploading the vehicle data group based on the received configuration information S (step ST609).

[0181] Next, when the processing timing T arrives, the in-vehicle device 101 retrieves the vehicle data stored in the storage unit 15 during the period from the previous processing timing T to the current processing timing T (step ST610).

[0182] Next, the in-vehicle device 101 transmits the retrieved vehicle data group and vehicle-related information, including the vehicle ID and authentication information Pb stored in the storage unit 15, to the vehicle management server 161 (step ST611).

[0183] Next, when the vehicle management server 161 receives vehicle-related information from the in-vehicle device 101, it performs authentication processing C2 on the in-vehicle device 101 using the authentication information Pb contained in the received vehicle-related information. Here, we assume that authentication processing C2 is successful (step ST612).

[0184] Next, the vehicle management server 161 performs analysis processing to analyze the group of vehicle data included in the vehicle-related information received from the in-vehicle device 101 (step ST613).

[0185] Figure 17 shows another example of the processing sequence of a terminal device, an in-vehicle device, and a configuration server in a communication system according to an embodiment of the present disclosure.

[0186] Referring to Figure 17, first, the terminal device 301 sends the service termination information to the setting server 151 (step ST701).

[0187] Next, when the configuration server 151 receives the service suspension information from the terminal device 301, it performs the authentication process C1 on the terminal device 301 using the authentication information Pa contained in the received service suspension information. Here, we assume that the authentication process C1 is successful (step ST702).

[0188] Next, if the authentication process C1 is successful, the configuration server 151 performs a notification process to notify the in-vehicle device 101 that use in vehicle 1 has been stopped. For example, as described above, the configuration server 151 refers to the correspondence table Tb in the storage unit 25 to identify the vehicle ID and upload destination information corresponding to the in-vehicle device ID included in the received use stop information. Then, the configuration server 151 sends upload stop information, which indicates a request to stop uploading vehicle data, along with the said upload destination information, to vehicle 1 with that vehicle ID (step ST703).

[0189] Next, the configuration server 151 performs a deletion process to remove the record containing the in-vehicle device ID included in the received service termination information from the corresponding table Tb (step ST704). Steps ST703 and ST704 may be executed in any order or in parallel.

[0190] Next, when the in-vehicle device 101 receives upload stop information from the setting server 151, it configures itself not to send the vehicle data group to the upload destination indicated by the upload destination information included in the upload stop information. For example, as described above, the in-vehicle device 101 deletes the upload destination information and authentication information Pb stored in the storage unit 15 (step ST705).

[0191] In the communication system 501 according to the embodiment of this disclosure, the setting server 151 is configured to acquire the in-vehicle device ID of the in-vehicle device 101 to be configured, the vehicle ID of the vehicle 1 to which the in-vehicle device 101 is retrofitted, and the setting information S of the in-vehicle device 101 from the terminal device 301, but is not limited to this configuration. The setting server 151 may be configured to acquire either the in-vehicle device ID or the vehicle ID and the setting information S. Alternatively, the setting server 151 may be configured to acquire other information in addition to the in-vehicle device ID, vehicle ID, and setting information S, instead of acquiring either or both of the in-vehicle device ID and the vehicle ID.

[0192] Furthermore, in the communication system 501 according to the embodiment of this disclosure, the setting server 151 is configured to hold a correspondence table Tb that shows the correspondence between the in-vehicle device ID, the vehicle ID, and the upload destination information, but the system is not limited to this configuration. The setting server 151 may also be configured not to hold a correspondence table Tb.

[0193] Furthermore, in the communication system 501 according to the embodiment of this disclosure, the setting server 151 is configured to delete the correspondence relationship Q corresponding to the in-vehicle device 101 from the correspondence table Tb when the use of the in-vehicle device 101 in the vehicle 1 is stopped, but the invention is not limited to this. The setting server 151 may be configured not to delete the correspondence relationship Q from the correspondence table Tb. In this case, for example, the correspondence table Tb includes, in addition to the correspondence relationship Q, a determination flag indicating whether the correspondence relationship Q is valid or invalid.

[0194] Furthermore, in the communication system 501 according to the embodiment of this disclosure, the setting server 151 is configured to perform a notification process to notify the in-vehicle device 101 of the cessation of use in the vehicle 1, but the system is not limited to this. The setting server 151 may be configured not to perform a notification process. In this case, for example, the terminal device 301 in the communication system 501 performs the notification process.

[0195] Furthermore, although the communication device in the communication system 501 according to the embodiment of this disclosure is described as an in-vehicle device retrofitted to the vehicle 1, it is not limited to this. The equipment to which the communication device is retrofitted is not limited to the vehicle 1, but may be other types of equipment such as batteries and generators.

[0196] Furthermore, some or all of the functions of the configuration server 151 according to the embodiment of this disclosure may be provided by cloud computing. That is, the configuration server 151 according to the embodiment of this disclosure may be a cloud server composed of multiple servers.

[0197] Furthermore, some or all of the functions of the vehicle management server 161 according to the embodiment of this disclosure may be provided by cloud computing. That is, the vehicle management server 161 according to the embodiment of this disclosure may be a cloud server composed of multiple servers.

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

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

[0200] The above description includes the following features: [Addendum 1] A setting device comprising: an acquisition unit that acquires setting information for a communication device, including upload destination information for a device to which data relating to a communication device has been retrofitted; and a setting processing unit that performs setting processing for setting the setting information acquired by the acquisition unit on the communication device, wherein the upload destination device is a device under a different management entity than the setting device, and the setting information includes first identification information for identifying the communication device, second identification information for identifying the device, authentication information used in the authentication processing of the communication device by the upload destination device, and the upload destination information.

[0201] [Note 2] A setting device comprising a processing circuit, wherein the processing circuit acquires setting information for the communication device, including upload destination information for a device to which data relating to a device to which a communication device has been retrofitted is uploaded, and performs setting processing to set the acquired setting information on the communication device, wherein the upload destination device is a device under a different management entity than the setting device.

[0202] [Note 3] A communication device comprising a processing circuit, the processing circuit receiving setting information of the communication device from an external device outside the device, which includes information about a device to which data relating to the device to which the communication device is retrofitted is uploaded, and transmitting the data to the upload destination device based on the received setting information, wherein the upload destination device is a device under a different management entity than the external device.

[0203] 1, 1A, 1B Vehicle 11 In-vehicle communication unit 12 External communication unit 13 Setting unit 14 Collection unit 15, 25 Storage unit 21, 31 Communication unit 22, 32 Authentication unit 23 Deletion processing unit 24 Setting processing unit 33 Analysis unit 51 CAN bus 101 In-vehicle device 151 Setting server 161, 161A, 161B Vehicle management server 171 External network 202, 202A, 202B In-vehicle equipment 301 Terminal device 401 In-vehicle network 501 Communication system Tb Correspondence table

Claims

1. A setting device comprising: an acquisition unit that acquires setting information for a communication device, including upload destination information for a device to which data relating to a communication device has been retrofitted; and a setting processing unit that performs setting processing for setting the setting information acquired by the acquisition unit on the communication device, wherein the upload destination device is a device under a different management entity than the setting device.

2. The setting device according to claim 1, wherein the acquisition unit further acquires first identification information for identifying the communication device and second identification information for identifying the device, and the setting processing unit performs the setting process using the first identification information and the second identification information acquired by the acquisition unit.

3. The setting device according to claim 2, further comprising a storage unit that holds correspondence information indicating the correspondence between the first identification information, the second identification information, and the upload destination information.

4. The setting device according to claim 3, further comprising: an update unit that deletes the correspondence relationship corresponding to the communication device from the correspondence information when the use of the communication device is stopped at the equipment to which the communication device is installed; and a notification unit that notifies the communication device of the cessation of use.

5. The setting device according to any one of claims 1 to 4, wherein the manufacturer of the setting device is the same as the manufacturer of the communication device.

6. A communication device comprising: a receiving unit that receives configuration information of the communication device from an external device outside the device, including information about a device to which data relating to the communication device is retrofitted; and a transmitting unit that transmits the data to the upload destination device based on the configuration information received by the receiving unit, wherein the upload destination device is a device under a different management entity than the external device.

7. A communication system comprising a communication device that is retrofitted to a device, and a setting device that manages the communication device, wherein the setting device acquires setting information for the communication device, including information about a device to which data relating to the device is uploaded, the setting device performs a setting process to set the acquired setting information on the communication device, the communication device transmits the data to the upload destination device based on the setting information, and the upload destination device is a device under a different management entity than the setting device.

8. A setting method for a setting device, comprising the steps of: obtaining setting information for a communication device, including upload destination information for a device to which data relating to a device to which a communication device has been retrofitted is uploaded; and performing a setting process for setting the acquired setting information for the communication device, wherein the upload destination device is a device under a different management entity than the setting device.

9. A method for transmitting information in a communication device, comprising the steps of: obtaining configuration information of the communication device from an external device located outside the device, including information about a device to which data relating to equipment to which the communication device is retrofitted is uploaded; and transmitting the data to the upload destination device based on the obtained configuration information, wherein the upload destination device is a device under a different management entity than the external device.

10. A setting program used in a setting device, which causes a computer to function as: an acquisition unit that acquires setting information for a communication device, including upload destination information for a device to which data relating to a device to which a communication device has been retrofitted is uploaded; and a setting processing unit that performs processing for setting the setting information acquired by the acquisition unit on the communication device, wherein the upload destination device is a device under a different management entity than the setting device.

11. An information transmission program used in a communication device, wherein the computer is configured to function as: an acquisition unit that acquires configuration information of the communication device from an external device outside the device, including information about a device to which data relating to the communication device is retrofitted; and a transmission unit that transmits the data to the upload destination device based on the configuration information acquired by the acquisition unit, wherein the upload destination device is a device under a different management entity than the external device.

Images