Vehicle and vehicle information management system

Abstract

The invention provides a vehicle and a vehicle information management system. A vehicle is provided with an information processing device that stores vehicle information including vehicle identification information. The information processing device acquires user meaning information indicating whether a vehicle user agrees to publish the vehicle identification information prior to a stage of providing the vehicle information to the management device. When the vehicle user agrees, the information processing device provides the vehicle information including the vehicle identification information to the management device. On the other hand, when the vehicle user does not consent, the information processing device acquires first identification information different from the vehicle identification information, and provides first corrected vehicle information including the first identification information instead of the vehicle identification information to the management device.

Description

Technical Field

[0001] The present disclosure relates to a technology for collecting and managing vehicle-related information. Background Art

[0002] Japanese Patent Laid-Open No. 2015-101195 discloses a vehicle information communication system. The vehicle uses transformation information to transform the vehicle's inherent vehicle identifier into another identifier. Furthermore, the vehicle sends the vehicle status information and the other identifier in correspondence to a vehicle status information server. In the case of a request from a specific operator to use the vehicle status information, the vehicle status information server sends information to the vehicle for inquiring the vehicle user whether the vehicle status information can be used. In the case of the vehicle user allowing the use of the vehicle status information, the above-mentioned transformation information is sent from the vehicle to the vehicle status information server. The vehicle status information server uses the transformation information received from the vehicle to reversely transform the other identifier into the original vehicle identifier. Furthermore, the vehicle status information server provides the vehicle status information and the original vehicle identifier in correspondence to the specific operator.

[0003] Japanese Patent Application Laid-Open No. 2007-264730 discloses an information intermediary system. The information intermediary system includes an information provider terminal, a user terminal, and an intermediary server. The information provider terminal transmits information to the intermediary server. The intermediary server collects and accumulates the information from the information provider terminal. When providing the accumulated information to the user terminal, the intermediary server replaces the information provider's attribute information, which is not permitted to be disclosed, with dummy information. Summary of the Invention

[0004] According to the technology described in Japanese Patent Application Laid-Open No. 2015-101195, the vehicle identifier is converted to another identifier in the vehicle regardless of whether the vehicle status information is usable. This results in an increase in the processing load in the vehicle.

[0005] The first aspect relates to a vehicle.

[0006] The vehicle includes an information processing device that stores vehicle information including vehicle identification information.

[0007] Before providing the vehicle information to the management device, the information processing device obtains user consent information indicating whether the vehicle user consents to disclosure of the vehicle identification information.

[0008] With the consent of the vehicle user, the information processing device provides the vehicle information including the vehicle identification information to the management device.

[0009] On the other hand, if the vehicle user disagrees, the information processing device obtains first identification information different from the vehicle identification information and provides the management device with first corrected vehicle information including the first identification information instead of the vehicle identification information.

[0010] The second aspect relates to a vehicle information management system.

[0011] The vehicle information management system includes a vehicle storing vehicle information including vehicle identification information, a first device for acquiring the vehicle information, and a management device.

[0012] Before providing the vehicle information to the management device, the first device obtains user consent information indicating whether the vehicle user consents to disclosure of the vehicle identification information.

[0013] With the vehicle user's consent, the first device provides the management device with the vehicle information including the vehicle identification information.

[0014] On the other hand, if the vehicle user disagrees, the first device obtains first identification information different from the vehicle identification information and provides the management device with first corrected vehicle information including the first identification information instead of the vehicle identification information.

[0015] The management device converts the vehicle identification information included in the vehicle information into second identification information, and provides the second corrected vehicle information including the second identification information instead of the vehicle identification information to the other system.

[0016] According to the present disclosure, before providing vehicle information to a management device, user consent information indicating whether the vehicle user consents to the disclosure of vehicle identification information can be obtained. If the vehicle user consents, the vehicle information, including the vehicle identification information, is provided intact to the management device. This eliminates the need to convert the vehicle identification information into first identification information within the vehicle, thereby reducing the processing load within the vehicle. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Features, advantages, and technical and industrial significance of exemplary embodiments of the present invention will be described below with reference to the accompanying drawings, in which like reference numerals represent like elements, and in which:

[0018] Figure 1 This is a conceptual diagram for explaining the outline of the vehicle information management system.

[0019] Figure 2 This is a conceptual diagram used to explain the collection and management of vehicle information.

[0020] Figure 3 This is a conceptual diagram for explaining the first comparative example.

[0021] Figure 4 This is a conceptual diagram for explaining the second comparative example.

[0022] Figure 5 This is a conceptual diagram for explaining the third comparative example.

[0023] Figure 6 This is a conceptual diagram for explaining the provision of information from a management device to other systems. DETAILED DESCRIPTION

[0024] Embodiments of the present disclosure will be described with reference to the accompanying drawings.

[0025] 1. Vehicle Information Management System

[0026] Figure 1 This is a conceptual diagram for explaining the outline of a vehicle information management system 1 according to this embodiment. The vehicle information management system 1 collects and manages information related to vehicles 100. The vehicle information management system 1 includes one or more vehicles 100 and a management device 200. Each vehicle 100 and the management device 200 can communicate with each other via a wireless communication network.

[0027] Each vehicle 100 includes an information processing device 110. Information processing device 110 performs various information processing operations. Furthermore, information processing device 110 includes one or more storage devices 115 to store various information. Examples of storage devices 115 include volatile memory, non-volatile memory, HDDs (Hard Disk Drives), SSDs (Solid State Drives), and combinations thereof. Furthermore, information processing device 110 communicates with the outside world via a communication interface.

[0028] For example, the information processing device 110 includes a controller such as an ECU (Electronic Control Unit). The information processing device 110 may also include a data communication module. The information processing device 110 may also include one or more processors. Examples of processors include general-purpose processors, special-purpose processors, CPUs (Central Processing Units), GPUs (Graphics Processing Units), ASICs (Application Specific Integrated Circuits), FPGAs (Field-Programmable Gate Arrays), integrated circuits, and combinations thereof. The functions of the information processing device 110 may also be implemented through the collaboration of a processor that executes a control program and the storage device 115. The control program is stored in the storage device 115. Alternatively, the control program may be recorded on a computer-readable recording medium. Generally speaking, the information processing device 110 can also be referred to as a processing circuit.

[0029] The storage device 115 of the information processing device 110 stores vehicle information VCL related to the vehicle 100. Specifically, the information processing device 110 stores the vehicle information VCL related to the vehicle 100. The vehicle information VCL includes vehicle identification information unique to the vehicle 100 (hereinafter referred to as the "vehicle ID"). The vehicle ID is also known as the VIN (Vehicle Identification Number). In addition to the vehicle ID, the vehicle information VCL may also include the following information. In other words, the vehicle ID and the following information may be associated with each other in the vehicle information VCL.

[0030] For example, the vehicle information VCL may include vehicle type information of the vehicle 100 .

[0031] As another example, the vehicle information VCL may also include travel history information indicating the travel history of the vehicle 100. For example, the travel history information may include the total travel distance of the vehicle 100. As another example, the travel history information may also include location history information of the vehicle 100. The location of the vehicle 100 may also be represented by a combination of latitude and longitude.

[0032] If vehicle 100 is a battery electric vehicle (BEV) or a hybrid electric vehicle (HEV, PHEV), vehicle information VCL may also include battery information related to the vehicle's battery. For example, battery information includes battery usage history information. Battery usage history information includes at least one of temperature history, SOC (State of Charge) history, current history, voltage history, and charging history. Each history may also be represented by a frequency distribution. Battery information may also include SOH (State of Health), which can be calculated based on the battery usage history information.

[0033] As another example, the vehicle information VCL may include troubleshooting information indicating the details of a troubleshooting that occurred in the vehicle 100. The troubleshooting information can be obtained by a self-diagnosis function of the vehicle 100, for example.

[0034] The management device 200 communicates with one or more vehicles 100 to collect and manage information related to the one or more vehicles 100. The management device 200 can also be called a management server. The management device 200 may be composed of a plurality of servers that perform distributed processing.

[0035] Management device 200 includes an information processing device 210. Information processing device 210 performs various information processing operations. Furthermore, information processing device 210 includes one or more storage devices 215 to store (or maintain) various types of information. Examples of storage devices 215 include volatile memory, nonvolatile memory, HDDs, SSDs, and combinations thereof. Furthermore, information processing device 210 communicates with the outside world via a communication interface.

[0036] Information processing device 210 may also include one or more processors. Examples of processors include general-purpose processors, special-purpose processors, CPUs, ASICs, FPGAs, integrated circuits, and / or combinations thereof. The functions of information processing device 210 may also be implemented through the collaboration of a processor executing a hypervisor and storage device 215. The hypervisor is stored in storage device 215. Alternatively, the hypervisor may be recorded on a computer-readable recording medium. Generally speaking, information processing device 210 may also be referred to as processing circuitry.

[0037] The vehicle information management system 1 may also include a user terminal 10. The user terminal 10 is a terminal used by a vehicle user U. The vehicle user U is a person who uses the vehicle 100. For example, the vehicle user U is the owner of the vehicle 100. Examples of the user terminal 100 include an in-vehicle terminal, a PC, a tablet, a smartphone, and the like. The user terminal 10 can communicate with the vehicle 100 and the management device 200 via a communication network.

[0038] The vehicle information management system 1 may also include a dealership terminal 20 used at a vehicle dealership. At the vehicle dealership, a predetermined tool can be used to read vehicle information VCL from the storage device 115 of the vehicle 100. The vehicle information VCL read from the vehicle 100 is input to the dealership terminal 20. In other words, the dealership terminal 20 can obtain the vehicle information VCL. The dealership terminal 20 can communicate with the management device 200 and the user terminal 10 via a wireless or wired communication network.

[0039] The management device 200 can collect vehicle information VCL from at least one of the information processing device 110 of the vehicle 100 and the retailer terminal 20. Specifically, the management device 200 can collect vehicle information VCL directly from the vehicle 100 or through the retailer terminal 20. For ease of explanation, the information processing device 110 of the vehicle 100 and the retailer terminal 20 are collectively referred to as the "first device." The first device can obtain vehicle information VCL and communicate with the user terminal 10 and the management device 200. The management device 200 can communicate with the first device and collect vehicle information VCL from the first device.

[0040] Hereinafter, the collection and management of vehicle information VCL in the vehicle information management system 1 according to the present embodiment will be described in detail.

[0041] 2. Collection and management of vehicle information

[0042] As described above, the vehicle ID is unique to the vehicle 100. Therefore, the vehicle 100 can be identified based on the vehicle ID. Furthermore, if there is information indicating the correspondence between the vehicle ID and the vehicle user U, the vehicle user U can also be identified based on the vehicle ID. In other words, the vehicle ID can be said to have an aspect of personal information. From the perspective of protecting personal information, the handling of vehicle information VCL, including the vehicle ID, requires careful attention.

[0043] According to this embodiment, before collecting vehicle information VCL, it is carefully considered whether the vehicle user U agrees to disclose the vehicle ID to a third party. In addition, the method of collecting / managing vehicle information VCL is switched based on whether the vehicle user U agrees to disclose the vehicle ID.

[0044] Figure 2 This is a conceptual diagram for explaining the collection and management of vehicle information VCL in this embodiment. As mentioned above, vehicle information VCL can be collected directly from vehicle 100 or via retailer terminal 20. For generalization, "vehicle 100" in the following description will be replaced with "first device."

[0045] The user intention information INT is information indicating whether the vehicle user U agrees to disclose the vehicle ID to a third party. When the vehicle user U agrees to disclose the vehicle ID, the user intention information INT indicates "agree". On the other hand, when the vehicle user U disagrees to disclose the vehicle ID, the user intention information INT indicates "disagree". The vehicle 100 obtains the user intention information INT indicating the intention of the vehicle user U of the vehicle 100. In particular, the vehicle 100 obtains the user intention information INT indicating the intention of the vehicle user U of the vehicle 100 in advance before providing the vehicle information VCL to the management device 200. For example, the vehicle user U uses the user terminal 10 to input the user intention information INT. The user terminal 10 communicates with the vehicle 100 and sends the user intention information INT to the vehicle 100. The vehicle 100 receives the user intention information INT and stores it in the storage device 115.

[0046] If the user intention information INT indicates "agreement," that is, if the vehicle user U agrees, the vehicle 100 communicates with the management device 200 and provides the management device 200 with the vehicle information VCL including the vehicle ID as is. Specifically, the vehicle 100 associates the vehicle ID with the vehicle information VCL and provides it to the management device 200. The management device 200 receives the vehicle information VCL including the vehicle ID via communication and stores it in the storage device 215.

[0047] On the other hand, when the user intention information INT indicates “disagreement”, that is, when the vehicle user U disagrees, the vehicle 100 acquires first identification information (hereinafter referred to as “first ID”) different from the vehicle ID.

[0048] For example, vehicle 100 converts the vehicle ID into a first ID using a conversion algorithm. The conversion algorithm used for the conversion may be common to all vehicles 100. In other words, vehicle 100 may convert the vehicle ID into the first ID using a specific conversion algorithm. In this case, the first ID is not the vehicle ID itself, but is unique to each vehicle 100. Alternatively, vehicle 100 may irreversibly convert the vehicle ID into the first ID using an irreversible conversion algorithm.

[0049] As another example, the first ID may be a randomly generated random number.

[0050] The vehicle 100 obtains first corrected vehicle information VCX1 by replacing the vehicle ID in the vehicle information VCL with the first ID. That is, the first corrected vehicle information VCX1 includes the first ID instead of the vehicle ID. Alternatively, the first corrected vehicle information VCX1 can be said to associate the first ID with the rest of the vehicle information VCL. The vehicle 100 communicates with the management device 200 and provides the management device 200 with the first corrected vehicle information VCX1, rather than the vehicle information VCL itself. In other words, the vehicle 100 associates the first ID with the rest of the vehicle information VCL and provides it to the management device 200. The management device 200 receives the first corrected vehicle information VCX1, which includes the first ID instead of the vehicle ID, via communication and stores it in the storage device 215.

[0051] As described above, according to this embodiment, before collecting vehicle information VCL, whether the vehicle user U agrees to disclose the vehicle ID is considered. In addition, the method of collecting and managing vehicle information VCL is switched based on whether the vehicle user U agrees to disclose the vehicle ID.

[0052] If the vehicle user U agrees, the vehicle 100 directly provides the vehicle information VCL including the vehicle ID to the management device 200. Since the vehicle 100 does not need to convert the vehicle ID into the first ID, the processing load on the vehicle 100 is reduced.

[0053] On the other hand, if the vehicle user U disagrees, the vehicle 100 does not provide the vehicle ID to the management device 200. Therefore, the vehicle ID does not leak from the management device 200 to the outside. This effectively protects the personal information of the vehicle user U. The vehicle user U does not harbor any distrust or aversion towards the vehicle information management system 1.

[0054] Furthermore, if the vehicle user U agrees, the vehicle ID is provided as is, eliminating the need for subsequent inverse conversion of the first ID into the vehicle ID. Even if the vehicle user U disagrees, inverse conversion of the first ID into the vehicle ID will naturally not occur. This elimination of the need for inverse conversion contributes to a reduction in the overall system processing load. Furthermore, since the information required for inverse conversion does not need to be exchanged between the vehicle 100 and the management device 200, communication bandwidth consumption and communication costs are minimized.

[0055] Furthermore, with the consent of the vehicle user U, the vehicle information VCL including the vehicle ID is stored in the management device 200. Therefore, the vehicle ID can be used in the management device 200. For example, the vehicle ID is advantageous for market malfunction analysis. The management device 200 can collect malfunction information from a large number of vehicles 100. However, when the vehicle ID cannot be used, only statistical information related to the malfunction can be obtained. There is a possibility that it will take a long time to specifically determine the cause of the malfunction based on the statistical information. In addition, when the vehicle ID cannot be used, malfunction information collected from the same vehicle 100 is counted repeatedly, and as a result, there is also a possibility that the accuracy of the statistical information is reduced. The reduction in the accuracy of the statistical information leads to a reduction in the accuracy of the malfunction analysis. That is, the inability to use the vehicle ID leads to a reduction in the efficiency and accuracy of the malfunction analysis. On the other hand, when the vehicle ID can be used, the vehicle 100 where the malfunction occurred can be identified, so the cause of the malfunction can be investigated efficiently and with high accuracy.

[0056] If the vehicle user U disagrees, the vehicle 100 provides the management device 200 with first corrected vehicle information VCX1 that includes the first ID in place of the vehicle ID. Alternatively, the first ID can be generated by converting the vehicle ID using a specific conversion algorithm. In this case, the first ID is not the vehicle ID itself, but is unique for each vehicle 100. This prevents duplicate counting of problem information collected from the same vehicle 100, and reduces the accuracy of statistical information related to problems.

[0057] In order to more clearly explain various effects obtainable by this embodiment, comparison with various comparative examples will be made.

[0058] Figure 3 This is a conceptual diagram illustrating the first comparative example. According to the first comparative example, vehicle information VCL including the vehicle ID is transmitted from the vehicle to the management device, regardless of whether the vehicle user U consents. Furthermore, the management device stores the vehicle information VCL including the vehicle ID. If the vehicle user U does not consent to the disclosure of the vehicle ID to a third party, the management device uses the conversion information to convert the vehicle ID to another ID and provides the corrected vehicle information VCX including the other ID to other systems.

[0059] However, some vehicle users U may be averse to or distrustful of having their vehicle IDs sent to or stored in the management device without authorization. Furthermore, there's a possibility that the vehicle ID stored in the management device could leak to the outside. Furthermore, since conversion information is also stored in the management device, even if corrected vehicle information VCX including a different ID is provided to another system, if the conversion information leaks from the management device, there's a possibility that the original vehicle ID could be restored from the other IDs and the conversion information. This is undesirable from the perspective of protecting personal information.

[0060] On the other hand, according to this embodiment, unless the vehicle user U consents, the vehicle ID is not transmitted from the vehicle 100 to the management device 200, nor is the vehicle ID stored in the management device 200. Therefore, the vehicle user U does not harbor any resentment or distrust towards the vehicle information management system 1. Furthermore, the vehicle ID is not leaked from the management device 200 to the outside. Consequently, the personal information of the vehicle user U is effectively protected.

[0061] Figure 4 This is a conceptual diagram illustrating a second comparative example. According to the second comparative example, vehicle information VCL including a vehicle ID is transmitted from the vehicle to the management device, regardless of whether the vehicle user U consents. The management device uses the conversion information to convert the vehicle ID to another ID and then deletes the vehicle ID. The management device then provides corrected vehicle information VCX including the other ID to other systems.

[0062] However, there are still vehicle users U who are averse to having their vehicle IDs sent to the management device without authorization. Furthermore, according to the second comparative example, the vehicle ID is not stored in the management device, making it completely unusable within the management device. As mentioned above, the vehicle ID is useful for analyzing market malfunctions, and the complete inability to utilize the vehicle ID reduces the efficiency and accuracy of malfunction analysis. In other words, using conversion information to reverse-convert other IDs into vehicle IDs within the management device increases the processing load on the management device.

[0063] On the other hand, according to this embodiment, the vehicle ID is not transmitted from the vehicle 100 to the management device 200 unless the vehicle user U consents. Therefore, the vehicle user U will not harbor any resentment or distrust towards the vehicle information management system 1. Furthermore, since the vehicle ID is transmitted from the vehicle 100 to the management device 200 with the consent of the vehicle user U, the vehicle ID can be utilized in the management device 200. Therefore, the cause of a problem can be investigated efficiently and accurately. Furthermore, since the vehicle ID is provided as is with the consent of the vehicle user U, there is no need to subsequently reverse-convert the first ID into the vehicle ID. The elimination of the need for reverse conversion contributes to a reduction in the processing load on the management device 200.

[0064] Figure 5 This is a conceptual diagram for explaining the third comparative example. According to the third comparative example, regardless of whether the vehicle user U agrees, the vehicle uses the transformation information to transform the vehicle ID into another ID. Furthermore, the vehicle transmits the corrected vehicle information VCX including the other ID to the management device. The management device stores the corrected vehicle information VCX including the other ID. In addition, when the vehicle user U permits the disclosure of the vehicle ID, the management device communicates with the vehicle and requests the vehicle to provide the transformation information. In response to the request from the management device, the vehicle transmits the transformation information to the management device. The management device uses the transformation information received from the vehicle to reversely transform the other ID into the original vehicle ID. Furthermore, the management device provides the vehicle information VCL including the vehicle ID to other systems.

[0065] However, converting the vehicle ID to another ID in the vehicle, regardless of whether the vehicle user U agrees, increases the processing load in the vehicle. Furthermore, according to the third comparative example, the vehicle ID is essentially not stored in the management device, making it difficult to utilize the vehicle ID in the management device. This inability to utilize the vehicle ID reduces the efficiency and accuracy of fault analysis. As mentioned above, in order to restore the vehicle ID, the management device must receive conversion information from the vehicle, requiring multiple communications between the vehicle and the management device. This results in increased communication bandwidth pressure and communication costs.

[0066] On the other hand, according to this embodiment, with the consent of the vehicle user U, the vehicle 100 provides the vehicle information VCL including the vehicle ID as is to the management device 200. Since the vehicle ID does not need to be converted into the first ID in the vehicle 100, the processing load in the vehicle 100 is reduced. In addition, with the consent of the vehicle user U, the vehicle ID is sent from the vehicle 100 to the management device 200, so the vehicle ID can be used in the management device 200. Therefore, the cause of the malfunction can be investigated efficiently and accurately. Furthermore, with the consent of the vehicle user U, the vehicle ID is provided as is, so there is no need to perform a process of inversely converting the first ID into the vehicle ID. The fact that there is no need for inverse conversion contributes to reducing the processing load of the system as a whole. In addition, there is no need to exchange information required for inverse conversion between the vehicle 100 and the management device 200, so the consumption of the communication band is suppressed and the communication cost is also suppressed.

[0067] 3. Abstraction of driving history information

[0068] Consider a case where the vehicle information VCL includes travel history information indicating the travel history of the vehicle 100. The possibility that the vehicle 100 is identified based on the travel history of the vehicle 100 is not zero.

[0069] For example, driving history information includes the total driving distance of vehicle 100. Even if the total driving distance is known to a single digit, it is possible to identify vehicle 100 based on the total driving distance. Therefore, when providing the first corrected vehicle information VCX1 to the management device 200, vehicle 100 (information processing device 110) may round the total driving distance included in the first corrected vehicle information VCX1. For example, rounding the total driving distance may involve truncating decimals below a predetermined digit (e.g., 100th or 1000th digit). As another example, rounding the total driving distance may involve rounding up decimals below a predetermined digit. As another example, rounding the total driving distance may involve rounding up decimals below a predetermined digit. As a result, the rounded total driving distance may yield a value such as 1000 km or 2000 km. As another example, rounding the total driving distance may involve expressing the total driving distance in predetermined distance units. The predetermined distance used as a unit is arbitrary, and examples include 500 km, 2000 km, and 5000 km. For example, if the total travel distance is expressed in units of 2000 km, the total travel distance is represented as 0 km if it is less than 2000 km, 2000 km if it is greater than 2000 km but less than 4000 km, and 4000 km if it is greater than 4000 km but less than 6000 km. The same applies to other predetermined distance values. The first corrected vehicle information VCX1 obtained through the rounding described above includes the value obtained by rounding the total travel distance, not the total travel distance itself. This first corrected vehicle information VCX1 is provided from the vehicle 100 to the management device 200. This further strengthens the protection of personal information.

[0070] Similarly, the vehicle 100 (information processing device 110 ) may round the total travel distance included in the vehicle information VCL when providing the vehicle information VCL to the management device 200 . This further strengthens the protection of personal information.

[0071] As another example, driving history information includes location history information of vehicle 100. The location of vehicle 100 is represented by a combination of latitude and longitude. Vehicle 100 can be identified based on the history of latitude and longitude. Therefore, when providing first corrected vehicle information VCX1 to management device 200, vehicle 100 (information processing device 110) may abstract the location history information included in the first corrected vehicle information VCX1. Abstracting the location history information, for example, means replacing the history of latitude and longitude with the name of a predetermined area (e.g., prefecture, city, state, or city). The resulting first corrected vehicle information VCX1 includes the abstracted location history information, rather than the location history information itself. This first corrected vehicle information VCX1 is provided from vehicle 100 to management device 200. This further strengthens the protection of personal information.

[0072] Similarly, the vehicle 100 (information processing device 110 ) may also abstract the location history information included in the vehicle information VCL when providing the vehicle information VCL to the management device 200 . This further strengthens the protection of personal information.

[0073] As another example, the management device 200 may perform rounding of the total travel distance and abstraction of the position history information instead of the vehicle 100. This can also achieve the same effect.

[0074] 4. Provide vehicle information to other systems

[0075] Figure 6 This is a conceptual diagram for explaining information provision from the management device 200 to other systems. When the first corrected vehicle information VCX1 is stored in the management device 200, the management device 200 provides the first corrected vehicle information VCX1 to other systems.

[0076] On the other hand, when the vehicle information VCL is stored in the management device 200, the management device 200 obtains second identification information (hereinafter referred to as "second ID") that is different from the vehicle ID included in the vehicle information VCL. For example, the management device 200 converts the vehicle ID into the second ID using a specific conversion algorithm. In this case, the second ID is not the vehicle ID itself, but is unique for each vehicle 100. Alternatively, the management device 200 may irreversibly convert the vehicle ID into the second ID using an irreversible conversion algorithm. As another example, the second ID may be a randomly generated random number.

[0077] The management device 200 obtains the second corrected vehicle information VCX2 by replacing the vehicle ID in the vehicle information VCL with the second ID. Specifically, the second corrected vehicle information VCX2 includes the second ID instead of the vehicle ID. Alternatively, the second corrected vehicle information VCX2 can be said to associate the second ID with the rest of the vehicle information VCL. Furthermore, even with the consent of the vehicle user U, the management device 200 does not provide the second corrected vehicle information VCX2, rather than the vehicle information VCL itself, to other systems.

[0078] As a result, the vehicle ID is not included in the information provided from the management device 200 to other systems, regardless of whether the vehicle user U agrees or not. This further strengthens the protection of personal information.

Claims

1. A vehicle, An information processing device is provided for storing vehicle information including vehicle identification information, The information processing device is composed of: Before providing the vehicle information to the management device, user consent information indicating whether the vehicle user agrees to disclose the vehicle identification information is obtained. providing the vehicle information including the vehicle identification information to the management device with the consent of the vehicle user, If the vehicle user disagrees, first identification information different from the vehicle identification information is acquired, and first corrected vehicle information including the first identification information instead of the vehicle identification information is provided to the management device.

2. The vehicle according to claim 1, wherein The information processing device is configured to convert the vehicle identification information into the first identification information using a predetermined conversion algorithm if the vehicle user does not consent.

3. The vehicle according to claim 1 or 2, wherein: The vehicle information also includes the total travel distance of the vehicle. The first corrected vehicle information includes a value obtained by rounding off the total travel distance instead of the total travel distance itself.

4. The vehicle according to claim 1 or 2, wherein: The vehicle information also includes the location history information of the vehicle. The first corrected vehicle information includes abstracted position history information obtained by abstracting the position history information, rather than the position history information itself.

5. A vehicle information management system comprising: Vehicle, storing vehicle information including vehicle identification information; A first device obtains the vehicle information; and Management device, The first device is composed of: Before providing the vehicle information to the management device, user consent information indicating whether the vehicle user agrees to disclose the vehicle identification information is obtained. providing the vehicle information including the vehicle identification information to the management device with the consent of the vehicle user, If the vehicle user disagrees, first identification information different from the vehicle identification information is obtained, and first corrected vehicle information including the first identification information instead of the vehicle identification information is provided to the management device. The management device is composed of: converting the vehicle identification information included in the vehicle information into second identification information, Even when the vehicle user agrees, the second corrected vehicle information including the second identification information instead of the vehicle identification information is provided to other systems.

Images