Management device and vehicle information management system

Abstract

The invention relates to a management device and a vehicle information management system. The management device includes a storage device. The management device acquires user meaning information indicating whether a vehicle user agrees to publish vehicle identification information of the vehicle. The management device receives vehicle information including vehicle identification information from the outside via communication. When the vehicle user agrees, the management device stores vehicle information including the vehicle identification information in the storage device. On the other hand, if there is no agreement of the vehicle user, the management device acquires first identification information different from the vehicle identification information, stores in the storage device first corrected vehicle information including the first identification information instead of the vehicle identification information, and deletes the vehicle identification information.

Description

Technical Field

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

[0002] 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 stores the information from the information provider terminal. When providing the stored 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.

[0003] Japanese Patent Application Laid-Open No. 2015-101195 discloses a vehicle information communication system. A vehicle uses transformation information to transform its inherent vehicle identifier into another identifier. The vehicle then associates the vehicle status information with the other identifier and transmits it to a vehicle status information server. Upon receiving a request from a specific operator to utilize the vehicle status information, the vehicle status information server transmits information to the vehicle inquiring whether the vehicle user can utilize the vehicle status information. If the vehicle user permits the use of the vehicle status information, the transformation information is transmitted from the vehicle to the vehicle status information server. The vehicle status information server uses the transformation information received from the vehicle to reverse-transform the other identifier into the original vehicle identifier. The vehicle status information server then associates the vehicle status information with the original vehicle identifier and provides it to the specific operator. Summary of the Invention

[0004] According to the technology described in Japanese Patent Application Laid-Open No. 2007-264730, even when disclosure of information provider attribute information is prohibited, the information provider's attribute information is stored in the intermediary server. This may cause some information providers to dislike or distrust this situation. Furthermore, there is a risk that the information provider's attribute information could leak externally from the intermediary server. This is undesirable from the perspective of protecting personal information.

[0005] A first aspect relates to a management device.

[0006] The management device includes an information processing device including a storage device.

[0007] The information processing device obtains user intention information indicating whether the vehicle user agrees to disclose the vehicle identification information of the vehicle.

[0008] The information processing device receives vehicle information including vehicle identification information from the outside via communication.

[0009] With the consent of the vehicle user, the information processing device stores the vehicle information including the vehicle identification information in the storage device.

[0010] On the other hand, without the vehicle user's consent, the information processing device obtains first identification information different from the vehicle identification information, stores first corrected vehicle information including the first identification information instead of the vehicle identification information in the storage device, and deletes the vehicle identification information.

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

[0012] The vehicle information management system includes a vehicle that stores vehicle information including vehicle identification information, a management device including a storage device, and a first device that provides the vehicle information to the management device via communication.

[0013] The management device obtains user consent information indicating whether the vehicle user agrees to disclose the vehicle identification information.

[0014] The management device receives vehicle information including vehicle identification information from the first device via communication.

[0015] With the consent of the vehicle user, the management device stores the vehicle information including the vehicle identification information in the storage device.

[0016] On the other hand, without the vehicle user's consent, the management device obtains first identification information different from the vehicle identification information, stores first corrected vehicle information including the first identification information instead of the vehicle identification information in the storage device, and deletes the vehicle identification information.

[0017] According to the present disclosure, without the vehicle user's consent, the management device stores first corrected vehicle information containing the first identification information in place of the vehicle identification information. The vehicle identification information is deleted and no longer stored in the management device. Therefore, the vehicle identification information is prevented from leaking from the management device to the outside. This effectively protects the vehicle user's personal information and mitigates any aversion or distrust among vehicle users. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] 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 designate like elements, and in which:

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

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

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

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

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

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

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

[0026] 1. Vehicle Information Management System

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

[0028] 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 / or combinations thereof. Furthermore, information processing device 110 communicates with the outside world via a communication interface.

[0029] 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 / or 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 in a computer-readable recording medium. Generally speaking, the information processing device 110 can also be referred to as a processing circuit.

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

[0031] For example, the vehicle information VCL may include vehicle model information of the vehicle 100 .

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

[0033] 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 may include battery usage history information. This 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). SOH may also be calculated based on the battery usage history information.

[0034] As yet another example, the vehicle information VCL may include troubleshooting information indicating details of a troubleshooting condition occurring in the vehicle 100. The troubleshooting information is obtained by a self-diagnosis function of the vehicle 100, for example.

[0035] The management device 200 communicates with one or more vehicles 100, collects and manages information related to the one or more vehicles 100. The management device 200 can also be called a management server. The management device 200 can also be composed of multiple servers that perform distributed processing.

[0036] 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 / or combinations thereof. Furthermore, information processing device 210 communicates with the outside world via a communication interface.

[0037] 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 between a processor executing a management program and storage device 215. The management program is stored in storage device 215. Alternatively, the management program may be recorded on a computer-readable recording medium. Generally speaking, information processing device 210 may also be referred to as processing circuitry.

[0038] The vehicle information management system 1 may further 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.

[0039] The vehicle information management system 1 may further include a dealership terminal 20 used at a vehicle dealership. At the vehicle dealership, a predetermined tool can be used to read the 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.

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

[0041] Next, the collection and management of the vehicle information VCL in the vehicle information management system 1 of the present embodiment will be described in detail.

[0042] 2. Collection and management of vehicle information

[0043] As mentioned 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 a personal information aspect. From the perspective of protecting personal information, the handling of vehicle information VCL containing the vehicle ID requires careful consideration.

[0044] According to this embodiment, whether the vehicle user U agrees to disclose the vehicle ID to a third party is fully considered. Then, the method of collecting and / or managing the vehicle information VCL is switched according to whether the vehicle user U agrees to disclose the vehicle ID.

[0045] Figure 2 This is a conceptual diagram used to illustrate 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. In general, the term "vehicle 100" in the following description will be replaced with "first device."

[0046] 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 transmits 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.

[0047] The vehicle 100 communicates with the management device 200 and provides the user intention information INT and the vehicle information VCL to the management device 200. The management device 200 receives the user intention information INT and the vehicle information VCL from the vehicle 100.

[0048] If the user intention information INT indicates "agreement", that is, if the vehicle user U agrees, the management device 200 stores the vehicle information VCL including the vehicle ID as is in the storage device 215. That is, the management device 200 stores the vehicle information VCL in association with the vehicle ID.

[0049] On the other hand, when the user intention information INT indicates "disagreement", that is, when the vehicle user U does not agree, the management device 200 obtains the first identification information (hereinafter referred to as "first ID") that is different from the vehicle ID. For example, the management device 200 converts the vehicle ID into the first ID using a conversion algorithm. The management device 200 may also convert the vehicle ID into the first ID using a fixed conversion algorithm. In this case, the first ID is not the original vehicle ID itself, but is different for each vehicle 100. In addition, the management device 200 may also irreversibly convert the vehicle ID into the first ID using an irreversible conversion algorithm. As another example, the first ID may also be a randomly generated random number.

[0050] The management device 200 then replaces the vehicle ID in the vehicle information VCL with the first ID, thereby obtaining first corrected vehicle information VCX1. Specifically, the first corrected vehicle information VCX1 includes the first ID instead of the vehicle ID. The first corrected vehicle information VCX1 can also be said to associate the first ID with other vehicle information VCL. The management device 200 then stores the first corrected vehicle information VCX1 in the storage device 215, rather than the vehicle information VCL.

[0051] Furthermore, the management device 200 deletes the vehicle ID received from the vehicle 100 without the consent of the vehicle user U. That is, the management device 200 does not store the vehicle ID.

[0052] As described above, according to this embodiment, whether the vehicle user U agrees to disclose the vehicle ID is considered. Then, the method of collecting and managing the vehicle information VCL is switched according to whether the vehicle user U agrees to disclose the vehicle ID.

[0053] Without the consent of the vehicle user U, the management device 200 stores the first corrected vehicle information VCX1, which includes the first ID in place of the vehicle ID. The vehicle ID is deleted and not stored in 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. It also reduces the vehicle user U's aversion to and distrust of the vehicle information management system 1.

[0054] On the other hand, if the vehicle user U agrees, the management device 200 does not need to convert the vehicle ID to the first ID. Since the conversion process is not performed uniformly, the processing load on the management device 200 is reduced.

[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 utilized in the management device 200. For example, the vehicle ID is advantageous for market performance analysis. The management device 200 can collect performance information from a large number of vehicles 100. However, if the vehicle ID is not available, only statistical information related to the performance is available. Specifically identifying the cause of the performance based on the statistical information risks being time-consuming. Furthermore, if the vehicle ID is not available, performance information collected from the same vehicle 100 may be counted repeatedly, resulting in a decrease in the accuracy of the statistical information. This decrease in the accuracy of the statistical information also leads to a decrease in the accuracy of the performance analysis. In other words, the inability to utilize the vehicle ID results in a decrease in the efficiency and accuracy of the performance analysis. On the other hand, if the vehicle ID is available, the vehicle 100 experiencing the performance issue can be identified, allowing the cause of the performance issue to be determined efficiently and accurately.

[0056] Without the consent of the vehicle user U, the first corrected vehicle information VCX1 containing the first ID in place of the vehicle ID is stored in the management device 200. The first ID can also be generated by converting the vehicle ID using a fixed conversion algorithm. In this case, the first ID is not the original vehicle ID itself but is unique for each vehicle 100. This prevents duplicate counting of failure information collected from the same vehicle 100, thereby minimizing the accuracy of statistical information related to failures.

[0057] Furthermore, according to the present embodiment, the process of converting the vehicle ID to another ID is not performed in the vehicle 100. Therefore, the processing load in the vehicle 100 is reduced.

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

[0059] Figure 3 This is a conceptual diagram illustrating the first comparative example. According to the first comparative example, vehicle information VCL including a vehicle ID is transmitted from the vehicle to the management device. The vehicle information VCL including the vehicle ID is then stored in the management device, regardless of the vehicle user U's consent. 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 into another ID and provides the corrected vehicle information VCX including the other ID to other systems.

[0060] However, there are also vehicle users U who have aversion or distrust towards storing their vehicle ID in the management device. In addition, there is a risk that the vehicle ID stored in the management device will leak to the outside. This is not desirable from the perspective of protecting personal information.

[0061] On the other hand, according to this embodiment, without the consent of the vehicle user U, the management device 200 stores the first corrected vehicle information VCX1 containing the first ID in place of the vehicle ID. The vehicle ID is deleted and not stored in 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. It also reduces the aversion and distrust that the vehicle user U may harbor towards the vehicle information management system 1.

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

[0063] However, since the vehicle ID is not stored in the management device, it cannot be effectively utilized in the management device. As mentioned above, the vehicle ID is useful for analyzing market downturns, and the inability to effectively utilize the vehicle ID reduces the efficiency and accuracy of downturn analysis. Furthermore, since the vehicle ID must be converted to another ID regardless of the vehicle user U's consent, the processing load on the management device increases.

[0064] On the other hand, according to this embodiment, vehicle information VCL including the vehicle ID is stored in the management device 200 with the consent of the vehicle user U. This allows the vehicle ID to be effectively utilized in the management device 200. Consequently, the cause of the problem can be efficiently and accurately identified. Furthermore, with the consent of the vehicle user U, the management device 200 does not need to convert the vehicle ID to the first ID. This eliminates the need for a uniform conversion process, reducing the processing load on the management device 200.

[0065] Figure 5 This is a conceptual diagram for explaining the third comparative example. According to the third comparative example, the vehicle uses the conversion information to convert the vehicle ID into another ID, regardless of whether the vehicle user U agrees. The vehicle then sends the corrected vehicle information VCX containing the other ID to the management device. The management device stores the corrected vehicle information VCX containing 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 conversion information. In response to the request from the management device, the vehicle sends the conversion information to the management device. The management device uses the conversion information received from the vehicle to reversely convert the other ID into the original vehicle ID. The management device then provides the vehicle information VCL containing the vehicle ID to other systems.

[0066] However, regardless of whether the vehicle user U agrees or not, the vehicle ID is converted to another ID in the vehicle, which increases the processing load in the vehicle. In addition, according to the third comparative example, the vehicle ID is basically not stored in the management device, so it is difficult to effectively use the vehicle ID in the management device. The inability to effectively use the vehicle ID leads to a decrease in the efficiency and accuracy of poor condition analysis. In order to restore the vehicle ID in the management device, as mentioned above, it is necessary to provide conversion information from the vehicle, and therefore, multiple communications are required between the vehicle and the management device. This puts pressure on the communication band and increases the communication cost.

[0067] On the other hand, according to the present embodiment, the process of converting the vehicle ID into another ID is not performed in the vehicle 100. Therefore, the processing load in the vehicle 100 is reduced. In addition, with the consent of the vehicle user U, the vehicle information VCL including the vehicle ID is stored in the management device 200, so that the vehicle ID can be effectively used in the management device 200. Therefore, the cause of the poor condition can be found efficiently and accurately. Furthermore, with the consent of the vehicle user U, the vehicle ID is stored as it 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 helps to reduce the processing load on the entire system. In addition, there is no need to exchange the 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.

[0068] 3. Abstraction of driving history information

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

[0070] For example, driving history information includes the total driving distance of vehicle 100. If the total driving distance is known to the unit's digit, it is possible to identify vehicle 100 based on this total driving distance. Therefore, when providing vehicle information VCL to management device 200, vehicle 100 (information processing device 110) may round the total driving distance included in the vehicle information VCL. For example, rounding the total driving distance may involve discarding decimals below a predetermined digit (e.g., hundreds or thousands). As another example, rounding the total driving distance may involve rounding up decimals below a predetermined digit. As yet another example, rounding the total driving distance may involve rounding up decimals below a predetermined digit. The resulting rounded value of the total driving distance may be, for example, 1000 km or 2000 km. As yet another example, rounding the total driving distance may involve expressing the total driving distance in predetermined distance units. The predetermined distance as a unit is arbitrary, for example, 500km, 2000km, 5000km, etc. can be listed. As an example, if the total driving distance is expressed in units of 2000km, then when the total driving distance is less than 2000km, it is expressed as 0km, when the total driving distance is greater than 2000km and less than 4000km, it is expressed as 2000km, and when the total driving distance is greater than 4000km and less than 6000km, it is expressed as 4000km. The same applies to the case where the predetermined distance is other values. The vehicle information VCL obtained by the rounding described above is not the total driving distance itself, but includes the value obtained by rounding the total driving distance. Such vehicle information VCL is provided from the vehicle 100 to the management device 200. As a result, the protection of personal information is further enhanced.

[0071] As another example, driving history information includes location history information for vehicle 100. The location of vehicle 100 is represented by a combination of latitude and longitude. It is possible to identify vehicle 100 based on the history of latitude and longitude. Therefore, when providing vehicle information VCL to management device 200, vehicle 100 (information processing device 110) may abstract the location history information included in the vehicle information VCL. Abstracting the location history information, for example, means replacing the latitude and longitude history with the name of a predetermined area (e.g., prefecture, city, state, or city). The vehicle information VCL obtained in this manner does not contain the location history information itself, but rather includes abstract location history information obtained by abstracting the location history information. This vehicle information VCL is provided from vehicle 100 to management device 200. This further enhances the protection of personal information.

[0072] As another example, the management device 200 may be used instead of the vehicle 100 to round off the total travel distance and abstract the position history information.

[0073] 4. Provide vehicle information to other systems

[0074] Figure 6 This is a conceptual diagram for explaining information provision to other systems from the management device 200. 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.

[0075] 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 fixed conversion algorithm. In this case, the second ID is not the original 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.

[0076] The management device 200 obtains 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. The second corrected vehicle information VCX2 can also be said to associate the second ID with other vehicle information VCL. Even with the consent of the vehicle user U, the management device 200 provides the second corrected vehicle information VCX2, not the vehicle information VCL itself, to other systems.

[0077] As a result, the vehicle ID is no longer included in the information provided from the management device 200 to other systems, regardless of the consent of the vehicle user U. Thus, the protection of personal information is further enhanced.

Claims

1. A management device, An information processing device including a storage device is provided, The information processing device is composed of: Obtain user consent information indicating whether the vehicle user agrees to disclose the vehicle identification information of the vehicle, receiving vehicle information including the vehicle identification information from the outside via communication, With the consent of the vehicle user, the vehicle information including the vehicle identification information is stored in the storage device. Without the consent of the vehicle user, first identification information different from the vehicle identification information is acquired, first corrected vehicle information including the first identification information instead of the vehicle identification information is stored in the storage device, and the vehicle identification information is deleted.

2. The management device according to claim 1, wherein: The information processing device is configured to convert the vehicle identification information into the first identification information using a fixed conversion algorithm without the consent of the vehicle user.

3. The management device according to claim 1 or 2, wherein: The information processing device is further configured as follows: converting the vehicle identification information included in the vehicle information into second identification information, Even when the vehicle user has given the consent, the second corrected vehicle information including the second identification information instead of the vehicle identification information is provided to other systems.

4. A vehicle information management system comprising: Vehicle, storing vehicle information including vehicle identification information; a management device having a storage device; and The first device provides the vehicle information to the management device via communication, The management device is composed of: Obtaining user consent information indicating whether the vehicle user agrees to disclose the vehicle identification information, receiving the vehicle information including the vehicle identification information from the first device via communication, With the consent of the vehicle user, the vehicle information including the vehicle identification information is stored in the storage device. Without the consent of the vehicle user, first identification information different from the vehicle identification information is acquired, first corrected vehicle information including the first identification information instead of the vehicle identification information is stored in the storage device, and the vehicle identification information is deleted.

5. The vehicle information management system according to claim 4, wherein: The management device is further configured as follows: converting the vehicle identification information included in the vehicle information into second identification information, Even when the vehicle user has given the consent, the second corrected vehicle information including the second identification information instead of the vehicle identification information is provided to other systems.

Images