Tire pass

Abstract

Disclosed is an apparatus for generating a tire pass, the apparatus comprising: one or more compute nodes; and one or more computer-readable media having computer-executable instructions thereon, the computer-executable instructions being configured to, when executed by the one or more compute nodes, execute the one or more compute nodes on the one or more compute nodes, and execute the one or more compute nodes on the one or more compute nodes. Causing the device to perform the following steps:-receiving a request for providing a decentralized identifier associated with the tire data and the data owner; -in response to the request, providing the decentralized identifier and generating the tire pass, the tire pass comprising the decentralized identifier and data relating to the tire data; -providing the tire pass for access to a data consumption service under or controlled by a data provision service associated with the data owner.

Description

Technical Field

[0001] The present invention relates to the field of sustainability, in particular to the field of processing used tires. The present disclosure relates to an apparatus for generating a tire pass, a computer-implemented method for generating a tire pass, a method for using a tire pass and a computer program element. Background Art

[0002] Vehicle tires are designed to withstand numerous stresses during their use and therefore consist of a highly complex mixture of materials. Due to these stresses, vehicle tires can only be used for a limited time. Consequently, tires are regularly disposed of, resulting in a significant accumulation of tire waste. Tire recycling rates remain low because they are made from disparate materials that must be separated.

[0003] In order to reuse scrap tires, different methods can be applied, such as re-grooving, retreading or recycling. Recycling allows the recovery of rubber and fillers. This recycled material can be used to produce new tires or other products. In this way, the tire material can be used multiple times and the circularity of the material flow can be achieved. In order to improve the processing of old tires, such as the reuse and recycling of old tires, standardized information about the old tires to be reused or recycled is needed. This data can be provided, for example, via the International Material Data System (IMDS) used in the automotive supply chain. This system allows data from the entire automotive supply chain to be collected. Participants in the automotive supply chain register for the IMDS service and maintain product entries in a central database provided and hosted by a third-party provider.

[0004] Data in systems like IMDS is static, prone to errors, and difficult to process and maintain. Due to the highly specific and centralized nature of these systems, exchanging and sharing tire data is laborious. Therefore, there is a need to simplify tire data exchange and sharing to increase the reuse and recycling rates of used tires. Summary of the Invention

[0005] In one aspect, an apparatus for generating a tire pass associated with a tire is disclosed, the apparatus comprising: one or more computing nodes; and one or more computer-readable media having computer-executable instructions thereon, the computer-executable instructions being configured to, when executed by the one or more computing nodes, cause the apparatus to perform the following steps:

[0006] - receiving a request for providing a decentralized identifier associated with a data owner and tire data associated with the tire,

[0007] - in response to the request, generating the tire pass, the tire pass comprising the decentralized identifier and data related to the tire data,

[0008] - providing the Tire Pass for access by a data consuming service under or controlled by a data providing service associated with the data owner.

[0009] In one aspect, an apparatus for generating a tire pass associated with a tire is disclosed, the apparatus comprising: one or more computing nodes; and one or more computer-readable media having computer-executable instructions thereon, the computer-executable instructions being configured to, when executed by the one or more computing nodes, cause the apparatus to perform the following steps:

[0010] - receiving a request for providing a decentralized identifier associated with a data owner and at least a portion of tire data associated with the tire,

[0011] - in response to the request, generating the tire pass, the tire pass comprising the decentralized identifier and data related to at least a portion of the tire data,

[0012] - providing the Tire Pass for access by a data consuming service under or controlled by a data providing service associated with the data owner.

[0013] In one aspect, an apparatus for generating a tire pass associated with a tire is disclosed, the apparatus comprising: one or more computing nodes; and one or more computer-readable media having computer-executable instructions thereon, the computer-executable instructions being configured to, when executed by the one or more computing nodes, cause the apparatus to perform the following steps:

[0014] - providing a decentralized identifier associated with the data owner and the tire data associated with that tire,

[0015] - generating the tire pass, the tire pass comprising the decentralized identifier and data related to the tire data,

[0016] -Provide the Tire Pass for access by data consuming services controlled by the data providing service associated with the data owner.

[0017] In one aspect, an apparatus for generating a tire pass associated with a tire, the tire pass including, inter alia, a decentralized identifier associated with tire data and data related to the tire data associated with the tire, is disclosed. The apparatus comprises: one or more computing nodes; and one or more computer-readable media having computer-executable instructions thereon, the computer-executable instructions being configured to, when executed by the one or more computing nodes, cause the apparatus to perform the following steps:

[0018] - receiving a request for providing a decentralized identifier associated with a data owner and tire data associated with the tire;

[0019] - in response to the request, providing the decentralized identifier and generating the tire passport, the tire passport comprising the decentralized identifier and data related to the tire data;

[0020] - providing the tire pass for access by a data consumption service controlled by or under the control of a data providing service associated with the data owner, in particular, wherein the data providing service includes computer executable instructions for providing and / or processing tire data associated with the data owner (e.g. for access and / or processing by the data consumption service).

[0021] In one aspect, an apparatus for generating a tire pass associated with a tire, the tire pass including, inter alia, a decentralized identifier associated with tire data and data related to the tire data associated with the tire, is disclosed. The apparatus comprises: one or more computing nodes; and one or more computer-readable media having computer-executable instructions thereon, the computer-executable instructions being configured to, when executed by the one or more computing nodes, cause the apparatus to perform the following steps:

[0022] - providing a decentralized identifier associated with the data owner and the tire data associated with the tire;

[0023] - generating the tire comprising the decentralized identifier and data related to the tire data,

[0024] - providing the tire pass for access by a data consumption service controlled by or under the control of a data providing service associated with the data owner, in particular, wherein the data providing service includes computer executable instructions for providing and / or processing tire data associated with the data owner (e.g. for access and / or processing by the data consumption service).

[0025] In another aspect, a computer-implemented method for generating a tire pass associated with a tire is disclosed, the method comprising the steps of:

[0026] - receiving a request for providing a decentralized identifier associated with a data owner and tire data associated with the tire,

[0027] - in response to the request, generating the tire, the tire comprising the decentralized identifier and data related to the tire data,

[0028] -Provide the Tire Pass for access by a data consuming service controlled by a data providing service associated with the data owner.

[0029] In another aspect, a computer-implemented method for generating a tire pass associated with a tire is disclosed, the method comprising the steps of:

[0030] - providing a decentralized identifier associated with the data owner and the tire data associated with that tire,

[0031] - generating the tire pass, the tire pass comprising the decentralized identifier and data related to the tire data,

[0032] -Provide the Tire Pass for access by a data consuming service controlled by a data providing service associated with the data owner.

[0033] In yet another aspect, a computer-implemented method is disclosed for using a tire pass to preferably determine characteristics and / or treatments of a tire associated with the tire pass, the method comprising the steps of:

[0034] - receiving a request for access to tire data associated with a decentralized identifier of a tire passport generated according to the method disclosed herein or by the apparatus disclosed herein,

[0035] - optionally authenticating and / or authorizing the request for access to the tire data,

[0036] - optionally based on the authentication and / or authorization, providing access rights to tire data associated with the decentralized identifier of the tire passport.

[0037] In yet another aspect, a computer-implemented method for monitoring at least one tire characteristic critical to reuse and / or recycling of the tire or components thereof is disclosed, the method comprising the steps of:

[0038] - collecting tire data of the tire or its component(s) related to the production of the tire or its components, in particular tire data related to characteristics that are critical for the reuse and / or recycling of the tire or its components, wherein the collected tire data comprises data associated with one or more production inputs used to produce the tire or its components;

[0039] - optionally, collecting tire data related to the use of the tire, in particular tire data related to characteristics that are critical for the reuse and / or recycling of the tire or its components;

[0040] - providing one or more decentralized identifiers associated with the tire or its component(s) and one or more decentralized identifiers associated with the one or more production inputs;

[0041] - generating at least one data set comprising at least a portion of the collected tire data and optionally a relationship data set specifying relationships between the provided decentralized identifiers;

[0042] - generating one or more access elements comprising one or more decentralized identifiers associated with the tire or its component(s) and access data related to at least one of the generated data sets, and optionally one or more relationship access elements comprising one or more decentralized identifiers associated with the tire or its component(s) and access data related to the generated relationship data sets;

[0043] - providing the one or more access elements to a decentralized network for access to the data set(s) by one or more data consuming network nodes of the decentralized network under the control of a data providing network node.

[0044] In yet another aspect, an apparatus for monitoring at least one tire characteristic critical to reuse and / or recycling of a tire or a component thereof is disclosed, the apparatus comprising:

[0045] - a data collection interface, which is configured to

[0046] collecting tire data of the tire or its component(s) related to the production of the tire or its component(s), in particular tire data related to characteristics that are critical for reuse and / or recycling of the tire or its component(s), wherein the collected tire data comprises data associated with one or more production inputs used to produce the tire or its component(s), and

[0047] o Optionally, collecting tire data related to the use of the tire, in particular tire data related to characteristics that are critical for reuse and / or recycling of the tire or its components;

[0048] - a decentralized identifier provider interface configured to provide one or more decentralized identifiers associated with the tire or its component(s) and one or more decentralized identifiers associated with the one or more production inputs;

[0049] - a data set generator configured to generate at least one data set comprising at least a portion of the collected tire data and optionally a relationship data set specifying relationships between the provided decentralized identifiers;

[0050] an access element generator configured to generate one or more access elements comprising one or more decentralized identifiers associated with the tire or its component(s) and access data related to at least one of the generated data sets, and optionally one or more relationship access elements comprising one or more decentralized identifiers associated with the tire or its component(s) and access data related to the generated relationship data sets;

[0051] - a decentralized network interface configured to provide the one or more access elements to a decentralized network for access to the data set(s) by one or more data consuming network nodes of the decentralized network under the control of a data providing network node.

[0052] In yet another aspect, a computer-implemented method for accessing at least one tire characteristic critical to tire reuse and / or recycling is disclosed, the method comprising the steps of:

[0053] - Provide a decentralized identifier associated with the tire or its components to be recycled or reused;

[0054] - collecting access data related to a decentralized identifier associated with a tire or a component thereof based on one or more access elements generated and / or provided according to the method disclosed herein or by the device disclosed herein, in particular recursively collecting access data at each production stage of a tire production chain and / or a tire use chain, wherein the recursive collection is based on one or more relational data sets provided by one or more participants of the tire production chain;

[0055] - requesting access rights to tire data from one or more participants of the tire production chain and / or the tire use chain based on the collected access data, in particular recursively requesting access rights to tire data from one or more participants (in particular each participant) of the tire production chain and / or the tire use chain based on the collected access data.

[0056] In yet another aspect, an apparatus for accessing at least one tire characteristic critical to tire reuse and / or recycling is disclosed, the apparatus comprising:

[0057] - an identifier providing interface configured to provide a decentralized identifier associated with a tire or component thereof to be recycled or reused;

[0058] an access data retriever configured to collect access data related to a decentralized identifier associated with a tire or a component thereof, based on one or more access elements generated and / or provided according to the method disclosed herein or by the apparatus disclosed herein, in particular to collect access data recursively at each production stage of a tire production chain and / or a tire use chain, wherein the recursive collection is based on one or more relational data sets provided by one or more participants of the tire production chain;

[0059] an access requester configured to request access rights to tire data from one or more participants of the tire production chain and / or the tire use chain based on the collected access data, in particular to recursively request access rights to tire data from one or more participants (in particular each participant) of the tire production chain and / or the tire use chain based on the collected access data.

[0060] A tire passport generated for a tire according to the methods set forth herein or by the apparatus set forth herein is used to determine the use of characteristics and / or treatments of the tire associated with the tire passport.

[0061] In yet another aspect, a tire associated with a tire passport is disclosed, wherein the tire passport, including a decentralized identifier and data related to tire data, is generated for the tire according to the method or by the apparatus set forth herein.

[0062] In yet another aspect, a system is disclosed that includes a tire associated with a tire passport, wherein the tire passport including a decentralized identifier and data related to tire data is generated for the tire according to the method or by the apparatus set forth herein.

[0063] In yet another aspect, a tire passport comprising a decentralized identifier and data related to tire data is disclosed, wherein the tire passport is generated for a tire according to a method or by an apparatus as set forth herein.

[0064] On the other hand, a computer element with instructions is disclosed, in particular a computer program product or a computer-readable medium, which, when executed on one or more computing nodes, is configured to perform the steps of any of the methods disclosed herein or to be performed by the apparatus disclosed herein.

[0065] Any disclosure and embodiment described herein may relate to the methods, devices, systems, tires, tire passes, uses, and computer elements listed above or below, and vice versa. The benefits provided by any embodiment and example are also applicable to all other embodiments and examples.

[0066] The methods, devices, systems, tires, tire passes, uses, and computer elements disclosed herein provide an efficient, secure, and robust way to share or exchange tire data between different participating nodes in the tire value chain. This allows, for example, the use of tire data and / or data related to the production and / or use of tires or their components to determine the appropriate treatment for used tires, thereby increasing the reuse and / or recycling rates of used tires. Appropriate treatment can be determined based on access. Specifically, tire data can be securely exchanged and shared under the sovereignty of the data owner by a) attaching a decentralized identifier to the data owner and the associated tire data, and b) providing access rights through a data consumption service controlled by a data providing service associated with the data owner. Thus, the data owner can control access to tire data by participating nodes or data consumption services in the decentralized network. This allows for streamlined and customizable data sharing or exchange across the entire tire ecosystem, including tire manufacturers, vehicle manufacturers, tire distributors, tire shops, vehicle owners, vehicle owners, vehicle renters, tire collectors, tire retreaders, and tire recyclers. This enables more reliable and efficient processing of tires and end-of-life tires by upstream participants in the tire ecosystem, while maintaining ownership of the tire data by the respective data owners. By directly combining tire-related data with decentralized identifiers and, optionally, one or more authentication mechanisms, more reliable and secure data sharing and exchange can be provided. By further including one or more authorization mechanisms, data sharing or exchange can be performed in a more flexible manner, enabling multiple data-consuming services from different participants in the tire ecosystem to access tire data. Furthermore, by making data related to the production of tires or their components and / or data related to the use of tires (e.g., characteristic data) accessible across the tire ecosystem's participants, more efficient and reliable monitoring of characteristics critical to recycling and / or reuse can be ensured through controlled and targeted access to such data. This monitoring concept allows for reliable monitoring of characteristics critical to tire recycling and / or reuse.

[0067] In particular, by collecting characteristic data during the production phase of a tire or its components and / or by collecting characteristic data during the tire's use and providing access to such data via an access element over a decentralized network, it is possible to share such characteristic data among participants in a tire chain or cycle. Furthermore, in particular, by using a relational dataset that specifies the relationship between production input(s) and production output(s) for each production step of the tire production chain and is stored decentralized for each participant in the tire chain or cycle, it is possible to recursively reconstruct a bill of materials for only those portions of the characteristic data that are relevant to the reuse or recycling process. Furthermore, in particular, by allowing the relevant data to be provided only to selected participants (such as recyclers and / or reusers), it is possible to provide tire producers and other participants in the tire production chain with the desired control over sensitive tire information. Furthermore, in particular, by providing such data related to characteristics that are critical for recycling and / or reuse, it is possible to more specifically monitor such characteristics and, therefore, determine appropriate reuse and / or recycling processes, thereby increasing the reuse and / or recycling of used tires.

[0068] By providing relational access elements associated with decentralized identifiers and access data for each stage of the production chain, the depth of the characteristics or characteristic data obtained via the decentralized network can be enhanced without having to disclose the complete bill of materials. Through the relational access elements, (multiple) corresponding inputs with (multiple) outputs can be accessed in a controlled and targeted manner according to the participants of the production chain and / or recycling chain and / or reuse chain. In this way, the reuse and / or recycling process that matches the characteristic data accessed via the decentralized network can be determined. This also allows to ensure a higher quality of the tires produced by the retreading and / or recycling operations. The higher quality of the recyclate allows this recyclate to be fed into the chemical production chain, because the negative impact on the production equipment during the production of chemical products due to the presence of critical substances in the recyclate can be avoided.

[0069] The following is an overview of embodiments of the present disclosure by way of examples. It should be understood that the present disclosure is not limited to the embodiments and / or examples.

[0070] In one embodiment, a decentralized identifier may include any unique identifier uniquely associated with the data owner and the tire data. A decentralized identifier may include any unique identifier uniquely associated with the manufacturer of a tire or its components and the tire or its components. A decentralized identifier may include one or more universally unique identifiers (UUIDs) and / or digital identifiers (DIDs). A decentralized identifier may be associated with a digital twin of a tire, which includes the tire data. A decentralized identifier may be associated with the physical entity of the tire or its components. Any combination of UUIDs and DIDs is possible. A decentralized identifier may be issued by a centralized or decentralized identity issuing authority. A decentralized identifier may be generated by or on behalf of the data owner. A decentralized identifier may be generated by or on behalf of the manufacturer of a tire or its components. A decentralized identifier may include one or more identifiers used in a decentralized network and allowing data exchange via the decentralized network. Data exchange may include discovering decentralized identifiers of participating nodes of the decentralized network, authenticating participating nodes of the decentralized network, and / or authorizing data transmission via peer-to-peer communication between participating nodes of the decentralized network. Decentralized identifiers can be associated with any participant in the tire ecosystem, including raw material suppliers, intermediate product manufacturers, tire manufacturers, vehicle manufacturers, tire distributors, tire workshops, vehicle owners, vehicle owners, vehicle rental companies, tire collectors, and tire recyclers. Decentralized identifiers can be associated with a machine, system, or device used to produce or recycle tires, or with a collection of such machine(s), device(s), and / or system(s). An identifier element can be associated with or connected to a tire or its component. At least during the production of a tire or its component, an identifier element can be associated with or connected to a tire or its component. Through the identifier element, a digital twin of a tire or its component can be accessed via a decentralized network. An identifier element can be uniquely associated with a tire or its component. An identifier element can be uniquely associated with a decentralized identifier(s) associated with the tire or its component. Decentralized identifier(s) can be uniquely associated with a tire or component. In this way, tire data or characteristic data can be provided for each tire / component or for individual tires / components. A decentralized identifier can be a digital identifier for or for a decentralized network. A decentralized identifier can be a digital identifier provided to a decentralized network and its participating nodes. Thus, such a decentralized identifier can represent the physical entity of a tire or its components within the decentralized network, and participating nodes can interpret the decentralized identifier's relationship to the physical entity of the tire or its components. The decentralized identifier can include authentication information. Through the decentralized identifier and its unique association with the data owner and the tire data, access to tire data can be controlled by the data owner.Through decentralized identifiers and their unique association with the data owner and the data, access to the data can be controlled by the data owner. This contrasts with centralized institutional solutions, where identifiers are provided by a centralized authority and access to the data is controlled by that centralized authority. In this context, decentralized means that the data owner controls the use of the identifiers at the implementation level.

[0071] In an embodiment, the tire pass may further include a public key of the data owner and / or a tire identifier associated with the tire. The tire identifier may include a batch number, tire name, tire ID, part number, lot number, or a combination thereof. The lot number may be assigned to the tire at the time of production or after production. The tire identifier allows for unique identification of the physical entity of the corresponding tire, thereby linking all data associated with the identifier (e.g., tire data and decentralized identifier) ​​to the physical entity of the tire.

[0072] In an embodiment, the tire can be a vehicle tire. The vehicle can be a car, such as a sedan, van, minivan, bus, SUV (sport utility vehicle); a truck; a van, a semi-trailer truck; a tractor; a motorcycle; a trailer; an ATV (all-terrain vehicle); a pickup truck; a heavy-duty truck, such as a bulldozer, a mobile crane, and an earth-moving truck; an airplane; and other modes of transportation that are typically equipped with one or more tires. The tire can be produced from chemical products. The chemical products can be chemical raw materials or intermediate chemical products. The chemical raw materials can include water glass and monomers for producing rubber, such as ethylene, propylene, butadiene, styrene, and polyisobutylene. The intermediate chemical products can include rubber (such as natural rubber and / or synthetic rubber), oil, steel, fillers (such as carbon black and silica), polymers, tackifiers, antioxidants, accelerators, and antiozonants. The tire can include a synthetic rubber inner liner. The tire can include a layer (also called a ply) above the inner liner that includes a thin fireproof wire or cable incorporated into the rubber. The tire may include a layer above the plies (also called a carcass ply) that includes thin steel cables incorporated into the rubber. The tire may include a layer above the carcass ply (also called a cap ply) that includes reinforced nylon-based cables embedded in the rubber layer. The tire may include bead wires at the edges of the tire that include or consist of steel. The tire may include a rubber tread and a rubber sidewall. The rubber tread may include a pattern. The tire may be produced by a production process that includes one or more production steps. The tire may be used throughout the life of the tire. The life of the tire may be extended through a recycling process. Recycling may include retreading or re-treading to extend the life of the tire. Re-treading may include carving a second tread layer into an old tire when the first tread layer has worn due to use of the tire. Retreading may include applying a new tread to the tire to extend its life.

[0073] In embodiments, the components may be chemical constituents or discrete components of the tire.

[0074] In an embodiment, tire data may be associated with a tire. Tire data may include data related to the characteristics of the tire and / or data related to the use of the tire. Such characteristics may be static or dynamic. Static characteristics may be characteristics that remain constant over time, such as EU label information, production date, etc. Dynamic characteristics may be characteristics that change over time, such as mileage, tire age, or tire weight. Data related to tire characteristics may include EU label information, tire specifications (such as tire width, aspect ratio, construction, rim diameter, load index, speed rating, and usage conditions), tire weight, raw materials used to produce the tire, tire production data, tire age, and / or approved uses. Data related to tire use may include mileage, average lifespan determined based on actual tire usage distance and tire usage time, the type of vehicle to which the tire is attached, the manufacturer of the vehicle to which the tire is attached, tire wear, tire current weight, data regarding the workshop to which the tire was attached, microplastic loss to the environment, tire usage conditions, tire intended use, maintenance data, recycling data, and / or weather conditions during tire use. Intended uses may include long-distance use, urban transportation use, and freight service use. Data acquired during the use of the tire can be used to determine data related to the use of the tire. For example, the loss of microplastics in the environment can be determined based on the weight of a new tire and the current weight of a used tire. In another example, tire data may relate to or include characteristics of (multiple) chemical products associated with the use of (multiple) chemical products in producing the tire. Tire data may relate to (multiple) tire identifiers associated with the tire, performance data associated with (multiple) chemical products used to produce the tire, the use of (multiple) chemical products in producing the tire, or a combination thereof. Tire data may include application characteristics of tires produced with or from (multiple) chemical products. Tire data may be generated or collected before, during, or after the production of the tire. Tire data may be collected before, during, or after the life cycle of the tire. Tire data may be generated by any participant in the tire ecosystem, such as chemical product suppliers, tire manufacturers, vehicle manufacturers, tire dealers, users, owners, or lessors of vehicles to which the tires are attached, tire warehouse operators, retreading companies, collection centers, return points, and recycling facilities. Tire data may be associated with the tires produced. Tire data can be updated with data acquired during the use of the tire on a vehicle(s). For example, sensors can capture real-time (or near-real-time) data from the physical tire, such as during the use of the tire, and use this data to update the tire data. Data captured during the use of the tire can be added to the tire data. The tire data can be associated with the vehicle produced.Tire data may be associated with a characteristic of the chemical product(s) used to produce the tire or at least one characteristic related to the use of the chemical product(s) used to produce the tire. Tire data may include chemical composition data, emissions data, recycled content, biobased content, and / or production data. Tire data may be stored in a database owned by or associated with the data owner. Tire data may be stored in a database accessible to the data owner.

[0075] In an embodiment, data related to the production of a tire or its components may be collected by the manufacturer of the tire or its components during the production stage of the tire or its components. Data related to the production of the tire or its components may be collected in connection with the production of the tire or its components. Data related to the production of the tire or its components may be collected before, during, or after the production of the tire or its components. Data related to the production of the tire or its components may be collected at each production stage of the tire or its components. The production stage may include any production step in the material chain of the tire. For example, the production stage may include the production of monomers or rubber. Further, for example, the production stage may include the production of steel. Further, for example, the production stage may include the production of nylon, reinforced nylon, and / or polyester used as a lining. Further, for example, the production stage may include the production of rubber using monomers. Further, for example, production may include the production of tires or their components using rubber, steel, nylon, reinforced nylon, or polyester.

[0076] In an embodiment, recycled content data and / or biobased content data may include any data related to the recycled content or biobased content of a physical entity used to provide or manufacture a tire. Recycled content may include content associated with materials (such as pyrolysis oil) obtained by chemically recycling waste materials (such as tires or parts thereof) and used to provide or manufacture the physical entity of a tire.

[0077] In an embodiment, emissions data may include any data related to an environmental footprint. An environmental footprint may refer to a tire and its associated environmental footprint. An environmental footprint may be specific to a tire. For example, an environmental footprint may relate to the tire, the company that produces the tire, a process such as the tire manufacturing process, or the raw materials or base substances or chemical products used to produce the tire. Emissions data may include data related to the carbon footprint or product carbon footprint (PCF) of the tire. Emissions data may include data related to greenhouse gas emissions, such as those released during the production of the tire. Emissions data may include data related to greenhouse gas emissions. Greenhouse gas emissions may include emissions such as carbon dioxide (CO2), methane (CH4), nitrous oxide (N2O), hydrofluorocarbon (HFC), perfluorocarbon (PFC), sulfur hexafluoride (SF6), nitrogen trifluoride (NF3), combinations thereof, and other emissions. Emissions data may include data related to greenhouse gas emissions generated by an entity or company's own operations (production, power plants, and waste incineration). Scope 2 may include emissions generated by externally provided energy production. Scope 3 may include all other emissions generated along the tire value chain. Specifically, this can include greenhouse gas emissions from the materials used to produce the tire. The product carbon footprint (PCF) can be the sum of the greenhouse gas emissions and removals generated by the consecutive and interconnected process steps associated with a specific tire. Cradle-to-gate PCF can aggregate greenhouse gas emissions based on selected process steps: for example, from the extraction of resources to the time the tire leaves the company's factory gate. This type of PCF can be called a partial PCF. To achieve this aggregation, each company that provides tires can provide its Scope 1 and Scope 2 contributions to the PCF for each tire.

[0078] In an embodiment, the production data may include any data related to the production of the tire. The production data may include any data related to the production of tire components. The production data may include tire production data from the production of the tire. The production data may include component production data from the production of the tire components. The production data may include monitoring and / or control data associated with the production of the tire. The production data may include monitoring and / or control data associated with the production of the tire components. The production data may include measurement data related to the quality of the tire. The production data may include measurement data related to the quality of the tire components.

[0079] In embodiments, the characteristic data may relate to one or more characteristics of a tire, its components, or a used tire. These characteristics may be related, associated, or correspond to the previously mentioned tire data. Characteristic data related to the production of the tire or its components may correspond to the previously mentioned production data. As previously mentioned, characteristic data related to the use of the tire may correspond to tire data collected during the life of the tire.

[0080] In embodiments, the data owner may include any entity that generates tire data or a portion thereof. A data generation node may be coupled to an entity that owns the tire for which the tire data is generated. A data generation node may be coupled to an entity that produces the tire for which the tire data is generated. A data generation node may be coupled to an entity that produces or owns the vehicle to which the tire is attached. Tire data may be generated by a third-party entity on behalf of the entity that owns the tire for which the tire data is generated. Tire data may be generated by a third-party entity on behalf of the entity that produces the tire for which the tire data is generated. The data owner may be a tire manufacturer. The data owner may be a vehicle manufacturer. The data owner may be a vehicle owner. Tire data or a portion thereof may be accessible to the data owner. Thus, the data owner may directly or indirectly own the tire data or a portion thereof. The tire data or a portion thereof may be stored in a database of the data owner or in a database associated with the data owner. The tire data or a portion thereof may be stored in a database accessible to the data owner. The tire data or a portion thereof may be stored in a database of the data owner or in a database controlled by the data owner. The tire data or a portion thereof may be associated with the data owner. The data owner may be the owner of the tire data or a portion thereof. In this sense, a data owner is broadly interpreted as an entity that can access tire data or a portion thereof and control access to the tire data or a portion thereof through a decentralized network of data consumption services. Access to the tire data or a portion thereof can be controlled by the data owner via a data provision service via a decentralized identifier and its unique association with the data owner and the tire data or a portion thereof.

[0081] In an embodiment, the tire production chain may include any participant involved in the production of tires or their components. Such production may involve a production process. The tire production chain may include a production chain. The tire usage chain may include any participant involved in the use of tires, such as vehicle manufacturers and vehicle users.

[0082] In an embodiment, a tire usage chain may include any participant involved in the use of tires. Such use may involve the manufacture of products (such as vehicles) containing tires. Such use may involve the recycling and / or reuse processes associated with used tires. Such use may involve the manufacture of products and / or the recycling and / or reuse processes.

[0083] Key characteristics for recycling and / or reuse may be one or more characteristics of a tire. These key characteristics may hinder the recycling and / or reuse process. For example, these key characteristics may hinder the quality of recyclables produced by a recycling process performed on waste or scrap tires. In another example, these key characteristics may hinder the reuse of used tires, for example, preventing them from being reused due to the need for recycling, disposal, or incineration. In yet another example, these key characteristics may hinder the recycling of waste or scrap tires, requiring them to be disposed of or incinerated. Such characteristics may relate to the reuse process. For example, retreading operations may not be permitted for certain types of tires and / or may only be repeated a limited number of times on a single tire. Such characteristics may relate to substances present within the tire that are key to recycling and / or reuse. The key substance(s) for recycling may hinder the quality of recyclables produced by the recycling process. The key substance(s) for recycling may relate to the recycling process. The key substance(s) for recycling may relate to the use of the recyclables. The key substance(s) for recycling may relate to both the recycling process and the use of the recyclables. (Multiple) key substances for reuse may hinder reuse. Key substances for reuse may involve a reuse process. (Multiple) key substances for recycling and / or reuse may include substances specific to one or more recovery processes and / or one or more reuse processes. (Multiple) key substances for recycling may involve chemical or mechanical recovery processes. (Multiple) key substances for recycling may involve a specific thermal recovery process, such as a thermal recovery process for producing pyrolysis oil. (Multiple) key substances for recycling may include substances specific to one or more uses of recyclates produced by the recovery process. (Multiple) key substances for recycling may involve a chemical recovery process for producing recyclates for petrochemical processes. The petrochemical process may include at least one process that is configured to at least partially decompose saturated hydrocarbons into unsaturated hydrocarbons. Hydrocarbon recyclates can be produced by pyrolysis. Key substances for recycling may include sulfur, halogens, oxygen, phosphorus, metals and inorganic substances, such as aluminum, antimony, barium, chromium, calcium, copper, iron, potassium, sodium, lead, silicon, titanium, zinc, arsenic, mercury, nickel, vanadium or a combination thereof.

[0084] A tire or component(s) thereof may be associated with an access element of a decentralized network, the access element including access data associated with at least one generated dataset. The access element may be associated with one or more datasets including at least a portion of the collected tire data. The access element may be associated with one or more relationship datasets specifying relationships between the tire or component(s) thereof and the production input(s) used to produce the tire or component(s). The dataset(s) may be provided to the decentralized network via the corresponding access element. The dataset(s) may be provided by a decentralized network node associated with a dedicated storage device of a tire or component manufacturer. The access data may include a representation for accessing the dataset(s). The access element may further include authentication information. The access data may include a locator or pointer to a dedicated storage address associated with the tire or component manufacturer. The access data may include a locator or pointer to a dedicated storage device associated with a production participant in a production chain producing the tire or component and storing tire data related to the production of the tire or component(s). The access data may include one or more digital links to tire data, such as tire data related to characteristics critical to the reuse and / or recycling of the tire or component(s). The digital representation(s) may comprise a locator or pointer, such as an am url or uri, to a dedicated memory address associated with a production participant of a production chain producing tires or parts thereof and storing tire data related to the production of plastic articles or parts thereof.

[0085] In an embodiment, a decentralized network may include one or more decentralized network nodes configured to conduct data transactions. The decentralized network node(s) may be associated with participants in the tire ecosystem (particularly, the tire cycle). Data transactions may be based on a transaction protocol that includes authentication and / or authorization mechanisms. Based on the authentication and / or authorization mechanisms, a peer-to-peer network may be established between the decentralized network nodes. One or more authentication mechanisms may be associated with or linked to a decentralized identifier. The one or more authentication mechanisms associated with the decentralized identifier may be provided to the decentralized network node(s). The one or more authentication mechanisms associated with the decentralized identifier(s) may be accessible to the decentralized network node(s). A decentralized configuration allows for more efficient utilization of computing resources and strengthens each data owner's control over the decentralized network. The one or more decentralized identifiers may be uniquely associated with the physical entity of a produced tire or component thereof. Access elements may include one or more authentication mechanisms associated with the decentralized identifier(s) and access data. Access elements may involve one or more authorization mechanisms associated with the decentralized identifier(s) and one or more data sets. The one or more authorization mechanisms may include authorization rules that determine whether access to the one or more data sets is granted. One or more authorization mechanisms may be associated with a data providing network node associated with a tire or component producer.One or more authorization mechanisms may be provided for each production stage or each producer in the tire production chain.

[0086] In an embodiment, a data consumption service may include computer-executable instructions for accessing and / or processing data associated with a data owner (e.g., tire data). The data consumption service or (multiple) data consumption network nodes may be configured to request access rights to data stored in dedicated storage devices associated with (multiple) data providing network nodes. The data consumption network nodes may be associated with participants in the recycling or reuse chain of tires or their components, such as sorters or recyclers of tires or their components or retreaders of used tires. Data generated by producers of tires or their components at each production stage may be accessed by (multiple) data consumption network nodes upon authentication and / or authorization.

[0087] In embodiments, recycling may refer to any recovery operation by which waste tires, such as scrap tires (e.g., any tires that the owner has discarded, intends to discard, or is required to discard), are reprocessed into products, materials, or substances, whether for their original purpose or otherwise. Recycling may include sorting, collection, mechanical recovery, chemical recovery, solvent-based recovery, or any intermediate processing steps, such as separation or purification.

[0088] In embodiments, recycling may refer to any operation by which a reusable tire is reused for the same purpose for which it was intended. Recycling may include, for example, preparing the tire for reuse by retreading. Recycling may include collection, sorting, and retreading.

[0089] In an embodiment, a data providing service may include computer-executable instructions for providing and / or processing data associated with a data owner (such as tire data and / or characteristic data) for access and / or processing by a data consuming service. The data providing service or (multiple) data providing network nodes may be configured to provide access to data stored in a dedicated storage device associated with (multiple) corresponding data providing network nodes. The data providing network nodes may be associated with participants in the production chain of tires or their components, such as producers of tires or their components. The data generated by the producers of tires or their components at each production stage may be provided by the data providing network nodes to the decentralized network, in particular for access by (multiple) data consuming network nodes. Access to the data may be under the control of the data providing network nodes. The data providing network nodes may be configured to authenticate the data consuming network nodes and / or authorize the data consuming network nodes to access the tire data.

[0090] In an embodiment, the physical entity may relate to a physical embodiment of a tire.The physical entity may relate to a physical embodiment of a tire component.

[0091] In an embodiment, a processor may refer to a circuit configured to perform the basic operations of a computer or system, and / or generally refers to a device configured to perform calculations or logical operations. In particular, a processor or computer processor may be configured to process the basic instructions that drive a computer or system. The processor may be a semiconductor-based processor, a quantum processor, or any other type of processor configured to process instructions. As an example, a processor may be or may include a central processing unit ("CPU"). The processor may be a ("GPU") graphics processing unit, a ("TPU") tensor processing unit, a ("CISC") complex instruction set computing microprocessor, a reduced instruction set computing ("RISC") microprocessor, a very long instruction word ("VLIW") microprocessor, or a processor that implements other instruction sets or multiple processors that implement an instruction set combination. The processing device may also be one or more special processing devices, such as an application-specific integrated circuit ("ASIC"), a field programmable gate array ("FPGA"), a complex programmable logic device ("CPLD"), a digital signal processor ("DSP"), a network processor, etc. The methods, systems, and devices described herein can be implemented as software in a DSP, microcontroller, or any other auxiliary processor, or as hardware circuits in an ASIC, CPLD, or FPGA. It should be understood that the term processor can also refer to one or more processing devices, such as a distributed processing device system located on multiple computer systems (e.g., cloud computing), and is not limited to a single device unless otherwise specified. A processor can be viewed as a sub-portion of a processor, wherein this sub-portion executes the methods disclosed herein in the form of threads, containers, and / or virtual machines.

[0092] In an embodiment, a computing node may refer to any device or system that includes at least one physical, tangible processor and a physical, tangible memory capable of having computer-executable instructions executed by the processor. A computing node may be, for example, a handheld device, a production facility, a sensor, a monitoring system, a control system, an appliance, a laptop computer, a desktop computer, a mainframe, a data center, or even a device that is not traditionally considered a computing node, such as a wearable device (e.g., glasses, a watch, etc.). The memory may take any form and depends on the nature and form of the computing node.

[0093] In embodiments, distributed computing may be implemented. Distributed computing may refer to any computing that utilizes multiple computing resources. Such utilization may be achieved through virtualization of physical computing resources. One example of distributed computing is cloud computing. "Cloud computing" may refer to a model for enabling on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services). When a cloud computing environment is distributed, it may be distributed within an organization and / or internationally across multiple organizations. In embodiments, distributed computing may be implemented in a federated network.

[0094] In an embodiment, memory can refer to physical system memory, which can be volatile, non-volatile, or a combination thereof. Memory can include non-volatile mass storage, such as physical storage media. Memory can be a computer-readable storage medium (such as RAM, ROM, EEPROM, CD-ROM) or other optical disk storage, disk storage, or other magnetic storage devices, non-disk storage (such as solid state disk) or any other physical tangible storage medium, which can be used to store the desired program code device in the form of computer-executable instructions or data structures and can be accessed by a computing system. In addition, memory can be a computer-readable medium (also referred to as a transmission medium) that carries computer-executable instructions. Further, after arriving at various computing system components, the program code device in the form of computer-executable instructions or data structures can be automatically transferred from a transmission medium to a storage medium (vice versa). For example, the computer-executable instructions or data structures received by a network or data link can be buffered in the RAM in a network interface module (e.g., "NIC"), and then eventually transferred to the computing system RAM and / or the storage medium with lower volatility at the computing system. Thus, it should be understood that storage media can be included in computing components that also (or even primarily) utilize transmission media.

[0095] In an embodiment, a wireless communication protocol may be used. The wireless communication protocol may include any known network technology, such as GSM (Global System for Mobile Communications), GPRS (General Packet Radio Service), EDGE (Enhanced Data Rates for GSM Evolution), UMTS (Universal Mobile Telecommunications System) / HSPA (High Speed ​​Packet Access), LTE (Long Term Evolution) technology using standards such as 2G, 3G, 4G or 5G, and the wireless communication protocol may further include a wireless local area network (WLAN), such as Wireless Fidelity (Wi-Fi).

[0096] In one embodiment, the request for a decentralized identifier includes tire data and / or an owner or tire identifier associated with the data owner or tire, respectively. The owner / tire identifier can be a string identifier associated with the data owner's name or the tire's name. The owner or tire identifier can be provided by a physical identifier provider, such as a barcode, a tag such as an RFID tag, or a QR code. This communication can be accomplished via ad-hoc Wi-Fi, Bluetooth Low Energy (BLE) beacon, and / or NFC. Communication between wallet apps can be performed via any available communication channel, including but not limited to a web server, ad-hoc Wi-Fi, Bluetooth Low Energy (BLE) beacon signals, NFC, barcode or QR code scanning, etc. The generated tire pass can be associated with the tire data owner by including the owner identifier. The owner identifier can be used in data transactions, such as sharing or exchanging tire data. The owner identifier can be provided to a transaction manager. Providing the decentralized identifier and the data owner's owner identifier to a transaction manager or data consumption service simplifies tracking of data transactions. Any transaction in the data ecosystem can be associated with, for example, the unambiguous name of the data owner.

[0097] The request may further include an authentication mechanism (e.g., a public-private key pair) and / or an identifier associated with the entity providing the decentralized identifier. This allows the request to be routed to a specific decentralized identifier provider. The authentication mechanism may be retrieved from an authentication data store (e.g., a vault) based on the decentralized identifier being requested.

[0098] The request to provide a decentralized identifier may be associated with a tire production facility that produces the tire. The request to provide a decentralized identifier may be generated by a computing system (e.g., an operating system) of the tire production facility that produces the tire. The request may be triggered upon the occurrence of a predefined event. For example, a detector may detect the produced tire. Based on this detection, the computing device (e.g., an operating system) of the tire production facility may generate a request to provide a decentralized identifier. The generated request may be provided to a decentralized identifier generator included in the apparatus for generating a tire pass. In response to receiving the request, the decentralized identifier generator may generate a decentralized identifier and provide the generated decentralized identifier.

[0099] In one embodiment, a decentralized identifier is provided by a central node or one or more decentralized nodes. The decentralized identifier generated by the central node or one or more decentralized nodes can be provided to nodes that generate tire passes and / or digital access elements, as well as to at least one authentication data registry node, which is preferably accessible via a data provisioning service and / or a data consumption service. This enables customized data sharing or exchange related to tires and the tire value chain that uses them. In particular, the data provisioning service and / or the data consumption service can customize the data sharing or exchange protocol based on the anchoring of the decentralized identifier to tire data. The authentication data registry node can be a central registry node, such as a centralized file system, a centrally managed distributed database, and / or a centrally managed peer-to-peer network. A centralized configuration allows for greater control and standardization via a central node. The authentication data registry node can be a decentralized registry, such as a distributed ledger, a decentralized file system, a distributed database, and / or a peer-to-peer network. A decentralized configuration allows for more efficient utilization of computing resources and strengthens control over data owners. Furthermore, the decentralized configuration is independent of the centrally managed nodes, thereby increasing system reliability and flexibility.

[0100] In one embodiment, generating a tire pass includes providing a decentralized identifier associated with the physical entity of the tire. In this context, the physical entity may be a physical tire associated with the decentralized identifier. The decentralized identifier may be associated with the physical entity of the tire to which the tire data or tire pass is associated. For example, the decentralized identifier may be associated with the physical entity of the tire. The decentralized identifier may be associated with the tire via a physical identifier. The physical identifier may include or correspond to an identifier element contained within or attached to the tire. The physical identifier may refer to, for example, a tire identifier. The identifier element may include a passive or active element, such as a barcode, QR code, embossed code, or RFID tag. The decentralized identifier may be assigned to the physical identifier. Assignment may include generating a code embedded with the provided decentralized identifier. Assignment may include associating the provided decentralized identifier with the physical identifier of the tire. For example, the identifier element may be physically attached to or contained within the tire, wherein the identifier element may include or correspond to the physical identifier. Determining or obtaining the physical identifier may be considered to trigger the provision of the decentralized identifier and may also trigger the subsequent assignment between the physical identifier and the decentralized identifier. A decentralized identifier can be associated with the physical entity to which the tire is supplied and to which tire data is associated. For example, a decentralized identifier can be associated with the physical entity of the vehicle to which the tire is attached. A decentralized identifier can also be associated with more than one physical entity to which the tire is supplied and to which tire data is associated. Associating decentralized identifiers with different physical entities in the tire value chain allows for virtual tracking of tires throughout the tire value chain. This allows for tracking tires and their associated tire data, for example, until end of life or until recycling.

[0101] In one embodiment, the tire pass includes one or more authentication mechanisms associated with a decentralized identifier and tire data or a portion thereof. The authentication mechanism may directly or indirectly involve the decentralized identifier and data related to the tire data. In an example of an indirect relationship, the authentication mechanism may involve a certificate mechanism. For example, when a data consumption service makes an access request, a dynamic access token may be generated based on a certificate mechanism. Such a dynamic access token may be used to open a peer-to-peer communication channel between a data consumption service associated with the tire pass and a data provision service. The authentication mechanism may include a token (such as a private key and a public key infrastructure), a certificate mechanism, or a biometric mechanism (such as a fingerprint, facial recognition, or voice recognition, etc.). For example, a common public key certificate is an X.509 certificate. Through the authentication mechanism, access to the data consumption service can be controlled in a secure manner, and the integrity of the data provision service can be ensured. This makes data exchange or sharing more reliable, controllable, and secure.

[0102] One or more authentication mechanisms associated with decentralized identifiers generated by a central node or one or more decentralized nodes can be provided to the node generating the tire pass and at least one decentralized authentication data registry, which are preferably accessible to data provision services and / or data consumption services. The authentication data registry can be a centralized registry, such as a centralized file system, a centrally managed distributed database, and / or a centrally managed peer-to-peer network. A centralized configuration allows for greater control and standardization via a central node. The authentication data registry can be a decentralized registry, such as a distributed ledger, a decentralized file system, a distributed database, and / or a peer-to-peer network. A decentralized configuration allows for more efficient utilization of computing resources and increased control by data owners.

[0103] In one embodiment, a tire pass involves or includes one or more authorization mechanisms associated with a decentralized identifier and data related to tire data. The authorization mechanism may include (multiple) authorization rules containing data transaction instructions or data transaction agreements, such as data usage policies, smart data contracts, or more complex data processing instructions associated with data provision and / or data consumption services. Through the authorization mechanism, access to tire data or a portion thereof and the use of the data by data consumption services can be controlled in a secure manner. One or more authorization mechanisms associated with a decentralized identifier generated by a central node or one or more decentralized nodes can be provided to a node used to generate or process a tire pass or to access tire data or a portion thereof. In addition or alternatively, one or more authorization mechanisms can be provided to at least one centralized or decentralized authorization data registry, which is preferably accessible to the data provision service and / or data consumption service.

[0104] In one embodiment, one or more authorization mechanisms associated with decentralized identifiers generated by one or more decentralized nodes may be provided to a node that generates or processes tire passes and at least one of: a centralized file system, a centrally managed distributed database, a centrally managed peer-to-peer network, a distributed ledger, a decentralized file system, a distributed database, and / or a peer-to-peer network, preferably accessible to a data providing service and / or a data consuming service.

[0105] In one embodiment, the data related to tire data includes the tire data or a portion thereof. In one embodiment, the data related to tire data includes one or more digital representations pointing to the tire data or a portion thereof. In this context, pointing to means any network representation or address suitable for accessing the tire data or a portion thereof. Therefore, the digital representation can be considered access data, and a tire pass can represent a digital data structure that allows a third party to access the tire data or a portion thereof. The data related to tire data can include multiple digital representations pointing to different portions of the tire data. The data related to tire data can include multiple digital representations pointing to different portions of the tire data. These different portions may overlap at certain data points. The digital representation can include an access point to the tire data or a portion thereof, a link for accessing the tire data or a portion thereof, an endpoint for accessing the tire data or a portion thereof, or a service endpoint for accessing the tire data or a portion thereof. In this way, the tire data or a portion thereof can be maintained and controlled by the data owner. Providing access via the representation of the access point simplifies data validation, integrity checks, quality checks, and access control, as it eliminates the need to perform checks and access controls across multiple distributed data points. The tire data or a portion thereof can be stored in a database of the data owner or a database associated with the data owner. The tire data, or a portion thereof, may be stored in a database accessible to the data owner. A reference to the digital representation of the tire data, or a portion thereof, may refer to, or be associated with, any such database associated with or accessible to the data owner. To enhance security, a reference to the digital representation of the tire data, or a portion thereof, may indirectly refer to, or be associated with, any such database associated with or accessible to the data owner.

[0106] The digital representation(s) can be used in conjunction with a decentralized identifier to access tire data or a portion thereof. For example, a data consumption service can request tire data or a portion thereof using a decentralized identifier and the corresponding digital representation(s). Data related to the tire data can correspond to a DID document associated with or including a decentralized identifier (e.g., a DID), a digital representation(s) pointing to the tire data or a portion thereof, and a public key. The DID document or a portion thereof can be propagated to a distributed ledger. The DID document or a portion thereof can be used to retrieve the digital representation(s) using the DID, as described later.

[0107] In one embodiment, the tire data, or a portion thereof, may include the tire's manufacturer, tire identifier(s), data regarding the chemical materials used to produce the tire, labeling data, data regarding retreading, the tire's recycled content, the tire's biobased content, tire emissions data, data regarding hazardous chemical materials contained within the tire, tire specification data, data related to the tire's characteristics, data related to the tire's use, production data, or a combination thereof. The data related to the tire's characteristics, data related to the tire's use, and production data may include the data previously mentioned. The tire data may be updated with data acquired during the use of the tire as described above. Data acquired during the use of the tire may be added to the existing tire data, for example, using a decentralized identifier.

[0108] In one embodiment, tire data may include one or more categories of tire data. At least one category of tire data may include or be associated with regulatory data or tire data, such as labeling information and / or chemical safety data associated with the hazards of chemical materials used to produce the tire. Chemical safety data may be associated with the raw materials and chemicals used to produce the tire. At least one category of tire data may be associated with data related to the characteristics of the tire. At least one category of tire data may be associated with data related to the use of the tire. At least one category of tire data may be associated with production data. At least one category of tire data may be associated with lifespan data. This data may be updated accordingly to reflect the current status of the tire. For example, the number of kilometers driven may be updated to reflect the amount of tire use. Lifespan data may include data related to the use of the tire mentioned above. Lifespan data may be acquired by sensors within the tire and / or the vehicle in which the tire is mounted. Lifespan data may be calculated based on characteristic data (such as the original weight of the tire) and data acquired during the use of the tire. For example, the loss of microplastics to the environment during the use of the tire may be calculated based on the original weight of the tire and the current weight of the tire. At least one type of tire data may include emissions data, recycled content data, bio-based content data, and / or production data associated with the physical entity of the tire. The emissions data, recycled content data, bio-based content data, and / or production data may be associated with more than one raw material or chemical product (e.g., a raw material or chemical product used to manufacture a tire). The emissions data, recycled content data, bio-based content data, and / or production data may be associated with more than one raw material or chemical product (e.g., a raw material or chemical product used to manufacture multiple components to assemble a tire).

[0109] Access to tire data may be controlled based on the categories. At least one category of tire data may include, or may be associated with, access-restricted tire data associated with the physical entity of the tire. For example, emissions data, recycled content data, bio-based content data, production data, the composition of chemical materials used to produce the tire, or a combination thereof, may be access-restricted. Such access restrictions may be provided by an authorization mechanism. For example, the authorization mechanism may include rules specifying which data-consuming services are granted access rights and under which conditions. At least one category of tire data may include non-access-restricted tire data associated with the physical entity of the tire. For example, label information and / or chemical product safety data associated with the physical entity of the tire may not be access-restricted or may be non-access-restricted. Such access may be provided by an authorization mechanism. For example, the authorization mechanism may include rules specifying that certain regulatory data of the tire may be accessible.

[0110] In one embodiment, the tire pass further includes decentralized identifier(s) associated with the chemical materials or components used to produce the tire and / or decentralized identifier(s) associated with the production of the tire (referred to herein as second decentralized identifier(s)). The second decentralized identifier(s) may be included along with the relationship between the decentralized identifier associated with the tire and the decentralized identifier(s) of the chemical materials used to produce the tire and / or the decentralized identifier(s) associated with the production of the tire. The second decentralized identifier(s) may be used to generate a concatenation with the decentralized identifier of the tire pass (hereinafter referred to as the first decentralized identifier) ​​based on a relationship representation according to which the first digital identifier is associated with the second identifier(s). The relationship representation may be associated with a relationship between the tire and each chemical material used to produce the tire. The relationship representation may specify that the chemical material(s) may be used to produce the tire and / or that the tire may be produced using the chemical material(s). One or more hash values ​​may be generated based on the relationship representation. The hash value(s) may be generated based on the concatenation of the decentralized identifiers. The hash value(s) may be generated for the concatenation of the decentralized identifiers. (Multiple) hash values ​​can represent a concatenation of decentralized identifiers. The hash value can be generated based on data associated with the first decentralized identifier and the (multiple) second decentralized identifiers. The hash value can be generated based on a combined data set associated with the first decentralized identifier and the (multiple) second decentralized identifiers. By concatenating decentralized identifiers associated with the chemical materials used to produce the tire, the tire, and the recycling of the tire, the chemical materials involved in the production of the tire and the chemical materials generated by the recycling of the tire can be virtually tracked and traced. This allows the decentralized identifier associated with the tire to be linked to the decentralized identifier associated with the chemical materials used to produce the tire. Therefore, the relationship between the tire and the chemical materials used to produce the tire can be reflected in the tire pass.

[0111] The request for providing a decentralized identifier may include the second identifier(s). The request for providing a decentralized identifier may include tire data or a portion thereof. Based on the tire data or a portion thereof, data associated with the chemical material(s) used to produce the tire and / or data associated with the production of the tire may be determined and used to retrieve the corresponding second decentralized identifier(s).

[0112] The decentralized identifier associated with the chemical material used to produce the tire can be associated with chemical material data indicating whether the chemical material is virgin material or recycled material, environmental impact and / or the source of the chemical material. The decentralized identifier associated with (multiple) chemical materials can be determined based on a physical identifier attached to the chemical material packaging. The chemical material can be a raw material, including virgin material or recycled material. The raw material can include water glass and monomers for producing rubber, such as ethylene, propylene, butadiene, styrene and polyisobutylene. The chemical material can be an intermediate product manufactured by (multiple) raw materials and / or other (multiple) intermediate products. The intermediate product can include dispersants, tackifiers, polymers (such as rubber, natural rubber and polyamide), oil, steel, fabrics, fillers (such as carbon black and silica), antioxidants, accelerators and antiozonants. The tire can be produced from raw materials and / or intermediate products. Chemical materials can be used directly or indirectly to manufacture tires. That is, some chemical materials can be used to manufacture one or more intermediate products, and then manufacture tires based on these one or more intermediate products.

[0113] In an embodiment of a method for monitoring at least one tire characteristic critical for the reuse and / or recycling of tires or components, tire data is collected by participants in a tire production chain in connection with the production of tires or components thereof. Tire data associated with one or more production inputs used to produce the tires or components thereof, in particular, associated decentralized identifiers associated with the one or more production inputs, can be collected. Tire data associated with the one or more production inputs used to produce the tires or components thereof can be collected at each production stage in the tire production chain. Tire data associated with the one or more production inputs used to produce the tires or components thereof are collected for each production stage and / or for each participant in the tire production chain. By collecting input data, production input(s) can be associated with production output(s) at each tire production stage, enabling tracking of material flows across participants in the tire production chain. This also allows tracking of characteristics critical for recycling and / or reuse across participants in the tire production chain.

[0114] In an embodiment of the method for monitoring at least one tire characteristic critical for reuse and / or recycling of tires or components, a relationship access element is provided for accessing a relationship data set specifying a relationship between a tire or component thereof at a production stage of the tire or component thereof and one or more corresponding production inputs used in said production stage. One or more relationship access elements can be configured to access tire data from one or more participants in a tire production chain and / or a tire usage chain. One or more relationship access elements can be configured to allow one or more participants using the tire or component thereof to access tire data for each production stage of the tire production chain.

[0115] In an embodiment of a method for monitoring at least one tire characteristic critical for the reuse and / or recycling of tires or components, one or more access elements can be configured to recursively access tire data at each production stage of the tire production chain. The recursive access can be based on access data provided by one or more participants in the tire production chain. The access data can be provided to the decentralized network by one or more participants in the tire production chain and / or tire use chain (in particular, sorter(s), collector(s), and / or recycler system(s) and / or recycling system(s)). Tire data can be recursively accessed from one or more participants in the tire production chain (in particular, tire and tire component producer(s)) at each production stage of a tire or its components.

[0116] Thus, the generated dataset(s) can be accessed by one or more participants in the tire production chain or tire use chain (particularly chemical producer(s) and / or tire producer(s) and / or recycler(s)) via one or more access elements generated according to the methods disclosed herein. The dataset(s) can be accessed by one or more participants in the tire production chain (particularly tire and / or component producer(s)) at each stage of tire production or tire component production. The dataset(s) can be accessed from one or more participants in the tire use chain (particularly retreader(s) and / or recycler(s)) at each stage of tire production. The dataset(s) can be recursively accessed based on one or more relational access elements provided by one or more participants in the tire production chain or tire use chain (particularly tire or component producer(s)). One or more relational access elements provided to the decentralized network by one or more participants in the tire production chain (particularly tire or component producer(s)) can be recursively accessed by one or more participants in the tire use chain or production chain (particularly collectors, sorters, retreaders, and / or recyclers).

[0117] In an embodiment of a method for monitoring at least one tire characteristic critical to the reuse and / or recycling of tires or components, a relationship access element may involve authorization rules that provide access rights to a relationship dataset based on a decentralized participant identifier. The decentralized participant identifier may be associated with an entity operating a data-consuming network node requesting access to the relationship dataset. The decentralized participant identifier may be associated with a data-consuming network node associated with a recycling system that provides a decentralized identifier for a tire upon recycling. The decentralized participant identifier may also be associated with a data-consuming network node associated with a retreading system that provides a decentralized identifier for a tire upon retreading. In this way, access to sensitive data related to the bill of materials of a tire in a production chain, such as tire data related to characteristics critical to recycling and / or reuse, can be restricted to specific network nodes associated with data access, such as tire data related to characteristics critical to recycling and / or reuse, to control and / or monitor the recycling and / or reuse process. Furthermore, data access can facilitate the detection of critical characteristics, such as critical substances, for recycling and / or reuse by participants in the tire production chain.

[0118] In an embodiment of a method for monitoring at least one tire characteristic critical to the reuse and / or recycling of a tire or component, at least a portion of the generated dataset(s) relates to or specifies a characteristic critical to recycling and / or reusing the tire or component thereof through a chemical recycling process (e.g., to produce hydrocarbon recyclates for use in petrochemical processes). The generated dataset(s) may include recycling-critical substances associated with one or more recycling processes. The generated dataset(s) may further relate to the recycled content used to produce the tire or component thereof, the reuse or repair operation performed on the tire, the tire type, and / or the permitted reuse operation to be performed on the tire.

[0119] In an embodiment of a method for monitoring at least one tire characteristic critical to the reuse and / or recycling of tires or components, the generated dataset(s) relate to characteristics critical to the recycling, recyclate usage, and / or each decentralized participant identifier for each recycling or reuse process. The participant identifier can be associated with an entity operating a data-consuming network node requesting access to the dataset(s). A recycling process can be represented by a recycling process identifier. A reuse process can be represented by a reuse process identifier. Recyclate usage can be represented by a recyclate type. The decentralized participant identifier can be provided by the data-consuming network node requesting access to the corresponding dataset. The recycling or reuse process identifier and / or recyclate type can be provided by the data-consuming network node requesting access to the corresponding dataset. The recycling or reuse process identifier and / or recyclate type can be provided by a data-providing network node providing access rights to the corresponding dataset. The recycling or reuse process identifier and / or recyclate type can be provided by an authorization rule that associates the decentralized participant identifier associated with the data-consuming network node requesting access to the corresponding dataset with the recycling or reuse process identifier and / or recyclate type. The authorization rules may relate to one or more data sets related to characteristics key to recycling, recyclate usage, and / or each decentralized participant identifier for each recycling process. A recycling process may relate to a mechanical and / or chemical recycling process, including solvent-based recycling. Recyclate usage may relate to the reuse of recyclate produced by such a recycling process. Recyclate usage may relate to hydrocarbon recyclate for use in petrochemical or refining processes. The authorization rules may relate to one or more data sets related to characteristics key to reuse for each reuse process. A reuse process may relate to a refurbishment process or another reuse process.

[0120] In an embodiment of a method for monitoring at least one tire characteristic critical for reuse and / or recycling of tires or components, an access element is provided for accessing generated dataset(s) comprising the characteristic critical for recycling by one or more data-consuming network nodes associated with one or more recyclers performing one or more recycling processes based on a recycling process, recyclate usage, and / or participant identifier. The access element may involve authorization rules that provide access to the dataset(s) based on the recycling process, recyclate usage, and / or participant identifier. The access element may involve authorization rules that provide access to the dataset(s) related to the characteristic critical for recycling based on a decentralized participant identifier, a recycling process identifier associated with the decentralized participant identifier, and / or a recyclate type identifier associated with the decentralized participant identifier. The access element may involve authorization rules that provide access to the dataset(s) related to the characteristic critical for recycling to selected participants of the tire ecosystem, particularly sorters, collectors, and / or recycler system participants.

[0121] In an embodiment of a method for monitoring at least one tire characteristic critical for reuse and / or recycling of tires or components, an access element is provided for accessing generated dataset(s) including the characteristic critical for reuse by one or more data-consuming network nodes associated with one or more reusers performing one or more reuse processes based on a reuse process and / or participant identifier. The access element may involve authorization rules that provide access to the dataset(s) based on the reuse process and / or participant identifier. The access element may involve authorization rules that provide access to the dataset(s) related to the characteristic critical for reuse based on a decentralized participant identifier and a reuse process identifier associated with the decentralized participant identifier. The access element may involve authorization rules that provide access to the dataset(s) related to the characteristic critical for reuse to selected participants of the tire ecosystem, particularly sorters, collectors, and / or reuse system participants. BRIEF DESCRIPTION OF THE DRAWINGS

[0122] Hereinafter, the present disclosure will be further described with reference to the accompanying drawings. In the accompanying drawings and the present disclosure, the same reference numerals are intended to refer to the same or similar elements, components and / or parts.

[0123] Figure 1 An example of a tire is schematically shown.

[0124] Figure 2 Examples of material layers that make up a tire tread are schematically illustrated.

[0125] Figure 3 An example of a tire ecosystem is shown.

[0126] Figure 4 An example of tire production controlled by an operating system including means for generating tire passes is shown.

[0127] Figure 5 An example of a production system that provides tires associated with a tire pass is shown.

[0128] Figures 6A to 6C An example of a method or apparatus for providing data associated with tire production, tire usage, and the handling of scrap tires across a tire value chain via a decentralized network is schematically illustrated.

[0129] Figure 7 An example method for generating a tire pass is shown.

[0130] Figure 8Example systems and associated methods are presented for generating a tire pass associated with a produced tire and providing access to the generated tire pass.

[0131] Figure 9 An example method for using a tire pass to further process tire data associated with the tire pass is shown.

[0132] Figure 10A 、 Figure 10B An example of an authentication protocol is shown.

[0133] Figure 11 An example method for authorizing access to tire data is shown.

[0134] Figure 12 A schematic illustration of providing access to a tire pass associated with a tire using a data consumption service associated with a data user via a data provision service associated with a data owner is shown.

[0135] Figure 13 Examples of ID-based owner data, ID-based tire pass data, and a decentralized identity infrastructure are shown.

[0136] Figure 14 An example of a tire pass including certificate-based data, ID-based tire pass data, and a decentralized identity infrastructure is shown.

[0137] Figures 15A to 17B Different example configurations of tire passes anchored by a decentralized identifier are shown.

[0138] Figure 18A 、 Figure 18B Shows examples of relational representations that can be used to generate cascades.

[0139] Figure 19 An example embodiment of a toroidal tire loop including participants connected by a decentralized network having decentralized network nodes associated with the participants is presented.

[0140] Figure 20 An example method for monitoring at least one tire characteristic critical to the reuse and / or recycling of a tire or component by at least one participant of a decentralized network is presented.

[0141] Figure 21 An example system for obtaining production- and / or usage-related tire data based on a decentralized tire identifier is presented.

[0142] Figure 22 A relational dataset illustrating the relationship between a specified tire or part thereof and production input(s) used to produce the tire or part thereof.

[0143] Figure 23 A method for obtaining tire data related to the production of tires or components thereof and / or tire data related to the use of the tire based on decentralized product identifier(s) and relationship access elements is presented. DETAILED DESCRIPTION

[0144] The following embodiments are merely examples for implementing the methods, devices, systems, and tire passes disclosed herein and should not be considered limiting.

[0145] Figure 1 Examples of tires are schematically illustrated. The tire may be a tire for a vehicle. Vehicles may include automobiles, such as cars, vans, minivans, buses, and SUVs (sport utility vehicles); trucks; vans, semi-trucks; tractors; motorcycles; trailers; ATVs (all-terrain vehicles); pickup trucks; heavy-duty vehicles, such as bulldozers, mobile cranes, and earthmovers; aircraft; and other modes of transportation that are typically equipped with one or more tires.

[0146] like Figure 1 As schematically illustrated, the tire 100 may include a tread portion 106 and a sidewall portion 108. The sidewall portion 108 may include a bead connected to the rim 104. The tread portion 106 may include a layered structure having different inner liners and a tread 102 (see FIG. Figure 2 ).

[0147] One of the main materials used in tires is rubber, such as natural rubber or synthetic rubber. Another main material includes fillers, such as carbon black or silica. Other materials include oil, steel, or fabrics, such as polyester, nylon, aramid, or rayon cord. Additional materials include chemical components, such as antioxidants, accelerators, accelerator decomposition products, sulfur, zinc oxide, or antiozonants.

[0148] Figure 2 Schematically shows the components constituting the tire tread (e.g. Figure 1 An example of a material layer of the tread portion 106).

[0149] Figure 2 Shown Figure 1 Portion 110 of tire 100 is shown to illustrate the layered structure of tread portion 106. First layer 208 may include a synthetic rubber inner liner. Second layer 206 may include plies that incorporate fiber filaments into the rubber. Third layer 204 may include a carcass layer that incorporates steel filaments into the rubber. Fourth layer 202 may include nylon filaments incorporated into the rubber. The outermost layer may include tread 102, which may include rubber, carbon black, and silica.

[0150] Figure 3 shows an example of a tire ecosystem. A tire can be Figure 1 The vehicle tire described in the context of FIG. Step 306 in the tire ecosystem may include the production of the tire in tire production 304. The tire may be produced in one or more production steps. The tire production may be connected to an operating system (see, e.g., Figure 4 ). The operating system can control the production of tires.

[0151] The tire can be produced from one or more chemical materials 302. Chemical materials 302 may include, for example, raw chemical materials or intermediate chemical products. Raw chemical materials may include water glass and monomers for producing rubber, such as ethylene, propylene, butadiene, styrene, and polyisobutylene. Intermediate chemical products may include rubber (such as natural rubber and / or synthetic rubber), oil, steel, fillers (such as carbon black and silica), polymers, tackifiers, antioxidants, accelerators, and antiozonants. Chemical materials 302 may be sourced from one or more chemical material suppliers, such as Figure 6A described in the context of .

[0152] Tires can include Figure 1 The tread portion and sidewall portion described in the context of FIG. The tread portion may include Figure 2 The hierarchical structure described in the context of .

[0153] The produced tires can be supplied from tire production 304 to vehicle manufacturers. The produced tires can be supplied from tire production 304 to workshops. The produced tires can be supplied from tire production 304 to tire dealers (not shown). Tire dealers can supply the tires to workshops and / or vehicle owners (not shown). The supply of tires can be performed using one or more distribution centers (not shown). Vehicle manufacturers can produce vehicles with tires produced by tire production 304 already attached (e.g., with new tires already attached). The produced vehicles can be provided to end users, who can use the vehicles and, therefore, the tires attached to the vehicles, in a use phase 308.

[0154] The use phase 308 may include tire repair. The use phase 308 may include replacing tires present on a vehicle. Tire repair and / or tire replacement may be performed by a workshop. For example, a workshop may replace a used tire attached to a vehicle with a new tire produced by tire production 304. For example, a workshop may repair a flat tire to extend the life of the tire. For example, a workshop may replace a scrapped tire with a used tire, such as a reusable tire.

[0155] The tire value chain may further include the collection of used and scrap tires 310. Used and scrap tires may be collected at a return point. Used and scrap tires may be provided to the return point by a workshop. Used and scrap tires may be provided to the return point by a tire dealer (not shown). Used and scrap tires may be collected from workshops and / or tire dealers and stored at the return point. The return point may be an initial collection center. The initial collection center may provide the collected used and scrap tires to a central return point. The return point may be a central return point.

[0156] The collected tires can be inspected and further processing can be determined. This further processing can depend on the condition of the tires, tire characteristics (such as type, age, size), and / or the presence of hazardous chemicals. If the collected tires are under a certain age and meet certain quality standards, such as no damage, tread pattern still present, and degree of wear, the collected tires can be reused (e.g., used tires) without any further processing (such as re-grooving or retreading). Recycling as used tires can include providing the used tires to a workshop or tire dealer. If the collected tires are under a certain age and meet certain quality standards, such as no damage, tire size suitable for retreading, and no chemical or oil damage, the collected tires can be retreaded. If the collected tires do not contain hazardous chemicals above a defined threshold, such as polycyclic aromatic compounds, dioxins, chlorine, bromine, and / or mercury, the collected tires can be recycled. If the collected tires cannot be reused, regrooved, reprocessed, or recycled, they can be provided to an incineration facility or disposed of in a landfill. For example, if received tires contain hazardous chemicals above a defined threshold, they can be incinerated or placed in a landfill.

[0157] The tire value chain may further include recycling, reuse, or disposal 312 of used tires. As previously mentioned, reuse, recycling, or disposal may depend on the condition of the tire, its properties, and / or the presence of hazardous chemicals. Reusing used tires can include both reuse without further processing and reuse with further processing. Further processing can include re-grooving or retreading. Reusing without further processing can include using the entire tire or parts of it, such as for use as fenders in shipping, in amusement parks, and in the cement industry. Reusing without further processing can include using it as a used tire. Regrooving may require carving a second tread layer into the tire when the first tread layer wears out. Regrooving can be performed on tires marked as regroovable. Regrooving can extend the life of the tire by up to 25%. Regrooving may require removing the tread of the old tire, applying a new tread, and performing vulcanization to attach the new tread to the tire. Regrooving can save up to 80% of the cost of a tire. Regrooving can be performed once or several times. Regrooving tires can be provided to workshops and / or tire dealers for further use in vehicles. Retreading companies can provide tires that cannot be retreaded to recycling companies for recycling.

[0158] Recycling can include mechanical recycling and chemical recycling (e.g., chemical recycling). Mechanical recycling can include shredding scrap tires at tire recycling companies. Shredded tires can be used for different applications depending on their size. For example, coarse fragments with a size of 50-250 mm can be used as drainage materials and as a substitute for natural gravel. Fine fragments with a size of 15-50 mm can be used as a base for water purification ground layers and as a substitute for natural gravel. Particles with a particle size of up to 6 mm can be used for rubber asphalt, foundry tailings, or as filler for artificial turf. Powder can be doped into paint for sound attenuation, or used as a subcomponent for making new tires and other molded products.

[0159] Chemical recycling can include desulfurization of scrap tires. Desulfurization can be performed at tire recycling companies. Desulfurization can be performed using the tread of scrap tires. Desulfurization can be performed using mechanical, microwave, chemical, or biological processes to break the sulfur bonds formed during vulcanization. Recycled materials (at low percentages) can be mixed into new tires and other rubber products that can be used to absorb sound, vibration, and shock.

[0160] Chemical recycling can include pyrolysis of scrap tires. Pyrolysis can be performed in tire recycling companies. The scrap tires can be shredded and heated in an oxygen-free atmosphere. Prior to heating, the metal and tire cord can be separated. The products produced by pyrolysis can include pyrolysis oil, recovered carbon black, and non-condensable gases. Approximately 15% of the weight of a single tire is steel, 30% to 40% becomes char (carbon black plus additives), and the remainder is pyrolysis oil / gas. Tire pyrolysis systems can include indirect-fired rotary kilns, stirred tank reactors, fluidized bed reactors, moving bed reactors, steel recovery, coke handling, grinding and pelletizing circuits, oil condensation systems, and gas purification systems.

[0161] A portion of the products obtained through recycling can be provided to tire production 304 and used to produce new tires. For example, carbon black obtained during pyrolysis and / or materials obtained through desulfurization can be provided to tire production 304. Scrap tire material produced through recycling can be provided to an incineration center or a landfill.

[0162] Scrap tires or parts of scrap tires that cannot be reused or recycled can be incinerated. Tire incineration can involve burning the scrap tires and recovering the energy generated, or feeding the tire or rubber scraps to cement plants. Incineration can be performed if retreading, re-grooving, or recycling is not possible. Incineration can be performed on scrap tires in pieces.

[0163] Figure 4 An example of a tire production 304 is shown that is combined with an operating system 402 including a device for generating tire passes for tires to produce one or more tires 404 from one or more incoming materials 302. The operating system 402 can be used to operate the tire production 304, for example, by managing the different production chains present within the tire production. The tire production 304 can produce tires from one or more chemical materials, for example, by reacting one or more chemical materials and / or by physically treating one or more chemical materials. The chemical materials can include, for example, Figure 1 and Figure 3 Chemical materials may include, for example, Figure 1 and Figure 3 Chemical materials can be supplied to tire production 304 from one or more suppliers (such as chemical companies that produce the chemical materials), for example, Figure 6A described in the context of .

[0164] To produce one or more tires 404, different materials 302 (hereinafter also referred to as inbound materials 302) may be provided as physical inputs from material providers or suppliers. Physical inputs for tire production 304 may include chemical materials, such as chemical raw materials, intermediates, or combinations thereof. Raw materials may be, for example, Figure 1 and Figure 3 virgin material or recycled raw material as described in the context of

[0165] Tire production 304 can transform incoming material 302 into one or more tires 404 exiting tire production 304 by chemical and / or physical transformation. The transformation can be performed via intermediate products or components. The transformation can be a chemical reaction or any other processing step. Inbound material 302 can be fed into tire production 304 at any entry point. Inbound material 302 can be fed into tire production 304 at the start of tire production 304. Inbound material can be considered an input for tire production 304.

[0166] Tire production 304 may include multiple production steps. The production steps included in tire production 304 may be defined by the system boundary of tire production 304. The system boundary may be defined by the location or control of the production process. The system boundary may be defined by the site of tire production 304. The system boundary may be defined by the production process controlled by one entity or multiple entities. The system boundary may be defined by a value chain with intertwined production processes leading to a final product, where these production processes may be controlled separately by multiple entities.

[0167] The operating system 402 of the tire production 304 can monitor and / or control the tire production 304 based on operating parameters associated with different processes performed by the tire production 304. One process step that is monitored and / or controlled can be the feeding of inbound material or the release of produced tire(s). Another process step that is monitored and / or controlled can be, for example, the use of a device for generating a tire pass (such as Figure 8 The operating system 402 may include such means for generating a tire pass. The operating system 402 may be configured to generate a tire pass associated with a tire produced by the tire production 304, for example, as Figure 7 and Figure 8 The operating system 402 may be communicatively coupled to such means for generating a tire pass, for example, the operating system 402 and the means for generating a tire pass may be separate units.

[0168] The operating system 402 may further include a requestor. The operating system may be communicatively coupled to such a requestor. The requestor may be configured to generate a request for generating a tire pass, for example, Figure 8 described in the context of .

[0169] The operating system 402 may further include an ID designator. The operating system may be communicatively coupled to such an ID designator. The ID designator may be configured to assign the decentralized identifier and associated information included in the tire pass to the physical identifier of the produced tire(s), such as Figure 5 and Figure 8 For example, the ID designator may generate a physical identifier having embedded therein (a plurality of) decentralized identifiers, and may provide the physical identifier to a labeling device that attaches the physical identifier to produced tires.

[0170] The ID designator, the requester and / or the means for generating a tire pass may be configured as a decentralized service or application executed via a decentralized network.

[0171] Figure 5 An example of providing a tire associated with a tire pass is shown. The tire may be produced by a tire production 304 including an operating system 402, such as Figure 4 described in the context of .

[0172] To produce a tire, intermediate products and raw materials may be provided as physical inputs. The intermediate products may include precursor materials. The precursor materials and raw materials may include virgin materials or recycled materials. The raw materials may be associated with a decentralized identifier. The decentralized identifier may be associated with a raw material pass for the raw material, which may be as follows: Figure 7 and Figure 8 The decentralized identifier can be associated with raw material data, including, for example, raw material name, raw material composition, chemical and / or physical properties of the raw material, emissions data of the raw material, recycled content data of the raw material, biobased content data of the raw material, renewable content data of the raw material, raw material production data, raw material declaration data, raw material safety data, certificate of analysis data associated with the raw material, certificates associated with the raw material, or a combination thereof.

[0173] The production of tires may comprise a two-step process: 1) producing intermediate product(s), and 2) producing tires from the intermediate product(s) and optionally additional raw materials (not shown). To produce the intermediate product(s), the raw materials may be used as physical input. An operating system (such as an operating system for the production of intermediate products) may access data related to the raw materials based on, for example, a decentralized identifier from a raw material provider. Such data may be used to operate the intermediate product production. For example, if the raw materials are recycled materials, a production step may be included to purify the recycled materials. For example, if the raw materials are virgin materials, the purification step may be omitted. The intermediate products may be formed by chemically reacting the raw materials or by physically treating the raw materials. Chemical reactions may include polymerization, precipitation, and other commonly known chemical reactions. Physical treatments may include mixing, grinding, extrusion, etc. An intermediate product pass may be generated for the intermediate products produced, as described below. Figure 7 and Figure 8 The intermediate product data may include data from the production of the intermediate product and additional data previously described with respect to tire data, such as data on the physical properties of the intermediate product, certificate of analysis data, material safety data, product declaration data, emission data, etc. The produced (multiple) intermediate products may be packaged, and the packaging may include a physical identifier, such as a QR code, an embossed code, or an optical holographic code, such as a zero-order diffraction microstructure. In FIG6 and Figure 7 In the context of , a physical identifier can be assigned to a decentralized identifier of an intermediate product pass.

[0174] In a second step, the intermediate product(s) can be supplied to a tire production to produce a tire, e.g. Figure 4 In addition to the intermediate products, further raw materials (not shown) may be provided to the tire production. Production data from the intermediate product production may be used by the tire production operating system (e.g. Figure 4 The operating system 402 described in the context of FIG. 1 is used to produce tires as described above. Intermediate products may include recycled materials or materials produced by different entities. Such intermediate products may be associated with a decentralized identifier via which the intermediate product data may be accessed. An ID reader may be used to read a physical identifier associated with the decentralized identifier, as described above. Figure 4 Decentralized identifiers can be used to retrieve intermediate product data, for example, Figure 12 described in the context of .

[0175] like Figure 7 and Figure 8As described in the context of , a tire pass can be generated for a produced tire, the tire pass comprising a decentralized identifier and data related to tire data. The decentralized identifier of the tire pass can be associated with the tire via a physical identifier. For example, the tire can include a physical identifier physically attached to the tire, such as a QR code, an embossed code, an optical hologram. Such a physical identifier element can be assigned to (multiple) decentralized identifiers. The assignment of the physical identifier element and (multiple) decentralized identifiers can be performed by an ID designator running locally in the decentralized system and / or distributed system (see, for example Figure 4 ) to be performed. For example, a packaging line may include a labeling device that detects the produced tires. Based on this knowledge, the requester may generate a request for generating a tire pass, and the decentralized identifier included in the generated tire pass may be assigned to the physical identifier, for example, by an ID assigner (see also below). Figure 7 and Figure 8 ). Assignment may include encoding the decentralized identifier in a physical identifier and providing the physical identifier (such as a code) to a tagging device configured to attach the physical identifier to the tire. The ID designator may be part of the tagging device or may be a separate device.

[0176] The generated tire passport may include a decentralized identifier and data related to tire data. The generated tire passport may further include a tire identifier associated with the produced tire. The data related to tire data may include tire data. Tire data may be recorded before and / or during and / or after production and / or during the use of the tire. Tire data may include emission data, such as CO2 footprint, PCF data, or recycled content data. For example, tire data may specify the recycled content of tire components, or the raw materials and / or intermediate products used to produce the tire. This recycled content may be directly associated with the decentralized identifier of the tire, or may be indirectly associated with the decentralized identifier of the tire, for example, via the decentralized identifiers of the raw materials or intermediate products. Tire data may include data related to tire characteristics, such as EU labeling information, tire specifications (such as tire width, aspect ratio, construction, rim diameter, load index, speed rating, usage conditions), the weight of the produced tire, the raw materials used to produce the tire, tire production data, the age of the tire, and / or approved uses. Tire data may include data related to the use of the tire, such as the number of kilometers traveled, the average lifespan determined based on the actual distance the tire is used and the time the tire is used, the type of vehicle to which the tire is attached, the manufacturer of the vehicle to which the tire is attached, the wear of the tire, the current weight of the tire, data about the workshop where the tire is attached, the loss of microplastics to the environment, the conditions of use of the tire, the intended use of the tire, maintenance data, and / or weather conditions when the tire is used. Tire data may include data related to production conditions provided by the operating system 402 of tire production 304. Tire data may include data related to operating conditions provided by the operating system 402 of tire production 304. Tire data may include data related to the manufacturer, such as the manufacturer's name, manufacturer's brand, or manufacturer's identifier. Tire data may include the tire name, tire brand, or tire identifier.

[0177] The data associated with the tire may include a digital representation (or representations) pointing to the tire data or a portion thereof. The data associated with the tire data may include multiple digital representations pointing to different portions of the tire data or a portion thereof. The data associated with the tire data may include multiple digital representations pointing to different portions of the tire data or a portion thereof. Such different portions may overlap at certain data points. The representation may include an access point to the tire data or a portion thereof, a link for accessing the tire data or a portion thereof, an endpoint for accessing the tire data or a portion thereof, or a service endpoint for accessing the tire data or a portion thereof.

[0178] The generated tire pass can include additional decentralized identifier(s) associated with chemical materials, such as intermediate products and raw materials used to produce the tire. These additional decentralized identifier(s) (also referred to as second decentralized identifier(s)) can be included along with the relationship between the decentralized identifier of the tire pass and the second decentralized identifier(s). This allows the decentralized identifier associated with the tire to be linked to the decentralized identifier associated with the chemical materials used to produce the tire. Thus, the relationship between the tire and the chemical materials used to produce the tire can be reflected in the tire pass.

[0179] Figures 6A to 6C An example of a method or apparatus for providing tire data associated with the production of tires and the use of tires, and tire recycling data associated with the processing of scrap tires across the tire value chain via a decentralized network is schematically illustrated.

[0180] exist Figure 6A In [1], a part of the tire ecosystem is shown, including tire production and the use of produced tires, such as in the manufacture of vehicles. In this example, input material providers, tire producers, and tire consumers can be connected to a decentralized network, such as Figure 12 Data on the input materials and the produced tires can be accessed via Figure 8 and Figure 12 The ID-based model described in the context of is provided in the form of a pass associated with the physical entity of the input material, tire, or vehicle to which the produced tire is attached.

[0181] The input material provider may provide input material 302. The input material 302 may include the following: Figure 1 and Figure 3 The raw materials or intermediates described in the context of the input material 302 may be provided by (a plurality of) data providers (also referred to as (a plurality of) data providing services) 602 associated with (a plurality of) input material providers connected to a decentralized network, such as Figure 12 A tire manufacturer may produce tire(s) 404 using input material(s) 302 provided to the tire manufacturer, such as, for example, Figures 3 to 5 Tire manufacturers can connect to Figure 12The data consumer (also referred to as data consumption service) 606 of the decentralized network described in the context of accesses the input material data associated with the input material 302. The input material data can be retrieved from the (multiple) data providers 602 associated with the corresponding (multiple) input material providers. The tire producer can generate a tire pass associated with the produced tire 404, for example, as Figure 7 and Figure 8 Tire manufacturers can connect to Figure 12 The tire pass and the tire data contained in the pass are provided by a data provider 602 of a decentralized network as described in the context of FIG. A tire consumer (such as a vehicle manufacturer or a workshop) can connect to the tire pass. Figure 12 The data consumer 606 of the decentralized network described in the context of accesses tire data associated with the produced tire 404 or a portion thereof.

[0182] The corresponding data owners in this example could be the input material producer, the tire producer, and the tire consumer. Data owners can include any entity that generates data. A data generation node can be coupled to a data owner, or to an entity that owns or produces the physical artifact from which or for which the data was generated. The data can also be generated by a third-party entity on behalf of the entity that owns the physical artifact from which or for which the data was generated.

[0183] exist Figure 6AIn the example of , a decentralized identifier for a tire pass can be associated with a tire. This decentralized identifier can be provided to value chain participants. Data associated with the tire can be collected across the production chain and during the use of the tire assigned to the tire-specific decentralized identifier via the tire-specific decentralized identifier. For example, one or more environmental attributes associated with the tire can be derived from environmental attribute(s) associated with input material 302 or any other product entity present in the tire's value chain. Tire data collected during production can include static or dynamic characteristics as described above. Tire data can relate to or include characteristics of chemical product(s) associated with the use of the chemical product(s) for producing the tire as described above. Data associated with the tire can be collected during the use of the tire attached to a vehicle via the tire-specific decentralized identifier. For example, such data can be collected by a workshop or by sensors attached to the tire. The decentralized identifier associated with the tire can be used to update tire data using data collected during the use of the tire (such as life data or maintenance data), for example by updating the tire data associated with the decentralized identifier or by adding the collected data to the tire data associated with the decentralized identifier. Such data may include data related to the use of the tire, such as distance traveled, average lifespan, type of vehicle to which the tire is attached, manufacturer of the vehicle to which the tire is attached, wear of the tire, current weight of the tire, maintenance data and / or weather conditions. The usage data may be used to determine the current condition of the tire, the average lifespan of the tire, or to determine the loss of microplastics to the environment, for example by comparing the weight of a new tire with the current weight of the tire.

[0184] In this way, the tire data can represent a digital twin of the tire, including the production history of the tire as well as the current state of the tire. Including data related to the use of the tire allows the digital twin of the tire to be updated so that it reflects the current state of the tire. In addition, environmental properties or hazardous contents within the tire can be tracked so that information can be transparent throughout the value chain, while the flow of information can be controlled by the participants in the supply chain. Data about the components used to produce the tire and data about the use of the tire can be used by return points, retreading companies and / or recyclers to determine the appropriate treatment of scrap tires based on the data. For example, tire recyclers (see e.g. Figure 6B ) can determine appropriate recycling operations based on the data.

[0185] like Figure 3 As described in the context of , scrap tires can be provided to tire recyclers. Scrap tires can correspond to Figure 6B The input material 302 of the tire recycler 608 is shown. The scrap tire data of the scrap tire 302 can be obtained by connecting to the Figure 12The tire recycler 608 can recycle the scrap tire(s) provided to the tire recycler, for example, Figure 3 Tire recyclers can connect to Figure 12 A data consumer (also referred to as a data consumption service) 606 of a decentralized network described in the context of accesses scrap tire data associated with scrap tires 302. The scrap tire data may be retrieved from data providers 602 associated with tire producers and / or vehicle manufacturers. A tire recycler may generate a recycled product pass associated with a product obtained through recycling, such as pyrolysis oil or carbon black 404, e.g., Figure 7 and Figure 8 Pyrolysis oil can be formed when shredded tires are pyrolyzed, for example, as Figure 3 The pyrolysis oil may contain a mixture of saturated and unsaturated hydrocarbons having 5 to 46 carbon atoms. The hydrocarbons may be saturated or unsaturated. The unsaturated hydrocarbons may include aromatic hydrocarbons. Examples of aromatic hydrocarbons may include monoaromatic compounds, diaromatic compounds, triaromatic compounds, and polycyclic aromatic compounds. Examples of non-aromatic compounds may include paraffins, monocycloalkanes, dicycloalkanes, and cycloalkanes. The pyrolysis oil may include up to 30 wt.% of hydrocarbons having 5 to 10 carbon atoms, up to 60 wt.% of hydrocarbons having 11 to 20 carbon atoms, up to 10 wt.% of hydrocarbons having 21 to 30 carbon atoms, and less than 10 wt.% of hydrocarbons having 31 to 46 carbon atoms.

[0186] Tire recyclers 608 can connect to Figure 12 In the example, the data owner may be a tire producer 304 and / or a vehicle manufacturer and a tire recycler 608.

[0187] exist Figure 6BIn this example, a decentralized identifier can be associated with a recycled product. This decentralized identifier can be provided to value chain participants. Data associated with the recycling of tires can be collected and assigned to the decentralized identifier via the decentralized identifier. The decentralized identifier can be associated with a tire-specific decentralized identifier. Thus, data about tires used to produce recycled products can be derived from the decentralized identifier contained in a recycled product pass. For example, a recycled material pass can contain the decentralized identifier contained in a tire pass and data regarding the relationship between the decentralized tire identifier contained in the recycled material pass and the decentralized identifier.

[0188] Products obtained by recycling tires, such as carbon black, can be provided to tire producers 304 and used as input materials 302 to produce new tires (see, e.g., Figure 3 ). Tire manufacturer 304 can obtain data from data consumers 606. Figure 12 Data about such products can be retrieved from data providers 602 associated with tire recyclers 608 as described in the context of FIG. Thus, input material providers for tire producer 304 can correspond to raw material supplier(s), intermediate product producer(s), and tire recycler(s).

[0189] The products obtained by recycling tires (e.g., pyrolysis oil) can be provided to chemical producers that produce chemical materials (e.g., raw materials and intermediate products), which use the pyrolysis oil as an input material 302 to produce raw materials (e.g., ethylene, propylene, and polyisobutylene) and intermediate products. Additional input materials 302 can be used together with the pyrolysis oil to produce chemical products. Thus, the pyrolysis oil produced by the tire recycler 608 can correspond to an input material 302 of a chemical material producer operating a chemical production network 610, such as, for example, Figure 6C The pyrolysis oil data of the pyrolysis oil 302 can be obtained by connecting to Figure 12 The chemical production network 610 may produce one or more raw materials and / or intermediate products 404, for example, in the context of a distributed network of tire recyclers 608 associated with the data provider (s) 602. Figure 3 Examples of raw materials include monomers used to make synthetic rubber. Examples of intermediate products include dispersants, fillers, and polymers such as synthetic rubber. A chemical producer operating a chemical production network 610 can connect to a network such as Figure 12A data consumer 606 of a decentralized network described in the context of accesses pyrolysis data associated with pyrolysis oil 302. The pyrolysis oil data may be retrieved from a data provider 602 associated with a tire recycler 608. A chemical producer may generate a chemical product pass associated with produced chemical products such as monomers, polymers, fillers, and dispersants, for example, as Figure 7 and Figure 8 Chemical producers can be connected to Figure 12 In the context of the invention, a data provider 602 of a decentralized network is used to provide chemical product data, or a portion thereof, contained in a chemical product passport. The chemical product data may include environmental attributes associated with a chemical product, such as recycled content from pyrolysis oil obtained from recycled tires. In this example, the corresponding data owners may be a tire recycler 608 and a chemical producer operating a chemical production network 610.

[0190] exist Figure 6C In the example of , a decentralized identifier can be associated with a chemical product. This decentralized identifier can be provided to value chain participants. Data associated with the produced chemical product can be collected via the decentralized identifier and assigned to the decentralized identifier. The decentralized identifier can include a decentralized identifier specific to pyrolysis oil and / or a decentralized identifier specific to tires. Thus, data about tires indirectly used to produce chemical products can be derived from the decentralized identifier contained in the chemical product pass. Furthermore, environmental attributes associated with the pyrolysis oil can be derived from the decentralized identifier contained in the recycled material pass associated with the pyrolysis oil produced by tire recycler 608.

[0191] Chemical products produced by chemical production network 610 can be provided as input materials 302 to tire production 304, such as Figure 6A As shown. Tire manufacturer 304 can Figure 12 The data consumer 606 described in the context of can retrieve chemical product data provided by a data consumer 606 associated with a chemical production network 610. The decentralized identifier of the chemical product pass can be associated with the decentralized identifier of a tire pass, which is associated with a tire produced from the chemical product. In this way, the environmental properties of the chemical product and the tire produced from the chemical product 302 can be tracked through the value chain all the way to the tire. By tracking the environmental properties of the tire in this way, information can be made transparent throughout the value chain, and the flow of information can be controlled by the participants in the supply chain. In addition, as Figure 4The production operating system described in the context of [ 1 ] can process environmental attributes according to the needs of the individual participants. Overall, this tracking enables the positive environmental impact of the individual tire value chain participants to be tracked, making the positive environmental impact transparent and attributable to the individual tire value chain participants.

[0192] Figure 7 An example method for generating a tire pass is shown. A tire pass may be generated for a tire 404 produced by tire production 304 from one or more inbound materials 302, e.g., Figures 4 to 6A The tire pass may be generated by the operating system 402 of the tire production 304. The tire pass may be generated by the operating system of the vehicle production. The operating system may include means for generating (multiple) tire passes, such as Figure 8 described in the context of .

[0193] In block 702, a request for generating a tire pass for a produced tire may be received. The request may include a data owner identifier and / or a tire identifier. The data owner may be the data owner of the collected data and / or data contained in a distributed data source. The data owner may be a chemical product producer. The data owner may be a data owner as described above. The tire identifier may be a batch number, a lot number, a tire name, and / or a tire ID. The request may be generated by a requestor, for example, Figure 7 The request may be received at a computing node (which acts as a management module for the DID owner, a user agent, an ID hub, and / or a certificate issuing authority). The decentralized identifier may be requested from a central node or a decentralized node.

[0194] In block 704, an authentication mechanism(s) may be provided or selected, which is generally optional. The authentication mechanism may include a private key-public key pair. If the decentralized identifier to be generated includes a DID, an authentication mechanism may be selected or provided.

[0195] In block 706, a decentralized identifier associated with the tire data and the data owner may be generated or provided. The decentralized identifier may include one or more DIDs and / or UUIDs. The decentralized identifier and data associated with the authentication mechanism may be generated or provided.

[0196] In block 708, data related to the tire data may be provided. The data related to the tire data may include the previously mentioned (e.g., Figures 4 to 6CThe tire data may be collected before, during, or after production and / or during use of the tire. The tire data may be stored on a data storage medium, such as one or more databases. Providing the tire data may include retrieving the tire data based on a tire identifier, such as the tire identifier included in the request received in block 702. The data associated with the tire data may include a reference to a digital representation (or multiple representations) of the tire data or a portion thereof, such as, for example, Figures 4 to 6C described in the context of .

[0197] In box 710, a tire pass can be generated based on the provided or generated decentralized identifier and data related to the tire data. The tire pass may include the decentralized identifier provided or generated in box 706 and the data related to the tire data provided in box 708. The tire pass may correspond to a DID document associated with the decentralized identifier, which is the DID. The DID document may contain (multiple) digital representations pointing to the tire data or a portion thereof. The tire pass may further include a tire identifier. The tire identifier may be the tire identifier included in the received request. The generated tire pass may be stored in a database. The generated tire pass or a portion thereof may be provided for access by a data consumption service, which is controlled by a data providing service associated with the data owner, such as, for example Figure 8 and Figure 12 described in the context of .

[0198] In block 714, which is generally optional, the physical identifier may be assigned to the decentralized identifier included in the tire pass. Assigning the decentralized identifier to the physical identifier may include generating a physical identifier in which the decentralized identifier is embedded. The physical identifier may be generated by an ID assignor, for example, as Figure 5 and can be attached to a tire, for example, using a tagging device.

[0199] The generated tire passport allows for simplified and customizable data sharing or exchange of tire data associated with tires produced by the tire industry with vehicle manufacturers and other participants in the tire value chain, such as retreading and recycling companies. The use of the tire data can increase the recycling rate of scrap tires, for example, by using the tire data to determine appropriate recycling processes for scrap tires.

[0200] Figure 8 Example systems and associated methods are presented for generating a tire pass associated with a produced tire and providing access to the generated tire pass.

[0201] Tire production 304 may use one or more incoming materials (also denoted as precursor materials) 302 to produce tire(s) 404. The incoming materials may include chemical raw materials and / or intermediate products, such as Figures 3 to 6A Tire production 304 may be as follows: Figures 3 to 6A Inbound material(s) 302 may enter system boundary 804 of tire production 304. Tire(s) 404 may be produced using inbound material(s) 302, e.g., Figures 3 to 6A The tire(s) 304 may leave the system boundary 804 of the tire production 304 .

[0202] When the tire 404 is produced or when the tire 404 leaves the tire production 304, a tire pass(es) associated with the produced tire(s) 404 may be generated. The tire pass(es) associated with the produced tire may be generated when a vehicle with the corresponding tire attached is produced. The tire pass(es) may be generated by the apparatus 802 for generating tire pass(es). The apparatus 802 may be configured to generate a tire pass(es) according to Figure 7 The method described in the context of can be used to generate (multiple) tire passes. Device 802 can be configured to receive a request for providing a decentralized identifier. The decentralized identifier can be associated with tire data and a data owner. The data owner can include any entity that generates the tire data or a portion thereof. The data owner can be the data owner of the tire data or a portion thereof. The data owner can be a tire manufacturer. The data owner can be a vehicle manufacturer. The tire data or a portion thereof can be accessed by the data owner. Therefore, the data owner can directly or indirectly own the tire data or a portion thereof. The decentralized identifier can be associated with the tire pass and the data owner. Device 802 can be configured to generate a tire pass in response to the received request.

[0203] The requester 806 may be configured to generate a request for a decentralized identifier. The request may be triggered by a tagging system such as a QR code generator. The request may be triggered by a code reading system such as a QR code reader. The request for providing a decentralized identifier may be provided to a decentralized ID generator 808, which is configured to generate a decentralized identifier. The decentralized ID generator 808 may be configured to generate a decentralized identifier associated with the tire data and the data owner. The decentralized ID generator 808 may provide the generated decentralized identifier to a decentralized ID provider 810. Although the decentralized ID generator 808 and the decentralized ID provider 810 may be configured to generate a decentralized identifier associated with the tire data and the data owner, the decentralized ID generator 808 may be configured to generate a decentralized identifier associated with the tire data and the data owner. The decentralized ID generator 808 may provide the generated decentralized identifier to the decentralized ID provider 810. Figure 8Although shown as separate units, their functionality may be combined within a single unit, such that the apparatus 802 comprises a decentralized ID providing unit configured to generate or retrieve a decentralized identifier and to provide the generated decentralized identifier.

[0204] The decentralized ID provider 810 may provide the decentralized identifier received from the decentralized ID generator 808 to the requester 806. The requester 806 may be configured to associate the received decentralized identifier(s) with the produced tire 404. Thus, the requester 806 may include information such as Figure 4 and Figure 5 The ID designator described in the context of FIG. This association may include encoding the decentralized identifier into a code and providing the code to label the tire 404. This association may include associating the decentralized identifier with a physical identifier of the tire. Thus, a physical identifier may be provided that associates the physical entity of the tire with the provided decentralized identifier and, therefore, with the tire pass associated with the decentralized identifier.

[0205] The decentralized ID provider 810 may provide the decentralized identifier to a tire pass generator 812, which is configured to generate a tire pass including the decentralized identifier received from the decentralized ID provider 810 and data related to the tire data. The tire pass generator 812 may generate the tire pass, such as in Figure 7 Tire data or a portion thereof may be provided to tire pass generator 812 from a data storage medium, such as a database (not shown). Digital representation(s) pointing to the tire data or a portion thereof may be generated by tire pass generator 812. The generated tire pass may be stored on a data storage medium (not shown).

[0206] The generated tire pass may be provided to a tire pass provider 814. The tire pass provider 814 may be configured to provide the tire pass for access by a data consumption service 818. The data consumption service 818 may be part of a decentralized network 816. The data consumption service 818 may be associated with a tire recipient, such as Figure 6B The tire pass provider 814 may control access to the data consumption service 818. The tire pass provider 814 may be a data providing service associated with the tire production 304. The tire pass provider 814 may be associated with or under the control of a data owner of the tire data associated with the generated tire pass. The tire data or a portion thereof contained in the tire pass may be provided to, for example, Figure 12This allows the transmission or access of tire passes and tire data or portions thereof in a controlled and secure manner.

[0207] Figure 9 An example method for using a tire pass to further process tire data associated with the tire pass is shown.

[0208] To use a tire pass, an instruction to access tire data associated with a decentralized identifier of the tire pass may be received in block 902. The structure of the tire pass may be as follows: Figure 13 and Figure 14 Tire passes can be Figure 7 and Figure 8 Generated as shown.

[0209] Before access to the tire data can be provided, the request can be authenticated in block 904. In particular, the data consumption service requesting access to the tire data and / or the data service provider providing access to the chemical process data can be authenticated. This authentication can be based on a decentralized identity and data associated with the authentication mechanism. Authentication can be performed through different communication modes, which will be discussed in detail in the following sections. Figure 10A and Figure 10B Shown in more detail in .

[0210] If the authentication fails, access to the tire data may be denied (see block 908). If the authentication is valid, an authorization step may be performed in block 910. Such authorization may be based on the decentralized identifier and data associated with the authorization rules. The data may be associated with the decentralized identifier.

[0211] If authorization fails, access to the tire data may be denied (see block 914), or access may be adjusted. In particular, the requested authorization may be adjusted to comply with applicable authorization rules. If authorization is valid, access to the tire data may be granted in accordance with the requested authorization rules, and the requested tire data may be provided in accordance with the authorization rules in block 916. This access to the tire data associated with the decentralized identifier may be provided using the digital representation(s) contained in the tire pass.

[0212] The received tire data may be processed in block 918. For example, the received tire data may be used to determine a disposition for the used tire, such as whether the tire may be reused, re-grooved, retreaded, or recycled.

[0213] Figure 10A and Figure 10B An example method for authenticating to access tire data associated with a tire passport is shown. During the authentication process, various communication modes can be implemented to verify identity.

[0214] Figure 10A 6. An example communication pattern is shown that can occur between a data providing service 602 and a data consuming service 606. In this case, the data providing service 602 can act as the verification entity, and a separate service may not be used for authentication.

[0215] The data consumption service 606 may issue a service request (see step [1]) to the data provision service 602. The request may include a decentralized identifier of the data consumption service decentralized identifier, such as a decentralized identifier (DID) or a verifiable credential.

[0216] In response to the request, the data-providing service may access a registry (e.g., a centralized or decentralized authentication registry) to retrieve data related to the authentication mechanism(s) associated with the decentralized identifier. For example, a centralized authentication registry may provide the authentication mechanism-related data via an authentication service that issues an access token. Further, for example, a decentralized authentication registry may provide the authentication mechanism-related data by generating a request token. The authentication mechanism-related data may include the public key of the data-consuming service.

[0217] Based on the retrieved data related to the authentication mechanism(s), the data providing service may generate an authentication request (e.g., corresponding to an authentication request token or a dynamic attribute token) (see step [2]). The authentication request may be generated based on the public key of the data consuming service and / or the private key of the data providing service 602. The generated authentication request may be sent to the data consuming service 606 (see step [3]).

[0218] Based on the received authentication request, the data consumption service 606 may generate authentication data for responding to the authentication request (step [4]). The generated authentication data may be sent back to the data provision service 602 (step [5]).

[0219] After receiving the response including the authentication data from the data consumption service 606, the data provisioning service 602 can then verify the authentication data (see step [6]). In response to the verification, the data provisioning service 602 can grant or deny the service request of the data consumption service 606 (step [7]).

[0220] Figure 10B Yet another communication pattern that can occur between the data providing service 602, the authentication service 1004, and the data consuming service 606 is shown.

[0221] First, the data consumption service 606 may request service or initiate communication with the data providing service 602 (step [1]). The request may include a decentralized identifier of the data consumption service decentralized identifier, such as a decentralized identifier (DID) or a verifiable credential.

[0222] Upon receiving the request, the data provision service 602 may access the distributed ledger to retrieve one or more authentication mechanisms associated with the decentralized identifier. Based on the retrieved authentication mechanism(s), the authentication service 1004 may generate an authentication request.

[0223] Here, at least one of the retrieved authentication mechanism(s) may be provided via authentication service 1004. Thus, in some embodiments, the generated authentication request may be sent directly to authentication service 1004 (steps [2], [3]). Upon receiving the authentication request from data provisioning service 602, authentication service 1004 may generate authentication data (step [4]). The authentication data generated by authentication service 1004 may be sent to data consumption service 606 (step [5]).

[0224] The data consumption service 606 may then pass the authentication data to the data provisioning service 602 (step [6]). Upon receiving the authentication data, the data provisioning service 602 may then verify the authentication data (step [7]). In response to the verification, the data provisioning service may grant or deny the service request of the data consumption service 606 (step [8]).

[0225] Alternatively, in some embodiments, after the data providing service 602 can generate an authentication request, and can send the authentication request to the data consuming service 602. The data consuming service can pass the authentication request to the authentication service 1004 (not shown).

[0226] Furthermore, after the authentication service 1004 can generate the authentication data, in some embodiments, the authentication service only contacts the data consumption service 606 to notify the receipt of the authentication request and obtain consent. When the data consumption service 606 receives the notification, the data consumption service 606 can agree and send the consent back to the authentication service 1004. After receiving the consent, the authentication service 1004 can then send the authentication data directly to the data providing service 602.

[0227] Finally, in many transactions, authentication can be performed by both parties to each other. In the case of such mutual authentication, each party can be both a principal entity and a verification entity. The data consumption service 606 and the data providing service 602 can control their decentralized identification. Initially, each service can exchange its own decentralized identifier. Next, each of these services can access the distributed ledger to obtain each other's (multiple) authentication mechanisms. Each service can then generate its own authentication request based on the (multiple) authentication methods of the other IDs. The generated authentication data can then be sent to the other services. After receiving each other's authentication data, each service can verify the received authentication data. Based on the verification results, these services can then perform additional communications, for example, one service can grant or deny the service request of another service.

[0228] Figure 10A and Figure 10B Only an example of an authentication protocol is shown. Additionally, although the communication arrows are discussed in a certain order or shown as a communication sequence, no particular order is required unless otherwise specified or because one communication depends on another communication being completed before the communication can be transmitted.

[0229] Figure 11 An example method for authorizing access to tire data is shown. The tire data may be associated with a tire pass that includes a decentralized identifier and data related to the tire data. The tire pass may be Figure 7 and Figure 8 is generated as described in the context of .

[0230] In block 1102, a decentralized identifier for a tire pass (hereinafter referred to as a decentralized tire identifier) ​​and a set of authorization rules for tire data associated with the decentralized identifier may be provided. The set of authorization rules may include usage specifications that define a usage policy for entities accessing tire data associated with the decentralized identifier. The set of rules may include one or more local rules specific to a particular location. The one or more local rules may be based on the location where the decentralized identifier is generated, the location where the data provision service is implemented, the location where the data consumption service is implemented, or a combination thereof.

[0231] One or more sets of local rules may be provided based on the location or data provided by the data provision service. The location may refer to a jurisdiction, and the local rules may be associated with legal requirements related to the production, supply, and end-of-life disposal of tires. For example, access to tires may be provided via authorization rules that may include jurisdictional or local rules. Tire data may include Figures 3 to 6CThe set of authorization rules may include at least one regulatory directive configured to provide access to tire data associated with regulatory requirements for tires. The provided set of authorization rules may be associated with an access entity decentralized identifier. The authorization rules may include computer-executable instructions for allowing access to tire data associated with the decentralized tire identifier, denying access to tire data associated with the decentralized tire identifier, modifying access to tire data associated with the decentralized tire identifier, or modifying tire data associated with the decentralized tire identifier. The authorization rules may be associated with each data point of the tire data or a category of tire data, wherein the selected authorization rule may be bound to the tire data, a category of tire data, an individual data point, or a combination thereof. The set of authorization rules may include one or more prescribed rules related to obligations for a data consumption service associated with the access entity decentralized identifier. The set of authorization rules may include one or more prescribed rules related to emissions data, production data, recycled content data, bio-based content data, provenance data, labor condition data, or a combination thereof. The set of authorization rules may include one or more processing rules related to processing of emissions data, production data, recycled content data, biobased content data, provenance data, labor condition data, or a combination thereof by a data consuming service associated with an access entity decentralized identifier.

[0232] In block 1104 , a decentralized identifier or data related to a decentralized identifier of an accessing entity (hereinafter referred to as an accessing entity decentralized identifier) ​​may be provided.

[0233] At block 1106, authorization rules for the tire data associated with the decentralized tire identifier may be selected based on the accessing entity decentralized identifier or data associated with the accessing entity decentralized identifier. The authorization rules may include computer-executable instructions for allowing, denying, or modifying the tire data. The authorization rules may be associated with each data point of the tire data or with a collection or category of tire data. The selected authorization rules may be stored for application to the tire data. Such authorization rules may be applied prior to or during a data transaction. The selected authorization rules may be bound to the tire data, individual data points, or categories of tire data for application to the tire data.

[0234] In block 1108, the selected authorization rule may be applied to the tire data associated with the decentralized tire identifier. The selected authorization rule may be applied before accessing the tire data. The selected authorization rule may be applied during runtime while accessing the tire data.

[0235] In block 1110 , tire data associated with the decentralized tire identifier may be provided according to the selected authorization rules.

[0236] Figure 12 A schematic illustration of providing, via a data provision service associated with a data owner, access to a tire pass associated with a tire using a data consumption service associated with a tire consumer via a decentralized network is shown.

[0237] The tire 402 produced by the tire production 304 can be provided in association with a tire pass. The tire pass can be as follows: Figure 7 and Figure 8 The tire pass may include a decentralized identifier associated with the tire data and the owner of the data. The tire pass may include data related to the tire data. The data related to the tire data may include a reference to a digital representation (or multiple representations) of the tire data or a portion thereof (see, for example, Figure 13 ).

[0238] The tire pass may further include or involve authentication and / or authorization information linked to a decentralized identifier. Authentication and / or authorization information may be provided for authenticating and / or authorizing the data providing service 602 and / or the data consuming service 606. The decentralized identifier may include (multiple) universal unique identifiers ((multiple) UUIDs) and / or (multiple) decentralized identifiers ((multiple) DIDs). The decentralized identifier may include any unique identifier uniquely associated with the data owner and / or the tire data and / or the tire. The data owner may be the producer of the tire. The data owner may own or access the tire data or a portion thereof. Access to the tire data may be controlled by the data owner via the decentralized identifier and its unique association with the data owner and / or the tire. The data owner may include any entity that generates the data. The data generation node may be coupled to the data owner, or to an entity that owns or produces a chemical product from which or for which data is generated. The data may be generated by a third-party entity on behalf of an entity that owns the tire from which or for which data is generated.

[0239] Tire 404 can be physically delivered to a tire consumer, such as a vehicle manufacturer, distributor, and / or workshop. Tire 404 may include a code, such as a QR code, that has been encoded with a decentralized identifier. The tire consumer can read the code using a code reader 1202. The decentralized identifier can be provided to a database 1204 associated with the tire consumer. In other embodiments, the tire consumer can retrieve the decentralized identifier using a registry 1206. For example, the tire identifier encoded in the code can be used to retrieve the decentralized identifier from the registry 1206. The registry 1206 can store the decentralized identifier associated with the tire pass. The registry 1206 can further store access data associated with the decentralized identifier. The access data can include a digital representation of the tire data or a portion thereof. Thus, the access data can allow identification of the data providing service 602 that provided the tire data or a portion thereof.

[0240] Based on the received decentralized identifier, data consumption service 606 may trigger a request to access tire data associated with the decentralized identifier, as indicated by arrow 1210. The decentralized identifier may be provided to data providing service 602 associated with the manufacturer of tire 404 or to the data providing service of the tire manufacturer. Additionally, authentication and / or authorization information may be provided.

[0241] Requests can be authenticated (see Figure 10A and Figure 10B ) and / or be authorized to access tire data associated with the decentralized identifier. Based on successful authorization and / or authentication, access to the tire associated with the decentralized identifier can be granted.

[0242] The data providing service 606 may use the received data to retrieve tire data associated with the produced tire 404, or a portion thereof, as indicated by arrows 1212 and 1214. The tire data associated with the tire 404, or a portion thereof, retrieved by the data providing service 602 may be provided to the data consuming service 606, as indicated by arrow 1216. The received tire data, or a portion thereof, may be stored in a database 1204 associated with the consumer of the tire 404, as indicated by arrow 1218.

[0243] Tire data, or portions thereof, can be uniquely associated with a tire through a decentralized identifier. Through a decentralized network, tire data, or portions thereof, can be transmitted in a standardized and secure manner between tire producers and consumers, as well as other participants in the tire value chain. This allows tire data, or portions thereof, to be shared directly among value chain participants, uniquely associated with the tire and without the need for a central intermediary. This ensures transparency of tire data sets across the entire value chain. Tire Passport thus allows for the sharing of tire data under simplified and customizable conditions without compromising data security and sovereignty.

[0244] Although the description of tire producers and tire consumers has been Figure 12 However, the exchange of tire data can also be carried out between the tire producer and other participants in the value chain, such as workshops, retreading companies and / or recycling companies.

[0245] Figure 13 Examples of ID-based owner data, ID-based tire pass data, and a decentralized identity manager are shown.

[0246] A decentralized identifier may be a decentralized ID (DID). A tire pass may be a DID document associated with a DID. ID-based owner data may include a DID associated with a subject (such as tire data) and may include an authentication mechanism. ID-based owner data may include owner data that is electronically owned and controlled by the DID owner. In this context, electronically owned may refer to data stored in an owner repository or wallet. Such data may be securely stored and / or managed on an organization's server or client device. ID-based owner data may include a DID, a private key, and a public key. An ID-based owner may own and control a DID representing an identity associated with a DID subject, a private key associated with the DID, and a public key pair. A DID may be understood as an identifier and authentication information associated with or uniquely linked to the identifier.

[0247] The DID subject may be a tire. The DID subject may be a machine, system, or device used to produce tires, or a collection of such (multiple) machines, (multiple) devices, and / or (multiple) systems. The DID owner may be a tire producer. The DID owner may be an upstream participant in the tire value chain of the tire producer, such as a supplier of raw chemical products or precursors used to produce tires. The DID owner may be a downstream participant in the tire value chain of the tire producer, such as a customer who consumes tires. The DID owner may be any participant in the tire supply chain, including raw chemical product suppliers, intermediate chemical product manufacturers, tire producers, vehicle producers, workshops, collectors, retreading companies, or recycling companies.

[0248] A DID can be any identifier associated with a DID subject and / or DID owner. Preferably, the identifier is unique to the DID subject and / or DID owner. The identifier can be unique at least within the scope of the intended use of the DID. The identifier can be: a locally or globally unique identifier for a tire; a machine, system, or device used to produce tires, or a collection of such machine(s), device(s), and / or system(s); a chemical manufacturer that produces chemicals, a tire producer, a downstream participant in the tire value chain of a tire producer, or a collection thereof; any participant in the tire value chain, including chemical product suppliers, intermediate chemical product manufacturers, tire producers, vehicle producers, workshops, collectors, retreading companies, or recycling companies, or a collection thereof.

[0249] A DID can be a Uniform Resource Identifier (URI), such as a Uniform Resource Locator (URL). A DID can be an Internationalized Resource Identifier (IRI). A DID can be a random string of numbers and letters to improve security. In one embodiment, a DID can be a 128-character string of letters and numbers, for example, following this format: didi:method name:method-specific didi, such as didi:example:ebfeb1f712ebc6f1c276e12ec21. A DID can be decentralized, independent of a centralized third-party management system, and controlled by the DID owner.

[0250] A DID document 1304 can be associated with a DID. Thus, a DID document 1304 can include a reference to the DID, which can be associated with the DID subject described by the DID document. The DID document 1304 can include authentication information, such as a public key. The public key can be used by a third-party entity that has been granted access to information and data owned by the DID owner / subject. The public key can be used to verify that the DID owner actually owns or controls the DID. The DID document 1304 can include authentication information, authorization information, such as authorizing a third-party entity to read the DID document or portions of the DID document 1304, without, for example, granting the third party the right to prove ownership of the DID.

[0251] The DID document 1304 may include additional identifier(s), such as identifier(s) associated with different portions or categories of tire data. The DID document 1304 may further include one or more representations that are digitally linked to the tire data, for example, via a service endpoint. A service endpoint may include a network address that runs a service on behalf of the DID owner. In particular, a service endpoint may refer to a service that the DID owner grants access to the tire data or a portion thereof. Such a service may include a service that reads or analyzes the tire data or a portion thereof. The tire data may include Figures 3 to 6C Data described in the context of

[0252] The DID document 1304 may include various other information, such as metadata specifying when the DID document 1304 was created, when it was last modified, and / or when it expires.

[0253] The DID and DD document 1340 can be associated with a data registry node such as a centralized data service system or a decentralized data service system 1306 (e.g., a distributed ledger or blockchain or a decentralized file system). The distributed ledger or blockchain can be used to store a representation of the DID pointing to the DID document 1304. The representation of the DID can be stored on a distributed computing node of the distributed ledger or blockchain 1306. For example, a DID hash can be stored on multiple computing nodes of the distributed ledger and point to the location of the DID document 1304. In some embodiments, the DID document 1304 can be stored on the distributed ledger 1306. Each of the computing nodes can store a copy of the distributed ledger 1306. In this way, each DID hash can be stored redundantly, thereby allowing for improved data security. DIDs associated with multiple different DID documents 1304 can be included in the distributed ledger 1306.

[0254] In some embodiments, the DID document 1304 may be stored on the distributed ledger 1306, i.e., in addition to or as an alternative to storing the associated DID representation on the distributed ledger 1306. In other embodiments, the DID document 1304 may be stored in a data store (not shown) associated with the distributed ledger or blockchain or decentralized file system.

[0255] The distributed ledger or blockchain 1306 can be any decentralized distributed network that includes various computing nodes that communicate with each other. For example, the distributed ledger 1306 can include a first distributed computing node, a second distributed computing node, a third distributed computing node, and any number of additional distributed computing nodes (not shown). The distributed ledger or blockchain 1306 can include known technology stacks such as Bitcoin (see, for example, the Bitcoin documentation published on November 11, 2022 at https: / / en.bitcoin.it / wiki / Protocol_documentation), Ethereum (see, for example, the Ethereum documentation published on August 15, 2022 at https: / / ethereum.org / en / developers / docs / ), Solana (see, for example, the Solana documentation published on November 11, 2022 at https: / / spl.solana.com / ), Polygon (see, for example, the Polygon documentation published on November 11, 2022 at https: / / wiki.polygon.technology / ), or other implementations that perform varying degrees of data transactions on a distributed ledger. The description of the example framework is for illustrative purposes only and should not be considered limiting.

[0256] Figure 14 Examples of ID-based credential data, ID-based tire pass data, and an identity manager are shown.

[0257] and Figure 13 Compared to the example, Figure 14An example is certificate-based. Certificate data 1402 may include authentication data of a subject and a certificate issuing authority. The subject may be a data owner or a data provisioning service 602 operated by or under the control of a data owner. Certificate data 1402 may further include the name of the subject for which the certificate was issued, such as a data owner name, a data owner ID, a data provider name, a data provider ID, or a combination thereof. The certificate may be an X.509 certificate, such as X509v3. Certificate data 1402 may be associated with an IDS infrastructure 1406, which includes, for example, a certificate issuing service (CA) 1408 and / or a dynamic provisioning service (DAPS) 1410 that provides dynamic attribute tokens (e.g., OAuth access tokens). Certificate data 1402 may further include various other information, such as metadata specifying when the certificate was created, when it was last modified, and / or when it expires. The information required to verify certificate data 1402 may be provided via an authentication registry associated with the certificate issuing service and / or the dynamic provisioning service. For example, in the IDSA Reference Architecture Model Version 3.0 of April 2019, a data provisioning service 602 associated with or under the control of a data owner, a certificate authority (CA) 1408, a dynamic attribute provisioning service (DAPS) 1410, and a data consumption service (not shown) is used to verify identity before performing data exchange (see, e.g., Figure 10A and Figure 10B ).

[0258] The certificate data 1402 and the tire pass data 1404 may be stored within the data provision service 602. The data provision service 602 may be associated with or under the control of a data owner of the tire data.

[0259] Tire pass data 1404 may include a decentralized identifier, authorization data, and an endpoint associated with the tire data or a portion thereof. The decentralized identifier may be a universally unique identifier (UUID), such as UUIDv4. UUIDv4 may conform to the following format: [0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}. The authorization information may be used to control access to the tire data or a portion thereof, for example, Figure 9 An endpoint may include any digital representation pointing to tire data or a portion thereof. Tire data may include Figures 3 to 6C data mentioned in the context of the

[0260] Tire pass data 1404 may include various other information, such as metadata specifying when the tire pass was created, when it was last modified, and / or when it expires.

[0261] Figures 15 to 17 show different example configurations of tire passes anchored by digital identifiers. These configurations include different relationships of passes generated in the tire value chain up to the vehicle. These passes can be used Figure 7 The method described in the context of is generated.

[0262] Figure 15A The individual configurations of the different passes generated in the tire value chain are shown, e.g. Figure 3 As described in the context of . Separate passes can be generated for multiple product stages in the tire value chain. Pass generation can include providing a decentralized identifier and data related to the corresponding product data for each of the multiple product stages. Pass generation can further include providing an authentication mechanism. These passes for multiple product stages can be based on cryptographic signatures. For example, these passes for multiple product stages can be cascaded by hash values ​​based on different data sets. Figure 15A As shown, Hash 1 can be based on data from a raw material pass, Hash 2 can be based on data from a chemical product pass, and Hash 3 can be based on data from a raw material pass plus data from a chemical product pass. Similarly, Hash 4 can be based on data from a tire pass, and Hash 5 can be based on data from a chemical product pass and a tire pass. Further cascading can be done for other combinations of passes, up to Hash 7, which can cascade a tire pass and a vehicle pass. Hashes can be used to generate a hash chain, allowing the raw materials and chemical products used to produce a tire, as well as the tire attached to a vehicle, to be determined. The sequence of hashes from Hash 1 to Hash 7 can be viewed as a "mirror" of the value chain from raw materials to vehicles, as it reflects the relationship between the various passes. Cascading via cryptographically signed hashes is just one example cascade. Other examples include permission aggregation of different ranges of data that can be embedded in sub-passes, aggregation of public keys with different cryptographic signatures, or aggregation of service endpoints with different links.

[0263] Figure 15B Different passes are shown, including concatenations associated with multiple digital identifiers based on relationship representations of different products associated with the product stages of the tire value chain. Among these passes, one pass is associated with a tire. In this particular example, a hash value is used for the concatenation associated with multiple decentralized identifiers. Figure 15A The dataset used to generate hash values ​​is schematically shown in Figure .

[0264] Raw material passes can be provided to intermediate product producers who use raw materials to produce intermediate products. Raw materials and intermediate products can include Figures 3 to 6CThe raw materials and intermediate products described in the context of . The raw material pass can be connected to the hash value "Hash1". The hash value "Hash1" can be generated via a hash algorithm such as MD5, SHA-1, SHA-2, SHA-3 or any other suitable algorithm based on a one-way function that cannot be reverse engineered. The hash value "Hash1" can be generated based on the data included in or connected to the raw material pass. The data used for hash generation may include a decentralized identifier and data related to the raw material data. The data used for hash generation may include a decentralized identifier associated with the raw material, data related to the raw material and / or encrypted information connected to the digital identifier. The hash value "Hash1" can be used by participating nodes in the tire value chain to check the integrity of the data packet transmitted from the raw material supplier to, for example, the intermediate product producer.

[0265] Similar to the raw material pass, the intermediate product pass can be provided to the tire producer who uses the intermediate product to produce the tire. The generation of the tire pass can be based on the intermediate product pass provided to the tire producer who uses the intermediate product to produce the tire. The tire pass can be connected to one or more hash values ​​"Hash 4", "Hash 5". The hash values ​​"Hash 4", "Hash 5" can be generated via hash algorithms such as MD5, SHA-1, SHA-2, SHA-3, or any other suitable algorithm based on a one-way function that cannot be reverse engineered. The hash values ​​"Hash 4", "Hash 5" can be generated based on the data included in or connected to the intermediate product pass and / or the raw material pass. (Multiple) hash values ​​"Hash 4", "Hash 5" can be generated based on the plaintext data itself or based on (multiple) hash values ​​generated from the plaintext data. For example, Hash 5 can be generated based on the intermediate product pass data and the tire pass data or based on hashed intermediate product data and hashed tire pass data. The data used for hash generation may include a decentralized identifier associated with an intermediate product used to produce the tire, a decentralized identifier associated with the tire, data related to the intermediate product, and / or data related to the tire.

[0266] The concatenation associated with the plurality of decentralized identifiers may relate to decentralized identifiers associated with the vehicle, the tire, and the precursor material(s) used to produce the tire. Hash data associated with or included in the respective pass may provide such a concatenation. The data used for hash generation may include Figure 15A Data mentioned in the context of Figure 15A As shown, a hash value "Hash4" associated with the tire pass can be generated. Figure 15AAs shown, a hash value "Hash5" can be generated that is associated with the intermediate product pass and the tire pass. The hash value(s) can be used by participating nodes in the tire value chain to verify the integrity of the transmitted data packets. The combined hash value(s) can be further used by participating nodes in the tire value chain to determine the relationships between products at different stages and verify the integrity of such relationships.

[0267] like Figure 15A and Figure 15B As shown, the hash value(s) may be linked to a pass associated with one or more product stages of the tire value chain.

[0268] Figure 16A An anchoring configuration for different passes generated in the tire value chain is shown. A vehicle pass can be generated for a vehicle. Separate passes can be generated for multiple additional product stages in the tire value chain and embedded in or linked to the vehicle pass. Pass generation can include providing a decentralized identifier and data related to the corresponding product data for each of the multiple product stages. Pass generation can further include providing an authentication mechanism. These passes for multiple product stages can be based on cryptographic signatures. For example, these passes for multiple additional product stages can be cascaded by hash values ​​based on different data sets. Figure 16A As shown, Hash 1 can be based on the data of the raw material pass, Hash 2 can be based on the data of the chemical product pass, and Hash 3 can be based on the data of the raw material pass plus the data of the chemical product pass. Similarly, Hash 4 can be based on the data of the tire pass, and Hash 5 can be based on the data of the chemical product pass and the tire pass. Further combinations of passes can be cascaded up to Hash 7, which can cascade the tire pass and the vehicle pass. Further combinations of passes can be cascaded up to Hash 7, which cascades all passes all the way to the vehicle pass. The sequence of hashes from Hash 1 to Hash 7 can be viewed as a "mirror" of the value chain from raw materials to vehicles, as it reflects the relationship between the various passes. Cascading via cryptographically signed hashes is just one example cascade. Other examples include permission aggregation of different ranges of data that can be embedded in sub-passes, aggregation of public keys with different cryptographic signatures, or aggregation of service endpoints with different links.

[0269] Figure 16B Different passes are shown, including concatenations associated with multiple decentralized identifiers based on relationship representations of different products associated with the product stages of the tire value chain. Among these passes, one pass is associated with a tire. In this particular example, a hash value is used for the concatenation associated with the multiple decentralized identifiers. Figure 16A The dataset used to generate hash values ​​is schematically shown in Figure .

[0270] The intermediate product pass can be provided to tire manufacturers who use the intermediate product to produce tires. The intermediate product pass can be connected to the intermediate product pass. Figure 16A The hash value is generated as described in the context of Hash2.

[0271] Similar to the intermediate product pass, the tire pass can be provided to the vehicle manufacturer who uses the tire for the vehicle. Figure 16A For passes, up to vehicle passes, hash values ​​can be generated in a similar manner.

[0272] In an anchored configuration, a vehicle pass may include a hash value associated with a pass associated with a product used to produce a vehicle (such as a tire). In this case, the cascade associated with multiple decentralized identifiers may involve decentralized identifiers associated with (multiple) raw materials, (multiple) intermediate products and (multiple) tires. The cascade may be provided by hash data associated with or included in the respective pass. The data used for hash generation may include any data included in the respective pass. The hash value "Hash6" may be based on at least the decentralized identifier associated with the vehicle pass and the data associated with the vehicle data. The hash value "Hash7" may be generated for passes associated with products of different product stages, such as Figure 16A The combined hash value "Hash 7" can be used by participating nodes in the tire value chain to determine the relationship between products at different stages and check the integrity of this relationship.

[0273] like Figure 16A and Figure 16B As shown, the hash value(s) may be linked to a pass associated with one or more product stages of the tire value chain.

[0274] Figure 17A A fully embedded configuration of different passes generated in the tire value chain is shown. Separate passes can be generated for multiple product stages in the tire value chain. Pass generation can include providing a decentralized identifier and data related to the corresponding product data for each of the multiple product stages. Pass generation can further include providing an authentication mechanism. These passes for multiple product stages can be based on cryptographic signatures. For example, these passes for multiple product stages can be cascaded by hash values ​​based on different data sets. Figure 17AAs shown, Hash 1 can be based on data from a raw material pass. Hash 2 can be based on data from both the raw material pass and the intermediate product pass. Further concatenation can be performed for other combinations of passes, up to Hash 7, which cascades the product all the way to the vehicle pass. Concatenation via cryptographically signed hashes is just one example. Other examples include aggregation of permissions for different ranges of data that can be embedded in sub-passes, aggregation of public keys with different cryptographic signatures, or aggregation of service endpoints with different links.

[0275] Figure 17B Different passes are shown, including concatenations associated with multiple decentralized identifiers based on relationship representations of different products associated with the product stages of the tire value chain. In these passes, a digital access element is associated with the tire. In this particular example, a hash value is used for the concatenation associated with the multiple decentralized identifiers. Figure 17A The dataset used to generate hash values ​​is schematically shown in Figure .

[0276] The intermediate product pass can be provided to tire manufacturers who use the intermediate product to produce tires. The intermediate product pass can be connected to the intermediate product pass. Figure 17A The hash value Hash2 is generated as described in the context of . Similar to the intermediate product pass, the tire pass can be provided to the vehicle manufacturer who uses the tire to produce the vehicle. The hash value can be as described in Figure 17A For passes, up to vehicle passes, hash values ​​can be generated in a similar manner.

[0277] In a fully embedded configuration, a combined hash value may be generated from passes associated with all products preceding the corresponding product (e.g., a vehicle). In this case, the cascade associated with multiple decentralized identifiers may involve decentralized identifiers associated with all previous products (e.g., raw material(s), intermediate product(s), and tire(s). The cascade may be provided by hash data associated with or included in the corresponding pass. The data used for hash generation may include any data included in the corresponding pass. For example, the hash value "Hash 5" may be based at least on decentralized identifiers associated with products up to and including tire passes. For example, the hash value Hash 7 may be based at least on decentralized identifiers associated with products up to and including vehicles. The combined hash values ​​"Hash 3," "Hash 5," and "Hash 7" may be used by participating nodes of the tire value chain to determine the relationship of products at different stages and to check the integrity of such relationships. As Figure 17A and Figure 17B As shown, the hash value(s) may be linked to a pass associated with one or more product stages of the tire value chain.

[0278] Figures 15A to 17B The configuration shown involves passes generated in the tire value chain up to vehicles. Similarly, passes generated in the recycling chain from tires to recyclables (various recyclables) can be cascaded. Furthermore, passes generated in the tire value chain up to vehicles and in the recycling chain from tires to recyclables (various recyclables) can be cascaded similarly. In this way, the circularity of products involving tires can be virtually represented and tracked.

[0279] Figure 18A and Figure 18B Shows examples of how to generate cascaded relational representations, for example, Figures 15A to 17B The cascade described.

[0280] Relationship representation can involve tire value chain (such as Figure 3 The different stages of the tire value chain described in the context of FIG. Passes to different stages of the tire value chain can be connected to relationship representations. The relationship representation can be associated with the product produced at the corresponding stage of the tire value chain and at least one product used to produce the corresponding product. The relationship representation can be associated with the product produced at the corresponding stage of the tire value chain and at least one product produced at the previous stage of the tire value chain. The relationship representation can specify the relationship between physical entities. The relationship representation can specify Figure 18A The second physical entity shown can be used to produce the first physical entity and / or Figure 18B The first physical entity shown can be produced by using the second physical entity. The relationship representation can relate to at least one intermediate product used to produce a tire. The relationship representation can relate to a tire produced by using at least one intermediate product.

[0281] Figure 19 An example embodiment of a donut-shaped tire loop 1934 including participants 1902 - 1918 connected by a decentralized network 1934 having decentralized network nodes 1920 - 1932 associated with the participants 1902 - 1918 is shown. Figure 19 The example embodiments shown may include Figures 6A to 6C Part of the tire ecosystem shown in .

[0282] Figure 19The participant network shown can be a material chain network. The material chain network can include one or more linear material chains, such as (multiple) production chains and / or (multiple) use chains. (Multiple) linear material chains can include (multiple) material production chains, in which tires or their components are produced by tire producer 1902 and used by tire producer 1908 to produce tires. (Multiple) linear material chains can include a material recycling chain, in which used tires are collected, sorted and recycled to recyclers 1918, and the recyclables are used by material producer 1902 to produce new materials. The material chain can include one or more production chains and / or use chains. (Multiple) use chains can include one or more recycling chains and / or one or more reuse chains. The material chain can include one or more connected production chains and / or use chains. One or more linear material chains can be connected to material cycle 1934.

[0283] The material chain network may include a material circulation network 1934, which includes the use of (multiple) recycled materials to produce new materials. One or more material cycles 1934 can allow the use of materials generated by the recycling of scrap tires to produce new products associated with one or more material chains, such as chemical products or materials. The material chain network (preferably material cycle 1934) can include the production, use, reuse and / or recycling of physical materials or products containing such materials. The product can be a material, a chemical product, an intermediate chemical product, a discrete component containing a material, an assembly of discrete components, a final product, a scrap product, a product to be recycled, a recycled product or a recyclate. To be processed, produced, recycled, etc. herein indicates that it is one of the next production steps included in the production chain of the output material. For example, the material to be recycled herein means that the next production step in the production chain of the output material is a recycling step. In some embodiments, it is the next step in processing the material.

[0284] A material or chemical product may refer to a chemical compound, a chemical component, a chemical molecule, a chemical composition, a chemical mixture, a chemical formulation, an intermediate chemical product, or a chemical base material that can be used to produce a discrete product. A chemical material or product stream may include a non-discrete material stream that can be further processed to produce a discrete product or component. A chemical material or product stream may include a liquid, a pellet, a beat, a powder, etc. A discrete product may refer to a discrete component, an assembly of discrete components, a final product, a scrapped product, a product to be recycled, or a recycled discrete product.

[0285] Chemical materials or products can be produced using raw materials and / or recyclates. Recyclates can refer to materials that are mechanically or chemically recycled. Recyclates or recycled material streams can include non-discrete material streams that can be further processed to produce new materials or chemical products. Recyclates or recycled material streams can include liquids, pellets, beats, powders, etc. Raw materials can refer to the starting materials used to produce materials or chemical products, such as (multiple) virgin raw materials. Virgin raw materials can be unused raw materials that have not been processed in any way except for production.

[0286] An end product may refer to a product that is the result of a material chain. An end product may refer to a product that is used by an end product user. An end-of-life (EOL) product may refer to a product that has been used by an end product user. An end-of-life product may refer to a product that no longer meets its use requirements. An end-of-life product may refer to a product that is no longer needed. An end-of-life product may be a product that is disposed of as waste, such as plastic waste. A recycled product may refer to any product or material that has been produced using end-of-life product(s). A reclaimed product may refer to a new product or material that has been produced using end-of-life product(s).

[0287] Figure 19 The material cycle 1934 shown may include multiple participants 1902 to 1918 forming the material cycle 1934. The material cycle 1934 may include all stages of the material, from the production of the material through the use of the material to the reuse of the material. Thus, the material may flow in a closed loop from the production of the component through the use of the final product to reuse. Reuse may include reusing the scrap product, refurbishing the scrap product, and / or recycling the scrap product to feed the recyclables back into the material production.

[0288] The participant(s) 1902 to 1918 of the material cycle may be associated with the production of any material or product and / or the recycling of any material or product. The participant(s) of the material cycle 1934 may include input material producer(s) 1906, chemical product producer(s) 1906, tire producer 1908, original equipment manufacturer (OEM) 1912, end product user 1914, EOL collector / sorter 1916, recycler 1918, or a combination thereof. The participant(s) may include any of the following: Figure 19 Various participants (multiple) not shown in .

[0289] Participants 1902 to 1918 in material cycle 1934 may be connected by material flow(s) 134. Material flow 1940 may correspond to the flow of a product or material from one participant 1902 to 1918 in the material cycle to a corresponding downstream participant 1902 to 1918 in material cycle 1934. Material flow 1940 may refer to a continuous or discontinuous flow of a product or material. A product or material flow may include any means of transport suitable for transporting a product from one participant 1902 to 1918 to another downstream participant 1902 to 1918. Transport means may include the use of packaging materials. Material flow 134 may be a unilateral flow, such as a directional material flow 1940. Material flow 1940 may flow from an upstream participant 1902 to 1918 in material cycle 1940 to a downstream participant 1902 to 1918, such as material flow 1940 from a recycler 1918 to a chemical product producer 1902. The material flow may include a reverse material flow 1940 from downstream participants 1902 to 1918 of the material cycle 1934 to upstream participants 1902 to 1918. For example, when a recycled product or recyclate does not meet quality specifications and requires further processing, material may flow 1940 from a chemical product producer 1902 to a recycler 1918.

[0290] Material stream 1940 can be associated with raw materials (e.g., virgin raw material(s)) used to produce materials or chemical products. Material stream 1940 can include recycled material(s) instead of or in addition to virgin raw material(s). Raw materials and recycled materials can be provided to chemical product producers for use in producing material(s), chemical product(s), and / or intermediate chemical product(s) (not shown).

[0291] Figure 19 The material circulation 1934 shown can be based on the example of a tire and its annular circulation. Figure 1 and Figure 2 An example of such a tire is shown in FIG. Participants may include input material producer(s) 1906, chemical product producer 1902, tire producer 1908, OEM 1912, end product user 1914 (e.g., consumer), waste collector and / or sorter 1916, recycler 1918 (e.g., recycler), or reuse operator (e.g., retreader (not shown)).

[0292] Tires can be produced by tire producers 1908. Tires can be produced from raw material streams and / or from recycled material streams 1944. Tires can be produced from chemical product(s) received from chemical product producers 1902. Tires can be produced from input material(s) received from input material suppliers 1906 (not shown). The produced tires can be provided to OEMs 1912. OEMs 1912 can use the supplied tire(s) to produce end products, such as vehicles including tires. The end products produced by OEMs 1912 can be provided to end product users 1914. Users use the end products including tires and, therefore, the tires. During use, maintenance can be performed on the tires, for example, by a vehicle maintenance workshop. If the tires are no longer usable in a vehicle, they can be removed from the vehicle and provided to a waste collector and / or sorter 1916. The collected used tires can be sorted by an EOL collector / sorter 1916. The sorter can separate the used tires into different parts. A portion of the sorted tires may contain reusable tires, such as tires that can be retreaded. Another portion of the sorted tires may contain recyclable tires. This sorted portion may be provided to a recycler 1918 to recycle the scrap tire portion. Circular material flow 1944 may close the loop between the participants.

[0293] In addition to being connected via material flow 1940, participants 1902 to 1918 in circular material cycle 1934 can be connected via data flow 1936 via a decentralized network 1938. Decentralized network 1938 can include one or more decentralized network nodes 1920 to 1932 associated with participants 1902 to 1918 in material cycle 1934. In a decentralized or distributed network 1938, in contrast to a centralized network, decentralized network nodes 1920 to 1932 are not exclusively dependent on a central network node. In other words, no single entity is the sole authority of the network. Decentralized network 130 can include both decentralized network nodes and a central network node. Decentralized network 1938 can include a central network node that can control and / or monitor decentralized network nodes 1920 to 1932. For example, the central network node(s) may provide authentication information that allows at least two decentralized network nodes 1920 to 1932 to establish a peer-to-peer communication channel between the respective decentralized network nodes 1920 to 1932 .

[0294] Network nodes 1920 to 1932 can be computing nodes. A computing node can be any device or system that includes at least one physical, tangible processor and a physical, tangible memory capable of having computer-executable instructions executed by the processor. The forms of computing nodes are now becoming increasingly diverse. Computing nodes can be, for example, handheld devices, monitoring systems, control systems, laptop computers, desktop computers, mainframes, and / or data centers. The memory can take any form and depends on the nature and form of the computing node. Decentralized network nodes 1920 to 1932 can be connected via wired and / or wireless connections (such as one of Ethernet, USB, LAN, WLAN, etc.). Wireless communication can use, for example, WLAN, Wi-Fi, cellular, and / or Bluetooth. Decentralized network nodes 1920 to 1932 can be configured to perform peer-to-peer data transactions as shown by arrows 1936 indicating data flow.

[0295] Decentralized network nodes 1920-1932 can be configured as data-consuming network nodes and / or data-providing network nodes. Decentralized network nodes 1920-1932 can be configured to provide data to other network nodes (multiple) of decentralized network 1938 and / or consume data from other nodes of decentralized network 1938. For example, decentralized network node 1924 associated with tire producer 1908 can be configured to provide tire data to downstream participants (such as OEM 1912 or recycler 1918). Further, for example, decentralized network nodes 1930, 1932 associated with EOL collector / sorter 1916 or recycler 1918 can be configured to access data from network nodes 1920-1932 associated with upstream participants (such as tire producer 1908).

[0296] The decentralized network node(s) 1920-1932 may include computer executable instructions configured to provide, consume, and / or process data, such as data associated with machine fluids or machines produced or processed within the circular material loop 126. The network node(s) may operate a data provisioning service configured to provide data to another decentralized network node 1920-1932 of the decentralized network 1938. The decentralized network node(s) 1920-1932 configured to provide data may be associated with a data owner or data generating node associated with a material or product produced or processed within the circular loop 1934. The decentralized network node(s) 1920-1932 may be connected to one or more dedicated data storage devices that store data associated with the material or product produced or processed in the circular loop 1934 (see, e.g., Figure 12).(multiple) dedicated data storage devices can be under the control of a data owner or data generation node that is associated with a material or product produced or processed in the ring loop 1934. The data owner can be the corresponding participant 1902 to 1918 of the ring loop 1934 to which the data generation nodes 1920 to 1932 are associated. The data generation nodes 1920 to 1932 can access(multiple) dedicated data storage devices. Therefore, access to data associated with the material or product produced or processed within the ring loop 1934 can be under the control of the data owner associated with the corresponding decentralized network node 1920 to 1932. This allows full control to be maintained over the data associated with the material or product produced or processed by the data owner within the ring loop 1934. At the same time, this enables the sharing of data associated with the material or product produced or processed within the ring loop 1934 under controlled conditions, for example by establishing peer-to-peer communication using an appropriate protocol including an authorization and authentication mechanism or scheme.

[0297] Decentralized network nodes 1920-1932 configured to consume data may include computer-executable instructions for accessing and / or processing data within decentralized network 1938, such as data associated with materials produced or processed within circular loop 1934 and provided by decentralized data-providing network nodes 1920-1932. Decentralized data-consuming network nodes 1920-1932 may be controlled or owned by or associated with any upstream or downstream participant in circular material loop 126.

[0298] The decentralized network 1938 may include additional decentralized network nodes. The additional decentralized network nodes may not be associated with the additional participants of the circular loop 1934. The additional nodes may be decentralized infrastructure service nodes ( Figure 1(not shown in the figure). The decentralized infrastructure service node can provide services to the decentralized participating nodes 1920-1932, such as verifying the identity of the decentralized network participating nodes 1920-1932 before performing data exchange. The decentralized network participating node(s) 1920-1932 may include or be associated with certificate(s), such as X.509 certificates. The certificate(s) may be associated with an identity manager, which may include, for example, a certificate issuance service and / or a dynamic provisioning service that provides dynamic attribute tokens (e.g., OAuth access tokens). In this way, the decentralized network node(s) 1920-1932 may be associated or connected to a unique identifier embedded in the X.509 certificate that identifies the corresponding decentralized network node(s) 1920-1932. The information required to verify the certificate may be provided via an authentication registry associated with the certificate issuance service and / or the dynamic provisioning service. For example, in the IDSA reference architecture model version 3.0 from April 2019, decentralized data providing network nodes associated with data owners, certificate authorities (CAs), dynamic attribute provisioning services (DAPS), and decentralized data consuming network nodes associated with data consumers are used to verify identities (not shown) before performing data exchange.

[0299] The materials or products produced by the participant(s) 1902-1918 of the circular loop 1934 can be associated with tire data associated with characteristics of the tires or components thereof produced by the participant(s) 1902-1908 of the circular loop 1934. The tire data can be provided for access by a decentralized data-providing network node 1924 associated with the tire producer. Access to the tire data can be controlled by the decentralized data-providing network node 124. The tire data can be accessed by a decentralized data-consuming network node(s) 1920-1932 associated with additional participants 1902-1918 of the loop 1934 (such as any downstream participants 1902-1918).

[0300] Data flows 1936 between decentralized network nodes 1920 through 1932 can be directly or indirectly associated with material flows 1940 between participants 1902 through 1918 of material cycle 1934. For example, if tire data associated with tires provided from tire producer 1908 to OEM 1912 is accessed by decentralized data-consuming network node 1926 associated with OEM 1912, data flows 1936 can be directly associated with material flows 1940. For example, if tire data associated with tires produced by tire producer 1908 is accessed by decentralized data-consuming network node 1932 associated with recycler 1918, data flows 1936 can be indirectly associated with material flows 1940.

[0301] Data transactions between decentralized network nodes 1920 to 1932 can be based on decentralized identifiers associated with the material or product data to be accessed. The decentralized identifier can be associated with the physical entity of the material or product. The decentralized identifier can be uniquely associated with the physical entity of the material or product. The decentralized identifier can uniquely identify the material or product within the decentralized network 1938. The decentralized identifier can be associated with (multiple) additional decentralized identifiers, such as (multiple) decentralized identifiers of (multiple) materials or (multiple) products used to produce a final product. This can allow tracking of (multiple) materials or (multiple) products used to produce a product (such as a final product). The decentralized identifier can be included in, for example, Figure 13 The access element associated with the material or product is described in more detail in the context of the

[0302] In particular, the generation of access elements associated with data related to the production and / or use of tires or their components and generated for each stage of the tire production chain allows the monitoring of characteristics that are critical for the recycling and / or reuse of used tires through a decentralized network. This monitoring is performed by providing access to tire data, as will be described below. Figures 20 to 23 This is described in more detail by way of examples.

[0303] Figure 20 An example method for monitoring at least one tire characteristic that is critical to the reuse and / or recycling of the tire or components thereof by at least one participant of a decentralized network is presented.

[0304] Tire data related to the production of tires or their components can be collected. Tire data can be collected before, during, and / or after the production of tires or their components. In this context, a component can include any discrete or non-discrete component produced by any participant in the tire production chain, such as a monomer, polymer, steel, filler, a component produced using a monomer or polymer, or a tire, polymer, or component produced using a monomer. A tire can refer to the end product of the tire production chain. A component can refer to any stage in the tire production chain. The tire production chain can include various stages, such as raw materials or recyclates used to produce monomers and / or polymers, intermediate materials or components, discrete components, or assemblies of discrete components used to produce tires.

[0305] Data may be generated in association with one or more network nodes 1920 to 1924, such as data associated with data generation node(s) associated with respective producers 1902 to 1908. The data may relate to different stages of the tire production chain for a tire. The data may relate to the production of monomers, polymers, the use of polymers and / or monomers in the production of components, or tires produced using the produced monomers or polymers and / or components. The data may be specific to the produced monomers, the produced polymers, any produced non-discrete or discrete components, or tires produced using the produced monomers, polymers, or any non-discrete or discrete components. The data may be specific to individual entities or batches of produced monomers, produced polymers, any produced non-discrete or discrete components, or tires produced using the produced monomers or any non-discrete or discrete components.

[0306] Tire data may include data associated with at least one characteristic critical to the recycling and / or reuse of used tires. A characteristic may represent a critical component or substance associated with one or more recycling processes and / or one or more reuse processes. A critical component or substance may be a component or substance that affects the quality of recyclate that can be produced by the recycling process. For example, in the case of producing pyrolysis oil for use in a steam cracking unit, a critical component may hinder the operation of the steam cracking unit. Components may include contaminants associated with the pyrolysis oil used in a steam cracking unit. Contaminants may include sulfur, halogens, oxygen, phosphorus, metals, and inorganic substances such as aluminum, antimony, barium, chromium, calcium, copper, iron, potassium, sodium, lead, silicon, titanium, zinc, arsenic, mercury, nickel, vanadium, or combinations thereof. The presence of these contaminants in the pyrolysis oil may adversely affect the operation of the steam cracking unit. These characteristics may represent characteristics critical to reuse operations. Such characteristics may relate to substances critical to reuse. Such characteristics may indicate tire types that are critical to reuse. Such characteristics may indicate the number of retreading operations that are permissible.

[0307] The data may include (multiple) decentralized identifiers associated with one or more production inputs used to produce the tire or its components. The data may relate to one or more production inputs of respective entities in a production chain used to produce the tire. Collecting data related to the production of the tire or its components may include collecting (multiple) decentralized identifiers associated with one or more production inputs used to produce the tire or its components. The decentralized identifiers associated with one or more production inputs used to produce the tire or its components may be collected by reading an identifier element (such as a barcode or QR code) attached to the production input.

[0308] Tire data may include characteristic data. The characteristic data may relate to or include characteristics of the plastic product or its components. The characteristics of the plastic product or its components may include performance characteristics, chemical characteristics (such as flammability, toxicity, acidity, reactivity, heat of combustion, etc.), and / or physical characteristics (such as density, color, hardness, melting point, boiling point, electrical conductivity, etc.).

[0309] By collecting tire data related to the production and / or use of tires or their components at each production stage of the product chain, a digital twin of the corresponding entity produced by one or more production participants in the tire production chain can be generated. In this way, the entity can be tracked in the tire production chain from raw materials or recyclate to tire.

[0310] Data related to the production and / or use of tires or their components may be stored in dedicated storage devices associated with the respective production participants in the tire production chain that produce the tires or their components. Data related to the production of tires or their components may include different datasets related to the production and / or use of tires or their components. Such datasets may be referred to as the datasets described above.

[0311] One or more decentralized identifiers may be provided that are associated with the tire or its components being produced. One or more decentralized identifiers may be provided that are associated with the production input(s) used to produce the tire. One or more decentralized identifiers may be uniquely associated with the physical entity of the tire or its components being produced. One or more decentralized identifiers may be uniquely associated with any entity produced by any participant in the production chain. One or more decentralized identifiers may include any unique identifier that is uniquely associated with the tire or its components, the production participant(s) in the production chain of the production entity, and / or data related to the production of the tire or its components. Decentralized identifiers may include or relate to one or more universally unique identifiers (UUIDs) or digital identifiers (DIDs). Via the decentralized identifier(s) and the unique association with the plastic article or its components, the producer and / or data access to the data may be controlled by the producer. This contrasts with a centralized mechanism approach in which identifiers are provided by such a centralized mechanism and access to the data is controlled by such a centralized mechanism. In this context, decentralized means that the use of identifiers is controlled by the data owner at the time of implementation.

[0312] The decentralized identifier(s) may include one or more identifiers used in a decentralized network and enabling data exchange or peer-to-peer communication via the decentralized network. Data exchange may include discovering decentralized identifiers of participating nodes of the decentralized network, authenticating participating nodes of the decentralized network, and / or authorizing data transmission via peer-to-peer communication between participating nodes of the decentralized network. The decentralized identifier(s) may be associated with any participant in a production chain and the corresponding entity produced by such participant.

[0313] One or more data sets may be generated using the collected tire data. The one or more data sets may include at least a portion of the collected tire data. The one or more data sets may include data point(s) or a collection of data points included in the collected tire data. The one or more data sets may be associated with the provided decentralized identifier(s) associated with the tire.

[0314] One or more relationship data sets may be generated. The relationship data set(s) may include the decentralized tire identifier(s) and the decentralized production input identifier(s). The relationship data set(s) may include relationships that specify relationships between the decentralized identifiers. For example, a decentralized tire identifier may be assigned a parent identifier, and a decentralized production input identifier(s) may be assigned a child identifier.

[0315] Access data associated with one or more datasets may be generated. Access data may be generated for each dataset. The access data may point to the corresponding dataset. The access data may relate to a dedicated storage device associated with a production participant in a production chain producing tires or components thereof and storing the corresponding dataset(s). The access data may include a locator or pointer to the dedicated storage device, which is associated with the production participant in the production chain producing tires or components thereof and storing the corresponding dataset(s). The access data may include one or more digital links to the generated dataset(s). The access data may include a locator or pointer, such as an AM URL or URI, to a dedicated storage address, which is associated with a production participant in the production chain producing tires or components thereof and storing the corresponding dataset(s). The access data may include at least one interface to a data-providing network node or a data-providing service. The access data may include at least one interface to a data-consuming network node or a data-consuming service. The access data may include an endpoint for data exchange or sharing (resource endpoint) or an endpoint for service interaction (service endpoint), which may be uniquely identified via a data transaction protocol. The access data pointing to the generated dataset(s) may be uniquely associated with a decentralized identifier. The decentralized identifier may be connected to the access data of the generated dataset(s).

[0316] An access element may be generated that includes one or more decentralized identifiers and access data. An access element that includes access data associated with a set of (multiple) relationship data may be represented as a relationship access element. The access element may be associated with a tire or a component thereof. The access data may be provided to a data-consuming network node or a data-consuming service. The access data may be provided by a decentralized network database, a database associated with a data-consuming network node, a data-providing network node associated with a producer of a corresponding entity, or a combination thereof. The access data may include a locator or pointer for accessing the corresponding set of (multiple) relationship data.

[0317] The access element may further include one or more authentication mechanisms associated with the (multiple) decentralized identifiers and the (multiple) datasets. The one or more authentication mechanisms may be associated or linked to the (multiple) decentralized identifiers, such as (multiple) decentralized producer identifiers, (multiple) decentralized tire identifiers, (multiple) decentralized component identifiers, (multiple) decentralized polymer identifiers, or (multiple) decentralized monomer identifiers. The one or more authentication mechanisms associated with the (multiple) decentralized identifiers may be accessed by the (multiple) decentralized participating network nodes. The digital access element may further involve authorization information linked to the (multiple) decentralized identifiers. The authorization information may be associated with the (multiple) decentralized identifiers and the (multiple) datasets. The authorization information may include access rules that depend on the dataset to be accessed and the role of the accessing data consuming network node.

[0318] The access elements may be provided for accessing the dataset(s) by one or more data consuming network nodes under the control of a data providing network node associated with a manufacturer of a tire or component thereof. The access elements may be provided to a decentralized registry node, for example, as further described below. The decentralized registry node may store the decentralized access elements.

[0319] Figure 21 An example system for obtaining production- and / or usage-related tire data based on a decentralized tire identifier is presented. Figure 21 The system can be used to recursively collect access data at each production stage of a tire production chain and / or a tire usage chain, wherein the recursive collection is based on one or more relational datasets provided by one or more participants of the tire production chain. Figure 21 The system can be used to recursively request access rights to tire data from one or more participants (in particular each participant) of the tire production chain and / or the tire usage chain based on the collected access data. Figure 21 The system can be used to implement Figure 23 The method shown.

[0320] The tire may be provided in association with a digital access element. The tire 404 may be connected to a Figure 3 The tire identification can be read by the ID provider 2114. The ID provider 2114 can be a smartphone running a tire identification application. The data obtained by the code reading application can be used to determine the tire identification. Figure 12 The data obtained by the code reading application can be used to determine the distributed access element identifier (hereinafter referred to as DID1) described in the context of Figure 12 The decentralized tire identifier (hereinafter referred to as UUID1) described in the context of FIG. The ID provider 2114 may be configured to utilize the decentralized registration node 2102 to perform an authentication step. For example, the ID provider 2114 may access a decentralized IAM network node (not shown), and the decentralized IAM network node may be configured to provide an access token to the ID provider 2114 upon successful authentication. The access token may be used by the ID provider 2114 to access the decentralized registration node 2102. The ID provider 2114 may provide a decentralized participant identifier associated with a participant of the tire ecosystem to the decentralized IAM network node for authentication.

[0321] The ID provider 2114 may be configured to provide a decentralized tire identifier (e.g., UUID1) to the decentralized network node 2104. The ID provider 2114 may be configured to provide authentication data such as a decentralized participant identifier and, optionally, an access token to the decentralized network node 2104.

[0322] The decentralized network node 2104 may be configured to verify the authentication data received from the ID provider 2114 with the decentralized IAM network node 1 2106. Figure 23 , and after successful authentication, the decentralized network node 2104 can be configured to access the decentralized registration node 2102 using the decentralized machine identifier received from the ID provider 2114, and access the access element associated with the decentralized tire identifier. The access element may include a decentralized identifier and access data pointing to a corresponding relationship data set. The access data may point to a decentralized data providing network node associated with the corresponding relationship data set. For example, the access element associated with the tire may include access data pointing to (multiple) decentralized data providing network nodes associated with tire data of the tire. The decentralized network node 2104 or a decentralized data consuming network node (not shown) associated with the decentralized network node 2104 can be configured to access the corresponding (multiple) decentralized data providing network nodes associated with the access data, and request (multiple) relationship data sets associated with the (multiple) decentralized identifiers from the (multiple) decentralized data providing network nodes, for example, Figure 12 What is shown.

[0323] refer to Figure 22 , the relational dataset 2204 associated with the tire may include a decentralized tire identifier and decentralized identifier(s) associated with production input(s) used to produce the tire (such as rubber, steel, and monomer(s). The production input(s) are in turn associated with the digital twin.

[0324] The relational dataset may be included in the digital twin of tire 2202. The relational dataset associated with rubber 2210 may include a decentralized rubber identifier and decentralized production input identifiers associated with production inputs (such as monomers) used to produce the rubber. The relational dataset may be included in the digital twin of rubber 2208.

[0325] Return Reference Figure 21 And continue to refer to Figure 22 , the decentralized network node 2104 can be configured to determine the decentralized production input identifier(s) contained in the relationship data set(s). The decentralized network node 2104 can be configured to access the decentralized registration node 2102 using the determined decentralized production input identifier(s) to determine the access data associated with the decentralized production input identifier(s). The decentralized network node 2104 or a decentralized data consuming network node (not shown) associated with the decentralized network node 2104 can be configured to access the production input data using the corresponding decentralized production input identifier, the access data, and optionally the decentralized participant identifier provided by the ID provider 2114 from the corresponding decentralized data providing network node(s).

[0326] In this example, the decentralized network node 2104 may receive a decentralized tire identifier associated with a tire from the ID provider 2114. The decentralized network node 2104 may use the decentralized tire identifier to access the decentralized registration node 2102 to determine access element(s) associated with the decentralized tire identifier. The determined access element(s) may contain access data pointing to a decentralized data providing network node associated with the tire data. The tire data may be stored on a storage environment associated with the decentralized data providing network node 124 (1208). The tire data may include a relationship data set indicating decentralized production input identifier(s) associated with production input(s) for producing the tire (see also Figure 22). The decentralized network node 2104 or a decentralized data-consuming network node associated with the decentralized network node 2104 can be configured to access (multiple) relational data sets from the decentralized data-providing network node 124. The decentralized network node 2104 or a decentralized data-consuming network node associated with the decentralized network node 2104 can be configured to access tire data from the decentralized data-providing network node 124. Access to the tire data can be authorized based on the decentralized participant identifier provided by the ID provider 2114. Access to the tire data can be controlled by the decentralized data-providing network node 124 associated with the tire data. This ensures that the tire data can only be accessed by authorized participants of the tire ecosystem, thereby avoiding uncontrolled access to the tire data.

[0327] Decentralized network node 2104 can be configured to retrieve, from the accessed relational dataset, decentralized production input identifier(s) associated with the production input(s) used to produce the tire. Decentralized network node 2104 can be configured to use the determined decentralized production input identifier(s) to access, from decentralized registration node 2102, access element(s) associated with the decentralized production input identifier(s). Decentralized network node 2104 or a decentralized data-consuming network node can be configured to access the relational dataset(s), for example, from decentralized data-providing network node(s) 2108 to 2112 associated with the production input(s). The production input data can be stored in a storage environment (DT storage devices 2 to 4, 2116 to 2120) associated with decentralized data-providing network nodes 2108 to 2112. Decentralized network node 2104 or a decentralized data-consuming network node can be configured to access the production input data as previously described.

[0328] The decentralized network node 2104 can be configured to retrieve the decentralized material identifier(s) associated with the material used to produce the production input (e.g., monomer) from the accessed relational dataset(s). The decentralized network node 2104 can be configured to use the determined decentralized identifier(s) to access access elements associated with the decentralized identifier(s) from the decentralized registration node 2102. The decentralized network node 2104 or a decentralized data consuming network node can be configured to access the relational dataset(s).

[0329] Thus, decentralized network node 2104 can be configured to determine a bill of materials tree associated with a tire based on the accessed relational dataset(s) and the links between the starting materials and the decentralized identifier(s) of the resulting products / intermediates. The bill of materials tree can represent the relationships among all materials used to produce the tire. Thus, recursively determining the decentralized identifier(s) using the relational representation(s) allows for obtaining tire data and characteristics that are critical for recycling and / or reuse of used tires.

[0330] The material data collected by the decentralized network nodes 2104 may be provided to an ID provider 2114. The ID provider 2114 may provide the collected data to a system configured to monitor characteristics critical to recycling and / or reuse and / or to generate reuse and / or recycling instructions based on characteristics critical to recycling and / or reuse contained in the collected tire data.

[0331] Figure 23 A method for obtaining tire data based on (multiple) decentralized product identifiers and relationships is presented. The method can be implemented in a decentralized network, such as Figure 19 The method can be described in the context of Figure 22 system implementation.

[0332] A decentralized identifier associated with a decentralized network participant can be provided to a decentralized network node that provides access to data of, for example, a producer of a tire chain, such as e.g. Figure 19 The decentralized network participants can be production participants in the tire production chain. Figure 19Any participant in the material cycle (e.g., including the production chain and the recycling chain) shown in the example of FIG. The decentralized identifier associated with the decentralized network participant requesting access may include a string of characters and / or a number. The decentralized identifier associated with the decentralized network participant requesting access may be associated with an authentication scheme (e.g., a private-public key scheme). Using the decentralized identifier associated with the decentralized network participant requesting access improves security regarding access to tire data, as access to the tire data may be restricted, and only defined decentralized network participants may be allowed to access such data. The decentralized identifier associated with the decentralized network participant requesting access may be provided to a decentralized identity management access node of the decentralized network. The decentralized identity management access node may be configured to perform an authentication step using a provider of decentralized participant identifiers. If authorization is successful, the decentralized identity management access node may provide an access token. This access token may be presented to the decentralized network node providing access to the data. Authentication ensures that the collection of data related to the production of plastic products or components thereof using the decentralized network node requesting access can only be initiated by an authenticated decentralized network participant. This results in increased security, as it prevents the complete bill of materials tree of a product or a portion thereof, which may contain sensitive data regarding supply chain information, from being obtained by unauthorized entities.

[0333] The decentralized network node requesting access may obtain access element(s) based on decentralized identifier(s) associated with the tire, one or more components of the tire, or a combination thereof, provided to the decentralized registration node. The decentralized registration node may store information such as Figure 20 (Multiple) decentralized identifiers associated with (multiple) access elements described in the context of.

[0334] A decentralized network node requesting access may access the decentralized registry using the decentralized identifier(s) associated with the tire or component thereof to determine the identity of the tire or component thereof. Figure 22 The access element associated with the (multiple) decentralized identifiers described in the context of .

[0335] Decentralized network nodes requesting access to data can be configured to Figure 22 The access element retrieved from the decentralized registry node described in the context of access to access (multiple) relational datasets. The (multiple) digital relational datasets may specify (multiple) relationships between tires or their components and production inputs (such as materials) used to produce the tires or their components, such as Figure 22As shown. (Multiple) relational data sets can be directly or indirectly associated with a decentralized identifier associated with a tire or a part thereof. This allows the use of a decentralized identifier associated with a tire or a part thereof to determine the corresponding (multiple) relational data sets. (Multiple) relational data sets can specify that a tire or a part thereof is produced using a production input (such as a material) and / or that a tire or a part thereof is produced using a material. (Multiple) relational data sets can be associated with a relationship between a tire or a part thereof and each production input (such as a material) used to produce the tire or a part thereof, for example using a decentralized identifier associated with the tire and (multiple) material identifiers associated with all production inputs (such as materials) used to produce the tire or a part thereof. Thus, such a relational data set can also specify raw materials and intermediate products used in the production of a tire or a part thereof. (Multiple) relational data sets can be associated with a relationship between (multiple) input materials and (multiple) output materials of a single production step or stage of a production chain. Such a relationship can be linked to reflect the entire product production chain. For example, in Figure 22 An example of a relational dataset(s) that can be used to determine decentralized material identifier(s) is shown in Determining decentralized identifier(s) associated with a tire or a component thereof using the relational dataset(s) can allow for construction of a bill of materials tree structure for the tire or a component thereof.

[0336] The decentralized sub-identifier(s) associated with a decentralized tire identifier can be determined based on the obtained relationship dataset(s). The decentralized tire identifier can be considered a decentralized parent identifier. The decentralized sub-identifier(s) can correspond to material identifier(s) associated with the material used to produce the tire or its parts. The relationship dataset can contain one or more decentralized sub-identifiers. The relationship dataset can include the decentralized tire identifier. This allows the decentralized tire identifier to be linked to the corresponding sub-identifier(s).

[0337] Whether to retrieve data associated with the decentralized sub-identifier(s) can be determined based on a decentralized sub-identifier with additional sub-identifiers. For example, if the sub-identifier(s) are associated with tire data related to characteristics critical to the recycling and / or reuse of the tire or its components, the data can be retrieved. If the sub-identifier(s) are not associated with tire data related to characteristics critical to the recycling and / or reuse of the tire or its components, the data cannot be retrieved. This determination can be made based on data provided to the decentralized network node. For example, data associated with a defined dataset (hereinafter also referred to as an asset) can be provided, and this data can be used to determine whether to retrieve additional data. The dataset can relate to tire data related to characteristics critical to the recycling and / or reuse of the tire or its components. The tire data can include one or more datasets related to characteristics critical to recycling, recyclate use, and / or each decentralized participant identifier associated with a data-consuming network node requesting access to the tire data. The tire data can also include one or more datasets related to characteristics critical to reuse, reuse, and / or each decentralized participant identifier associated with a data-consuming network node requesting access to the tire data. Based on this information provided to the registration node and / or data providing network node, a determination can be made as to whether data should be provided. If tire data related to characteristics critical to the recycling and / or reuse of tires or their components is to be obtained, the method obtains the data. Otherwise, the method proceeds to check the decentralized sub-identifier.

[0338] Production-related data, such as tire data, can be obtained based on the determined decentralized sub-identifier(s). The production-related data (e.g., tire) can be obtained from a decentralized data-providing network node associated with the production-related data. The corresponding decentralized data-providing network node can be determined by the decentralized network node using the determined decentralized sub-identifier(s). For example, the decentralized sub-identifier(s) can be associated with access data pointing to data related to production or a portion thereof. The access data can correspond to an endpoint address associated with the corresponding decentralized data-providing network node. The access data can be stored on a decentralized registration node and can be determined using the previously determined decentralized sub-identifier(s). The access data can be used to access the tire data at the decentralized data-providing network node associated with the digital representation. The decentralized data-providing network node can be associated with a storage environment storing the tire data. The decentralized data-providing network node can be associated with a data owner of the tire data. The decentralized data-providing network node can be associated with the manufacturer of the corresponding tire or component thereof. Data exchange can be performed after a corresponding authentication and authorization process. Authorization can be based on a decentralized participant identifier. For example, the decentralized data providing network node can determine whether the tire data can be accessed using authorization or access rules associated with the provided decentralized participant identifier. The accessed tire data can be transmitted to and stored in a storage environment associated with the decentralized network node requesting access to the data.

[0339] It can be determined whether a relationship exists between the determined decentralized sub-identifier(s). To this end, the decentralized network node requesting data can access a decentralized registry node and determine whether an access element associated with the determined decentralized sub-identifier(s) exists in the registry. If so, the method proceeds to determine the sub-identifier(s). If not, the method proceeds to access and obtain the data.

[0340] The access element associated with the determined decentralized sub-identifier(s) can be obtained from the decentralized registration network node as described above. The access data can be used to access the associated relationship data set(s) as described above. The determined decentralized sub-identifier(s) can be considered as decentralized parent identifier(s). The method can return to this determination and repeat the steps using the determined decentralized sub-identifier(s) until there are no additional decentralized sub-identifier(s), for example, until a leaf node of the bill of materials tree is reached. Recursively determining the decentralized sub-identifier(s) associated with the decentralized material identifier allows for obtaining a complete bill of materials tree structure associated with the tire or parts thereof, for example, allowing for determining relationships between materials used to produce the tire or parts thereof.

[0341] In a final step, the collected tire data can be provided. The collected data can include all tire data collected based on sub-identifiers from different participating network nodes. The collected tire data can be provided to a storage environment associated with the network node requesting the data. The network node requesting the tire data can be part of a decentralized network, such as a decentralized data-consuming network node.

[0342] The present disclosure has also been described with reference to preferred embodiments as examples. However, other variations will be apparent to and can be implemented by those skilled in the art and those practicing the claimed invention upon study of the drawings, the present disclosure, and the claims. It is particularly noteworthy that any of the steps presented may be performed in any order, i.e., the present invention is not limited to a particular order of steps. Furthermore, there is no requirement that different steps be performed at a single location or node in a distributed system, i.e., each step may be performed at a different node using different devices / data processing units.

[0343] In the claims and description, "comprising" does not exclude other elements or steps, and the indefinite article "a" or "an" does not exclude a plurality. "Can" or "may" refers to an optional feature. A single element or other unit may fulfill the functions of several entities or items recited in the claims. The mere fact that certain measures are recited in mutually different dependent claims does not indicate that a combination of these measures cannot be used to advantage in an embodiment.

[0344] The disclosure has also been described with reference to various preferred embodiments and examples. However, other variations can be understood and effected by those skilled in the art and those practicing the claimed invention from a study of the drawings, the disclosure, and the claims.

[0345] Any steps presented herein may be performed in any order. The methods disclosed herein are not limited to a particular order of steps. They are not required to be performed in a particular location or on a particular computing node in a distributed system. In other words, each step may be performed on a different computing node using different equipment / data processing.

[0346] As used herein, "determining" also includes "initiating or causing a determination," "generating" also includes "initiating and / or causing generation," and "providing" also includes "initiating or causing determination, generation, selection, sending, and / or receiving." "Initiating or causing performance of an action" includes any processing signal that triggers a computing node or device to perform a corresponding action.

[0347] All terms and definitions used herein are to be understood broadly and have their ordinary meanings.

Claims

1. A device for generating a tire pass, the device comprising: One or more compute nodes; and one or more computer-readable media having computer-executable instructions thereon, the computer-executable instructions being configured to, when executed by the one or more computing nodes, cause the apparatus to perform the following steps: - receiving a request for providing a decentralized identifier associated with tire data and a data owner; - in response to the request, generating the tire passport, the tire passport comprising the decentralized identifier and data related to the tire data; - providing the Tire Pass for access by a data consuming service under or controlled by a data providing service associated with the data owner.

2. The device according to claim 1, wherein The decentralized identifier is provided by a central node or one or more decentralized nodes.

3. The device according to claim 1 or 2, wherein: The decentralized identifier is provided to the node generating the tire pass and to at least one authentication data registry, these nodes preferably being accessible to the data providing service and / or the data consuming service.

4. The device according to any one of claims 1 to 3, wherein The generation of the tire pass includes providing a decentralized identifier associated with the physical entity of the tire.

5. The device according to any one of claims 1 to 4, wherein The tire passport includes one or more authentication mechanisms associated with the decentralized identifier and data related to the tire data.

6. The device according to any one of claims 1 to 5, wherein: The tire passport involves one or more authorization mechanisms associated with the decentralized identifier and data related to the tire data.

7. The device according to any one of claims 1 to 6, wherein: The data associated with the tire data includes one or more digital representations pointing to the tire data or a portion thereof.

8. The device according to any one of claims 1 to 7, wherein The tire pass is associated with data related to different categories of tire data.

9. The device according to any one of claims 1 to 8, wherein The tire passport is associated with at least one type of tire data, the at least one type of tire data comprising data related to characteristics of the tire and / or data related to use of the tire and / or production data.

10. The device according to any one of claims 1 to 9, wherein The tire pass is associated with at least one type of tire data, the at least one type of tire data including access-restricted tire data associated with a physical entity of the tire.

11. A computer-implemented method for generating a tire pass, the method comprising the steps of: - receiving a request for providing a decentralized identifier associated with tire data and a data owner; - in response to the request, generating the tire passport, the tire passport comprising the decentralized identifier and data related to the tire data; - providing the Tire Pass for access by a data consuming service under or controlled by a data providing service associated with the data owner.

12. Use of a tire pass generated by a method according to claim 11 or by an apparatus according to any one of claims 1 to 10 for determining characteristics and / or treatments of a tire associated with the tire pass.

13. A tire associated with a tire pass, wherein: The tire pass comprising a decentralized identifier and data related to the tire data is The method according to claim 11 or generated by the apparatus according to any one of claims 1 to 10.

14. A tire pass comprising a decentralized identifier and data associated with tire data, wherein: The tire pass is The method according to claim 11 or generated by the apparatus according to any one of claims 1 to 10.

15. A computer element having instructions which, when executed on one or more computing nodes, are configured to perform the steps of the method according to claim 11 or to be performed by the apparatus according to any one of claims 1 to 10.

Images