Information processing device

Abstract

To appropriately provide information about information collection to an information provider.SOLUTION: Information on a benefit occurring when first data obtained during traveling by a first vehicle is provided to a first business operator is obtained, information on the benefit is presented to a user associated with the first vehicle, and the user is asked whether to consent to provide the first data to the first business operator.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present disclosure relates to techniques for collecting information from vehicles. [Background technology]

[0002] In recent years, there has been a demand for more appropriate management of personal information. In this regard, for example, Patent Document 1 discloses an evaluation device capable of calculating the risk of an individual being identified in a system in which personal information is anonymized and provided to an outside party. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2017-228255 A Summary of the Invention [Problem to be solved by the invention]

[0004] The present disclosure aims to provide appropriate guidance to information providers regarding information collection. [Means for solving the problem]

[0005] One aspect of the present disclosure is to The information processing device has a control unit that executes the following operations: acquiring information regarding benefits that will be generated when first data acquired by a first vehicle while traveling is provided to a first business operator; presenting the information regarding the benefits to a user associated with the first vehicle; and asking the user whether or not he or she agrees to the provision of the first data to the first business operator.

[0006] Further, other aspects include a method executed by the above-mentioned device, a program for causing a computer to execute the method, or a computer-readable storage medium non-transitoryly storing the program. Effect of the Invention

[0007] According to the present disclosure, it is possible to appropriately provide information providers with guidance regarding information collection. [Brief description of the drawings]

[0008] [Figure 1] 1 is a schematic diagram of a vehicle system according to a first embodiment. [Diagram 2] FIG. 2 is a diagram showing components of an in-vehicle device and a server device. [Diagram 3] 4 shows an example of data stored in the in-vehicle device and the server device. [Figure 4] 4 is a flowchart of a process executed by an in-vehicle device. [Diagram 5] 4 is a flowchart of a process executed by an in-vehicle device. [Figure 6] An example of a screen for asking for consent to provide data. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] In recent years, attempts have been made to utilize data collected from automobiles. It is expected that various services can be provided by using the data collected from vehicles as big data. On the other hand, the data transmitted from the vehicle may include personal information or information similar to personal information. Such data may include not only personal information itself, but also information linked to an individual, such as location information. This may raise privacy concerns.

[0010] For this reason, attempts are being made to explain the collection and use of data to users (e.g., vehicle drivers) in advance before entering into a data provision contract. However, when entering into a data provision contract, it is not common for companies to explain to users what effects providing that data will have on them, which makes users hesitant to provide their data. The information processing device according to the present disclosure solves such problems.

[0011] An information processing device according to a first aspect of the present disclosure includes: The vehicle has a control unit that acquires information regarding benefits that will be generated when first data acquired by a first vehicle while traveling is provided to a first business operator, presents the information regarding the benefits to a user associated with the first vehicle, and asks the user whether or not he or she agrees to the provision of the first data to the first business operator.

[0012] The first data is data acquired while the first vehicle is traveling, and includes personal information of the driver and data related to the traveling of the first vehicle (e.g., position information, speed information, etc.). The first data is also referred to as sensor data. The control unit acquires information regarding benefits generated by providing the first data to the first business operator. The first business operator is a business operator that provides a predetermined service using the first data. The information regarding benefits may be information regarding benefits that the user can directly obtain, such as "an incentive given to the user in exchange for providing data." The information regarding benefits may also be information regarding public benefits, such as "providing data improves the accuracy of driving assistance functions and reduces traffic accidents." For this reason, the control unit may obtain predefined information regarding benefits and provide guidance to the user based on the information. A user associated with a first vehicle is typically a driver of the first vehicle, but a user associated with a first vehicle may also be a passenger, an owner of the first vehicle, etc.

[0013] In addition, when there are multiple types of first data, the control unit may obtain and present information on benefits for each type of first data. In this case, the control unit may allow the user to select the type of first data to be provided to the first business operator.

[0014] In addition, when obtaining consent, the control unit may further present to the user a condition under which the first vehicle acquires the first data. With this configuration, it is possible to allow the user to understand under what condition the first data is acquired.

[0015] The control unit may further present data regarding the proportion of users who have agreed to the provision of the first data to the total number of users. For example, if there are multiple users under the management of the system, it may be possible to display what percentage of the total users have agreed to provide data.

[0016] Specific embodiments of the present disclosure will be described below with reference to the drawings. Unless otherwise specified, the hardware configuration, module configuration, functional configuration, and the like described in each embodiment are not intended to limit the technical scope of the disclosure to only those.

[0017] First Embodiment An overview of a vehicle system according to a first embodiment will be described with reference to FIG. The vehicle system according to the embodiment includes a vehicle 10 equipped with an on-vehicle device 100, and a server device 200. The system may include a plurality of vehicles 10 (on-vehicle devices 100).

[0018] The vehicle 10 is a probe vehicle for collecting data. The vehicle 10 is configured to be able to collect data related to driving and data related to occupants, and can transmit the collected data to the server device 200 via the in-vehicle device 100. Examples of the data related to driving include the vehicle speed, direction of travel, location information, information related to driving operations, information related to vehicle behavior, image data captured by an on-board camera, etc. Examples of the data related to the occupants include personal identifiers, gender, age, etc. In the following description, data collected by the vehicle 10 will be referred to as sensor data. Although the sensor data is an example of the "first data," the data collected by the vehicle 10 does not necessarily have to be obtained by sensing.

[0019] The server device 200 is a device that provides a predetermined service based on sensor data collected from the vehicle 10. For example, by collecting position information and speed information from a plurality of vehicles 10, congestion information and traffic information can be generated and provided to other vehicles. In addition, by collecting data on the vehicle occupants, it becomes possible to provide information suited to individuals. In addition, by collecting images captured by an on-board camera, it becomes possible to generate road map data. The server device 200 requests a plurality of vehicles 10 to transmit predetermined sensor data, and the vehicles 10 (on-vehicle devices 100) respond by transmitting the sensor data.

[0020] The server device 200 may be a device that provides a service to the vehicle 10 (or other vehicles) based on the sensor data collected from the vehicle 10, or may be a device that relays the sensor data collected from the vehicle 10 to an additional external device. For example, when there are multiple types of sensor data collected from the vehicle 10, the server device 200 may relay the sensor data to different external devices under the management of different operators for each type of sensor data.

[0021] Furthermore, the server device 200 obtains consent from a user (eg, a driver) associated with the vehicle 10 to provide the sensor data (ie, to transmit the sensor data to the server device 200). The presence or absence of consent is stored in both the server device 200 and the in-vehicle device 100, and the in-vehicle device 100 transmits data to the server device 200 only when there is consent to the provision of data. The in-vehicle device 100 has a database that stores the presence or absence of consent for each type of sensor data, and determines whether the user has consented (has consented in the past) to transmitting certain sensor data based on the database.

[0022] In the vehicle system according to this embodiment, a plurality of in-vehicle devices 100 and a server device 200 are connected to each other via a network. The network may be, for example, a WAN (Wide Area Network) that is a global public communication network such as the Internet or other communication networks. The network may also include a telephone communication network such as a mobile phone, or a wireless communication network such as Wi-Fi (registered trademark).

[0023] Each element that makes up the system will be explained. FIG. 2 is a diagram showing a system configuration of the in-vehicle device 100 and the server device 200. As shown in FIG.

[0024] First, the configuration of the server device 200 will be described. The server device 200 can be configured as a computer having a processor such as a CPU or GPU, a main memory such as a RAM or ROM, and an auxiliary memory such as an EPROM, a hard disk drive, or a removable medium. The auxiliary memory stores an operating system (OS), various programs, various tables, and the like, and by executing the programs stored therein, it is possible to realize various functions that meet a predetermined purpose, as described below. However, some or all of the functions may be realized by hardware circuits such as ASIC or FPGA. The server device 200 may be configured as a single computer, or may be configured as a plurality of computers that cooperate with each other.

[0025] The server device 200 includes a control unit 201 , a storage unit 202 , and a communication unit 203 .

[0026] The control unit 201 is a calculation device that manages the control performed by the server device 200. The control unit 201 can be realized by a calculation processing device such as a CPU. The control unit 201 is configured to have two functional modules: a consent acquisition unit 2011 and a data acquisition unit 2012. Each functional module may be realized by causing a CPU to execute a program stored in an auxiliary storage unit.

[0027] The consent acquisition unit 2011 acquires consent to data provision from the user of the vehicle 10 prior to acquiring sensor data from the vehicle 10. The server device 200 is configured to be able to acquire or store data relating to the use of the sensor data to be acquired (hereinafter, use data). The use data includes data relating to the use of the sensor data, the destination of the sensor data, the acquisition conditions of the sensor data, the transmission timing of the sensor data, the entity (business entity) that will use the sensor data, and the like. The consent acquisition unit 2011 presents these to the user of the vehicle 10 via the in-vehicle device 100.

[0028] The usage data also includes data on risks that may arise from providing the sensor data. The consent acquisition unit 2011 presents an explanation or the like on the risks to the user of the vehicle 10 via the in-vehicle device 100. Furthermore, the usage data includes data on benefits to be generated by providing the sensor data. The consent acquisition unit 2011 presents an explanation of the benefits to the user of the vehicle 10 via the in-vehicle device 100.

[0029] The consent acquisition unit 2011 determines whether or not consent to data provision has been obtained for each type of sensor data, based on a response from the user of the vehicle 10. When consent to provision has been obtained for a specific type of sensor data, the consent acquisition unit 2011 stores the presence or absence of consent in both the server device 200 and the in-vehicle device 100. When there is a plurality of sensor data to be provided or when there are a plurality of businesses that use the sensor data, a comprehensive consent may be obtained, or multiple consents may be obtained. When the user of the vehicle 10 agrees to the data provision, it can be considered that a data provision contract has been established between the user and the business entity receiving the sensor data.

[0030] The data acquisition unit 2012 requests each of the multiple vehicles 10 (on-vehicle devices 100) to transmit sensor data. For example, if the server device 200 executes a service of generating road map data based on images captured by the vehicles 10, the server device 200 requests the vehicles 10 to transmit image data. The type of sensor data requested by the server device 200 may differ depending on the service executed by the server device 200. The data acquisition unit 2012 also receives sensor data from the multiple vehicles 10 (on-vehicle devices 100) and stores it in the memory unit 202. The stored sensor data is used to provide a predetermined service.

[0031] The storage unit 202 includes a main storage device and an auxiliary storage device. The main storage device is a memory in which the programs executed by the control unit 201 and data used by the control programs are expanded. The auxiliary storage device is a device in which the programs executed by the control unit 201 and data used by the control programs are stored. The storage unit 202 stores sensor data collected from the vehicle 10.

[0032] The above-mentioned usage data is also stored in the storage unit 202. Fig. 3A shows an example of usage data 202A. The usage data is data related to the handling of the sensor data, and includes information regarding the identifier of the sensor data (data ID), the type of the sensor data, the destination of the sensor data, the conditions for acquiring the sensor data, the transmission cycle of the sensor data, the business entity that uses the sensor data, and the like. The destination of the sensor data may be represented by a network address, etc. Examples of the conditions for acquiring the sensor data include "an image is captured at a specific point," "a video is captured in a specific section," and "location information is acquired every second during a specific time period."

[0033] Furthermore, the usage data includes data (risk-related data) for informing the user of risks that may arise from providing the sensor data. The risk-related data may include, for example, the following information. What information is collected and by which company? How the collection of information affects you - In the unlikely event of a data leak, what data will be available to third parties? Is there a risk that data obtained by a third party will be misused? The risk-related data may include an explanation of an event that does not normally occur, such as an information leak, or an explanation of an event that occurs during normal operation. The target event may be any event that the user considers to be a risk.

[0034] Furthermore, the usage data includes data for informing the user of benefits generated by providing the sensor data (benefit-related data). The benefit-related data may include, for example, the following information. What information is collected and by which company? What benefits will users receive as a result of their information being collected by the business? What benefits will accrue to anyone other than the user as a result of the information being collected by the business? -Whether there is compensation (incentive) for collecting information, and if so, what is the content (e.g. amount) The benefits generated by providing the sensor data may include benefits other than direct benefits to the user. For example, the benefits generated by providing the sensor data may be benefits to the public, such as "providing image data improves crime prevention in the area where the vehicle has traveled" or "providing location information improves the accuracy of traffic congestion prediction." The benefits generated by providing the sensor data may also relate to benefits that can be obtained by businesses that use the sensor data.

[0035] The storage unit 202 also stores data for managing user consent to the provision of sensor data (hereinafter, consent data). Here, the consent data will be described. The consent data is data that records whether or not the transmission of the sensor data to the outside is permitted for each driver, transmission destination, and type of sensor data. The consent data can be generated based on the result of an interaction with the driver, for example.

[0036] FIG. 3B is an example of the consent data 202B. As shown in the figure, the consent data includes fields for a driver ID, a data ID, a transmission destination, and whether or not to provide. The driver ID field stores an identifier that uniquely identifies the driver. The data ID field stores information that identifies the type of sensor data. The transmission destination field stores information that identifies the destination of the sensor data. The provision whether or not field stores whether or not there is consent to the provision of the sensor data ("permitted" or "rejected").

[0037] The communication unit 203 is a communication interface for connecting the server device 200 to a network. The communication unit 203 includes, for example, a network interface board and a wireless communication circuit for wireless communication.

[0038] Next, the in-vehicle device 100 will be described. The vehicle 10 is a connected car having a communication function with an external network. The vehicle 10 is equipped with an in-vehicle device 100.

[0039] The in-vehicle device 100 is a computer for collecting information. In this embodiment, the in-vehicle device 100 has a plurality of sensors for collecting information related to the traveling of the vehicle 10, and transmits the collected sensor data to the server device 200 at a predetermined timing. The in-vehicle device 100 may be a device (such as a car navigation device) that provides information to a passenger of the vehicle 10, or may be an electronic control unit (ECU) that the vehicle 10 has. The in-vehicle device 100 may also be a data communication module (DCM) having a communication function.

[0040] The in-vehicle device 100 can be configured as a computer having a processor such as a CPU or GPU, a main memory such as a RAM or ROM, and an auxiliary memory such as an EPROM, a hard disk drive, or a removable medium. The auxiliary memory stores an operating system (OS), various programs, various tables, etc., and by executing the programs stored therein, various functions that match a predetermined purpose, as described below, can be realized. However, some or all of the functions may be realized by hardware circuits such as ASIC or FPGA.

[0041] The in-vehicle device 100 includes a control unit 101, a storage unit 102, a communication unit 103, and an input / output unit 104. The in-vehicle device 100 is also connected to a sensor group 110 and a camera 120.

[0042] The control unit 101 is a calculation unit that executes a predetermined program to realize various functions of the in-vehicle device 100. The control unit 101 may be realized by, for example, a CPU. The control unit 101 is configured to have, as functional modules, a data collection unit 1011, a management unit 1012, and a data transmission unit 1013. Each functional module may be realized by executing a stored program by a CPU.

[0043] The data collection unit 1011 acquires sensor data from one or more sensors included in the sensor group 110 at a predetermined timing, and stores the sensor data in the sensor DB 102A of the storage unit 102. When a plurality of pieces of sensor data are available, the data collection unit 1011 may acquire all of the sensor data. The sensor DB 102A is a database in which sensor data collected from sensors possessed by the vehicle 10 is stored. The data collection unit 1011 may also acquire image data via the camera 120, which is an image sensor, and store the acquired image data in the sensor DB 102A.

[0044] 3C is an example of data stored in the sensor DB 102A. In addition to the sensor data, the sensor DB 102A stores the driver's identifier, the date and time when the sensor data was acquired, the location (location information) when the sensor data was acquired, and the ID of the sensor data.

[0045] Based on the consent obtained from the driver, the management unit 1012 determines which of the sensor data stored in the sensor DB 102A should be transmitted to the server device 200. Specifically, the management unit 1012 executes the following process.

[0046] (1) Processing for receiving usage data from the server device 200 The server device 200 transmits the above-mentioned usage data to the in-vehicle device 100, thereby requesting data from the vehicle 10. In other words, the usage data also functions as data for requesting the vehicle 10 to transmit specific sensor data. As described above, the usage data includes an identifier (data ID) of the sensor data, a type (data type) of the sensor data, a transmission destination of the sensor data, an acquisition condition of the sensor data, a transmission cycle of the sensor data, etc. The usage data may include information for explaining the usage of the sensor data, a business entity that uses the sensor data, risks, benefits, etc. The usage data transmitted from the server device 200 is stored in the storage unit 102 .

[0047] (2) Managing user consent for external transmission of sensor data External transmission refers to transmitting the sensor data to a device (e.g., the server device 200) outside the vehicle 10 (i.e., providing the sensor data to the outside). The management unit 1012 acquires from the driver whether or not there is consent to the provision of specific sensor data included in the usage data received from the server device 200, and generates the consent data described above. The consent data is stored in the storage unit 102 (consent data 102B), and is also transmitted to the server device 200 and stored in the storage unit 202 (consent data 202B). The management unit 1012 determines whether or not to transmit the sensor data requested by the server device 200 based on the consent data and the detection result of the driver.

[0048] (3) A process of identifying sensor data that is requested by the server device 200 and for which permission has been obtained for external transmission. The management unit 1012 determines whether the requested sensor data is permitted to be transmitted to the outside based on the consent data and the usage data, and if transmission is permitted, determines that the sensor data is to be transmitted.

[0049] For example, the management unit 1012 determines whether the in-vehicle device 100 has the sensor data specified by the request data. The management unit 1012 recognizes what type of sensor data is requested by referring to a data ID included in the request data. The management unit 1012 also compares the acquisition condition included in the request data with the records recorded in the sensor DB 102A to determine whether the in-vehicle device 100 has the matching sensor data.

[0050] If the in-vehicle device 100 holds the sensor data specified by the request data and if consent has been given to the provision of the sensor data, the management unit 1012 determines that the sensor data is to be transmitted. In addition, if the driver of vehicle 10 has no history of allowing external transmission of the target sensor data, the management unit 1012 may inquire of the driver of vehicle 10 regarding whether or not transmission is permitted, and update the consent data based on the result of the inquiry.

[0051] The data transmission unit 1013 transmits the sensor data determined by the management unit 1012 from the storage unit 102 to the The acquired information is then transmitted to the server device 200.

[0052] The storage unit 102 is a memory device including a main storage device and an auxiliary storage device. The auxiliary storage device stores an operating system (OS), various programs, various tables, etc., and by loading the programs stored therein into the main storage device and executing them, it is possible to realize various functions that meet a predetermined purpose, as described below. The primary storage device may include a random access memory (RAM) or a read only memory (ROM). The secondary storage device may include an erasable programmable read only memory (EPROM) or a hard disk drive (HDD). It may also include a disk drive (HDD, Hard Disk Drive). may include removable media, i.e., portable recording media.

[0053] The communication unit 103 is a wireless communication interface for connecting the in-vehicle device 100 to a network. The communication unit 103 is configured to be able to communicate with the server device 200 according to a communication standard such as a mobile communication network, a wireless LAN, or Bluetooth (registered trademark).

[0054] The input / output unit 104 is a means for accepting input operations performed by a user of the device and presenting information. In this embodiment, it is made up of one touch panel display. That is, it is made up of a liquid crystal display and its control means, and a touch panel and its control means.

[0055] The sensor group 110 is a collection of multiple sensors that the vehicle 10 has. The multiple sensors may be, for example, a speed sensor, an acceleration sensor, a GPS module, or the like, that acquire data related to the traveling of the vehicle. The multiple sensors may also be, for example, an image sensor, an illuminance sensor, a rainfall sensor, or the like, that acquire data related to the traveling environment of the vehicle 10. The sensor group 110 may include a sensor for collecting data related to the driver or passengers of the vehicle 10. For example, the vehicle passengers may be identified based on an image obtained by capturing an image of the interior of the vehicle, and data related to the passengers may be transmitted as sensor data.

[0056] The camera 120 includes a first camera mounted facing outside the vehicle and a second camera mounted in a position capable of capturing the face of an occupant sitting in the driver's seat. The first camera functions as an image sensor that acquires an image, and the second camera is used to identify the driver of the vehicle 10 based on the facial image. The image acquired by the first camera is also an example of sensor data.

[0057] 2 is an example, and all or part of the illustrated functions may be executed using a dedicated circuit. Also, programs may be stored or executed using a combination of a main memory and an auxiliary memory other than those illustrated.

[0058] Next, the process executed by the in-vehicle device 100 will be described in detail. 4 and 5 are flowcharts of the process executed by the in-vehicle device 100. FIG.

[0059] In addition, in parallel with the execution of the illustrated flowchart, the data collection unit 1011 executes a process of periodically acquiring sensor data from a sensor (or a first camera) included in the sensor group 110 and storing the data in the sensor DB 102A of the memory unit 102.

[0060] The management unit 1012 executes a process of receiving usage data from the server device 200 and a process of transmitting sensor data based on the received usage data. 4 is a flowchart of a process in which the in-vehicle device 100 receives application data from the server device 200. The process shown in the figure is executed at a predetermined timing (for example, when the vehicle's driving system is started).

[0061] First, in step S11, the management unit 1012 makes an inquiry to the server device 200 to determine whether or not there is usage data to be received. Whether or not there is usage data to be received can be determined based on, for example, the last update date and time and the version number of the usage data. For this reason, the server device 200 may notify the in-vehicle device 100 of the last update date and time and the version number of the usage data. Furthermore, the in-vehicle device 100 may store these in the storage unit 102. If there is usage data to be received, the process proceeds to step S12. In step S12, the management unit 1012 receives the usage data from the server device 200 and stores it in the storage unit 102. At this time, old usage data may be deleted.

[0062] 5 is a flowchart of a process in which the on-board device 100 transmits sensor data to the server device 200 based on application data. The illustrated process is periodically executed while the vehicle 10 is traveling. First, in step S21, the management unit 1012 acquires a face image of the driver via the camera 120 (second camera) and identifies the driver based on the face image. The driver can be identified, for example, by comparing a feature amount obtained by converting the face image with a feature amount corresponding to one or more drivers stored in advance. In step S22, the management unit 1012 identifies the sensor data requested by the server device 200 based on the usage data. In this step, the sensor data requested by the server device 200 and stored in the storage unit 102 is specified. The sensor data specified in this step may be of multiple types.

[0063] The processes of steps S23 to S26 are executed for each of the plurality of sensor data identified in step S22. First, in step S23, the management unit 1012 judges whether or not the driver's consent has been obtained for transmitting the target sensor data to the server device 200. For example, if there is a record in the consent data 102B whose data ID and transmission destination match and whose provision permission field is "permitted", this step will be judged as positive. If the provision permission field is "rejected" or if there is no corresponding record (if the driver has not expressed an intention to transmit the target sensor data to the outside), this step will be judged as negative.

[0064] If the determination in step S23 is positive, the process proceeds to step S24, in which the data transmission unit 1013 transmits the corresponding sensor data.

[0065] If the determination in step S23 is negative, the process proceeds to step S25. In step S25, the management unit 1012 judges whether the driver has previously expressed an intention to refuse the transmission of the sensor data having the corresponding data ID. For example, if there is a record in the consent data 102B whose data ID and transmission destination match, and whose provision availability field is "rejected", this step is judged as positive. If the judgment in step S25 is positive, the corresponding sensor data is not transmitted.

[0066] If the determination in step S25 is negative, it means that the driver has not previously expressed an intention regarding the sensor data of the corresponding data ID. In this case, the process proceeds to step S26, where the driver is asked whether or not he or she has given consent. In step S26, the management unit 1012 asks the driver via the input / output unit 104 whether it is OK to transmit the sensor data of the relevant type. The confirmation can be performed, for example, via a screen as shown in FIG. 6(A). The screen may display the type of sensor data, its purpose, transmission destination, acquisition conditions, the business entity that will use the sensor data, and the business entity that will provide the sensor data. This may include information about the risks and benefits of using

[0067] For example, a GUI component for informing the user of risks and benefits may be arranged on the screen, and specific risks and benefits may be provided based on the user's operation. Fig. 6(B) is an example of a screen for informing the user of information related to risks, and Fig. 6(C) is an example of a screen for informing the user of information related to benefits. These screens can be generated based on information included in the usage data. When there are multiple types of sensor data to be transmitted, consent may be obtained for each type on multiple screens, or the user may be allowed to select whether or not to consent to the provision of each type of sensor data on the same screen.

[0068] When the driver responds, the result is reflected in the agreement data 102B and the agreement data 202B. Also, based on the content of the response, the processes of steps S23 and S24 are repeated.

[0069] As described above, according to the first embodiment, data regarding the presence or absence of consent to data transmission is accumulated in the in-vehicle device 100 for each sensor data transmitted from the vehicle 10 to the server device 200 and for each driver. Furthermore, the in-vehicle device 100 controls the transmission of data to the server device 200 based on the data.

[0070] Furthermore, when requesting the driver's consent to the data provision, the in-vehicle device 100 presents information that specifically guides the driver to the risks and benefits that will arise from the data provision. This allows the driver to recognize the risks and benefits that will result from the data provision, and enables the driver to make an appropriate decision.

[0071] Second Embodiment In the first embodiment, the in-vehicle device 100 provides the use of the sensor data, the business entity that uses the sensor data, and an explanation of risks and benefits, etc., based on the use data received from the server device 200. On the other hand, other statistical information may be included in the use data and provided in step S26.

[0072] For example, the server device 200 may calculate a value such as "what percentage of all users have agreed to the data provision" for each data ID based on the consent data acquired from multiple vehicles 10 (on-vehicle devices 100) under its management. Also, the calculated value may be included in the usage data.

[0073] In this case, when inquiring of the driver as to whether or not the driver consents to the data provision in step S26, the in-vehicle device 100 (management unit 1012) may, for example, notify the driver on a screen such as that shown in FIG. 6(A) of "what percentage of all users have consented to the data provision" and then ask the driver for his / her decision. In this embodiment, the percentage of users who agreed to the provision of data is displayed relative to the total number of users. However, other information may be displayed as long as it is related to the overall trend of agreement.

[0074] (Modification) The above-described embodiment is merely an example, and the present disclosure can be modified and implemented as appropriate without departing from the spirit and scope of the present disclosure. For example, the processes and means described in this disclosure can be freely combined and implemented as long as no technical contradiction occurs.

[0075] In the first and second embodiments, a face image is used as information for identifying the driver of the vehicle 10, but the driver of the vehicle 10 may be identified based on other biometric information. Examples of such biometric information include a fingerprint, a voiceprint, and an iris pattern.

[0076] In the description of the embodiment, only the server device 200 is exemplified as a destination of the sensor data, but the sensor data may be transmitted to multiple destinations. In this case, the purpose data may be received from each of the multiple external devices. The destination of the sensor data may be the manufacturer of the vehicle 10 or a related business operator, or a third party with which a data provision contract has been concluded. In addition, in the description of the embodiment, consent was obtained for "transmitting the sensor data outside the vehicle 10," but consent may also be for "providing the sensor data to a specified business operator" or "using the sensor data by the business operator."

[0077] In addition, in the description of the embodiment, consent confirmation is performed on the driver of the vehicle 10, but the subject of confirmation may be a passenger, the owner of the vehicle 10, or the like.

[0078] Furthermore, if the risks and benefits of providing sensor data differ depending on the conditions for providing the data, the risks and benefits for each condition may be explained to the driver, allowing the driver to select under which conditions the data provision contract will be concluded.

[0079] Furthermore, a process described as being performed by one device may be shared and executed by multiple devices. Alternatively, a process described as being performed by different devices may be executed by one device. In a computer system, the hardware configuration (server configuration) by which each function is realized can be flexibly changed.

[0080] The present disclosure can also be realized by supplying a computer program implementing the functions described in the above embodiments to a computer, and having one or more processors of the computer read and execute the program. Such a computer program may be provided to the computer by a non-transitory computer-readable storage medium connectable to the system bus of the computer, or may be provided to the computer via a network. Non-transitory computer-readable storage media include, for example, any type of disk, such as a magnetic disk (floppy disk, hard disk drive (HDD), etc.), an optical disk (CD-ROM, DVD disk, Blu-ray disk, etc.), a read-only memory (ROM), a random access memory (RAM), an EPROM, an EEPROM, a magnetic card, a flash memory, an optical card, and any type of medium suitable for storing electronic instructions. [Explanation of symbols]

[0081] 10. Vehicle 100...In-vehicle equipment 200 Server device 101,201...Control unit 102,202...Storage section 103,203···Communications Department 104...Input / output section 110 Sensor group 120···Camera

Claims

1. Acquiring information regarding a profit to be generated when first data acquired by a first vehicle while traveling is provided to a first business operator; presenting information regarding the benefit to a user associated with the first vehicle; Inquiring of the user as to whether or not the user agrees to provide the first data to the first business entity; An information processing device having a control unit that executes the above.

2. The first data is of multiple types, The control unit acquires and presents information regarding the benefit for each type of the first data. The information processing device according to claim 1 .

3. The information regarding the benefit includes information regarding an incentive to be given to the user in exchange for the first data. The information processing device according to claim 1 .

4. The control unit further presents a condition for acquiring the first data by the first vehicle. The information processing device according to claim 1 .

5. The control unit further presents data regarding a ratio of users who have agreed to provide the first data to the entirety. The information processing device according to claim 1 .

Images