Center, management system, management method, and management program

Abstract

A center (3) is provided with a vehicle-side unit (110) and a service-side unit (120). The vehicle-side unit repeatedly acquires from each of a plurality of onboard devices (2) a vehicle data group formed in a first data structure wherein a plurality of vehicle data are classified into categories. For each vehicle the vehicle-side unit creates, as a shadow (114), a vehicle data group to which vehicle identification information and timing identification information are appended, and stores the shadow in a shadow storage unit (112). After a request is received from a service providing unit (4) is received, the service-side unit instructs the vehicle-side unit to acquire designated data about a prescribed vehicle for a prescribed period of time from the shadow storage unit, on the basis of the request.

Description

Cross - reference to related applications

[0001] This international application claims priority based on Japanese Patent Application No. 2021 - 110901 filed with the Japan Patent Office on July 2, 2021, and incorporates the entire contents of Japanese Patent Application No. 2021 - 110901 by reference into this international application.

Technical Field

[0002] This disclosure relates to a center for managing vehicle data, a management system, a management method, and a management program.

Background Art

[0003] Patent Document 1 describes a digital twin simulation that reproduces the state of a real - world vehicle in a virtual space by collecting vehicle data from the vehicle.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

[0005] The vehicle data that can be obtained by CAN communication does not have a form that is easy for users who utilize the vehicle data to use. This is because, for example, the data that can be obtained from the CAN communication frame varies depending on the vehicle manufacturer, vehicle type, and shipping date, etc. As a result of the inventors' detailed examination, it has been found that users who want to handle vehicle data need specialized knowledge such as the structure of the CAN communication frame and the bus through which the data flows, and there is a problem that they cannot easily access the vehicle data.

[0006] This disclosure facilitates the utilization of vehicle data.

[0007] One aspect of the present disclosure is a center including a vehicle-side unit and a service-side unit.

[0008] The vehicle-side unit is communicably connected to a plurality of in-vehicle devices mounted on each of a plurality of vehicles. The service-side unit is communicable with a service providing unit.

[0009] The vehicle-side unit includes a shadow creation unit. The shadow creation unit is configured to repeatedly acquire a vehicle data group formed in a first data structure in which a plurality of vehicle data are classified into each category from each of the plurality of in-vehicle devices. Then, for each vehicle, the shadow creation unit creates a vehicle data group to which vehicle identification information for identifying the vehicle and timing identification information for identifying the timing at which the vehicle data was acquired are attached as a shadow, and stores it in a shadow storage unit provided in the vehicle-side unit in the form of the first data structure.

[0010] The service-side unit includes an instruction unit. When the instruction unit receives, from the service providing unit, a request for instructing the acquisition of corresponding vehicle data by designating specific vehicle data or a specific category among the plurality of vehicle data constituting the vehicle data group as designated data, the instruction unit instructs the vehicle-side unit to acquire the designated data of the predetermined vehicle at the predetermined time from the shadow storage unit of the vehicle-side unit based on the request.

[0011] In the center of the present disclosure configured as described above, the shadow has a data structure classified into a plurality of categories, and a plurality of vehicle data are organized in a hierarchical structure. Therefore, the center of the present disclosure can access the plurality of vehicle data constituting the shadow by the data name of specific vehicle data or the category name of a specific category, and can facilitate the use of vehicle data.

[0012] Another aspect of the present disclosure is a management system (1) including a plurality of in-vehicle devices mounted on each of a plurality of vehicles to acquire vehicle data from the vehicles, and a center for managing the vehicle data. The center includes a vehicle-side unit and a service-side unit. The vehicle-side unit includes a shadow creation unit. The service-side unit includes an instruction unit.

[0013] The management system of the present disclosure configured as described above is a system including the center of the present disclosure, and can obtain the same effects as the center of the present disclosure.

[0014] Yet another aspect of the present disclosure is a management method executed by a center including a vehicle-side unit and a service-side unit.

[0015] The vehicle-side unit repeatedly acquires a vehicle data group formed in a first data structure in which a plurality of vehicle data are classified into each category from each of the plurality of in-vehicle devices, and for each vehicle, vehicle identification information for identifying the vehicle and timing identification information for identifying the timing at which the vehicle data is acquired are attached to create a vehicle data group as a shadow, and stores it in a shadow storage unit provided in the vehicle-side unit in the form of the first data structure.

[0016] When the service-side unit receives, from the service providing unit, a request for instructing acquisition of specific vehicle data or a specific category as designated data among the plurality of vehicle data constituting the vehicle data group, the service-side unit instructs the vehicle-side unit to acquire the designated data of the predetermined vehicle at the predetermined time from the shadow storage unit of the vehicle-side unit based on the request.

[0017] The management method of the present disclosure is a method executed by the center of the present disclosure, and by executing this method, the same effects as the center of the present disclosure can be obtained.

[0018] Yet another aspect of the present disclosure is a management program that causes a computer of a center including a vehicle-side unit and a service-side unit to function as a shadow creation unit and an instruction unit.

[0019] The computer controlled by the management program of the present disclosure can form part of the center of the present disclosure and can obtain the same effects as the center of the present disclosure.

Brief Description of the Drawings

[0020]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Embodiments for Carrying Out the Invention

[0021] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings.

[0022] As shown in FIG. 1, the mobility IoT system 1 of the present embodiment includes a plurality of data collection devices 2, a management center 3, and a service providing server 4. IoT is an abbreviation for Internet of Things.

[0023] The data collection device 2 is mounted on a vehicle and has a function of performing data communication with the management center 3 via a wide area wireless communication network NW.

[0024] The management center 3 is a device that manages the mobility IoT system 1. The management center 3 has a function of performing data communication with a plurality of data collection devices 2 and the service providing server 4 via the wide area wireless communication network NW.

[0025] The service providing server 4 is, for example, a server installed to provide a service for managing the operation of a vehicle. Note that the mobility IoT system 1 may include a plurality of service providing servers with different service contents. These service providing servers 4 may be configured on-premises, may be configured in the cloud, or may be configured as the same server physically as the management center 3.

[0026] As shown in FIG. 2, the data collection device 2 includes a microcomputer 11, a vehicle interface (hereinafter referred to as vehicle I / F) 12, a communication unit 13, and a storage unit 14.

[0027] The microcomputer 11 includes a first core 21, a second core 22, a ROM 23, a RAM 24, a flash memory 25, an input / output unit 26, and a bus 27.

[0028] The various functions of the microcomputer 11 are realized by the first core 21 and the second core 22 executing a program stored in a non-transitory tangible recording medium. In this example, the ROM 23 corresponds to the non-transitory tangible recording medium storing the program. Further, by executing this program, a method corresponding to the program is executed.

[0029] Note that part or all of the functions executed by the first core 21 and the second core 22 may be configured hardware-wise by one or a plurality of ICs or the like.

[0030] The flash memory 25 is a non-volatile memory capable of data rewriting. The flash memory 25 includes a standardized vehicle data storage unit 25a that stores standardized vehicle data, which will be described later.

[0031] The input / output unit 26 is a circuit for enabling data input / output between the outside of the microcomputer 11 and the first core 21 and the second core 22.

[0032] The bus 27 connects the first core 21, the second core 22, the ROM 23, the RAM 24, the flash memory 25, and the input / output unit 26 so that data can be input / output to and from each other.

[0033] The vehicle I / F 12 is an input / output circuit for enabling signal input / output between the electronic control devices and sensors mounted on the vehicle.

[0034] The vehicle I / F 12 includes a power supply voltage input port, a general-purpose input / output port, a CAN communication port, an Ethernet communication port, and the like.

[0035] The power supply voltage input port includes a +B voltage port to which a +B voltage is input and an IG voltage port to which an IG voltage is input. Note that the vehicle I / F 12 includes a DC / DC converter and a protection circuit including a Zener diode. Thereby, the power supply voltage input port is configured to be capable of corresponding to both the input of a 12V vehicle voltage and the input of a 48V vehicle voltage.

[0036] The CAN communication port is a port for transmitting and receiving data according to the CAN communication protocol. The Ethernet communication port is a port for transmitting and receiving data based on the Ethernet communication protocol. CAN is the abbreviation of Controller Area Network. CAN is a registered trademark. Ethernet is a registered trademark.

[0037] Other electronic control devices mounted on the vehicle are connected to the CAN communication port and the Ethernet communication port. Thereby, the data collection device 2 can transmit and receive communication frames with other electronic control devices.

[0038] The communication unit 13 performs data communication with the management center 3 via the wide area wireless communication network NW.

[0039] The storage unit 14 is a storage device for storing various data.

[0040] As shown in FIG. 20, one ECU 210, a plurality of ECUs 220, a plurality of ECUs 230, an in-vehicle communication device 240, and an in-vehicle communication network 250 are mounted on the vehicle. ECU is the abbreviation of Electronic Control Unit.

[0041] The ECU 210 realizes coordinated control for the entire vehicle by coordinating a plurality of ECUs 220.

[0042] The ECU 220 is provided for each domain classified by the functions in the vehicle, and mainly executes the control of a plurality of ECUs 230 existing within that domain. Each ECU 220 is connected to the subordinate ECU 230 via a separately provided lower-layer network (for example, CAN). The ECU 220 has a function of centrally managing access rights to the subordinate ECU 230 and performing user authentication and the like. The domains are, for example, the power train, the body, the chassis, and the cockpit, etc.

[0043] The ECUs 230 connected to the ECU 220 belonging to the domain of the power train include, for example, an ECU 230 that controls the engine, an ECU 230 that controls the motor, and an ECU 230 that controls the battery, etc.

[0044] The ECUs 230 connected to the ECU 220 belonging to the domain of the body include, for example, an ECU 230 that controls the air conditioner and an ECU 230 that controls the doors, etc.

[0045] The ECUs 230 connected to the ECU 220 belonging to the chassis domain include, for example, an ECU 230 that controls the brakes and an ECU 230 that controls the steering, etc.

[0046] The ECUs 230 connected to the ECU 220 belonging to the cockpit domain include, for example, an ECU 230 that controls the display of the meter and navigation, and an ECU 230 that controls the input device operated by the vehicle occupants, etc.

[0047] The vehicle external communication device 240 performs data communication with a communication device outside the vehicle (for example, a cloud server) via a wide area wireless communication network NW.

[0048] The in-vehicle communication network 250 includes CAN FD and Ethernet. CAN FD is the abbreviation of CAN with Flexible Data Rate. CAN FD bus-connects the ECU 210, each ECU 220, and the vehicle external communication device 240. Ethernet individually connects between the ECU 210, each ECU 220, and the vehicle external communication device 240.

[0049] The ECU 210 is an electronic control device mainly configured around a microcomputer including a CPU 210a, a ROM 210b, a RAM 210c, etc. Various functions of the microcomputer are realized by the CPU 210a executing a program stored in a non-transitory tangible recording medium. In this example, the ROM 210b corresponds to the non-transitory tangible recording medium storing the program. Further, by executing this program, a method corresponding to the program is executed. Note that part or all of the functions executed by the CPU 210a may be configured hardware-wise by one or a plurality of ICs or the like. Also, the number of microcomputers constituting the ECU 210 may be one or more.

[0050] The ECU 220, the ECU 230, and the vehicle external communication device 240 are all electronic control devices mainly configured around a microcomputer including a CPU, a ROM, a RAM, etc., similar to the ECU 210. Also, the number of microcomputers constituting the ECU 220, the ECU 230, and the vehicle external communication device 240 may be one or more. The ECU 220 is an ECU that supervises one or more ECUs 230, and the ECU 210 is an ECU that supervises one or more ECUs 220 or that supervises the ECUs 220 and 230 of the entire vehicle including the vehicle external communication device 240.

[0051] The data collection device 2 is connected to the ECU 210 so as to be capable of data communication with the ECU 210. That is, the data collection device 2 receives the information of the ECUs 210, 220, and 230 via the ECU 210. Also, the data collection device 2 transmits requests regarding vehicle control to the ECU 210 or transmits them to the ECUs 220 and 230 via the ECU 210.

[0052] As shown in FIG. 3, the management center 3 includes a control unit 31, a communication unit 32, and a storage unit 33.

[0053] The control unit 31 is an electronic control device mainly composed of a microcomputer including a CPU 41, a ROM 42, a RAM 43, etc. Various functions of the microcomputer are realized by the CPU 41 executing a program stored in a non-transitory tangible recording medium. In this example, the ROM 42 corresponds to the non-transitory tangible recording medium storing the program. Further, by executing this program, a method corresponding to the program is executed. Note that part or all of the functions executed by the CPU 41 may be configured hardware-wise by one or a plurality of ICs or the like. Also, the number of microcomputers constituting the control unit 31 may be one or plural.

[0054] The communication unit 32 performs data communication with a plurality of data collection devices 2 and service providing servers 4 via a wide area wireless communication network NW.

[0055] The storage unit 33 is a storage device for storing various data.

[0056] As shown in FIG. 4, the data collection device 2 includes a first unit 101 as a functional block realized by the first core 21 executing a program stored in the ROM 23. The data collection device 2 includes a second unit 102 as a functional block realized by the second core 22 executing a program stored in the ROM 23.

[0057] The first unit 101 includes a real-time operating system (hereinafter, RTOS) 103 and a first application 104.

[0058] The first application 104 executes various processes for controlling the vehicle. The first application 104 is configured to be able to access the standardized vehicle data storage unit 25a of the flash memory 25 and refer to the standardized vehicle data in order to execute various processes for controlling the vehicle.

[0059] The RTOS 103 manages the first application 104 so as to ensure the real-time nature of the processes by the first application 104.

[0060] The second unit 102 includes a general-purpose operating system (hereinafter, GPOS) 105 and a second application 106.

[0061] The second application 106 executes processes related to the services provided by the service providing server 4. The second application 106 is configured to be able to access the standardized vehicle data storage unit 25a of the flash memory 25 and refer to the standardized vehicle data in order to execute processes related to the services.

[0062] The GPOS 105 is basic software installed in the data collection device 2 for operating various applications, and manages the second application 106.

[0063] Note that the data collection device 2 may realize the operation in the RTOS 103 and the operation in the GPOS 105 using a hypervisor on a single-core microcomputer.

[0064] As shown in FIG. 5, the management center 3 is a functional block realized by the CPU 41 executing a program stored in the ROM 42, and includes a vehicle-side unit 110 and a service-side unit 120. The side closer to the access to the vehicle is the vehicle-side unit 110, and the side closer to the access from the service providing server 4 is the service-side unit 120. The functional block is divided into two, and these two functional blocks are configured to be loosely coupled.

[0065] The method for realizing these elements that make up the management center 3 is not limited to software, and for some or all of these elements, one or more pieces of hardware may be used for realization. For example, when the above function is realized by an electronic circuit that is hardware, the electronic circuit may be realized by a digital circuit including a number of logic circuits, an analog circuit, or a combination thereof.

[0066] The vehicle-side unit 110 manages access to the vehicle and data received from the vehicle. The vehicle-side unit 110 includes a mobility gateway (hereinafter, mobility GW) 111. The mobility GW 111 has the function of relaying an access request to the vehicle to the vehicle, and also has the function of managing data received from the vehicle.

[0067] And the mobility GW 111 includes a shadow storage unit 112 and a vehicle control unit 113. The shadow storage unit 112 stores a shadow 114 that stores vehicle data for each vehicle equipped with the data collection device 2. The shadow 114 indicates a vehicle data group of a certain vehicle. The vehicle control unit 113 has the function of controlling the vehicle equipped with the data collection device 2 based on an instruction from the service providing server 4.

[0068] The service-side unit 120 receives requests from the service providing server 4 and provides vehicle data. The service-side unit 120 includes a data management unit 121 and an access API 122. API is the abbreviation of Application Programming Interface.

[0069] The data management unit 121 has the function of managing a digital twin 123, which is a virtual space for providing vehicle access that does not depend on changes in the connection state of the vehicle. The data management unit 121 manages data necessary for accessing the vehicle data managed by the vehicle-side unit 110.

[0070] The access API 122 is a standard interface for the service providing server 4 to access the mobility GW 111 and the data management unit 121. The access API 122 provides an API for the service providing server 4 to access the vehicle and obtain vehicle data.

[0071] Next, the processing executed by the vehicle I / F 12 will be described.

[0072] When the vehicle I / F 12 receives a communication frame, it determines the communication protocol of the communication frame based on the communication port that received the communication frame. Specifically, for example, when the vehicle I / F 12 receives a communication frame on the CAN communication port, it determines that the communication protocol of the received communication frame is the CAN communication protocol. Also, for example, when the vehicle I / F 12 receives a communication frame on the Ethernet communication port, it determines that the communication protocol of the received communication frame is the Ethernet communication protocol.

[0073] Then, the vehicle I / F 12 determines whether the communication frame is necessary based on the identification information of the communication frame, and if it determines that it is necessary, it outputs the received communication frame to the first unit 101.

[0074] As shown in FIG. 6, the CAN frame is composed of a start of frame, an arbitration field, a control field, a data field, a CRC field, an ACK field, and an end of frame. Note that the arbitration field is composed of an 11-bit or 29-bit identifier (i.e., ID) and a 1-bit RTR bit.

[0075] Also, the 11-bit identifier used in CAN communication is called a CAN ID. The CAN ID is preset based on the content of the data included in the CAN frame, the transmission source of the CAN frame, the destination of the CAN frame, and the like.

[0076] The data field is a payload composed of first data, second data, third data, fourth data, fifth data, sixth data, seventh data, and eighth data, each of which is 8 bits (i.e., 1 byte). Hereinafter, each of the first to eighth data of the data field is also referred to as CAN data.

[0077] Therefore, when the vehicle I / F 12 receives a CAN frame, it determines whether the received CAN frame is necessary based on the CAN ID.

[0078] Next, the processing executed by the first unit 101 will be described.

[0079] When the first unit 101 acquires the communication frame output from the vehicle I / F 12, it extracts identification information and a payload from the communication frame, creates standard format data composed of the identification information and the payload, and stores the created standard format data in the flash memory 25. For example, when the first unit 101 acquires a CAN frame, it creates standard format data composed of the CAN ID and the first to eighth data. Here, the identification information (second identification information) included in the standard format data does not have to be the same as the identification information (first identification information) extracted from the communication frame. For example, unique second identification information may be generated using the first identification information, or second identification information may be generated by converting using the identification information of the communication protocol and the first identification information.

[0080] Note that when standard format data including the same identification information as the created standard format data is already stored in the flash memory 25, the first unit 101 updates the standard format data by overwriting and storing it in the standard format data. That is, the flash memory 25 stores the latest standard format data regarding the same identification information.

[0081] Next, the procedure of the data normalization process executed by the second unit 102 will be described. The data normalization process is a process that is repeatedly executed during the operation of the microcomputer 11.

[0082] When the data normalization process is executed, as shown in FIG. 7, the second core 22 first determines, at S10, whether a preset normalization execution condition is satisfied.

[0083] The normalization execution condition is that at least any one of a first high-frequency normalization condition, a second high-frequency normalization condition, a third high-frequency normalization condition, a first low-frequency normalization condition, a second low-frequency normalization condition, an event normalization condition, and an invariant normalization condition described later is satisfied.

[0084] The first high-frequency normalization condition is that a preset first high-frequency normalization period (for example, 500 ms in this embodiment) has elapsed.

[0085] The second high-frequency normalization condition is that a preset second high-frequency normalization period (for example, 2 s in this embodiment) has elapsed.

[0086] The third high-frequency normalization condition is that a preset third high-frequency normalization period (for example, 4 s in this embodiment) has elapsed.

[0087] The first low-frequency normalization condition is that a preset first low-frequency normalization period (for example, 30 s in this embodiment) has elapsed.

[0088] The second low-frequency normalization condition is that a preset second low-frequency normalization period (for example, 300 s in this embodiment) has elapsed.

[0089] The event normalization condition is that a preset event normalization period (for example, 12 hours in this embodiment) has elapsed.

[0090] The invariant normalization condition is that the current processing of S10 is the first processing of S10 after the microcomputer 11 is started.

[0091] Here, when the normalization execution condition is not satisfied, the second core 22 ends the data normalization process. On the other hand, when the normalization execution condition is satisfied, the second core 22 acquires, in S20, the standard format data corresponding to the satisfied normalization condition among the seven normalization conditions constituting the normalization execution condition from the flash memory 25. For example, when the second high-frequency normalization condition is satisfied, the second core 22 acquires, in S20, the standard format data corresponding to the second high-frequency normalization condition.

[0092] Then, the second core 22 divides, in S30, the data included in the standard format data. For example, since the standard format data generated from the CAN frame is composed of the CANID and the first to eighth data, the second core 22 divides the first to eighth data byte by byte and extracts eight CAN data.

[0093] Furthermore, the second core 22 refers to the vehicle data conversion table 23a stored in the ROM 23 in S40 and converts each extracted data divided in S30 into control labels and vehicle data. The control label is identification information indicating the type of the vehicle data.

[0094] The vehicle data conversion table 23a includes normalization information and semantic information.

[0095] The normalization information is information for normalizing the extracted data so that the same physical quantity has the same value regardless of the vehicle type and vehicle manufacturing company.

[0096] The semantic information is information (for example, arithmetic expressions, conversion tables) for converting the normalized vehicle data into meaningful vehicle data. The vehicle data before normalization may also be used. Semantic conversion includes newly generating information that was not in the payload of the communication frame using arithmetic expressions and the like.

[0097] As shown in FIG. 8, the normalization information of the vehicle data conversion table 23a includes, as setting items, for example, "CANID", "ECU", "Position", "DLC", "Unique Label", "Resolution", "Offset", and "Unit".

[0098] "ECU" is identification information indicating the ECU that is the transmission source of the CAN frame. For example, "ENG" indicates that it is the engine ECU.

[0099] "Position" is information indicating the position of the CAN data within the data field (for example, the bit position). "DLC" is information indicating the data length. DLC is the abbreviation of Data Length Code. That is, data for "DLC" bits is extracted from the "Position" of the data field.

[0100] "Unique Label" is information indicating a control label. For example, "ETHA" indicates the intake air temperature, and "NE1" indicates the engine speed. "Resolution" is information indicating the value per bit. "Offset" indicates the offset amount of the value of the data. "Unit" indicates the unit of the data.

[0101] Therefore, data corresponding to the "Unique Label" is extracted from the standard format data by "CANID", "ECU", "Position", "DLC", and "Unique Label". Further, the extracted data is converted into vehicle data represented by "Resolution", "Offset", and "Unit".

[0102] Further, the semantic information in the vehicle data conversion table 23a is, for example, as shown in FIG. 8, a conversion formula that converts from the "steering movement angle" with a control label of "SSA" to the "steering angle" by subtracting the "steering zero point" with a control label of "SSAZ". Thereby, vehicle data representing the "steering movement angle" and vehicle data representing the "steering zero point" are converted into vehicle data representing the "steering angle" having the meaning of "steering amount from the reference position". For the newly generated vehicle data by semantic conversion, "unique label", "unit", etc. are assigned.

[0103] Also, the vehicle data conversion table 23a is provided for the data of the "shift position", which is a predetermined control label. By the vehicle data conversion table 23a, the data indicating "P range", "N range", "D range", and "R range" are respectively converted.

[0104] When the process of S40 ends, as shown in FIG. 7, the second core 22 hierarchizes the converted vehicle data and stores it in the flash memory 25 at S50. Specifically, the second core 22 stores the converted vehicle data in the corresponding area of the standardized vehicle data storage unit 25a provided in the flash memory 25.

[0105] The standardized vehicle data storage unit 25a stores standardized vehicle data configured by hierarchizing vehicle data.

[0106] The standardized vehicle data is created for each vehicle (that is, for each data collection device 2) and has a plurality of hierarchical structures. In the standardized vehicle data, one or a plurality of items are set for each of the plurality of layers. For example, as shown in FIG. 9, the standardized vehicle data includes, as items set in the topmost first layer, "attribute information", "powertrain", "energy", "ADAS / AD", "body", "multimedia", and "others". ADAS is an abbreviation for Advanced Driver Assistance System. AD is an abbreviation for Autonomous Driving. These "attribute information", "powertrain", and "energy", etc. correspond to categories.

[0107] Also, each vehicle data includes, as items, "unique label", "ECU", "data type", "data size", "data value", and "data unit". "Unique label" and "ECU" are as described above. "Data type", "data size", and "data unit" indicate the type, size, and unit related to the numerical value indicated by the "data value", respectively.

[0108] As shown in FIG. 10, the standardized vehicle data includes at least a second layer and a third layer in addition to the first layer. The second layer is the layer immediately below the first layer, and the third layer is the layer immediately below the second layer. The standardized vehicle data is an item set in the above-described normalization and semantic processing. The standardized vehicle data has a data structure with a hierarchical structure.

[0109] For example, "attribute information", which is an item in the first layer, includes, as items in the second layer, "vehicle identification information", "vehicle attribute", "transmission configuration", "firmware version", and the like. "Vehicle identification information" is a category name indicating information that can uniquely identify a vehicle. "Vehicle attribute" is a category name indicating the type of vehicle. "Transmission information" is a category name indicating information related to the transmission. "Firmware version" is a category name indicating information related to the vehicle's firmware.

[0110] Also, "powertrain", which is an item in the first layer, is a category name indicating powertrain information, and includes, as items in the second layer, "accelerator pedal", "engine", "engine oil", and the like. The "accelerator pedal" includes one or more vehicle data such as the state and opening degree of the accelerator pedal. The "engine" includes one or more individual vehicle data such as the state and rotation speed of the engine. These second layers also correspond to categories. The same applies to other items in the first layer.

[0111] Further, "Energy", which is an item in the first layer, is a category name indicating energy information, and as items in the second layer, it includes "Battery Status", "Battery Configuration", "Fuel", etc.

[0112] Also, "Vehicle Identification Information", which is an item in the second layer, includes "Vehicle Identification Number", "Body Number", and "License Plate" as items in the third layer. These items in the third layer include one or more individual vehicle data (also referred to as items).

[0113] Also, "Vehicle Attributes", which is an item in the second layer, includes "Brand Name", "Model", "Manufacturing Year", etc. as items in the third layer.

[0114] Also, "Transmission Configuration", which is an item in the second layer, includes "Transmission Type" as an item in the third layer. These items in the third layer are also referred to as items and are the smallest units of the data structure.

[0115] For example, when the control label of the converted vehicle data in the second core 22 is "Vehicle Identification Information", the converted vehicle data is stored in the storage area in the standardized vehicle data storage unit 25a where the first layer is "Attribute Information", the second layer is "Vehicle Identification Information", and the third layer is "Vehicle Identification Number".

[0116] Next, the procedure for the data collection device 2 to create standardized vehicle data will be described using the sequence diagram shown in FIG. 11.

[0117] As shown by arrow L11, when the vehicle I / F 12 acquires vehicle data from the vehicle, the vehicle I / F 12 performs communication protocol determination as shown by arrow L12. Further, the vehicle I / F 12 filters unnecessary vehicle data as shown by arrow L13 and outputs the necessary vehicle data to the first unit 101 as shown by arrow L14.

[0118] When the first unit 101 acquires vehicle data from the vehicle I / F 12, as indicated by the arrow L15, it converts the vehicle data into a standard format, and as indicated by the arrow L16, stores the vehicle data converted into the standard format in the flash memory 25.

[0119] When the second unit 102 acquires the vehicle data converted into the standard format from the flash memory 25, as indicated by the arrow L17, it converts the acquired vehicle data, as indicated by the arrow L18. Further, the second unit 102 structures the converted data to create standardized vehicle data, as indicated by the arrow L19.

[0120] Next, the procedure of the data transmission process executed by the data collection device 2 will be described. The data transmission process is a process that is repeatedly executed during the operation of the microcomputer 11.

[0121] When the data transmission process is executed, as shown in FIG. 12, the second core 22 first determines, at S110, whether or not a preset first high-frequency transmission condition is satisfied. The first high-frequency transmission condition is that, with the current time being tx and the transmission interval setting value (for example, 500 ms in this embodiment) being T, mod{tx / (T×2)} is 0.

[0122] Here, when the first high-frequency transmission condition is not satisfied, the second core 22 proceeds to S130. On the other hand, when the first high-frequency transmission condition is satisfied, the second core 22 extracts, at S120, the vehicle data set as the first high-frequency data from the vehicle data constituting the standardized vehicle data from the standardized vehicle data storage unit 25a, transmits it to the management center 3, and proceeds to S130.

[0123] Note that, in addition to the above-described first high-frequency data, the vehicle data constituting the standardized vehicle data is set to any one of the second high-frequency data, third high-frequency data, fourth high-frequency data, fifth high-frequency data, sixth high-frequency data, first low-frequency data, second low-frequency data, third low-frequency data, fourth low-frequency data, event data, and invariant data, which will be described later. And a transmission frequency setting table that defines to which of the first, second, third, fourth, fifth, and sixth high-frequency data, the first, second, third, and fourth low-frequency data, event data, and invariant data each vehicle data is set is stored in advance in the flash memory 25.

[0124] When shifting to S130, the second core 22 determines whether or not a preset second high-frequency transmission condition is satisfied. The second high-frequency transmission condition is that mod{(tx + T) / (T × 2)} is 0.

[0125] Here, when the second high-frequency transmission condition is not satisfied, the second core 22 shifts to S150. On the other hand, when the second high-frequency transmission condition is satisfied, the second core 22 extracts, at S140, the vehicle data set to the second high-frequency data from among the vehicle data constituting the standardized vehicle data from the standardized vehicle data storage unit 25a, transmits it to the management center 3, and shifts to S150.

[0126] When shifting to S150, the second core 22 determines whether or not a preset third high-frequency transmission condition is satisfied. The third high-frequency transmission condition is that mod{tx / (T × 8)} is 0.

[0127] Here, when the third high-frequency transmission condition is not satisfied, the second core 22 shifts to S170. On the other hand, when the third high-frequency transmission condition is satisfied, the second core 22 extracts, at S160, the vehicle data set to the third high-frequency data from among the vehicle data constituting the standardized vehicle data from the standardized vehicle data storage unit 25a, transmits it to the management center 3, and shifts to S170.

[0128] When shifting to S170, the second core 22 determines whether a preset fourth high-frequency transmission condition is satisfied. The fourth high-frequency transmission condition is that mod{(tx + T) / (T × 8)} is 0.

[0129] Here, when the fourth high-frequency transmission condition is not satisfied, the second core 22 shifts to S190. On the other hand, when the fourth high-frequency transmission condition is satisfied, the second core 22 extracts, at S180, the vehicle data set as the fourth high-frequency data from among the vehicle data constituting the standardized vehicle data from the standardized vehicle data storage unit 25a, transmits it to the management center 3, and then shifts to S190.

[0130] When shifting to S190, the second core 22 determines whether a preset fifth high-frequency transmission condition is satisfied. The fifth high-frequency transmission condition is that mod{tx / (T × 16)} is 0.

[0131] Here, when the fifth high-frequency transmission condition is not satisfied, the second core 22 shifts to S210. On the other hand, when the fifth high-frequency transmission condition is satisfied, the second core 22 extracts, at S200, the vehicle data set as the fifth high-frequency data from among the vehicle data constituting the standardized vehicle data from the standardized vehicle data storage unit 25a, transmits it to the management center 3, and then shifts to S210.

[0132] When shifting to S210, the second core 22 determines whether a preset sixth high-frequency transmission condition is satisfied. The sixth high-frequency transmission condition is that mod{(tx + T) / (T × 16)} is 0.

[0133] Here, when the sixth high-frequency transmission condition is not satisfied, the second core 22 shifts to S230. On the other hand, when the sixth high-frequency transmission condition is satisfied, the second core 22 extracts, at S180, the vehicle data set as the sixth high-frequency data from among the vehicle data constituting the standardized vehicle data from the standardized vehicle data storage unit 25a, transmits it to the management center 3, and then shifts to S230.

[0134] When shifting to S230, the second core 22 determines whether a preset first low-frequency transmission condition is satisfied. The first low-frequency transmission condition is that mod{tx / (T×120)} is 0.

[0135] Here, when the first low-frequency transmission condition is not satisfied, the second core 22 shifts to S250. On the other hand, when the first low-frequency transmission condition is satisfied, the second core 22 extracts, from the vehicle data constituting the standardized vehicle data, the vehicle data set as the first low-frequency data from the standardized vehicle data storage unit 25a at S240, transmits it to the management center 3, and then shifts to S250.

[0136] When shifting to S250, as shown in FIG. 13, the second core 22 determines whether a preset second low-frequency transmission condition is satisfied. The second low-frequency transmission condition is that mod{(tx + T) / (T×120)} is 0.

[0137] Here, when the second low-frequency transmission condition is not satisfied, the second core 22 shifts to S270. On the other hand, when the second low-frequency transmission condition is satisfied, the second core 22 extracts, from the vehicle data constituting the standardized vehicle data, the vehicle data set as the second low-frequency data from the standardized vehicle data storage unit 25a at S260, transmits it to the management center 3, and then shifts to S270.

[0138] When shifting to S270, the second core 22 determines whether a preset third low-frequency transmission condition is satisfied. The third low-frequency transmission condition is that mod{tx / (T×1200)} is 0.

[0139] Here, when the third low-frequency transmission condition is not satisfied, the second core 22 shifts to S290. On the other hand, when the third low-frequency transmission condition is satisfied, the second core 22 extracts, from the vehicle data constituting the standardized vehicle data, the vehicle data set as the third low-frequency data from the standardized vehicle data storage unit 25a at S280, transmits it to the management center 3, and then shifts to S290.

[0140] When transitioning to S290, the second core 22 determines whether a preset fourth low-frequency transmission condition is satisfied. The fourth low-frequency transmission condition is that mod{(tx + T) / (T × 1200)} is 0.

[0141] Here, if the fourth low-frequency transmission condition is not satisfied, the second core 22 transitions to S310. On the other hand, if the fourth low-frequency transmission condition is satisfied, the second core 22 extracts, from the vehicle data constituting the standardized vehicle data, the vehicle data set as the fourth low-frequency data from the standardized vehicle data storage unit 25a at S300, transmits it to the management center 3, and transitions to S310.

[0142] When transitioning to S310, the second core 22 determines whether a preset event transmission condition is satisfied. The event transmission condition is that mod{tx / (T × 172800)} is 0.

[0143] Here, if the event transmission condition is not satisfied, the second core 22 transitions to S330. On the other hand, if the event transmission condition is satisfied, the second core 22 extracts, from the vehicle data constituting the standardized vehicle data, the vehicle data set as the event data from the standardized vehicle data storage unit 25a at S320, transmits it to the management center 3, and transitions to S330.

[0144] When transitioning to S330, the second core 22 determines whether a preset invariant transmission condition is satisfied. The invariant transmission condition is that the processing of the current S330 is the first processing of S330 since the microcomputer 11 was started.

[0145] Here, when the invariant transmission condition is not satisfied, the second core 22 ends the data transmission process. On the other hand, when the event transmission condition is satisfied, the second core 22 extracts, at S340, the vehicle data set as invariant data from among the vehicle data constituting the standardized vehicle data from the standardized vehicle data storage unit 25a, transmits it to the management center 3, and ends the data transmission process.

[0146] As shown in FIG. 14, assuming that the time t0 is the first transmission timing, at the time t0, the first high-frequency data, the third high-frequency data, the fifth high-frequency data, the first low-frequency data, the third low-frequency data, the event data, and the invariant data are transmitted.

[0147] The first high-frequency data is transmitted every time 1000 ms has elapsed since the time t0. The second high-frequency data is transmitted at the time t1 when 500 ms has elapsed since the time t0, and thereafter, is transmitted every time 1000 ms has elapsed since the time t1.

[0148] The third high-frequency data is transmitted every time 4 s has elapsed since the time t0. The fourth high-frequency data is transmitted at the time t4 when 2 s has elapsed since the time t0, and thereafter, is transmitted every time 4 s has elapsed since the time t4.

[0149] The fifth high-frequency data is transmitted every time 8 s has elapsed since the time t0. The sixth high-frequency data is transmitted at the time when 4 s has elapsed since the time t0, and thereafter, is transmitted every time 8 s has elapsed.

[0150] The first low-frequency data is transmitted every time 1 minute has elapsed since the time t0. The second low-frequency data is transmitted at the time when 30 s has elapsed since the time t0, and thereafter, is transmitted every time 1 minute has elapsed.

[0151] The third low-frequency data is transmitted every time 10 minutes has elapsed since the time t0. The fourth low-frequency data is transmitted at the time when 5 minutes has elapsed since the time t0, and thereafter, is transmitted every time 10 minutes has elapsed.

[0152] Event data is transmitted every 12 hours after time t0 has elapsed.

[0153] The second application 106 of the second unit 102 performs analysis. When the second application 106 is, for example, a driving diagnosis application, the second application 106 detects "sudden steering", "sudden braking", and "sudden acceleration", or outputs analysis results such as "anxious driving" and "leisurely driving". Also, when the second application 106 is, for example, a parking monitoring application, the second application 106 detects "suspicious person discovery" and "entry into the vehicle".

[0154] The second application 106 transmits information indicating the above detection results or analysis results (hereinafter, analysis information) to the management center 3. The second application 106 transmits "events" such as the above "sudden steering" and "suspicious person discovery" to the management center 3 at the timing of detection. Also, the second application 106 transmits a "state" such as the above "anxious driving" to the management center 3 at the timing of determining the "state" or transmits it to the management center 3 periodically.

[0155] As shown in FIG. 15, the mobility GW 111 includes a shadow creation unit 115, a latest index creation unit 116, and a latest index storage unit 117.

[0156] Every time vehicle data or analysis information is transmitted from the data collection device 2, the shadow creation unit 115 updates the standardized vehicle data by overwriting the transmitted vehicle data or analysis information in the corresponding area of the structured standardized vehicle data.

[0157] When the shadow creation unit 115 updates the standardized vehicle data, if the analysis information regarding the above "status" has not been transmitted, the previous value is copied to the corresponding area corresponding to this "status". Also, when the shadow creation unit 115 updates the standardized vehicle data, if the analysis information regarding the above "event" has not been transmitted, the corresponding area corresponding to this "event" is set to "blank (no event)".

[0158] Then, the shadow creation unit 115 creates a new shadow 114 using the updated standardized vehicle data. And the shadow creation unit 115 stores the created shadow 114 in the shadow storage unit 112. As a result, in the shadow storage unit 112, a plurality of shadows 114 with different creation times are stored for each vehicle. One shadow 114 is a vehicle data group at a predetermined time of a certain vehicle and includes a vehicle data group represented by the standardized data structure shown in FIG. 10. Note that the timing at which the shadow creation unit 115 receives the structured standardized vehicle data via the communication unit 32 varies depending on the vehicle, but new shadow creation may be performed at the same timing for all vehicles. The shadow creation unit 115 may perform new shadow creation at a fixed cycle for all vehicles. In the shadow storage unit 112, past shadows 114 are accumulated for each vehicle. The shadows 114 that have passed a certain period may be sequentially deleted.

[0159] The shadow creation unit 115 receives the standardized vehicle data formed in a hierarchical structure from the data collection device 2. The shadow creation unit 115 may receive a part of the hierarchical structure data of the standardized vehicle data. When creating a new shadow 114 using the updated standardized vehicle data, the shadow creation unit 115 may attach arbitrary information such as a serial number and store it in the shadow storage unit 112.

[0160] As shown in FIG. 16, the shadow 114 includes a vehicle data storage unit 114a and a device data storage unit 114b.

[0161] The vehicle data storage unit 114a stores "object-id", "Shadow_version", and "mobility-data" as data related to the vehicle equipped with the data collection device 2.

[0162] "object-id" is a number for identifying the vehicle. "object-id" is assigned each time the vehicle to be managed is registered in the management center 3.

[0163] "Shadow_version" is a numerical value indicating the version of the shadow 114, and a timestamp indicating the creation time is set each time the shadow 114 is created.

[0164] "mobility-data" is the above standardized vehicle data.

[0165] The device data storage unit 114b stores "object-id", "update_time", "version", "power_status", "power_status_timestamp", and "notify_reason" as data related to the hardware and software installed in the data collection device 2. Data such as "version" and "power_status" are transmitted from the data collection device 2 separately from the standardized vehicle data when changes occur.

[0166] "object-id" is a character string for identifying the vehicle equipped with the data collection device 2 and functions as a partition key.

[0167] "update_time" is a numerical value indicating the update time.

[0168] "version" is a character string indicating the version of the hardware and software of the data collection device 2.

[0169] 「power_status」 is a character string indicating the system state (on, off, etc.) of the data collection device 2.

[0170] 「power_status_timestamp」 is a numerical value indicating the notification time of the system state.

[0171] 「notify_reason」 is a character string indicating the reason for notification.

[0172] In this way, the shadow 114 includes the information of the data collection device 2 in addition to the vehicle data group. Note that the device data storage unit 114b may store the information of the data collection device 2 separately in the ROM 42 without including it in the shadow 114. The device data storage unit 114b may store only the latest data in the ROM 42 instead of accumulating past data for each timestamp.

[0173] The latest index creation unit 116 acquires the latest shadow 114 for each vehicle from the shadow storage unit 112, and creates the latest index 118 (also referred to as the first index) using the acquired shadow 114. Then, the latest index creation unit 116 stores the created latest index 118 in the latest index storage unit 117. One latest index 118 is stored in the latest index storage unit 117 for each vehicle. An index is parameter information that serves as a key when searching for the shadow 114 from the shadow storage unit 112. The latest index creation unit 116 generates the latest index 118 by using the vehicle data acquired from the data collection device 2 or by generating data itself.

[0174] As shown in FIG. 17, the latest index 118 stores "gateway-id", "object-id", "shadow-version", "vin", "location-lon", "location-lat", and "location-alt".

[0175] The "gateway-id" is information for identifying the mobility GW111.

[0176] The "object-id" is information for identifying the vehicle equipped with the data collection device 2.

[0177] The "shadow-version" corresponds to the "Shadow_version" of the shadow 114. That is, the "shadow-version" is information for identifying the shadow 114, and a timestamp is set.

[0178] The "vin" is the registration number unique to the vehicle equipped with the data collection device 2.

[0179] The "location-lon" is information indicating the latitude where the vehicle equipped with the data collection device 2 exists.

[0180] The "location-lat" is information indicating the longitude where the vehicle equipped with the data collection device 2 exists.

[0181] The "location-alt" is information indicating the altitude where the vehicle equipped with the data collection device 2 exists.

[0182] As shown in FIG. 15, the data management unit 121 includes an index creation unit 124 and an index storage unit 125.

[0183] The index creation unit 124 periodically acquires the latest index 118 from the latest index storage unit 117, and creates an index 126 (also referred to as the second index) using the acquired latest index 118. Then, the index creation unit 124 stores the created index 126 in the index storage unit 125. As a result, a plurality of indexes 126 with different creation times are stored in the index storage unit 125 for each vehicle.

[0184] As shown in FIG. 18, the index 126 stores "timestamp", "schedule-type", "gateway-id", "object-id", "shadow-version", "vin", "location", and "alt".

[0185] "timestamp" is a timestamp indicating the time in milliseconds.

[0186] "schedule-type" indicates whether the scheduler of the data source is periodic or an event. If it is periodic, "schedule-type" is set to "Repeat", and if it is an event, "schedule-type" is set to "Event".

[0187] "gateway-id" is information for identifying the mobility GW111. "object-id" is information for identifying the vehicle equipped with the data collection device 2.

[0188] "shadow-version" is the timestamp of the gateway and is information for identifying the shadow 114. "vin" is the registration number unique to the vehicle equipped with the data collection device 2.

[0189] "location" is information indicating the latitude and longitude where the vehicle equipped with the data collection device 2 is located. "alt" is information indicating the altitude where the vehicle equipped with the data collection device 2 is located.

[0190] Here, a configuration may be adopted in which the latest index creation unit 116 and the latest index storage unit 117 are not provided, and the index creation unit 124 may generate the index 126 by acquiring the shadow 114 stored in the shadow storage unit 112. Desirably, the index creation unit 124 generates the index 126 using the latest index 118 acquired from the latest index storage unit 117. This is one of the configurations for making the mobility GW111 and the data management unit 121 loosely coupled.

[0191] Furthermore, the configuration may be such that the index creation unit 124 and the index storage unit 125 are not provided either. For example, the index acquisition unit 127 uses the "object-id" specified from the access API 122 and the time stamp ("shadow-version") to request the acquisition of the vehicle data specified to the data acquisition unit 119.

[0192] As shown in FIG. 15, the mobility GW 111 includes a data acquisition unit 119. The data management unit 121 includes an index acquisition unit 127.

[0193] The index acquisition unit 127 provides an index that can identify the shadow 114 in order to acquire vehicle data corresponding to the specified parameters from the shadow 114. When the index acquisition unit 127 receives a request from the access API 122 instructing the acquisition of specified data of a specified vehicle at a specified time, the index acquisition unit 127 acquires the index 126 corresponding to the specified time and the specified vehicle of the received request from the index storage unit 125.

[0194] Furthermore, the index acquisition unit 127 designates the shadow 114 specified based on the acquired index 126 as the specified shadow, and transmits a request instructing the acquisition of the specified data in the specified shadow to the data acquisition unit 119. Specifically, since the shadow 114 is uniquely determined by the "object-id" and the "shadow-version", the index acquisition unit 127 requests the data acquisition unit 119 to acquire the specified data using the "object-id" and the "shadow-version".

[0195] When the data acquisition unit 119 receives a request from the index acquisition unit 127, the data acquisition unit 119 extracts the specified data from the specified shadow indicated by the received request, and transmits the extracted specified data to the access API 122. Here, the extracted specified data may be transmitted to the access API 122 via the index acquisition unit 127.

[0196] In addition, in order to obtain specified data of a specified vehicle at a specified time, the access API 122 may obtain a corresponding index 126 from the index storage unit 125 via the index acquisition unit 127, and request the data acquisition unit 119 to obtain the specified data using the obtained index 126 (the "object-id" and the "shadow-version").

[0197] The requests RQ1, RQ2, and RQ3 shown in FIG. 19 are specific examples of requests sent by the service providing server 4 to the access API 122. In other words, it is an API for obtaining vehicle data provided by the access API 122 to the service providing server 4.

[0198] Request RQ1 is a request for obtaining the latitude (i.e., data with "item-names" being "latitude") of the vehicle with "object-id" being "dt-000002" and the vehicle with "object-id" being "dt-000008" for 10 seconds from 5:17:10.5 seconds on August 27, 2019.

[0199] Via the access API 122 that has received request RQ1, the index acquisition unit 127 obtains a "shadow-version" that can identify a shadow 114 corresponding to the "object-id" and the time information from the index storage unit 125. Then, the index acquisition unit 127 instructs the data acquisition unit 119 to obtain the "latitude" corresponding to the "object-id" and the "shadow-version". The data acquisition unit 119 obtains the corresponding vehicle data from the shadow storage unit 112, and the vehicle data is transmitted to the access API 122.

[0200] Request RQ2 is a request to obtain the latitudes of vehicles that exist between 5:17:10.5 seconds and 10 seconds on August 27, 2019, in the area within a rectangle specified by the upper left point specified by the longitude represented by 135.8974670767784 and the altitude represented by 36.16643474082275, and the lower right point specified by the longitude represented by 139.7863560656673 and the altitude represented by 35.05532363071164.

[0201] Via the access API 122 that received Request RQ2, the index acquisition unit 127 acquires a list of "object-id" of vehicles existing in the specified area at the specified time from the index storage unit 125, and acquires the "shadow-version" at the specified time of the "object-id". Then, the index acquisition unit 127 instructs the data acquisition unit 119 to acquire the "latitude" corresponding to the "object-id" and "shadow-version". The data acquisition unit 119 acquires the corresponding vehicle data from the shadow storage unit 112, and the vehicle data is transmitted to the access API 122.

[0202] Request RQ3 is a request to obtain information on all items in the category "ADAS / AD" at 5:17:10.5 seconds on August 27, 2019, for the vehicle with "object-id" being "dt-000002" and the vehicle with "object-id" being "dt-000008".

[0203] Via the access API 122 that has received the request RQ3, the index acquisition unit 127 acquires from the index storage unit 125 a "shadow version" that can identify the shadow 114 corresponding to the "object-id" and the time information. Then, the index acquisition unit 127 instructs the data acquisition unit 119 to acquire information on all items in the category "ADAS / AD" corresponding to the "object-id" and the "shadow version". The data acquisition unit 119 acquires the corresponding vehicle data from the shadow storage unit 112, and the vehicle data is transmitted to the access API 122.

[0204] Also, by designating the above analysis information as the designated data of the request that the service providing server 4 transmits to the access API 122, it is possible for the service providing server 4 to acquire the above analysis information. For example, the index acquisition unit 127 acquires from the index storage unit 125 an index 126 corresponding to the designated vehicle and the designated time of the received request. Further, based on the acquired index 126, the index acquisition unit 127 designates the identified shadow 114 as the designated shadow, and transmits to the data acquisition unit 119 a request for instructing the acquisition of data in the category "dangerous driving information" in the designated shadow. Note that the category "dangerous driving information" includes "sudden steering", "sudden braking", and "sudden acceleration" as items. Thereby, the service providing server 4 can acquire data including "sudden steering", "sudden braking", and "sudden acceleration".

[0205] As shown by arrow L1 in FIG. 5, the service providing server 4 identifies the shadow 114 corresponding to the specified vehicle by accessing the digital twin 123 of the data management unit 121 via the access API 122. Then, as shown by arrow L2 in FIG. 4, the service providing server 4 transmits a control instruction including the specified shadow and the control content to the vehicle control unit 113 of the mobility GW 111. Thereby, the vehicle control unit 113 transmits the control instruction to the data collection device 2 of the vehicle corresponding to the specified shadow. And when the control instruction is received by the data collection device 2, control based on the control instruction is executed in the vehicle equipped with the data collection device 2.

[0206] The management center 3 configured in this way includes a vehicle-side unit 110 and a service-side unit 120.

[0207] The vehicle-side unit 110 is connected to be data communicable with a plurality of data collection devices 2 mounted on each of the plurality of vehicles. The service-side unit 120 is connected to be data communicable with the service providing server 4.

[0208] And the vehicle-side unit 110 includes a shadow creation unit 115.

[0209] The shadow creation unit 115 repeatedly acquires a vehicle data group formed in a first data structure in which a plurality of vehicle data are classified into each category from each of the plurality of data collection devices 2. And for each vehicle, the shadow creation unit 115 creates a vehicle data group to which vehicle identification information (in this embodiment, "object-id") for identifying the vehicle and timing identification information (in this embodiment, "Shadow_version") for identifying the timing when the vehicle data was acquired are assigned as the shadow 114, and stores it in the shadow storage unit 112 provided in the vehicle-side unit 110 in the form of the first data structure.

[0210] The service-side unit 120 includes an index acquisition unit 127. When the index acquisition unit 127 receives from the service providing server 4 a request for instructing the acquisition of corresponding vehicle data by designating specific vehicle data or a specific category among a plurality of vehicle data constituting the vehicle data group, it instructs the vehicle-side unit 110 to acquire the designated data of a predetermined vehicle at a predetermined time from the shadow storage unit 112 of the vehicle-side unit 110 based on the request. The vehicle-side unit 110 acquires vehicle data corresponding to the designated data from the designated shadow 114 of the designated vehicle from the shadow storage unit 112 and transmits it to the service-side unit 120. The service-side unit 120 transmits the transmitted vehicle data to the service providing server 4 that made the request.

[0211] In such a management center 3, the shadow 114 has a first data structure in which a plurality of vehicle data are classified into each category, and the plurality of vehicle data are organized in a hierarchical structure. Therefore, the management center 3 can access a plurality of vehicle data constituting the shadow 114 by the data name of specific vehicle data or the category name of a specific category, and can facilitate the use of vehicle data.

[0212] Note that the "data name of specific vehicle data" is, for example, the above "vehicle identification number", "body number", "license plate number", "brand name", "model", "manufacturing year", and "transmission type". Also, the "category name of a specific category" is, for example, the above "attribute information", "power train", "energy", "vehicle identification information", "vehicle attribute", "transmission configuration", "firmware version", "accelerator pedal", "engine", "engine oil", "battery state", "battery configuration", and "fuel".

[0213] In addition to the vehicle data group formed in the first data structure, the shadow 114 includes device information formed in the second data structure and indicating the state of in-vehicle devices. The in-vehicle devices are the hardware mounted on the data collection device 2. As a result, the management center 3 can also manage the above device information.

[0214] Further, the index creation unit 124 of the service side unit 120 creates an index 126 which is data for specifying the shadow 114 and is formed in the third data structure, and stores it in the index storage unit 125 provided in the service side unit 120.

[0215] The vehicle side unit 110 also includes a latest index creation unit 116. The latest index creation unit 116 creates a latest index 118 for identifying the latest shadow 114 for each of a plurality of vehicles, and stores it in the latest index storage unit 117 provided in the vehicle side unit 110.

[0216] The index creation unit 124 repeatedly acquires the latest index 118 from the latest index storage unit 117, creates the latest index 118 with time information for specifying the shadow 114 corresponding to the latest index 118 as the index 126, and stores it in the index storage unit 125 provided in the service side unit 120.

[0217] As a result, the service side unit 120 specifies the shadow 114 by referring to the index 126 (that is, without directly referring to the shadow 114). Since this index 126 is composed of information for identifying the shadow 114 (that is, the latest index 118) and time information, it is information that does not depend on the vehicle manufacturer, vehicle, and shipping date. Therefore, the management center 3 can allow service developers to develop services without considering differences in the formats of vehicle data.

[0218] Also, when the index acquisition unit 127 receives a request, it acquires the index 126 corresponding to the specified time and specified vehicle of the request from the index storage unit 125, and identifies the shadow 114 based on the acquired index 126.

[0219] Also, the vehicle-side unit 110 includes a data acquisition unit 119. The data acquisition unit 119 acquires the shadow 114 specified by the index acquisition unit 127 from the shadow storage unit 112, extracts the specified data from the acquired shadow 114, and transmits it to the service-side unit 120.

[0220] Thereby, the management center 3 can provide the specified data of the specified vehicle at the specified time to the service-providing server 4.

[0221] Also, in the plurality of data collection devices 2, for each of the plurality of vehicle data constituting the vehicle data group, one of a plurality of different transmission timings is set. Then, the vehicle-side unit 110 receives each of the plurality of vehicle data constituting the vehicle data group from the plurality of data collection devices 2 at the transmission timing set for the vehicle data.

[0222] Thereby, the management center 3 can reduce the frequency of receiving unnecessary unupdated vehicle data and reduce the communication processing load.

[0223] The data collection device 2 includes a vehicle data conversion table 23a in which "resolution" and "offset" are set as normalization information. Then, the vehicle data is generated by the data collection device 2 normalizing the data acquired from the vehicle by the data collection device 2 based on the normalization information of the vehicle data conversion table 23a.

[0224] Thereby, the management center 3 can provide vehicle data in a format that does not depend on the vehicle type and vehicle manufacturer to the service-providing server 4.

[0225] The vehicle data conversion table 23a further includes semantic information for converting into vehicle data generated using a plurality of normalized vehicle data. Then, the vehicle data is generated by the in-vehicle device converting using a plurality of normalized vehicle data based on the semantic information of the vehicle data conversion table 23a.

[0226] Thereby, the management center 3 can provide the service providing server 4 with the semanticized vehicle data using the vehicle data acquired from the vehicle by the data collection device 2.

[0227] The plurality of categories are set based on the functions or domains of the vehicle. Thereby, the management center 3 can collectively acquire all the vehicle data related to the function or domain corresponding to a specific category by the category name of the specific category.

[0228] Also, the shadow creation unit 115 of the management center 3 repeatedly acquires the analysis information generated by analyzing a plurality of vehicle data from each of the plurality of data collection devices 2, and creates a shadow 114 including the acquired analysis information. And the above specified data further includes analysis information. Thereby, the management center 3 can acquire the analyzed data from the vehicle, manage the shadow 114, and provide the analyzed data to various service providers.

[0229] Note that the vehicle control unit 113 may acquire a control instruction from the service providing server 4 via the access API 122 of the service side unit 120. Providing the access API 122 to the service side unit 120 and providing the vehicle control unit 113 to the vehicle side unit 110 is also one of the configurations that loosely couple the two units.

[0230] In the embodiments described above, the management center 3 corresponds to the center, the data collection device 2 corresponds to the in-vehicle device, the service providing server 4 corresponds to the service providing unit, the index acquisition unit 127 corresponds to the instruction unit, and the mobility IoT system 1 corresponds to the management system.

[0231] As described above, one embodiment of the present disclosure has been described. However, the present disclosure is not limited to the above embodiment and can be implemented with various modifications.

[0232] The control unit 31 and its 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 by a computer program. Alternatively, the control unit 31 and its 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. Or, the control unit 31 and its 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 by one or more hardware logic circuits. Further, the computer program may be stored in a computer-readable non-transitory tangible recording medium as instructions to be executed by a computer. The method for realizing the functions of each part included in the control unit 31 does not necessarily have to include software, and all of its functions may be realized using one or more hardware.

[0233] The multiple functions of one component in the above embodiment may be realized by multiple components, or one function of one component may be realized by multiple components. Also, the multiple functions of multiple components may be realized by one component, or one function realized by multiple components may be realized by one component. Further, a part of the configuration of the above embodiment may be omitted. Also, at least a part of the configuration of the above embodiment may be added to or replaced with the configuration of another above embodiment.

[0234] In addition to the above-described management center 3, the present disclosure can also be realized in various forms such as a system having the management center 3 as a component, a program for causing a computer to function as the management center 3, a non-transitory tangible recording medium such as a semiconductor memory recording this program, and a data management method.

Claims

1. A vehicle-side unit (110) data communicably connected to a plurality of in-vehicle devices (2) mounted on each of a plurality of vehicles, And a service-side unit (120) capable of data communication with a service providing unit (4). The vehicle-side unit Repeatedly acquires a vehicle data group formed in a first data structure in which a plurality of vehicle data are classified into each category from each of the plurality of in-vehicle devices, and for each vehicle, vehicle identification information for identifying the vehicle, and timing identification information for identifying the timing at which the vehicle data was acquired are attached to the vehicle data group, which is created as a shadow (114), and stored in a shadow storage unit (112) provided in the vehicle-side unit in the form of the first data structure. It comprises a shadow creation unit (115) configured to store. The service-side unit When a request for acquiring the corresponding vehicle data is received from the service providing unit using specific vehicle data or a specific category among the plurality of vehicle data constituting the vehicle data group as designated data, based on the request, the vehicle-side unit is instructed to acquire the designated data of a predetermined vehicle at a predetermined time from the shadow storage unit of the vehicle-side unit. A center (3) comprising an instruction unit (127) configured to do so.

2. The center according to claim 1, The shadow includes device information formed in a second data structure and indicating the state of in-vehicle equipment in addition to the vehicle data group formed in the first data structure.

3. The center according to claim 1 or claim 2, The service-side unit Creates an index (126) which is data for specifying the shadow and is formed in a third data structure, and comprises an index creation unit (124) configured to store it in an index storage unit (125) provided in the service-side unit.

4. The center according to claim 3, wherein the vehicle-side unit is configured to create a latest index (118) for identifying the latest one of the shadows for each of the plurality of vehicles and store the latest index in a latest index storage unit (117) provided in the vehicle-side unit, and includes a latest index creation unit (116); the index creation unit repeatedly obtains the latest index from the latest index storage unit and creates the latest index with time information for specifying the shadow corresponding to the latest index as the index.

5. The center according to claim 4, wherein when receiving the request, the instruction unit obtains the index corresponding to the predetermined time and the predetermined vehicle from the index storage unit, and is configured to specify the shadow based on the obtained index; the vehicle-side unit includes a data acquisition unit (119) configured to acquire the shadow specified by the instruction unit from the shadow storage unit, extract the specified data from the acquired shadow, and transmit the data to the service-side unit.

6. The center according to any one of claims 1 to 5, wherein in the plurality of in-vehicle devices, for each of the plurality of vehicle data constituting the vehicle data group, one of a plurality of different transmission timings is set; the vehicle-side unit receives each of the plurality of vehicle data constituting the vehicle data group from the plurality of in-vehicle devices at the transmission timing set for the vehicle data.

7. The center according to any one of claims 1 to 6, wherein The in-vehicle device includes a vehicle data conversion table in which "resolution" and "offset" are set as normalization information. The vehicle data is a center generated by the in-vehicle device normalizing data acquired from the vehicle by the in-vehicle device based on the normalization information of the vehicle data conversion table.

8. The center according to claim 7, The vehicle data conversion table further includes semantic information for converting the vehicle data into the vehicle data generated using a plurality of the normalized vehicle data. The vehicle data is a center generated by the in-vehicle device converting a plurality of the normalized vehicle data based on the semantic information of the vehicle data conversion table.

9. The center according to any one of claims 1 to 8, The plurality of categories are set based on the functions or domains of the vehicle.

10. The center according to any one of claims 1 to 9, The category further includes attribute information.

11. The center according to any one of claims 1 to 10, The shadow creation unit repeatedly acquires analysis information generated by analyzing a plurality of the vehicle data from each of the plurality of in-vehicle devices, and creates the shadow including the acquired analysis information. The specified data further includes the analysis information.

12. A management system (1) including a plurality of in-vehicle devices (2) mounted on each of a plurality of vehicles to acquire vehicle data from the vehicles, and a center (3) for managing the vehicle data, The center is A vehicle-side unit (110) connected to be data communicable with the plurality of in-vehicle devices, A service system comprising a service providing unit (4) and a service side unit (120) capable of data communication with the service providing unit (4), wherein the vehicle side unit repeatedly acquires a vehicle data group formed in a first data structure in which a plurality of the vehicle data are classified into respective categories from each of the plurality of in-vehicle devices, and for each vehicle, vehicle identification information for identifying the vehicle and timing identification information for identifying the timing at which the vehicle data was acquired are added to the vehicle data group, which is then created as a shadow (114), and the shadow creation unit (115) is configured to store the vehicle data group in a shadow storage unit (112) provided in the vehicle side unit in the form of the first data structure. The service side unit When receiving, from the service providing unit, a request for instructing acquisition of corresponding vehicle data by designating specific vehicle data or a specific category among the plurality of vehicle data constituting the vehicle data group as designation data, the instruction unit (127) is configured to instruct the vehicle side unit to acquire the designation data of a predetermined vehicle at a predetermined time from the shadow storage unit of the vehicle side unit based on the request.

13. The management system according to claim 12, wherein the in-vehicle device includes a vehicle data conversion table in which "resolution" and "offset" are set as normalization information. The vehicle data is generated by the in-vehicle device normalizing data acquired from the vehicle by the in-vehicle device based on the normalization information in the vehicle data conversion table.

14. The management system according to claim 13, wherein the vehicle data conversion table further includes semantic information for converting the vehicle data generated using the plurality of normalized vehicle data into the vehicle data. The vehicle data is a management system generated by the in-vehicle device converting using a plurality of normalized vehicle data based on the semantic information in the vehicle data conversion table.

15. A vehicle-side unit (110) data communicably connected to a plurality of in-vehicle devices (2) mounted on each of a plurality of vehicles, A management method executed by a center (3) including a service-side unit (120) data communicable with a service providing unit (4), wherein the vehicle-side unit repeatedly acquires a vehicle data group formed in a first data structure in which a plurality of vehicle data are classified into each category from each of the plurality of in-vehicle devices, and for each vehicle, a vehicle identification information for identifying the vehicle and a timing identification information for identifying the timing at which the vehicle data is acquired are attached to the vehicle data group to create a shadow (114), and stores the shadow in a shadow storage unit (112) provided in the vehicle-side unit in the form of the first data structure, When the service-side unit receives, from the service providing unit, a request for instructing acquisition of specific vehicle data or a specific category among the plurality of vehicle data constituting the vehicle data group as designated data, the service-side unit instructs the vehicle-side unit to acquire the designated data of a predetermined vehicle at a predetermined time from the shadow storage unit of the vehicle-side unit.

16. A vehicle-side unit (110) data communicably connected to a plurality of in-vehicle devices (2) mounted on each of a plurality of vehicles, A computer of a center (3) including a service-side unit (120) data communicable with a service providing unit (4), In the vehicle-side unit, a vehicle data group formed in a first data structure in which a plurality of vehicle data are classified into each category is repeatedly acquired from each of the plurality of in-vehicle devices, and for each vehicle, vehicle identification information for identifying the vehicle and timing identification information for identifying the timing at which the vehicle data was acquired are added to the vehicle data group, which is then created as a shadow (114) and stored in a shadow storage unit (112) provided in the vehicle-side unit in the form of the first data structure. A shadow creation unit (115) configured to do so, and, In the service-side unit, when a request for instructing acquisition of corresponding vehicle data is received from the service providing unit using specific vehicle data or a specific category among the plurality of vehicle data constituting the vehicle data group as designated data, the vehicle-side unit is instructed to acquire the designated data of a predetermined vehicle at a predetermined time from the shadow storage unit of the vehicle-side unit. An instruction unit (127) configured to do so A management program for causing it to function as such.

Images