In-vehicle device, information processing method, and information processing program

Abstract

To provide an in-vehicle device, an information processing method, and an information processing program that easily accommodate additions or changes of vehicle-related functions.SOLUTION: An in-vehicle device 101 that is mounted on a vehicle 1 includes: a communication unit 31 that receives setting information that corresponds to a selected function and is related to an in-vehicle apparatus, from a management device; and a setting unit 12 that performs setting processing related to the in-vehicle apparatus, based on the setting information related to the in-vehicle apparatus received by the communication unit.SELECTED DRAWING: Figure 5

Description

[Technical Field]

[0001] The present disclosure relates to an in-vehicle device, an information processing method, and an information processing program. [Background technology]

[0002] Conventionally, technologies relating to an in-vehicle network equipped with a plurality of in-vehicle ECUs (Electronic Control Units) have been developed. For example, Japanese Patent Laid-Open Publication No. 2000-229546 (Patent Document 1) discloses the following vehicle control device. That is, the vehicle control device includes a central ECU 1 that manages the operation of the entire vehicle, a plurality of terminal ECUs 2a, 2b, . . . 2n that respectively control the operation of each part of the vehicle, and an in-vehicle LAN 3 that interconnects these ECUs. The central ECU obtains vehicle information indicating vehicle specifications from information on terminals selectively shorted by a vehicle information cartridge 8 made of conductive parts and attached to a connector unit 7, and provides the vehicle information to each of the terminal ECUs. The function type of each terminal ECU is individually set according to the vehicle information. The vehicle specifications are then managed by the vehicle information cartridge. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2000-229546 Summary of the Invention [Problem to be solved by the invention]

[0004] In the past, the settings for each on-board ECU to execute various vehicle functions were individually configured before the vehicle was shipped. Therefore, if a change in the functions to be provided occurred after the vehicle was shipped, it was necessary for the dealer or other facility to individually change the settings for each vehicle.

[0005] As described above, the vehicle control device described in Patent Document 1 uses a vehicle information cartridge to set functions and control characteristics for each on-board ECU according to the vehicle specifications. However, when the settings of the on-board ECU are changed or an on-board ECU is added, the vehicle information cartridge must be changed or added, which creates a problem of being unable to respond flexibly.

[0006] The present invention has been made to solve the above-mentioned problems, and its purpose is to provide an in-vehicle device, an information processing method, and an information processing program that can easily accommodate additions or changes to vehicle functions. [Means for solving the problem]

[0007] The vehicle-mounted device of the present disclosure is an vehicle-mounted device that is mounted on a vehicle and includes a communication unit that receives setting information regarding the vehicle's vehicle-mounted equipment corresponding to a selected function from a management device, and a setting unit that performs setting processing regarding the vehicle-mounted equipment based on the setting information received by the communication unit.

[0008] The information processing method disclosed herein is an information processing method in an on-board device mounted in a vehicle, and includes a step of receiving setting information regarding the on-board equipment of the vehicle corresponding to a selected function from a management device, and a step of performing setting processing regarding the on-board equipment based on the received setting information.

[0009] The information processing program disclosed herein is an information processing program used in an on-board device installed in a vehicle, and is a program that causes a computer to function as a communication unit that receives setting information regarding the on-board equipment of the vehicle corresponding to a selected function from a management device, and a setting unit that performs setting processing regarding the on-board equipment based on the setting information received by the communication unit.

[0010] One aspect of the present disclosure can be realized not only as an in-vehicle device equipped with such a characteristic processing unit, but also as a semiconductor integrated circuit that realizes part or all of the in-vehicle device, or as a system that includes the in-vehicle device. [Effects of the Invention]

[0011] According to the present disclosure, it is possible to easily accommodate additions or changes to vehicle functions. [Brief explanation of the drawings]

[0012] [Figure 1] FIG. 1 is a diagram illustrating a configuration of a communication system according to an embodiment of the present disclosure. [Figure 2] FIG. 2 is a diagram illustrating a configuration of a management device according to an embodiment of the present disclosure. [Figure 3] FIG. 3 is a diagram illustrating an example of correspondence information stored in a storage unit in a management device according to an embodiment of the present disclosure. [Figure 4] FIG. 4 is a diagram illustrating an example of correspondence information stored in a storage unit in a management device according to an embodiment of the present disclosure. [Figure 5] FIG. 5 is a diagram illustrating an example of the configuration of an in-vehicle device according to an embodiment of the present disclosure. [Figure 6] FIG. 6 is a diagram illustrating an example of correspondence information stored in a storage unit in a management device according to an embodiment of the present disclosure. [Figure 7] FIG. 7 is a diagram illustrating an example of a history of vehicle information stored in a storage unit in a management device according to an embodiment of the present disclosure. [Figure 8] FIG. 8 is a diagram illustrating an example of a sequence of the communication system when the in-vehicle device according to the embodiment of the present disclosure is started up in a state where no setting information is saved. [Figure 9] FIG. 9 is a diagram illustrating an example of a sequence of a communication system when an in-vehicle device according to an embodiment of the present disclosure is started up with setting information saved. DETAILED DESCRIPTION OF THE INVENTION

[0013] First, the contents of the embodiments of the present disclosure will be listed and described. (1) An in-vehicle device according to an embodiment of the present disclosure is an in-vehicle device mounted on a vehicle, and includes a communication unit that receives setting information related to the in-vehicle equipment of the vehicle corresponding to a selected function from a management device, and a setting unit that performs setting processing related to the in-vehicle equipment based on the setting information received by the communication unit.

[0014] With this configuration, after the vehicle is shipped, the on-board devices can be easily configured to support any desired function related to the vehicle. Also, for on-board devices added to the vehicle after the vehicle is shipped, the settings can be easily configured to support any desired function, just like for on-board devices installed in the vehicle before the shipment. Therefore, it is possible to easily accommodate additions or changes to vehicle functions.

[0015] (2) The communication unit may receive the setting information for at least one of a vehicle model and a model year.

[0016] With this configuration, it is no longer necessary to configure each vehicle model or year to accommodate the functions to be realized before the vehicle is shipped, and common settings can be made between vehicles of different models or years, thereby reducing the increase in product numbers and simplifying configuration and management.

[0017] (3) The setting unit may use the setting information for setting vehicle information related to the vehicle to be transmitted from the vehicle to the management device.

[0018] With this configuration, vehicle information for executing any function can be collected from the vehicle to which the setting information is sent, and various functions can be realized using the vehicle information.

[0019] (4) The vehicle information may include information regarding the running of the vehicle.

[0020] With this configuration, it is possible to realize functions such as driving management using data related to vehicle driving.

[0021] (5) The vehicle information may include information indicating measurement results for the vehicle.

[0022] With this configuration, it is possible to realize functions such as a driving environment survey using the measurement results from sensors in the vehicle.

[0023] (6) In accordance with the setting process, the communication unit may acquire the vehicle information from the frame based on data location information included in the setting information and used to identify the vehicle information within the frame transmitted and received by the vehicle, and transmit the vehicle information to the management device.

[0024] For example, the storage location of vehicle information in a frame may differ depending on the model and year of manufacture, but by creating data location information in the management device, it is not necessary to create different application software for each vehicle, compared to a configuration in which data location information is registered in advance in the vehicle, and this increases the flexibility of system construction.In addition, since the vehicle information to be transmitted can be extracted from the frame and transmitted to the management device, the amount of communication from the vehicle to the outside can be reduced.

[0025] (7) The communication unit may transmit the vehicle information to the management device at a timing for transmitting the vehicle information to the management device indicated by transmission timing information included in the setting information, in accordance with the setting process.

[0026] The optimal timing for transmitting vehicle information may vary depending on the function to be realized, and by configuring the management device to create transmission timing information as described above, there is no need to create different application software for each vehicle, compared to a configuration in which transmission timing information is registered in advance in the vehicle, thereby increasing the flexibility of system construction.

[0027] (11) An information processing method according to an embodiment of the present disclosure is an information processing method in an on-board device mounted on a vehicle, and includes the steps of receiving setting information for on-board equipment of the vehicle corresponding to a selected function from a management device, and performing setting processing for the on-board equipment based on the received setting information.

[0028] With this configuration, after the vehicle is shipped, the on-board devices can be easily configured to support any desired function related to the vehicle. Also, for on-board devices added to the vehicle after the vehicle is shipped, the settings can be easily configured to support any desired function, just like for on-board devices installed in the vehicle before the shipment. Therefore, it is possible to easily accommodate additions or changes to vehicle functions.

[0029] (12) An information processing program according to an embodiment of the present disclosure is an information processing program used in an on-board device mounted in a vehicle, and is a program for causing a computer to function as a communication unit that receives setting information related to the on-board equipment of the vehicle corresponding to a selected function from a management device, and a setting unit that performs setting processing related to the on-board equipment based on the setting information received by the communication unit.

[0030] With this configuration, after the vehicle is shipped, the on-board devices can be easily configured to support any desired function related to the vehicle. Also, for on-board devices added to the vehicle after the vehicle is shipped, the settings can be easily configured to support any desired function, just like for on-board devices installed in the vehicle before the shipment. Therefore, it is possible to easily accommodate additions or changes to vehicle functions.

[0031] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. In the drawings, identical or corresponding parts are designated by the same reference numerals, and their description will not be repeated. Furthermore, at least some of the embodiments described below may be combined in any manner.

[0032] [Overall configuration] 1 is a diagram illustrating a configuration of a communication system according to an embodiment of the present disclosure. Referring to FIG. 1, a communication system 301 includes one or more in-vehicle ECUs (in-vehicle devices) 101, a terminal device 161, and a management device 201. Each in-vehicle ECU 101, terminal device 161, and management device 201 can transmit and receive information via a network 151 such as the Internet. The in-vehicle ECU 101 and the in-vehicle devices 111 are mounted on a vehicle 1.

[0033] The management device 201 is managed, for example, by a business operator that provides functions related to the vehicle 1. The terminal device 161 is managed, for example, by a business operator or an individual (hereinafter collectively referred to as a user) that executes the functions related to the vehicle 1. Specifically, the functions related to the vehicle 1 are, for example, a function for managing the driving history of the vehicle 1.

[0034] The management device 201 collects vehicle information about the corresponding vehicle 1 from one or more on-board ECUs 101. Then, the management device 201 creates information to be provided that is used to execute the above function selected by the user, based on the collected vehicle information or information about the one or more vehicles. The vehicle information includes, for example, information about the traveling of the vehicle 1.

[0035] Specifically, the management device 201 collects, for example, location information, vehicle speed information, etc. of each of the multiple vehicles 1, and creates, as provided information, map information, etc., in which the traveling position of each vehicle 1 is mapped on a map in a display mode according to the vehicle speed, based on the collected location information, vehicle speed information, etc. For example, by using this provided information, a business operator, which is a user, can manage the operation of each vehicle 1.

[0036] The vehicle information is not limited to location information or vehicle speed information, but may be, for example, brake information indicating the brake state. The vehicle information is also not limited to information related to the traveling of the vehicle 1, but may be information indicating measurement results in the vehicle 1, specifically, information indicating measurement results by on-board devices 111 such as sensors in the vehicle 1, such as image information showing an image of the surroundings of the vehicle 1, door open / close status, and temperature information. The vehicle information may also be, for example, identification information of the vehicle 1 or network configuration information of the vehicle 1.

[0037] [Configuration of management device] 2 is a diagram illustrating a configuration of a management device according to an embodiment of the present disclosure. Referring to FIG. 2, management device 201 includes a communication unit 21, a storage unit 22, a setting information creation unit 23, and a provision information creation unit 24. The communication unit 21, the setting information creation unit 23, and the provision information creation unit 24 may all or partly be implemented by a processor such as a CPU (Central Processing Unit) and a DSP (Digital Signal Processor). The storage unit 22 may be, for example, a non-volatile memory.

[0038] The communication unit 21 transmits and receives information to and from a plurality of in-vehicle ECUs 101 and a terminal device 161 via the network 151 .

[0039] The storage unit 22 stores correspondence information indicating the correspondence between functions executed by a user and setting information for the vehicle 1. The setting information is, for example, information used for setting up the vehicle 1 to transmit vehicle information about the vehicle 1 from the vehicle 1 to the management device 201. In other words, the setting information is information related to the setting made for the vehicle 1 in order to obtain vehicle information from the vehicle 1 that is used to create the information to be provided.

[0040] 3 and 4 are diagrams illustrating an example of correspondence information stored in a storage unit in the management device according to the embodiment of the present disclosure. Referring to Fig. 3, the storage unit 22 stores, for example, a correspondence table Ta indicating the correspondence between functions and vehicle information.

[0041] Specifically, vehicle speed information and brake information are used to create information to be provided for function A. Vehicle speed information and image information are used to create information to be provided for function B.

[0042] When a new function is added or when an existing function is changed, the correspondence table Ta is updated by the user, for example.

[0043] 4, in addition to the correspondence table Ta, the storage unit 22 further stores a correspondence table Tb indicating, for each vehicle type, identification information (hereinafter also referred to as storage ID) of a frame in which vehicle information of each in-vehicle device 111 is stored. The vehicle type is set, for example, according to the use and destination of the vehicle 1.

[0044] In the vehicle 1, the vehicle information acquired by each on-board device 111 is transmitted and received in accordance with, for example, the CAN (Controller Area Network) (registered trademark) standard. In this case, the vehicle information is stored in a CAN frame to which a CAN-ID (Identifier) ​​indicating the type of data, etc., is attached. The CAN frame may be a frame conforming to the classic CAN standard or a frame conforming to the CAN FD (CAN with Flexible Data Rate) standard.

[0045] Specifically, in vehicle 1 of vehicle type X1, the storage ID for vehicle speed information is CAN-ID "1", the storage ID for braking information is CAN-ID "2", and the storage ID for image information is CAN-ID "3". In vehicle 1 of vehicle type X2, the storage ID for vehicle speed information is CAN-ID "3", the storage ID for braking information is CAN-ID "2", and the storage ID for image information is CAN-ID "1". In vehicle 1 of vehicle type X3, the storage ID for vehicle speed information is CAN-ID "1", the storage ID for braking information is CAN-ID "1", and the storage ID for image information is CAN-ID "2". In this example, in vehicle 1 of vehicle type X3, vehicle speed information and braking information are stored in CAN frames with the same CAN-ID.

[0046] Note that storage unit 22 is not limited to a configuration in which correspondence information is stored in correspondence table Ta and correspondence table Tb, and may store, for example, a table that combines the contents of correspondence table Ta and the contents of correspondence table Tb.

[0047] Referring back to FIG. 2, the setting information creating unit 23 creates setting information for the in-vehicle device 111 that corresponds to the selected function.

[0048] More specifically, it is assumed that the user newly selects a function by operating the terminal device 161. In this case, the terminal device 161 transmits selection information indicating the user's selection result to the management device 201 via the network 151.

[0049] In the management device 201, the communication unit 21, for example, accepts a function selection by a user and outputs selection information indicating the selection result to the setting information creation unit 23. That is, the communication unit 21 receives the selection information transmitted from the terminal device 161 via the network 151 and outputs the received selection information to the setting information creation unit 23.

[0050] The setting information creation unit 23 stores the selection information received from the communication unit 21 in the storage unit 22. The setting information creation unit 23 also references the above-mentioned correspondence information to acquire setting information corresponding to the selected function. The setting information indicates, for example, the type of vehicle information data used to execute the function. More specifically, the setting information creation unit 23 creates the setting information based on the correspondence table Ta and the correspondence table Tb. For example, assume that the selection information indicates "function A." In this case, the setting information creation unit 23 references the correspondence table Ta to confirm that the vehicle information corresponding to function A is vehicle speed information and braking information.

[0051] Then, the setting information creation unit 23 creates setting information for each vehicle type by referring to the correspondence table Tb. The setting information creation unit 23 creates setting information indicating CAN-ID "1" corresponding to the vehicle speed information and CAN-ID "2" corresponding to the braking information as setting information to be transmitted to the vehicle 1 of vehicle type X1. The setting information creation unit 23 then outputs the created setting information corresponding to vehicle type X1 to the communication unit 21. The communication unit 21 transmits the setting information created by the setting information creation unit 23 to one or more vehicles 1 of vehicle type X1 via the network 151.

[0052] Furthermore, the setting information creation unit 23 creates setting information indicating the CAN-ID "3" corresponding to the vehicle speed information and the CAN-ID "2" corresponding to the braking information as setting information to be transmitted to the vehicle 1 of the vehicle type X2. Then, the setting information creation unit 23 outputs the created setting information corresponding to the vehicle type X2 to the communication unit 21. The communication unit 21 transmits the setting information created by the setting information creation unit 23 to one or more vehicles 1 of the vehicle type X2 via the network 151.

[0053] Furthermore, the setting information creation unit 23 creates setting information indicating the CAN-ID "1" corresponding to the vehicle speed information and the CAN-ID "1" corresponding to the braking information as setting information to be transmitted to the vehicle 1 of the vehicle type X3. Then, the setting information creation unit 23 outputs the created setting information corresponding to the vehicle type X3 to the communication unit 21. The communication unit 21 transmits the setting information created by the setting information creation unit 23 to one or more vehicles 1 of the vehicle type X3 via the network 151.

[0054] The correspondence table Tb may indicate the storage ID of each piece of vehicle information for only one vehicle model, that is, the setting information creating unit 23 may be configured to create setting information for only one vehicle model.

[0055] In the vehicle 1, the in-vehicle ECU 101 receives the setting information transmitted from the management device 201, and performs setting processing for the in-vehicle device 111 in the vehicle 1 based on the received setting information. That is, the in-vehicle ECU 101 performs setting processing so that vehicle information corresponding to the CAN-ID indicated in the received setting information is transmitted to the management device 201. Details of the setting processing by the in-vehicle ECU 101 will be described later.

[0056] In the management device 201, when the communication unit 21 receives the vehicle information transmitted from the in-vehicle ECU 101 after the setting process via the network 151, the communication unit 21 outputs the received vehicle information to the provided information creation unit 24. The provided information creation unit 24 creates provided information based on the vehicle information received from the communication unit 21.

[0057] More specifically, it is assumed that the provided information creation unit 24 confirms that function A has been selected by the user by referring to the selection information stored in the storage unit 22. It is also assumed that the provided information creation unit 24 receives vehicle speed information and braking information from the communication unit 21 as vehicle information. In this case, the provided information creation unit 24 creates provided information to be used when executing function A, using the vehicle speed information and braking information received from the communication unit 21. Then, the provided information creation unit 24 stores the created provided information in the storage unit 22.

[0058] For example, when executing function A, the user operates the terminal device 161 to request the management device 201 for the provided information corresponding to function A. When the communication unit 21 in the management device 201 receives the request for provided information from the terminal device 161, the communication unit 21 acquires the provided information corresponding to function A stored in the storage unit 22, and transmits the acquired provided information to the terminal device 161 via the network 151. This allows the user to execute function A using the provided information created by the management device 201.

[0059] In addition, the setting information is not limited to information used for settings to send vehicle information from vehicle 1 to management device 201, but may also be information used for some other settings, such as operation settings to make in-vehicle equipment 111 correspond to the selected function.

[0060] Furthermore, the storage unit 22 may not store the correspondence information. In this case, the setting information creation unit 23 creates the setting information by performing some other calculation process without using the correspondence information.

[0061] Furthermore, the information to be provided may be created by a device other than the management device 201. In this case, the management device 201 transmits the vehicle information received from the vehicle 1 to the other device.

[0062] Furthermore, the user may directly input the selected function to the management device 201 without using the terminal device 161. In this case, the communication system 301 does not need to include the terminal device 161.

[0063] Furthermore, the management device 201 is not limited to a configuration that acquires the result of a function selection by a user, but may be a configuration that automatically selects a function based on some kind of information, for example.

[0064] [Configuration of on-board equipment] FIG. 5 is a diagram illustrating an example of a configuration of an in-vehicle device according to an embodiment of the present disclosure. Referring to FIG. 5, an in-vehicle ECU 101 is an example of an in-vehicle device, and is connected to a plurality of in-vehicle devices 111 via, for example, a CAN bus 10, and is capable of communicating with the plurality of in-vehicle devices 111 connected to the in-vehicle ECU 101. The in-vehicle ECU 101 includes a setting unit 12, a storage unit 13, and a communication unit 31. The communication unit 31 includes an exterior communication unit 11 and an interior communication unit 14. Some or all of the exterior communication unit 11, the setting unit 12, and the interior communication unit 14 are realized by a processor such as a CPU and a DSP. The storage unit 13 is, for example, a non-volatile memory.

[0065] The exterior-vehicle communication unit 11 communicates with the management device 201 via the network 151 by wirelessly communicating with a wireless base station (not shown) in accordance with a communication method such as WiFi (registered trademark), LTE (Long Term Evolution), or 5G. For example, the exterior-vehicle communication unit 11 receives setting information transmitted from the management device 201 via the network 151 and outputs the received setting information to the setting unit 12. Note that the exterior-vehicle communication unit 11 is not limited to a configuration in which it communicates with the management device 201 via a wireless base station and the network 151, and may be configured to communicate with the management device 201 via a wired line. Furthermore, the exterior-vehicle communication unit 11 may be configured to communicate with the management device 201 further via another in-vehicle ECU 101.

[0066] The in-vehicle communication unit 14 communicates with the multiple in-vehicle devices 111 in accordance with the CAN standard. For example, the in-vehicle communication unit 14 receives vehicle speed information transmitted from a vehicle speed sensor 111A and brake information transmitted from a brake control device 111B, and performs a process of relaying the received vehicle speed information and brake information to an autonomous driving ECU (not shown). The in-vehicle communication unit 14 also receives image information transmitted from a camera 111C, and performs a process of storing the received image information in the storage unit 13.

[0067] The in-vehicle ECU 101 and the in-vehicle devices 111 are not limited to being configured to transmit and receive CAN frames, and may be configured to perform communication in accordance with standards such as LIN (Local Interconnect Network), CXPI (Clock Extension Peripheral Interface), Ethernet (registered trademark), or USB (Universal Serial Bus).The in-vehicle ECU 101 and the in-vehicle devices 111 may also be configured to perform wireless communication in accordance with standards such as Bluetooth (registered trademark).

[0068] In this way, when communication is performed between the in-vehicle ECU 101 and the in-vehicle device 111 in accordance with a standard other than CAN, the setting information transmitted from the management device 201 to the in-vehicle ECU 101 includes, for example, a stored ID other than the CAN-ID.

[0069] The setting unit 12 receives the setting information output from the exterior communication unit 11, stores the setting information in the storage unit 13, and performs setting processing for the in-vehicle device 111 based on the setting information. For example, the setting unit 12 uses the setting information for setting to transmit vehicle information about the vehicle 1 from the vehicle 1 to the management device 201. Specifically, as the setting processing, the setting unit 12 performs setting so that vehicle information corresponding to the type of data indicated by the setting information is transmitted to the management device 201.

[0070] For example, in a vehicle 1 of vehicle type X1, when the setting unit 12 receives setting information indicating CAN-ID "1", as a setting process, it performs setting on the vehicle speed sensor 111A or the on-board ECU 101 so that the vehicle information of CAN-ID "1", i.e., vehicle speed information, is transmitted to the management device 201.

[0071] More specifically, when the in-vehicle communication unit 14 is receiving vehicle speed information transmitted from the vehicle speed sensor 111A periodically or irregularly, the setting unit 12 sets the in-vehicle communication unit 14 to output the received vehicle speed information to the external communication unit 11. The setting unit 12 also sets the external communication unit 11 to transmit the vehicle speed information received from the in-vehicle communication unit 14 to the management device 201.

[0072] On the other hand, when vehicle speed information is not being transmitted from the vehicle speed sensor 111A to the in-vehicle communication unit 14, the setting unit 12, as a setting process, requests the vehicle speed sensor 111A to transmit the vehicle speed information via the in-vehicle communication unit 14. In response to a request from the in-vehicle ECU 101, the vehicle speed sensor 111A transmits the vehicle speed information to the in-vehicle ECU 101 periodically or irregularly. The setting unit 12 also sets the in-vehicle communication unit 14 to output the received vehicle speed information to the external communication unit 11. The setting unit 12 also sets the external communication unit 11 to transmit the vehicle speed information received from the in-vehicle communication unit 14 to the management device 201.

[0073] By performing such setting processing, the speed information of the vehicle 1 indicated by the setting information is transmitted to the management device 201.

[0074] [Data location information and transmission timing information] The setting information may include data location information used to identify vehicle information in a frame transmitted and received by the vehicle 1. That is, the in-vehicle communication unit 14 may be configured to acquire vehicle information from the CAN frame based on the data location information included in the setting information in accordance with the setting process of the setting unit 12, and transmit the vehicle information to the management device 201.

[0075] The setting information may also include transmission timing information indicating the timing of transmission of the vehicle information to the management device 201. That is, the in-vehicle communication unit 14 may be configured to transmit the vehicle information to the management device 201 at the transmission timing to the vehicle information management device 201 indicated by the transmission timing information included in the setting information, in accordance with the setting process of the setting unit 12.

[0076] 6 is a diagram illustrating an example of correspondence information stored in a storage unit in a management device according to an embodiment of the present disclosure. Referring to FIG. 6, in addition to the correspondence tables Ta and Tb, the storage unit 22 may further store a correspondence table Tc indicating data position information and transmission timing information for each vehicle model. FIG. 6 representatively illustrates data position information and transmission timing information for vehicle model X3.

[0077] The data position information indicates the CAN-ID, which is the storage ID of each vehicle information, and the position of the vehicle information in the CAN frame. The transmission timing information indicates the transmission timing at which the vehicle information should be transmitted to the management device 201.

[0078] Specifically, the correspondence table Tc shows the correspondence between the type of vehicle information, the storage ID, the byte position and bit position that are the starting point and the ending point of the vehicle information in the payload of the CAN frame, the bit length, the transmission trigger, and the transmission period.

[0079] In the example shown in FIG. 6, in vehicle 1 of model X3, vehicle speed information is 8-bit data extending from bit 0 of the first byte to bit 7 of the first byte in the payload of the CAN frame with CAN-ID "1." Furthermore, when an event occurs, for example, when the in-vehicle communication unit 14 receives vehicle information, this is the timing for transmitting the vehicle speed information from the vehicle 1 to the management device 201. Furthermore, brake information is 1-bit data extending from bit 0 of the second byte to bit 0 of the second byte in the payload of the CAN frame with CAN-ID "1." Furthermore, the transmission timing of the brake information is cyclically timing every 100 milliseconds. Furthermore, image information is 48-bit data extending from bit 0 of the first byte to bit 7 of the sixth byte in the payload of the CAN frame with CAN-ID "2." Furthermore, the transmission timing of the image information is cyclically timing every 500 milliseconds.

[0080] In the management device 201, the setting information creation unit 23 creates setting information based on the correspondence tables Ta, Tb, and Tc. For example, assume that the selection information indicates "function B." In this case, the setting information creation unit 23 references the correspondence table Ta and confirms that the vehicle information corresponding to function B is vehicle speed information and image information.

[0081] Furthermore, the setting information creation unit 23 creates setting information for each vehicle model by referring to the correspondence table Tb. For example, the setting information creation unit 23 creates setting information indicating a CAN-ID "1" corresponding to the vehicle speed information and a CAN-ID "2" corresponding to the image information as setting information to be transmitted to the vehicle 1 of vehicle model X3.

[0082] In addition, the setting information creation unit 23 refers to the correspondence table Tc to create setting information to be transmitted to the vehicle 1 of the vehicle type X3, which further indicates the start and end points of the vehicle information corresponding to the vehicle speed information and image information, as well as the transmission trigger and transmission period.

[0083] Then, the setting information creation unit 23 outputs the created setting information corresponding to the vehicle model X3 and function B to the communication unit 21. The communication unit 21 transmits the setting information created by the setting information creation unit 23 via the network 151 to one or more vehicles 1 of the vehicle model X3.

[0084] In the in-vehicle ECU 101 , the external communication unit 11 receives the setting information transmitted from the management device 201 via the network 151 and outputs the received setting information to the setting unit 12 .

[0085] The setting unit 12 receives the setting information output from the external communication unit 11 and, based on the setting information, performs setting processing for the in-vehicle equipment 111 so that vehicle information corresponding to the specified data type is sent to the management device 201 at the specified timing.

[0086] More specifically, as a setting process, the setting unit 12 sets the in-vehicle communication unit 14, the out-vehicle communication unit 11, the vehicle speed sensor 111A, etc. so that vehicle speed information is extracted from the position indicated by the setting information in the payload of the CAN frame with CAN-ID "1" and transmitted to the management device 201 at the transmission timing indicated by the setting information. Also, as a setting process, the setting unit 12 sets the in-vehicle communication unit 14, the out-vehicle communication unit 11, the camera 111C, etc. so that image information is extracted from the position indicated by the setting information in the payload of the CAN frame with CAN-ID "3" and transmitted to the management device 201 at the transmission timing indicated by the setting information.

[0087] The in-vehicle communication unit 14 extracts vehicle information from the position set by the setting unit 12 in the CAN frame including the CAN-ID set by the setting unit 12. Then, when the transmission trigger for the vehicle information is the occurrence of an event, the in-vehicle communication unit 14 outputs the vehicle information to the exterior communication unit 11 in response to receiving the vehicle information from the in-vehicle device 111. On the other hand, when the transmission trigger for the vehicle information is a periodic timing, the in-vehicle communication unit 14 stores the vehicle information in the memory unit 13 every time it receives the vehicle information from the in-vehicle device 111, and at the periodic timing, obtains one or more pieces of stored vehicle information from the memory unit 13 and outputs the information to the exterior communication unit 11.

[0088] In this way, by storing the correspondence table Tc in the management device 201 and using this to create setting information, after the in-vehicle ECU 101 is installed in a certain vehicle 1, it becomes possible to extract and transmit vehicle information by receiving setting information from the management device 201. This makes it possible to, for example, relax restrictions on the vehicle model in which the in-vehicle ECU 101 is installed, thereby increasing the degree of freedom in where the in-vehicle ECU 101 is installed. Furthermore, because vehicle information can be acquired from each vehicle 1 in vehicle information units rather than CAN frame units, it is not necessary to install application software for each vehicle model for processing vehicle information in the management device 201, and it becomes possible, for example, to handle the vehicle information with one type of application software.

[0089] The correspondence table Tc may indicate either the data position information or the transmission timing information.

[0090] Furthermore, the management device 201 may not have the correspondence table Tc. In this case, for example, the in-vehicle ECU 101 refers to the data position information and the transmission timing information registered in advance in the storage unit 13, and extracts and transmits the vehicle information from the CAN frame.

[0091] Furthermore, the above-described "for each vehicle model" may be replaced with "for each vehicle model year" or "for each combination of vehicle model and model year." That is, the setting unit 12 creates setting information for at least one of the vehicle model and model year. The model year refers to the year in which the vehicle was manufactured.

[0092] Furthermore, the in-vehicle ECU 101 is not limited to a configuration that extracts vehicle information from a CAN frame, but may be a configuration that transmits a CAN frame including vehicle information to the management device 201.

[0093] [Vehicle information history information] In the management device 201 , the provision information creation unit 24 may be configured to create history information of the vehicle information received from the communication unit 21 and store it in the storage unit 22 .

[0094] 7 is a diagram illustrating an example of a history of vehicle information stored in a storage unit in a management device according to an embodiment of the present disclosure. Referring to FIG. 7, the storage unit 22 stores history information HD of each piece of vehicle information for each vehicle 1. FIG. 7 shows the history information HD of a certain vehicle C1.

[0095] In the example shown in Figure 7, at time t1, the vehicle speed information is "1", the image information is "A", and no braking information is obtained. At time t2, the vehicle speed information is "1", the image information is "B", and no braking information is obtained. At time t3, the vehicle speed information is "0", the image information is "C", and no braking information is obtained.

[0096] The amount of history information HD to be stored in the management device 201 increases in accordance with the number of vehicles 1, but as described above, by registering vehicle information extracted from CAN frames in the database rather than on a CAN frame-by-canonical basis, the amount of data stored in the memory unit 22 can be reduced.

[0097] It is assumed that the provided information creation unit 24 confirms that the user has selected function A by referring to the selection information stored in the storage unit 22. The provided information creation unit 24 creates provided information to be used when executing function A by referring to the history information HD in the storage unit 22. Then, the provided information creation unit 24 stores the created provided information in the storage unit 22.

[0098] [Operation flow] Next, the operation of each device in the communication system according to the embodiment of the present disclosure will be described with reference to the drawings.

[0099] Each device in the communication system 301 is equipped with a computer including a memory, and a processing unit such as a CPU in the computer reads from the memory and executes a program including some or all of the steps of the following sequence. The programs for these multiple devices can each be installed externally. The programs for these multiple devices are distributed in a state where they are stored on a recording medium.

[0100] 8 is a diagram showing an example of a sequence of a communication system when an in-vehicle device according to an embodiment of the present disclosure is started up without saving any setting information. The following describes the operation of each device in the in-vehicle ECU 101, the multiple in-vehicle devices 111, the management device 201, and the terminal device 161 in the vehicle 1 of vehicle model X1. The multiple in-vehicle devices 111 are assumed to be a vehicle speed sensor 111A, a brake control device 111B, and a camera 111C.

[0101] 8, it is assumed that the user first selects function C by operating terminal device 161. In this case, terminal device 161 transmits selection information indicating the result of the user's selection to management device 201 via network 151 (step S11).

[0102] Next, when the management device 201 receives the selection information transmitted from the terminal device 161 via the network 151, it creates setting information based on the received selection information. Specifically, it is assumed that the management device 201 confirms that the vehicle information corresponding to the function C indicated by the selection information is vehicle speed information. In this case, the management device 201 creates, for example, setting information corresponding to the vehicle model X1, setting information indicating the CAN-ID "1" corresponding to the vehicle speed information of the vehicle 1 of the vehicle model X1 (step S12).

[0103] Next, for example, when the ignition switch of the vehicle 1 is turned on, the on-board ECU 101, the vehicle speed sensor 111A, the brake control device 111B, and the camera 111C in the vehicle 1 are activated (step S13).

[0104] Next, the vehicle speed sensor 111A measures the speed of the vehicle 1, stores the vehicle speed information indicating the measurement result in a CAN frame including the CAN-ID "1", and transmits the information to the in-vehicle ECU 101 (step S14).

[0105] Next, the brake control device 111B stores brake information indicating the state of the brakes in the vehicle 1 in a CAN frame including the CAN-ID "2" and transmits the information to the in-vehicle ECU 101 (step S15).

[0106] Next, the camera 111C captures an image of the surroundings of the vehicle 1, stores image information indicating the captured image of the surroundings in a CAN frame including the CAN-ID "3", and transmits the image information to the in-vehicle ECU 101 (step S16).

[0107] Next, when the in-vehicle ECU 101 receives vehicle information from at least one of the vehicle speed sensor 111A, the brake control device 111B, and the camera 111C, the in-vehicle ECU 101 transmits a setting information request to the management device 201 via the network 151 to check whether setting information has been created. Here, after receiving the vehicle speed information from the vehicle speed sensor 111A (step S14), the in-vehicle ECU 101 transmits the setting information request to the management device 201 (step S17).

[0108] The setting information request includes, for example, identification information of the in-vehicle ECU 101 that is the sender, and the vehicle model X1 of the vehicle 1 equipped with the in-vehicle ECU 101. The in-vehicle ECU 101 may be configured to send the setting information request to the management device 201 before receiving vehicle speed information from the vehicle speed sensor 111A. That is, the in-vehicle ECU 101 may send the setting information request when started up and before receiving vehicle information. The in-vehicle ECU 101 may also be configured to send the setting information request periodically or irregularly until, for example, the ignition switch of the vehicle 1 is switched from the on state to the off state.

[0109] Next, when the management device 201 receives the setting information request transmitted from the in-vehicle ECU 101, the management device 201 confirms that the vehicle model of the vehicle 1 equipped with the in-vehicle ECU 101 that is the source of the received setting information request is "X1." The management device 201 also confirms whether or not setting information corresponding to the vehicle model X1 has been created. Here, since the management device 201 has created setting information corresponding to the vehicle model X1 in step S12, the management device 201 transmits the setting information via the network 151 to the in-vehicle ECU 101 that is the source of the setting information request (step S18).

[0110] Next, when the in-vehicle ECU 101 receives the setting information transmitted from the management device 201 via the network 151, it performs setting processing for the in-vehicle device 111 based on the received setting information. Specifically, as the setting processing, the in-vehicle ECU 101 performs setting so that vehicle speed information corresponding to CAN-ID "1" is transmitted to the management device 201 at a specified timing. After this setting processing, the vehicle speed information from the vehicle speed sensor 111A is transmitted to the management device 201. Furthermore, the in-vehicle ECU 101 stores the received setting information in the storage unit 13 (step S19).

[0111] Next, the vehicle speed sensor 111A measures the speed of the vehicle 1, stores the vehicle speed information indicating the measurement result in a CAN frame including the CAN-ID "1", and transmits the information to the in-vehicle ECU 101 (step S20).

[0112] Next, when the in-vehicle ECU 101 receives the vehicle speed information transmitted from the vehicle speed sensor 111A, it transmits the received vehicle speed information to the management device 201 via the network 151 in accordance with the contents of the setting process performed in step S19 (step S21).

[0113] Next, when the management device 201 receives the vehicle speed information transmitted from the in-vehicle ECU 101 via the network 151, it uses the received vehicle speed information to create provision information to be used for executing the function C. Then, the management device 201, for example, stores the created provision information. Note that the management device 201 may be configured to create the history information HD as described above, and use the history information HD to create provision information to be used for executing the selected function C (step S22).

[0114] Next, the brake control device 111B stores brake information indicating the state of the brakes in the vehicle 1 in a CAN frame including the CAN-ID "2" and transmits the information to the in-vehicle ECU 101 (step S23).

[0115] Next, when the in-vehicle ECU 101 receives the brake information transmitted from the brake control device 111B, it does not transmit the received brake information to the management device 201 in accordance with the contents of the setting process performed in step S19 (step S24).

[0116] Next, the camera 111C captures an image of the surroundings of the vehicle 1, stores image information indicating the captured image of the surroundings in a CAN frame including the CAN-ID "3", and transmits the image information to the in-vehicle ECU 101 (step S25).

[0117] Next, when the in-vehicle ECU 101 receives the image information transmitted from the camera 111C, it does not transmit the received image information to the management device 201 in accordance with the contents of the setting process performed in step S19 (step S26).

[0118] Next, the terminal device 161 is operated by the user to request, for example, the management device 201 for the provision information corresponding to function C (step S27).

[0119] Next, when the management device 201 receives a request for provision information from the terminal device 161, it transmits the stored provision information corresponding to function C to the terminal device 161 via the network 151 (step S28). This allows the user to execute function C using the provision information created by the management device 201. Then, for example, operations similar to steps S20 to S28 described above are repeated until the ignition switch of the vehicle 1 is switched to the off state. Then, for example, when the ignition switch of the vehicle 1 is switched to the off state, the on-board ECU 101, the vehicle speed sensor 111A, the brake control device 111B, and the camera 111C are stopped.

[0120] The in-vehicle ECU 101, the vehicle speed sensor 111A, the brake control device 111B, and the camera 111C may be configured to be activated by a trigger other than the ignition switch being switched on, or to be deactivated by a trigger other than the ignition switch being switched off.

[0121] Furthermore, when the management device 201 receives a setting information request from the in-vehicle ECU 101 (step S17) and has not yet created the corresponding setting information, the management device 201 does not transmit the setting information to the in-vehicle ECU 101.

[0122] Here, with regard to communication within the vehicle 1, for example, initial settings of the in-vehicle ECU 101 using a diagnostic tool or the like are performed in the vehicle 1 at a dealer or the like. In this case, even if the in-vehicle ECU 101 has never received setting information from the management device 201, communication between the in-vehicle device 111 and the in-vehicle ECU 101 can be performed normally.

[0123] When the in-vehicle ECU 101 is initially set at a dealer or the like, setting information corresponding to a function to be executed by a user may be stored in the in-vehicle ECU 101 .

[0124] 9 is a diagram showing an example of a sequence of a communication system when an in-vehicle device according to an embodiment of the present disclosure is started up with setting information saved. Here, it is assumed that the setting process in step S19 shown in FIG. 8 has already been performed, in which vehicle speed information corresponding to CAN-ID "1" is transmitted to management device 201.

[0125] 9, first, it is assumed that the user changes the selection from function C to function D by operating terminal device 161. In this case, terminal device 161 transmits selection information indicating the result of the user's selection to management device 201 via network 151 (step S30).

[0126] Next, when the management device 201 receives the selection information transmitted from the terminal device 161 via the network 151, it creates setting information based on the received selection information. Specifically, it is assumed that the management device 201 confirms that the vehicle information corresponding to the function D indicated by the selection information is braking information. In this case, the management device 201 creates, for example, setting information corresponding to the vehicle model X1, setting information indicating the CAN-ID "2" corresponding to the braking information of the vehicle 1 of the vehicle model X1 (step S31).

[0127] Next, for example, when the ignition switch of the vehicle 1 is turned on, the in-vehicle ECU 101, the vehicle speed sensor 111A, the brake control device 111B, and the camera 111C are activated (step S32).

[0128] Next, the setting unit 12 in the in-vehicle ECU 101 performs setting processing for the in-vehicle device 111 based on the setting information stored in the storage unit 13. Specifically, as the setting processing, the in-vehicle ECU 101 performs setting so that the vehicle speed information corresponding to CAN-ID "1" is transmitted to the management device 201 at a specified timing (step S33).

[0129] Next, the vehicle speed sensor 111A measures the speed of the vehicle 1, stores the vehicle speed information indicating the measurement result in a CAN frame including the CAN-ID "1", and transmits the information to the in-vehicle ECU 101 (step S34).

[0130] Next, similarly to step S17 shown in FIG. 8, after receiving vehicle speed information from the vehicle speed sensor 111A (step S34), the in-vehicle ECU 101 transmits a setting information request to the management device 201 (step S35).

[0131] Next, the in-vehicle ECU 101 transmits the received vehicle speed information to the management device 201 via the network 151 in accordance with the contents of the setting process performed in step S33 (step S36). Note that the transmission of the vehicle speed information by the in-vehicle ECU 101 (step S36) may be performed before the transmission of the setting information request by the in-vehicle ECU 101 (step S35).

[0132] Next, the brake control device 111B stores brake information indicating the state of the brakes in the vehicle 1 in a CAN frame including the CAN-ID "2" and transmits the information to the in-vehicle ECU 101 (step S37).

[0133] Next, when the in-vehicle ECU 101 receives the brake information transmitted from the brake control device 111B, it does not transmit the received brake information to the management device 201 in accordance with the contents of the setting process performed in step S33 (step S38).

[0134] Next, the camera 111C captures an image of the surroundings of the vehicle 1, stores image information indicating the captured image of the surroundings in a CAN frame including the CAN-ID "3", and transmits the image information to the in-vehicle ECU 101 (step S39).

[0135] Next, when the in-vehicle ECU 101 receives the image information transmitted from the camera 111C, it does not transmit the received image information to the management device 201 in accordance with the contents of the setting process performed in step S33 (step S40).

[0136] Next, when the management device 201 receives the setting information request transmitted from the in-vehicle ECU 101, the management device 201 confirms that the vehicle model of the vehicle 1 equipped with the in-vehicle ECU 101 that is the source of the received setting information request is "X1." The management device 201 also confirms whether or not new setting information corresponding to the vehicle model X1 has been created. Here, since the management device 201 has created new setting information corresponding to the vehicle model X1 in step S31, the management device 201 transmits the new setting information via the network 151 to the in-vehicle ECU 101 that is the source of the setting information request (step S41).

[0137] If the management device 201 has not created new setting information corresponding to the vehicle model X1, the management device 201 does not transmit the setting information. In this case, the contents of the setting process that has already been performed are maintained in the vehicle 1. If the management device 201 has not created new setting information corresponding to the vehicle model X1, the management device 201 may transmit the setting information that has already been transmitted to the in-vehicle ECU 101 again.

[0138] Next, when the in-vehicle ECU 101 receives the setting information transmitted from the management device 201 via the network 151, it performs setting processing for the in-vehicle device 111 based on the received setting information. Specifically, the in-vehicle ECU 101 performs setting so that transmission of vehicle speed information corresponding to CAN-ID "1" is stopped and transmission of brake information corresponding to CAN-ID "2" to the management device 201 is performed at a specified timing. After this setting processing, brake information from the brake control device 111B is transmitted to the management device 201. Furthermore, the in-vehicle ECU 101 stores the received setting information in the storage unit 13 (step S42).

[0139] Next, the vehicle speed sensor 111A measures the speed of the vehicle 1, stores the vehicle speed information indicating the measurement result in a CAN frame including the CAN-ID "1", and transmits the information to the in-vehicle ECU 101 (step S43).

[0140] Next, when the in-vehicle ECU 101 receives the vehicle speed information transmitted from the vehicle speed sensor 111A, it does not transmit the received vehicle speed information to the management device 201 in accordance with the contents of the current setting process performed in step S42 (step S44).

[0141] Next, the brake control device 111B stores brake information indicating the state of the brakes in the vehicle 1 in a CAN frame including the CAN-ID "2" and transmits the information to the in-vehicle ECU 101 (step S45).

[0142] Next, when the in-vehicle ECU 101 receives the brake information transmitted from the brake control device 111B, it transmits the received brake information to the management device 201 via the network 151 in accordance with the contents of the current setting process performed in step S42 (step S46).

[0143] Next, when the management device 201 receives the braking information transmitted from the in-vehicle ECU 101 via the network 151, it uses the received braking information to create provision information to be used for executing function D. Then, the management device 201, for example, stores the created provision information. Note that the management device 201 may be configured to create history information HD as described above, and use the history information HD to create provision information to be used for executing the selected function D (step S47).

[0144] Next, the camera 111C captures an image of the surroundings of the vehicle 1, stores image information indicating the captured image of the surroundings in a CAN frame including the CAN-ID "3", and transmits the image information to the in-vehicle ECU 101 (step S48).

[0145] Next, when the in-vehicle ECU 101 receives the image information transmitted from the camera 111C, it does not transmit the received image information to the management device 201 in accordance with the current setting process performed in step S42 (step S49).

[0146] Next, the terminal device 161 is operated by the user to request, for example, the management device 201 for the provision information corresponding to function D (step S50).

[0147] Next, when the management device 201 receives a request for provided information from the terminal device 161, the management device 201 transmits the stored provided information corresponding to function D to the terminal device 161 via the network 151 (step S51). This allows the user to execute function D using the provided information created by the management device 201.

[0148] Then, for example, operations similar to steps S43 to S51 described above are repeated until the ignition switch of the vehicle 1 is switched to the OFF state. Furthermore, if the user further changes the function, operations similar to steps S30, S31 and steps S34 to S51 described above are performed. Then, for example, when the ignition switch of the vehicle 1 is switched to the OFF state, the on-board ECU 101, the vehicle speed sensor 111A, the brake control device 111B, and the camera 111C are stopped.

[0149] In addition to function changes, if new on-board equipment 111 is added to vehicle 1 after the vehicle 1 has been shipped, the vehicle 1 can be adapted to the function to be executed by performing the above-mentioned setting process on the on-board ECU 101 etc. installed in the vehicle 1.

[0150] It is conceivable that various vehicle-related functions can be executed using vehicle information acquired by an on-board ECU. Conventionally, settings for each on-board ECU for transmitting vehicle information to an external device have been individually configured according to the vehicle model before shipping the vehicle. Therefore, if a change in the functions to be provided occurs after shipping the vehicle, it has been necessary for a dealer or the like to individually change the settings for each vehicle.

[0151] As described above, the vehicle control device described in Patent Document 1 uses a vehicle information cartridge to set functions and control characteristics for each on-board ECU according to the vehicle specifications. However, when the settings of the on-board ECU are changed or an on-board ECU is added, the vehicle information cartridge must be changed or added, which creates a problem of being unable to respond flexibly.

[0152] In contrast to this, in the in-vehicle device according to the embodiment of the present disclosure, the communication unit 31 receives setting information for the in-vehicle device 111 of the vehicle 1, which corresponds to the selected function, from the management device 201. Then, the setting unit 12 performs setting processing for the in-vehicle device 111 based on the setting information received by the communication unit 31.

[0153] With this configuration, after the vehicle 1 is shipped, the in-vehicle ECU 101 and the like can be easily configured to correspond to any function related to the vehicle 1. Furthermore, the in-vehicle ECU 101 added to the vehicle 1 after the vehicle 1 is shipped can also be easily configured to correspond to any function, just like the in-vehicle ECU 101 mounted in the vehicle 1 before the shipment.

[0154] Therefore, the in-vehicle device according to the embodiment of the present disclosure can easily accommodate additions or changes to vehicle-related functions.

[0155] Note that some or all of the functions of the management device 201 according to the embodiment of the present disclosure may be provided by cloud computing. That is, the management device 201 according to the embodiment of the present disclosure may be a cloud server configured by multiple servers.

[0156] The above-described embodiments should be considered to be illustrative in all respects and not restrictive. The scope of the present invention is defined by the claims, not by the above description, and is intended to include all modifications within the meaning and scope of the claims. [Explanation of symbols]

[0157] 1 vehicle 10 CAN bus 11 External communication unit 12 Setting section 13 Storage section 14 In-vehicle communication unit 21 Communications Department 22 Memory section 23 Setting information creation section 24 Information Creation Department 31 Communications Department 101 In-vehicle ECU (in-vehicle device) 111 Automotive equipment 111A Vehicle speed sensor 111B Brake control device 111C Camera 151 Network 161 Terminal Equipment 201 Management device 301 Communication Systems Ta, Tb, Tc correspondence table HD History Information

Claims

1. An in-vehicle device mounted on a vehicle, a communication unit that receives setting information related to an in-vehicle device of the vehicle corresponding to the selected function from a management device; a setting unit that performs setting processing for the in-vehicle device based on the setting information received by the communication unit, the communication unit transmits confirmation information to the management device for confirming whether the setting information has been created in the management device; the communication unit repeatedly transmits the confirmation information to the management device; the communication unit receives the setting information for performing operation settings in each vehicle that differ depending on the vehicle model, The confirmation information includes a model of the vehicle in which the in-vehicle device is installed.

2. The in-vehicle device according to claim 1 , wherein the communication unit receives the setting information for each combination of vehicle model and year.

3. The in-vehicle device according to claim 1 , wherein the setting unit uses the setting information for setting to transmit vehicle information about the vehicle from the vehicle to the management device.

4. The in-vehicle device according to claim 3 , wherein the vehicle information includes information relating to the running of the vehicle.

5. The in-vehicle device according to claim 3 or 4, wherein the vehicle information includes information indicating a measurement result of the vehicle.

6. 6. The in-vehicle device according to claim 3, wherein the communication unit acquires the vehicle information from the frame based on data location information included in the setting information and used to identify the vehicle information within the frame transmitted and received by the vehicle, in accordance with the setting process, and transmits the vehicle information to the management device.

7. 7. The in-vehicle device according to claim 3, wherein the communication unit transmits the vehicle information to the management device at a transmission timing of the vehicle information to the management device indicated by transmission timing information included in the setting information in accordance with the setting process.

8. An information processing method in an in-vehicle device mounted on a vehicle, comprising: receiving setting information related to an in-vehicle device of the vehicle corresponding to the selected function from a management device; performing a setting process for the in-vehicle device based on the received setting information; transmitting confirmation information to the management device to confirm whether the setting information has been created in the management device; In the step of transmitting the confirmation information to the management device, the confirmation information is repeatedly transmitted to the management device; In the step of receiving the setting information, the setting information is received so that operation settings that differ depending on the vehicle model are performed in each vehicle, The information processing method, wherein the confirmation information includes a model of the vehicle in which the in-vehicle device is installed.

9. An information processing program used in an in-vehicle device mounted on a vehicle, Computer, a communication unit that receives setting information related to an in-vehicle device of the vehicle corresponding to the selected function from a management device; a setting unit that performs setting processing for the in-vehicle device based on the setting information received by the communication unit; It is a program to function as the communication unit transmits confirmation information to the management device for confirming whether the setting information has been created in the management device; the communication unit repeatedly transmits the confirmation information to the management device; the communication unit receives the setting information for performing operation settings in each vehicle that differ depending on the vehicle model, The information processing program, wherein the confirmation information includes a model of the vehicle in which the in-vehicle device is installed.

Images