Method for issuing and using vehicle-related non-fungible tokens and information technology system

Abstract

The present invention relates to a method for issuing and using vehicle-related non-fungible tokens (NFTs), in which an information technology system (1) issues at least one non-fungible token (NFT) assigned to a vehicle (2), the non-fungible token (NFT) comprising at least one proof of ownership, usage rights and / or property of the vehicle (2). The method according to the invention is characterized in that at least one vehicle-internal detection device (ERF-i) detects vehicle-related raw data (RD), vehicle-internal and / or vehicle-external collection devices (SAM-i, SAM-e) store at least a portion of the raw data (RD), vehicle-internal and / or vehicle-external aggregation devices (AGG-i, AGG-e) prepare at least a portion of the stored raw data (RD), a vehicle-internal transformation device (WAN-i) transforms the prepared data (AD) into NFT input data (ED), a vehicle-internal transmission device (UBE-i) transmits the NFT input data (ED) to a vehicle-external issuing device (PRA), and the vehicle-external issuing device issues one of the non-fungible tokens (NFTs) in an unaltered form using the NFT input data.

Description

[Technical field]

[0001] The present invention relates to a method for issuing and using vehicle-related non-fungible tokens and an information technology system for carrying out the method as recited in the preamble of claim 1. [Background technology]

[0002] Certain digital currencies or the respective blockchains underlying digital currencies, such as the Ethereum blockchain, Binance Smart Chain or Solana, allow the creation of so-called non-fungible tokens (NFTs), also referred to as issuance in the following. NFTs are non-fungible digital objects. To issue an NFT, information related to the NFT is integrated in the form of an information block into the blockchain of the respective NFT's underlying digital currency. With NFTs, files that are often easily copied digitally, such as computer-generated artworks, are characterized as unique works, the ownership of which is transferred to a specific stakeholder by selling the NFT.

[0003] To avoid storing excessively large amounts of data on the blockchain, information blocks integrated into the blockchain can also contain links to resources outside the blockchain. The owner and all properties of an NFT are publicly viewable. The properties of an NFT cannot be changed after it is issued.

[0004] As "cryptocurrency" gains acceptance, so too does the popularity of NFTs. For example, US Patent No. 5,999,333 and US Patent No. 5,999,349 to Nike disclose a useful everyday method of using NFTs in connection with purchasable physical goods. The method describes creating an NFT representing a retail item, such as a pair of athletic shoes, when an individual purchases the retail item. The individual includes a unique user ID to which a corresponding NFT is assigned. The purchaser of the retail item thereby obtains a unique digital proof of the purchase of the retail item. In that case, properties of the retail item, such as color, material, manufacturer, model name, size, etc., can be incorporated into the creation of the respective NFT. The purchaser of the retail item can resell the NFT assigned to the retail item to a third party. In that case, the purchaser does not necessarily deliver the physical retail item or its digital image to the third party. The method further describes using a digital image of the physical retail item in a video game, creating a combined digital image of the retail item by blending properties of the two source retail items, and associating the digital image of the athletic shoes and the corresponding NFT with an event. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] U.S. Pat. No. 10,505,726 [Patent Document 2] U.S. Pat. No. 11,113,754 Summary of the Invention [Problem to be solved by the invention]

[0006] The invention is based on the problem of providing a particularly secure and more reliable method and information technology system for issuing and using vehicle-related non-fungible tokens, which can increase the user comfort of vehicle owners. [Means for solving the problem]

[0007] According to the invention, this problem is solved by a method for issuing and using vehicle-related non-fungible tokens having the features of claim 1 and by an information technology system having the features of claim 12. Advantageous embodiments and developments are evident from the dependent claims.

[0008] In a method for issuing and using vehicle-related non-fungible tokens (NFTs), an information technology system issues at least one non-fungible token NFT comprising at least one proof of ownership, usage rights and / or property of the vehicle assigned to a vehicle, and according to the present invention, at least one vehicle-internal detection device detects vehicle-related raw data, a vehicle-internal and / or vehicle-external collection device stores at least a portion of the raw data, a vehicle-internal and / or vehicle-external aggregation device prepares at least a portion of the stored raw data, a vehicle-internal conversion device converts the prepared data into NFT input data, a vehicle-internal transmission device transmits the NFT input data to a vehicle-external issuing device, and the vehicle-external issuing device issues one of the NFTs in an unaltered form using the NFT input data.

[0009] Using the method according to the invention, NFTs can be issued for vehicles, and information related to each vehicle can be stored and assigned to the corresponding vehicle or each vehicle user. This allows the provision of entirely new types of services to the customers of the car manufacturer, improving customer satisfaction and user comfort. Unlike, for example, sneakers, paintings, movies, or songs, the vehicle itself is an information technology system, or part of a larger information technology system, involved in the issuance of NFTs related to itself.

[0010] The issuance of object-related NFTs has seen an increase in fraud attempts. For example, a fraudster may pose as a famous artist and issue and sell NFTs for artworks, without being the maker or owner of the artwork. A similar problem exists when creating NFTs for retail items. A fraudster may perform the steps required to issue an NFT assigned to each retail item on-site at a store, such as scanning an identification tag or taking a photo, without purchasing the retail item. However, such fraud attempts can be reliably prevented by actively incorporating into the generation of the NFT the object for which each NFT is to be created.

[0011] Vehicle-related raw data is detected using vehicle-internal detection devices. The detection devices can be sensors, and the raw data can be measurements of the respective sensors. The detection devices can be systems that have read access to a data bus and / or a physical storage medium and that read the corresponding data transmitted via the bus and / or stored in the storage medium. The vehicle can have one or more detection devices. Each detection device can be located anywhere in the vehicle and can be integrated into one or more mutually independent vehicle subsystems or can be distributed. The raw data generated by the one or more detection devices is then stored by one or more collection devices. The collection device can store the raw data from the one or more detection devices. In that case, in order to reduce storage requirements, it is also possible to discard a portion of the raw data that is no longer needed. Depending on which type of NFT is to be issued, the raw data required for this is transmitted from the collection device to an aggregation device and prepared there. The preparation of the raw data can include, for example, conversion of the raw data into a specific file format, file size compression, classification, filtering, consolidation, or other data processing.

[0012] The retrieval and storage of data may be subject to various data protection law restrictions. By preparing the raw data, the raw data can be manipulated so that the applicable data protection standards are met. Preferably, for this purpose the raw data is stored for the shortest possible period.

[0013] The conversion device then collects the prepared data generated by all the aggregation devices and generates NFT input data therefrom, which is also sent to the vehicle-external issuing device via the transmission device. The transmission of the NFT input data to the vehicle-external issuing device can be wired or preferably wireless. This can be achieved by proven transmission technologies such as mobile radio, Wi-Fi, Bluetooth, NFC, etc. The data collection, caching, and transmission are preferably performed securely by cryptographic authentication and encryption means.

[0014] A vehicle external issuing device is a computer system capable of creating new NFTs, i.e. integrating blocks of data with accumulated information into the blockchain that underlies cryptocurrencies. NFT input data enters the NFT issuance process in an unaltered form. This means that the NFT input data is incorporated one-to-one into the corresponding blocks of information in the blockchain. For example, if a vehicle identification number is part of the NFT input data, the corresponding vehicle identification number is integrated into the corresponding NFT as plaintext. If the dataset is too large, for example in the case of images, a corresponding link to the online data storage where the corresponding image is stored can also be integrated into the NFT.

[0015] In that case, compared to integrating vehicle-related and / or supply chain-related information directly into the blockchain to record the authenticity and / or origin of the product, the use of NFTs allows for particularly flexible subsequent use of the information stored on the blockchain (as an NFT).

[0016] An advantageous development of the method provides for at least one vehicle exterior detection device to be integrated into the process of generating the prepared data. The vehicle exterior detection device as well as the vehicle exterior collection device and / or aggregation device can be components of a central computing device, for example a cloud server or a server collection. Such a cloud server can be operated, for example, by a car manufacturer and can be used for managing vehicle fleet information. This allows for information related to the management of the vehicle fleet to be detected. Furthermore, comprehensive data that is only available to the vehicle manufacturer, for example information generated during the manufacture of the vehicle, can be detected. The individual detection devices, collection devices and / or aggregation devices can therefore be integrated anywhere in the vehicle, in the vehicle subsystem, in the cloud server, in the server collection or components thereof, and also in the mobile terminal device. However, at least one vehicle interior detection device is involved in the creation of the prepared data in order to send at least one piece of information representative of the respective vehicle, such as, for example, the vehicle identification number, the cryptographic private key of the vehicle or other identifiers, to the conversion device. In the simplest case, the vehicle interior detection device can be a device for reading digital information from a data storage. NFT input data is generated by each vehicle's in-vehicle conversion device and transmitted from each vehicle to which each NFT is applied to a vehicle's external issuing device.

[0017] In the case of an external vehicle detection device, raw data detected outside the vehicle can also be transmitted to the respective vehicle for further processing. Similarly, raw data detected inside the vehicle can also be transmitted to a central computing unit where it can be further processed. The prepared data generated outside the vehicle is then sent back to the respective vehicle again for conversion into NFT input data. This ensures that fraudsters cannot create NFTs assigned to the corresponding vehicle.

[0018] According to another advantageous embodiment of the method, at least two separate vehicle subsystems are provided with their own aggregation device, and the raw data detected in each vehicle subsystem is prepared by the respective aggregation device of the vehicle subsystem. This ensures that the raw data cannot leave the respective vehicle subsystem, i.e. locally generated data remains in the respective vehicle subsystem. Local data preparation has two advantages. On the one hand, the prepared data requires less storage capacity than the raw data itself, so that the transmission of excessively large data sets is prevented. Usually, raw data is relatively voluminous and therefore particularly critical from the point of view of data protection. However, there is also no risk of data protection being violated if the raw data does not leave the respective subsystem in which it was created.

[0019] Another advantageous embodiment of the method further provides that the prepared data is temporarily cached in the aggregation device before being sent to the conversion device. Typically, each aggregation device can prepare the raw data immediately before transmitting it to the conversion device. However, this requires a relatively large amount of raw data to be stored in the respective aggregation device. However, the aggregation device can prepare the raw data once or multiple times during detection of the raw data and cache the prepared data before transmitting the prepared data to the conversion device. This allows discarding raw data that is no longer needed and / or prepared data that is no longer needed and correspondingly saving storage capacity.

[0020] According to a further advantageous embodiment of the method, a configuration data set is generated by the configuration device, the configuration data set including the configuration of each of the detection device, the collection device, the aggregation device, the conversion device and / or the transmission device, the configuration being read by each device to control the behavior of each device to issue a specific NFT. Depending on the application or type of NFT to be created, the collection and processing of specific vehicle-related raw data is required. In that case, the configuration data set can be used to parameterize the corresponding device in such a way that the information required for the creation, i.e. issuance, of the desired NFT is obtained. In that case, depending on the application and the NFT to be created, a new configuration of each of the devices is not necessarily required to create a new NFT.

[0021] The configuration device can be formed inside the vehicle or outside the vehicle. The configuration device is operated by a user, such as, for example, a vehicle owner, a vehicle dealer, a vehicle manufacturer, etc. To operate the configuration device, for example, an internal vehicle man-machine interface, such as the vehicle's infotainment system or a web application, can be used. For example, the corresponding web application can be operated via a browser running on a computer or even by an application (app) running on a smartphone. The operation of the configuration device can vary in scope depending on the user's authorization level and / or the user's expertise. In this way, the operation of the configuration device can be made particularly easy for unauthorised laymen and a wealth of configuration options can be offered to authorised experts. For example, a layman can operate the configuration device via an operating screen, while an expert can program the respective device himself, right down to the definition of parameter values ​​and constants.

[0022] Another advantageous embodiment of the method according to the invention comprises: - Defining the input data for the NFT to be created, -Defining the circumstances in which NFTs should be issued; -Definition of the raw data to be detected, - definition of the aggregation function used by the aggregator to prepare the raw data; and / or - Defining the conversion function used by the conversion device to convert the prepared data into NFT input data; A configuration data set is provided that includes at least one of:

[0023] The decision of which NFTs should be created can be made by a top-down or bottom-up approach. The top-down approach contemplates the user to specify which desired NFTs should be created. Based on that, the configuration device independently determines which raw data needed to create the respective NFTs needs to be detected and how the raw data needs to be further processed. In contrast, the bottom-up approach contemplates the user of the configuration device to indicate which raw data needs to be detected during the use of the vehicle and how the raw data needs to be further processed. Then, depending on the settings made, different NFTs can be issued.

[0024] According to another advantageous embodiment of the method, a predefined configuration data set is generated by the configuration device from a list of predefined configuration data sets and loaded by the device. This allows a particularly intuitive and easy operation of the configuration device by a lay user using a corresponding input screen. For example, the lay user selects the desired NFT to be issued, based on which the configuration device loads the corresponding predefined configuration data set, thereby enabling the detection device, the collection device, the aggregation device, the conversion device and the transmission device to issue the desired corresponding NFT.

[0025] In the case of a detection device, the configuration dataset may define, for example, in which system the detection device should be executed (i.e., e.g., a vehicle, a cloud server, a specific control device, etc.), the type and amount of raw data to be detected, under what conditions and / or at what points in time each raw data should be detected, and to which collection device(s) the raw data should be transmitted.

[0026] In the case of a collection device, the configuration data set may define, for example, on which system the collection device should be executed, from which detection devices information should be received, what type and amount of raw data should be received by each detection device, and under what conditions the raw data should be stored or discarded, to which respective aggregator devices the stored raw data should be forwarded, and under what conditions and / or times the forwarding of information should occur to each aggregator device.

[0027] In the case of an aggregator, the configuration data set may for example define on which system the aggregator should be executed, from which collection device the raw data should be received, and in that case also define the type of raw data and the amount of raw data to be processed, the aggregation functions used to prepare the raw data, and the exact behavior of each aggregation function. These may include for example the amount of raw data on which each aggregation function depends, the calculation rules indicating how the prepared data should be generated from the raw data, a set of points in time and / or conditions that define when each aggregation function should be executed and when its use may clear which raw data.

[0028] In the case of a conversion device, the configuration dataset may define, for example, which system the conversion device should run on, from which aggregation device the prepared data should be received, which conversion function should generate NFT input data from the prepared data, and / or the sequence of events and / or conditions when an NFT should be issued.

[0029] In the case of a transmitting device, the configuration data set may define, for example, to which issuing device NFT input data used to issue an NFT is transmitted.

[0030] Another advantageous embodiment of the method further contemplates that the user is queried for approval of the issuance of the NFT before the user manually initiates the issuance of one of the NFTs or automatically issues one of the NFTs. In other words, a manual control action is required on the part of the user before a vehicle-related NFT is issued. This gives the user full control to prevent the issuance of unwanted NFTs for his vehicle. Since the blockchain is typically public and viewable, the user can prevent third parties from reading information linked to the NFT input data from the blockchain if the user does not want to do so. The user may wish to issue a particular NFT, but may want to avoid the publication of certain information in the form of NFT input data in the blockchain. In this way, the user can initiate or enable the issuance of NFTs desired by the user and avoid the issuance of NFTs not desired by the user.

[0031] According to another advantageous embodiment of the method, a private key that allows a third party to transact one of the NFTs is stored in a vehicle internal hardware wallet and / or in a wallet that is accessed by the vehicle. This allows the vehicle as an information technology system to be integrated into the creation or issuance of NFTs, but also allows the use of NFTs from the vehicle. A particularly convenient use of NFTs is possible with a hardware wallet integrated in the vehicle. The private key required to transact is then stored in this hardware wallet. However, the computation unit of the vehicle can also communicate, for example via a telematics unit, with a server of a service provider that manages a user account to which a corresponding NFT has been assigned. The computation unit of the vehicle can also be communicatively connected, for example, to a mobile terminal device that includes a corresponding hardware wallet.

[0032] To conduct a transaction, user authentication may be required, which may be achieved by using conventional authentication methods such as entering a password, reading a biometric identification characteristic, or scanning a code.

[0033] Another advantageous embodiment of the method further contemplates that one of the NFTs includes properties that can be configured for the production of a vehicle, and that a vehicle with a unique combination of properties is prohibited from issuing another NFT corresponding to the unique combination of properties and / or from producing another vehicle corresponding to the unique combination of properties. Vehicle properties may include, for example, the vehicle's engine, the selected chassis, the selected special features, the selected vehicle paint, etc. A purchaser of a vehicle may have configured a unique vehicle. If this is the case, the purchaser may stipulate that no other vehicles with the same properties, i.e., the unique combination of properties, will be produced by the vehicle manufacturer in the future. It is also possible that, although production of such vehicles may continue, no further NFTs may be generated for such vehicles except by the owner of the first vehicle with the unique combination of properties. This allows for a special user experience for the purchaser of the vehicle, since there may not be any other owners of such vehicles or NFTs assigned to such vehicles. Of course, a purchaser of a vehicle with a unique combination of properties may resell the NFTs owned by the purchaser.

[0034] Preferably, the NFT is issued when at least one of the following events occurs: - Manufacturing of vehicles, -Sales of vehicles, - Carrying out repairs or maintenance on vehicles; - parking of vehicles at designated places; - Reaching a given point in time or passing a given period of time; - travelling a specified distance by vehicle; -The presence or absence of certain vehicle features, and / or -The superiority or inferiority of the vehicle's performance compared to the performance of each of the vehicles in the fleet.

[0035] NFTs created during the manufacture of a vehicle may include vehicle data such as, for example, the vehicle identification number, series, model, paint, engine, equipment, production location, date and / or time of completion, and day / month / year vehicle serial number.

[0036] NFTs can also be issued when a vehicle is sold or gifted, i.e. when the vehicle changes hands, allowing the NFT to be used to track the exact owner of the vehicle.

[0037] NFTs may also be issued when parts and / or components of a vehicle are repaired, maintained, or otherwise replaced or manipulated. This may include, for example, performing software updates or decommissioning / scrap of the vehicle. This may ensure that only authorized repair or maintenance work is performed on the vehicle. For example, creation of the corresponding NFT may only be possible through authorized workshops. Of course, physical changes may be performed on the vehicle without issuance of a new NFT. However, if the NFT corresponding to such changes is missing, the corresponding vehicle owner or potential purchaser will know that the vehicle has been tampered with.

[0038] It is also possible to issue an NFT if the vehicle stops at a specific location. To detect where the vehicle stops, various methods can be used, such as GPS location monitoring. For this purpose, the vehicle can have a corresponding navigation system or communicate with a mobile terminal device, such as a smartphone or a mobile navigation device. In video games, so-called "challenges" are known. For achieving certain achievements in a video game, a trophy is awarded to the player. This can also be applied to vehicles. For example, an NFT can be issued if a certain country or city is visited with the vehicle. This can motivate the vehicle user to travel more with his vehicle, improving the user experience with the vehicle. Other locations that can involve the issuance of an NFT are, for example, visiting certain tourist attractions, UNESCO World Heritage sites, participating in certain sporting events, ground hopping, etc.

[0039] Additionally, an NFT may be issued when a particular time point is reached or a defined period of time has passed. For example, an NFT may be issued when a particular time on a particular date is reached, on the anniversary of the vehicle owner's birthday, the vehicle's registration or sale date, when a financing period expires, etc.

[0040] An NFT may be issued when a certain distance is traveled with the vehicle, for example, every 10,000 kilometers, every 50,000 kilometers, or every 100,000 kilometers, and / or when a certain number or combination of events is achieved, for example, visiting 10 UNESCO landmarks or visiting 100 stadiums. In this case, the NFT may also include information indicating its rarity, such as bronze status, silver status, gold status, etc. For example, a silver status NFT may be issued every 50,000 kilometers and a gold status NFT may be issued every 100,000 kilometers. In this case, a distinction may also be made between different drivers of the vehicle.

[0041] This can also be used to issue driver-related NFTs, taking into account other vehicle-related information, e.g., if driver X has not driven faster than the maximum permitted speed, say by 10km / h, in the last 10 years.

[0042] In general, an NFT can be issued when a particular vehicle feature is realized or used, or is inoperative or unused. For example, an NFT can be issued when the radio is listened to for 1000 hours in the vehicle, when the seat back of the vehicle is never used, when the window wiper of the vehicle is wiped 1 million times, when the fog lights of the vehicle are never used, etc. By issuing such an NFT, the condition of the vehicle can also be evaluated, which can be relevant in negotiating the price when reselling the vehicle. For example, for a vehicle with an automatic transmission, the number of kickdowns that have been performed can be counted, and an NFT can be issued for every 1,000 kickdowns, for example. The more such NFTs issued for a vehicle, the more wear the vehicle has.

[0043] The NFTs issued for a particular vehicle can be compared with the NFTs issued for other vehicles. This allows to hold competitions, so-called challenges. For example, NFTs can be issued for vehicles in a fleet that travel the longest distance in a particular year, are driven most efficiently, travel the most passenger kilometers, drive the fastest, spend the longest in traffic jams, have the longest useful life, have the most gold status NFTs, etc. It is also possible to count the number of users who use a particular vehicle function, for example the 1000th user of live traffic.

[0044] Hosting such challenges increases customer interest in the vehicles and creates a particularly exciting user experience.

[0045] According to the present invention, an information technology system is provided with a vehicle, a central computing unit and an issuing device, the vehicle, the central computing unit and the issuing device being configured to execute the aforementioned method. The vehicle may comprise one or more computing units actively involved in issuing NFTs. This includes the above-mentioned detection device, collection device, aggregation device, conversion device and transmission device, the vehicle comprising at least an internal detection device, a conversion device and a transmission device. One or more detection devices, collection devices and / or aggregation devices may also be provided on the central computing device outside the vehicle. In that case, configuration devices for configuring the respective devices may be formed inside the vehicle or outside the vehicle. The issuing device may be part of the central computing unit or may be operated by a third party. For example, the issuing device is a component of a distributed infrastructure used to manage a blockchain operated with distributed ledger technology. The individual components of the information technology system may exchange data with each other via various proven communication paths.

[0046] An advantageous development of the information technology system comprises a mobile terminal device coupled directly to the vehicle or indirectly via a central computing unit, in which the detection devices, collection devices and / or aggregation devices external to the vehicle are executed. The mobile terminal device is, for example, a smartphone, a tablet computer, a laptop, a wearable device such as a smart watch, etc. The coupling between the vehicle and the mobile terminal device can be wired, for example using a USB cable, and / or wireless, for example using WLAN, Bluetooth, NFC, etc. Software or applications can be executed in the mobile terminal device, which provide the corresponding functions of the detection devices, collection devices and / or aggregation devices by means of the mobile terminal device. The information technology system can thus be expanded particularly simply and flexibly.

[0047] Further advantageous embodiments of the inventive method for issuing and using vehicle-related non-fungible tokens and the information technology system used for this will become apparent from the exemplary embodiments described in detail below with reference to the figures. [Brief description of the drawings]

[0048] [Figure 1] FIG. 1 shows a schematic diagram of an information technology system according to the present invention used for the issuance of non-fungible tokens. [Diagram 2] 1 is a schematic flow chart of the steps of a method according to the present invention for issuing non-fungible tokens. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0049] FIG. 1 shows a schematic diagram of an information technology system 1 according to the invention, comprising a vehicle 2, a central computing unit 4, a component device KONF, an issuing device PRA, and a wallet 3 for storing a non-fungible token NFT. However, in this case, the non-fungible token NFT is not stored directly in the wallet 3, but is instead stored as an information block in a decentralized blockchain. In that case, the information block contains an identifier of a user account assigned to a user. This identifier is typically formed by a public key. To transfer a non-fungible token NFT, the identifier of the new user is written into the information block of the non-fungible token NFT. The authorization authentication of this process requires the private key of the original owner. This private key is stored in the wallet 3.

[0050] Information technology system 1 can be used to issue and use vehicle-related non-fungible token NFTs. Such non-fungible token NFTs can, for example, prove ownership, use rights, and / or property of vehicle 2. Vehicle 2, together with its internal systems and computational units not shown in detail, is part of information technology system 1 and is responsible for the issuance of non-fungible token NFTs. Vehicle-related data used for the issuance of non-fungible token NFTs is obtained from vehicle 2.

[0051] In order to detect relevant data, for example sensor values ​​or data read out via a bus system of the vehicle 2, one or more computing units of the vehicle 2 comprise detection devices ERF-i. The detection devices ERF-i read out corresponding sensor data and / or vehicle buses and generate therefrom raw data RD. The raw data RD are transferred to the collection device SAM-i for storage. In that case, the collection device SAM-i can also receive raw data RD from multiple detection devices ERF-i.

[0052] The stored raw data RD are then transferred to the aggregator AGG-i for preparation. Again, the aggregator AGG-i may receive the raw data RD from one or several collectors SAM-i. In the exemplary embodiment of Fig. 1, only one aggregator AGG-i is shown for the vehicle 2. However, the vehicle 2 may also include several aggregators AGG-i.

[0053] After successful transmission of the raw data RD to the aggregator AGG-i, the corresponding raw data RD may be erased from the collector SAM-i. To prepare the raw data RD to generate the prepared data AD, the raw data RD may be, for example, filtered, put into a unified file format, sorted, irrelevant data discarded, consolidated or otherwise further digitally processed.

[0054] The prepared data AD is transmitted to the conversion device WAN-i and converted by the conversion device into NFT input data ED. The NFT input data ED has a corresponding file format required for issuing a non-fungible token NFT and contains information to be integrated into the non-fungible token NFT. The issuing device PRA can then read the NFT input data ED and issue it in an unaltered form into a non-fungible token NFT. For this purpose, the issuing device PRA integrates a corresponding information block into a blockchain managed by a distributed infrastructure. To transmit the NFT input data ED from the vehicle 2 to the issuing device PRA, the vehicle 2 transmits the NFT input data ED by the transmission device UBE-i. For example, the NFT input data ED can be transmitted via mobile radio to a cloud server, which then forwards the NFT input data ED via the Internet to the distributed infrastructure used to manage the blockchain. In that case, the cloud server itself can also form a node of the distributed infrastructure. The central computing unit 4 can also form the cloud server or function as a node of the distributed infrastructure.

[0055] After processing the corresponding NFT input data ED and issuing the non-fungible token NFT by the decentralized infrastructure, the corresponding non-fungible token NFT is assigned to a user account that can be accessed by a private key stored in wallet 3.

[0056] Depending on the information contained in the non-fungible token NFT, the data can also be retrieved from the central computing unit 4, for example a cloud server or a back-end of the car manufacturer. This allows information linked to the management of the vehicle fleet to be integrated into the non-fungible token NFT. For this purpose, the central computing unit 4 comprises at least one detection device ERF-e, a collection device SAM-e and an aggregation device AGG-e as well as the vehicle 2. As a result, the prepared data AD generated by the aggregation device AGG-e integrated in the central computing unit 4 is transmitted to the vehicle 2 and supplied to the conversion device WAN-i. By integrating the vehicle 2 into the issuance process of the non-fungible token NFT with the data obtained from the central computing unit 4, the prevention of fraudulent issuance of the non-fungible token NFT valid for the vehicle 2 is ensured with a particularly high degree of reliability.

[0057] Depending on the desired non-fungible token NFT to be created, different devices need to detect very different data in different time periods. For this, the individual devices such as the detection devices ERF-i, ERF-e, the collection devices SAM-i, SAM-e, the aggregation devices AGG-i, AGG-e, the conversion devices WAN-i and the transmission devices UBE-i need to be parameterized, i.e. configured. Such configuration is performed using a configuration data set K generated by a configuration device KONF. The configuration device KONF can be executed inside the vehicle, in the central computing unit 4, as shown, or externally to both devices. The depth to which the individual devices of the information technology system 1 are configured by the configuration device KONF then depends on the type of non-fungible token NFT to be created and the authorization level of the user operating the configuration device KONF. Thus, a layman can select a pre-created configuration profile, for example, from a list of pre-created configuration data sets. However, an expert can, if he wishes or needs it, perform detailed settings on the individual devices down to the programming level.

[0058] 2 shows a schematic flow chart of the steps of the method according to the invention for issuing non-fungible tokens NFTs. In method step 201, indicated by an arrow, the administrator of the central computing unit 4 defines which types of non-fungible tokens NFTs can be issued. From this, a definition data set DEF is created with the NFT definition, including the configuration and settings of the individual devices.

[0059] In method step 202, a list of issueable non-fungible tokens NFTs is created from the definition data set DEF. These are provided for issuance to the NFT service Service.

[0060] In method step 203, the user authorizes their vehicle 2 to participate in the NFT service and selects the desired non-fungible token NFT to be issued.

[0061] In method step 204, data is sent to all vehicles 2 for which a non-fungible token NFT is desired, informing the respective vehicle 2 which raw data RD needs to be collected to generate the corresponding non-fungible token NFT and how it should be further processed. The corresponding information is obtained by a first distributed system 5 including the vehicles 2 and a central computing unit 4. A mobile terminal device, for example a smartphone, can also be part of the first distributed system 5. The detection of the raw data RD is represented by box 6 and the processing of the raw data RD into NFT input data ED is represented by box 7.

[0062] In method step 205, the NFT input data ED is transmitted to the issuing device PRA by the transmission device UBE-i inside the vehicle. In the exemplary embodiment of FIG. 2, the data transmission is performed indirectly via a preparation device AGG-PRA integrated in the central computing unit 4. The preparation device AGG-PRA can compile multiple data sets of NFT input data ED and then hand them over to the issuing device PRA in method step 206. The issuing device PRA can then also be part of a second distributed system 9 that manages the blockchain underlying the corresponding non-fungible token NFT. In method step 207, the issuing device PRA is configured according to a definition data set DEF.

[0063] In method step 208, vehicle 2 inquires whether it can receive a non-fungible token NFT or automatically issues a notification that it can issue a non-fungible token NFT.

[0064] In method step 209, the issuing device PRA finally issues the non-fungible token NFT created according to the NFT input data ED by including the corresponding information block in the respective underlying blockchain. For this purpose, an intelligent contract SC, also called a smart contract, is signed. In method step 210, the issuing device PRA initiates the transfer of the issued non-fungible token NFT to the user's wallet 3.

Claims

1. A method for issuing and using vehicle-related non-fungible tokens (NFTs), comprising: an information technology system (1) issuing at least one non-fungible token (NFT) assigned to a vehicle (2) comprising at least one proof of ownership, use rights and / or property of said vehicle (2), the method comprising:

1. A method comprising: at least one vehicle-internal detection device (ERF-i) detecting vehicle-related raw data (RD); vehicle-internal and / or vehicle-external collection devices (SAM-i, SAM-e) storing at least a portion of said raw data (RD); vehicle-internal and / or vehicle-external aggregation devices (AGG-i, AGG-e) preparing at least a portion of the stored raw data (RD); a vehicle-internal conversion device (WAN-i) converting prepared data (AD) into NFT input data (ED); a vehicle-internal transmission device (UBE-i) transmitting said NFT input data (ED) to a vehicle-external issuing device (PRA); and said vehicle-external issuing device issuing one of said non-fungible tokens (NFT) in an unaltered form using said NFT input data.

2. 2. The method according to claim 1, characterized in that at least one vehicle external detection device (ERF-e) is integrated into the process of generating prepared data (AD).

3. 3. A method according to claim 1 or 2, characterized in that at least two separate vehicle subsystems each have their own aggregator (AGG-i), and the raw data (RD) detected in each vehicle subsystem is prepared by the respective aggregator (AGG-i) of said vehicle subsystem.

4. The method according to any one of claims 1 to 3, characterized in that the prepared data (AD) is temporarily cached in the aggregation device (AGG-i, AGG-e) before being sent to the translation device (WAN-i).

5. 5. Method according to any one of claims 1 to 4, characterized in that a configuration data set (K) is generated by a configuration device (KONF), said configuration data set comprising the configuration of each of the detection devices (ERF-i, ERF-e), collection devices (SAM-i, SAM-e), aggregation devices (AGG-i, AGG-e), transformation devices (WAN-i) and / or transmission devices (UBE-i), said configurations being read by each of the devices (ERF-i, ERF-e, SAM-i, SAM-e, AGG-i, AGG-e, WAN-i, UBE-i) in order to control the behavior of said each of the devices (ERF-i, ERF-e, SAM-i, SAM-e, AGG-i, AGG-e, WAN-i, UBE-i) to issue specific non-fungible tokens (NFTs).

6. The configuration data set (K) includes the following information: - definition of the NFT input data (ED) to be created, - Defining the circumstances in which Non-Fungible Tokens (NFTs) should be issued; - definition of the raw data (RD) to be detected, definition of the aggregation functions used by the aggregator devices (AGG-i, AGG-e) to prepare said raw data (RD), and / or - definition of the transformation function used by said transformation device (WAN-i) to transform said prepared data (AD) into NFT input data (ED); The method of claim 5, comprising at least one of:

7. 7. A method according to claim 5 or 6, characterized in that a predetermined configuration data set (K) from a list of predetermined configuration data sets (K) is generated by a configuration device (KONF) and read by said device (ERF-i, ERF-e, SAM-i, SAM-e, AGG-i, AGG-e, WAN-i, UBE-i).

8. 8. The method of claim 1, wherein a user manually initiates the issuance of one of the non-fungible tokens (NFT) or a user is queried for approval of the issuance of one of the non-fungible tokens (NFT) before automatically issuing one of the non-fungible tokens (NFT).

9. The method according to any one of claims 1 to 8, characterized in that a private key that allows a third party to transact one of the non-fungible tokens (NFTs) is stored in a vehicle internal hardware wallet and / or in a wallet (3) that is accessed by the vehicle (2).

10. 10. The method according to claim 1, wherein one of the non-fungible tokens (NFT) comprises properties that can be configured for the production of a vehicle (2), and a vehicle (2) having a unique combination of properties is prohibited from issuing another non-fungible token (NFT) corresponding to the unique combination of properties and / or from producing another vehicle (2) corresponding to the unique combination of properties.

11. The following situations: - the manufacture of said vehicle (2), - sale of said vehicle (2), - carrying out repairs or maintenance on said vehicle (2), - the stopping of said vehicle (2) at a defined location, - the arrival of a given time or the passage of a given period of time; - a determined distance travelled by said vehicle (2), - the presence or absence of certain vehicle features; and / or - the superiority or inferiority of the vehicle performance in comparison with the vehicle performance of each of the vehicles (2) of the fleet; The method according to any one of claims 1 to 10, characterized in that a non-fungible token (NFT) is issued if at least one of the following is realized:

12. An information technology system (1) comprising a vehicle (2), a central computing unit (4) and an issuing device (PRA), An information technology system, characterized in that said vehicle (2), said central computing unit (4) and said issuing device (PRA) are configured to carry out the method according to any one of the claims 1 to 11.

13. The information technology system (1) according to claim 12, characterized in that it is a mobile terminal device coupled directly to the vehicle (2) or indirectly via the central computing unit (4), in which a vehicle external detection device (ERF-e), a collection device (SAM-e) and / or an aggregation device (AGG-e) are executed.

Images