DE102023005095A1 - Method for activating a vehicle function and information technology system - Google Patents

Abstract

The invention relates to a method for enabling a vehicle function, wherein the vehicle function can be provided via the hardware of a vehicle (1), the hardware is configured by software, and wherein the vehicle function is provided by the hardware when the hardware is configured according to an enabling configuration. The device according to the invention is characterized in that
- a user (2) of the vehicle (1) logs into a central computing device (3) with a user account;
- the user (2) links his wallet (4) to the user account;
- the central computing device (3) initiates the minting of an NFT (NFT), wherein the release configuration is assigned to the NFT (NFT) as a digital asset (13);
- the central computing device (3) causes the NFT (NFT) to be assigned to the wallet (4) of the user (2);
- the central computing device (3) reads the NFTs (NFT) stored in the wallet (4);
- the central computing device (3) obtains respective release configurations for NFTs (NFT) stored in the wallet (4) and transmits them to the vehicle (1);
- the hardware of the vehicle (1) or the vehicle (1) itself is modified;
- the release configuration is adapted to the changed hardware; and
- the adapted release configuration is used in the vehicle (1).

Description

The invention relates to a method for activating a vehicle function according to the type defined in more detail in the preamble of claim 1 and to an information technology system comprising a central computing device and a vehicle.

The degree of digitalization in vehicles is constantly increasing. For example, the mechanical steering system or the control of the braking system and fuel pump based on pedal position are being replaced by electronic control systems. This is also known as drive-by-wire. In addition, new assistance functions are being provided to increase safety and comfort, such as lane keeping assist, adaptive cruise control, traffic sign recognition, or the ability to watch films on an in-vehicle display, make video calls, stream audiobooks, and the like.

Various vehicle functions require the installation of specific hardware components in the vehicle. During the ordering process, a vehicle can be configured so that certain hardware components are installed that generally allow the provision of several functions, although only some of these functions are actually purchased by a customer. The remaining functions, i.e. those not purchased, are then blocked for use in the vehicle manufactured for the customer by a software configuration. However, since the necessary hardware is already installed, this makes it possible to subsequently unlock the functions via software. For example, by reconfiguring the vehicle's software, increased engine power could be temporarily or permanently enabled, a seat heating function could be subscribed to, for example, for the winter months, or similar.

To manage vehicle functions used in the vehicle, the user interacts with the vehicle manufacturer, for example, via a central portal, such as a server operated by the vehicle manufacturer that forms an interface between a user account and their vehicle. This allows the user to connect their vehicle to their user account and book vehicle functions individually. However, control over the booked functions remains with the vehicle manufacturer, which can negatively impact a user's decision-making process regarding the additional booking of separate functions. It would be desirable, therefore, to transfer control over bookable vehicle functions to the customer.

Certain digital currencies, also known as cryptocurrencies, or the respective underlying blockchains, such as the Ethereum blockchain, the Binance Smart Chain, or Solana, allow the creation of so-called non-fungible tokens (NFTs). The creation of NFTs is also referred to as minting. In particular, the minting and/or initiation of transactions of a respective NFT is controlled by a so-called smart contract. A smart contract is program code written into the blockchain that is automatically executable on the blockchain by the crypto network managing the blockchain based on the information written into the blockchain. While the units of a respective cryptocurrency are divisible, i.e., "fungible," each NFT is unique, i.e., "non-fungible." An NFT represents a specific asset, particularly a digital asset such as an image file, video file, sound file, text file, or the like. Physical assets such as houses, vehicles, sneakers, or the like can also be assigned to an NFT as "proof of ownership." The information describing or referencing the asset associated with an NFT is typically written into the NFT's metadata. The metadata can be stored in the blocks of the blockchain itself, or preferably in a storage location external to the blockchain. A blockchain can be managed centrally or decentrally. A so-called non-fungible token standard, such as ERC721 or ERC1155, defines how the respective metadata is to be designed and processed.

Furthermore, so-called hybrid smart contracts are known, which link program code running on the blockchain with information and calculations available external to the blockchain. So-called blockchain oracles are used as an interface. One such service for linking a blockchain with external systems, which enables the execution of smart contracts based on real-world inputs and outputs, is provided by the company Chainlink, for example.

From the DE 10 2022 000 646 A1 A method for minting and using vehicle-related non-fungible tokens is known. The publication describes the provision of NFT-based vehicle functions. For this purpose, vehicle data is collected during vehicle operation and used to mint NFTs. Thus, the vehicle itself participates in the NFT minting process. For example, NFTs can be minted when the vehicle is manufactured, repaired, or undergoes maintenance. is used, the vehicle is sold, or the like. This makes it possible to track the condition or level of wear and tear of the vehicle using NFTs. Vehicle-related NFTs can also be minted when certain milestones are reached with the vehicle, such as reaching a set operating time, distance traveled, staying in a certain location, or the like. This allows so-called "achievements" to be achieved with the vehicle, making the use of the vehicle even more attractive for a user by providing gamification-based functions. Using the NFTs minted when such an achievement is achieved, the user can track their personal achievements and present them to others as proof.

Furthermore, the US 2022/0383295 A1 a so-called collection container for NFT goods. This publication addresses the problem that an NFT is usually linked to digital goods, also known as "digital assets," with which one cannot interact in the real world. The collection container represents an electronic device in the form of a computing device that is capable of downloading digital goods linked to an NFT via the internet and issuing them via output means included in the collection container. For example, digital works of art can be displayed on a display device or audio content can be played via integrated speakers. The collection container has its own wallet so that respective NFTs or digital goods can be clearly assigned to a specific collection container. Owners of such collection containers can trade the NFTs they own, including the corresponding digital goods, for example by exchanging the collection containers themselves or by conducting corresponding transactions of the NFTs on the respective underlying blockchain.

Furthermore, the US 2023/0071093 A1 A system and method for the uniform listing and transfer of NFT assets across multiple platforms, based on the use of smart contracts. The document describes a mediator for using various NFT marketplaces. The smart contract for minting an NFT includes conditions that can be processed by several different NFT marketplaces. Furthermore, the document describes a translation module capable of defining conditions for smart contracts in natural language and translating them into machine-readable code. This increases the user-friendliness of formulating smart contracts for users with little or no programming knowledge.

It may happen that the vehicle's hardware is changed after a longer period of time, for example, by replacing certain components, or the user purchases a new vehicle and returns the old one. In this context, the question arises as to how the acquired vehicle function can be implemented via the new hardware. Components originally intended for implementing the vehicle function, such as certain lighting devices, certain seat-integrated massage actuators, or the like, may no longer be present and/or new components may have been installed.

The object of the present invention is to provide an improved method for activating a vehicle function, which allows a user to permanently use a vehicle function once acquired.

According to the invention, this object is achieved by a method for activating a vehicle function having the features of claim 1. Advantageous embodiments and further developments as well as an information technology system for implementing the method emerge from the dependent claims.

• - sich ein Nutzer des Fahrzeugs an einer zentralen Recheneinrichtung mit einem Nutzeraccount anmeldet;
• - der Nutzer sein Wallet mit dem Nutzeraccount verknüpft;
• - die zentrale Recheneinrichtung das Prägen eines NFTs veranlasst, wobei dem NFT die Freigabekonfiguration als digitales Gut zugeordnet wird;
• - die zentrale Recheneinrichtung bewirkt, dass das NFT dem Wallet des Nutzers zugeordnet wird;
• - die zentrale Recheneinrichtung die im Wallet gespeicherten NFTs ausliest;
• - die zentrale Recheneinrichtung für im Wallet gespeicherte NFTs jeweilige Freigabekonfigurationen bezieht und an das Fahrzeug überträgt;
• - die Hardware des Fahrzeugs oder das Fahrzeug an sich geändert wird;
• - die Freigabekonfiguration an die geänderte Hardware angepasst wird; und
• - die angepasste Freigabekonfiguration im Fahrzeug genutzt wird.

A generic method for enabling a vehicle function, wherein the vehicle function can be provided via the hardware of a vehicle, the hardware is configured by software, and wherein the vehicle function is provided by the hardware when the hardware is configured according to the release configuration, is further developed according to the invention in that

• - a user of the vehicle logs into a central computer system with a user account;
• - the user links his wallet to the user account;
• - the central computing device initiates the minting of an NFT, whereby the release configuration is assigned to the NFT as a digital asset;
• - the central computing device causes the NFT to be assigned to the user's wallet;
• - the central computing device reads the NFTs stored in the wallet;
• - the central computing device obtains the respective release configurations for NFTs stored in the wallet and transmits them to the vehicle;
• - the vehicle's hardware or the vehicle itself is modified;
• - the release configuration is adapted to the changed hardware; and
• - the adapted release configuration is used in the vehicle.

By adjusting the release configuration, new program code sections can be incorporated, which in turn allow the new hardware to be controlled. If the user changes their vehicle, or existing hardware components are replaced and/or new hardware components are installed in the user's old vehicle, these can be used accordingly to provide the vehicle function. This reliably ensures that the user can permanently use a vehicle function once acquired.

Vehicle functions can include any conceivable function that can be executed through software adaptations on the hardware already installed in the vehicle. These can include, for example, special graphical elements of a graphical user interface, such as a special speedometer design for an instrument cluster configured as a display device, a special artificial engine noise for an electric motor that is output via external vehicle speakers, increased engine power, a comfort function such as seat heating, a massage function, a lighting function, such as a special light pattern for ambient lighting, or the like.

The central computing device is a cloud server or server network, in particular managed by the vehicle manufacturer. The user has an individual user account, clearly referenced via an individual user name and secured by a personal password. The user's vehicle is linked to their user account, allowing the central computing device to clearly associate users with the respective vehicles. For this purpose, the vehicle is linked to the user account via a unique identifier such as a serial number, vehicle identification number, or the like. The user also has a wallet for cryptocurrencies or NFTs. The user then links this wallet to their user account, allowing the central computing device to verify the wallet's contents. In the simplest case, this simply means that the user deposits a public address of their wallet, for example, the so-called "public key," with the central computing device. The infrastructure operated by the vehicle manufacturer, i.e., a platform provided on the central computing device, can also have integrated wallet functionality. This allows not only the vehicle manufacturer to have its own manufacturer wallet, but also the vehicle manufacturer to assign a separate wallet to each user account. This reduces the barrier for non-technical users to using the method according to the invention, as users do not have to create a wallet themselves.

To unlock specific vehicle configurations, the vehicle manufacturer develops corresponding release configurations. A release configuration is the corresponding program code, which, once implemented on a computing unit in the vehicle, adapts the respective computing unit or hardware so that the vehicle function provided by the respective hardware can also be used. In the simplest case, a flag is changed, for example, from 0 to 1 or negative to positive. The vehicle manufacturer can provide appropriately designed release configurations for a wide variety of hardware combinations. For each release configuration, the central computing unit triggers a corresponding minting of the respective NFTs. For example, the time for minting an NFT can be selected so that the NFT is minted exactly when the user acquires the respective release configuration from the vehicle manufacturer through the occurrence of the event. There are various ways in which the central computing unit can assign the respective NFTs to the user's wallet. The central computing unit or the vehicle manufacturer can either have its own manufacturer wallet, to which the NFTs are assigned during minting. The NFTs are then transferred from the manufacturer's wallet to the user's wallet. However, it is also possible that the user's wallet address or public key is directly entered during the minting process, so that the freshly minted NFTs initially appear in the user's wallet.

After purchasing the vehicle function, the user can activate the vehicle function in their vehicle. This can occur automatically upon purchasing the vehicle function or can be initiated manually by the user. To do so, the user can use various human-machine interfaces, such as a user interface in the vehicle itself, for example, implemented as a touch-sensitive display device, a mobile device such as a smartphone linked to the vehicle, in particular via the user account, or using a browser-based access interface, for example, using a desktop computer connected to the Internet. Users log in to the central computing device using their user account, select their vehicle in a corresponding input mask, and activate a specific vehicle function, for example, by checking a box. The computing unit used for this purpose—for example, an internal vehicle computing unit, the user's smartphone, or even the desktop computer—sends information to the central computing device via a corresponding application programming interface (API), indicating that the respective vehicle function should be activated.

At various times, for example, when the user opens their user account via a corresponding portal or every time the vehicle is started, the central computing device can read the user's wallet and thus record the NFTs stored there. Accordingly, the central computing device adapts an output mask to display currently available vehicle functions. This allows the user to switch purchased vehicle functions on and off as needed. After the user has activated a respective vehicle function, the central computing device sends a corresponding signal to the vehicle to activate the vehicle function. For this purpose, the central computing device can, for example, transmit the program code of the release configuration itself to the respective computing unit of the vehicle, with the command that the respective program code be executed.

To implement the method according to the invention, all current or future blockchain technologies and the cryptocurrencies that can be provided thereby can be used. The blockchain can be managed centrally or decentrally.

In the simplest case, the NFT simply contains a unique identifier, such as a unique token ID. The central computing device can maintain a file in which a connection between the NFTs and respective vehicle functions is stored. The central computing device can then read the user's wallet, obtain the unique token ID, and consult the file to determine which vehicle function is usable by the user. The central computing device then activates the corresponding vehicle function in the user's vehicle. In this case, it is not even necessary to assign a reference to the digital asset to the NFT, since the central computing device already has this information.

• - das NFT das digitale Gut umfasst; oder
• - das digitale Gut in einem zentralen oder dezentralen Netzwerkspeicher vorgehalten wird, wobei das NFT einen Verweis auf das digitale Gut umfasst.

The method according to the invention can provide that

• - the NFT includes the digital asset; or
• - the digital asset is stored in a centralized or decentralized network storage, whereby the NFT includes a reference to the digital asset.

This makes it possible to link specific vehicle functions to NFTs in different ways. The corresponding program code can either be written directly into a block of the blockchain used that represents the NFT. However, it is also possible to store the corresponding program code and any required media files on the centralized or decentralized network storage and simply integrate a reference to the corresponding storage location into the blockchain. Such a reference is also called a URI. For example, it can be a URL. The digital asset can thus be stored both on-chain and off-chain.

The central network storage may in particular be the server used as the central computing facility or a server in the server network.

Distributed or decentralized network storage could, for example, be the so-called "InterPlanetary File System" (IPFS). This is a protocol and a network for creating peer-to-peer storage for files, such as so-called hypermedia. The advantage of using decentralized network storage over centralized network storage is that it is characterized by a lower probability of failure. There is a high risk that a central node will fail, at least temporarily, for example due to a cyberattack, maintenance work, environmental influences such as a power outage, flooding, or the like. During this period, no digital goods can be retrieved from the central network storage. With decentralized network storage, however, the respective information is stored on multiple nodes, so that if one or a few nodes fail, the information can be retrieved from another node.

The fact that the release configuration is "assigned" to an NFT should be understood in an abstract way. Thus, a wide variety of assignment modalities are possible. As already mentioned, the corresponding program code can be written directly into the blockchain or on the corresponding The NFTs are stored in the user's wallet and referenced by the link. It is also possible for the vehicle manufacturer to identify different vehicle functions or release configurations with an individual and unique identifier. This could be an ID, for example. This identifier can then be written, for example, as plain text into the blockchain itself or into the metadata in the network storage. The actual program code can then be stored in a protected memory of the central computing device, inaccessible to the public. If the central computing device then reads the NFT in the user's wallet, the central computing device also reads the unique identifier of the release configuration and can read the digital data required to activate the vehicle function in the vehicle, in particular the aforementioned program code, from the protected memory.

The method according to the invention can further provide that the release configuration is assigned to the NFT in cryptographically encrypted form, the central computing device decrypts the release configuration after reading the user's wallet and obtaining the release configuration, and transmits the decrypted release configuration to the vehicle. This further improves the integrity of the program code underlying the release configuration and any media files, as well as cybersecurity when implementing the method according to the invention. Proven cryptographic encryption techniques can be used here, such as signature-based encryption using asymmetric key pairs. In particular, the program code of the release configuration can be written cryptographically encrypted directly into the blockchain, written into the metadata of the NFT, or stored on a corresponding central or decentralized network storage referenced by the metadata. This also counteracts the "theft" of the program code by third parties. To decrypt the encrypted release configuration, the central processing unit requires a corresponding private key, which it already possesses as the encrypting element of the release configuration's program code. Communication between the central processing unit and the vehicle can also be encrypted, so that, in a broader sense, the decrypted release configuration is re-encrypted and then decrypted in the vehicle. This also prevents data interception during data exchange between the central processing unit and the vehicle.

In general, there are two different concrete implementation variants of how the release configuration assigned to an NFT can be changed.

• - die zentrale Recheneinrichtung an unterschiedliche Hardware angepasste Freigabekonfigurationen auf einem zentralen oder dezentralen Netzwerkspeicher speichert;
• - das NFT als dynamisches NFT geprägt wird;
• - die zentrale Recheneinrichtung eine Fahrzeugarchitekturinformation einem Blockchain-Orakel vermittelt, wobei die Fahrzeugarchitekturinformation die Hardware des Fahrzeugs des Nutzers beschreibt;
• - das Blockchain-Orakel die Metadaten des dynamischen NFTs anpasst, sodass dem dynamischen NFT die an die Fahrzeugarchitekturinformation angepasste Freigabekonfiguration als digitales Gut zugeordnet wird; und
• - das Fahrzeug die angepasste Freigabekonfiguration vom Netzwerkspeicher bezieht.

Thus, a first alternative embodiment of the method according to the invention provides that

• - the central computing device stores release configurations adapted to different hardware on a central or decentralised network storage;
• - the NFT is minted as a dynamic NFT;
• - the central computing device transmits vehicle architecture information to a blockchain oracle, wherein the vehicle architecture information describes the hardware of the user's vehicle;
• - the blockchain oracle adapts the metadata of the dynamic NFT so that the release configuration adapted to the vehicle architecture information is assigned to the dynamic NFT as a digital asset; and
• - the vehicle retrieves the customized release configuration from the network storage.

With the help of blockchain oracles and dynamic NFTs, the content of an NFT's metadata can also be changed retroactively. To do this, a smart contract is used when minting the NFT, which triggers the change to the metadata depending on external conditions. Such a smart contract is also referred to as a hybrid smart contract. Since smart contracts can typically only read content stored on-chain, i.e., read information from the blockchain, a blockchain oracle is required, which forms a link between smart contracts and the outside world. This means that content stored off-chain can also be used as an execution condition for logic defined in a smart contract.

To do this, the vehicle manufacturer first develops the customized hardware or a new vehicle and adapts the respective vehicle functions to the new hardware. The underlying release configurations are then adapted to the new hardware, and corresponding updated program versions are stored in the central or decentralized network storage. The central network storage can, for example, be the central computing device itself. Decentralized network storage is, in particular, storage managed by a peer-to-peer network, such as the so-called InterPlanetary File System (IPFS).

The smart contract used to mint the dynamic NFT can then contain information that the NFT's metadata should be changed as soon as the vehicle manufacturer provides a new release configuration at an address stored in the smart contract. This enables, in a particularly reliable and convenient way, that the NFT's metadata is automatically adjusted when a correspondingly adjusted release configuration is uploaded. The vehicle architecture information provides a precise name for the hardware configuration, so that the appropriate release configuration for this hardware configuration can be written into the metadata of the dynamic NFT. Proven application programming interfaces (APIs) can be used for communication between the central computing device and the blockchain oracle.

After the release configuration assigned to the dynamic NFT has been updated, it is transmitted to the vehicle. This can be initiated by the central processing unit or by an internal vehicle processing unit. For example, a central control unit of the vehicle can detect the replacement of a hardware component, whereupon a program routine is started that retrieves updated release configurations. Such a command could also be sent from the central processing unit to the vehicle, or the central processing unit could actively transmit the adjusted release configuration to the vehicle itself.

Preferably, the central computing device executes the release configurations adapted to different hardware in a third-party information-specific manner. The blockchain oracle obtains third-party information when adapting the metadata, and the blockchain oracle takes the third-party information into account when adapting the metadata. Third-party information refers to all other information that is not vehicle-related or vehicle hardware-related. For example, it could be current news, a current weather report, or other information available online. The blockchain oracle can also obtain said third-party information via corresponding APIs. This makes it possible to adapt the release configuration to current third-party information.

For example, a vehicle function might involve emitting a specific light pattern in the vehicle interior, for example, using so-called ambient lighting. As third-party information, the blockchain oracle can determine that it is raining at the location of the user's vehicle at the time the dynamic NFT is adjusted. The program routine underlying the release configuration can then be adjusted so that the light pattern emitted via the ambient lighting is primarily designed in shades of blue. Another vehicle function could provide for the output of certain acoustic signals such as sounds, music, or the like in the vehicle interior. As third-party information, the calendar date could be taken into account, whereupon the blockchain oracle determines that the release configuration will be changed in spring. Spring-like birdsong is then imprinted on the acoustic signal underlying the vehicle function. The central computing facility or the vehicle manufacturer can give the blockchain oracle instructions as to which third-party information the metadata or media files included in the metadata or referenced by the metadata should be adapted and in what way.

An alternative embodiment of the method according to the invention, however, provides that the central computing device writes program code into the NFT's metadata when minting the NFT. The execution of this code by an in-vehicle computing unit generates the release configuration in the vehicle. The computing unit, taking the program code into account, adapts the release configuration to the current hardware. Thus, the release configuration can also be adapted to the current vehicle hardware using static NFTs. This embodiment has the advantage of being more cost-effective to implement, as the corresponding blockchain oracle services do not have to be paid for. However, this embodiment is subject to certain limitations. For example, the program code written into the NFT's metadata during minting is fixed and cannot be subsequently modified. Therefore, it must be known in advance within which parameter limits adaptations to modified hardware are possible. For example, variables can be used as placeholders for certain sizes, which are then precisely defined subsequently. However, unforeseen innovations may occur, meaning that the full potential of future hardware developments may not be fully utilized. In addition, generating the vehicle configuration in the vehicle requires computing operations, so powerful computer systems are preferable. However, such systems also consume a particularly large amount of electrical energy.

Here, too, there are various ways to determine whether a release configuration needs to be adjusted. For example, every time the vehicle is started, an in-vehicle computing unit can read the user's wallet and thus identify the NFTs stored in the wallet. The relevant metadata is then read, and the program code referenced therein is executed. For this purpose, the corresponding program code can be transferred to the vehicle. The adjustment of the release configuration could also be initiated manually by the user or automatically by an in-vehicle computing unit upon detection of new hardware components in the vehicle.

The metadata can contain certain variables whose precise values are read from the vehicle itself. For example, a new vehicle might be equipped with a display with a particularly high resolution. The resolution is higher than that of a previous display. The resolution is referenced by the variable in question. If the program code contained in the metadata for generating release configurations is then executed in the vehicle, the display resolution values stored in a processing unit in the vehicle are taken into account.

Preferably, the NFT's metadata is stored on a decentralized network storage. This reduces the risk of accessing the metadata because, should some nodes of the decentralized network storage fail, the metadata can still be retrieved by accessing another node of the network storage. However, using a decentralized network storage may involve increased costs.

A further advantageous embodiment of the method according to the invention further provides that the metadata define an API via which the computing unit obtains the data required to generate the release configuration from a central and/or decentralized network storage. This data can be program code and/or media files. Therefore, additional data may be required to generate the adapted release configuration, which can be obtained accordingly. In particular, the program code can be adapted by the vehicle manufacturer at any time.

Preferably, the data describes third-party information. Thus, even using static NFTs, it is possible to incorporate information from outside the blockchain into the adjustment of the release configurations. For example, the aforementioned blue ambient lighting can be implemented in rainy weather, or birdsong can be incorporated into the acoustic signal in spring.

A further advantageous embodiment of the method according to the invention further provides that the computing unit uses generative AI to generate the release configuration. With the help of generative AI, such as so-called large language models (LLM), complex media content can be generated in a particularly simple manner. In particular, natural language can be used to formulate design requirements. The generative AI can be executed externally to the vehicle, for example on a cloud server. To interact with the cloud server, the computing unit can contact it via the Internet. Proven APIs can also be used for this purpose. If, for example, a specific image or video needs to be displayed in the vehicle as part of the vehicle's function, the corresponding image or video content can be generated by the generative AI. The corresponding text describing the image content is described or referenced by the metadata of the NFT.

In an information technology system comprising a central computing device and a vehicle, according to the invention, the central computing device and the vehicle are configured to execute a method described above. The vehicle can be any road vehicle such as a car, truck, van, bus, or the like. In general, it can also be a rail vehicle, watercraft, or aircraft. Communication between the vehicle and the central computing device can, in particular, be wireless. For this purpose, the central computing device can be connected to a network, in particular the Internet. The vehicle can have a telecommunications unit, usually referred to as a telematics unit. Such a telematics unit enables the vehicle's on-board electronics to be connected to the Internet via mobile radio. The user can also have a mobile device such as a smartphone, tablet computer, laptop, wearable, or the like, which can be coupled to the vehicle via cable or wirelessly and/or is also indirectly connected to the central computing device via the user's user account. The central computing facility is also connected to a cryptocurrency network capable of minting and sending corresponding NFTs. Thus, the central computing facility can form a computing node of this cryptocurrency network or be in communication with such a network. These can be any conceivable cryptocurrency network or cryptocurrency already known. They can also be previously unknown and unprogrammed types of cryptocurrencies. In particular, smart contract standards or non-fungible token standards tailored specifically to the implementation of the method according to the invention can be newly defined and established.

Further advantageous embodiments of the method according to the invention for enabling vehicle functions also emerge from the exemplary embodiments which are described in more detail below with reference to the figures.

• 1 eine schematische Darstellung der an der Ausführung des erfindungsgemäßen Verfahrens zur Freischaltung von Fahrzeugfunktionen beteiligten Akteure;
• 2 eine schematische Darstellung des Aufbaus eines NFTs gemäß einer ersten Ausführungsform;
• 3 eine schematische Darstellung des Aufbaus eines NFTs gemäß einer zweiten Ausführungsform; und
• 4 eine schematische Darstellung des Aufbaus eines NFTs gemäß einer dritten Ausführungsform.

Showing:

• 1 a schematic representation of the actors involved in the execution of the method according to the invention for activating vehicle functions;
• 2 a schematic representation of the structure of an NFT according to a first embodiment;
• 3 a schematic representation of the structure of an NFT according to a second embodiment; and
• 4 a schematic representation of the structure of an NFT according to a third embodiment.

One in 1 The user 2 shown owns a vehicle 1, here in the form of a first vehicle 1.1, which is sold after a certain period of time and replaced by a second vehicle 1.2. The user 2 has purchased a vehicle function for the vehicle 1 from the vehicle manufacturer. The vehicle function can be provided via the hardware of the vehicle 1. The vehicle function is provided when the hardware is configured by software according to a release configuration. In order to receive the release configuration, the user 2 is registered with the vehicle manufacturer via a user account. For this purpose, the vehicle manufacturer offers a corresponding portal via a central computing device 3. The portal is accessible via all common end devices, in particular via the Internet, such as a mobile end device such as a smartphone 9, a tablet computer, a laptop, a desktop computer, an in-vehicle computing unit or the like.

The user 2 links his wallet 4 for cryptocurrencies with his user account. The central computing device 3 causes the minting of a 2 to 4 The non-fungible token (NFT) shown here, with the release configuration being assigned to the NFT as a digital asset. By acquiring the vehicle function, the central computing device 3 subsequently causes the respective NFT to be assigned to the wallet 4 of user 2.

Now, user 2 wants to activate the vehicle function in their vehicle 1. This can be initiated manually, for example. This causes the central computing device 3 to read the NFTs stored in wallet 4 and transfer the associated release configurations for the NFTs found in wallet 4 to vehicle 1. User 2 can then use the vehicle function in the first vehicle 1.1.

Now, the hardware used to output the vehicle function in vehicle 1 changes, or user 2 switches from the first vehicle 1.1 to the second vehicle 1.2. User 2 now wants to use the vehicle function he already acquired in the second vehicle 1.2. However, the hardware of the second vehicle 1.2 is configured differently, so that either the previous vehicle function cannot be output to its full extent, or the hardware has been expanded to provide more options for outputting the vehicle function.

According to the invention, the release configuration is now adapted to the modified hardware of the vehicle 1. This enables the user 2 to permanently utilize the vehicle function to its maximum extent. For example, an adapted program code is implemented that is capable of controlling several newly installed light bars to emit a colored and dynamic light pattern.

There are generally several options for adjusting the release configuration. One variant uses a so-called blockchain oracle 6, which is able to read the metadata 7 associated with an NFT (see 2 to 4 ) even after minting. To this end, the blockchain oracle 6 forms an interface between a blockchain 10 used to carry out transactions of the respective NFTs and so-called off-chain resources 11. The off-chain resources 11 are any sources external to the blockchain 10, such as an internet server. The central computing device 3 can also be such an off-chain resource 11.

2 shows the general structure of an NFT. The NFT includes metadata 7, which which can be stored completely or in part on-chain and/or off-chain. The metadata 7 can comprise a first content 12.1 and a second content 12.2. For example, the first content 12.1 is public content and the second content 12.2 is private content, indicated by the pictogram of a padlock. The respective content, or a part of the content 12.1, 12.2, forms the digital asset 13 assigned to the NFT. For example, this can be video clips, sound files, images, and the like. In particular, the public content, i.e. the first content 12.1, is stored on a decentralized network storage 5.2, such as the so-called IPFS. Since a distributed peer-to-peer network is used to manage the blockchain 10 and thus also the NFTs, the box representing the NFT is in 2 also connected to a corresponding decentralized network storage 5.2. The decentralized network storage 5.2 also represents so-called Web3 applications.

Preferably, the first content 12.1 only comprises sample files that do not fully allow reconstruction of the shared configuration. The second content 12.2, i.e., the private content, is preferably stored on a central network system 5.1. In particular, the central network storage 5.1 is cryptographically encrypted and thus not publicly accessible. The central network storage 5.1 also represents a so-called Web2 application. In particular, the second content 12.2 is modifiable, while the first content 12.1 is not modifiable but can be supplemented.

If there is a new vehicle generation or modified hardware, the release configuration is adapted by the vehicle manufacturer to the modified hardware. The new content is then uploaded to the corresponding network storage devices 5.1 and 5.2. When the vehicle is changed or the hardware is changed, the modified content can then be downloaded from the respective vehicle. Since the metadata 7 and the already stored first content 12.1 cannot normally be modified, the second content 12.2 is preferably adapted for this purpose, which can still be addressed via the reference included in the metadata 7. For example, the metadata 7 can contain multiple references for different program versions, where the references for newer program versions initially point to empty memory areas of the second content 12.2 or the central network storage device 5.1. If new program versions for modified hardware are created by the vehicle manufacturer, these memory areas are filled and can be retrieved accordingly.

3 shows the possible embodiment using so-called dynamic NFTs (dNFT) in combination with the aforementioned blockchain oracle 6. The blockchain oracle 6 is connected to the central computing device 3 and the off-chain resources 11 in order to receive information from the outside world. Depending on this information, the blockchain oracle 6 can incorporate changes into the metadata 7 of the dynamic NFT (dNFT). For example, the blockchain oracle 6 can query the vehicle manufacturer whether or when a new version of the respective release configurations is available. To do so, the blockchain oracle 6 also obtains information from the respective vehicle 1 regarding exactly which hardware is installed and compares this information with the release configurations offered by the vehicle manufacturer. In particular, the metadata 7 is stored on a central network storage device 5.1, but in an unencrypted and thus publicly accessible form. The metadata 7 in turn refers to a content 12 which includes, for example, example images, video material, image material and sound material for the activated vehicle model of the user 2.

The contents 12 on the decentralized network storage 5.2 are, in particular, immutable. To change the release configuration, the vehicle manufacturer adds new program code to said decentralized network storage 5.2. The blockchain oracle 6 changes the metadata 7 to update the stored reference to the respective data so that the added program code is addressed.

The process is as follows: First, the hardware of vehicle 1 is modified. The vehicle manufacturer changes the release configuration accordingly and uploads the modified release configuration to the decentralized network storage 5.2. The blockchain oracle 6 may have subscribed to a service from the vehicle manufacturer that provides for the transmission of corresponding information from the central computing device 3 to the blockchain oracle 6 when corresponding release configurations are changed.

The blockchain oracle 6 can then adjust the reference included in the metadata 7 to the decentralized network storage 5.2 according to a manufacturer's specification. This enables the vehicles 1 to address the changed storage location by reading the metadata 7 and download the current release configuration.

Further information for adjusting the release configurations can also be taken into account via the respective off-chain resources 11. For example, a light pattern in question can be designed in blue in rainy weather, and the like.

4 shows an alternative embodiment using static NFTs. The NFT comprises an API and a program code 8 that enables a respective in-vehicle computing unit to independently generate the adapted release configuration in the vehicle itself. The API can be used to load necessary information from external sources. In particular, the program code 8 is based on the use of generative artificial intelligence. For example, public example images and the design data for images, videos, and sound are stored as a so-called container image on a decentralized network storage 5.2 as content 12.

Taking the API into account, information provided by off-chain resources 11 can also be incorporated into the generation process of the release configuration in the vehicle (not shown).

The process is as follows: First, a new vehicle generation or hardware is made available. When the hardware of vehicle 1 is changed, the software or program code 8 described by the NFT is downloaded to vehicle 1. Program code 8 is then executed in vehicle 1, thus generating the modified release configuration.

QUOTES CONTAINED IN THE DESCRIPTION

This list of documents submitted by the applicant was generated automatically and is included solely for the convenience of the reader. This list is not part of the German patent or utility model application. The DPMA assumes no liability for any errors or omissions.

Cited patent literature

• DE 10 2022 000 646 A1 [0007]
• US 2022/0383295 A1 [0008]
• US 2023/0071093 A1 [0009]

Claims (9)

Method for activating a vehicle function, wherein the vehicle function can be provided via the hardware of a vehicle (1), the hardware is configured by software, and wherein the vehicle function is provided by the hardware when the hardware is configured according to a release configuration, characterized in that - a user (2) of the vehicle (1) logs into a central computing device (3) with a user account; - the user (2) links his wallet (4) to the user account; - the central computing device (3) initiates the minting of an NFT (NFT), wherein the release configuration is assigned to the NFT (NFT) as a digital asset (13); - the central computing device (3) causes the NFT (NFT) to be assigned to the wallet (4) of the user (2); - the central computing device (3) reads out the NFTs (NFT) stored in the wallet (4); - the central computing device (3) obtains respective release configurations for NFTs (NFT) stored in the wallet (4) and transmits them to the vehicle (1); - the hardware of the vehicle (1) or the vehicle (1) itself is changed; - the release configuration is adapted to the changed hardware; and - the adapted release configuration is used in the vehicle (1). Procedure according to Claim 1 , characterized in that - the central computing device (3) stores release configurations adapted to different hardware on a central (5.1) or decentralized network storage (5.2); - the NFT (NFT) is minted as a dynamic NFT (dNFT); - the central computing device (3) conveys vehicle architecture information to a blockchain oracle (6), wherein the vehicle architecture information describes the hardware of the vehicle (1) of the user (2); - the blockchain oracle (6) adapts the metadata (7) of the dynamic NFT (dNFT) so that the release configuration adapted to the vehicle architecture information is assigned to the dynamic NFT (dNFT) as a digital asset (13); and - the vehicle (1) obtains the adapted release configuration from the network storage (5.1, 5.2). Procedure according to Claim 2 , characterized in that the central computing device (3) executes the release configurations adapted to different hardware in a third-party information-specific manner, the blockchain oracle (6) obtains third-party information when adapting the metadata (7) and takes the third-party information into account when adapting the metadata (7). Procedure according to Claim 1 , characterized in that the central computing device (3) writes a program code (8) into the metadata (7) of the NFT (NFT) when minting the NFT (NFT), the execution of which by an internal vehicle computing unit generates the release configuration in the vehicle (1), wherein the computing unit, taking into account the program code, adapts the release configuration to the current hardware. Procedure according to Claim 4 , characterized in that the metadata (7) of the NFT (NFT) are stored on a decentralized network storage (5.2). Procedure according to Claim 4 or 5 , characterized in that the metadata (7) define an API (API) via which the computing unit obtains data required to generate the release configuration from a central (5.1) and/or decentralized network storage (5.2). Procedure according to Claim 6 , characterized in that the data describe third-party information. Method according to one of the Claims 4 until 7 , characterized in that the computing unit uses generative AI to generate the release configuration. Information technology system, comprising a central computing device (3) and a vehicle (1), characterized in that the central computing device (3) and the vehicle (1) are configured to carry out a method according to one of the Claims 1 until 8 are set up.

Images