Data management system, data center, data management program, and data management method

Abstract

A data management system (1) is provided with a plurality of in-vehicle devices (2) and a data center (3). The data center is provided with a first management unit (63), a second management unit (68), and a data distribution unit (64). The first management unit manages, for each vehicle driver, personal characteristic data related to personal characteristics of the driver on the basis of a plurality of pieces of vehicle data. The second management unit manages, for each vehicle, information for identifying an application (16) downloaded to the vehicle and personal characteristic data identification information for identifying the personal characteristic data used by the application. The data distribution unit distributes the personal characteristic data corresponding to the personal characteristic data identification information to an in-vehicle device.

Description

Data management system, center, data management program, and data management method CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This international application claims the benefit of Japanese Patent Application No. 2024-105138, filed with the Japan Patent Office on June 28, 2024, the entire disclosure of which is incorporated herein by reference.

[0002] The present disclosure relates to a data management system, a center, a data management program, and a data management method that utilize data acquired from a vehicle.

[0003] Patent Document 1 describes a service providing server that provides services by accessing a digital twin that reproduces the state of a vehicle in the real world in a virtual space by collecting vehicle data from multiple vehicles.

[0004] International Publication No. 2023 / 276957

[0005] When providing a service to a vehicle driver, it may be necessary to acquire vehicle data related to the vehicle from the target vehicle to which the service is to be provided.

[0006] As a result of detailed consideration by the inventors, it was found that in order to provide appropriate services to each vehicle driver, it may be necessary to generate new information required for the service for each driver using vehicle data obtained from the vehicle, which may reduce the convenience of providing the service.

[0007] The present disclosure facilitates the use of vehicle data.

[0008] One aspect of the present disclosure is a data management system including a plurality of on-board devices mounted on a plurality of vehicles, respectively, and a center configured to perform data communication between the plurality of on-board devices.

[0009] The center includes an acquisition unit, a first management unit, a second management unit, and a data distribution unit.

[0010] The acquisition unit is configured to acquire a plurality of vehicle data related to the vehicle from the in-vehicle device.

[0011] The first management unit is configured to manage a plurality of personal characteristic data relating to the personal characteristics of each driver of the vehicle based on the plurality of vehicle data acquired by the acquisition unit.

[0012] The second management unit is configured to manage, for each vehicle, one or more pieces of application identification information for identifying one or more applications downloaded to the vehicle, and one or more pieces of personal characteristic data identification information for identifying one or more pieces of personal characteristic data used by the one or more applications downloaded to the vehicle.

[0013] The data distribution unit is configured to distribute, to the in-vehicle device, one or more pieces of personal characteristic data corresponding to one or more pieces of personal characteristic data specifying information.

[0014] The in-vehicle device includes a data storage unit and an access management unit.

[0015] The data storage unit is configured to store one or more pieces of personal characteristic data downloaded from the center for each driver.

[0016] The access management unit is configured to manage access to the one or more personal characteristic data by one or more applications downloaded to the vehicle.

[0017] In the data management system of the present disclosure configured as above, the center can provide the vehicle with personal characteristic data for each driver that is used by the application downloaded to the vehicle. This eliminates the need for the application downloaded to the vehicle to use vehicle data acquired from the vehicle to newly generate personal characteristic data for each driver that the application uses. Therefore, the data management system of the present disclosure can facilitate the use of vehicle data.

[0018] Another aspect of the present disclosure is a center configured to perform data communication between a plurality of on-board devices mounted on each of a plurality of vehicles, and including an acquisition unit, a first management unit, a second management unit, and a data distribution unit.

[0019] The center of the present disclosure configured in this manner is a device provided in the data management system of the present disclosure, and can obtain the same effects as the data management system of the present disclosure.

[0020] Yet another aspect of the present disclosure is a data management program that causes a center computer configured to perform data communication with multiple on-board devices installed in multiple vehicles to function as an acquisition unit, a first management unit, a second management unit, and a data distribution unit.

[0021] A computer controlled by the data management program of the present disclosure can constitute part of the center of the present disclosure, and can obtain the same effects as the center of the present disclosure.

[0022] Yet another aspect of the present disclosure is a data management method executed in a data management system including a plurality of on-board devices mounted on each of a plurality of vehicles and a center configured to perform data communication between the plurality of on-board devices.

[0023] In the data management method of the present disclosure, the center acquires a plurality of vehicle data items related to the vehicle from the in-vehicle device.

[0024] The center manages a plurality of pieces of personal characteristic data relating to the personal characteristics of each driver of the vehicle based on the plurality of pieces of vehicle data acquired.

[0025] The center manages, for each vehicle, one or more pieces of application identification information for identifying one or more applications downloaded to the vehicle, and one or more pieces of personal characteristic data identification information for identifying one or more pieces of personal characteristic data used by the one or more applications downloaded to the vehicle.

[0026] The center distributes one or more pieces of personal characteristic data corresponding to one or more pieces of personal characteristic data specifying information to the vehicle-mounted device.

[0027] The in-vehicle device stores one or more pieces of personal characteristic data downloaded from the center for each driver.

[0028] The in-vehicle device manages access to one or more personal characteristic data by one or more applications downloaded to the vehicle.

[0029] The data management method of the present disclosure is a method executed in the data management system of the present disclosure, and by executing this method, it is possible to obtain the same effects as the data management system of the present disclosure.

[0030] 1 is a block diagram showing the configuration of a mobility IoT system. FIG. 1 is a block diagram showing the configuration of an on-board device and a center of a first embodiment. FIG. 2 is a functional block diagram showing the functional configuration of an on-board device and a center of a first embodiment. FIG. 3 is a diagram showing the configuration of primary processed data. FIG. 4 is a diagram showing the configuration of a CAN frame. FIG. 5 is a diagram showing the configuration of a vehicle data conversion table. FIG. 6 is a diagram showing the configuration of secondary processed data. FIG. 7 is a flowchart showing the procedure for generating and synchronizing secondary processed data. FIG. 8 is a functional block diagram showing the functional configuration of a center. FIG. 9 is a block diagram showing the configuration of an application storage unit and a download data management unit. FIG. 10 is a block diagram showing the configuration of a download data storage unit. FIG. 11 is a flowchart showing profile download processing. FIG. 12 is a flowchart showing synchronization processing. FIG. 13 is a flowchart showing deletion notification processing. FIG. 14 is a flowchart showing deletion update processing. FIG. 15 is a block diagram showing the configuration of an on-board device and a center of a second embodiment. FIG. 16 is a functional block diagram showing the functional configuration of an on-board device and a center of a second embodiment. FIG. 17 is a flowchart showing the procedure for generating and synchronizing a model.

[0031] First Embodiment A first embodiment of the present disclosure will be described below with reference to the drawings.

[0032] 1, a mobility IoT system 1 of this embodiment includes a plurality of in-vehicle devices 2, a center 3, and a service providing server 4. IoT is an abbreviation for Internet of Things.

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

[0034] The center 3 is a device that manages the mobility IoT system 1. The center 3 has a function of performing data communication between the multiple in-vehicle devices 2 and the service providing server 4 via the wide area wireless communication network NW.

[0035] The service providing server 4 is, for example, a server installed to provide a service for selecting a vehicle to which a shadow mode application is to be distributed. Note that the mobility IoT system 1 may include multiple service providing servers each providing a different service content.

[0036] As shown in FIG. 2, the in-vehicle 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.

[0037] The microcomputer 11 includes a CPU 21 , a ROM 22 , a RAM 23 , an input / output unit 24 , and a bus 25 .

[0038] The various functions of the microcomputer 11 are realized by the CPU 21 executing a program stored in a non-transitory physical recording medium. In this example, the ROM 22 corresponds to the non-transitory physical recording medium storing the program. Execution of this program also 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.

[0039] The input / output unit 24 is a circuit for inputting and outputting data between the CPU 21 and the outside of the microcomputer 11 .

[0040] The bus 25 connects the CPU 21, the ROM 22, the RAM 23, and the input / output unit 24 so that data can be input and output to and from each other.

[0041] The vehicle I / F 12 is an input / output circuit for transmitting and receiving signals to and from electronic control devices, sensors, and the like mounted on the vehicle.

[0042] 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.

[0043] 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. 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 an abbreviation for Controller Area Network. Ethernet is a registered trademark.

[0044] Other electronic control units mounted on the vehicle are connected to the CAN communication port and the Ethernet communication port, thereby enabling the in-vehicle device 2 to transmit and receive communication frames to and from the other electronic control units.

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

[0046] The storage unit 14 is a storage device for storing various data, and includes a vehicle data conversion table 26 (described later), a vehicle data storage unit 27 (described later), and a download data storage unit 28 (described later).

[0047] The center 3 includes a control unit 31 , a communication unit 32 , and a storage unit 33 .

[0048] 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. The 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. Furthermore, the execution of this program results in the execution of a method corresponding to the program. Note that some or all of the functions executed by the CPU 41 may be configured as hardware using one or more ICs, etc. Furthermore, the number of microcomputers constituting the control unit 31 may be one or more.

[0049] The communication unit 32 performs data communication between the plurality of in-vehicle devices 2 and the service providing server 4 via the wide area wireless communication network NW.

[0050] The storage unit 33 is a storage device for storing various data, and includes a primary processed data storage unit 44 (to be described later), a secondary processed data storage unit 45 (to be described later), and an application storage unit 46 (to be described later).

[0051] As shown in FIG. 3, the in-vehicle device 2 includes a data acquisition unit 51, a primary processing unit 52, and a data linking unit 53 as functional blocks realized by the CPU 21 executing a program stored in the ROM 22.

[0052] The data acquisition unit 51 acquires data input to the vehicle I / F 12 (i.e., data input to the general-purpose input / output port, the CAN communication port, and the Ethernet communication port). Examples of data input to the general-purpose input / output port include image data captured by a camera mounted on the vehicle. Data input to the CAN communication port is a CAN frame. Data input to the Ethernet communication port is an Ethernet frame.

[0053] The primary processing unit 52 processes the vehicle data acquired by the data acquisition unit 51 into common data (hereinafter referred to as primary processed data) in which the same physical quantities have the same values ​​regardless of the vehicle model and vehicle manufacturing company (hereinafter referred to as manufacturer) by referring to the vehicle data conversion table 26 stored in the memory unit 14.

[0054] The vehicle data conversion table 26 contains conversion information for converting vehicle data of the vehicle (hereinafter referred to as the "own vehicle") in which the on-board device 2 is mounted into common data. The conversion information may be set based on the Vehicle Signal Specifications (VSS). VSS stands for Vehicle Signal Specifications.

[0055] The primary processed data includes, for example, a time stamp, a vehicle speed, a steering angle, an accelerator pedal position, a brake pedal position, and a vehicle position, as shown in FIG.

[0056] Here, a specific example of processing vehicle data into primary processed data will be described.

[0057] As shown in Fig. 5, a CAN frame is composed of a start of frame, arbitration field, control field, data field, CRC field, ACK field, and end of frame. The arbitration field is composed of an 11-bit or 29-bit identifier (i.e., ID) and a 1-bit RTR bit.

[0058] The 11-bit identifier used in CAN communication is called a CAN ID. The CAN ID is set in advance based on the content of the data included in the CAN frame, the source of the CAN frame, the destination of the CAN frame, etc.

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

[0060] The primary processing unit 52 first divides the first to eighth data into 1-byte pieces and extracts eight CAN data. The CPU 41 then refers to the vehicle data conversion table 26 and converts each extracted data piece into a control label and vehicle data. The control label is identification information that indicates the type of the vehicle data.

[0061] The vehicle data conversion table 26 includes normalization information and semantic information.

[0062] The normalization information is information for normalizing the extracted data so that the same physical quantity has the same value regardless of the vehicle model and manufacturer.

[0063] Semantic information is information (e.g., an arithmetic expression or a conversion table) for converting normalized vehicle data into meaningful vehicle data. Vehicle data before normalization may also be used. Semantic information includes newly generating information that was not included in the payload of a communication frame using an arithmetic expression or the like.

[0064] As shown in FIG. 6, the normalization information of vehicle data conversion table 26 includes setting items such as "CANID," "ECU," "position," "DLC," "unique label," "resolution," "offset," and "unit."

[0065] "ECU" is identification information that indicates the ECU that is the sender of the CAN frame. For example, "ENG" indicates an engine ECU.

[0066] "Position" is information indicating the position (e.g., bit position) of the CAN data within the data field. "DLC" is information indicating the data length. DLC stands for Data Length Code. In other words, "DLC" bits of data are extracted from the "position" of the data field.

[0067] "Unique label" is information indicating the control label. For example, "ETHA" indicates the intake air temperature, and "NE1" indicates the engine speed. "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.

[0068] Therefore, data corresponding to the "unique label" is extracted from the CAN frame using the "CAN ID," "ECU," "position," "DLC," and "unique label." The extracted data is then converted into vehicle data expressed by the "resolution," "offset," and "unit."

[0069] Further, the semantic information of the vehicle data conversion table 26 is, for example, a conversion formula for converting a "steering movement angle" whose control label is "SSA" into a "steering angle" by subtracting a "steering zero point" whose control label is "SSAZ" as shown in Fig. 6. In this way, the vehicle data representing the "steering movement angle" and the vehicle data representing the "steering zero point" are converted into vehicle data representing a "steering angle" which has the meaning of "amount of steering from a reference position". A "unique label", "unit", etc. are assigned to the vehicle data newly generated by the semanticization.

[0070] The system also has a vehicle data conversion table 26 for data on "shift position," which is a predetermined control label. The vehicle data conversion table 26 converts the data into data indicating "P range," "N range," "D range," and "R range," respectively.

[0071] As shown in FIG. 3 , the data linking unit 53 manages access from the service application 16 installed in the vehicle to the secondary processed data stored in the download data storage unit 28 (described later). The service application 16 is installed in the in-vehicle device 2 or another electronic control unit connected to the in-vehicle device 2 and provides a predetermined service to the vehicle user. The predetermined service is, for example, a service that provides driving advice to make driving easier for the driver or driving advice tailored to the driver. For example, driving advice may be advice to reduce the number of sudden braking attempts for a driver who tends to brake suddenly (e.g., advice such as "press the brake pedal quickly"). For example, driving advice may be advice to reduce the number of sudden acceleration attempts for a driver who tends to accelerate suddenly (e.g., advice such as "press the accelerator pedal slowly").

[0072] The data linking unit 53 uploads the image data acquired by the data acquisition unit 51 and the primary processed data generated by the primary processing unit 52 to the center 3 together with information identifying the driver of the vehicle and information identifying the vehicle.

[0073] The center 3 has functional blocks realized by the CPU 41 executing a program stored in the ROM 42, including a primary processing data acquisition unit 61, a secondary processing unit 62, a data management unit 63, and a data distribution unit 64.

[0074] The primary processed data acquisition unit 61 acquires image data and primary processed data uploaded to the center 3 from multiple vehicle-mounted devices 2, and stores the acquired image data and primary processed data in the primary processed data storage unit 44 of the center 3.

[0075] The secondary processing unit 62 uses the plurality of primary processed data and image data stored in the primary processed data storage unit 44 to generate common data that can be used in common by the service application 16 and the service providing server 4. The secondary processing unit 62 starts generating common data when the primary processed data for the required period has been accumulated.

[0076] The secondary processing unit 62 stores the generated plurality of common data in the secondary processed data storage unit 45. Hereinafter, the common data stored in the secondary processed data storage unit 45 will be referred to as secondary processed data.

[0077] The secondary processing unit 62 generates secondary processed data indicating the driver's facial direction, or secondary processed data indicating whether the driver is feeling drowsy, for example, by analyzing the image data.

[0078] The data stored in the primary processed data storage unit 44 and the secondary processed data storage unit 45 can be accessed by the administrator of the center 3 via an interface provided in the center 3 .

[0079] The secondary processing unit 62 generates secondary processed data indicating whether or not a traffic jam has occurred by determining whether or not a preset traffic jam determination condition is met, for example. The traffic jam determination condition is, for example, that the vehicle speed is less than 10 km / h and the distance between the vehicle ahead and the vehicle is 20 m or less for 10 minutes or more.

[0080] The secondary processing unit 62, for example, performs statistical processing using a large number of primary processed data to generate secondary processed data indicating the characteristics of a standard driver (hereinafter referred to as standard driver characteristic data), secondary processed data indicating the characteristics of a good driver (hereinafter referred to as good driver characteristic data), and secondary processed data indicating the characteristics of each driver (hereinafter referred to as driver individual characteristic data).

[0081] The standard driver characteristic data is, for example, an average value obtained by calculating the acceleration during sudden acceleration of the vehicle for each driver and averaging the accelerations during sudden acceleration for a large number of drivers. Note that the acceleration during sudden deceleration may be used instead of the acceleration during sudden acceleration of the vehicle. By referring to the standard driver characteristic data, an application installed in the vehicle can determine whether the driver frequently accelerates suddenly and can then warn the driver or suggest adaptive cruise control to the driver.

[0082] The good driver characteristic data is, for example, an average value of the acceleration during sudden acceleration for the top 5% of drivers (or taxi drivers) with the lowest acceleration during sudden acceleration. By referring to the good driver characteristic data, an application installed in the vehicle can determine whether the driver is driving safely.

[0083] The driver's individual characteristic data is information that indicates, for example, the characteristics of the driving style of an individual driver. Examples of the driving style characteristics of an individual driver include the distance between the vehicle and the vehicle in front while driving on a highway (hereinafter referred to as the vehicle-to-vehicle distance in front) and the acceleration required to follow the vehicle in front while driving on a highway (hereinafter referred to as the following acceleration). By referencing the driver's individual characteristic data, an application installed in the vehicle can execute adaptive cruise control by adjusting the vehicle-to-vehicle distance in front and the following acceleration to match the individual driver, thereby providing a service that makes the driver feel like they are driving naturally while using adaptive cruise control.

[0084] The secondary processed data includes, for example, an environment model data set 71, a vehicle model data set 72, and a human model data set 73, as shown in FIG.

[0085] The environment model data set 71 includes "personal ID," "VIN," "traffic jam," "expressway," "general road," "parking lot," "geofence," "day / night," and "timestamp."

[0086] "Personal ID" is information that identifies the driver who is driving the vehicle. "VIN" is a registration number unique to the vehicle. "Traffic jam" indicates whether the vehicle is in a traffic jam. "Expressway" indicates whether the vehicle is traveling on an expressway. "General road" indicates whether the vehicle is traveling on a general road. "Parking lot" indicates whether the vehicle is parked in a parking lot. "Geofence" is information that identifies the geofence to which the vehicle belongs. "Day / night" indicates whether the vehicle is traveling during the day or at night. "Timestamp" indicates the time when the in-vehicle device 2 acquired the data, for example, in seconds.

[0087] The vehicle model data set 72 includes "personal ID", "VIN", "driving", "stopped", "power off", "ACC use status", "navigation use status", "vehicle speed", "position information", and "timestamp".

[0088] "Driving" indicates whether the host vehicle is driving or not. "Stopped" indicates whether the host vehicle is stopped or not. "Power Off" indicates whether the host vehicle's IG power supply is off or not. "ACC Use Status" indicates whether the host vehicle is using adaptive cruise control or not. "Navigation Use Status" indicates whether the host vehicle is using the route guidance function of the navigation device or not. "Vehicle Speed" indicates the vehicle's driving speed. "Location Information" indicates the location of the host vehicle using latitude and longitude.

[0089] The human model data set 73 includes "personal ID," "VIN," "driver type," "number of occupants," "driving tendency," "face direction," "drowsiness," "personal ACC setting," "personal ADAS setting," and "timestamp." ADAS is an abbreviation for Advanced Driving Assistant System.

[0090] "Driver type" indicates the age, gender, driving history, etc. of the driver of the vehicle. "Number of occupants" indicates the number of people in the vehicle. "Driving tendency" indicates the driving tendency of the driver of the vehicle. "Driving tendency" indicates, for example, whether the driver brakes or turns suddenly more or less than average. "Facial direction" indicates the facial direction of the driver of the vehicle. "Drowsiness" indicates whether the driver of the vehicle is drowsy.

[0091] The "ACC individual settings" include the distance between the vehicle and the vehicle in front while traveling on a highway, and the acceleration required to follow the vehicle in front while traveling on a highway.

[0092] The "ADAS personal settings" indicate, for each ADAS function, whether the driver accepts recommendations and, if so, the timing of the recommendations. For example, information is set such that, among the ADAS functions, ACC recommendations are accepted and LKA recommendations are rejected. LKA stands for Lane Keeping Assist. The "ADAS personal settings" information is obtained by accumulating and analyzing the vehicle's driving data and the results of ADAS function recommendations (i.e., whether they were accepted or rejected) at the center 3, thereby analyzing the characteristics of the driver's receptivity to recommendations.

[0093] The data management unit 63 manages the secondary processed data stored in the secondary processed data storage unit 45. Specifically, the data management unit 63 provides the secondary processed data corresponding to each vehicle to the data distribution unit 64, and provides the secondary processed data required by the service providing server 4 to the service providing server 4.

[0094] The data distribution unit 64 distributes the secondary processed data corresponding to each vehicle, among the plurality of secondary processed data stored in the secondary processed data storage unit 45 , to each in-vehicle device 2 .

[0095] The data linking unit 53 of the in-vehicle device 2 stores the secondary processed data downloaded from the center 3 in the download data storage unit 28 .

[0096] Next, a procedure in which the center 3 generates secondary processed data and synchronizes it with the vehicle-mounted device 2 will be described.

[0097] As shown in FIG. 8, in S1, the in-vehicle device 2 acquires vehicle data from the vehicle using the data acquisition unit 51.

[0098] At S2, the in-vehicle device 2 processes the vehicle data acquired by the data acquisition unit 51 into primary processed data using the primary processing unit 52, and then uploads the image data acquired by the data acquisition unit 51 and the primary processed data generated by the primary processing unit 52 to the center 3 using the data linking unit 53, together with information identifying the driver of the vehicle and information identifying the vehicle.

[0099] In S3, the center 3 determines whether or not the primary processed data for the required period has been accumulated. If the primary processed data for the required period has not been accumulated, the in-vehicle device 2 repeats the processes of S1 and S2. On the other hand, if the primary processed data for the required period has been accumulated, the center 3 generates secondary processed data by the secondary processing unit 62 in S4.

[0100] In S5, the center 3 stores the secondary processed data generated in S4 in the secondary processed data storage unit 45, thereby updating the secondary processed data.

[0101] In S6, the center 3 synchronizes the secondary processed data between the center 3 and the vehicle-mounted device 2 by distributing the secondary processed data updated in S5 to each vehicle using the data distribution unit 64.

[0102] As shown in FIG. 9, the center 3 further includes an application distribution unit 67 and a download data management unit 68 .

[0103] The application distribution unit 67 distributes the application stored in the application storage unit 46 to the vehicle in response to a request from the vehicle.

[0104] The download data management unit 68 manages applications installed in the vehicle and data used by the applications installed in the vehicle.

[0105] As shown in FIG. 10, the application storage unit 46 stores a plurality of applications 101, 102, 103 and a plurality of application data lists 111, 112, 113 that are registered in the center 3 by application developers.

[0106] The usage data lists 111, 112, and 113 each include information indicating one or more items of secondary processed data (hereinafter referred to as secondary processed data item information) used by the applications 101, 102, and 103. Examples of the items of secondary processed data include the above-mentioned "traffic jam," "expressway," "driving," "power off," "ACC usage status," "driver type," and "number of occupants."

[0107] The usage data lists 111 to 113 are created by application developers and registered in the center 3. Although three applications 101, 102, and 103 are shown in Fig. 10, the number of applications registered in the center 3 may be four or more.

[0108] Download data management unit 68 stores download management data 121, 122, 123, and 124 for each of a plurality of vehicles managed by center 3. Although four pieces of download management data 121, 122, 123, and 124 are shown in Figure 10, the number of download management data registered in download data management unit 68 may be five or more.

[0109] Download management data 121, 122, 123, and 124 correspond to vehicles whose "VIN" is "AAAA," "BBBB," "CCCC," and "DDDD," respectively.

[0110] The download management data 121, 122, 123, and 124 include application lists 131, 132, 133, and 134 and download data lists 141, 142, 143, and 144, respectively.

[0111] The application lists 131, 132, 133, and 134 each contain information (hereinafter, application identification information) for identifying one or more applications downloaded to vehicles with "VIN" of "AAAA," "BBBB," "CCCC," and "DDDD."

[0112] The download data lists 141, 142, 143, and 144 each include one or more secondary processed data item information used by one or more applications listed in the application lists 131, 132, 133, and 134, respectively.

[0113] For example, if a vehicle with a "VIN" of "AAAA" downloads the applications 101 and 102, information indicating the applications 101 and 102 is stored in the application list 131. In addition, the download data list 141 stores information that integrates one or more pieces of secondary processed data item information included in the usage data list 111 and one or more pieces of secondary processed data item information included in the usage data list 112.

[0114] As indicated by arrow L1 in Fig. 9 , download data management unit 68 acquires information indicating the downloaded applications from application distribution unit 67. Then, download data management unit 68 creates an application list for each vehicle based on the information indicating the downloaded applications. Furthermore, download data management unit 68 acquires one or more application data lists from application storage unit 46 based on application identification information included in the created application list, as indicated by arrow L2 in Fig. 9 . Then, download data management unit 68 creates a download data list for each vehicle based on the acquired one or more application data lists.

[0115] 9, the data distribution unit 64 refers to the download data list stored in the download data management unit 68. Furthermore, as shown by arrow L4 in FIG. 9, the data distribution unit 64 extracts only the secondary processed data required by each vehicle from the secondary processed data storage unit 45 and distributes it to each vehicle.

[0116] As a result, the secondary processed data used by the installed application is stored in the download data storage unit 28 of the in-vehicle device 2 of each vehicle, as shown in Figure 11. Figure 11 shows a state in which a personal profile 151 storing one or more secondary processed data corresponding to a driver whose "personal ID" is "1111" and a personal profile 152 storing one or more secondary processed data corresponding to a driver whose "personal ID" is "2222" are stored in a vehicle whose "VIN" is "AAAA." Note that the one or more secondary processed data items are the same in the personal profile 151 and the personal profile 152.

[0117] Next, a description will be given of the procedure of the profile download process executed by the microcomputer 11 of the in-vehicle device 2. The profile download process is a process that starts after the vehicle switches from the IG OFF state to the IG ON state.

[0118] When the profile download process is executed, the CPU 21 of the microcomputer 11 identifies the driver in S10 as shown in Fig. 12. Specifically, the CPU 21 identifies the driver by, for example, analyzing image data acquired by photographing the face of the person sitting in the driver's seat. Alternatively, the CPU 21 may identify the driver by performing data communication with a device (e.g., a smartphone) carried by the person sitting in the driver's seat.

[0119] In S20, the CPU 21 determines whether or not a personal profile corresponding to the driver identified in S10 is stored in the in-vehicle device 2.

[0120] If a personal profile corresponding to the driver identified in S10 is stored in the in-vehicle device 2, the CPU 21 ends the profile download process. On the other hand, if a personal profile corresponding to the driver identified in S10 is not stored in the in-vehicle device 2, the CPU 21 downloads the personal profile corresponding to the driver identified in S10 from the center 3 in S30, and ends the profile download process.

[0121] Next, a description will be given of the procedure of the synchronization process executed by the control unit 31 of the center 3. The synchronization process is a process that is started when the secondary processed data stored in the secondary processed data storage unit 45 is updated.

[0122] When the synchronization process is executed, the CPU 41 of the control unit 31 determines whether there is a difference between the secondary processed data on the center 3 side and the secondary processed data on the vehicle side in S110, as shown in Fig. 13. Specifically, the CPU 41 determines that there is a difference between the secondary processed data on the center 3 side and the secondary processed data on the vehicle side when the version of the secondary processed data stored in the center 3 (hereinafter referred to as the center version) does not match the version of the secondary processed data stored in the vehicle side (hereinafter referred to as the vehicle version).

[0123] That is, the center 3 determines for each vehicle whether the secondary processing data stored in the secondary processing data storage unit 45 has been updated, and if the secondary processing data has been updated, updates the version of the secondary processing data for the vehicle for which the secondary processing data has been updated. Furthermore, when the in-vehicle device 2 installed in the vehicle downloads secondary processing data from the center 3, it uploads version information indicating the version added to the downloaded secondary processing data to the center 3. This allows the center 3 to determine for each vehicle whether the center-side version and the vehicle-side version match.

[0124] If there is no difference between the secondary processed data on the center 3 side and the secondary processed data on the vehicle side in S110, the CPU 41 ends the synchronization process. On the other hand, if there is a difference between the secondary processed data on the center 3 side and the secondary processed data on the vehicle side, the CPU 41 downloads the latest secondary processed data corresponding to the vehicle to the in-vehicle device 2 in S120 and ends the synchronization process.

[0125] Next, a description will be given of the procedure of the deletion notification process executed by the microcomputer 11 of the in-vehicle device 2. The deletion notification process is a process that is repeatedly executed while the in-vehicle device 2 is in operation.

[0126] 14, the CPU 21 of the microcomputer 11 determines in S210 whether or not the application has been deleted in the vehicle in which the in-vehicle device 2 is installed. If the application has not been deleted, the CPU 21 ends the deletion notification process.

[0127] On the other hand, if the application has been deleted, the CPU 21 transmits an application deletion notification including application identification information for identifying the deleted application to the center 3 in S220, and ends the deletion notification process.

[0128] Next, a description will be given of the procedure of the deletion / update process executed by the control unit 31 of the center 3. The deletion / update process is a process that is repeatedly executed while the center 3 is in operation.

[0129] 15, when the deletion update process is executed, the CPU 41 of the control unit 31 determines in S310 whether or not an application deletion notification has been received from the in-car device 2. If an application deletion notification has not been received, the CPU 41 ends the deletion update process.

[0130] On the other hand, if an application deletion notification has been received, the CPU 41 updates the application list and download data list corresponding to the vehicle (hereinafter referred to as the target vehicle) equipped with the in-vehicle device 2 that is the sender of the application deletion notification at S320. Specifically, the CPU 41 updates the application list by deleting from the application list the applications identified by the application identification information included in the application deletion notification. Furthermore, the CPU 41 acquires one or more application data lists from the application storage unit 46 based on the application identification information included in the updated application list, and creates a download data list based on the acquired one or more application data lists, thereby updating the download data list.

[0131] In S330, the CPU 41 refers to the download data list updated in S320, extracts only the secondary processing data required for the target vehicle from the secondary processing data storage unit 45, downloads it to the target vehicle, and terminates the deletion and update process.

[0132] The mobility IoT system 1 configured in this manner includes a plurality of on-board devices 2 mounted on each of a plurality of vehicles, and a center 3 configured to perform data communication between the plurality of on-board devices 2.

[0133] The center 3 includes a primary processing data acquisition unit 61 , a data management unit 63 , a download data management unit 68 , and a data distribution unit 64 .

[0134] The primary processed data acquisition unit 61 is configured to acquire the primary processed data and image data from the in-vehicle device 2 .

[0135] The data management unit 63 is configured to manage multiple secondary processed data related to the driver's personal characteristics for each vehicle driver based on the multiple primary processed data and image data acquired by the primary processed data acquisition unit 61.

[0136] The download data management unit 68 is configured to manage, for each vehicle, one or more pieces of application identification information for identifying one or more applications (e.g., service application 16) downloaded to the vehicle, and one or more pieces of secondary processing data item information for identifying one or more pieces of secondary processing data used by the one or more applications downloaded to the vehicle.

[0137] The data distribution unit 64 is configured to distribute, to the in-vehicle device 2, one or more pieces of secondary processed data corresponding to one or more pieces of secondary processed data item information.

[0138] The in-vehicle device 2 includes a download data storage unit 28 and a data linking unit 53 .

[0139] The download data storage unit 28 is configured to store the secondary processed data downloaded from the center 3 for each driver.

[0140] The data linking unit 53 is configured to manage access to one or more secondary processed data by one or more applications downloaded to the vehicle.

[0141] In this mobility IoT system 1, the center 3 can provide the vehicle with the secondary processed data used by the application downloaded to the vehicle for each driver. This eliminates the need for the application downloaded to the vehicle to newly generate the secondary processed data used by the application for each driver using the primary processed data and image data acquired from the vehicle. This makes it easier for the mobility IoT system 1 to use vehicle data.

[0142] The multiple secondary processed data managed by the data management unit 63 include data generated by extracting feature amounts using one or multiple primary processed data. The feature amounts include “traffic jam,” “expressway,” “general road,” “parking lot,” “geofence,” and “day / night” from the environment model dataset 71, “driving,” “stopped,” “power off,” “ACC usage status,” and “navigation usage status” from the vehicle model dataset 72, and “number of occupants” and “driving tendency” from the human model dataset 73.

[0143] The plurality of secondary processed data managed by the data management unit 63 includes data generated by extracting feature amounts by performing image analysis on one or more image data. The feature amounts include "face direction" and "drowsiness" of the human model data set 73.

[0144] Furthermore, the plurality of secondary processed data are managed by the data management unit 63 in a state where they are associated with a "personal ID" that identifies the driver corresponding to the plurality of secondary processed data and a "VIN" that identifies the vehicle corresponding to the plurality of secondary processed data. In such a mobility IoT system 1, an application that operates in accordance with the characteristics of an individual can easily switch users by referring to the secondary processed data associated with the "personal ID" corresponding to the target individual.

[0145] The plurality of secondary processed data includes "ACC personal settings" and "ADAS personal settings" used in a specific application. The plurality of secondary processed data are stored in the download data storage unit 28 as personal profiles 151, 152, .... In such a mobility IoT system 1, an application that operates in accordance with the characteristics of an individual can easily switch users by referencing the personal profile corresponding to the target individual.

[0146] Furthermore, the secondary processing unit 62 of the center 3 generates standard driver characteristic data indicating the standard characteristics of the drivers of the multiple vehicles, multiple driver individual characteristic data for each of the multiple drivers, and good driver characteristic data based on the multiple primary processed data and image data acquired from the multiple on-board devices 2 mounted on each of the multiple vehicles. As a result, such a mobility IoT system 1 can provide the driver with services that take into account the standard driver characteristics or good driver characteristics by having the application refer to the standard driver characteristic data or the good driver characteristic data, and further, can provide the driver with services tailored to the individual characteristics by having the application refer to the driver individual characteristic data.

[0147] When an application is deleted from the vehicle, the in-vehicle device 2 transmits an application deletion notification to the center 3, the application deletion notification including application identification information (hereinafter, deleted application identification information) that identifies the deleted application. When the center 3 receives the application deletion notification, the center 3 updates one or more pieces of application identification information and one or more pieces of secondary processed data item information managed by the download data management unit 68 based on the deleted application identification information included in the application deletion notification. In this mobility IoT system 1, when an application is deleted from the vehicle, it is possible to prevent the secondary processed data used by the deleted application from being unnecessarily downloaded to the vehicle.

[0148] In the above-described embodiment, the mobility IoT system 1 corresponds to a data management system.

[0149] Furthermore, the primary processed data and image data correspond to vehicle data, the primary processed data acquisition unit 61 corresponds to an acquisition unit, the secondary processed data corresponds to personal characteristic data, and the data management unit 63 corresponds to a first management unit.

[0150] Furthermore, the service application 16 corresponds to an application, the application lists 131 to 134 correspond to application specifying information, the download data lists 141 to 144 correspond to personal characteristic data specifying information, and the download data management section 68 corresponds to a second management section.

[0151] The download data storage unit 28 corresponds to a data storage unit, and the data linking unit 53 corresponds to an access management unit.

[0152] In addition, "personal ID" corresponds to personal identification information, "VIN" corresponds to vehicle identification information, "ACC personal settings" and "ADAS personal settings" correspond to setting information, standard driver characteristic data corresponds to standard characteristic data, driver personal characteristic data corresponds to personal characteristic data, secondary processing unit 62 corresponds to the generation unit, and good driver characteristic data corresponds to good characteristic data.

[0153] Moreover, S220 corresponds to the processing performed by the deletion notification unit, and S320 corresponds to the processing performed by the deletion update unit.

[0154] Second Embodiment A second embodiment of the present disclosure will be described below with reference to the drawings. In the second embodiment, differences from the first embodiment will be described. The same reference numerals will be used to designate common components.

[0155] As shown in FIG. 16, the mobility IoT system 1 of the second embodiment differs from the first embodiment in that the configuration of the center 3 is changed.

[0156] The center 3 of the second embodiment differs from the first embodiment in that the storage unit 33 further includes a learning model storage unit 47 .

[0157] 17, the center 3 of the second embodiment differs from the first embodiment in that it includes a learning unit 65 and a model distribution unit 66. Note that the secondary processing unit 62 and the data distribution unit 64 are not shown in FIG.

[0158] The learning unit 65 uses the plurality of primary processed data and image data stored in the primary processed data storage unit 44 to generate a learning model that can be used in common by the service application 16 and the service providing server 4. The learning unit 65 starts learning the learning model when the required period of primary processed data has been accumulated.

[0159] The learning unit 65 stores the generated learning model in the learning model storage unit 47 .

[0160] The learning unit 65 generates a learning model that learns individual behavioral characteristics (e.g., the destination of the vehicle driver) by inputting, for example, the vehicle's current location information, the current time, the number of passengers, and the navigation destination. Such a learning model can estimate the vehicle's destination based on the vehicle's current location information, the current time, and the number of passengers. The destination information estimated by the learning model can be used for services such as automatically notifying the driver of the required time to reach the destination or suggesting an alternative route if the route to the destination is congested.

[0161] The learning unit 65 generates one common learning model 81 and multiple individual adaptation learning models 82. The common learning model 81 is a learning model that can be used regardless of the vehicle and driver by using vehicle data and image data acquired from multiple vehicles. The individual adaptation learning model 82 is a learning model that is adapted to each of multiple drivers by using vehicle data and image data individually for multiple vehicles and multiple drivers.

[0162] The learning unit 65 also generates a learning model for estimating the driver's emotions by performing machine learning using, for example, driver image data generated by photographing the driver and vehicle operation data (for example, steering operation data, accelerator operation data, brake operation data, ADAS function data, and air conditioner control data). Examples of the driver's emotions include impatience, irritation, tension, and relaxation.

[0163] The data management unit 63 manages the learning models stored in the learning model storage unit 47. Specifically, the data management unit 63 provides the learning models corresponding to each vehicle to the model distribution unit 66, and provides the learning models required by the service providing server 4 to the service providing server 4.

[0164] The model distribution unit 66 distributes to each in-vehicle device 2 only the learning models required by each vehicle from among the multiple learning models stored in the learning model storage unit 47 .

[0165] That is, the usage data list stored in the application storage unit 46 may include learning model specification information that specifies the learning model used by the corresponding application. Therefore, the download data list stored in the download data management unit 68 may include learning model specification information.

[0166] Therefore, the model distribution unit 66 refers to the download data list to extract only the learning models required by each vehicle from the learning model storage unit 47 and distribute them to each vehicle. The model distribution unit 66 may distribute the common learning model 81 stored in the learning model storage unit 47 to each in-vehicle device 2.

[0167] The data linking unit 53 of the in-vehicle device 2 stores the learning model downloaded from the center 3 in the download data storage unit 28 .

[0168] Next, a procedure in which the center 3 generates a learning model and synchronizes it with the in-vehicle device 2 will be described.

[0169] As shown in FIG. 18, in S410, the in-vehicle device 2 acquires vehicle data from the vehicle using the data acquisition unit 51.

[0170] In S420, the in-vehicle device 2 determines whether the acquired vehicle data is data that needs to be processed for model learning. Specifically, for example, if the vehicle data is image data, it is determined that the data does not need to be processed, and if the vehicle data is not image data, it is determined that the data needs to be processed.

[0171] If the data does not require processing for model learning, the in-vehicle device 2 uploads the acquired vehicle data to the center 3 via the data linking unit 53 .

[0172] On the other hand, if the data requires processing for model learning, the in-vehicle device 2 processes the vehicle data acquired by the data acquisition unit 51 into primary processed data using the primary processing unit 52 at S430, and uploads the primary processed data generated by the primary processing unit 52 to the center 3 using the data linkage unit 53.

[0173] In S440, the center 3 determines whether the primary processed data and image data for the required period have been accumulated. If the primary processed data for the required period has not been accumulated, the in-vehicle device 2 repeats the processes of S410 to S430. On the other hand, if the primary processed data for the required period has been accumulated, the center 3 generates a learning model by the learning unit 65 in S450.

[0174] In S460, the center 3 stores the learning model generated in S450 in the learning model storage unit 47, thereby updating the learning model.

[0175] In S470, the center 3 synchronizes the learning model between the center 3 and the in-vehicle device 2 by distributing the learning model updated in S460 to each vehicle using the model distribution unit 66.

[0176] The mobility IoT system 1 configured in this manner includes a plurality of on-board devices 2 mounted on each of a plurality of vehicles, and a center 3 configured to perform data communication between the plurality of on-board devices 2.

[0177] The center 3 includes a primary processing data acquisition unit 61 , a data management unit 63 , a download data management unit 68 , and a data distribution unit 64 .

[0178] The primary processed data acquisition unit 61 is configured to acquire the primary processed data and image data from the in-vehicle device 2 .

[0179] The data management unit 63 is configured to manage multiple learning models related to the driver's personal characteristics for each vehicle driver based on the multiple primary processed data and image data acquired by the primary processed data acquisition unit 61.

[0180] The download data management unit 68 is configured to manage, for each vehicle, one or more application identification information for identifying one or more applications (e.g., service application 16) downloaded to the vehicle, and one or more learning model identification information for identifying one or more learning models used by the one or more applications downloaded to the vehicle.

[0181] The data distribution unit 64 is configured to distribute one or more learning models corresponding to one or more pieces of learning model identification information to the in-vehicle device 2.

[0182] The in-vehicle device 2 includes a download data storage unit 28 and a data linking unit 53 .

[0183] The download data storage unit 28 is configured to store the learning model downloaded from the center 3 for each driver.

[0184] The data linking unit 53 is configured to manage access to one or more learning models by one or more applications downloaded to the vehicle.

[0185] In this mobility IoT system 1, the center 3 can provide the vehicle with a learning model for each driver that is used by an application downloaded to the vehicle. This eliminates the need for the application downloaded to the vehicle to generate a new learning model for each driver using the primary processed data and image data acquired from the vehicle. This allows the mobility IoT system 1 to easily use vehicle data.

[0186] The multiple learning models managed by the data management unit 63 include a learning model that learns the behavioral characteristics of the vehicle driver (i.e., the "vehicle's destination") using one or more primary processed data and image data.

[0187] In the embodiment described above, the individually adapted learning model 82 corresponds to the individual characteristic data, and the learning model specifying information corresponds to the individual characteristic data specifying information.

[0188] 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 modifications.

[0189] [Modification 1] In the first embodiment, the in-vehicle device 2 generates the primary processed data from the vehicle data. However, in the first embodiment, the center 3 may collect vehicle data from the in-vehicle device 2 and generate the primary processed data from the collected vehicle data, thereby acquiring the primary processed data.

[0190] [Modification 2] In the above embodiment, the synchronization process is started when the secondary processed data stored in the secondary processed data storage unit 45 is updated. However, the synchronization process may be started when an application downloaded to the vehicle is terminated or started, when an electronic control unit in the vehicle is connected to Wi-Fi, or when an electronic control unit in the vehicle is connected to Bluetooth. Wi-Fi is a registered trademark. Bluetooth is a registered trademark.

[0191] The microcomputer 11, the control unit 31, and the methods described herein may be implemented by a special-purpose computer configured by configuring a processor and memory programmed to execute one or more functions embodied in a computer program. Alternatively, the microcomputer 11, the control unit 31, and the methods described herein may be implemented by a special-purpose computer configured by configuring a processor with one or more dedicated hardware logic circuits. Alternatively, the microcomputer 11, the control unit 31, and the methods described herein may be implemented by one or more special-purpose computers configured by combining a processor and memory programmed to execute one or more functions with a processor configured with one or more hardware logic circuits. Furthermore, the computer program may be stored as instructions executed by a computer on a computer-readable non-transitory tangible recording medium. The methods for implementing the functions of each unit included in the microcomputer 11 and the control unit 31 do not necessarily need to include software; all of the functions may be implemented using one or more hardware components.

[0192] 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. Furthermore, multiple functions of multiple components may be realized by one component, or one function realized by multiple components may be realized by one component. Furthermore, part of the configuration of the above embodiments may be omitted. Furthermore, 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.

[0193] In addition to the above-mentioned in-vehicle device 2 and center 3, the present disclosure can also be realized in various forms, such as a system having the in-vehicle device 2 and center 3 as components, a program for causing a computer to function as the in-vehicle device 2 and center 3, a non-transient physical recording medium such as a semiconductor memory on which this program is recorded, and a data management method. [Technical Idea Disclosed in the Present Specification] [Item 1] A data management system (1) comprising a plurality of on-board devices (2) mounted on a plurality of vehicles, respectively, and a center (3) configured to perform data communication between the plurality of on-board devices, wherein the center comprises: an acquisition unit (61) configured to acquire a plurality of vehicle data relating to the vehicles from the on-board devices; a first management unit (63) configured to manage a plurality of personal characteristic data relating to personal characteristics of the drivers for each driver of the vehicles based on the plurality of vehicle data acquired by the acquisition unit; a second management unit (68) configured to manage, for each vehicle, one or more application identification information for identifying one or more applications (16) downloaded to the vehicle, and one or more personal characteristic data identification information for identifying the one or more personal characteristic data used by the one or more applications downloaded to the vehicle; and a data distribution unit (64) configured to distribute the one or more personal characteristic data corresponding to the one or more personal characteristic data identification information to the on-board devices, wherein the on-board devices: A data management system comprising: a data storage unit (28) configured to store one or more of the personal characteristic data downloaded from the center for each of the drivers; and an access management unit (53) configured to manage access to the one or more of the personal characteristic data by one or more of the applications downloaded to the vehicle.

[0194] [Item 2] The data management system according to Item 1, wherein the plurality of personal characteristic data managed by the first management unit includes data generated by extracting feature amounts using one or more of the vehicle data.

[0195] [Item 3] The data management system according to item 1 or 2, wherein the plurality of pieces of personal characteristic data managed by the first management unit include data generated by extracting feature amounts by performing image analysis of image data included in one or more pieces of vehicle data.

[0196] [Item 4] The data management system according to any one of Items 1 to 3, wherein the plurality of pieces of personal characteristic data managed by the first management unit includes a learning model that learns behavioral characteristics of the driver of the vehicle using one or more pieces of vehicle data.

[0197] [Item 5] The data management system according to any one of items 1 to 4, wherein the plurality of personal characteristic data are managed by the first management unit in a state where the plurality of personal characteristic data are associated with personal identification information that identifies the driver corresponding to the plurality of personal characteristic data and vehicle identification information that identifies the vehicle corresponding to the personal characteristic data.

[0198] [Item 6] A data management system according to any one of items 1 to 5, wherein the plurality of pieces of personal characteristic data include setting information used in a specific application, and the plurality of pieces of personal characteristic data are stored in the data storage unit as a personal profile.

[0199] [Item 7] A data management system according to any one of items 1 to 6, wherein the center further comprises a generation unit (62) configured to generate standard characteristic data indicating standard characteristics of the drivers of the plurality of vehicles and the plurality of personal characteristic data for each of the plurality of drivers based on the plurality of vehicle data acquired from the plurality of on-board devices mounted on each of the plurality of vehicles, and wherein the plurality of personal characteristic data are each stored in the data storage unit of the on-board device mounted on a corresponding one of the vehicles.

[0200] [Item 8] The data management system according to Item 7, wherein the generation unit is further configured to generate excellent characteristic data indicating excellent characteristics of the driver based on the plurality of vehicle data acquired from the plurality of on-board devices mounted on each of the plurality of vehicles.

[0201] [Item 9] A data management system according to any one of items 1 to 8, wherein the in-vehicle device further comprises a deletion notification unit (S220) configured to, when the application is deleted from the vehicle, transmit to the center an application deletion notification including deleted application identification information that identifies the deleted application, and the center further comprises a deletion update unit (S320) configured, when receiving the application deletion notification, to update one or more pieces of application identification information and one or more pieces of personal characteristic data identification information managed by the second management unit based on the deleted application identification information included in the application deletion notification.

[0202] [Item 10] A center (3) configured to perform data communication with a plurality of on-board devices (2) mounted on a plurality of vehicles, the center comprising: an acquisition unit (61) configured to acquire a plurality of vehicle data related to the vehicles from the on-board devices; a first management unit (63) configured to manage a plurality of personal characteristic data related to personal characteristics of the drivers for each driver of the vehicles based on the plurality of vehicle data acquired by the acquisition unit; a second management unit (68) configured to manage, for each vehicle, one or more application identification information for identifying one or more applications (16) downloaded to the vehicle and one or more personal characteristic data identification information for identifying the one or more personal characteristic data used by the one or more applications downloaded to the vehicle; and a data distribution unit (64) configured to distribute the one or more personal characteristic data corresponding to the one or more personal characteristic data identification information to the on-board devices.

[0203] [Item 11] A data management program for causing a computer of a center (3) configured to perform data communication with a plurality of in-vehicle devices (2) mounted on each of a plurality of vehicles to function as: an acquisition unit (61) configured to acquire a plurality of vehicle data related to the vehicles from the in-vehicle devices; a first management unit (63) configured to manage a plurality of personal characteristic data related to the personal characteristics of the driver for each driver of the vehicle based on the plurality of vehicle data acquired by the acquisition unit; a second management unit (68) configured to manage, for each vehicle, one or more application identification information for identifying one or more applications (16) downloaded to the vehicle and one or more personal characteristic data identification information for identifying the one or more personal characteristic data used by the one or more applications downloaded to the vehicle; and a data distribution unit (64) configured to distribute the one or more personal characteristic data corresponding to the one or more personal characteristic data identification information to the in-vehicle devices.

[0204] [Item 12] A data management method executed in a data management system (1) including a plurality of on-board devices (2) mounted on each of a plurality of vehicles and a center (3) configured to perform data communication between the plurality of on-board devices, wherein the center: acquires a plurality of vehicle data related to the vehicles from the on-board devices; manages a plurality of personal characteristic data related to personal characteristics of the drivers for each driver of the vehicles based on the acquired plurality of vehicle data; manages, for each vehicle, one or more application identification information for identifying one or more applications (16) downloaded to the vehicles and one or more personal characteristic data identification information for identifying the one or more personal characteristic data used by the one or more applications downloaded to the vehicles; downloads the one or more personal characteristic data corresponding to the one or more personal characteristic data identification information to the on-board devices; the on-board devices: store the one or more personal characteristic data downloaded from the center for each driver; and manages access to the one or more personal characteristic data by the one or more applications downloaded to the vehicles.

Claims

1. A data management system (1) comprising a plurality of on-board devices (2) mounted on a plurality of vehicles, respectively, and a center (3) configured to perform data communication between the plurality of on-board devices, wherein the center comprises: an acquisition unit (61) configured to acquire a plurality of vehicle data relating to the vehicles from the on-board devices; a first management unit (63) configured to manage a plurality of personal characteristic data relating to the personal characteristics of each driver of the vehicle based on the plurality of vehicle data acquired by the acquisition unit; a second management unit (68) configured to manage, for each vehicle, one or more application identification information for identifying one or more applications (16) downloaded to the vehicle and one or more personal characteristic data identification information for identifying the one or more personal characteristic data used by the one or more applications downloaded to the vehicle; and a data distribution unit (64) configured to distribute the one or more personal characteristic data corresponding to the one or more personal characteristic data identification information to the on-board devices, wherein the on-board devices: A data management system comprising: a data storage unit (28) configured to store one or more of the personal characteristic data downloaded from the center for each of the drivers; and an access management unit (53) configured to manage access to the one or more of the personal characteristic data by one or more of the applications downloaded to the vehicle.

2. A data management system according to claim 1, wherein the plurality of personal characteristic data managed by the first management unit includes data generated by extracting features using one or more of the vehicle data.

3. A data management system as claimed in claim 1 or claim 2, wherein the plurality of personal characteristic data managed by the first management unit includes data generated by extracting features by performing image analysis of image data included in one or more of the vehicle data.

4. A data management system as described in claim 1 or claim 2, wherein the plurality of personal characteristic data managed by the first management unit includes a learning model that learns the behavioral characteristics of the driver of the vehicle using one or more of the vehicle data.

5. A data management system as described in claim 1 or claim 2, wherein the plurality of personal characteristic data are managed by the first management unit in a state where they are associated with personal identification information that identifies the driver corresponding to the plurality of personal characteristic data and vehicle identification information that identifies the vehicle corresponding to the personal characteristic data.

6. A data management system according to claim 1 or claim 2, wherein the plurality of personal characteristic data includes setting information used in a specific application, and the plurality of personal characteristic data is stored in the data storage unit as a personal profile.

7. A data management system as set forth in claim 1 or claim 2, wherein the center further comprises a generation unit (62) configured to generate standard characteristic data indicating standard characteristics of the drivers of the plurality of vehicles and a plurality of personal characteristic data for each of the plurality of drivers based on a plurality of vehicle data acquired from a plurality of on-board devices mounted on each of the plurality of vehicles, and wherein each of the plurality of personal characteristic data is stored in the data storage unit of the on-board device mounted on the corresponding vehicle.

8. A data management system as set forth in claim 7, wherein the generation unit is further configured to generate excellent characteristic data indicating the characteristics of an excellent driver based on a plurality of vehicle data acquired from a plurality of on-board devices mounted on each of a plurality of the vehicles.

9. A data management system as claimed in claim 1 or claim 2, wherein the in-vehicle device further comprises a deletion notification unit (S220) configured to, when an application is deleted from the vehicle, send to the center an application deletion notification including deleted application identification information that identifies the deleted application, and the center further comprises a deletion update unit (S320) configured, upon receiving the application deletion notification, to update one or more of the application identification information and one or more of the personal characteristic data identification information managed by the second management unit based on the deleted application identification information included in the application deletion notification.

10. A center (3) configured to perform data communication with a plurality of on-board devices (2) mounted on a plurality of vehicles, comprising: an acquisition unit (61) configured to acquire a plurality of vehicle data related to the vehicles from the on-board devices; a first management unit (63) configured to manage a plurality of personal characteristic data related to the personal characteristics of each driver of the vehicle based on the plurality of vehicle data acquired by the acquisition unit; a second management unit (68) configured to manage, for each vehicle, one or more application identification information for identifying one or more applications (16) downloaded to the vehicle and one or more personal characteristic data identification information for identifying one or more of the personal characteristic data used by the one or more applications downloaded to the vehicle; and a data distribution unit (64) configured to distribute one or more of the personal characteristic data corresponding to one or more of the personal characteristic data identification information to the on-board devices.

11. A data management program for causing a computer of a center (3) configured to perform data communication with a plurality of on-board devices (2) mounted on each of a plurality of vehicles to function as: an acquisition unit (61) configured to acquire a plurality of vehicle data related to the vehicles from the on-board devices; a first management unit (63) configured to manage a plurality of personal characteristic data related to the personal characteristics of each driver of the vehicle based on the plurality of vehicle data acquired by the acquisition unit; a second management unit (68) configured to manage, for each vehicle, one or more application identification information for identifying one or more applications (16) downloaded to the vehicle and one or more personal characteristic data identification information for identifying the one or more personal characteristic data used by the one or more applications downloaded to the vehicle; and a data distribution unit (64) configured to distribute the one or more personal characteristic data corresponding to the one or more personal characteristic data identification information to the on-board devices.

12. A data management method executed by a data management system (1) comprising a plurality of on-board devices (2) mounted on each of a plurality of vehicles and a center (3) configured to perform data communication between the plurality of on-board devices, wherein the center: acquires a plurality of vehicle data related to the vehicles from the on-board devices; manages a plurality of personal characteristic data related to the personal characteristics of the driver for each driver of the vehicle based on the acquired plurality of vehicle data; manages, for each vehicle, one or more application identification information for identifying one or more applications (16) downloaded to the vehicle and one or more personal characteristic data identification information for identifying the one or more personal characteristic data used by the one or more applications downloaded to the vehicle; downloads the one or more personal characteristic data corresponding to the one or more personal characteristic data identification information to the on-board device; the on-board device stores the one or more personal characteristic data downloaded from the center for each driver; and manages access to the one or more personal characteristic data by the one or more applications downloaded to the vehicle.

Images