Data collection device, data collection system. and collection rule generation method

Abstract

To provide a data collection device capable of improving efficiency in collecting vehicle data.SOLUTION: A generation section 13A generates collection items being data items to be collected from a vehicle 2 among the data items of vehicle data and data collection conditions to collect the collection items as user-based data being a collection rule based on a use service which a user using the vehicle 2 uses.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present disclosure relates to a data collection device, a data collection system, and a collection rule creation method. [Background technology]

[0002] In recent years, the amount of vehicle data generated by vehicles is increasing due to the advancement of connected vehicles and autonomous driving technology. In addition, technologies that provide useful services to users by collecting and analyzing vehicle data on a server installed outside the vehicle are becoming widespread.

[0003] In the above situation, in order to provide various services, it is necessary to collect various different types of vehicle data, but acquiring all of the vehicle data increases the load on the communication network. Therefore, from the viewpoint of reducing the load on the communication network, it is desirable to efficiently collect vehicle data.

[0004] In response to this, Patent Document 1 discloses a remote collection system that collects vehicle data under a specific vehicle environment. In this remote collection system, if the collection conditions for vehicle data specified by a server that collects data match the environment of the vehicle itself, the vehicle returns the vehicle data to the center. This allows the vehicle to select the vehicle data to return to the center, making it possible to collect desired vehicle data while reducing the load on the communication network. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] JP 2016-119547 A Summary of the Invention [Problem to be solved by the invention]

[0006] In the technology described in Patent Document 1, vehicle data corresponding to the vehicle environment such as braking conditions and traffic congestion conditions is collected, but the user who is using (driving) the vehicle is not taken into consideration, and the vehicle data to be acquired is determined uniformly for all users. For this reason, there is a risk that vehicle data that is not necessary for some users may be collected, which is problematic in terms of the efficiency of collecting vehicle data.

[0007] An object of the present disclosure is to provide a data collection device, a data collection system, and a collection rule creation method that can further improve the efficiency of collecting vehicle data. [Means for solving the problem]

[0008] A data collection device according to one aspect of the present disclosure is a data collection device that collects data from a vehicle that matches collection rules from the vehicle data generated by the vehicle, and has a creation unit that creates collection items, which are data items of the vehicle data to be collected from the vehicle, and collection conditions for collecting the collection items as the collection rules, based on a service used by a user of the vehicle. Effect of the Invention

[0009] According to the present invention, it is possible to further improve the efficiency of collecting vehicle data. [Brief description of the drawings]

[0010] [Figure 1] FIG. 1 is a diagram illustrating a configuration of a data collection system according to an embodiment of the present disclosure. [Diagram 2] FIG. 13 is a diagram illustrating an example of an attribute management table. [Diagram 3] FIG. 13 illustrates an example of a service management table. [Figure 4] FIG. 13 is a diagram illustrating an example of a collection item definition table. [Diagram 5] FIG. 13 is a diagram illustrating an example of a collection condition definition table. [Figure 6] FIG. 13 is a diagram illustrating an example of a priority definition table. [Figure 7] FIG. 13 is a diagram showing an example of a table of collection items by user. [Figure 8] FIG. 13 is a diagram showing an example of a user-specific collection condition table. [Figure 9] FIG. 13 is a diagram illustrating an example of a user priority table. [Figure 10] 13 is a flowchart illustrating an example of a user-specific data creation process. [Figure 11] 13 is a flowchart illustrating an example of an item table creation process. [Figure 12] 13 is a flowchart illustrating an example of a condition table creation process. [Figure 13] 11 is a flowchart illustrating an example of a priority table creation process. [Figure 14] 11 is a flowchart illustrating an example of a collection process. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

[0012] Fig. 1 is a diagram showing a configuration of a data collection system according to an embodiment of the present disclosure. The data collection system shown in Fig. 1 includes a server 1 and a vehicle 2. The server 1 and the vehicle 2 are connected to each other so as to be able to communicate with each other. Although only one vehicle 2 is shown in Fig. 1, there may be a plurality of vehicles 2.

[0013] The server 1 is a data collection device that collects vehicle data, which is data generated in the vehicle 2, and has a user registration unit 11, a data management unit 12, a user-specific data management unit 13, a communication unit 14, a collected data processing unit 15, and a vehicle data storage unit 16.

[0014] The user registration unit 11 receives user information relating to the user who uses the vehicle 2 from the user, and registers the user information in the data management unit 12 .

[0015] The data management unit 12 manages various data related to the processing performed by the server 1. In this embodiment, the data management unit 12 manages an attribute management table 101, a service management table 102, a collection item definition table 103, a collection condition definition table 104, and a priority definition table 105. The attribute management table 101 and the service management table 102 are user information registered by the user registration unit 11. The collection item definition table 103, the collection condition definition table 104, and the priority definition table 105 are system information registered in advance.

[0016] The user-specific data management unit 13 manages a user-specific collection item table 201, a user-specific collection condition table 202, and a user-specific priority table 203 as user-specific data indicating collection rules for collecting vehicle data for each user. The user-specific data management unit 13 also includes a creation unit 13A and a transmission unit 13B.

[0017] The creation unit 13A creates user-specific data based on the data (101-105) managed by the data management unit 12. The transmission unit 13B transmits, from the user-specific data, target user data that corresponds to the user who uses the vehicle 2, to the vehicle 2 via the communication unit 14.

[0018] The communication unit 14 is communicatively connected to the vehicle 2. The collected data processing unit 15 collects vehicle data via the communication unit 14. The vehicle data storage unit 16 stores the vehicle data collected by the collected data processing unit 15.

[0019] The vehicle 2 is, for example, an automobile, and includes a communication unit 21, a user authentication unit 22, a collected data management unit 23, and a data collection unit 24.

[0020] The communication unit 21 is communicably connected to the server 1. The user authentication unit 22 authenticates a user who uses the vehicle 2. The method of authenticating the user may be, for example, a method using a user ID and a password.

[0021] The collected data management unit 23 acquires and manages the above-mentioned target user data from the server 1 as data indicating collection rules for collecting vehicle data from the vehicle 2 used by the user authenticated by the user authentication unit 22. The target user data includes a user collection item table 301, a user collection condition table 302, and a user priority table 303 extracted from the user-specific collection item table 201, the user-specific collection condition table 202, and the user-specific priority table 203, respectively.

[0022] The components and functions of the server 1 and the vehicle 2 described above may be realized, for example, by a processor reading a computer program from a recording medium and executing the read computer program using memory as a usage area.

[0023] 2 is a diagram showing an example of the attribute management table 101. The attribute management table 101 is attribute information indicating user attributes, which are attributes of the users, for each user, and includes fields 111-114.

[0024] Field 111 stores a user ID, which is identification information for identifying a user. Field 112 stores the name of the user. Field 113 stores a user type, which is the type of user. In this embodiment, vehicle 2 is a rental car, and the user types include an administrator, who is the user who rents out vehicle 2, and a general user, who is the user who rents vehicle 2. Note that the administrator may use (drive) the vehicle in the same way as a general user, for the purpose of managing and transporting the vehicle.

[0025] The field 114 stores user attributes. In this embodiment, the user attributes include an accident history, which is a history of accidents that occurred during driving a vehicle in the past, a driving frequency of driving a vehicle, and a driving area in which the vehicle is driven. Note that the user attributes of the administrator do not need to be registered.

[0026] 3 is a diagram showing an example of the service management table 102. The service management table 102 is available service information indicating, for each user, available services that are vehicle-related services used by the user, and includes fields 121-125.

[0027] The field 121 stores a user ID, the field 122 stores a user name, and the field 123 stores a user type.

[0028] Fields 124 and 125 store the service name of the service to be used as identification information for identifying the service to be used by the user. In this embodiment, field 124 stores the service name of a common service that is a common service to be used by all users. In the example of FIG. 3, the common service is a maintenance timing suggestion service that suggests the timing of vehicle maintenance, but is not limited thereto. Field 125 stores the service name of a user-selected service selected by the user. There may be multiple user-selected services, and field 125 is provided for each user-selected service. In the example of FIG. 3, the user-selected services shown are a safe driving support service that supports safe driving of a vehicle and a telematics insurance service that provides insurance according to the driving conditions of the vehicle, but are not limited thereto.

[0029] 4 is a diagram showing an example of the collection item definition table 103. The collection item definition table 103 is item definition information indicating data items of vehicle data to be collected from the vehicle 2 used by the user for each service used (more specifically, for each user selected service) and each user attribute, and includes fields 131 to 133.

[0030] Field 131 stores the service name of the service being used (more specifically, the user-selected service). Field 132 stores the user attributes. Field 133 stores item information indicating collection items, which are data items of vehicle data to be collected from a vehicle 2 used by a user who uses the service being used with the service name in field 131 and who has the user attributes in field 132. In this embodiment, the item information indicates, for each data item, whether or not that data item is to be collected. In the example of FIG. 4, data items to be collected are indicated with "◯" and data items that are not to be collected are indicated with a blank space.

[0031] Although FIG. 4 shows the collection item definition table 103 related to the safe driving support service, in reality, the collection item definition table 103 shows collection items corresponding to each of the user attributes for each user selected service.

[0032] 5 is a diagram showing an example of the collection condition definition table 104. The collection condition definition table 104 is condition definition information indicating data collection conditions, which are collection conditions for collecting each data item of vehicle data from the vehicle 2, for each service used (more specifically, for each user-selected service) and each user attribute, and includes fields 141 to 143.

[0033] Field 141 stores the service name of the service being used (more specifically, the user-selected service). Field 142 stores the user attributes. Field 143 stores the data collection conditions for data items to be collected from the vehicle 2 used by the user who uses the service having the service name in field 141 and has the user attributes in field 142. The data collection conditions are set for each data item that varies depending on the service being used and the user attributes. In the example of FIG. 4, data collection conditions for the items "vehicle speed", "sudden braking judgment", "sudden steering judgment", and "amount of collected data" are shown. For example, the data collection conditions for the item "vehicle speed" indicate that the vehicle speed is collected from the vehicle 2 driven by a user who uses the safe driving support service and has a history of accidents when the speed reaches 30 km / h or more, and that the vehicle speed is collected from the vehicle 2 driven by a user who has no history of accidents when the speed reaches 40 km / h or more.

[0034] 6 is a diagram showing an example of the priority definition table 105. The priority definition table 105 is priority definition information indicating the priority of data items of vehicle data for each service used (more specifically, for each common service) and each user attribute, and includes fields 151 to 153. In this embodiment, the priority is set for the common service.

[0035] Field 151 stores the service name of the service being used (more specifically, the common service). Field 152 stores the user type. Field 153 stores priority information indicating the collected data priority, which is the priority of each data item of vehicle data collected from a vehicle 2 used by a user who uses the service having the service name in field 151 and has the user attribute in field 152. The collected data priority may be fixed in advance for each data item, or it may vary. Furthermore, no priority is set for data items that are not collected. In the example of FIG. 6, the priority has two levels, high "high" and low "low", and when it varies, "variable" is stored.

[0036] 7 is a diagram showing an example of the user-specific collection item table 201. The user-specific collection item table 201 is information indicating, for each user, collection items that are data items of vehicle data to be collected from the vehicle 2 used by that user, and includes fields 211-213.

[0037] Field 211 stores the user ID of the user. Field 212 stores the service name of the service (more specifically, the user selected service) used by the user. Field 213 stores collection item information indicating collection items, which are data items of vehicle data to be collected from the vehicle 2 used by the user. In this embodiment, the collection item information indicates, for each data item, whether or not the data item is to be collected, that is, whether or not it is a collection item. In the example of FIG. 7, data items to be collected are indicated with "◯" and data items not to be collected are indicated with a blank space.

[0038] 8 is a diagram showing an example of the user-specific collection condition table 202. The user-specific collection condition table 202 is information indicating, for each user, data collection conditions related to values ​​of collection items to be collected from the vehicle 2 used by that user, and includes fields 221-223.

[0039] A field 221 stores the user ID of the user. A field 222 stores the service name of the service used by the user. A field 223 stores the data collection conditions. The collection conditions are defined for each collection item.

[0040] 9 is a diagram showing an example of the user priority table 203. The user priority table 203 is information indicating collected data priority, which is the priority of data items of vehicle data to be acquired for each user, and includes fields 231-233.

[0041] A field 231 stores a user ID. A field 232 stores a service name. A field 232 stores a collected data priority. The collected data priority is defined for each collection item.

[0042] FIG. 10 is a flowchart for explaining an example of a user-specific data creation process up to the point where the server 1 creates user-specific data.

[0043] In the user-specific data creation process, first, the creation unit 13A of the user-specific data management unit 13 checks whether the attribute management table 101 and the service management table 102, which are user information, are registered in the data management unit 12 (step S101).

[0044] If the user information is not registered (step S101: No), the user registration unit 11 accepts the user information from the user and registers the user information in the data management unit 12 as the attribute management table 101 and the service management table 102 (step S102).

[0045] If the user information has been registered (step S101: Yes), the creating unit 13A checks whether the user information has been changed since the user-specific data was created the previous time (step S103).

[0046] If the user information has not been changed (step S103: No), the creation unit 13A determines that there is no need to create user-specific data, and ends the process.

[0047] Furthermore, if the user information has been changed (step S103: Yes) and if the user information has been registered in the data management unit 12 in step S102, the creation unit 13A executes an item table creation process (see FIG. 11) to create a user-specific collection item table 201 (step S104).

[0048] Thereafter, the creation unit 13A executes a condition table creation process (see FIG. 12) for creating the user-specific collection condition table 202 (step S105).

[0049] Then, the creation unit 13A executes the priority table creation process (see FIG. 13) for creating the user-specific priority table 203 (step S106), and ends the process.

[0050] Fig. 11 is a flowchart for explaining an example of the item table creation process in step S104 in Fig. 10. The item table creation process is a process performed for each user (more specifically, for each user ID), and Fig. 11 shows an example of the item table creation process for a specific user.

[0051] In the item table creation process, the creation unit 13A first identifies, as a target service, a user selected service used by a user to be processed from the service management table 102 (step S201).

[0052] The creation unit 13A identifies item information corresponding to the target service from the collection item definition table 103 (step S202).

[0053] The creation unit 13A identifies the user attributes of the user to be processed from the attribute management table 101. Then, the creation unit 13A identifies collection items, which are data items of vehicle data to be collected from the user with the identified user attributes, from the identified item information, and generates a record corresponding to the user to be processed in the user-specific collection item table 201 based on the collection items and the collected data items (step S203), and ends the process.

[0054] Fig. 12 is a flowchart for explaining an example of the condition table creation process in step S105 in Fig. 10. The condition table creation process is a process performed for each user (more specifically, for each user ID), and Fig. 12 shows an example of the condition table creation process for a specific user.

[0055] In the condition table creation process, the creation unit 12A first identifies, as a target service, a user selected service used by a user to be processed from the service management table 102 (step S301).

[0056] The creation unit 13A identifies a data collection condition corresponding to the target service from the collection condition definition table 104 (step S302).

[0057] The creation unit 13A identifies the user attributes of the user to be processed from the attribute management table 101. Then, the creation unit 13A identifies data collection conditions related to values ​​of data items to be collected from the user of the identified user attributes from the identified data collection conditions, and generates a record corresponding to the user to be processed in the user-specific collection condition table 202 based on the data collection conditions (step S303), and ends the process.

[0058] Fig. 13 is a flowchart for explaining an example of the priority table creation process in step S106 in Fig. 10. The priority table creation process is a process performed for each user (more specifically, for each user ID), and Fig. 13 shows an example of the priority table creation process for a specific user.

[0059] In the priority table creation process, the creation unit 13A selects one of the available services included in the service management table 102, and determines whether or not the selected available service is a common service (step S401).

[0060] If the selected service to be used is not a common service (step S401: No), the creation unit 13A returns to the process of step S401. On the other hand, if the selected service to be used is a common service (step S401: Yes), the creation unit 13A identifies the user type of the user to be processed from the attribute management table 101. Then, the creation unit 13A obtains the collected data priority corresponding to the common service and the identified user type from the priority definition table 105 (step S402).

[0061] The creation unit 13A predicts the network load related to the collection of vehicle data from the vehicle 2 used by the user to be processed, based on the acquisition items and data collection conditions of the user to be processed in the user-specific collection item table 201 and the user-specific collection condition table 202 (step S403). For example, the creation unit 13A predicts the product of the number of acquisition data items and the collection frequency of vehicle data according to the data collection conditions as the network load. The collection frequency of vehicle data according to the data collection conditions can be obtained using a lookup table prepared in advance.

[0062] Then, the creation unit 13A determines whether the predicted network load is equal to or greater than a predetermined threshold value (step S404).

[0063] If the network load is above the threshold (step S404: Yes), the creation unit 13A sets the data item “variation” in the acquired collected data priority to a low priority of “low,” creates a record corresponding to the user to be processed in the user priority table 203 (step S405), and terminates the processing.

[0064] If the network load is less than the threshold (step S404: No), the creation unit 13A sets the data item “Change” in the acquired collected data priority to “High”, which is the high priority, and creates a record corresponding to the user to be processed in the user priority table 203 (step S406), and terminates the processing.

[0065] FIG. 14 is a flowchart illustrating an example of a collection process for collecting vehicle data.

[0066] In the collection process, first, the user authentication unit 22 of the vehicle 2 authenticates the user who uses the vehicle 2. Here, it is assumed that the authentication of the user is successful. In this case, the user authentication unit 22 notifies the authentication success information collection data management unit 23 that the authentication was successful (step S501).

[0067] When the authentication success information is notified, the collected data management unit 23 transmits an acquisition request to the server 1 via the communication unit 21 to request acquisition of target user data, which is user-specific data of the authenticated user (step S502). The acquisition request includes the user ID of the authenticated user. The user ID is received from the user by the user authentication unit 22, for example.

[0068] When the communication unit 14 of the server 1 receives the acquisition request, the transmission unit 13B of the user-specific data management unit 13 transmits the records of the user-specific data (user-specific collection item table 201, user-specific collection condition table 202, and user-specific priority table 203) including the user ID included in the acquisition request as target user data (user collection item table 301, user collection condition table 302, and user priority table 303) to the vehicle 2 via the communication unit 14. When the communication unit 21 of the vehicle 2 receives the target user data, the collected data management unit 23 holds the target user data (step S503).

[0069] Thereafter, the data collection unit 24 collects vehicle data of the vehicle 2 based on the target user data held in the collected data management unit 23 (step S504). At this time, the data collection unit 24 sets the collection frequency of data items with low collected data priority in the target user data lower than the collection frequency of data items with high collected data priority.

[0070] The data collection unit 24 transmits the collected vehicle data to the server 1 via the communication unit 21. When the communication unit 14 of the server 1 receives the vehicle data, the collected data processing unit 15 registers the vehicle data in the vehicle data storage unit 16 (step S505), and ends the process.

[0071] In step S505, the data collection unit 24 may transmit data items with low collected data priority in the target user data at a lower frequency than the transmission frequency of data items with high collected data priority.

[0072] As described above, according to this embodiment, the creation unit 13A creates collection items, which are data items to be collected from the vehicle 2 among the data items of the vehicle data, and data collection conditions for collecting the collection items, as user-specific data, which are collection rules for collecting vehicle data, based on the service used by the user who uses the vehicle 2. Therefore, it becomes possible to collect vehicle data according to the user, and therefore it becomes possible to further improve the efficiency of collecting vehicle data.

[0073] In the present embodiment, the creation unit 13A creates the collection rule based on the user's attributes. Therefore, it is possible to reflect the user's attributes in the collected data, and therefore it is possible to further improve the efficiency of collecting vehicle data.

[0074] In this embodiment, the creation unit 13A creates collection items for user-specific data using a collection item definition table 103 that indicates data items corresponding to each user attribute for each service used. The creation unit 13A also creates data collection conditions for user-specific data using a collection condition definition table 104 that indicates data collection conditions corresponding to each user attribute for each service used. In these cases, it becomes possible to easily create user-specific data.

[0075] In the present embodiment, the creation unit 13A creates collection items and collection conditions for user-specific data based on a selected service among the services to be used. In this case, it is possible to more appropriately improve the efficiency of collecting vehicle data.

[0076] In this embodiment, the creation unit 13A creates the collection data priority for collecting collection items corresponding to the common service as the user-specific data, which is the collection rule, based on the user-specific data created from the selected service (the user-specific collection item table 201 and the user-specific collection condition table 202). In this case, it is possible to change the priority for collecting collection items corresponding to the common service common to the users according to the user, so that it is possible to further improve the efficiency of collecting vehicle data.

[0077] The above-described embodiments of the present disclosure are illustrative examples of the present disclosure, and are not intended to limit the scope of the present disclosure to only these embodiments. A person skilled in the art can implement the present disclosure in various other forms without departing from the scope of the present disclosure. [Explanation of symbols]

[0078] 1: Server 2: Vehicle 11: User registration unit 12: Data management unit 12A: Creation unit 13: User-specific data management unit 13A: Creation unit 13A: Creation unit 13B: Transmission unit 14: Communication unit 15: Collected data processing unit 16: Vehicle data storage unit 21: Communication unit 22: User authentication unit 23: Collected data management unit 24: Data collection unit

Claims

1. A data collection device that collects, from a vehicle, vehicle data generated in the vehicle that matches a collection rule, comprising: A data collection device having a creation unit that creates collection items, which are data items among the data items of the vehicle data to be collected from the vehicle, and collection conditions for collecting the collection items as the collection rules based on services used by a user of the vehicle.

2. The data collection device according to claim 1 , wherein the creation unit creates the collection rule further based on an attribute of the user.

3. The data collection device according to claim 2 , wherein the creation unit determines the collection rule by using item definition information indicating the collection items corresponding to the service and the attribute.

4. The data collection device according to claim 2 , wherein the creation unit creates the collection rule by using condition definition information indicating the collection condition according to the service and the attribute.

5. The services include a selected service selected for each user and a common service common to all users; The data collection device according to claim 1 , wherein the creation unit creates the collection items and the collection conditions as the collection rules based on the selected service.

6. 6. The data collection device according to claim 5, wherein the creation unit further creates the collection items based on the common service as the collection rules, and creates, as the collection rules, priorities for collecting the collection items created from the common service based on the collection rules created from the selected service.

7. A data collection system including the data collection device according to claim 1 and the vehicle, The data collection device includes: a transmission unit that transmits the collection rule created by the creation unit to the vehicle; a collected data processing unit that receives and stores vehicle data from the vehicle; The vehicle is a collected data management unit that receives the collection rules from the data collection device and manages them; a data collection unit that collects the vehicle data based on the collection rules and transmits the vehicle data to the data collection device.

8. 1. A method for creating collection rules by a data collection device that collects, from a vehicle, vehicle data generated in the vehicle that matches a collection rule, comprising: A collection rule creation method for creating collection rules that include collection items, which are data items among the data items of the vehicle data to be collected from the vehicle, and collection conditions for collecting the collection items, based on services used by a user of the vehicle.

Images