Data management system, data management method, and server

Abstract

To promote driving in consideration of at least one of environment and safety.SOLUTION: A data management system 20 includes a marketplace 1 that manages a digital asset as a non-fungible token (NFT), and a driver terminal 5 used by a driver of a vehicle 4 to acquire the NFT. The marketplace 1 registers a plurality of target conditions in association with the NFT, the plurality of target conditions being conditions concerning at least one of environment and safety that are desired to be achieved during driving. The marketplace 1 obtains data for determining whether driving of the vehicle 4 by the driver has achieved a selected target condition, from the vehicle 4, the driver terminal 5, or a data center. When the driving of the vehicle 4 by the driver has achieved the selected target condition, the marketplace gives the NFT associated with the achieved target condition to the driver terminal 5.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] This disclosure relates to a data management system, a data management method, and a server.

Background Art

[0002] Japanese Unexamined Patent Application Publication No. 2022-13271 (Patent Document 1) discloses a non-fungible token circulation platform that does not require wallet preparation, private key management, or payment of network fees (such as gas).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] Vehicles are widely used as means of transportation. In recent years, all drivers are required to drive in an environmentally conscious manner. Also, safe driving is an obligatory duty for all drivers. Nevertheless, there are cases where driving that is not sufficiently environmentally conscious or safe driving is not performed. This disclosure has been made to solve the above problems, and one of the objects of this disclosure is to promote driving that takes into account at least one of the environment and safety.

Means for Solving the Problems

[0005] (1) The data management system according to the first aspect of this disclosure comprises a server that manages digital assets as non-fungible tokens (NFTs) and a first computer device used by a vehicle driver to acquire non-fungible tokens. The server registers each of a plurality of target conditions, which are conditions relating to at least one of the environment and safety that are desirable to be achieved during driving, associating each with a non-fungible token. The first computer device notifies the server of the target conditions selected by the driver from among the plurality of target conditions. The server obtains data from the vehicle, the first computer device, or an external server to determine whether the driver's driving of the vehicle has achieved the selected target conditions, and if the driver's driving of the vehicle has achieved the selected target conditions, it grants the first computer device a non-fungible token associated with the achieved conditions.

[0006] (2) The data management system further comprises a second computer device that requests the registration of target conditions. The server associates information indicating the person who registered the target conditions with a digital asset and registers it in a non-fungible token.

[0007] (3) A non-fungible token includes a digital image for visual verification of the non-fungible token. The data management system further includes a third computer device that requests registration of the digital image. The server registers the non-fungible token by associating information indicating the designer of the digital image with the digital asset.

[0008] (4) The data management system further comprises a fourth computer device for trading non-fungible tokens. The server trades non-fungible tokens when an agreement for trading non-fungible tokens is reached between the driver and the trader, or between the trader and other traders.

[0009] (5) The data management system further comprises other servers. These other servers include a distributed ledger where non-fungible tokens are stored and function as nodes in the blockchain network.

[0010] (6) A data management method relating to a second aspect of this disclosure includes the steps of: storing transaction data, including non-fungible tokens which are digital assets, in a distributed ledger; registering target conditions relating to at least one of environmental and safety conditions which are desirable to be achieved during driving, in association with the non-fungible tokens; obtaining data for determining whether the vehicle has achieved the target conditions; and, if the vehicle has achieved the target conditions, granting the driver of the vehicle a non-fungible token associated with the achieved target conditions.

[0011] (7) The registration step includes registering the target condition if the target condition satisfies the law and international standards, and modifying the target condition to satisfy the law and international standards and registering the modified target condition if the target condition does not satisfy the law and international standards.

[0012] (8) The target conditions include at least one of the following: fuel consumption or electricity consumption is better than specified; air conditioning power consumption is less than specified; greenhouse gas emissions are less than standard amounts; rest periods are longer than the first hour; and continuous operating time is shorter than the second hour.

[0013] (9) The server relating to the third aspect of this disclosure includes a processor that executes the data management method described above.

[0014] In the configurations described in (1) to (5) above, a digital asset is awarded as a non-fungible token to the driver (first computer device) of a vehicle that has achieved the target conditions. The target conditions are set with respect to at least one of the environmental and safety aspects that are desirable to achieve during driving. This provides the driver with an incentive to achieve the target conditions and acquire non-fungible tokens. Therefore, according to the configurations described in (1) to (5) above, driving that takes into consideration at least one of the environmental and safety aspects can be promoted. Furthermore, according to the methods described in (6) to (8) above and the configuration described in (9) above, driving that takes into consideration the environmental or safety aspects can be promoted in a similar manner to the configurations described in (1) to (5) above. [Effect of the Invention]

[0015] According to the present disclosure, it is possible to promote driving that takes into account at least one of environment and safety. [Brief Description of the Drawings]

[0016] [Figure 1] It is a figure which shows an example of the whole structure of the blockchain ecosystem which concerns on embodiment of this indication. [Figure 2] It is a figure which shows another example of the whole structure of the blockchain ecosystem which concerns on embodiment of this indication. [Figure 3] It is a block diagram which shows a typical structural example of a marketplace. [Figure 4] It is a conceptual diagram of the NFT badge in this embodiment. [Figure 5] It is a figure for demonstrating the target condition for acquiring an NFT badge. [Figure 6] It is a figure for demonstrating the outline of the process related to the NFT badge in this embodiment. [Figure 7] It is a sequence diagram which shows a series of processing procedures regarding registration of an NFT badge. [Figure 8] It is a flowchart which shows an example of the processing procedure regarding certification of a target condition. [Figure 9] It is a sequence diagram which shows a series of processing procedures regarding awarding of an NFT badge. [Figure 10] It is a sequence diagram which shows a series of processing procedures regarding trading of an NFT badge. [Mode for Carrying Out the Invention]

[0017] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. In the drawings, the same or corresponding parts are denoted by the same reference numerals, and the description thereof will not be repeated.

[0018] [Embodiment] [System Configuration] FIG. 1 is a diagram showing an example of the overall configuration of a blockchain ecosystem according to an embodiment of the present disclosure. The blockchain ecosystem 10 manages data using blockchain technology. In the present embodiment, the data managed by the blockchain ecosystem 10 is a non-fungible token (NFT) given to the way of driving a vehicle. More specifically, when “target conditions” (details will be described later) registered in advance regarding driving with consideration for the environment and / or safety are achieved, a proof NFT is given to the driver. Since this proof has a badge-type design, hereinafter, the proof NFT will be referred to as an “NFT badge”. The NFT badge will be described in detail after FIG. 4.

[0019] The blockchain ecosystem 10 includes a plurality of nodes 9 and a data management system 20.

[0020] Each of the plurality of nodes 9 is a computer device such as a server. Blockchain-based software is installed on each node 9. A distributed ledger network (blockchain network) is formed by a plurality of nodes 9 each having a blockchain node function communicating with each other via a network NW. The distributed ledger network may be a public type, a consortium type, or a private type.

[0021] The data management system 20 includes, for example, a marketplace 1, a plurality of designer terminals 2, a plurality of registrant terminals 3, a plurality of vehicles 4, a plurality of driver terminals 5, and a plurality of trader terminals 6. The number of each component included in the data management system 20 is not particularly limited. To avoid complexity, hereinafter, the data management system 20 will be described assuming that it includes one of each component.

[0022] Marketplace 1 is operated by an organization (such as a company, association, or joint venture) that manages NFT badges. Marketplace 1 typically includes a server (see Figure 3). Marketplace 1 is connected to Designer Terminal 2, Registrant Terminal 3, Vehicle 4, Driver Terminal 5, and Trader Terminal 6 via wired or wireless communication. Marketplace 1 manages (distributes) the costs and rewards incurred in connection with various processes related to NFT badges (registration, issuance, exchange, etc.).

[0023] Marketplace 1, for example, obtains driving information for vehicle 4 from driver terminal 5. The method of obtaining driving information for vehicle 4 is not limited. Marketplace 1 may obtain driving information for vehicle 4 directly from vehicle 4, or it may obtain driving information for vehicle 4 from a data center that collects driving information for various vehicles (typically a server operated by the vehicle manufacturer).

[0024] Marketplace 1 is communicatively connected to at least one of the multiple nodes 9. Nodes 9 connected to Marketplace 1 are referred to as node 91, and those not directly connected to Marketplace 1 are referred to as node 92. Marketplace 1 may request node 91 to issue NFT badges or to change the ownership of NFT badges (for example, to exchange NFT badges).

[0025] The designer terminal 2, registrant terminal 3, driver terminal 5, and trader terminal 6 are typically smartphones, tablets, personal computers, workstations, etc. However, a server may be used instead of such client terminals.

[0026] Designer terminal 2 registers the NFT badge design (a digital image for visually confirming the NFT) created by the designer. Registrant terminal 3 registers the target conditions for drivers to earn NFT badges. Target conditions can be registered by various registrants (in other words, they can be publicly solicited). Vehicle 4 is driven by the driver. NFT badges are awarded according to how the driver drives vehicle 4. Driver terminal 5 displays the NFT badges and accepts driver operations related to the issuance and trading of NFT badges. Trader terminal 6 displays the NFT badges and accepts trader operations related to the trading of NFT badges between drivers and traders (or between traders themselves).

[0027] Marketplace 1 corresponds to the "server" in this disclosure. Driver terminal 5 corresponds to the "first computer equipment" in this disclosure. Registrant terminal 3 corresponds to the "second computer equipment" in this disclosure. Designer terminal 2 corresponds to the "third computer equipment" in this disclosure. Trader terminal 6 corresponds to the "fourth computer equipment" in this disclosure. Node 9 (Node 91) corresponds to the "other server" in this disclosure. Data center corresponds to the "external server" in this disclosure.

[0028] Figure 2 shows another example of the overall configuration of a blockchain ecosystem according to an embodiment of this disclosure. The blockchain ecosystem 10A shown in Figure 2 includes a data management system 20A. The data management system 20A differs from the data management system 20 shown in Figure 1 in that the marketplace 1A has blockchain node functionality. The marketplace 1A can issue NFT badges and change the ownership of NFT badges through its node functionality.

[0029] In this disclosure, "issuing an NFT" is not limited to Marketplace 1A issuing NFTs itself, as shown in the system configuration of Figure 2, but also includes Marketplace 1 requesting an external node 91 to issue an NFT badge, as shown in the system configuration of Figure 1 (see Figure 9). The same applies to other processes related to NFT badges (such as changing ownership). The following explanation will use the system configuration of Figure 1 as an example, but those skilled in the art should be able to appropriately substitute it with the system configuration of Figure 2.

[0030] Figure 3 is a block diagram showing a typical configuration example of Marketplace 1. Marketplace 1 includes a management server 11, an input device 12, an output device 13, and a communication device 14. The management server 11 includes a processor 111, memory 112, storage 113, and a network interface 114. The components of the management server 11 are connected to each other by a communication bus.

[0031] The processor 111 is a computing device such as a CPU (Central Processing Unit) or MPU (Micro-Processing Unit). The memory 112 is volatile memory (working memory) such as RAM (Random Access Memory). The storage 113 is rewritable non-volatile memory such as an HDD (Hard Disk Drive), SSD (Solid State Drive), or flash memory.

[0032] Storage 113 stores a system program 71, which includes the OS (Operating System), and a control program 72, which includes computer-readable code necessary for control calculations. The processor 111 reads the system program 71 and the control program 72, loads them into memory 112, and executes them to perform various processes. Storage 113 also stores a designer management database 73, a registrant management database 74, a driver management database 75, and a trader management database 76.

[0033] The designer management database 73 includes, for example, a designer ID, basic designer information (name, address, email address, etc.), a registration history of NFT badge designs (designs registered in the past), and account information used for the exchange of fees and / or rewards. The registrant management database 74 includes, for example, a registrant ID, basic registrant information, a registration history of goal conditions for earning NFT badges, and account information. The driver management database 75 includes, for example, a driver ID, basic driver information, NFT badge ownership information (ownership history), and account information. The trader management database 76 includes, for example, a trader ID, basic trader information, NFT badge ownership information, and account information. Note that the driver management database 75 and the trader management database 76 may be integrated into a single database. The processor 111 registers, updates, and deletes records in these databases.

[0034] The network interface 114 is connected to the input device 12, the output device 13, and the communication device 14. The input device 12 is a keyboard, mouse, etc., and accepts input from the operator of the management server 11. The output device 13 is, for example, a display, which displays various information to the operator of the management server 11. The communication device 14 performs data communication with external devices of the marketplace 1 (designer terminal 2, registrant terminal 3, node 91, etc.).

[0035] Although Figure 3 shows an example in which the management server 11 includes one processor 111, the management server 11 may include multiple processors. That is, the management server 11 includes one or more processors. The same applies to the memory 112 and storage 113. In this specification, "processor" is not limited to a processor in the narrow sense that executes processing in a stored-program manner, but may include hardwired circuits such as ASICs (Application Specific Integrated Circuits) and FPGAs (Field-Programmable Gate Arrays). Therefore, the term "processor" can also be interpreted as processing circuitry in which processing is predefined by computer-readable code and / or hardwired circuits.

[0036] <NFTバッジ> Figure 4 is a conceptual diagram of an NFT badge in this embodiment. An NFT badge includes, for example, a badge design and a serial number. The NFT badge is stored in a distributed ledger (blockchain in this example) along with information indicating the designer of the NFT badge's design, information indicating the registrant who has met the target conditions for obtaining the NFT badge, and information indicating the current owner (driver or trader) of the NFT badge.

[0037] Figure 5 illustrates the target conditions for earning an NFT badge. The target conditions include at least one of the following: eco-conditions and safety conditions. Eco-conditions are the conditions for determining whether environmentally conscious driving was performed. Safety conditions are the conditions for determining whether safe driving was performed (whether the driver was in a state capable of safe driving).

[0038] Figure 5 illustrates six exemplary target conditions 1-6. Target conditions 1-4 are eco-conditions, while target conditions 5 and 6 are safety conditions. Here, we describe an example where the aggregation period for the parameters related to each target condition is one month, but the aggregation period can be set to any period.

[0039] Target conditions 1 and 2 are conditions related to fuel efficiency (or electric energy efficiency). For example, Marketplace 1 determines that Target Condition 1 has been achieved if the average fuel efficiency for one month is better than a predetermined value A [km / L], the distance traveled in one month is longer than a predetermined distance B [km], and the vehicle is a specific vehicle model C. Fuel efficiency may be expressed as an absolute value (A [km / L]) as in Target Condition 1, or as a relative value within the same vehicle model (within the top D%) as in Target Condition 2.

[0040] Target condition 3 is a condition relating to the settings of the air conditioning (A / C) system installed in the vehicle. Target condition 3 is achieved, for example, when the monthly power consumption of the air conditioning system is a predetermined amount G [kWh], the monthly driving distance is longer than a predetermined distance H [km], and the vehicle type is a specific vehicle type I. Target condition 3 may include, in place of or in addition to, conditions relating to other parameters that affect power consumption, such as the set temperature of the air conditioning system and the set airflow rate of the air conditioning system.

[0041] Target condition 4 concerns the emission of thermal gases from the vehicle. Target condition 4 is achieved, for example, when the monthly CO2 emissions are less than a predetermined amount J [kg] and the vehicle type is a specific vehicle type I. The emission of thermal gases such as CO2 can be calculated from the vehicle's activity level (fuel consumption and / or power consumption) and a known emission factor (emissions per unit of activity). Target condition 4 may also include, in addition to or instead of, conditions concerning the emission of air pollutants such as NOx (nitrogen oxides) and PM (particulate matter).

[0042] Target condition 5 concerns the continuous driving time of the vehicle. Target condition 5 is achieved, for example, when the continuous driving time in a month is less than a predetermined L hours. Target condition 6 concerns the rest time taken between two driving trips. Target condition 6 is achieved, for example, when at least N hours of rest are taken after driving longer than M hours in a month.

[0043] If a driver achieves a target condition, Marketplace 1 grants the driver an NFT badge associated with that target condition, depending on the condition achieved. For example, one NFT badge may be associated with each of target conditions 1 through 6. Alternatively, one NFT badge may be associated with a combination of two or more conditions from target conditions 1 through 6.

[0044] NFT badges may be ranked according to the difficulty of achieving the objective conditions. For example, if a relatively easy objective condition is achieved, Marketplace 1 will award the driver a regular NFT badge (common badge). If a relatively difficult objective condition is achieved, Marketplace 1 will award the driver a rare NFT badge (rare badge). If an extremely difficult objective condition is achieved, Marketplace 1 will award the driver an extremely rare NFT badge (super rare badge).

[0045] <Processing Overview> Figure 6 is a diagram illustrating the overview of the processing related to NFT badges in this embodiment. The designer terminal 2 has an application (software) installed for registering badge designs for NFT badges. When the designer creates a badge design, they load the badge design into the application. The designer terminal 2 then applies (requests) the registration of the loaded badge design to the marketplace 1.

[0046] The registrant terminal 3 has an application (software) installed for registering NFT badges. Registrants who wish to register an NFT badge select their desired badge design from the various badge designs registered on Marketplace 1 using the application. Registrants also enter the target conditions for obtaining the NFT badge. Registrant terminal 3 notifies Marketplace 1 of the selected badge design according to the registrant's actions and requests Marketplace 1 to register the entered target conditions.

[0047] The target conditions submitted from the registrant terminal 3 are not necessarily appropriate from an environmental and safety standpoint. The target conditions may be illegal (non-compliant with regulations). The target conditions may be excessively easy or difficult to achieve and therefore substantially meaningless. Therefore, it is preferable for Marketplace 1 to certify whether the target conditions submitted from the registrant terminal 3 are appropriate. Marketplace 1 may certify and register only target conditions that meet predetermined criteria. Alternatively, Marketplace 1 may modify some of the target conditions submitted from the registrant terminal 3 to meet predetermined criteria and register the modified target conditions.

[0048] The registrant terminal 3 may pay the fees associated with registering the NFT badge to Marketplace 1. As explained in Figure 4, the NFT badge is associated with the name of the registrant (usually a company name). Therefore, it is assumed that the registrant willingly pay the fees as advertising costs for their registrant name (sponsor fees for the NFT badge). The operator of Marketplace 1 receives a portion of the fees paid from the registrant terminal 3 to Marketplace 1 as a registration fee. As will be explained in more detail later, another portion of the fees paid from the registrant terminal 3 to Marketplace 1 may be paid to the designer terminal 2 via the administrator server 1. This allows the designer of the badge design selected by the registrant to receive compensation (design usage fees).

[0049] However, the registered device 3 is not always the one paying the fees; it may also receive rewards. For example, when participating in an activity to earn an NFT badge, the driver may pay a fee (participation fee), and the registered device 3 may receive a portion of that fee.

[0050] In this example, it is assumed that fees and rewards are exchanged using cryptocurrency (digital assets). However, the currency used for exchanging fees and rewards is not limited to cryptocurrency; it may also be real currency (cash, account balance). Points from a points service may be used instead of currency.

[0051] The driver terminal 5 has an app installed for earning NFT badges. The driver selects an NFT badge to try to earn from among the various NFT badges and target conditions registered in Marketplace 1 via the app. The driver terminal 5 notifies Marketplace 1 of the selected NFT badge (activity participation).

[0052] The driver terminal 5 may also have an application installed for acquiring vehicle driving information. For example, the driver terminal 5 periodically acquires parameters related to the target conditions of the selected NFT badge (such as fuel consumption, mileage, thermal gas emissions, and continuous driving time) from a data center that collects various vehicle information. The driver terminal 5 then sends the acquired parameters to the marketplace 1.

[0053] Marketplace 1 determines whether the target conditions have been met based on the parameters obtained from driver terminal 5. If the target conditions are met, Marketplace 1 grants an NFT badge to driver terminal 5.

[0054] The trader terminal 6 has an application installed for trading NFT badges. Trading NFT badges can be a transaction between an NFT badge and cryptocurrency, or an exchange of NFT badges with each other. The trader terminal 6 displays NFT badges owned and collected by various drivers and traders. Traders select the NFT badge they wish to trade between drivers and traders (or between one trader and another) using the application. If both the driver and traders agree to the transaction, the trader terminal 6 requests the transaction of the selected NFT badge from Marketplace 1. Marketplace 1 notifies the trader terminal 6 of the completion of the transaction (completion of the NFT badge exchange).

[0055] <Processing Procedure> <<Registering an NFT Badge>> Figure 7 is a sequence diagram showing a series of processing steps related to the registration of an NFT badge. In the diagram, from left to right, the processes are shown to be executed by the trader terminal 6, the driver terminal 5 (which may also be the vehicle 4), the registrant terminal 3, the designer terminal 2, the marketplace 1, and the node 91 (blockchain). The same applies to Figures 9 and 10, which will be described later. Hereafter, steps will be abbreviated as S.

[0056] In S101, the designer terminal 2 requests (applies for) the registration of the badge design created by the designer to the marketplace 1. The marketplace 1 registers the badge design in accordance with the request from the designer terminal 2 (S102). At this time, the marketplace 1 may review whether the badge design is appropriate in light of copyright, public order and morals, etc.

[0057] In S103, the registrant terminal 3 selects a badge design according to the registrant's operation. The registrant terminal 3 also requests (applies for) the registration of target conditions to marketplace 1 according to the registrant's operation. Marketplace 1 certifies whether the target conditions requested for registration by the registrant terminal 3 are appropriate (S104).

[0058] Figure 8 is a flowchart showing an example of the processing procedure for determining target conditions (processing procedure S104). The process shown in this flowchart is executed by Marketplace 1 when, for example, a request for registration of target conditions is received from the registrant terminal 3 (when the target conditions are entered by the registrant).

[0059] In S41, Marketplace 1 determines whether the target conditions entered by the registrant include eco-conditions. If the target conditions include eco-conditions (YES in S41), Marketplace 1 determines whether the eco-conditions included in the target conditions meet predetermined criteria (S42). The criteria are set to meet at least laws (including government ordinances, ministerial ordinances, circulars, etc.) and international standards, and preferably to values ​​that are reasonable from the standpoint of social responsibility. If the eco-conditions included in the target conditions meet the criteria (YES in S42), Marketplace 1 proceeds to S45. If the eco-conditions included in the target conditions do not meet the criteria (NO in S42), Marketplace 1 modifies the eco-conditions to meet the criteria (S43) and proceeds to S45. If the target conditions do not include eco-conditions in S41 (NO in S41), Marketplace 1 adds eco-conditions that meet the criteria (S44) and then proceeds to S45.

[0060] In S45, Marketplace 1 determines whether the target conditions entered by the registrant include safety conditions. If the target conditions include safety conditions (YES in S45), Marketplace 1 determines whether the safety conditions included in the target conditions meet predetermined standards (S46). These standards, like the standards for eco-conditions, are predetermined from the perspectives of law, international standards, and social responsibility. If the safety conditions included in the target conditions meet the standards (YES in S46), Marketplace 1 proceeds to S49. If the safety conditions included in the target conditions do not meet the standards (NO in S46), Marketplace 1 modifies the safety conditions to meet the standards (S47) and proceeds to S49. If the target conditions do not include safety conditions in S45 (NO in S45), Marketplace 1 adds safety conditions that meet the standards (S48) and then proceeds to S49.

[0061] In S49, Marketplace 1 provisionally registers target conditions that meet ecological and safety requirements.

[0062] Referring again to Figure 7, in S105, Marketplace 1 sends the provisionally registered target conditions to Registrant Terminal 3 and asks the Registrant to confirm whether there are any problems with the provisionally registered target conditions (whether they are acceptable). If the Registrant accepts, Registrant Terminal 3 notifies Marketplace 1 of this (S106). Registrant Terminal 3 also sends transaction data for sending cryptocurrency to Node 91 according to the Registrant's operation (S107). Node 91 sends the registration fee to Marketplace 1 (S108). When Marketplace 1 receives the acceptance notification from Registrant Terminal 3 and the registration fee has been received, it registers the target conditions that were in the provisionally registered state (S109). As a result, the NFT badge (a combination of badge design and target conditions) is registered.

[0063] As mentioned above, if an NFT badge is registered, a portion of the registration fee may be returned to the designer who created the badge data used for the NFT badge. In S110, Marketplace 1 sends a portion of the registration fee to Designer Terminal 2 as a design usage fee.

[0064] In S111, Marketplace 1 notifies the driver terminal 5 of the newly registered NFT badge. The driver terminal 5 displays the newly registered NFT badge and introduces it to the driver (user). When the driver confirms the NFT badge on the app and decides to participate in the activity to acquire the NFT badge (S112), the driver terminal 5 notifies Marketplace 1 of the participation (S113). Although not shown, the driver terminal 5 may pay a participation fee to Marketplace 1 for the activity.

[0065] In Figure 8, it was explained that the target conditions include both ecological and safety conditions. From an environmental and safety perspective, it is desirable for the target conditions to include both conditions. However, as explained in Figure 5, the target conditions may include only one of the ecological or safety conditions.

[0066] ≪NFT Badge Granting≫ Figure 9 is a sequence diagram showing a series of processing steps related to the granting of NFT badges. In S201, Marketplace 1 determines whether the conditions for starting an activity to acquire an NFT badge have been met (for example, whether the start time of the period specified in the target conditions has arrived). If the conditions for starting are met, Marketplace 1 notifies the driver terminal 5 of the start of the activity (S202). Marketplace 1 may also notify the vehicle 4 of the start of the activity in addition to the driver terminal 5.

[0067] In S203, the driver terminal 5 transmits the driving information of the vehicle 4 to the marketplace 1. As mentioned above, the driver terminal 5's application periodically obtains the driving information of the vehicle 4 from a data center that collects the vehicle 4's driving information. The driver terminal 5 may transmit parameters related to the target conditions (fuel consumption, mileage, thermal gas emissions, continuous driving time, etc.) to the marketplace 1 after a period defined in the target conditions (e.g., one month) has elapsed. The driver terminal 5 may transmit parameters related to the target conditions to the marketplace 1 at shorter time intervals (e.g., once a day). Alternatively, the parameters related to the target conditions may be transmitted from the vehicle 4 to the marketplace 1.

[0068] Marketplace 1 stores driving information (parameters related to target conditions) obtained from the driver terminal 5 (or vehicle 4) in the driver management database 75 (see Figure 3) (S204). Marketplace 1 determines whether a predetermined termination condition has been met (for example, whether the end time of the period defined in the target condition has arrived) (S205). Here, we assume a situation where the target condition was achieved at the time the termination condition was met.

[0069] In steps S206-S208, Marketplace 1 performs the NFT issuance process together with Node 91. More specifically, Marketplace 1 first generates an NFT badge and associates the NFT badge with a driver ID (S206). Marketplace 1 sends the associated NFT badge and driver ID to Node 91 (S207). Node 91 issues a transaction based on the data from Marketplace 1 (S208). That is, Node 91 generates transaction data, adds an electronic signature to the generated transaction data, and sends it to other Nodes 92 in the blockchain ecosystem 10. The transaction data sent to other Nodes 92 is added to the distributed ledger (blockchain) of the other Nodes 92 based on a known consensus algorithm.

[0070] In S209, Marketplace 1 confirms the addition of the transaction data to the distributed ledger. Once the addition of the transaction data is confirmed, Marketplace 1 grants an NFT badge to driver terminal 5 (S210). As a result, driver terminal 5 acquires the NFT badge (S211).

[0071] In this example, if an NFT badge is awarded, a portion of the costs (registration fee and / or participation fee) is returned to the designer of the badge design and the registrant who met the target conditions for that NFT badge. Marketplace 1 sends a portion of the costs to designer terminal 2 (S212). Marketplace 1 also sends a portion of the costs to registrant terminal 3 (S213).

[0072] Trading NFT badges Figure 10 is a sequence diagram illustrating a series of processing steps related to NFT badge trading. Here, we describe an example where an NFT badge is transferred from a driver to a trader, and the NFT badge cryptocurrency is paid from the trader to the driver.

[0073] In S301, driver terminal 5 lists the NFT badge on marketplace 1. That is, the driver's NFT badge becomes available for purchase. In S302, trader terminal 6 selects the NFT badge it wishes to purchase on marketplace 1. This means that an agreement for the NFT badge transaction is reached between driver terminal 5 and trader terminal 6.

[0074] In S303, Marketplace 1 requests the transaction terminal 6 to send cryptocurrency. The amount to be sent is the sum of the NFT badge price and the transaction fee. The transaction terminal 6 sends transaction data for sending cryptocurrency to node 91 according to the transaction operator's instructions (S304). Node 91 sends the NFT badge price to driver terminal 5 (S305). Node 91 also sends the transaction fee to Marketplace 1 (S306).

[0075] In S307, Marketplace 1 requests Node 91 to transfer the NFT badge from the driver to the trader (change of ownership). Node 91 responds to the request from Marketplace 1 and issues a transaction to transfer the NFT badge (S308). This changes the ownership information of the NFT badge from the driver to the trader. After the transaction is completed, Node 91 notifies Marketplace 1 that the NFT badge has been transferred from the driver to the trader (S309). Subsequently, Node 91 notifies the driver terminal 5 and the trader terminal 6 that the transaction (exchange of NFT badge for payment) is complete (S310, S311).

[0076] In this example, when an NFT badge is traded, a portion of the transaction fee is returned to the designer and registrant of the NFT badge. Marketplace 1 sends a portion of the transaction fee as a reward to designer terminal 2 (S312). Marketplace 1 also sends a portion of the transaction fee as a reward to registrant terminal 3 (S313).

[0077] Figure 10 illustrates an example of exchanging NFT badges for cryptocurrency. However, NFT badges can also be exchanged for other NFT badges. Those skilled in the art will easily understand the processing procedures for such transactions from Figure 10.

[0078] As described above, in this embodiment, an NFT badge is awarded when the driver achieves the target conditions. The target conditions include eco-conditions and safety conditions, and are defined to achieve environmental load reduction and safe driving from the perspectives of laws, international standards, and social responsibility. Therefore, when the target conditions are achieved with the acquisition of an NFT badge as motivation, the environmental load is reduced and safe driving is ensured. Thus, according to this embodiment, environmentally and safety-conscious driving can be promoted.

[0079] The embodiments disclosed herein should be considered in all respects to be illustrative and not restrictive. The scope of this disclosure is indicated by the claims rather than by the description of the embodiments above, and all modifications within the meaning and scope equivalent to the claims are intended to be included. [Explanation of symbols]

[0080] 1.1A Marketplace, 2 Designer terminal, 3 Registrant terminal, 4 Vehicle, 5 Driver terminal, 6 Trader terminal, 11 Management server, 111 Processor, 112 Memory, 113 Storage, 114 Network interface, 12 Input device, 13 Output device, 14 Communication device, 71 System program, 72 Control program, 73 Designer management database, 74 Registrant management database, 75 Driver management database, 76 Trader management database, 9.91.92 Nodes, 10.10A Blockchain ecosystem, 20.20A Data management system, NW Network.

Claims

1. A data management system, A server that manages digital assets as non-fungible tokens, The vehicle includes a first computer device used by the vehicle driver to acquire the non-fungible token, The server registers each of a plurality of target conditions, which are conditions relating to at least one of the environment and safety that are desirable to be achieved during operation, by associating them with the non-fungible token. The non-fungible token includes a digital image for visually confirming the non-fungible token. The first computer device notifies the server of the target condition selected by the driver from among the plurality of target conditions, The aforementioned data management system is A second computer device that requests the registration of the aforementioned target conditions, The system further comprises a third computer device that requests the registration of the aforementioned digital image, The aforementioned server, The aforementioned target conditions, registrant information indicating the registrant of the aforementioned target conditions, the aforementioned digital image, and designer information indicating the designer of the aforementioned digital image are associated and registered in the aforementioned non-fungible token. Data for determining whether the driver's driving of the vehicle achieved the selected target conditions is obtained from the vehicle, the first computer equipment, or an external server. A data management system that, when the driver's driving of the vehicle achieves the selected target conditions, assigns the non-fungible token associated with the achieved target conditions, the registrant information, the digital image, and the designer information to the first computer device.

2. The system further comprises a fourth computer device for trading the aforementioned non-fungible tokens, The data management system according to claim 1, wherein the server trades the non-fungible token when an agreement to trade the non-fungible token is reached between the driver and the trader, or between the trader and another trader.

3. With additional servers, The data management system according to claim 1 or 2, wherein the other server includes a distributed ledger on which the non-fungible tokens are stored and functions as a node in a blockchain network.

4. A computer-based data management method, The computer includes the step of storing transaction data, including non-fungible tokens which are digital assets, in a distributed ledger. The non-fungible token includes a digital image for visually confirming the non-fungible token. The aforementioned data management method is: The computer registers, in association with, target conditions relating to at least one of environmental and safety conditions that are desirable to be achieved during operation, registrant information indicating the person who registered the target conditions, the digital image, and designer information indicating the designer of the digital image. The computer acquires data for determining whether the vehicle has achieved the target conditions, A data management method comprising the step of granting the driver of the vehicle the non-fungible token associated with the achieved target condition, the registrant information, the digital image, and the designer information, if the vehicle achieves the target condition.

5. The aforementioned registration step is, If the aforementioned target conditions meet the law and international standards, the computer takes the step of registering the aforementioned target conditions. The data management method according to claim 4, further comprising the step of: if the target conditions do not satisfy the law and the international standards, the computer modifies the target conditions to satisfy the law and the international standards, and registers the modified target conditions.

6. The data management method according to claim 4, wherein the target conditions include at least one of the following: fuel efficiency or electricity consumption is better than a specified value; the amount of electricity consumed by the air conditioner is less than a predetermined amount; greenhouse gas emissions are less than a standard amount; the rest period is longer than the first hour; and the continuous operating time is shorter than the second hour.

7. A server comprising a processor that performs the data management method described in any one of claims 4 to 6.

Images