Information processing device, information processing method, and program

Abstract

To transmit information on the state of a vehicle in an appropriate format.SOLUTION: An information processing apparatus is an information processing apparatus to be mounted on a specific vehicle. A control unit of the information processing apparatus acquires, from the specific vehicle, first information related to a power source of the specific vehicle. The control unit of the information processing apparatus specifies, based on the first information, a type of the specific vehicle, from among multiple types classified based on power sources of vehicles. The control unit of the information processing apparatus transmits, to a predetermined server device, second information related to the state of the specific vehicle, in a first format of multiple data transmission formats designated for each of the types, the first format being a data transmission format corresponding to the type of the specific vehicle.SELECTED DRAWING: Figure 8

Description

[Technical field]

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

[0002] Patent Document 1 discloses an in-vehicle communication device mounted on a vehicle. The in-vehicle communication device disclosed in Patent Document 1 buffers a plurality of types of vehicle data flowing through an in-vehicle communication network. The in-vehicle communication device creates a table that specifies the types of vehicle data to be selected and a compression method for the vehicle data of the selected type based on information received from a server. The in-vehicle communication device also selects the vehicle data of the selected type from the buffered plurality of types of vehicle data based on the created table, and compresses the selected vehicle data. The in-vehicle communication device then transmits the compressed vehicle data to the server. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2018-005848 A Summary of the Invention [Problem to be solved by the invention]

[0004] The present disclosure is directed to transmitting information regarding the vehicle's condition in an appropriate format. [Means for solving the problem]

[0005] An information processing device according to a first aspect of the present disclosure includes: An information processing device mounted on a specific vehicle, Obtaining first information from the specific vehicle related to a power source of the specific vehicle; Identifying a type of the specific vehicle from a plurality of types classified according to a power source of the vehicle based on the first information; Transmitting second information on the status of the specific vehicle to a predetermined server device in a first format, which is a data transmission format corresponding to the type of the specific vehicle, among a plurality of data transmission formats designated for each of the plurality of types; The control unit executes the above.

[0006] An information processing method according to a second aspect of the present disclosure includes: An information processing method executed by a computer installed in a specific vehicle, comprising: Obtaining first information from the specific vehicle related to a power source of the specific vehicle; Identifying a type of the specific vehicle from a plurality of types classified according to a power source of the vehicle based on the first information; Transmitting second information on the status of the specific vehicle to a predetermined server device in a first format, which is a data transmission format corresponding to the type of the specific vehicle, among a plurality of data transmission formats designated for each of the plurality of types; Includes.

[0007] The program according to the third aspect of the present disclosure comprises: A program for causing a computer mounted on a specific vehicle to execute an information processing method, The information processing method includes: Obtaining first information from the specific vehicle related to a power source of the specific vehicle; Identifying a type of the specific vehicle from a plurality of types classified according to a power source of the vehicle based on the first information; Transmitting second information on the status of the specific vehicle to a predetermined server device in a first format, which is a data transmission format corresponding to the type of the specific vehicle, among a plurality of data transmission formats designated for each of the plurality of types; Includes. Effect of the Invention

[0008] The present disclosure allows for the transmission of information regarding the vehicle's condition in an appropriate format. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram showing a schematic configuration of a management system. [Diagram 2] FIG. 2 is a diagram showing an example of a table configuration of generation information and state information when the specific type of vehicle is a plug-in hybrid vehicle. [Diagram 3] FIG. 3 is a diagram showing an example of a table configuration of generation information and state information when the specific type of vehicle is a fuel cell vehicle. [Figure 4] FIG. 4 is a diagram showing an example of a table configuration of generation information and state information when the specific type of vehicle is an electric vehicle. [Diagram 5] FIG. 5 is a block diagram illustrating an example of a functional configuration of the in-vehicle device. [Figure 6] FIG. 6 is a diagram showing an example of a table configuration of the generating method information stored in the generating method information database. [Figure 7] FIG. 7 is a diagram showing an example of a table configuration of type information held in the type information database. [Figure 8] FIG. 8 is a flowchart of the transmission process. [Figure 9] FIG. 9 is a flowchart of the identification process. [Figure 10] FIG. 10 is a flowchart of the update process. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] An information processing device according to a first aspect of the present disclosure is an information processing device mounted on a specific vehicle. A control unit of the information processing device according to the first aspect of the present disclosure acquires first information from the specific vehicle. Here, the first information is information related to the power source of the vehicle. Therefore, the control unit can grasp the power source of the specific vehicle based on the first information. Then, the control unit identifies the type of the specific vehicle from multiple types classified by the vehicle's power source based on the first information.

[0011] The control unit transmits the second information regarding the status of the specific vehicle to the predetermined server device in a first format, where the first format is a data transmission format corresponding to the type of the specific vehicle among a plurality of data transmission formats designated for each of the plurality of types.

[0012] As described above, the information processing device identifies the type of the specific vehicle based on the first information. Then, the information processing device transmits the second information in the first format to a predetermined server device. In this way, the information processing device can transmit information about the vehicle status in an appropriate format.

[0013] Hereinafter, specific embodiments of the present disclosure will be described with reference to the drawings. The dimensions, materials, shapes, and relative positions of the components described in the present embodiments are not intended to limit the technical scope of the present disclosure unless otherwise specified.

[0014] First Embodiment (System Overview) A management system 1 in this embodiment will be described with reference to Figs. 1 to 4. Fig. 1 is a diagram showing a schematic configuration of the management system 1. The management system 1 includes an in-vehicle device 100 and a management server 200. In the management system 1, the in-vehicle device 100 and the management server 200 are connected to each other via a network N1. The network N1 may include, for example, a WAN (Wide Area Network), which is a global public communication network such as the Internet. Network) or a telephone communication network such as a mobile phone may be employed.

[0015] (Management Server) The management server 200 is a server that manages the status of the vehicle 10. The management server 200 receives information relating to the status of the vehicle 10 (hereinafter, may be referred to as "status information") from the in-vehicle device 100 mounted on the vehicle 10. Here, the management server 200 receives the status information from the in-vehicle device 100 in a predetermined data transmission format (hereinafter, may be simply referred to as "predetermined format"). Details of the predetermined format will be described later.

[0016] (In-vehicle device) The on-board device 100 communicates with the management server 200 via the network N1. The on-board device 100 also generates generated information based on the CAN data acquired from the vehicle 10. The on-board device 100 generates status information based on the generated information and transmits it to the management server 200. Details of the generated information and the status information will be described later.

[0017] At this time, the vehicle 10 on which the in-vehicle device 100 is mounted belongs to any one of a plurality of types classified according to the power source of the vehicle. The plurality of types classified according to the power source of the vehicle are a plug-in hybrid vehicle, a fuel cell vehicle, and an electric vehicle.

[0018] It is assumed that the type to which the vehicle 10 belongs (hereinafter, may be referred to as a "specific type") is a plug-in hybrid vehicle. In this case, the vehicle 10 is a vehicle having an internal combustion engine and a motor.

[0019] FIG. 2 is a diagram showing an example of a table configuration of the generation information and status information when the specific type of vehicle 10 is a plug-in hybrid vehicle. As shown in FIG. 2, the generation information has a number field, a generation data field, and a remarks field. In the number field, row numbers in the generation information table are input in order starting from 1. In the generated data field, data (generated data) relating to the status of vehicle 10 is input. On-board device 100 generates the generated data based on the CAN data of vehicle 10. In the remarks field, an explanation of the content of the generated data input in the generated data field is input.

[0020] In the example shown in FIG. 2, internal combustion engine-related generated data is input as generated data corresponding to row number "2". The internal combustion engine-related generated data is, for example, data related to the output of the internal combustion engine. Furthermore, motor-related generated data is input as generated data corresponding to row number "3". The motor-related generated data is, for example, data related to the output of the motor. Furthermore, fuel cell-related generated data is input as generated data corresponding to row number "4". The fuel cell-related data is, for example, generated data related to the amount of power generated by the fuel cell.

[0021] When the vehicle 10 is a plug-in hybrid vehicle, the vehicle 10 has an internal combustion engine and a motor. Therefore, it is assumed that the CAN data of the vehicle 10 includes information related to the internal combustion engine and information related to the motor. Therefore, the in-vehicle device 100 is The in-vehicle device 100 generates internal combustion engine-related generated data based on the information related to the internal combustion engine included in the AN data, and generates motor-related generated data based on the information related to the motor included in the CAN.

[0022] On the other hand, if the vehicle 10 is a plug-in hybrid vehicle, the vehicle 10 does not have a fuel cell. Therefore, the CAN data of the vehicle 10 does not include CAN data related to the fuel cell. Therefore, the in-vehicle device 100 cannot acquire CAN data for generating the fuel cell-related generated data, and the fuel cell-related generated data is null. In the example of the generated information shown in FIG. 2, "---", indicating a null value, is input to the fuel cell-related generated data (the generated data input in the generated data field in row number "4"). Details of the state information in FIG. 2 will be described later.

[0023] Next, assume that the specific type of vehicle 10 is a fuel cell vehicle. In this case, vehicle 10 is a vehicle having a motor and a fuel cell. Therefore, the CAN data acquired by the in-vehicle device 100 includes information related to the motor and information related to the fuel cell. Therefore, the in-vehicle device 100 generates motor-related generated data based on the information related to the motor included in the CAN data. Also, the in-vehicle device 100 generates fuel cell-related generated data based on the information related to the fuel cell included in the CAN.

[0024] On the other hand, the vehicle 10 does not have an internal combustion engine. Therefore, the CAN data acquired by the in-vehicle device 100 does not include CAN data related to the internal combustion engine. Therefore, the in-vehicle device 100 cannot acquire CAN data for generating the internal combustion engine-related generated data, and the internal combustion engine-related generated data is null.

[0025] Fig. 3 is a diagram showing an example of a table configuration of the generation information and status information when the specific type of vehicle 10 is a fuel cell vehicle. The contents of the information entered in the number field, the generated data field, and the remarks field shown in Fig. 3 are similar to those of the generation information shown in Fig. 2, and therefore will not be described. In the example shown in Fig. 3, "---", indicating a null value, is entered in the internal combustion engine-related generated data (the generated data entered in the generated data field in row number "2"). Details of the status information in Fig. 3 will also be described later.

[0026] Next, assume that the specific type of the vehicle 10 is an electric vehicle. In this case, the vehicle 10 is a vehicle powered by a motor. Therefore, the CAN data acquired by the in-vehicle device 100 includes information related to the motor. Therefore, the in-vehicle device 100 generates motor-related generated data based on the information related to the motor included in the CAN data. In addition, the in-vehicle device 100 generates fuel cell-related generated data based on information related to the fuel cell included in the CAN data.

[0027] On the other hand, unlike a plug-in hybrid vehicle, the vehicle 10 does not have an internal combustion engine. Also, unlike a fuel cell vehicle, the vehicle 10 does not have a fuel cell. Therefore, the CAN data acquired by the in-vehicle device 100 does not include CAN data related to the internal combustion engine and CAN data related to the fuel cell. Therefore, since the in-vehicle device 100 cannot acquire CAN data for generating the internal combustion engine-related generated data and the fuel cell-related generated data, the internal combustion engine-related generated data and the fuel cell-related generated data are null values.

[0028] 4 is a diagram showing an example of a table configuration of the generation information and status information when the specific type of vehicle 10 is an electric vehicle. The contents of the information entered in the number field, the generated data field, and the remarks field shown in FIG. 4 are similar to those of the generation information shown in FIG. 2, and therefore a description thereof will be omitted. In the example shown in FIG. 4, the generated data related to the internal combustion engine (the generated data entered in the generated data field in row number "2") contains "--" indicating a null value. 4, "---", which indicates a null value, is entered in the generated data related to the fuel cell (the generated data entered in the generated data field in row number "4").

[0029] Here, the predetermined format is a format in which there are no rows in the generation information in which the generation data is null. On the other hand, as shown in Figs. 2 to 4, if the specific type is different, the rows in which the null values ​​are input will be different. Therefore, the in-vehicle device 100 identifies the specific type of the vehicle 10 based on the CAN data acquired from the vehicle 10. Then, the in-vehicle device 100 generates status information that matches the predetermined format by deleting rows in the generation information that contain null values ​​based on the specific type of the vehicle 10.

[0030] Returning to Fig. 2, the status information when the vehicle 10 is a plug-in hybrid vehicle will be described. As shown in Fig. 2, the status information has a number field, a generated data field, and a remarks field. The content of the information entered in the number field, generated data field, and remarks field is the same as the information entered in the corresponding fields in the generated information, so a description thereof will be omitted.

[0031] 2, in the generation information, the generation data (fuel cell related generation data) input in the generation data field in line number "4" is null. Therefore, the in-vehicle device 100 generates status information by deleting the line corresponding to line number "4" in the generation information, thereby formatting the generation information to conform to a predetermined format. In this manner, the in-vehicle device 100 generates the status information.

[0032] Returning to Fig. 3, the status information when the vehicle 10 is a fuel cell vehicle will be described. The contents of the information entered in the number field, generated data field, and remarks field in the status information shown in Fig. 3 are the same as those in the status information shown in Fig. 2.

[0033] 3, in the generation information, the generation data (generation data related to the internal combustion engine) input in the generation data field in line number "2" is null. Therefore, the in-vehicle device 100 generates status information in which the line corresponding to line number "2" in the generation information is deleted, thereby formatting the generation information to conform to a predetermined format. In this manner, the in-vehicle device 100 generates the status information.

[0034] Returning to Fig. 4, the status information when the vehicle 10 is an electric vehicle will be described. The contents of the information entered in the number field, the generated data field, and the remarks field in the status information shown in Fig. 4 are the same as those in the generated information shown in Fig. 2.

[0035] As shown in FIG. 4, in the generation information, the generation data input in the generation data field in line number "2" (generation data related to the internal combustion engine) is null. Also, in the generation information, the generation data input in the generation data field in line number "4" (generation data related to the fuel cell) is null. Therefore, the in-vehicle device 100 formats the generation information to conform to a predetermined format by generating status information in which the lines corresponding to line numbers "2" and "4" in the generation information are deleted. In this manner, the in-vehicle device 100 generates the status information.

[0036] In this way, the in-vehicle device 100 generates status information that matches a predetermined format corresponding to the specific type. Then, the in-vehicle device 100 transmits the status information to the management server 200 in the predetermined format corresponding to the specific type of the vehicle 10. Details of the generated information and the method of generating the status information will be described later.

[0037] The in-vehicle device 100 includes a computer having a processor 110, a main memory unit 120, an auxiliary memory unit 130, and a communication interface (communication I / F) 140. The processor 110 is, for example, a CPU (Central Processing Unit) or a DSP (Digital Signal Processor). The main memory unit 120 is, for example, a RAM (Random Access Memory). The auxiliary memory unit 130 is, for example, a ROM (Read Only Memory). The auxiliary memory unit 130 is, for example, a HDD (Hard Disk Drive) or a disk recording medium such as a CD-ROM, a DVD disk, or a Blu-ray disk. The auxiliary memory unit 130 may be a removable medium (portable storage medium). Here, examples of the removable medium include a USB memory or an SD card. The communication I / F 140 is, for example, a LAN (Local Area Network) interface board, or a wireless communication circuit for wireless communication.

[0038] In the vehicle-mounted device 100, the auxiliary storage unit 130 stores an operating system (OS), various programs, various information tables, and the like. In the vehicle-mounted device 100, the processor 110 loads the programs stored in the auxiliary storage unit 130 into the main storage unit 120 and executes them to realize various functions as described below. However, some or all of the functions in the vehicle-mounted device 100 may be realized by a hardware circuit such as an ASIC or an FPGA. The vehicle-mounted device 100 does not necessarily have to be realized by a single physical configuration, and may be configured by a plurality of computers that cooperate with each other. The management server 200 is also configured to include a computer, similar to the vehicle-mounted device 100.

[0039] (Functional configuration) Next, the functional configuration of the in-vehicle device 100 constituting the management system 1 will be described with reference to Fig. 5 to Fig. 7. Fig. 5 is a block diagram showing an example of the functional configuration of the in-vehicle device 100.

[0040] The in-vehicle device 100 includes a control unit 101, a communication unit 102, an acquisition unit 103, a generation method information database 104 (generation method information DB104), and a type information database 105 (type information DB105). The control unit 101 can be realized by a processor 110 in the in-vehicle device 100. The communication unit 102 has a function of connecting the in-vehicle device 100 to the network N1. The communication unit 102 can be realized by a communication I / F 140 in the in-vehicle device 100.

[0041] The acquisition unit 103 has a function of acquiring CAN data of the vehicle 10. The acquisition unit 103 can be realized by an interface that connects the in-vehicle device 100 and the vehicle 10. The control unit 101 acquires the CAN data of the vehicle 10 via the acquisition unit 103.

[0042] The generation method information DB 104 has a function of holding the generation method information. The generation method information is information used by the in-vehicle device 100 to generate the generation information. Fig. 6 is a diagram showing an example of a table configuration of the generation method information held in the generation method information DB 104. As shown in Fig. 6, the generation method information has a number field, an input data field, a generation method field, and a remarks field.

[0043] The number field is input with the row number corresponding to the generation data field into which the generated generation data is input when the generation information is generated. The input data field is input with information specifying the CAN data (input data) used when generating the generation data. The input data field is input with information specifying at least one input data. The generation method field is used to input a method (generation method) for converting the input data specified in the input data field and generating generated data. Specifically, the generation method field is used to input a formula for converting the input data. The remarks field is used to input an explanation of the contents of the generated data.

[0044] Here, the number field is filled with a line number corresponding to the generation data field into which the generation data generated when the generation information is generated is input. Therefore, the correspondence between the line number input in the number field and the content of the generation data input in the remarks field in the generation method information and the generation information is consistent.

[0045] Control unit 101 converts the input data and generates generated data using the generation method entered in the generation method field based on the generation method information held in generation method information DB 104. In this way, control unit 101 generates generation information based on the generation method information held in generation method information DB 104.

[0046] The type information DB 105 has a function of storing type information. The type information is information related to a specific type of the vehicle 10. The control unit 101 identifies the specific type of the in-vehicle device 100 based on the type information stored in the type information DB 105. In addition, the control unit 101 formats the generation information based on the type information stored in the type information DB 105.

[0047] Fig. 7 is a diagram showing an example of a table configuration of type information held in type information DB 105. As shown in Fig. 7, type information has a type field, a related data field, and a deletion number field.

[0048] The type field is input with information indicating a candidate for a specific type of the vehicle 10. In this embodiment, the types field is input with "plug-in hybrid vehicle", "fuel cell vehicle", and "electric vehicle".

[0049] In the related data field, CAN data (hereinafter sometimes referred to as "related data") related to the power source of the vehicle 10 is entered if the vehicle 10 is of the specific type entered in the type field. Specifically, if "plug-in hybrid vehicle" is entered in the type field, information indicating that the CAN data related to the internal combustion engine and motor of the vehicle 10 is related data is entered in the related data field. In addition, if "fuel cell vehicle" is entered in the type field, information indicating that the CAN data related to the fuel cell of the vehicle 10 is related data is entered in the CAN data field. In addition, if "electric vehicle" is entered in the type field, information indicating that the CAN data related to the motor of the vehicle 10 is related data is entered in the CAN data field.

[0050] The control unit 101 identifies the specific type of the vehicle 10 based on the type information held in the type information DB 105. Specifically, the control unit 101 acquires CAN data (hereinafter, sometimes referred to as "acquired data") related to the power source of the vehicle 10 by the acquisition unit 103. The control unit 101 identifies an associated data field in which the associated data matches the acquired data. Then, the control unit 101 identifies the type of the vehicle 10 in which the associated data is entered in a type field corresponding to the associated data field in which the associated data matches the acquired data as the specific type of the vehicle 10. Note that in this embodiment, the control unit 101 identifies the specific type of the vehicle 10 as an "electric vehicle" when the acquired data does not include data other than the CAN data related to the motor of the vehicle 10.

[0051] In the deletion number field, a line number to be deleted from the generation information when the generation information is formatted into a predetermined format is entered if the vehicle 10 is of the type entered in the type field. If "plug-in hybrid vehicle" is entered in the type field, "4" is entered in the deletion number field. Therefore, if the specific type of the vehicle 10 is a "plug-in hybrid vehicle", the control unit 101 deletes the line corresponding to line number "4" in the generation information when formatting the generation information, as shown in FIG. 2. If "fuel cell vehicle" is entered in the type field, "3" is entered in the deletion number field. Therefore, if the specific type of the vehicle 10 is a "fuel cell vehicle", the control unit 101 deletes the line corresponding to line number "3" in the generation information when formatting the generation information, as shown in FIG. 3. If "electric vehicle" is entered in the type field, "2, 3" is entered in the deletion number field. Therefore, if the specific type of the vehicle 10 is an "electric vehicle", the control unit 101 deletes the lines corresponding to line numbers "2" and "3" in the generation information when formatting the generation information, as shown in FIG. 4.

[0052] The control unit 101 can format the generated information into a predetermined format based on the type information held in the type information DB 105. In this manner, the control unit 101 generates status information in a predetermined format designated for a particular type of the vehicle 10. The control unit 101 transmits the status information to the management server 200 via the communication unit 102.

[0053] (Transmission process) The transmission process executed by the control unit 101 in the in-vehicle device 100 in the management system 1 will be described with reference to Fig. 8. Fig. 8 is a flowchart of the transmission process. The transmission process is a process for transmitting state information to the management server 200. The transmission process is repeatedly executed at predetermined intervals.

[0054] In the transmission process, first, in S101, CAN data (acquired data) related to the power source of the vehicle 10 is acquired from the vehicle 10. Next, in S102, type information is acquired from the type information DB 105. Next, in S103, an identification process is executed based on the acquired data acquired in S101 and the type information acquired in S102. Here, the identification process is a process for identifying a specific type of the vehicle 10. The details of the identification process will be described later.

[0055] Next, in S104, generation method information is obtained from the generation method information DB 104. Next, in S105, generation information is generated based on the generation method information. As a result, any of the generation information shown in FIG. 2 to FIG. 4 is generated. Next, in S106, the generation information is formatted based on the type information. That is, rows in the generation information are deleted so that the generation data in the generation information does not include null values, and status information is generated. Next, in S107, the status information is transmitted to the management server 200. Then, the transmission process is temporarily terminated.

[0056] (Specific processing) Next, the identification process executed by the control unit 101 in the in-vehicle device 100 in the management system 1 will be described with reference to Fig. 9. Fig. 9 is a flowchart of the identification process. The identification process is a process for identifying a specific type of the vehicle 10.

[0057] In the identification process, first, in S201, it is determined whether or not the acquired data acquired in S101 in the transmission process includes CAN data related to the internal combustion engine. If a positive determination is made in S201, the type of the vehicle including the internal combustion engine is classified into three types (plug The specific type of the vehicle 10 is a plug-in hybrid vehicle out of the three types of vehicles (internal hybrid vehicle, fuel cell vehicle, and electric vehicle). Therefore, in S202, it is determined that the specific type of the vehicle 10 is a plug-in hybrid vehicle. Then, the determination process is terminated.

[0058] If a negative determination is made in S201, then in S203 it is determined whether or not the data acquired in S101 in the transmission process includes CAN data related to the fuel cell. If a positive determination is made in S203, then the type of the vehicle including the fuel cell is a fuel cell vehicle out of three types (plug-in hybrid vehicle, fuel cell vehicle, and electric vehicle). Thus, in S204, it is determined that the specific type of the vehicle 10 is a fuel cell vehicle. Then, the determination process is terminated.

[0059] If a negative determination is made in S203, the acquired data does not include any CAN data related to the internal combustion engine or any CAN data related to the fuel cell. Therefore, it can be assumed that the acquired data does not include any information other than the CAN data related to the motor. Therefore, in S205, the specific type of the vehicle 10 is identified as an electric vehicle. Then, the identification process is terminated.

[0060] As described above, in the management system 1, the specific type of the vehicle 10 is identified based on the CAN data of the vehicle 10. Then, the status information is transmitted to the management server 200 in a predetermined format corresponding to the specific type of the vehicle 10. In this way, the management system 1 can transmit the status information in an appropriate format.

[0061] (Modification 1 of the first embodiment) In this embodiment, the in-vehicle device 100 generates the generated information and deletes lines including null values ​​in the generated information, thereby formatting the generated information into a predetermined format. However, the in-vehicle device 100 does not necessarily have to generate the generated information once and then format it into a predetermined format. For example, the in-vehicle device 100 may directly generate generated data other than the line number input in the deletion number field in the type information held in the type information DB 105 as status information and transmit it to the management server 200.

[0062] (Modification 2 of the first embodiment) In this embodiment, the predetermined format is a format in which there is no row in the generation information in which the generated data is null. However, the predetermined format does not necessarily have to be a format in which there is no row in the generation information in which the generated data is null, as long as it is a format designated for each of a plurality of types classified according to the power source of the vehicle 10. For example, assume that there is no null value in the generated data in the generation information. In this case, the predetermined format may be, for example, a format in which the generated data is arranged in order of importance of the generated data, which is determined by the type of vehicle.

[0063] (Third Modification of the First Embodiment) In this embodiment, the multiple types classified according to the power source of the vehicle are a plug-in hybrid vehicle, a fuel cell vehicle, and an electric vehicle. However, the multiple types classified according to the power source of the vehicle do not necessarily have to be a plug-in hybrid vehicle, a fuel cell vehicle, and an electric vehicle. In this modified example, the multiple types classified according to the power source of the vehicle are a hybrid vehicle, a fuel cell vehicle, and an electric vehicle. In other words, the multiple types may include a "hybrid vehicle," which is a type that includes both a hybrid vehicle that can be charged from an external source (a plug-in hybrid vehicle) and a hybrid vehicle that is not charged from an external source (a normal hybrid vehicle).

[0064] In this case, among the multiple types, fuel cell vehicles and electric vehicles do not have internal combustion engines, while hybrid vehicles (plug-in hybrid vehicles and normal hybrid vehicles) have internal combustion engines. Therefore, in the identification process, the in-vehicle device 100 identifies the specific type of the vehicle 10 as a hybrid vehicle when the acquired data includes CAN data related to the internal combustion engine. In this way, even if the multiple types are hybrid vehicles, fuel cell vehicles, and electric vehicles, it is possible to transmit status information to the management server 200 in an appropriate format corresponding to the specific type of the vehicle 10.

[0065] <Second embodiment> It is assumed that there may be cases where new data needs to be added to the status information transmitted by the in-vehicle device 100 in order to manage the status of the vehicle 10. Furthermore, when new data is added to the status information, it may be necessary to change the format of the status information. Therefore, the in-vehicle device 100 in this embodiment receives update information from the management server 200. The update information includes information requesting that specific data be added to the status information and transmitted to the management server 200. Furthermore, the update information includes information specifying a new data transmission format (hereinafter, sometimes referred to as a "new format") corresponding to the status information to which the specific data has been added. Below, only the points that differ from the first embodiment will be described.

[0066] The control unit 101 receives update information from the management server 200 via the communication unit 102. In this embodiment, the in-vehicle device 100 receives update information from the management server 200 via the network N1. However, the in-vehicle device 100 may receive update information from an external device other than the management server 200.

[0067] The update information includes information requesting that predetermined data be added to the status information and transmitted to the management server 200. In this embodiment, the status information is generated by generating the generation information and formatting the generated generation information. Therefore, the update information includes information related to the generation of the generation data (predetermined data) in the generation information. Specifically, the update information includes information specifying input data for generating the generation data (hereinafter, may be referred to as "input data information"). The update information also includes information specifying a generation method for converting the input data to convert the generation data (hereinafter, may be referred to as "method information"). The update information also includes information explaining the contents of the generation data generated by the input data information and the method information (hereinafter, may be referred to as "remark information"). The update information also includes information about the row number to which the generation data is input in the generation information (hereinafter, may be referred to as "number information").

[0068] Based on the update information, the control unit 101 updates the generation method information held in the generation method information DB 104. Specifically, the control unit 101 inputs the input data information in the update information into an input data field in the generation method information. The control unit 101 also inputs the method information in the update information into a generation method field in the generation method information. The control unit 101 also inputs the remarks information in the update information into a remarks field in the generation method information.

[0069] Here, the control unit 101 updates the generation method information held in the generation method information DB 104 based on the number information in the update information. That is, the control unit 101 adds a new row in the generation method information that corresponds to the row number input in the number information. Then, the control unit 101 inputs input data information, method information, and remark information to the newly added row.

[0070] The update information also includes information specifying a new format. Specifically, the update information includes information (hereinafter, sometimes referred to as "definition information") that specifies the line numbers to be deleted from the generation information when the generation information is formatted into a new format. In other words, the definition information is information that specifies the new format. The update information includes definition information that corresponds to each specific type.

[0071] The control unit 101 updates the deletion number field in the type information held in the type information DB 105 based on the definition information in the update information. Specifically, the control unit 101 inputs the line number specified in the definition information corresponding to a specific type into the deletion number field for the specific type in the type information. This causes the update information to update the line number to be deleted when formatting the generation information into the new format. In this way, the new format is defined.

[0072] (Update process) Next, the update process executed by the control unit 101 in the in-vehicle device 100 in the management system 1 will be described with reference to Fig. 10. Fig. 10 is a flowchart of the update process. The update process is a process for updating the generation method information held in the generation method information DB 104 and the type information held in the type information DB 105. The update process starts when the in-vehicle device 100 receives update information from the management server 200.

[0073] In the update process, first, in S301, update information is acquired. Next, in S302, the generation method information held in the generation method information DB 104 is updated based on the number information, input data information, method information, and remark information contained in the update information. Next, in S303, the type information held in the type information DB 105 is updated based on the definition information contained in the update information. Then, the update process is terminated.

[0074] As described above, in this embodiment, the generation method information held in the generation method information DB 104 and the type information held in the type information DB 105 are updated based on the update information. As a result, when the control unit 101 of the in-vehicle device 100 executes the transmission process, the generation information is generated based on the updated generation method information. Also, when the control unit 101 of the in-vehicle device 100 executes the transmission process, the generation information is formatted (state information is generated) based on the updated type information. As a result, it is possible to transmit state information to which data necessary for managing the state of the vehicle 10 has been added. The management system 1 makes it possible to transmit appropriate state information in an appropriate format.

[0075] (Modification of the second embodiment) In this embodiment, the management server 200 transmits update information including definition information corresponding to each specific type. Furthermore, the management server 200 transmits update information including number information, input data information, method information, and remark information to the in-vehicle device 100 without considering the specific type of the vehicle 10. However, the management server 200 may transmit update information that matches the specific type of the vehicle 10. In this case, the management server 200 identifies the specific type of the vehicle 10 based on, for example, the identifier of the vehicle 10. The management server 200 transmits update information to the in-vehicle device 100 when the update information is information for adding generated data that can be generated by the in-vehicle device 100. In this case, the in-vehicle device 100 can generate the generated data added by the update information, so the generation information does not include a null value. Therefore, the update information does not need to include definition information.

[0076] <Other embodiments> The above-described embodiment is merely an example, and the present disclosure may be modified as appropriate without departing from the spirit and scope of the present disclosure. Furthermore, the processes and means described in the present disclosure may be freely combined and implemented as long as no technical contradiction occurs.

[0077] Furthermore, a process described as being performed by one device may be shared and executed by multiple devices. Alternatively, a process described as being performed by different devices may be executed by one device. In a computer system, the hardware configuration (server configuration) by which each function is realized can be flexibly changed.

[0078] The present disclosure can also be realized by supplying a computer program implementing the functions described in the above embodiments to a computer, and having one or more processors of the computer read and execute the program. Such a computer program may be provided to the computer by a non-transitory computer-readable storage medium connectable to the system bus of the computer, or may be provided to the computer via a network. The non-transitory computer-readable storage medium includes any type of medium suitable for storing electronic instructions, such as, for example, a magnetic disk (such as a floppy disk or a hard disk drive (HDD)), an optical disk (such as a CD-ROM, a DVD disk, or a Blu-ray disk), a read-only memory (ROM), a random access memory (RAM), an EPROM, an EEPROM, a magnetic card, a flash memory, or an optical card. [Explanation of symbols]

[0079] 1. Management System 10. Vehicle 100...In-vehicle equipment 101 Control section 102 Communications Department 103...Acquisition Department 104...Generation method information DB 105··Type information DB 200 Management Server

Claims

1. An information processing device mounted on a specific vehicle, obtaining first information from the specific vehicle related to a power source of the specific vehicle; Identifying a type of the specific vehicle from a plurality of types classified according to a power source of the vehicle based on the first information; Transmitting second information on the state of the specific vehicle to a predetermined server device in a first format, which is a data transmission format corresponding to the type of the specific vehicle, among a plurality of data transmission formats designated for each of the plurality of types; A control unit that executes Information processing device.

2. The specific vehicle type is any one of a hybrid vehicle, a fuel cell vehicle, and an electric vehicle. The information processing device according to claim 1 .

3. The control unit is identifying the type of the specific vehicle as a hybrid vehicle if the first information includes at least information related to an internal combustion engine; The information processing device according to claim 2 .

4. The control unit is identifying the type of the specific vehicle as a fuel cell vehicle when the first information includes at least information related to a fuel cell; The information processing device according to claim 2 .

5. The control unit is Identifying the type of the specific vehicle as an electric vehicle when the first information does not include information other than information related to the motor. The information processing device according to claim 2 .

6. The control unit is receiving third information from an external device, the third information including information requesting that predetermined data be added to the second information and transmitted to the predetermined server device, and information specifying a new second format, which is a data transmission format corresponding to the second information to which the predetermined data has been added; Further execute transmitting the second information, to which the predetermined data has been added, in the second format corresponding to the specific vehicle type based on the third information to the predetermined server device; The information processing device according to claim 1 .

7. a first database storing fourth information for generating data included in the second information, and a second database storing fifth information on the first format designated for each of the plurality of types; The control unit is updating fourth information stored in the first database and fifth information stored in the second database based on the third information; Further execute The information processing device according to claim 6.

8. An information processing method executed by a computer installed in a specific vehicle, comprising: obtaining first information from the specific vehicle related to a power source of the specific vehicle; Identifying a type of the specific vehicle from a plurality of types classified according to a power source of the vehicle based on the first information; Transmitting second information on the state of the specific vehicle to a predetermined server device in a first format, which is a data transmission format corresponding to the type of the specific vehicle, among a plurality of data transmission formats designated for each of the plurality of types; Including, Information processing methods.

9. The specific vehicle type is any one of a hybrid vehicle, a fuel cell vehicle, and an electric vehicle. The information processing method according to claim 8.

10. identifying the type of the specific vehicle as a hybrid vehicle if the first information includes at least information related to an internal combustion engine; The information processing method according to claim 9.

11. identifying the type of the specific vehicle as a fuel cell vehicle when the first information includes at least information related to a fuel cell; The information processing method according to claim 9.

12. Identifying the type of the specific vehicle as an electric vehicle when the first information does not include information other than information related to the motor. The information processing method according to claim 9.

13. receiving third information from an external device, the third information including information requesting that predetermined data be added to the second information and transmitted to the predetermined server device, and information specifying a new second format, which is a data transmission format corresponding to the second information to which the predetermined data has been added; Further comprising: transmitting the second information, to which the predetermined data has been added, in the second format corresponding to the specific vehicle type based on the third information to the predetermined server device; The information processing method according to any one of claims 8 to 12.

14. The computer includes: a first database storing fourth information for generating data included in the second information, and a second database storing fifth information on the first format designated for each of the plurality of types; In the information processing method, updating fourth information stored in the first database and fifth information stored in the second database based on the third information; Further comprising: The information processing method according to claim 13.

15. A program for causing a computer mounted on a specific vehicle to execute an information processing method, The information processing method includes: obtaining first information from the specific vehicle related to a power source of the specific vehicle; Based on the first information, the characteristic is selected from a plurality of types classified according to a power source of the vehicle. Identifying a type of fixed vehicle; Transmitting second information on the state of the specific vehicle to a predetermined server device in a first format, which is a data transmission format corresponding to the type of the specific vehicle, among a plurality of data transmission formats designated for each of the plurality of types; Including, program.

16. The specific vehicle type is any one of a hybrid vehicle, a fuel cell vehicle, and an electric vehicle. The program according to claim 15.

17. In the information processing method, identifying the type of the specific vehicle as a hybrid vehicle if the first information includes at least information related to an internal combustion engine; The program according to claim 16.

18. In the information processing method, identifying the type of the specific vehicle as a fuel cell vehicle when the first information includes at least information related to a fuel cell; The program according to claim 16.

19. In the information processing method, Identifying the type of the specific vehicle as an electric vehicle when the first information does not include information other than information related to the motor. The program according to claim 16.

20. The information processing method includes: receiving third information from an external device, the third information including information requesting that predetermined data be added to the second information and transmitted to the predetermined server device, and information specifying a new second format, which is a data transmission format corresponding to the second information to which the predetermined data has been added; Further comprising: transmitting the second information, to which the predetermined data has been added, in the second format corresponding to the specific vehicle type based on the third information to the predetermined server device; 20. The program according to any one of claims 15 to 19.

Images