Method and information technology system for unlocking a vehicle function

Abstract

The invention relates to a method for unlocking a vehicle function, wherein the vehicle function is providable via hardware of a vehicle (1), which 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. The device according to the invention is characterized in that: - a user (2) of the vehicle (1) logs in to a central computing device (3) using a user account; the user (2) binds his wallet (4) to the user account; - the central computing device (3) initiates the generation of a non-fungible token (NFT), wherein the release configuration is assigned to the non-fungible token (NFT) as a digital asset (13); - the central computing device (3) causes the assignment of the non-fungible token (NFT) to the wallet (4) of the user (2); - the central computing device (3) reads the non-fungible token (NFT) stored in the wallet (4); - the central computing device (3) retrieves the corresponding release configuration for the non-fungible token (NFT) stored in the wallet (4) and transmits it to the vehicle (1); - the hardware of the vehicle (1) or the vehicle (1) itself is changed; - the release configuration is adjusted according to the changed hardware; and - the adjusted release configuration is used in the vehicle (1).

Description

Technical Field

[0001] The present invention relates to a method for unlocking vehicle functions of the type defined in more detail in the preamble of claim 1, and an information technology system having a central computing device and a vehicle. Background Technology

[0002] Vehicles are becoming increasingly digitized. As a result, mechanical steering systems, braking systems activated by pedal position, and fuel pumps are being replaced by electronic control systems. This is also known as drive-by-wire. Furthermore, new driver assistance features are being offered to enhance safety and comfort, such as lane keeping assist, adaptive cruise control, traffic sign recognition, and the ability to watch movies, make video calls, or play audiobooks on in-vehicle displays.

[0003] Here, various vehicle functions require the installation of specific hardware components within the vehicle. During the ordering process, specific hardware components can be installed, typically allowing for multiple functions, of which customers usually only purchase some. The remaining functions, i.e., those not purchased, are then disabled in the vehicle manufactured for the customer via software configuration. However, since the necessary hardware has already been installed, this allows these functions to be unlocked later via software. Therefore, for example, by reconfiguring the vehicle software, it is possible to temporarily or permanently unlock higher engine power, or, for example, reserve seat heating functions for winter months.

[0004] To manage vehicle features used in a vehicle, users need to interact with the vehicle manufacturer, for example, via a central portal (e.g., a server operated by the vehicle manufacturer), which forms the interface between the user's account and their vehicle. In this way, users can connect their vehicle to their user account and personalize their reservations for vehicle features. However, the vehicle manufacturer retains control over the reserved features, which can negatively impact the user's decision-making process when adding features. Therefore, it is preferable to transfer control of the reservable vehicle features to the customer.

[0005] Blockchain technology allows for the generation of non-fungible tokens (NFTs). The creation of NFTs is also known as NFT generation. Specifically, the initiation of the generation and / or transfer of a corresponding NFT is controlled by so-called smart contracts. A smart contract is program code written into the blockchain, which the blockchain network can automatically execute based on the information written into the blockchain. Each NFT is unique, i.e., "non-fungible." Here, an NFT represents a specific asset, particularly a digital asset, such as image files, video files, audio files, text files, etc. Physical assets can also be allocated to NFTs in the form of "proof of ownership," such as houses, vehicles, sneakers, etc. Information describing or referencing the asset allocated to the NFT is typically written into the NFT's metadata. Metadata can be stored in blocks within the blockchain itself, or preferably in a storage location outside the blockchain. Blockchains can be centrally managed or decentralized. Here, so-called non-fungible token standards, such as ERC721 or ERC1155, define how the corresponding metadata is constructed and processed.

[0006] Furthermore, so-called hybrid smart contracts are known, which associate program code running on the blockchain with information and computations available outside the blockchain. Here, a blockchain oracle is used as the interface. For example, Chainlink provides such services for connecting the blockchain to external systems, enabling the execution of smart contracts based on real-world inputs and outputs.

[0007] DE 10 2022 000 646 A1 discloses a method for generating and using vehicle-related non-fungible tokens (NFTs). This patent document describes the provision of vehicle functionality based on NFTs. For this purpose, vehicle data is collected during vehicle operation and used to generate NFTs. Therefore, the vehicle itself participates in the NFT generation process. For example, NFTs can be generated during vehicle manufacturing, repair, maintenance, and sale. This allows for tracking the vehicle's condition or wear and tear using NFTs. Vehicle-related NFTs can also be generated when the vehicle reaches specific milestones, such as achieving set operating time, mileage, or time spent at specific locations. Thus, so-called "achievements" can be accomplished through the vehicle, thereby making vehicle use more attractive to users by providing gamified functionality. Users can track their personal performance using the NFTs generated upon achieving achievements and display them as proof to others.

[0008] Furthermore, US 2022 / 0383295 A1 discloses a so-called NFT asset repository. This patent aims to address the problem that NFTs are typically associated with digital assets (also known as "Digital Assets"), but cannot be interacted with in the real world. The repository constitutes an electronic device in the form of a computing device capable of downloading the digital assets associated with the NFTs via the internet and outputting them through output tools built into the repository. Thus, for example, digital artwork can be displayed on a display device, or audio content can be played through an integrated speaker. Here, the repository has its own wallet, allowing the corresponding NFT or digital asset to be uniquely allocated to a specific repository. Owners of such repositories can transfer / exchange their NFTs along with the corresponding digital assets, for example, by exchanging the repository itself, or by performing the corresponding NFT exchange on the underlying blockchain.

[0009] Furthermore, US 2023 / 0071093 A1 describes a system and method for consistently setting up and transferring NFT assets across multiple platforms based on the use of smart contracts. This patent document describes an intermediary mechanism for utilizing various NFT marketplaces. Here, the smart contract used to generate the NFT includes processable conditions from multiple different NFT marketplaces. Additionally, the patent document describes a conversion module capable of defining the conditions of the smart contract in natural language and converting them into machine-readable code. This improves the user-friendliness of smart contract writing for users with little or no programming knowledge.

[0010] This situation may arise after a considerable period of time when the vehicle hardware has changed, such as replacing certain parts, or when a user purchases a new vehicle and abandons the old one. In this case, the problem lies in how to output the previously purchased vehicle functions via the new hardware. Components originally designed to output vehicle functions, such as specific headlights, seat-integrated massage actuators, or similar components, may no longer be available, or new components may have been installed. Summary of the Invention

[0011] The purpose of this invention is to provide an improved method for unlocking vehicle functions, which allows users to permanently use previously purchased vehicle functions.

[0012] According to the invention, this objective is achieved by a method for unlocking vehicle functions having the features of claim 1. Advantageous designs and improvements, as well as the information technology system for performing the method, are derived from the relevant claims.

[0013] A general method for unlocking vehicle functions, wherein the vehicle functions are provided via vehicle hardware configured by software, and wherein the vehicle functions are provided by the hardware when the hardware is configured according to an unlock configuration / enable configuration / release configuration, a further development according to the invention being:

[0014] - Vehicle users log in to the central computing device using their user accounts;

[0015] - Users link their wallets to their user accounts;

[0016] - The central computing device initiates the generation of NFTs, in which the release configuration is allocated as a digital asset to the NFT;

[0017] - Central computing devices enable the distribution of NFTs to user wallets;

[0018] -The central computing device reads the NFTs stored in the wallet;

[0019] - The central computing device retrieves the appropriate release configuration for the NFTs stored in the wallet and transmits it to the vehicle;

[0020] - Modify the vehicle hardware or the vehicle itself;

[0021] - Adjust / adapt configuration release based on changed hardware; and

[0022] - Use the adjusted release configuration in the vehicle.

[0023] By releasing configuration adjustments, new code segments can be considered, which in turn enable control of new hardware. Therefore, if a user changes vehicles, or if existing hardware components are replaced and / or new hardware components are installed in a user's old vehicle, these code segments can be used accordingly to provide vehicle functionality. This reliably ensures that users can permanently use previously purchased vehicle functions.

[0024] Here, vehicle function refers to any conceivable function that can be executed by software adjustments to hardware already installed in the vehicle. In this case, it could be, for example, special graphical elements of a graphical user interface, such as a specially designed tachometer for a combination instrument cluster designed as a display device, a unique simulated engine sound output from an electric motor via external speakers, enhanced engine power, comfort functions such as seat heating and massage functions, and lighting functions such as special light patterns for ambient lighting.

[0025] The central computing device is a cloud server or server cluster, particularly managed by vehicle manufacturers. Users have individual user accounts, uniquely referential via usernames and protected by personal passwords. Here, a user's vehicle is linked to their user account, allowing the central computing device to uniquely allocate between the user and the corresponding vehicle. For this purpose, the vehicle is linked to the user account via a unique identifier (e.g., serial number, vehicle identification number, etc.). Furthermore, the user has a digital wallet for storing digital credentials or NFTs. The user then links the wallet to their user account so the central computing device can verify the wallet's contents. In its simplest case, this simply means the user saves their wallet's public address, such as a so-called "public key," to the central computing device. Here, the infrastructure operated by the vehicle manufacturer—the platform provided on the central computing device—also has integrated wallet functionality. Therefore, vehicle manufacturers can not only have their own manufacturer wallets, but they can also allocate their own wallets for each user account. This lowers the barrier to entry for non-technically savvy users to use the method according to the invention, as users are therefore not required to create their own wallets.

[0026] To unlock corresponding vehicle configurations, vehicle manufacturers develop corresponding release configurations. A release configuration is a set of program code that, when executed on the vehicle's computing unit, allows adjustments to the computing unit or hardware to make available vehicle functions accessible via that hardware. In the simplest case, this involves changing a bit signature, such as changing it from 0 to 1 or from a negative to a positive value. Vehicle manufacturers can provide release configurations tailored to various hardware combinations. For each release configuration, a central computing device triggers the generation of the corresponding NFT. For example, the timing of NFT generation can be chosen so that the NFT is generated precisely when the user obtains the release configuration from the vehicle manufacturer due to an event. There are various ways the central computing device can trigger the allocation of the corresponding NFT to the user's wallet. The central computing device or vehicle manufacturer may have its own manufacturer wallet, to which the NFT is allocated upon generation. Subsequently, the NFT is transferred from the manufacturer wallet to the user's wallet. Alternatively, the user's wallet address or public key may be directly specified during generation, so the newly generated NFT initially appears in the user's wallet.

[0027] After purchasing a vehicle feature, a user can activate it in their vehicle. This can be done automatically upon purchase or manually by the user. For this purpose, users can use various human-machine interfaces, such as the vehicle's own user interface, a touchscreen display, a mobile device connected to the vehicle (especially via a user account), such as a smartphone, or a browser-based access interface, such as an internet-connected desktop computer. The user can then log into the central computing device via their user account, select their vehicle in the corresponding input field, and activate the specific vehicle feature, for example, by checking a checkmark. The respective computing units used for this purpose, such as the in-vehicle computing unit, the user's smartphone, or desktop computer, send information to the central computing device via the corresponding application programming interface (API), indicating that the corresponding vehicle feature should be activated.

[0028] At different times, such as when a user logs into their account through a portal or each time the vehicle is started, the central computing device can read the user's wallet and thus record the NFTs stored therein. Correspondingly, the central computing device adjusts the output mask to display currently available vehicle features. This allows the user to turn purchased vehicle features on and off as needed. After the user activates a corresponding vehicle feature, the central computing device sends a corresponding signal to the vehicle to activate that feature. For this purpose, the central computing device can, for example, transmit the release configuration program code itself along with instructions to execute the corresponding program code to the appropriate computing unit in the vehicle.

[0029] All existing or future blockchain technologies can be used to provide the method according to the invention. The blockchain can be centrally or decentralized.

[0030] In its simplest case, an NFT contains only a unique identifier, such as a unique token identifier (TokenID). A central computing device can maintain a file storing the relationship between the NFT and its corresponding vehicle functionality. Therefore, the central computing device can read the user's wallet, obtain the unique token identifier (TokenID), and see in the file which vehicle functionality the user can therefore access. The central computing device then prompts the unlocking of the corresponding vehicle functionality in the user's vehicle. In this scenario, there's no need to assign a reference to the digital asset to the NFT, as the central computing device already possesses this information.

[0031] Herein, the method according to the present invention specifies:

[0032] -NFTs contain digital assets; or

[0033] - Digital assets are stored in centralized or decentralized network storage, where NFTs contain references to the digital asset.

[0034] Therefore, it's possible to bind the corresponding vehicle functionality to NFTs in different ways. The corresponding program code could then be directly written into the corresponding block representing the NFT in the blockchain used. Alternatively, it's also possible to store the corresponding program code and any necessary media files in a centralized or decentralized / centralized network storage, and only integrate a reference to the corresponding storage location into the blockchain. Such a reference is also called a URI, such as a URL. This allows digital assets to be stored "on-chain" or "off-chain."

[0035] In particular, a centralized network storage can be a server used as a central computing device, or a server in a server cluster.

[0036] Distributed or decentralized network storage can be, for example, the so-called "InterPlanetary File System" (IPFS). In this case, it is a protocol and network used to form a peer-to-peer storage for files, such as so-called hypermedia files. The advantage of using decentralized network storage compared to centralized network storage is its lower probability of failure. Centralized network storage is highly susceptible to at least temporary failures due to environmental factors such as network attacks, maintenance, power outages, or floods. During this period, no digital assets can be retrieved from centralized network storage. However, with decentralized network storage, relevant information is stored on multiple nodes, so even if one or a few nodes fail, information can still be obtained from other nodes.

[0037] Here, the "allocation" of release configurations to NFTs should be understood in an abstract way. Multiple allocation models can be considered. As mentioned earlier, the corresponding program code can be directly written to the blockchain or stored in the corresponding network storage and referenced via a link. Alternatively, vehicle manufacturers may use a single, unique identifier to mark different vehicle functions or release configurations. For example, this could be an ID. This identifier could then be written in plaintext to the blockchain itself or to metadata in the network storage. The actual program code can then be stored in protected storage on a central computing device, inaccessible to the public. When the central computing device reads an NFT from a user's wallet, it also reads the unique identifier of the release configuration and can retrieve the digital data required to activate the vehicle function in the vehicle—specifically, the aforementioned program code—from the protected storage.

[0038] Furthermore, the method according to the invention specifies that the release configuration is distributed to the NFT in an encrypted form using cryptographic techniques. The central computing device, after reading the user's wallet and obtaining the release configuration, decrypts the release configuration and transmits the decrypted release configuration to the vehicle. This further improves the integrity of the underlying program code of the release configuration and any media files, as well as network security when executing the method according to the invention. In this case, verified cryptographic encryption techniques can be employed, such as signature-based encryption using asymmetric key pairs. Thus, the program code of the release configuration can be cryptographically encrypted and directly written to the blockchain, written to NFT metadata, or stored in a corresponding centralized or decentralized network storage referenced by metadata. Therefore, it also resists the "theft" of the program code by third parties. To decrypt the encrypted release configuration, the central computing device needs the corresponding private key, which it already possesses as the cryptographic organization of the release configuration program code. Here, encryption can also be used for communication between the central computing device and the vehicle, thus, in a broader sense, the decrypted release configuration is re-encrypted and then decrypted again in the vehicle. This also prevents data interception during data exchange between the central computing device and the vehicle.

[0039] Typically, there are two different implementation variants regarding how to change the release configuration assigned to an NFT.

[0040] Thus, a first alternative embodiment of the method according to the present invention specifies:

[0041] - The central computing device stores the release configuration, which is adjusted for different hardware, on a centralized or decentralized network storage.

[0042] - Generate NFTs in the form of dynamic NFTs;

[0043] - The central computing device transmits vehicle architecture information to the blockchain oracle, whereby the vehicle architecture information describes the hardware of the user's vehicle;

[0044] - Blockchain oracles adjust the metadata of dynamic NFTs to allocate release configurations adjusted for vehicle architecture information to dynamic NFTs as digital assets; and

[0045] - The vehicle retrieves the adjusted release configuration from the network memory.

[0046] With the help of blockchain oracles and dynamic NFTs, the metadata content of NFTs can also be modified subsequently. To do this, a smart contract is used when generating the NFT, which triggers metadata changes based on external boundary conditions. This type of smart contract is also known as a hybrid smart contract. Since smart contracts can typically only read content stored on-chain—that is, information can only be read from the blockchain—a blockchain oracle is needed to form a connection between the smart contract and the outside world. In this way, content stored off-chain can also be used as execution conditions for logic defined in the smart contract.

[0047] To this end, vehicle manufacturers first develop compatible hardware or new vehicles, and then adjust the corresponding vehicle functions based on the new hardware. Correspondingly, the underlying release configuration is adjusted according to the new hardware, and the corresponding updated program version is stored in a centralized or decentralized network storage. Centralized network storage can be, for example, the central computing device itself. Decentralized network storage is particularly storage managed by peer-to-peer networks (e.g., the InterPlanetary File System (IPFS)).

[0048] Therefore, the smart contract used to generate the dynamic NFT may contain information indicating that the NFT's metadata should be changed once the vehicle manufacturer provides a new release configuration at the address stored in the smart contract. This allows the NFT's metadata to be automatically adjusted when the corresponding adjusted release configuration is uploaded, in a particularly reliable and convenient manner. Here, the vehicle architecture information specifies the exact name of the hardware configuration, so that a matching release configuration can be written into the dynamic NFT's metadata for that hardware configuration. Communication between the central computing device and the blockchain oracle can be achieved using a verified application programming interface (API).

[0049] After updating the release configuration assigned to the dynamic NFT, the release configuration is transmitted to the vehicle. This can be initiated by a central computing device or by an onboard computing unit. For example, the vehicle's central control unit can determine the replacement of a hardware component and then initiate a routine that prompts the retrieval of the updated release configuration. Such instructions can also be sent from the central computing device to the vehicle, or the central computing device can proactively forward the adjusted release configuration itself to the vehicle.

[0050] Preferably, the central computing device executes a release configuration adjusted / adapted for different hardware in a manner specific to third-party information. The blockchain oracle obtains this third-party information when adjusting metadata, and considers this third-party information during the adjustment process. The third-party information comprises all information unrelated to the vehicle or its hardware. For example, this could be current news, current weather forecasts, or other information retrievable from the internet. The blockchain oracle can also obtain this third-party information via a corresponding API. This enables the release configuration to be adjusted based on the current third-party information.

[0051] For example, a vehicle function might output a specific light pattern within the vehicle's interior, such as when using ambient lighting. As third-party information, a blockchain oracle could determine that it was raining at the location of the user's vehicle at the time the dynamic NFT was adjusted. The underlying routines for the release configuration could then be adjusted so that the light pattern emitted by the ambient lighting is primarily designed to be blue. Another vehicle function might be designed to output specific sound signals within the vehicle's interior, such as engine sounds or music. Third-party information could consider, for example, a calendar date, and the blockchain oracle would then determine that the release configuration would be changed in the spring. Subsequently, spring birdsong would be superimposed onto the sound signal upon which the vehicle function relies. Here, the central computing device or vehicle manufacturer could instruct the blockchain oracle on which third-party information should be used and in what manner to adjust the metadata or media files contained in or referenced by the metadata.

[0052] Conversely, an alternative embodiment of the method according to the invention specifies that a central computing device writes program code into the NFT's metadata when generating the NFT. This program code is then executed by an onboard computing unit to generate a release configuration in the vehicle, wherein the computing unit adjusts the release configuration based on the current hardware, taking into account the program code. Therefore, a static NFT can also be used to adjust the release configuration according to the vehicle's current hardware. This implementation variant is more cost-effective because it avoids paying corresponding blockchain oracle service fees. However, this implementation has certain limitations. The program code written into the NFT's metadata during generation is fixed and cannot be changed subsequently. Therefore, the limits within which the modified hardware can be adjusted must be known beforehand. For example, variables can be used as placeholders for specific parameters, which are then precisely defined later. However, unforeseen innovations may occur, potentially preventing the full utilization of the potential of future hardware development. Furthermore, generating the vehicle configuration in the vehicle requires computational operations, thus preferably requiring a powerful computer system. However, such a system also consumes a significant amount of electrical energy.

[0053] There are several methods for determining when to adjust the release configuration. For example, each time the vehicle is started, the onboard computing unit can read the user's wallet and thus identify the NFTs held within. It then reads the corresponding metadata and executes the program code referenced therein. This program code can then be transferred to the vehicle. Adjustments to the release configuration can also be initiated manually by the user or automatically by the onboard computing unit by recognizing new hardware components in the vehicle.

[0054] The metadata may contain specific variables whose exact values ​​are read within the vehicle itself. For example, a new car might have a display with a particularly high resolution, higher than the previous generation. The resolution is referenced through these variables. Therefore, when the program code included in the metadata for generating the release configuration is executed within the vehicle, the display resolution value stored in the vehicle's internal computing unit is taken into account.

[0055] Preferably, the NFT's metadata is stored on a decentralized web storage. This reduces the risk of metadata access failure, because even if several nodes of the decentralized web storage fail, the metadata can still be retrieved through other nodes accessing the web storage. However, using a decentralized web storage may come with increased costs.

[0056] Furthermore, another advantageous embodiment of the method according to the invention specifies a metadata-defined API via which the computing unit retrieves data required to generate the release configuration from a centralized and / or decentralized network storage. This data may be program code and / or media files. Thus, additional data may be required to generate the adjusted release configuration, and this data can be retrieved accordingly. In particular, the program code can be adjusted at any time by the vehicle manufacturer.

[0057] Preferably, this data describes third-party information. Therefore, it is also possible, when using static NFTs, to consider information from outside the blockchain to adjust the release configuration. For example, ambient lighting could be activated on rainy days, or birdsong could be incorporated into the sound signal in spring.

[0058] Furthermore, another advantageous embodiment of the method according to the invention specifies that the computing unit uses generative AI to generate release configurations. With the aid of generative AI, such as a so-called Large Language Model (LLM), complex media content can be generated in a particularly simple way. Specifically, natural language can be used to express design requirements for this purpose. Here, the generative AI can be executed outside the vehicle, for example, on a cloud server. To interact with the cloud server, the computing unit can connect to the cloud server via the Internet. Verified APIs can also be used for this purpose. For example, if, as part of vehicle functionality, specific images or videos need to be displayed in the vehicle, the generative AI can be used to generate corresponding image or video content. Here, the corresponding text describing the image content is described or referenced through NFT metadata.

[0059] According to the present invention, in an information technology system comprising a central computing device and a vehicle, the central computing device and the vehicle are configured to perform the above-described method. The vehicle can be any road vehicle, such as a car, truck, van, bus, etc. Generally, it can also be a rail vehicle, a water transport vehicle, or an aircraft. Specifically, communication between the vehicle and the central computing device can be wireless. For this purpose, the central computing device can be connected to a network, particularly the Internet. The vehicle can have a telecommunications unit, commonly referred to as a telematics unit. This telematics unit enables the vehicle's onboard electronic equipment to connect to the Internet via a mobile network. Users can also possess mobile terminal devices, such as smartphones, tablets, laptops, wearable devices, etc., which can be connected to the vehicle via wired or wireless means, and / or indirectly connected to the central computing device via a user account. Further, the central computing device is connected to a blockchain network capable of generating and sending corresponding NFTs. Therefore, the central computing device can constitute a computing node of this blockchain network, or establish a communication connection with such a blockchain network. Here, this can be any conceivable known blockchain network. It can also be a type of blockchain network that is currently unknown and undeveloped. In particular, this allows for the redefinition and setting of smart contract standards or non-fungible token standards specifically tailored to the implementation of the methods according to the invention. Attached Figure Description

[0060] Other advantageous embodiments of the method for unlocking vehicle functions according to the invention also arise from the embodiments described in more detail below with reference to the accompanying drawings.

[0061] in:

[0062] Figure 1 A schematic diagram of the participants involved in implementing the method for unlocking vehicle functions according to the present invention is shown;

[0063] Figure 2A schematic diagram of the NFT structure according to the first embodiment is shown;

[0064] Figure 3 A schematic diagram of the NFT structure according to the second embodiment is shown; and

[0065] Figure 4 A schematic diagram of an NFT structure according to a third embodiment is shown. Detailed Implementation

[0066] like Figure 1 As shown, User 2 owns Vehicle 1, here referred to as Vehicle 1.1, which will be sold after a period of time and replaced with Vehicle 1.2. User 2 has purchased a certain vehicle function from the vehicle manufacturer. This vehicle function is provided via the hardware of Vehicle 1. The vehicle function is provided when the hardware is configured via software according to the release configuration. To obtain the release configuration, User 2 has registered with the vehicle manufacturer via a user account. For this purpose, the vehicle manufacturer provides a corresponding portal website via a central computing device 3. This portal website is accessible through all commonly used terminal devices, particularly via the Internet, such as mobile terminal devices like smartphones 9, tablets, laptops, desktop computers, in-vehicle computing units, etc.

[0067] User 2 links their digital wallet 4 to their user account. Central computing device 3 then generates... Figures 2 to 4 The non-fungible token (NFT) shown is used to allocate the release configuration as a digital asset to the NFT. After purchasing the vehicle function, the central computing device 3 prompts the allocation of the corresponding NFT to the user 2's wallet 4.

[0068] User 2 now wishes to activate the vehicle function in their vehicle 1. This process can be triggered manually, for example. This prompts the central computing device 3 to read the non-fungible tokens (NFTs) stored in wallet 4 and transfer the assigned release configuration to vehicle 1 for the NFTs found in wallet 4. Thus, user 2 can use the vehicle function on the first vehicle 1.1.

[0069] Now, the hardware used in vehicle 1 to output vehicle functions has been changed, or user 2 has switched from vehicle 1.1 to vehicle 1.2. User 2 wants to use the vehicle functions they have purchased in vehicle 1.2 as well. However, the hardware in vehicle 1.2 has a different design, so it is not possible to fully output the previous vehicle functions, or the hardware has been expanded to provide more options for outputting vehicle functions.

[0070] According to the present invention, a hardware adjustment release configuration for the modified vehicle 1 is now specified. This allows the user 2 to use the vehicle function permanently to the greatest extent possible. For example, adapted program code can be implemented to control multiple newly installed light bars to output colored and dynamic light patterns.

[0071] There are typically several methods for adjusting the release configuration. One variant uses a so-called blockchain oracle, which is capable of altering the metadata allocated to non-fungible tokens (NFTs) after generation (see [link]). Figures 2 to 4 To this end, blockchain oracle 6 forms an interface between blockchain 10, used for executing the exchange of corresponding non-fungible tokens (NFTs), and so-called off-chain resources 11. Off-chain resources 11 are arbitrary resources that operate outside of blockchain 10, such as internet servers. Central computing device 3 can also be such an off-chain resource 11.

[0072] Figure 2 The general structure of a non-fungible token (NFT) is shown. A NFT contains metadata 7, which can be stored entirely or partially on-chain and / or off-chain. Metadata 7 can contain first content 12.1 and second content 12.2. For example, first content 12.1 is public content, and second content 12.2 is private content, represented by a padlock icon. Here, the corresponding content, or a portion of content 12.1, 12.2, constitutes the digital asset 13 allocated to the NFT. Here, it can be, for example, video clips, audio files, images, etc. Specifically, the public content, i.e., first content 12.1, is stored on a decentralized network storage 5.2, such as the so-called IPFS. A distributed peer-to-peer network is used to manage the blockchain 10 and thus the NFTs. Figure 2 The box representing non-fungible tokens (NFTs) is also connected to the corresponding decentralized web storage 5.2. Furthermore, decentralized web storage 5.2 here represents so-called Web3 applications.

[0073] Preferably, the first content 12.1 contains only sample files that do not allow for a complete reconstruction of the release configuration. The second content 12.2, i.e., private content, is preferably stored on a centralized network system 5.1. In particular, the centralized network storage 5.1 is cryptographically encrypted and therefore not publicly accessible. Furthermore, the centralized network storage 5.1 here also represents a so-called Web2 application. Specifically, the second content 12.2 is modifiable, while the first content 12.1 is immutable, but can be supplemented.

[0074] If a new generation of vehicles or hardware configuration changes, the vehicle manufacturer adjusts and releases the configuration for the changed hardware. The new content is then imported into the corresponding network storage devices 5.1 and 5.2. Thus, when switching vehicles or changing hardware, the modified content can be downloaded from the corresponding vehicle. Since metadata 7 and the already saved first content 12.1 are generally unchangeable, it is preferable to adjust the second content 12.2 for this purpose, which is still addressable through references included in metadata 7. For example, metadata 7 may contain multiple references for different program versions, where the reference for the newer program version initially points to empty storage areas in second content 12.2 or centralized network storage device 5.1 that are still free. When the vehicle manufacturer generates a new program version for the adapted hardware, these storage areas are populated and can be retrieved accordingly.

[0075] Figure 3 A possible implementation using so-called dynamic NFTs (dNFTs) in conjunction with the blockchain oracle 6 is demonstrated. The blockchain oracle 6 connects to a central computing device 3 and off-chain resources 11 to obtain information from the outside world. Based on this information, changes can be input into the metadata 7 of the dynamic NFT (dNFT) by the blockchain oracle 6. For example, the blockchain oracle 6 can query a vehicle manufacturer whether a new corresponding release configuration is available and when it will be available. Furthermore, the blockchain oracle 6 obtains information from the corresponding vehicle 1 indicating the specific hardware installed and compares this information with the release configuration provided by the vehicle manufacturer. Here, the metadata 7 is specifically stored on a centralized network storage 5.1, however, in an unencrypted and therefore publicly viewable form. The metadata 7 also references content 12, which includes, for example, example images, video materials, and image and audio materials of the vehicle model activated by user 2.

[0076] Specifically, the content 12 stored on the decentralized network storage 5.2 is immutable. To change the release configuration, the vehicle manufacturer supplements new program code into the decentralized network storage 5.2. The blockchain oracle 6 modifies the metadata 7 to update the saved references to the corresponding data, thereby addressing the supplemented program code.

[0077] The process is as follows: First, the hardware of vehicle 1 is modified. The vehicle manufacturer correspondingly changes the release configuration and uploads the modified release configuration to the decentralized network storage 5.2. Blockchain oracle 6 may have subscribed to a service from the vehicle manufacturer that specifies the transmission of corresponding information from central computing device 3 to blockchain oracle 6 upon the release configuration change. Subsequently, blockchain oracle 6 can adjust the reference to decentralized network storage 5.2 contained in metadata 7 according to the manufacturer's specifications. This allows vehicle 1 to address the changed storage location by reading metadata 7 and download its latest release configuration.

[0078] Furthermore, here, other information can be considered via the corresponding off-chain resource 11 to adjust the release configuration, so the light pattern can preferably be designed as blue, for example, on rainy days.

[0079] Figure 4 An alternative implementation using static non-fungible tokens (NFTs) is demonstrated. Here, the NFT includes an API and program code 8, which enables the corresponding onboard computing unit to automatically generate an adjusted release configuration within the vehicle itself. The required information can be reloaded from external sources via the API. Specifically, program code 8 is based on the use of generative artificial intelligence. Here, for example, public example images, as well as design data for images, videos, and audio, are stored as content 12 on a decentralized network storage 5.2 in the form of so-called container mirrors.

[0080] Here, considering the API, the information provided by off-chain resource 11 can also flow into the vehicle to release the configuration generation process (not shown).

[0081] The process is as follows: First, a new generation of vehicles or new hardware can be provided. When the hardware of vehicle 1 is changed, software or program code 8 described by a non-fungible token (NFT) will be downloaded into vehicle 1. Then, program code 8 is executed in vehicle 1, thus generating the modified release configuration.

Claims

1. A method for unlocking vehicle functions, wherein, The vehicle functions are provided by the hardware of the vehicle (1), which is configured by software, and wherein the vehicle functions are provided by the hardware when the hardware is configured according to the release configuration. Its features are, - The user (2) of the vehicle (1) logs into the central computing device (3) using a user account; - The user (2) binds his / her wallet (4) to the user account; - The central computing device (3) initiates the generation of nonfungible tokens, wherein the release configuration is allocated as digital assets (13) to the nonfungible tokens; - The central computing device (3) prompts the distribution of the nonfungible token to the user's (2) wallet (4). - The central computing device (3) reads the non-fungible tokens stored in the wallet (4); - The central computing device (3) obtains the corresponding release configuration for the non-fungible tokens stored in the wallet (4) and transmits it to the vehicle (1). - Modify the hardware of vehicle (1) or vehicle (1) itself; - Adjust the release configuration according to the changed hardware; and - The adjusted release configuration is used in the vehicle (1).

2. The method according to claim 1, Its features are, -The central computing device (3) stores the release configuration adjusted for different hardware on a centralized network storage (5.1) or a decentralized network storage (5.2); - The nonfungible token is generated in the form of a dynamic nonfungible token (dNFT); - The central computing device (3) transmits vehicle architecture information to the blockchain oracle (6), wherein the vehicle architecture information describes the hardware of the user's (2) vehicle (1); - The blockchain oracle (6) adjusts the metadata (7) of the dynamic non-fungible token (dNFT) to allocate the release configuration adjusted for the vehicle architecture information as a digital asset (13) to the dynamic NFT (dNFT); and - The vehicle (1) retrieves the adjusted release configuration from the network memory (5.1, 5.2).

3. The method according to claim 2, Its features are, The central computing device (3) executes a release configuration tailored to different hardware in a manner specific to third-party information, and the blockchain oracle (6) obtains third-party information when adjusting the metadata (7) and takes the third-party information into account when adjusting the metadata (7).

4. The method according to claim 1, Its features are, When generating the nonfungible token, the central computing device (3) writes program code (8) into the metadata (7) of the nonfungible token and generates a release configuration in the vehicle (1) by executing the program code by the vehicle computing unit, wherein the computing unit adjusts the release configuration according to the current hardware while taking the program code into account.

5. The method according to claim 4, Its features are, The metadata (7) of the non-fungible token is stored on the decentralized network storage (5.2).

6. The method according to claim 4 or 5, Its features are, The metadata (7) defines an application programming interface (API) via which the computing unit obtains the data required to generate the release configuration from a centralized network storage (5.1) and / or a decentralized network storage (5.2).

7. The method according to claim 6, Its features are, The data describes third-party information.

8. The method according to any one of claims 4 to 7, Its features are, The computing unit uses generative AI to generate the release configuration.

9. An information technology system comprising a central computing device (3) and a vehicle (1). Its features are, The central computing device (3) and the vehicle (1) are configured to perform the method according to any one of claims 1 to 8.

Images