Data processing device, data processing method and data processing program
Patent Information
- Application Number
- JP2023011005
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-01-27
- Publication Date
- 2025-07-17
- Estimated Expiration
- 2043-01-27
AI Technical Summary
The challenge lies in handling vehicle data collected using different methods, as the format of the data varies, making it difficult to integrate and utilize effectively.
A data processing device and method that standardizes vehicle data by generating standardized data IDs and values through normalization, allowing data to be formatted consistently regardless of the acquisition method, and transmitting it based on dynamic or static data characteristics.
Enables the use of vehicle data in a common format, facilitating easier integration and management, and allows for efficient transmission based on data frequency changes, reducing wasteful data transmission.
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
[Technical field]
[0001] The present disclosure relates to a data processing device, a data processing method, and a data processing program for acquiring vehicle data. [Background technology]
[0002] Patent Document 1 describes a digital twin simulation that reproduces the real-world state of a vehicle in a virtual space by collecting vehicle data from the vehicle. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] JP 2019-153291 A Summary of the Invention [Problem to be solved by the invention]
[0004] In recent years, the development of mobility services that utilize vehicle data has become more common. Particularly in the field of logistics, there is a demand to collect vehicle data such as driving data, fuel consumption, and battery information in order to comply with legal regulations or improve the efficiency of transportation and delivery.
[0005] For example, static information such as the manufacturer and specifications of the battery can be collected by reading a QR code or barcode attached to the battery. Dynamically changing information such as the battery usage history can be repeatedly collected and recorded from the vehicle using wireless communication such as BLE and Wi-Fi. In this way, various data collection methods are possible. QR code is a registered trademark. BLE is an abbreviation for Bluetooth Low Energy. Bluetooth is a registered trademark. Wi-Fi is a registered trademark.
[0006] As a result of detailed investigation by the inventors, it was found that if the format of collected data differs for each data collection method, it becomes difficult to handle the data when using vehicle data. The present disclosure aims to make data easier to use. [Means for solving the problem]
[0007] One aspect of the present disclosure is a data processing device (2) including a first acquisition unit (5), a second acquisition unit (3, 4), a standardization processing unit (S10 to S360), a data storage unit (7), and a data transmission unit (S410 to S430).
[0008] The first acquisition unit is configured to acquire first data, which is data related to the vehicle, from the vehicle in a preset first acquisition method. The second acquisition unit is configured to acquire second data, which is data relating to something other than the vehicle, from something other than the vehicle in a preset second acquisition manner.
[0009] The standardization processing unit is configured to generate, for the first data acquired by the first acquisition unit, first standardized data including a first data ID for identifying the first data and a first standard data value obtained by normalizing the value of the first data, and to generate, for the second data acquired by the second acquisition unit, second standardized data including a second data ID for identifying the second data and a second standard data value obtained by normalizing the value of the second data.
[0010] The data store is configured to store the first standardized data and the second standardized data. The data transmission unit is configured to transmit the first standardized data and the second standardized data stored in the data storage unit when a predetermined data transmission condition is satisfied for each of the first standardized data and the second standardized data.
[0011] The data processing device of the present disclosure configured in this manner converts each piece of data into a format consisting of a data ID and a data value, and normalizes multiple pieces of data received using different acquisition methods to generate multiple standardized data, thereby making it possible to provide data in a common data format that is independent of the acquisition method, making it easier to use the data.
[0012] Another aspect of the present disclosure is a data processing method executed by a data processing device. In the data processing method disclosed herein, first data, which is data related to the vehicle, is acquired from the vehicle using a first acquisition method that is set in advance, and second data, which is data related to something other than the vehicle, is acquired from something other than the vehicle using a second acquisition method that is set in advance.
[0013] In the data processing method disclosed herein, for acquired first data, first standardized data is generated, the first standardized data including a first data ID for identifying the first data and a first standard data value obtained by normalizing the value of the first data, and for acquired second data, second standardized data is generated, the second standardized data including a second data ID for identifying the second data and a second standard data value obtained by normalizing the value of the second data.
[0014] In the data processing method of the present disclosure, when a preset data transmission condition is satisfied for each of the first standardized data and the second standardized data, the first standardized data and the second standardized data are transmitted.
[0015] The data processing method of the present disclosure is a method executed by the data processing device of the present disclosure, and by executing the method, it is possible to obtain the same effects as the data processing device of the present disclosure. Yet another aspect of the present disclosure is a data processing program for causing a computer to function as a first acquisition unit (5), a second acquisition unit (3, 4), a standardization processing unit (S10 to S360), a data storage unit (7), and a data transmission unit (S410 to S430).
[0016] A computer controlled by the data processing program of the present disclosure can constitute a part of the data processing device of the present disclosure, and can obtain the same effects as the data processing device of the present disclosure. [Brief description of the drawings]
[0017] [Figure 1] FIG. 1 is a block diagram showing a configuration of a data processing device. [Diagram 2] 13 is a flowchart showing a format standardization process. [Diagram 3] FIG. 1 is a diagram illustrating a common format. [Figure 4] 13 is a flowchart showing a data extraction process. [Diagram 5] 11 is a diagram for explaining a storage format of raw data IDs and raw data values. FIG. [Figure 6] 13 is a flowchart showing a data standardization process. [Figure 7] 13 is a diagram for explaining a storage format of a standard data ID and a standard data value. FIG. [Figure 8] 13 is a flowchart showing a data transmission process. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0018] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. The data processing device 1 of this embodiment is a smartphone carried by the driver of the vehicle, and as shown in FIG. 1, includes a control unit 2, a QR code reader 3, a Wi-Fi communication unit 4, a BLE communication unit 5, a data acquisition unit 6, a data storage unit 7, an external communication unit 8, and a bus 9.
[0019] The control unit 2 is an electronic control device mainly composed of a microcomputer including a CPU 11, a ROM 12, a RAM 13, etc. Various functions of the microcomputer are realized by the CPU 11 executing a program stored in a non-transient real recording medium. In this example, the ROM 12 corresponds to the non-transient real recording medium storing the program. Furthermore, the execution of this program executes a method corresponding to the program. Note that some or all of the functions executed by the CPU 11 may be configured as hardware using one or more ICs, etc. Also, the number of microcomputers constituting the control unit 2 may be one or more.
[0020] The QR code reader 3 includes a camera (not shown) and reads the QR code by photographing the QR code with the camera. The QR code reader 3 decodes the QR code read by the camera and outputs the data obtained by the decoding as QR code data. In this embodiment, the QR code reader 3 reads the QR code attached to a battery mounted on the vehicle.
[0021] The QR code data includes one or more raw data IDs for identifying battery data relating to the battery (e.g., the battery manufacturer and specifications) and one or more raw data values indicating values of the battery data corresponding to each of the one or more raw data IDs.
[0022] The Wi-Fi communication unit 4 performs short-distance wireless communication in accordance with the Wi-Fi standard. The Wi-Fi communication unit 4 outputs received data as Wi-Fi data. In this embodiment, the Wi-Fi communication unit 4 performs data communication with a charging device that charges the battery of the vehicle.
[0023] The Wi-Fi data includes one or more raw data IDs for identifying charging device data (e.g., charging power) related to the charging device, and one or more raw data values that indicate values of the charging device data corresponding to each of the one or more raw data IDs.
[0024] The BLE communication unit 5 performs short-distance wireless communication in accordance with BLE, which is an extended specification of Bluetooth. The BLE communication unit 5 outputs received data as BLE data. In this embodiment, the BLE communication unit 5 performs data communication with multiple ECUs mounted on the vehicle. ECU is an abbreviation for Electronic Control Unit.
[0025] The BLE data includes one or more raw data IDs for identifying vehicle data related to the vehicle (e.g., vehicle speed, engine RPM), and one or more raw data values indicating values of the vehicle data corresponding to each of the one or more raw data IDs.
[0026] The data acquisition unit 6 is an electronic control device mainly composed of a microcomputer including a CPU 21, a ROM 22, a RAM 23, etc. Various functions of the microcomputer are realized by the CPU 21 executing a program stored in a non-transitive substantial recording medium. In this example, the ROM 22 corresponds to the non-transitive substantial recording medium storing the program. Furthermore, the execution of this program executes a method corresponding to the program. Note that some or all of the functions executed by the CPU 21 may be configured as hardware using one or more ICs, etc. Also, the number of microcomputers constituting the data acquisition unit 6 may be one or more.
[0027] The data storage unit 7 is a storage device for storing various data. The external communication unit 8 performs data communication with the management center 100 via the wide area wireless communication network NW. The management center 100 is a device that acquires vehicle data related to a plurality of vehicles corresponding to each of the plurality of data processing devices 1 from each of the plurality of data processing devices 1, and manages the plurality of vehicles.
[0028] The bus 9 connects the control unit 2, the QR code reader 3, the Wi-Fi communication unit 4, the BLE communication unit 5, the data acquisition unit 6, the data storage unit 7, and the external communication unit 8 so that they can input and output data to each other.
[0029] Next, a description will be given of the procedure of the format standardization process executed by the data acquisition unit 6. The format standardization process is a process that is repeatedly executed while the data processing device 1 is in operation. 2, when the format standardization process is executed, the CPU 21 of the data acquisition unit 6 first determines in S10 whether or not QR code data has been output from the QR code reader 3. If QR code data has not been output from the QR code reader 3, the CPU 21 proceeds to S30.
[0030] On the other hand, when QR code data is output from the QR code reader 3, the CPU 21 acquires the QR code data output from the QR code reader 3 in S20, and generates commonly formatted data by converting the QR code data into a commonly formatted data described below, and then proceeds to S30.
[0031] In S30, the CPU 21 determines whether or not Wi-Fi data has been output from the Wi-Fi communication unit 4. If Wi-Fi data has not been output from the Wi-Fi communication unit 4, the CPU 21 proceeds to S50.
[0032] On the other hand, when Wi-Fi data is output from the Wi-Fi communication unit 4, the CPU 21 acquires the Wi-Fi data from the Wi-Fi communication unit 4 in S40, generates commonly formatted data by converting the Wi-Fi data into the above-mentioned common format, and proceeds to S50.
[0033] When the process proceeds to S50, the CPU 21 determines whether or not BLE data has been output from the BLE communication unit 5. Here, if BLE data has not been output from the BLE communication unit 5, the CPU 21 ends the format standardization process.
[0034] On the other hand, when BLE data is output from the BLE communication unit 5, the CPU 21 acquires the BLE data from the BLE communication unit 5 in S60, and generates commonly formatted data by converting the BLE data into the above-mentioned common format, and then terminates the format commonization process.
[0035] As shown in FIG. 3, the commonly formatted data is made up of one communication type field and one or more data fields. The communication type field stores communication type information indicating the communication type. The data size of the communication type information is 8 bits. The communication type information is set to 0 or 1 depending on the communication type. When the communication type information is set to 0, the data in the data field is dynamic data. When the communication type information is set to 1, the data in the data field is static data. Dynamic data is data whose value changes in a short period of time, and static data is data whose value does not change in a short period of time. In this embodiment, Wi-Fi data and BLE data are dynamic data, and QR code data is static data.
[0036] One data field stores one data ID and one data value. The data size of one data ID is 16 bits. The data size of one data value is variable. If the data value is a numeric value, it is expressed in binary. If the data value is a character, it is expressed in UTF-8 format.
[0037] In S20 above, the CPU 21 generates one or more data fields by extracting raw data values corresponding to one or more raw data IDs included in the acquired QR code data from the QR code data. The CPU 21 also generates a communication type field in which the communication type information is set to 1. The CPU 21 then generates commonly formatted data by concatenating one communication type field with one or more data fields.
[0038] In the above S40, the CPU 21 generates one or more data fields by extracting corresponding raw data values from the Wi-Fi data for each of one or more raw data IDs included in the acquired Wi-Fi data. The CPU 21 also generates a communication type field in which the communication type information is set to 0. The CPU 21 then generates commonly formatted data by concatenating one communication type field with one or more data fields.
[0039] In the above S60, the CPU 21 generates one or more data fields by extracting corresponding raw data values from the BLE data for each of one or more raw data IDs included in the acquired BLE data. The CPU 21 also generates a communication type field in which communication type information is set to 0. The CPU 21 then generates commonly formatted data by concatenating one communication type field with one or more data fields.
[0040] Next, a description will be given of the procedure of the data extraction process executed by the control unit 2. The data extraction process is a process that is repeatedly executed while the data processing device 1 is in operation. When the data extraction process is executed, the CPU 11 of the control unit 2 first determines in S110 whether or not the data acquisition unit 6 has generated new commonly formatted data, as shown in Fig. 4. If the data acquisition unit 6 has not generated new commonly formatted data, the CPU 11 ends the data extraction process.
[0041] On the other hand, if the data acquisition unit 6 has generated new commonly-formatted data, the CPU 11 acquires the new commonly-formatted data in S120, and identifies the communication type by extracting communication type information from the acquired commonly-formatted data.
[0042] At S130, the CPU 11 determines whether the data included in the acquired commonly-formatted data is dynamic data or not, based on the identification result at S120. Specifically, when the communication type information of the commonly-formatted data is set to 0, the CPU 11 determines that the data included in the commonly-formatted data is dynamic data. On the other hand, when the communication type information of the commonly-formatted data is set to 1, the CPU 11 determines that the data included in the commonly-formatted data is static data.
[0043] Here, if the data contained in the commonly formatted data is dynamic data, in S140, the CPU 11 extracts one data field, in which the raw data ID and raw data value have not been identified, from the commonly formatted data acquired in S120, in order from the beginning of the commonly formatted data.
[0044] In S150, the CPU 11 identifies the raw data ID of the data field extracted in S140. At S160, the CPU 11 identifies the raw data values of the data fields extracted at S140.
[0045] In S170, the CPU 11 updates the raw data value identified in S160. Specifically, as shown in Fig. 5, the CPU 11 associates the raw data ID identified in S150 with the raw data value identified in S160 and stores them in the RAM 13. If the raw data ID identified in S150 is not stored in the RAM 13, the CPU 11 stores the raw data ID identified in S150 and the raw data value identified in S160 in the RAM 13. On the other hand, if the raw data ID identified in S150 has already been stored in the RAM 13, the CPU 11 overwrites the raw data value identified in S160 in the storage area in which the raw data value corresponding to the raw data ID identified in S150 is stored.
[0046] 4, in S180, CPU 11 determines whether or not there is a next data field following the data field extracted in S140. If there is a next data field following the data field extracted in S140, CPU 11 proceeds to S140. On the other hand, if there is no next data field following the data field extracted in S140, CPU 11 ends the data extraction process.
[0047] Furthermore, if it is determined in S130 that the data included in the commonly formatted data is not dynamic data, then in S190 the CPU 11 extracts one data field in the same manner as in S140.
[0048] In S200, the CPU 11 identifies the raw data ID of the data field extracted in S190 in the same manner as in S150. In S210, the CPU 11 identifies the raw data values of the data field extracted in S190 in the same manner as in S160.
[0049] In S220, the CPU 11 updates the raw data value identified in S210 in the same manner as in S170. In S230, the CPU 11 determines whether or not there is a next data field following the data field extracted in S190. If there is a next data field following the data field extracted in S190, the CPU 11 proceeds to S190. On the other hand, if there is no next data field following the data field extracted in S190, the CPU 11 executes a data standardization instruction in S240 and ends the data extraction process.
[0050] Next, a description will be given of the procedure of the data standardization process executed by the control unit 2. The data standardization process is a process that is repeatedly executed while the data processing device 1 is in operation. When the data standardization process is executed, the CPU 11 of the control unit 2 first determines whether or not preset data standardization conditions are met in S310, as shown in Fig. 6. In this embodiment, the data standardization conditions include a first regular standardization condition, a second regular standardization condition, a third regular standardization condition, a first event standardization condition, and a second event standardization condition.
[0051] The first regular standardization condition is that a first period (e.g., 1 second) has elapsed since the first regular standardization condition was last satisfied. The second regular standardization condition is that a second period (e.g., 1 minute) has elapsed since the second regular standardization condition was last satisfied. The third regular standardization condition is that a third period (e.g., 1 hour) has elapsed since the third regular standardization condition was last satisfied.
[0052] The first event standardization condition is that the control unit 2 executes a data standardization instruction. The second event standardization condition is that a raw data value corresponding to a raw data ID that matches a preset second event target data ID changes.
[0053] Here, if the data standardization condition is not satisfied, the CPU 11 ends the data standardization process. On the other hand, if the data standardization condition is satisfied, the CPU 11 acquires, in S320, one or more raw data IDs that are preset for the satisfied data standardization condition, and one or more raw data values corresponding to the one or more raw data IDs.
[0054] In S330, the CPU 11 generates standardized data by performing data standardization using one or more raw data IDs and one or more raw data values acquired in S320. The standardized data is composed of one standard ID and one standard data value. Specifically, the CPU 11 refers to the standardization table stored in the ROM 12 and converts one or more raw data IDs and one or more raw data values into one or more standard IDs and one or more standard data values.
[0055] The standardization table includes a plurality of normalization information and a plurality of semantic information. The normalization information is information for normalizing raw data values so that the same physical quantities have the same values regardless of the vehicle model and vehicle manufacturer.
[0056] The normalization information includes ID conversion information for converting raw data IDs to standard IDs, and data value conversion information for converting raw data values to standard data values. The ID conversion information is information for converting data IDs so that the same type has the same value regardless of the vehicle model and vehicle manufacturer. For example, the raw data ID for "vehicle speed" differs depending on the vehicle model and vehicle manufacturer. In contrast, the raw data ID for "vehicle speed" is converted to the same standard ID based on the ID conversion information, regardless of the vehicle model and vehicle manufacturer. The data value conversion information includes, for example, "number of significant digits," "resolution," "offset," and "unit." "Number of significant digits" is information indicating the number of significant digits of a standard data value. "Resolution" is information indicating the numerical value per bit. "Offset" indicates the offset amount of the numerical value of the data. "Unit" indicates the unit of the data.
[0057] The data value conversion information also includes, for example, a correspondence table between raw data values and standard data values. For example, the correspondence table associates raw data values "0", "1", "2", and "3" with shift positions "P", "R", "N", and "D", respectively.
[0058] The semantic information is information (e.g., an arithmetic formula, a conversion table) for converting the normalized raw data values into meaningful vehicle data. The semantic information may use the raw data values before normalization.
[0059] The semantic information includes a "standard ID" corresponding to the standard data value calculated by the conversion, and a conversion formula or conversion table for converting the raw data value into the standard data value. The conversion formula is, for example, a formula for converting the raw data value indicating the "steering movement angle" into the standard data value indicating the "steering angle" by subtracting the raw data value indicating the "steering zero point".
[0060] In S340, the CPU 11 updates the standardized data generated in S330. Specifically, as shown in Fig. 7, the CPU 11 associates the standard ID with the standard data value for the standardized data generated in S330 and stores them in the data storage unit 7. If the standard ID of the standardized data generated in S330 is not stored in the data storage unit 7, the CPU 11 stores the standard ID and the standard data value of the standardized data generated in S330 in the data storage unit 7. On the other hand, if the standard ID of the standardized data generated in S330 is stored in the data storage unit 7, the CPU 11 overwrites the standard data value of the standardized data generated in S330 in the storage area in which the standard data value corresponding to the standard ID of the standardized data generated in S330 is stored.
[0061] 6, the CPU 11 determines whether the first event standardization condition or the second event standardization condition is satisfied at S350. If the first event standardization condition or the second event standardization condition is not satisfied, the CPU 11 ends the data standardization process. On the other hand, if the first event standardization condition or the second event standardization condition is satisfied, the CPU 11 executes a data transmission instruction at S360 and ends the data standardization process.
[0062] Next, a description will be given of the procedure of the data transmission process executed by the control unit 2. The data transmission process is a process that is repeatedly executed while the data processing device 1 is in operation. When the data transmission process is executed, the CPU 11 of the control unit 2 first determines whether or not preset data transmission conditions are met in S410, as shown in Fig. 8. In this embodiment, the data transmission conditions include a first periodic transmission condition, a second periodic transmission condition, a third periodic transmission condition, and an event transmission condition.
[0063] The first periodic transmission condition is that a first period (e.g., 1 second) has elapsed since the first periodic transmission condition was last satisfied. The second periodic transmission condition is that a second period (e.g., 1 minute) has elapsed since the second periodic transmission condition was last satisfied. The third periodic transmission condition is that a third period (e.g., 1 hour) has elapsed since the third periodic transmission condition was last satisfied. The event transmission condition is that the control unit 2 executes a data transmission instruction.
[0064] If the data transmission condition is not satisfied, the CPU 11 ends the data transmission process. On the other hand, if the data transmission condition is satisfied, the CPU 11 acquires, from the data storage unit 7, one or more standardized data items that are preset for the satisfied data standardization condition in S420.
[0065] In S430, the CPU 11 causes the external communication unit 8 to execute a process of transmitting one or more standardized data acquired in S420 to the management center 100, and ends the data transmission process. The data processing device 1 configured in this manner includes a BLE communication unit 5, a Wi-Fi communication unit 4, a QR code reader 3, a data acquisition unit 6, a control unit 2, a data storage unit 7, and an external communication unit 8.
[0066] The BLE communication unit 5 acquires vehicle data related to the vehicle from the vehicle by performing short-distance wireless communication in a method conforming to BLE. The Wi-Fi communication unit 4 acquires charging device data relating to the charging device from the charging device by performing short-distance wireless communication in a method compliant with the Wi-Fi standard.
[0067] The QR code reader 3 reads a QR code attached to a battery mounted in a vehicle, thereby acquiring battery data relating to the battery from the battery. The data acquisition unit 6 and the control unit 2 generate standardized data for the vehicle data acquired by the BLE communication unit 5, the standardized data including a standard ID for identifying the vehicle data and a standard data value obtained by normalizing the value of the vehicle data.
[0068] The data acquisition unit 6 and the control unit 2 generate standardized data for the charging device data acquired by the Wi-Fi communication unit 4, the standardized data including a standard ID for identifying the charging device data and a standard data value obtained by normalizing the value of the charging device data.
[0069] The data acquiring unit 6 and the control unit 2 generate standardized data for the battery data acquired by the QR code reader 3, the standardized data including a standard ID for identifying the battery data and a standard data value obtained by normalizing the value of the battery data.
[0070] The data storage unit 7 stores the standardized data and the standardized data. The control unit 2 and the external communication unit 8 transmit the standardized data stored in the data storage unit 7 to the management center 100 when a preset data transmission condition is met.
[0071] Such a data processing device 1 converts each piece of data into a format consisting of a data ID and a data value, and normalizes multiple pieces of data acquired using different acquisition methods to generate multiple standardized data, thereby making it possible to provide data in a common data format that is independent of the acquisition method, making it easier to use the data.
[0072] Furthermore, in the data processing device 1, the data acquisition unit 6 that generates the commonly formatted data is separated from the other components (i.e., the control unit 2, the QR code reader 3, the Wi-Fi communication unit 4, the BLE communication unit 5, the data storage unit 7, and the external communication unit 8) that configure the data processing device 1. Therefore, when adding a new acquisition method to the data processing device 1, it is only necessary to add a new data communication unit (e.g., the QR code reader 3, the Wi-Fi communication unit 4, the BLE communication unit 5, etc.) and change the configuration of the data acquisition unit 6, which makes it easy to expand the data processing device 1.
[0073] Furthermore, the data acquisition unit 6 determines whether each of the vehicle data acquired by the BLE communication unit 5, the charging device data acquired by the Wi-Fi communication unit 4, and the battery data acquired by the QR code reader 3 is dynamic data or static data, and sets communication type information indicating whether the data is dynamic data or static data in the standardized data. Specifically, the data acquisition unit 6 adds the communication type information to the commonly formatted data, thereby setting the communication type information in the standardized data.
[0074] When the data transmission condition set according to the communication type information is satisfied, the control unit 2 and the external communication unit 8 transmit the standardized data. In this embodiment, the first periodic transmission condition, the second periodic transmission condition, or the third periodic transmission condition is set as the data transmission condition for the dynamic data, and the event transmission condition is set for the static data.
[0075] Such a data processing device 1 can transmit dynamic data whose data value changes in a short time to the management center 100 at an appropriate timing according to how often the data value changes. This allows the management center 100 to manage changes in dynamic data. Furthermore, the data processing device 1 can transmit static data whose data value does not change in a short time to the management center 100 at an appropriate timing according to how often the data value changes. This allows the data processing device 1 to suppress wasteful transmission of static data to the management center 100 even when the data value of the static data has not changed.
[0076] Furthermore, when the communication type information indicates static data, the data transmission condition (i.e., the event transmission condition) is set so that the standardized data corresponding to the static data is transmitted immediately after it is generated. This enables the data processing device 1 to provide the management center 100 with the standardized data corresponding to the static data as early as possible.
[0077] Furthermore, when the communication type information indicates dynamic data, the data transmission conditions (i.e., the first periodic transmission condition, the second periodic transmission condition, and the third periodic transmission condition) are set so that the standardized data corresponding to the dynamic data is transmitted every time a preset transmission cycle (i.e., the first cycle, the second cycle, and the third cycle) elapses. This allows the data processing device 1 to provide the management center 100 with the standardized data at any timing that does not depend on the data acquisition frequency for each data acquisition method of the QR code reader 3, the Wi-Fi communication unit 4, and the BLE communication unit 5.
[0078] In addition, a raw data ID for identifying the vehicle data is added to the vehicle data acquired by the BLE communication unit 5. A raw data ID for identifying the charging device data is added to the charging device data acquired by the Wi-Fi communication unit 4. A raw data ID for identifying the battery data is added to the battery data acquired by the QR code reader 3.
[0079] Then, the data acquisition unit 6 converts the vehicle data acquired by the BLE communication unit 5 into commonly formatted data including a raw data ID and a raw data value indicating the value of the vehicle data. The data acquisition unit 6 converts the charging device data acquired by the Wi-Fi communication unit 4 into commonly formatted data including a raw data ID and a raw data value indicating the value of the charging device data. The data acquisition unit 6 converts the battery data acquired by the QR code reader 3 into commonly formatted data including a raw data ID and a raw data value indicating the value of the battery data.
[0080] The control unit 2 generates standardized data by normalizing raw data values contained in the commonly formatted data. Such a data processing device 1 can generate standardized data at any timing independent of the data acquisition frequency for each data acquisition method of the QR code reader 3, the Wi-Fi communication unit 4, and the BLE communication unit 5.
[0081] Furthermore, the data acquisition unit 6 determines whether the vehicle data acquired by the BLE communication unit 5 is dynamic data or static data, and adds communication type information indicating whether the data is dynamic or static data to the commonly formatted data. The data acquisition unit 6 determines whether the charging device data acquired by the Wi-Fi communication unit 4 is dynamic data or static data, and adds communication type information indicating whether the data is dynamic or static data to the commonly formatted data. The data acquisition unit 6 determines whether the battery data acquired by the QR code reader 3 is dynamic data or static data, and adds communication type information indicating whether the data is dynamic or static data to the commonly formatted data.
[0082] In addition, the data transmission conditions for static data are set so that the standardized data that is the subject of the data transmission conditions is transmitted every time after it is generated. This enables the data processing device 1 to provide the management center 100 with the standardized data that corresponds to the static data as early as possible.
[0083] Furthermore, the data transmission condition for static data is set to prohibit transmission when the standardized data subject to the data transmission condition is generated and the standard data value included in the standardized data has not changed. This allows the data processing device 1 to prevent wasteful transmission of static data to the management center 100 even when the data value of the static data has not changed.
[0084] In the embodiment described above, the BLE communication unit 5 corresponds to a first acquisition unit, the Wi-Fi communication unit 4 and the QR code reader 3 correspond to a second acquisition unit, and S10 to S360 correspond to the processing of a standardization processing unit.
[0085] Moreover, the data accumulation unit 7 corresponds to a data storage unit, and S410 to S430 correspond to the processing as a data transmission unit. In addition, the method compliant with BLE corresponds to the first acquisition method, vehicle data corresponds to the first data, the method compliant with the Wi-Fi standard corresponds to the second acquisition method, charging device data corresponds to the second data, reading the QR code corresponds to the second acquisition method, and battery data corresponds to the second data.
[0086] Furthermore, the standard data ID included in the standardized data of the vehicle data corresponds to the first data ID, and the standard data value included in the standardized data of the vehicle data corresponds to the first standard data value. Furthermore, the standard data ID included in the standardized data of the charging device data and the battery data corresponds to the second data ID, and the standard data value included in the standardized data of the charging device data and the battery data corresponds to the second standardized data.
[0087] In addition, the communication type information corresponds to type information, the first period, the second period and the third period correspond to transmission periods, the raw data ID included in the commonly formatted data of the vehicle data corresponds to the first raw data ID, and the raw data ID included in the commonly formatted data of the charging device data and the battery data corresponds to the second raw data ID.
[0088] Furthermore, the raw data values included in the commonly-formatted data of the vehicle data correspond to first raw data values, and the commonly-formatted data of the vehicle data corresponds to first commonly-formatted data. Furthermore, the raw data values included in the common-formatted data of the charging device data and the battery data correspond to second raw data values, and the common-formatted data of the charging device data and the battery data corresponds to second common data.
[0089] Although one embodiment of the present disclosure has been described above, the present disclosure is not limited to the above embodiment and can be implemented in various modified forms. [Variation 1] In the above embodiment, the data processing device 1 is a smartphone, but the data processing device 1 may be an in-vehicle device mounted in a vehicle.
[0090] [Variation 2] In the above embodiment, a form in which short-distance wireless communication is performed in accordance with the Wi-Fi standard or BLE has been shown, but the data processing device 1 may be configured to perform wireless communication in any form as long as it can perform wireless communication, for example, wireless communication may be performed in accordance with the UWB standard. UWB is an abbreviation for Ultra Wide Band.
[0091] [Variation 3] In the above embodiment, a QR code attached to the battery is read, but a bar code attached to the battery may be read.
[0092] The control unit 2 and the method described in the present disclosure may be realized by a dedicated computer provided by configuring a processor and a memory programmed to execute one or more functions embodied in a computer program. Alternatively, the control unit 2 and the method described in the present disclosure may be realized by a dedicated computer provided by configuring a processor with one or more dedicated hardware logic circuits. Alternatively, the control unit 2 and the method described in the present disclosure may be realized by one or more dedicated computers configured by a combination of a processor and a memory programmed to execute one or more functions and a processor configured with one or more hardware logic circuits. In addition, the computer program may be stored in a computer-readable non-transient tangible recording medium as instructions executed by a computer. The method for realizing the functions of each unit included in the control unit 2 does not necessarily need to include software, and all of the functions may be realized using one or more hardware.
[0093] In the above embodiments, multiple functions of one component may be realized by multiple components, or one function of one component may be realized by multiple components. Also, multiple functions of multiple components may be realized by one component, or one function realized by multiple components may be realized by one component. Also, part of the configuration of the above embodiments may be omitted. Also, at least part of the configuration of the above embodiments may be added to or substituted for the configuration of another of the above embodiments.
[0094] In addition to the data processing device 1 described above, the present disclosure can also be realized in various forms, such as a system including the data processing device 1 as a component, a program for causing a computer to function as the data processing device 1, a non-transient physical recording medium such as a semiconductor memory on which this program is recorded, and a data processing method. [Technical idea disclosed in this specification] [Item 1] A first acquisition unit (5) configured to acquire first data, which is data related to the vehicle, from the vehicle in a first acquisition method set in advance; A second acquisition unit (3, 4) configured to acquire second data, which is data related to the vehicle, from a source other than the vehicle by a second acquisition method set in advance; a standardization processing unit (S10 to S360) configured to generate, for the first data acquired by the first acquisition unit, first standardized data including a first data ID for identifying the first data and a first standard data value obtained by normalizing a value of the first data, and to generate, for the second data acquired by the second acquisition unit, second standardized data including a second data ID for identifying the second data and a second standard data value obtained by normalizing a value of the second data; a data storage unit (7) configured to store the first standardized data and the second standardized data; a data transmission unit (S410 to S430) configured to transmit the first standardized data and the second standardized data stored in the data storage unit when a preset data transmission condition is satisfied for each of the first standardized data and the second standardized data; A data processing device (2) comprising:
[0095] [Item 2] Item 1. A data processing device according to item 1, the standardization processing unit is configured to determine whether the first data and the second data acquired by the first acquisition unit and the second acquisition unit are dynamic data or static data, and to set type information indicating whether the data is the dynamic data or the static data in the first standardized data and the second standardized data; The data processing device is configured such that the data transmission unit transmits the first standardized data and the second standardized data when the data transmission condition set for each of the first standardized data and the second standardized data in accordance with the type information is satisfied.
[0096] [Item 3] Item 2. A data processing device comprising: A data processing device in which, when the type information indicates the static data, the data transmission condition is set so that the first standardized data or the second standardized data that is the subject of the data transmission condition is transmitted after it is generated.
[0097] [Item 4] The data processing device according to item 2 or 3, A data processing device, wherein when the type information indicates the dynamic data, the data transmission condition is set so as to transmit the first standardized data or the second standardized data that is the subject of the data transmission condition every time a predetermined transmission period elapses.
[0098] [Item 5] A data processing device according to any one of items 1 to 4, A first raw data ID for identifying the first data is added to the first data acquired by the first acquisition unit, A second raw data ID for identifying the second data is added to the second data acquired by the second acquisition unit, The standardization processing unit includes: converting the first data acquired by the first acquisition unit into first common data including the first raw data ID and a first raw data value indicating a value of the first data; converting the second data acquired by the second acquisition unit into second common data, which is common data including the second raw data ID and a second raw data value indicating a value of the second data; generating the first standardized data by normalizing the first raw data values included in the first common data; A data processing device configured to generate the second standardized data by normalizing the second raw data values included in the second common data.
[0099] [Item 6] Item 6. A data processing device according to item 5, The standardization processing unit is a data processing device configured to determine whether the first data and the second data acquired by the first acquisition unit and the second acquisition unit are dynamic data or static data, and to add type information indicating whether the data is dynamic data or static data to the first common data and the second common data.
[0100] [Item 7] Item 3. A data processing device according to item 3, The data processing device, wherein the data transmission condition is set so as to transmit the first standardized data or the second standardized data that is the subject of the data transmission condition every time after the first standardized data or the second standardized data that is the subject of the data transmission condition is generated.
[0101] [Item 8] Item 3. A data processing device according to item 3, The data processing device, wherein the data transmission conditions are set to prohibit transmission when the data values contained in the first standardized data or the second standardized data that are subject to the data transmission conditions have not changed, even if the first standardized data or the second standardized data that is subject to the data transmission conditions has been generated.
[0102] [Item 9] A data processing method executed by a data processing device, comprising: Acquire first data relating to the vehicle from the vehicle using a first acquisition method set in advance; Acquire second data, which is data relating to the vehicle, from a source other than the vehicle by a second acquisition method set in advance; generating, for the acquired first data, first standardized data including a first data ID for identifying the first data and a first standard data value obtained by normalizing a value of the first data; and generating, for the acquired second data, second standardized data including a second data ID for identifying the second data and a second standard data value obtained by normalizing a value of the second data; A data processing method for transmitting the first standardized data and the second standardized data when a preset data transmission condition is satisfied for each of the first standardized data and the second standardized data.
[0103] [Item 10] Computer, A first acquisition unit (5) configured to acquire first data relating to the vehicle from the vehicle in a first acquisition method set in advance; A second acquisition unit (3, 4) configured to acquire second data, which is data related to the vehicle, from a source other than the vehicle by a second acquisition method set in advance; a standardization processing unit (S10 to S360) configured to generate, for the first data acquired by the first acquisition unit, first standardized data including a first data ID for identifying the first data and a first standard data value obtained by normalizing a value of the first data, and to generate, for the second data acquired by the second acquisition unit, second standardized data including a second data ID for identifying the second data and a second standard data value obtained by normalizing a value of the second data; a data storage unit (7) configured to store the first standardized data and the second standardized data; and a data transmission unit configured to transmit the first standardized data and the second standardized data stored in the data storage unit when a preset data transmission condition is satisfied for each of the first standardized data and the second standardized data (S410 to S430); A data processing program that functions as a [Explanation of symbols]
[0104] REFERENCE SIGNS LIST 1... data processing device, 2... control unit, 3... QR code reader, 4... Wi-Fi communication unit, 5... BLE communication unit, 6... data receiving unit, 7... data storage unit, 8... external communication unit
Claims
1. A first acquisition unit (5) configured to acquire first data, which is data related to the vehicle, from the vehicle by a preset first acquisition method; A second acquisition unit (3, 4) configured to acquire second data, which is data related to outside the vehicle, from outside the vehicle by a preset second acquisition method; For the first data acquired by the first acquisition unit, generate first standardized data including a first data ID for identifying the first data and a first standard data value obtained by normalizing the value of the first data so that the same physical quantity has the same value regardless of the vehicle type and vehicle manufacturing company. For the second data acquired by the second acquisition unit, generate second standardized data including a second data ID for identifying the second data and a second standard data value obtained by normalizing the value of the second data so that the same physical quantity has the same value regardless of the vehicle type and vehicle manufacturing company. A normalization processing unit (S10 to S360) configured to perform such generation; A data storage unit (7) configured to store the first standardized data and the second standardized data; A data transmission unit (S410 to S430) configured to transmit the first standardized data and the second standardized data stored in the data storage unit when a preset data transmission condition is satisfied for each of the first standardized data and the second standardized data A data processing device (2) comprising the above components.
2. The data processing device according to claim 1, wherein The normalization processing unit determines whether each of the first data and the second data acquired by the first acquisition unit and the second acquisition unit is dynamic data or static data, and is configured to set type information indicating whether it is the dynamic data or the static data in the first standardized data and the second standardized data; The data transmission unit is configured to transmit the first standardized data and the second standardized data when a data transmission condition set according to the type information is satisfied for each of the first standardized data and the second standardized data.
3. The data processing device according to claim 2, wherein When the type information indicates the static data, the data transmission condition is a data processing device configured to transmit after the first standardized data or the second standardized data, which is the target of the data transmission condition, is generated.
4. The data processing device according to claim 2 or claim 3, When the type information indicates the dynamic data, the data transmission condition is a data processing device configured to transmit the first standardized data or the second standardized data, which is the target of the data transmission condition, every time a preset transmission period elapses.
5. The data processing device according to any one of claims 1 to 3, In the first data acquired by the first acquisition unit, a first raw data ID for identifying the first data is added, In the second data acquired by the second acquisition unit, a second raw data ID for identifying the second data is added, The normalization processing unit, For the first data acquired by the first acquisition unit, converts it into first common data including the first raw data ID and a first raw data value indicating the value of the first data, For the second data acquired by the second acquisition unit, converts it into second common data which is common data including the second raw data ID and a second raw data value indicating the value of the second data, Generates the first standardized data by normalizing the first raw data value included in the first common data, A data processing device configured to generate the second standardized data by normalizing the second raw data value included in the second common data.
6. The data processing device according to claim 5, The normalization processing unit is configured to determine whether the first data and the second data acquired by the first acquisition unit and the second acquisition unit are dynamic data or static data, and add type information indicating whether it is dynamic data or static data to the first common data and the second common data.
7. The data processing device according to claim 3, The data transmission condition is a data processing device configured to transmit every time the first standardized data or the second standardized data, which is the target of the data transmission condition, is generated.
8. The data processing device according to claim 3, The data transmission condition is a data processing device that is set to prohibit transmission even when the first standardized data or the second standardized data, which is the target of the data transmission condition, is generated, as long as the data values included in the first standardized data or the second standardized data have not changed.
9. A data processing method executed by a data processing device, acquiring first data, which is data related to the vehicle, from the vehicle by a preset first acquisition method, acquiring second data, which is data related to entities other than the vehicle, from entities other than the vehicle by a preset second acquisition method, generating first standardized data for the acquired first data, including a first data ID for identifying the first data and a first standard data value obtained by normalizing the value of the first data so that the same physical quantity has the same value regardless of the vehicle type and vehicle manufacturing company, and generating second standardized data for the acquired second data, including a second data ID for identifying the second data and a second standard data value obtained by normalizing the value of the second data so that the same physical quantity has the same value regardless of the vehicle type and vehicle manufacturing company, A data processing method for transmitting the first standardized data and the second standardized data when a preset data transmission condition is satisfied for each of the first standardized data and the second standardized data.
10. A computer, a first acquisition unit (5) configured to acquire first data, which is data related to the vehicle, from the vehicle by a preset first acquisition method, a second acquisition unit (3, 4) configured to acquire second data, which is data related to entities other than the vehicle, from entities other than the vehicle by a preset second acquisition method, a normalization processing unit (S10 to S360) configured to generate first standardized data for the first data acquired by the first acquisition unit, including a first data ID for identifying the first data and a first standard data value obtained by normalizing the value of the first data so that the same physical quantity has the same value regardless of the vehicle type and vehicle manufacturing company, and generate second standardized data for the second data acquired by the second acquisition unit, including a second data ID for identifying the second data and a second standard data value obtained by normalizing the value of the second data so that the same physical quantity has the same value regardless of the vehicle type and vehicle manufacturing company A data storage unit (7) configured to store the first standardized data and the second standardized data, and For each of the first standardized data and the second standardized data, when a preset data transmission condition is satisfied, a data transmission unit (S410 to S430) configured to transmit the first standardized data and the second standardized data stored in the data storage unit A data processing program for causing the system to function as described above.