Data registration system

Abstract

Provided is a data registration system capable of efficiently registering highly effective data related to a vehicle or the like. The data registration system includes an integration processing server and an integrated database server. The integration processing server creates a data mart having an FCD, weather data, vehicle condition data, fuel economy data, navigation data, a vehicle ID, and a user ID which are linked to one another and creates an encrypted data mart by compressing the data mart by the Lzo algorithm and encrypting the compressed data mart. The integrated database server stores the encrypted data mart in a storage region.

Claims

1. A data registration system comprising: a data reception unit to which a plurality of types of data and vehicle-identifying data for identification of at least one of a vehicle and an owner of the vehicle are input through a network, the plurality of types of data including movement status data representing a time-series movement status of a mobile station, consumption rate data representing an energy consumption rate of the vehicle moving together with the mobile station, navigation data representing a navigation computation result and a setting state in the vehicle, and weather data representing weather in a region in which the mobile station existed; a data group creation unit which creates a data group having the movement status data, the consumption rate data, the navigation data, the weather data, and the vehicle-identifying data that are linked to one another; a registered data creation unit which compresses the data group by a predetermined compression algorithm and creates registered data using the compressed data group; and a data storage unit which stores the registered data in a storage region, wherein the data group creation unit creates a first data group having the vehicle-identifying data, the movement status data, and the consumption rate data that are linked to one another, a second data group having the vehicle-identifying data, the movement status data, and the navigation data that are linked to one another, and a third data group having the movement status data and the weather data that are linked to each other, and creates the data group using the first to third data groups, wherein the movement status data and the navigation data each comprise a vehicle position at a time of sampling as a piece of data, and if the movement status data and the navigation data are not coincident in the vehicle position at the time of sampling with each other in a case of creating the second data group, the data group creation unit links one piece of the movement status data and one piece of the navigation data which are closest in the vehicle position at the time of sampling to each other according to common user information data.

2. The data registration system according to claim 1, wherein the movement status data and the navigation data each comprise a time stamp at a time of sampling and a vehicle position at the time of sampling as pieces of data, and in a case where there are a plurality of data having a same vehicle position at the time of sampling in the movement status data and the navigation data in a case of creating the second data group, the data group creation unit links data which are closest in the time stamp at the time of sampling to each other among the plurality of data.

3. The data registration system according to claim 1, wherein the movement status data and the navigation data each comprise a time stamp at the time of sampling and the vehicle position at the time of sampling as pieces of data, and in a case where there are a plurality of data having a same vehicle position at the time of sampling in the movement status data and the navigation data in a case of creating the second data group, the data group creation unit links data which are closest in the time stamp at the time of sampling to each other among the plurality of data.

4. The data registration system according to claim 1, wherein the plurality of types of data further include vehicle condition data representing at least one of a manufacturing condition and a repair condition of the vehicle, and the data group creation unit creates the data group by further linking the vehicle condition data in addition to the movement status data, the consumption rate data, the navigation data, the weather data, and the vehicle-identifying data.

5. The data registration system according to claim 4, wherein the data group creation unit creates a first data group having the vehicle-identifying data, the movement status data, and the consumption rate data that are linked to one another, a second data group having the vehicle-identifying data, the movement status data, and the navigation data that are linked to one another, a third data group having the movement status data and the weather data that are linked to each other, and a fourth data group having the vehicle-identifying data, the movement status data, and the vehicle condition data that are linked to one another, and creates the data group using the first to fourth data groups.

6. The data registration system according to claim 5, wherein the movement status data and the navigation data each comprise a vehicle position at a time of sampling as a piece of data, and if the movement status data and the navigation data are not coincident in the vehicle position at the time of sampling with each other in case of creating the second data group, the data group creation unit links one piece of the movement status data and one piece of the navigation data which are closest in the vehicle position at the time of sampling to each other.

7. The data registration system according to claim 5, wherein the movement status data and the navigation data each comprise a time stamp at a time of sampling and a vehicle position at the time of sampling as pieces of data, and in a case where there are a plurality of data having a same vehicle position at the time of sampling in the movement status data and the navigation data in a case of creating the second data group, the data group creation unit links data which are closest in the time stamp at the time of sampling to each other among the plurality of data.

8. The data registration system according to claim 6, wherein the movement status data and the navigation data each comprise a time stamp at the time of sampling and the vehicle position at the time of sampling as pieces of data, and in a case where there are a plurality of data having a same vehicle position at the time of sampling in the movement status data and the navigation data in the case of creating the second data group, the data group creation unit links data which are closest in the time stamp at the time of sampling to each other among the plurality of data.

9. The data registration system according to claim 1, wherein the registered data creation unit creates the registered data by encrypting the compressed data group by a predetermined encryption algorithm.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

(1) FIG. 1 is a diagram schematically showing a configuration of a data registration system according to one embodiment of the present invention;

(2) FIG. 2 is a flowchart showing a linked data creation process;

(3) FIG. 3 is a flowchart showing a data integration process;

(4) FIG. 4 is a flowchart showing an FCD-navigation provisional data mart creation process;

(5) FIG. 5 is a flowchart showing an encrypted data mart creation process; and

(6) FIG. 6 is a flowchart showing a data storage process.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

(7) A data registration system according to one embodiment of the present invention will be described below with reference to the drawings. As shown in FIG. 1, a data registration system 1 according to the present embodiment comprises a data processing server 2, an integration processing server 3, and an integrated database server 4.

(8) Each of the servers 2 to 4 comprises a processor, a memory, an I/O interface, and the like and is configured to be capable of executing various types of arithmetic processing on the basis of an arithmetic program in the memory and I/O data.

(9) The data processing server 2 executes a linked data creation process (to be described later), and the like and stores a large number of pieces of user information data in a storage region. Each piece of user information data is obtained by linking a piece of personal information of a user of a vehicle, a user registration date, a user ID, and a vehicle ID to one another and is created using the pieces of data when the pieces of data are input via an input interface (not shown) by a server administrator. Note in the present embodiment that the data processing server 2 corresponds to a data reception unit and that a user ID and a vehicle ID correspond to a piece of vehicle-identifying data.

(10) A weather server 11, a large number of plants 12 (only one of which is shown), a large number of dealers 13 (only one of which is shown), navigation devices (not shown) of a large number of vehicles 14 (only one of which is shown), and the like are connected to the data processing server 2 over a network 10. The various types of pieces of data below are input from the elements. Note that the following description assumes that a power source of each vehicle 14 is an internal combustion engine.

(11) More specifically, a piece of weather data is input from the weather server 11 to the data processing server 2. The piece of weather data is obtained by linking a mesh code of a country where a vehicle is used, the weather, a time stamp at the time of measurement of the weather, and the like to one another.

(12) A piece of manufacturing data is input from each plant 12 to the data processing server 2. The piece of manufacturing data is obtained by linking a vehicle ID, a time stamp at the time of vehicle manufacture, a manufacturing plant name, a manufacturing lot number of a vehicle, and the like to one another.

(13) A piece of dealer data is input from each dealer 13 to the data processing server 2. The piece of dealer data is obtained by linking a vehicle ID, a time stamp at the time of vehicle maintenance or repair, a dealer name, vehicle maintenance details or repair details, and the like to one another. Note that a piece of manufacturing data and a piece of dealer data will be collectively called a “piece of vehicle condition data” in the following description.

(14) A piece of movement status data, a piece of fuel economy data, and a piece of navigation data are input from the navigation device (mobile station) of each vehicle 14 to the data processing server 2. The piece of movement status data, the piece of fuel economy data, and the piece of navigation data are sampled at predetermined control intervals from when an ignition switch of the vehicle 14 is turned on to when the ignition switch is turned off. Results of the sampling are input to the data processing server 2. In this case, a piece of data sampled at a time when the ignition switch is turned off is input from the navigation device to the data processing server 2 at a time when the ignition switch is turned on next time.

(15) The piece of movement status data is obtained by linking a position of the vehicle 14 which is a position (a longitude and a latitude) of a navigation device, a time stamp at the time of sampling of the position, and a user ID to one another. A piece of movement status data will be referred to as an “FCD” hereinafter. The piece of fuel economy data is obtained by linking the fuel economy of the vehicle 14, a time stamp at the time of sampling of the fuel economy, and the user ID to one another.

(16) The piece of navigation data is obtained by linking respective settings for a departure place and a destination, a result of computing a latitude and a longitude of a current place and a route from the departure place to the destination, a time stamp at the time of sampling of the pieces of data, and the user ID in the navigation device of the vehicle 14 to one another.

(17) Note that time stamps included in a piece of weather data, a piece of vehicle condition data, a piece of movement status data, a piece of fuel economy data, and a piece of navigation data when the pieces of data are input will be collectively referred to as “time stamps at the time of sampling” in the following description.

(18) The data processing server 2 creates a piece of linked data through the linked data creation process (to be described later) and outputs the piece of linked data to the integration processing server 3.

(19) The integration processing server 3 creates a data mart using pieces of linked data input from the data processing server 2 through a data integration process (to be described later) and encrypts the data mart to create an encrypted data mart, and outputs the encrypted data mart to the integrated database server 4. Note in the present embodiment that the integration processing server 3 corresponds to a data group creation unit and a registered data creation unit and that a data mart and an encrypted data mart correspond to a data group and a piece of registered data, respectively.

(20) The integrated database server 4 stores an encrypted data mart input from the integration processing server 3 in a storage region, as will be described later.

(21) The linked data creation process described earlier will be described with reference to FIG. 2. The process creates pieces of linked data using various types of pieces of data (i.e., a piece of movement status data, a piece of fuel economy data, a piece of navigation data, a piece of vehicle condition data, and a piece of weather data) input to the data processing server 2 and outputs the pieces of linked data to the integration processing server 3, and is executed at predetermined control intervals ΔT (e.g., 5 minutes) in the data processing server 2.

(22) As shown in FIG. 2, each type of piece of data input to the data processing server 2 is first read (step S1 of FIG. 2). A time stamp at the time of reading (hereinafter referred to as a “reading time stamp”) is linked to the type of piece of data read (step S2 of FIG. 2).

(23) It is then judged whether a user ID in the piece of data having the reading time stamp linked thereto coincides with a user ID in a piece of user information data stored in the data processing server 2 (step S3 of FIG. 2).

(24) If a result of the judgment is affirmative (YES in step S3 of FIG. 2), i.e., if the piece of data having the reading time stamp linked thereto is a piece of data with a user ID (an FCD, a piece of fuel economy data, or a piece of navigation data), a vehicle ID corresponding to a user ID in a coincident piece of user information data is linked to the piece of data having the reading time stamp linked thereto (step S4 of FIG. 2).

(25) The piece of linked data (i.e., the FCD, the piece of fuel economy data, or the piece of navigation data) after the above-described linking is output to the integration processing server 3 (step S5 of FIG. 2). After that, the present process ends.

(26) On the other hand, if the judgment result is negative (NO in step S3 of FIG. 2), i.e., if the piece of data having the reading time stamp linked thereto is a piece of data without a user ID (a piece of vehicle condition data or a piece of weather data), it is judged whether a vehicle ID in the piece of data having the reading time stamp linked thereto coincides with a vehicle ID in a piece of user information data stored in the data processing server 2 (step S6 of FIG. 2).

(27) If a result of the judgment is affirmative (YES in step S6 of FIG. 2), i.e., if the piece of data having the reading time stamp linked thereto is a piece of vehicle condition data with a vehicle ID, a user ID corresponding to a vehicle ID in a coincident piece of user information data is linked to the piece of vehicle condition data (step S7 of FIG. 2).

(28) The piece of linked data that is the piece of vehicle condition data after the above-described linking is output to the integration processing server 3 (step S5 of FIG. 2). After that, the present process ends.

(29) On the other hand, if the judgment result is negative (NO in step S6 of FIG. 2), i.e., if the piece of data having the reading time stamp linked thereto is a piece of weather data without a user ID and a vehicle ID, the piece of linked data that is the piece of weather data having only the reading time stamp linked thereto is output to the integration processing server 3 without any change (step S5 of FIG. 2). After that, the present process ends.

(30) The data integration process will be described with reference to FIG. 3. The process creates an encrypted data mart using pieces of linked data input from the data processing server 2 and outputs the created encrypted data mart to the integrated database server 4, and is executed at the predetermined control intervals ΔT described earlier in the integration processing server 3.

(31) As shown in FIG. 3, a piece of linked data input from the data processing server 2 is first stored in a storage region (step S20 of FIG. 3).

(32) It is then judged whether a time for encrypted data mart creation has come (step S21 of FIG. 3). The creation time is set to a predetermined time (e.g., 24:00) of a day.

(33) If a result of the judgment is negative (NO in step S21 of FIG. 3), the present process ends without doing anything.

(34) On the other hand, if the judgment result is affirmative (YES in step S21 of FIG. 3), an FCD-fuel-economy provisional data mart is created (step S22 of FIG. 3). The FCD-fuel-economy provisional data mart (a first data group) is created by searching for FCDs and pieces of fuel economy data for the last 30 days stored in the storage region using a user ID and a vehicle ID as a key and linking the FCDs and the pieces of fuel economy data to each other and created as a data group (map) having the user ID, the vehicle ID, an FCD, a piece of fuel economy data, a sampling time stamp of the piece of fuel economy data, and a reading time stamp of the piece of fuel economy data which are linked to one another.

(35) An FCD-navigation provisional data mart is then created (step S23 of FIG. 3). More specifically, the creation of the FCD-navigation provisional data mart (a second data group) is executed in the manner shown in FIG. 4.

(36) As shown in FIG. 4, the FCDs and pieces of navigation data for the last 30 days are compared using the user ID and the vehicle ID as a key, and it is judged whether each FCD coincides exactly in latitude and longitude, i.e., vehicle position with any piece of navigation data (step S40 of FIG. 4).

(37) If a result of the judgment is negative (NO in step S40 of FIG. 4), i.e., if the FCD does not coincide exactly in latitude and longitude with any piece of navigation data, the FCD and one piece of navigation data which are closest in latitude and longitude are linked to each other (step S41 of FIG. 4).

(38) On the other hand, if the judgment result is affirmative (YES in step S40 of FIG. 4), it is judged whether the number of pieces of data exactly coincident in latitude and longitude is one (step S42 of FIG. 4).

(39) If a result of the judgment is affirmative (YES in step S42 of FIG. 4), the FCD and the coincident piece of navigation data are linked to each other (step S43 of FIG. 4).

(40) On the other hand, if the judgment result is negative (NO in step S42 of FIG. 4), and there are a plurality of pieces of data exactly coincident in latitude and longitude, the FCD and one piece of navigation data which are closest in sampling time stamp are linked to each other (step S44 of FIG. 4).

(41) It is judged subsequently to the above-described linking processing whether linking of all pieces of data is over (step S45 of FIG. 4). If a result of the judgment is negative (NO in step S45 of FIG. 4), the above-described processes are executed again.

(42) On the other hand, if the judgment result is affirmative (YES in step S45 of FIG. 4), i.e., when linking of the FCDs and the pieces of navigation data for the last 30 days is over, the present process ends. With the above-described processing, the FCD-navigation provisional data mart is created as a data group (map) having the user ID, the vehicle ID, an FCD, a piece of navigation data, a sampling time stamp of the piece of navigation data, and a reading time stamp of the piece of navigation data which are linked to one another.

(43) Referring back to FIG. 3, after the FCD-navigation provisional data mart is created in the above-described manner, an FCD-weather provisional data mart is created (step S24 of FIG. 3). More specifically, mesh codes are linked to the FCDs for the last 30 days stored in the storage region on the basis of pieces of latitude and longitude data of the FCDs. The FCDs and pieces of weather data are then compared. An FCD and a piece of weather data which are coincident in mesh code with each other are searched for, and the coincident pieces of data are linked to each other. In the above-described manner, the FCD-weather provisional data mart (a third data group) is created as a data group (map) having the user ID, the vehicle ID, a mesh code, an FCD, a piece of weather data, a sampling time stamp of the piece of weather data, and a reading time stamp of the piece of weather data which are linked to one another.

(44) An FCD-vehicle-condition provisional data mart is created (step S25 of FIG. 3). The FCD-vehicle-condition provisional data mart (a fourth data group) is created by searching for the FCDs and pieces of vehicle condition data for the last 30 days stored in the storage region using the user ID and the vehicle ID as a key and linking the FCDs and the pieces of vehicle condition data to each other and created as a data group (map) having the user ID, the vehicle ID, an FCD, a piece of vehicle condition data, a sampling time stamp of the piece of vehicle condition data, and a reading time stamp of the piece of vehicle condition data which are linked to one another.

(45) A data mart is created (step S26 of FIG. 3). More specifically, the data mart is created by linking the four provisional data marts created in the above-described manner to one another using a user ID and a vehicle ID as a key and created as a data group (map) having the user ID, the vehicle ID, an FCD, a piece of navigation data, a piece of weather data, a piece of vehicle condition data, a sampling time stamp, and a reading time stamp which are linked to one another.

(46) The data mart is then compressed into data in Lzo format using the Lzo algorithm (step S27 of FIG. 3). After that, an encrypted data mart creation process is executed (step S28 of FIG. 3). More specifically, the encrypted data mart creation process is executed in the manner shown in FIG. 5.

(47) As shown in FIG. 5, an encryption condition flag F_ENC is first read (step S50 of FIG. 5). The encryption condition flag F_ENC is set to any one of “1” to “5” in accordance with the intended use (the purpose of analysis) of the data mart (to be described below) by an administrator of the integration processing server 3.

(48) (a) If changes in vehicle ID at a fixed location do not interfere with data analysis (e.g., if the traffic volume and the congestion degree at a specific intersection are desired to be analyzed), the encryption condition flag F_ENC is set to “1.”

(49) (b) If changes in vehicle ID for a fixed length of time do not interfere with data analysis (e.g., if the trade area of a tourist spot or a shop is desired to be analyzed), the encryption condition flag F_ENC is set to “2.”

(50) (c) If movement preferences of a user are desired to be analyzed, the encryption condition flag F_ENC is set to “3.”

(51) (d) If usage in the marketplace for each vehicle type is to be analyzed, the encryption condition flag F_ENC is set to “4.”

(52) (e) The encryption condition flag F_ENC is set to “5” for purposes other than the purposes (a) to (d).

(53) It is then judged whether the read encryption condition flag F_ENC is “1” (step S51 of FIG. 5). If a result of the judgment is affirmative (YES in step S51 of FIG. 5), a cipher key is set to a combination of a part of a mesh code and a fixed key (step S52 of FIG. 5). The fixed key is set in advance.

(54) On the other hand, if the judgment result is negative (NO in step S51 of FIG. 5), i.e., if F_ENC≠1, it is judged whether the encryption condition flag F_ENC is “2” (step S53 of FIG. 5). If a result of the judgment is affirmative (YES in step S53 of FIG. 5), the cipher key is set to a combination of a part of a sampling time stamp of a piece of navigation data and the fixed key (step S54 of FIG. 5).

(55) On the other hand, if the judgment result is negative (NO in step S53 of FIG. 5), i.e., if F_ENC≠1,2, it is judged whether the encryption condition flag F_ENC is “3” (step S55 of FIG. 5). If a result of the judgment is affirmative (YES in step S55 of FIG. 5), the cipher key is set to a combination of a part of the user ID and the fixed key (step S56 of FIG. 5).

(56) On the other hand, if the judgment result is negative (NO in step S55 of FIG. 5), i.e., if F_ENC≠1 to 3, it is judged whether the encryption condition flag F_ENC is “4” (step S57 of FIG. 5). If a result of the judgment is affirmative (YES in step S57 of FIG. 5), the cipher key is set to a combination of a part of the vehicle ID and the fixed key (step S58 of FIG. 5).

(57) On the other hand, if the judgment result is negative (NO in step S57 of FIG. 5), i.e., if F_ENC=5, the cipher key is set to the fixed key (step S59 of FIG. 5).

(58) After the cipher key is set in accordance with a value of the encryption condition flag F_ENC, as described above, vehicle IDs and user IDs in the data mart are encrypted by a predetermined encryption algorithm (e.g., SHA-256) using the cipher key (step S60 of FIG. 5).

(59) The encrypted data mart is created by linking a piece of vehicle type data and the encryption condition flag to the data mart having the encrypted vehicle IDs and user IDs (step S61 of FIG. 5). The piece of vehicle type data corresponds to a part of the vehicle ID. After that, the present process ends.

(60) Referring back to FIG. 3, after the encrypted data mart creation process is executed in the above-described manner, the encrypted data mart is output to the integrated database server 4 (step S29 of FIG. 3). After that, the present process ends.

(61) A data storage process will be described with reference to FIG. 6. The process stores an encrypted data mart input from the integration processing server 3 in the storage region in the integrated database server 4, and is executed each time an encrypted data mart is input.

(62) As shown in FIG. 6, an encrypted data mart is first read (step S80 of FIG. 6). A vehicle type is determined on the basis of a piece of vehicle type data included in the encrypted data mart (step S81 of FIG. 6). The vehicle type that is determined will be referred to as a determined vehicle type hereinafter.

(63) It is then judged whether the encryption condition flag F_ENC included in the encrypted data mart is “1” (step S82 of FIG. 6).

(64) If a result of the judgment is affirmative (YES in step S82 of FIG. 6), the encrypted data mart is stored as a piece of registered data in a first region for the determined vehicle type (step S83 of FIG. 6). After that, the present process ends.

(65) On the other hand, if the judgment result is negative (NO in step S82 of FIG. 6), i.e., if F_ENC≠1, it is judged whether the encryption condition flag F_ENC is “2” (step S84 of FIG. 6).

(66) If a result of the judgment is affirmative (YES in step S84 of FIG. 6), the encrypted data mart is stored as a piece of registered data in a second region for the determined vehicle type (step S85 of FIG. 6). After that, the present process ends.

(67) On the other hand, if the judgment result is negative (NO in step S84 of FIG. 6), i.e., if F_ENC≠1, 2, it is judged whether the encryption condition flag F_ENC is “3” (step S86 of FIG. 6).

(68) If a result of the judgment is affirmative (YES in step S86 of FIG. 6), the encrypted data mart is stored as a piece of registered data in a third region for the determined vehicle type (step S87 of FIG. 6). After that, the present process ends.

(69) On the other hand, if the judgment result is negative (NO in step S86 of FIG. 6), i.e., if F_ENC≠1 to 3, it is judged whether the encryption condition flag F_ENC is “4” (step S88 of FIG. 6).

(70) If a result of the judgment is affirmative (YES in step S88 of FIG. 6), the encrypted data mart is stored as a piece of registered data in a fourth region for the determined vehicle type (step S89 of FIG. 6). After that, the present process ends.

(71) On the other hand, if the judgment result is negative (NO in step S88 of FIG. 6), i.e., if F_ENC=5, the encrypted data mart is stored as a piece of registered data in a fifth region for the determined vehicle type (step S90 of FIG. 6). After that, the present process ends.

(72) As described above, in the data registration system 1 according to the present embodiment, a data mart is created as a data group having an FCD, a piece of weather data, a piece of vehicle condition data, a piece of fuel economy data, and a piece of navigation data input over the network 10 and a vehicle ID and a user ID which are linked to each other and is compressed. Additionally, an encrypted data mart is created by encrypting only vehicle IDs and user IDs in the compressed data mart by an encryption algorithm using a cypher key, and is stored as a piece of registered data in the storage region in the integrated database server 4.

(73) In this case, an FCD, a piece of weather data, a piece of vehicle condition data, a piece of fuel economy data, and a piece of navigation data are highly effective at the time of forming pieces of data related to a vehicle into big data and analyzing the big data, and it is possible to efficiently register such highly effective data while enhancing confidentiality.

(74) Additionally, a data mart is created by creating an FCD-fuel-economy provisional data mart, an FCD-navigation provisional data mart, an FCD-weather provisional data mart, and an FCD-vehicle-condition provisional data mart and collectively linking the provisional data marts. A load at the time of data mart creation can be made smaller than in a case where a data mart is created in one operation.

(75) Additionally, if an FCD does not coincide exactly in latitude and longitude, i.e., vehicle position at the time of sampling with any piece of navigation data in the FCD-navigation provisional data mart creation process shown in FIG. 4, the FCD and one piece of navigation data which are closest in latitude and longitude are linked to each other. Thus, an FCD-navigation provisional data mart can be created by linking pieces of data which are closest in vehicle position at the time of sampling and are estimated to be highly related to each other.

(76) If there are a plurality of pieces of navigation data exactly coincident in latitude and longitude with an FCD, the FCD and one of the plurality of pieces of data which are closest in time stamp at the time of sampling are linked to each other. Thus, an FCD-navigation provisional data mart can be created by linking pieces of data which are closest in time stamp at the time of sampling and are estimated to be highly related to each other. In the above-described manner, the accuracy of FCD-navigation provisional data mart creation can be enhanced.

(77) Moreover, since a data mart is encrypted after being compressed, the size of an encrypted data mart can be reduced. This makes it possible to increase the number of pieces of registered data which can be stored in a storage region of the same size while enhancing the security of a piece of registered data.

(78) Note that although the embodiment is an example which creates a data mart as a data group by creating an FCD-fuel-economy provisional data mart, an FCD-navigation provisional data mart, an FCD-weather provisional data mart, and an FCD-vehicle-condition provisional data mart and collectively linking the four provisional data marts, a data mart as a data group may be created by collectively linking an FCD-fuel-economy provisional data mart, an FCD-navigation provisional data mart, and an FCD-weather provisional data mart.

(79) In this case, step S25 of FIG. 3 according to the embodiment may be omitted, and a data mart as a data group may be created by a method similar to steps S22 to S24 and S26 described earlier.

(80) Also, although the embodiment is an example which uses a navigation device as a mobile station, a mobile station according to the present invention is not limited to this and may be one which moves together with a vehicle. For example, a handheld terminal, such as a smartphone, may be used as a mobile station.

(81) In this case, a handheld terminal may perform data communication with an ECU or a navigation device of a vehicle and receive data as a vehicle ID and/or a user ID, and a piece of data having a position (a latitude and a longitude) of the handheld terminal, a time stamp at the time of sampling of the position, the user ID, and the like which are linked to one another may be input as a piece of movement status data from any one of the handheld terminal and the ECU and the navigation device of the vehicle to the data processing server 2.

(82) If a handheld terminal is used as a mobile station, a result of performing future route computation and the like in the handheld terminal by a user may be input as a piece of navigation data from the handheld terminal to the data processing server 2, and a piece of movement status data may be input from the handheld terminal to the data processing server 2, not only during a period from when an ignition switch of a vehicle is turned on to when the ignition switch is turned off but also after the ignition switch of the vehicle is turned off In the case of such a configuration, a data mart may be created to have, for example, a fixed value or null data as a piece of data which does not change while the ignition switch of the vehicle is off (e.g., a piece of fuel economy data).

(83) Moreover, note that although the embodiment is an example which uses a vehicle ID and a user ID as a piece of vehicle-identifying data, a piece of vehicle-identifying data according to the present invention is not limited to this and may be one for identification of at least one of a vehicle and a user of the vehicle. For example, a vehicle ID or a user ID may be used as a piece of vehicle-identifying data. In this case, for example, only one of a vehicle ID and a user ID may be linked to pieces of data other than a piece of weather data, and a data mart may be created using only one of a vehicle ID and a user ID as a key in steps S22 to S26 of FIG. 3 in the linked data creation process in FIG. 2 according to the embodiment.

(84) On the other hand, although the embodiment is an example in which a data registration system according to the present invention is applied to a vehicle having an internal combustion engine as a power source, the data registration system according to the present invention is not limited to this and is applicable to a vehicle having something other than an internal combustion engine as a power source. For example, the data registration system according to the present invention is also applicable to a fuel cell vehicle, an electric vehicle, and the like.

(85) Also, although the embodiment is an example which uses fuel economy as a piece of consumption rate data, a piece of consumption rate data according to the present invention is not limited to this and may be one which represents an energy consumption rate of a vehicle. For example, in the case of a fuel cell vehicle, a hydrogen consumption rate corresponds to a piece of consumption rate data. In the case of an electric vehicle, a power consumption rate corresponds to a piece of consumption rate data.

(86) Additionally, although the embodiment is an example which uses Lzo algorithm as a compression algorithm at the time of data mart compression, the compression algorithm at the time of data mart compression is not limited to this and may be one which can compress data. For example, Gzip or the like may be used as the compression algorithm at the time of data mart creation.

(87) On the other hand, although the embodiment creates a data mart by the method shown in FIG. 3, a data mart creation method is not limited to this. For example, steps S25 and S26 may be omitted from the method in FIG. 3, and a data mart may be created by linking a piece of weather data and a piece of vehicle condition data to two provisional data marts created in steps S22 and S23.

(88) Although the embodiment is an example in which an encrypted data mart is created by encrypting a compressed data mart, and the encrypted data mart is stored as a piece of registered data in the integrated database server 4, the compressed data mart may be stored in the integrated database server 4 without being encrypted.

(89) Additionally, although the embodiment is an example in which a data registration system is composed of three servers, a data registration system may be composed of one or two servers or four or more servers.

REFERENCE SIGNS LIST

(90) 1 data registration system

(91) 2 data processing server (data reception unit)

(92) 3 integration processing server (data group creation unit and registered data creation unit)

(93) 4 integrated database server (data storage unit)

(94) 10 network

(95) 14 vehicle