Methods and systems for triggering product data exchange within decentral networks

Abstract

The invention relates to the field of sustainability, in particular to the field of sustainable industrialization. The disclosure relates to methods, systems and computer-elements for monitoring and / or controlling data exchange between decentral provider network node(s) connected to one or more local data provider component(s) of one or local data provider compute and storage environment(s) and decentral consumer network node(s) connected to one or more local data consumer component(s) of one or more local data consumer compute and storage environment(s).

Description

[0001] 241372

[0002] METHODS AND SYSTEMS FOR TRIGGERING PRODUCT DATA EXCHANGE WITHIN DECENTRAL NETWORKS

[0003] TECHNICAL FIELD

[0004] The invention relates to the field of sustainability, in particular to the field of sustainable industrialization. The disclosure relates to methods, systems and computer-elements for monitoring and / or controlling data exchange between decentral provider network node(s) connected to one or more local data provider component(s) of one or local data provider compute and storage environment(s) and decentral consumer network node(s) connected to one or more local data consumer component(s) of one or more local data consumer compute and storage environment(s).

[0005] TECHNICAL BACKGROUND

[0006] In the supply and production of products multiple regulatory requirements need to be met, which differ depending on the product. To fulfil such regulatory requirements, data on such products may need to be exchanged between different participants involved in the production and use of such products. Such data may be exchanged in a secure and controlled manner within a decentral network connecting different participants involved in the production and / or recycling of the product. Owing to the decentralization, offering of such data to data consumers and discovery of data available within the decentral network by data consumers requires cumbersome querying of the decentral network. Hence, there is a need to simplify offering of data to data consumers and discovery of available data within the decentral network. In addition, there is a need to allow for simplified triggering of generation of data required by data consumers.

[0007] SUMMARY OF THE INVENTION

[0008] In an aspect disclosed is a method, in particular a computer-implemented method executed by at least one orchestration component of a local orchestration compute and storage environment, for monitoring and / or controlling data exchange between decentral provider network node(s) connected to one or more local data provider component(s) of one or local data provider compute and storage environment(s) and decentral consumer network node(s) connected to one or more local data consumer component(s) of one or more local data consumer compute and storage environment(s), wherein the one or more local data provider components and the one or more local data consumer components are configured to provide triggers to and to receive requests from the at least one orchestration component communicatively coupled to the one or more local data provider component(s) and the one or more local data consumer component(s) via local communication protocol(s), optionally wherein the at least one orchestration component is configured to orchestrate the one or more local data provider component(s) and the one or more local data consumer component(s), e.g. via the local communication protocol(s), for data exchange between the decentral provider network node(s) and the decentral consumer network node(s), e.g. via decentral communication protocol(s), the method comprising: providing mapping data including mappings between local identifiers associated with local data provider compute and / or storage environments and local data consumer compute and storage environments and decentral participant identifiers associated with such compute and storage environments, optionally wherein the local identifiers identify the local data provider compute and storage environments and the local data consumer compute and storage 241372

[0009] 2 environments within a local environment and wherein the decentral participant identifiers identify decentral network node(s) connected to such compute and storage environments within a decentral network, optionally wherein the mapping data is stored in configuration data base accessible by the at least one orchestration component, optionally wherein the at least one orchestration component is configured to access the mapping of local identifiers to decentral identifiers, optionally wherein the mapping data further includes endpoint(s) of decentral provider network node(s) associated with at least a part of the decentral participant identifiers, receiving via the local communication protocol an asset generation trigger for generating a digital asset associated with a supply chain product and for providing the generated digital asset for access by one or more of the decentral consumer network node(s) from one or more of the local data consumer component(s) and / or receiving via the local communication protocol an asset consumption trigger for consuming generated digital asset(s) associated with supply chain product(s) by one or more of the decentral consumer network node(s) from one or more of the local data provider component(s), wherein the asset generation trigger includes decentral participant identifier(s) associated with local data provider compute and / or storage environments requested to generate and provide the digital asset and / or wherein the asset consumption trigger for consuming generated includes decentral participant identifier(s) associated with the decentral consumer network node(s) requested to gather the generated digital asset(s), optionally wherein the asset generation trigger further includes a data structure for collecting property / ies of the supply chain product, optionally wherein the asset consumption trigger includes decentral asset identifier(s) associated with the generated digital asset(s), optionally wherein the asset generation trigger is received by the orchestration component for providing a request for generating and providing the digital asset via the local communication protocol to one or more of the local data provider component(s), in particular to one or more of the local data provider component(s) associated with the one or more decentral participant identifier(s) included in the received trigger, optionally wherein the asset consumption trigger is received by the orchestration component for providing a request for consuming the generated digital asset(s) via the local communication protocol to one or more of the local data consumer component(s), in particular to one or more of the local data consumer component(s) associated with the one or more decentral participant identifier(s) included in the received trigger, determining local identifier(s) associated with the local data provider compute and storage environment(s) and / or the local data consumer compute and storage environment(s) based on the received trigger(s) and the mapping data, generating a request for generating the digital asset and for providing the generated digital asset for access based on the received asset generation trigger and providing the generated request via the local communication protocol to local data provider component(s) associated with the determined local identifier(s) for triggering generation of the digital asset and provision of the generated digital asset for access by the local data provider component(s) and / or generating a request for consuming generated digital asset(s) based on the received asset consumption trigger and providing the generated request via the local communication protocol to local data consumer component(s) associated with the determined local identifier(s) for triggering gathering of the generated digital asset(s) by the decentral consumer network node(s) connected to the local data consumer component(s), optionally wherein the request for generating and providing the digital asset further includes a data structure for collecting property / ies of the supply chain product, optionally wherein the request for consumption of generated digital asset(s) includes decentral asset identifier(s) associated with the generated digital asset(s). 241372

[0010] 3

[0011] Disclosed is in another aspect a local orchestration compute and storage environment for monitoring and / or controlling data exchange between decentral provider network node(s) connected to one or more local data provider component(s) of one or local data provider compute and storage environment(s) and decentral consumer network node(s) connected to one or more local data consumer component(s) of one or more local data consumer compute and storage environment(s), wherein the one or more local data provider components and the one or more local data consumer components are configured to provide triggers to and to receive requests from the at least one orchestration component communicatively coupled to the one or more local data provider component(s) and the one or more local data consumer component(s) via local communication protocol(s), optionally wherein the at least one orchestration component is configured to orchestrate the one or more local data provider component(s) and the one or more local data consumer component(s), e.g. via the local communication protocol(s), for data exchange between the decentral provider network node(s) and the decentral consumer network node(s), e.g. via decentral communication protocol(s), the local orchestration compute and storage environment comprising: a local configuration database configured to provide mapping data including mappings between local identifiers associated with local data provider compute and / or storage environments and local data consumer compute and storage environments and decentral participant identifiers associated with such compute and storage environments, optionally wherein the local identifiers identify the local data provider compute and storage environments and the local data consumer compute and storage environments within a local environment and wherein the decentral participant identifiers identify decentral network node(s) connected to such compute and storage environments within a decentral network, optionally wherein the configuration data base is accessible by the at least one orchestration component, optionally wherein the at least one orchestration component is configured to access the mapping of local identifiers to decentral identifiers, optionally wherein the mapping data further includes endpoint(s) of decentral provider network node(s) associated with at least a part of the decentral participant identifiers; a local communication interface configured to receive via the local communication protocol an asset generation trigger for generating a digital asset associated with a supply chain product and for providing the generated digital asset for access by one or more of the decentral consumer network node(s) from one or more of the local data consumer component(s) and / or receiving via the local communication protocol an asset consumption trigger for consuming generated digital asset(s) associated with supply chain product(s) by one or more of the decentral consumer network node(s) from one or more of the local data provider component(s), wherein the asset generation trigger includes decentral participant identifier(s) associated with local data provider compute and / or storage environments requested to generate and provide the digital asset and / or wherein the asset consumption trigger for consuming generated includes decentral participant identifier(s) associated with the decentral consumer network node(s) requested to gather the generated digital asset(s), optionally wherein the asset generation trigger further includes a data structure for collecting property / ies of the supply chain product, optionally wherein the asset consumption trigger includes decentral asset identifier(s) associated with the generated digital asset(s), optionally wherein the asset generation trigger is received by the orchestration component for providing a request for generating and providing the digital asset via the local communication protocol to one or more of the local data provider component(s), in particular to one or more of the local data provider component(s) associated with the one or more decentral participant identifier(s) included in the received trigger, optionally wherein the asset consumption trigger is received by the orchestration component for providing a request for consuming the generated digital asset(s) via the local communication protocol to one or more of the local data consumer component(s), in particular to one or more of 241372

[0012] 4 the local data consumer component(s) associated with the one or more decentral participant identifier(s) included in the received trigger; a request generator configured to

[0013] ■ determine local identifier(s) associated with the local data provider compute and storage environment(s) and / or the local data consumer compute and storage environment(s) based on the received trigger(s) and the mapping data,

[0014] ■ generate a request for generating the digital asset and for providing the generated digital asset for access based on the received asset generation trigger and / or generate a request for consuming generated digital asset(s) based on the received asset consumption trigger, optionally wherein the request for generating and providing the digital asset further includes a data structure for collecting property / ies of the supply chain product, optionally wherein the request for consumption of generated digital asset(s) includes decentral asset identifier(s) associated with the generated digital asset(s); a local communication interface configured to provide the generated request for generating and providing the digital asset via the local communication protocol to local data provider component(s) associated with the determined local identifier(s) for triggering generation of the digital asset and provision of the generated digital asset for access by the local data provider component(s) and / or to provide the generated request via the local communication protocol to local data consumer component(s) associated with the determined local identifier(s) for triggering gathering of the generated digital asset(s) by the decentral consumer network node(s) connected to the local data consumer component(s).

[0015] Disclosed is in another aspect a system for monitoring and / or controlling data exchange according to a decentral communication protocol between decentral provider network node(s) connected to one or more local data provider component(s) of one or local data provider compute and storage environment(s) and decentral consumer network node(s) connected to one or more local data consumer component(s) of one or more local data consumer compute and storage environment(s), wherein the one or more local data provider components and the one or more local data consumer components are connected to at least one orchestration component via local communication protocol(s), the system comprising: the one or more local data provider compute and storage environment(s) including the one or more local data provider components configured to

[0016] • provide configuration data for generating and providing a digital asset to be consumed via a decentral network protocol by the decentral consumer network node(s), wherein the digital asset is associated with a supply chain product produced or producible by a supply chain production using one or more production input(s) and wherein the configuration data includes a representation for accessing supply chain product data stored in a local source data storage and being associated with the supply chain product, a data model associated with the supply chain product or a product produced using the supply chain product and one or more decentral participant identifier(s) associated with the one or more decentral consumer network node(s);

[0017] • generate a digital asset associated with a supply chain product produced or producible by a production from one or more production input(s) based on the configuration data and providing the digital asset for access via the decentral network protocol by the decentral consumer network node(s); 241372

[0018] 5 wherein a request for consuming the generated digital asset via the decentral network protocol by the decentral consumer network node(s) is triggered by the one or more local data provider component(s), optionally wherein an asset consumption trigger for requesting consumption of the generated digital asset is generated by the one or more local data provider component(s) by selecting and / or providing at least a part of the configuration data, optionally wherein the asset consumption trigger is provided to at least one of the orchestration component(s) via local communication protocol(s), optionally wherein the request is provided by the one or more local data provider component(s) to the orchestration component, optionally wherein the trigger is provided to the orchestration component for providing the request for consuming the generated digital asset via the local communication protocol(s) from the orchestration component to at least a part of the one or more local data consuming component(s), in particular to one or more local data consuming component(s) associated with the one or more decentral participant identifier(s), or wherein a request for generating and providing the digital asset for access via the decentral network protocol by the decentral consumer network node(s) is received by one or more of the local data provider component(s) based on a trigger by one or more of the local data consumer component(s), optionally wherein the configuration data is provided by the request, optionally wherein the trigger is generated by the one or more local data consumer component(s) by selecting and / or providing at least a part of the configuration data, optionally wherein the trigger is provided by the one or more local data consumer component(s) to at least one of the orchestration component(s), optionally wherein trigger is provided to the orchestration component for providing the request for generating and providing the digital asset via the local communication protocol(s) from the orchestration component to at least a part of the one or more local data providing component(s); the one or more local data consumer compute and storage environment(s) including the one or more local data consumer component(s) configured to

[0019] • receive a request for consumption of generated digital asset(s) associated with the supply chain product(s) by the decentral consumer network node(s) via the decentral network protocol based on a trigger by one or more of the local data provider component(s), wherein the request is received from at least one orchestration component by one or more of the local data consumer component(s) via the local communication protocol(s),

[0020] • generate or select - based on the received request - configuration data associated with the consumption of digital asset(s) and the processing of consumed digital asset(s), optionally wherein the configuration data includes a representation for accessing a local target data storage of the local data consumer compute and storage environment configured to store processed digital asset(s), a data structure for collecting at least one property associated with the supply chain product and one or more decentral participant identifier(s) associated with the decentral provider network node(s);

[0021] • gather the digital asset(s) by the decentral consumer network node(s) from decentral provider network node(s) connected to one or more of the local data provider component(s) based on the received request,

[0022] • process at least a part of the gathered digital asset(s) based on the generated or selected configuration data and provide the processed digital asset(s) for generating digital product passport(s) associated with the one or more product(s); 241372

[0023] 6 wherein the request for consumption of generated digital assets(s) associated with the supply chain product(s) is triggered by the one or more local data consumer component(s), optionally wherein the request for consumption is triggered by a request for generating digital asset(s) and for providing the generated digital asset(s) for access by the decentral consumer network node(s) provided to the orchestration component(s), optionally wherein the request for generating digital asset(s) and for providing the generated digital asset(s) is generated by the one or more local data consumer component(s) by selecting and / or providing at least a part of the configuration data, optionally wherein the request for generating digital asset(s) and for providing the generated digital asset(s) is provided by the one or more local data consumer component(s) to the orchestration component, optionally wherein the request for generating digital asset(s) and for providing the generated digital asset(s) is provided to the orchestration component for providing the request via the local communication protocol from the orchestration component to at least a part of the one or more local data providing component(s), in particular to one or more local data providing component(s) associated with the one or more decentral participant identifier(s), or wherein the request for consumption of generated digital assets(s) associated with the supply chain product(s) is received by the one or more local data consumer component(s) based on a trigger by one or more of the local data provider component(s), optionally wherein the trigger is provided by the one or more local data provider component(s) to the orchestration component, optionally wherein the trigger is provided to the orchestration component for providing the request for consuming the generated digital asset via the local communication protocol from the orchestration component to at least a part of the one or more local data consuming component(s), in particular to one or more local data consuming component(s) associated with one or more decentral participant identifier(s) included in the trigger; a local orchestration compute and storage environment including the one or more local orchestration component(s), wherein the local orchestration compute and storage environment includes a configuration database storing mapping data including mappings between local identifiers associated with local data provider compute and / or storage environments and local data consumer compute and storage environments and decentral participant identifiers associated with such compute and storage environments and wherein the orchestration component is configured to determine local identifier(s) associated with the local data provider compute and storage environment(s) and / or the local data consumer compute and storage environment(s) based on the received trigger(s) and the mapping data and to the received triggers as requests via the local communication protocol to local data provider component(s) associated with the determined local identifier(s) for triggering generation of the digital asset and provision of the generated digital asset for access by the local data provider component(s) and / or to local data consumer component(s) associated with the determined local identifier(s) for triggering gathering of the generated digital asset(s) by the decentral consumer network node(s) connected to the local data consumer component(s), optionally wherein the local identifiers identify the local data provider compute and storage environments and the local data consumer compute and storage environments within a local environment and wherein the decentral participant identifiers identify decentral network node(s) connected to such compute and storage environments within a decentral network, optionally wherein the at least one orchestration component is configured to orchestrate the one or more local data provider component(s) and the one or more local data consumer component(s), e.g. via the local 241372

[0024] 7 communication protocol(s), for data exchange between the decentral provider network node(s) and the decentral consumer network node(s), e.g. via decentral communication protocol(s).

[0025] In yet another aspect disclosed is a computer element, in particular a computer program product or a computer readable medium, with instructions, which when executed on one or more computing node(s) are configured to carry out the steps of any of the methods disclosed herein.

[0026] In yet another aspect the present disclosure relates to a computer element with instructions, which when executed on one or more computing node(s) are configured to carry out the steps of the method(s) of the present disclosure or are configured to be carried out by the local orchestration compute and storage environment disclosed herein.

[0027] Any disclosure, embodiments and examples described herein relate to the methods, the apparatuses, systems, the supply chain products and computer elements lined out above and below. Advantageously, the benefits provided by any of the embodiments and examples equally apply to all other embodiments and examples.

[0028] EMBODIMENTS

[0029] In the following, embodiments of the present disclosure will be outlined by ways of embodiments and / or examples. It is to be understood that the present disclosure is not limited to said embodiments and / or examples.

[0030] To enable or improve the generation and exchange of digital assets associated with supply chain product(s) used to produce one or more product(s), efficient offering of available digital assets for consumption as well as efficient triggering of generation of such digital assets is crucial. However, the discovery of digital assets available for consumption within the decentral network is cumbersome since it requires querying of the decentral network to locate the data provider providing the digital asset as well as locating the digital asset. In addition, data providers are limited in offering generated digital assets to data consumers via the decentral network since this requires knowledge of endpoint(s) of decentral consumer network node able to receive and process the generated digital assets.

[0031] By orchestrating via the orchestration component the communication between the local data provider component(s) and the local data consumer component(s) according to the local communication protocol, data exchange between decentral network nodes of the decentral network, such as the decentral provider network node(s) connected to the local data provider component(s) and the decentral consumer network node(s) connected to the local data consumer component(s), may be controlled and / or monitored. The data exchange may be monitored and / or controlled by the orchestration component based on triggers received from the local data provider component(s) via the local communication protocol and / or based on triggers received by the local data consumer component(s). This way, more efficient sharing of digital assets associated with the supply chain products may be enabled while ensuring full data sovereignty of the data owner of the digital assets, such as the supply chain product producer, by using the decentral network protocol for exchanging the digital assets.

[0032] By using the mapping data, recipients of triggers received via the local communication protocol may be reliably and efficiently determined based on decentral participant identifiers included in the received triggers. This way, requests may be routed by the orchestration component(s) in an efficient manner from local data provider component(s) to local data 241372

[0033] 8 consumer component(s) or vice versa based on the local communication protocol. Depending on the envisaged data transfer to be executed via the decentral network, the orchestration component orchestrates a data pipeline setup in the local data provider and data consumer compute and storage environments. The data pipeline may allow generation and provision of digital assets or processing of digital assets gathered via the decentral communication protocol. The exchange of the actual digital assets is not executed via the orchestration component(s) and the orchestration component(s) do not have access to such digital assets. Hence the digital assets are transferred only via a peer-to-peer communication between decentral network nodes of the decentral network under full control of the data owner of the digital assets. The orchestration component(s) only enable communication between tenants with respect to requests for digital assets or offers of digital assets and ensures that the digital asset(s) transferred via the decentral network adhere(s) to the data structure(s) and content the provider and / or recipient of such data expect. This way the digital assets associated with the supply chain products are kept under full control of the respective data owner of such digital assets, such as the supply chain product producer, while enabling secure and efficient transfer of such digital assets via the decentral network based on the orchestration of requests from tenants by the orchestration component. This way, discovery of endpoint(s) of respective decentral network node(s) and decentral asset identifier(s) of digital asset(s) to request the digital asset(s) and / or to offer digital asset(s) by querying the decentral network and configuration of such decentral network node(s) to process such data offer(s) can be avoided. This reduces the number of data transactions performed within the decentral network, reducing latency and energy consumption and hence also the environmental impact associated with the digital asset transfers via the decentral network.

[0034] By routing requests for consumption of generated digital assets received via the local communication protocol from the local data provider component(s) based on the mapping data and decentral participant identifier(s) defined or selected by the local data provider component(s), inefficient discovery of accessible digital assets within the decentral network can be avoided, reducing the energy consumption associated with the discovery of accessible digital assets within the decentral network and hence also the environmental impact associated with the exchange of digital assets within the decentral network. This way, digital product passport(s) associated with a product produced using the supply chain products may be generated in a more efficient and reliable manner, ensuring a higher data quality of the data included in the digital product passport. A higher data quality may allow a more efficient processing of the product and / or a more efficient production of further products based on the product using the data included in the digital product passport(s).

[0035] By routing requests for generation and provisioning of digital assets received via the local communication protocol from local data consumer component(s) based on the mapping data and decentral participant identifier(s) defined or selected by the local data consumer component(s), digital assets required for generation of digital product passports associated with products produced from the supply chain product(s) may be reliably and efficiently generated and provided for access via the decentral network by decentral consumer network node(s) connected to the local data consumer component(s). This way, a high data quality of the digital product passports associated with the products may be ensured, allowing to improve the processing of the products and / or production of further products based on the data included in the digital product passports.

[0036] Various units, entities, nodes or other computing components may be described as “configured to” perform a task or tasks.

[0037] Configured to shall recite structure meaning “having circuitry that” performs the task or tasks on operation. The units, 241372

[0038] 9 circuits, entities, nodes or other computing components can be configured to perform the task even when the unit / circuit / component is not operating. The units, circuits, entities, nodes or other computing components that form the structure corresponding to “configured to” may include hardware circuits and / or memory storing program instructions executable to implement the operation. The units, circuits, entities, nodes or other computing components may be described as performing a task or tasks, for convenience in the description. Such descriptions shall be interpreted as including the phrase “configured to.”

[0039] In general, the methods, apparatuses, systems, computer elements, nodes or other computing components described herein may include memory, software components and hardware components. The memory can include volatile memory such as static or dynamic random-access memory and / or nonvolatile memory such as optical or magnetic disk storage, flash memory, programmable read-only memories, etc. The hardware components may include any combination of combinatoric logic circuitry, clocked storage devices such as flops, registers, latches, etc., finite state machines, memory such as static random-access memory or embedded dynamic random-access memory, custom designed circuitry, programmable logic arrays, etc.

[0040] The supply chain product may include production inputs for producing the product. The supply chain product may be produced or producible by a suppl chain product production from one or more production input(s). The supply chain product(s) may be produced or producible by upstream production stage(s) with respect to the product production stage. Produced supply chain product(s) may be physical entity / ies of supply chain product(s) having been produced by the supply chain product production. Producible supply chain product(s) may not yet have been produced by the supply chain product production but may be producible by one or more production process(es) performed within the supply chain product production. Producible supply chain product(s) may include supply chain product(s) planned to be produced, for example based on demand data received from downstream production stages. The supply chain product may be a discrete product, such as a component or a component assembly. The supply chain product may be a battery or a battery component. The supply chain product may be a chemical product.

[0041] The product may be a discrete product. The product may be a component, a component-assembly or an end-product. The product may be a battery or a battery component. The product may be an electronic product. The product may be a chemical product.

[0042] The chemical product may include inorganic chemical products and organic chemical products. Inorganic chemical products may be devoid of carbon atoms and / or carbon-hydrogen bond(s) while organic chemical products may include at least one carbon atom and / or at least one carbon-hydrogen bond. The chemical product may be a naturally occurring chemical product, i.e. any unprocessed chemical substance that is found in nature, such as chemicals from plants, micro-organisms, animals, the earth and the sea or any chemical substance that is found in nature and extracted using a process that does not change its chemical composition. The chemical product may be produced via one or more process steps. The process steps may involve chemical reactions and / or physical processes. The physical process(es) may involve the use of chemical production inputs, such as chemical materials. Physical process(es) may include mixing, dispersing, extrusion, molding, casting, weaving, knitting, coating and / or filling. 241372

[0043] 10

[0044] Inorganic chemical products may include aluminium, iron, steel, copper, zinc, lead, nickel, titanium, magnesium, chromium, tin, manganese and / or cobalt. Organic chemical products may include detergents, cosmetic products, paints, lubricants, paper, pulp paper, paper boards and / or polymer products. Polymer products may include chemical products including or consisting of at least one polymer, such as synthetic textiles, footwear, mattresses, absorbent hygiene products, toys, fishing nets and fishing gear. The polymer may be selected from polyolefins, polyvinyls, polystyrenes, polyesters, polyethers, polyurethanes, poly(meth)acrylates, polyamides, polycarbonates, polyacetals, fluoropolymers, epoxides, silicons, polyimides, polylactic acid, cellulose, lignin, copolymers of such polymers and / or blends of such polymers. Organic chemical products may include compositions including alkanes, alkenes and alkynes, aromatic compounds, alcohols, aldeyhdes, ketons, carboxylic acids, esters, ethers, amines, amides, nitriles and / or halides.

[0045] The supply chain product and the product may be part of a product ecosystem. The product ecosystem may include chemical products. The product ecosystem may include production stage(s) for producing the product. The product ecosystem may include processing chains to process used products resulting from the use of produced products. Processing chains may include recycling chains to recycle at least part of the used product or a component thereof. Processing chains may include re-use chains to re-use the used product. The product ecosystem may include various participants, such as raw input material producers, chemical product producers, chemical product users, end-product producers, end-product users, EOL product collectors and recyclers. The participants may be associated with the local data provider compute and storage environment(s) and / or the local data consumer compute and storage environment(s). Participants associated with the local data provider compute and storage environment(s) may include data providers. Participants associated with the local data provider compute and storage environment(s) may include data providers, such as supply chain product producers. Participants associated with the local data consumer compute and storage environment(s) may include data consumers, such as supply chain product consumer(s), product producer(s) and / or entity / les generating the digital product passport(s).

[0046] The local data provider compute and storage environment(s) may include one or more component(s) configured to perform different functionalities. The component(s) may include one or more local data provider component(s) configured to generate and / or provide digital assets, one or more local data provider component(s) configured to request consumption of generated digital asset(s) and / or one or more local data provider component(s) configured to orchestrate, e.g. to monitor and / or control, generation and / or provision of digital assets. Requesting consumption of generated digital assets from or by the one or more decentral consumer network node(s) connected to one or more local data consumer component(s) may include triggering consumption of the generated digital assets by the decentral data consumer network node(s) through the decentral network. The local data provider compute and storage environment and the one or more local data provider component(s) included therein may be associated with a local identifier (also referred to as tenant identifier) uniquely identifying such local environment within other environments. The local data consumer compute and storage environment(s) may include one or more component(s) configured to perform different functionalities. The component(s) may include one or more local data consumer component(s) configured to trigger access of digital assets via the decentral network protocol, one or more local data consumer component(s) configured to process accessed digital assets and / or one or more local data consumer component(s) configured to orchestrate, e.g. to monitor and / or control, accessing of digital assets and / or processing of accessed digital assets. The local data consumer compute and storage environment and the one or more local data 241372

[0047] 11 consumer component(s) included therein may be associated with a local identifier (also referred to as tenant identifier) uniquely identifying such local environment within other environments.

[0048] Tenants may also be referred to as one or more local data provider compute and storage environments and / or one or more data local data consumer compute and storage environment. Tenant component(s) may also be referred to as one or more local data provider component(s) and / or one or more local data consumer component(s). The tenant component(s) may be configured to communicate with the orchestration component via the local communication protocol(s). The tenant component(s) may be configured to communicate with other tenant component(s) via or by using the orchestration component. The tenant component(s) may be configured to communicate with other tenant component(s) solely through the orchestration component.

[0049] The local orchestration compute and storage environment may include one or more component(s) configured to perform different functionalities. The component(s) may include one or more local orchestration component(s) configured to receive triggers via the local communication protocol(s) from local data provider component(s) and / or local data consumer component(s), one or more local orchestration component(s) configured to process the received triggers, one or more local orchestration component(s) configured to generate and provide requests via the local communication protocol(s) to local data provider component(s) and / or local data consumer component(s), one or more component(s) configured to store data model(s) received via the local communication protocol(s) from local data consumer component(s) and / or to store mappings between local identifiers associated with the local data provider compute and storage environments and the local data consumer compute and storage environments and decentral participant identifiers associated with such compute and storage environments. The orchestration component(s) may be configured to orchestrate, e.g. control and / or monitor, data exchange via the decentral network by exchanging, receiving and / or sending, requests via the local communication protocol with, from and / or to local data consumer and / or provider component(s). The orchestration component(s) may be communicatively connected to the tenant component(s). The orchestration component(s) may be configured to communicate with tenant component(s) based on the local communication protocol. The orchestration component(s) may be configured to communicate with individual tenant component(s) based on the local communication protocol. The orchestration component(s) may be configured to orchestrate communication channels to multiple tenant components. The orchestration component(s) may be configured to centrally orchestrate communication to multiple tenant components. The orchestration component(s) may be configured to centrally orchestrate communication between multiple tenant components indirectly, e.g. through or via the orchestration component. The orchestration component(s) may implement network interface(s) for communication with the tenants via the local communication protocol. The network interface(s) may include API(s), such as a REST API(s).

[0050] The local compute and storage environment may include distributed compute and storage environments. The distributed compute and storage environments may be controlled by the data provider, such as the supply chain product producer, the data consumer, such as the supply chain product consumer or product producer, or the entity orchestrating the tenants via the orchestration component(s).

[0051] The local communication protocol may facilitate communication in distributed compute and storage environment. The local communication protocol may include web protocols, such as HTTP / HTTPS methods, URI, MIME types or combinations thereof. The local communication protocol may implement stateless communication. Stateless communication may include requests and triggers that include all data required to process the request or trigger by the at least one orchestration component. This way, the orchestration component(s) do not have to retain session information, allowing efficient communication with multiple tenants and improving scalability and reliability. The local communication protocol may be configured to communicatively couple the orchestration component with multiple tenant components. The local communication protocol may be configured to decouple communication between tenant components. The local communication protocol may be configured to open communication channel between the orchestration component and multiple tenant components. The local communication protocol may be configured to open communication channel between the orchestration component and multiple tenant components per tenant component. The local communication protocol may be configured to close communication channel between the orchestration component and multiple tenant components e.g. per tenant component.

[0052] The local data provider component(s) may be connected to decentral provider network node(s) of the decentral network. The decentral network may be associated with participants of the product ecosystem. The local data consumer component(s) may be connected to decentral consumer network node(s) of the decentral network. The decentral network nodes may be configured to perform data transactions or data exchanges, e.g. via peer-to-peer communication. The decentral provider network node(s) may be associated with data providers, such as supply chain product producer and / or the supply chain product productions. The decentral consumer network node(s) may be associated with data consumers, such as supply chain product users, product producers, product productions and / or entities generating digital product passports associated with the product. The data transactions or exchanges may be based on a decentral network protocol establishing peer-to- peer communication between the decentral network nodes. The decentral network nodes of the decentral network may be configured to provide or send digital assets to another decentral network node of the decentral network and / or to ingest or receive digital assets from another decentral network node of the decentral network. Providing digital assets for access via the decentral network by decentral consumer network node(s) may include indirect or direct access of the decentral network consumer node(s) to the digital assets.

[0053] The decentral network protocol may specify a communication protocol for peer-to-peer communication according to a communication standard defined for the decentral network. The decentral network protocol may relate to decentral asset identifier(s) identifying the at least one supply chain product and / or decentral participant identifiers related to the least one participant node and / or authentication and / or authorization mechanism(s) authentication and / or authorizing the at least one participant node for data exchange.

[0054] The data transactions or exchanges may be based on the decentral network protocol including decentral asset identifier(s) associated with at the least one supply chain product and / or decentral participant identifiers associated with the decentral network nodes. Based on the decentral participant identifier(s) associated with the decentral network nodes, the decentral network nodes for peer-to-peer communication may be identified. Based on the decentral asset identifier(s) of the supply chain products the digital assets associated with the supply chain product(s) for peer-to-peer data exchange may be identified. 13

[0055] The digital assets may include the decentral asset identifier(s) associated with the supply chain product. The asset identifier(s) may be linked to one or more supply chain product data points associated with the supply chain product. The decentral asset identifier(s) may be linked to the one or more property data points associated with property / ies of the supply chain product. Property may include chemical and / or physical properties, emission properties, recycled content properties, biobased content properties, renewable content properties and / or production properties associated with the production of the supply chain product. Emission properties may include the carbon footprint of the supply chain product. The one or more property data points may be linked to the decentral asset identifier included in the digital asset. The one or more supply chain product data points, or the one or more property data points may be stored in local data base of the respective local data provider compute and / or storage environment for access by decentral consumer network node(s) associated with local data consumer component(s), e.g. authenticated and / or authorized for such access. The one or more supply chain product data points, or one or more property data points may be stored in the respective local data provider compute and / or storage environment for transfer to the decentral consumer network node(s) associated with local data consumer component(s), e.g. when accessed or on providing the supply chain product.

[0056] The decentral asset identifier(s) may comprise any unique identifier uniquely associated with the physical entity of the supply chain product and the supply chain product data points and / or the property data points. Decentral asset identifier(s) in this context may refer to the use of the asset identifier(s) for exchange of the digital assets via the decentral network protocol. The decentral asset identifier(s) may relate to local identifiers such as unique locators and / or decentral identifier(s) as defined by the decentral network. The decentral identifier(s) may include Universally Unique I Dentifier(s) (UUID(s)) and / or Digital I Dentifier(s) (DID(s)). The decentral identifier(s) may be issued by a central or decentral identity issuer of the decentral network according to the decentral network protocol. The decentral asset identifier(s) may not be discoverable by participant nodes of the decentral network according to the decentral network protocol. The decentral asset identifier(s) may be discoverable and / or accessible by participant nodes of the decentral network according to the decentral network protocol. The decentral asset identifier(s) may be linked to authentication and / or authorization information. Via the decentral asset identifier(s) and the unique association with the physical entity of the supply chain product and the supply chain product data points and / or the property data points, access to such data points may be controlled by the data owner of such data points, such as the supply chain product producer. This contrasts with central authority schemes, where identifiers are provided by such central authority and access to data is controlled by such central authority.

[0057] The decentral asset identifier(s) may be uniquely associated with the supply chain product or the physical entity of the supply chain product, e.g. as packaged for transportation to the supply chain product consumer. The decentral asset identifier(s) may be uniquely associated with the digital assets providing access to the supply chain product data associated with the supply chain product.

[0058] The decentral asset identifier(s) may be uniquely associated with the decentral participant identifier associated with the decentral provider network node configured to provide digital asset(s) the decentral identifier(s) are associated with and an endpoint of such decentral provider network node. The decentral asset identifier(s) may be uniquely associated with the decentral participant identifier associated with the decentral provider network node. The decentral provider network node may be any computing node or data storage structure providing an endpoint accessible for the decentral consumer network 14 node(s) via the decentral network protocol. Decentral in this context may refer to implementations where the digital assets are stored in a local database associated with the data owner of the digital asset(s) and access to the digital assets stored in such local database is controlled by the data owner of the digital assets based on the decentral asset identifier(s) and decentral participant identifier(s) associated with decentral consumer network node(s).

[0059] The data transactions or exchanges may be based on a decentral network protocol including authentication and / or authorization mechanism(s). Based on the authentication and / or authorization mechanism(s) a peer-to-peer network between participant nodes, e.g. decentral network nodes, of the decentral network may be established. The one or more authentication mechanism(s) may be associated with or linked to the decentral participant identifier(s) associated with the participant nodes of the decentral network. The one or more authentication mechanism(s) associated with the decentral participant identifier(s) may be provided to participant node(s) for authenticating the peer-to-peer communication between respective participant nodes. The one or more authentication mechanism(s) associated with the decentral participant identifier(s) may be accessible by the decentral provider network node and / or the decentral consumer network node. The one or more authorization mechanism(s) may include at least one authorization rule for providing and / or consuming and / or accessing digital assets. The one or more authorization mechanism(s) may be associated with or linked to the decentral participant identifier(s) associated with the participant nodes and / or the decentral asset identifier(s) associated with the digital assets. The one or more authorization mechanism(s) may be associated with or linked to the decentral asset identifier(s) related to digital assets to be accessed and / or exchanged. The decentral configuration allows for more efficient use of computing resources and strengthens control by each data owner of the decentral network.

[0060] The exchange of digital assets may be orchestrated via one or more data pipeline(s) configured by the tenants. The data pipelines may be associated with configuration data. The configuration data may be associated with the configuration of the data pipeline. The configuration data may relate to or be stored in local storage environment(s) included in the tenants. The configuration data may relate to processing of data, such as supply chain product data and digital assets. The configuration data may relate to decentral participant identifier(s) associated with the decentral provider network node(s) or the decentral consumer network node(s) of the decentral network, respectively.

[0061] The configuration data may include a configuration data identifier uniquely identifying the configuration data within the respective local data provider compute and storage environment and data pipeline configuration data associated with a configuration of a data pipeline for requesting consumption of digital asset(s) associated with supply chain product(s) via the decentral network protocol by the one or more decentral consumer network node(s) connected to the one or more local data consumer component(s). The data pipeline may be configured for generating digital assets(s) to be consumed by the one or more decentral consumer network node(s) via the decentral network protocol. The data pipeline may relate to a local data source associated with the respective local data provider compute and storage environment. The local data source may store supply chain product data used to generate the digital asset(s) exchanged via the decentral network protocol.

[0062] The configuration data may include a configuration data identifier uniquely identifying the configuration data within the respective local data consumer compute and storage environment, and data pipeline configuration data associated with a configuration of a data pipeline for processing digital asset(s) associated with supply chain product(s) consumed by the one or more decentral consumer network node(s) from decentral provider network node(s) connected to a local asset storage of 241372

[0063] 15 the local data provider compute and / or storage environment generating the digital asset(s). The data pipeline may be configured for processing digital asset(s) consumed via the decentral network protocol. The data pipeline may relate to a local target data storage associated with or included in the local data consumer compute and / or storage environment. The local target data storage may store processed digital assets. The one or more data pipeline(s) configured by the one or more tenants may be orchestrated by the orchestration component. The data pipelines may be configured for generating digital assets to be provided and / or consumed via the decentral network protocol. The data pipelines may be configured for consuming digital assets and / or for processing digital assets consumed via the decentral network protocol.

[0064] In an embodiment the at least one orchestration component is configured to orchestrate the one or more local data provider component(s) and the one or more local data consumer component(s), e.g. via the local communication protocol(s), for data exchange between the decentral provider network node(s) and the decentral consumer network node(s), e.g. via decentral communication protocol(s). Orchestration may include monitoring and / or controlling the local data provider component(s) and the local data consumer component(s). Orchestration may include receiving requests from the local data provider component(s) and / or the local data consumer component(s) and forwarding such requests to respective request recipients based on a mapping between local identifiers associated with the local data provider component(s) and the local data consumer component(s) and respective decentral participant identifiers associated with decentral network node(s) connected to such component(s). The orchestration component may be configured to orchestrate communication channels to local data provider component(s) and the local data consumer component(s). The orchestration component may be configured to centrally orchestrate communication to multiple local data provider component(s) and the local data consumer component(s). By orchestrating communications between provider and consumer tenants via the central orchestration component, provider tenants can be reliably and efficiently notified with respect to digital asset(s) required by the data consumer(s). This way, consumer tenants may efficiently trigger generation and provision of digital asset(s) required for generation of digital product passports, allowing to ensure a higher quality of the data included in the generated digital product passports and hence allowing a more efficient processing of the products and / or production of further products using the product as production input based on the data included in the digital product passport.

[0065] In an embodiment the local data consumer compute and storage environment(s) are associated with local identifier(s) identifying the local data consumer compute and storage environment(s) within a local environment associated with the local communication protocol and with decentral participant identifier(s) identifying the data consumer(s) associated with the local data consumer compute and storage environment(s) within a decentral network associated with the decentral network protocol. In an embodiment the local data provider compute and storage environment(s) are associated with local identifier(s) identifying the local data provider compute and storage environment(s) within a local environment associated with the local communication protocol and with decentral participant identifier(s) identifying the data provider associated with the local data provider compute and storage environment(s) within a decentral network associated with the decentral network protocol. By mapping local identifiers with decentral identifiers, storage of only one set of identifiers, namely the decentral participant identifiers, is required by the local compute and storage environments to ensure forwarding of requests / triggers to local compute and storage environments associated with the decentral participant identifiers defined in such requests / triggers. This way, maintenance of such database may be avoided while ensuring efficient forwarding of requests to the respective recipients based on decentral participant identifiers included in the requests / triggers received by the at least one orchestration component.

[0066] In an embodiment the local data provider component(s) communicate with the local data consumer component(s) associated based on the local communication protocol via the orchestration component. The one or more local data provider component(s) and the one or more data consumer component(s) may be connected via local communication protocol(s) to the at least one orchestration component. The local data provider component(s) and the local data consumer component(s) may communicate via the local communication protocol(s) through the at least one orchestration component. The local data provider component(s) and the local data consumer component(s) may communicate with each other solely through the at least one orchestration component. The data exchanged via the local communication protocol may not include digital assets. Digital assets may be solely exchanged based on the decentral network protocol between decentral provider network nodes connected to the local data provider component(s) and decentral consumer network nodes connected to local data consumer component(s). This way, it can be ensured that the digital assets are exchanged under full data sovereignty of the data owner of the digital assets.

[0067] In an embodiment the local identifiers identify the local data provider compute and storage environments and the local data consumer compute and storage environments within a local environment and the decentral participant identifiers identify decentral network node(s) connected to such compute and storage environments within a decentral network. By using a mapping between local identifiers and decentral participant identifiers, request recipients can be reliably determined by the at least one orchestration component based on decentral participant identifier(s) known to the component(s) providing the trigger / request, ensuring that received requests / triggers are forwarded to the corresponding recipient, known to the component(s) providing the trigger / request

[0068] In an embodiment the mapping data is stored in a configuration data base accessible by the at least one orchestration component, wherein the at least one orchestration component is configured to access the mapping of local identifiers to decentral identifiers. At least one of the orchestration component(s) may be associated with a configuration data base. The configuration data base may provide access to the mapping data. The configuration data base may store the mapping data. The configuration data base may store the mapping data in key value pairs including pairs of local identifiers and decentral participant identifiers per tenant. The mapping data may further include names of participants associated with local data provider compute and / or storage environments and / or names of participants associated with the local data consumer compute and / or storage environments. The configuration data base may further store one or more data model(s) provided by the one or more local data consumer component(s) for collecting properties of the supply chain product.

[0069] In an embodiment the mapping data further includes endpoint(s) of decentral provider network node(s) associated with at least a part of the decentral participant identifiers. This way, such endpoints may be provided as part of a request to local data consumer component(s), allowing to gather digital asset(s) using such received endpoints and avoiding querying of the decentral network to determine such endpoints. This way, the digital assets can be gathered via the decentral network more efficiently, allowing more efficient generation of digital product passports associated with product produced using the supply chain products the digital assets are associated with. 241372

[0070] 17

[0071] In an embodiment the asset generation trigger further includes a data structure for collecting property / ies of the supply chain product. The data structure may include a data model defining the property / ies to be collected. The property / ies may include chemical property / ies and / or physical property / ies of the supply chain product. The properties may further include properties associated with the production of the supply chain product, such as the supply chain product producer, production location, water consumption or the like. The data structure included in the trigger may be stored in the configuration data base. In an embodiment the asset consumption trigger further includes decentral asset identifier(s) associated with the generated digital asset(s). This way, the digital asset(s) may be gathered via the decentral network based on the decentral asset identifier(s) included in the request generated by the orchestration component based on the received asset consumption trigger, avoiding querying of the decentral network for such decentral asset identifier(s). This allows more efficient gathering of the digital assets via the decentral network and hence also more efficient generation of digital product passports.

[0072] In an embodiment the asset generation trigger is received by the orchestration component for providing a request for generating and providing the digital asset via the local communication protocol to one or more of the local data provider component(s). The request may be provided to one or more of the local data provider component(s) associated with the one or more decentral participant identifier(s) included in the received asset generation trigger. This way, the local data consumer component(s) may trigger generation and provision of digital assets via the decentral communication protocol without requiring direct communication with the local data provider component(s), avoiding querying of the decentral network to determine endpoints of decentral provider network node(s) connected to such local data provider component(s) for providing such triggers. This allows to more efficiently trigger generation and provision of digital assets, resulting in a higher data quality of digital product passports generated from such digital assets.

[0073] In an embodiment the asset consumption trigger is received by the orchestration component for providing a request for consuming the generated digital asset(s) via the local communication protocol to one or more of the local data consumer component(s). The request may be provided to one or more of the local data consumer component(s) associated with the one or more decentral participant identifier(s) included in the received asset consumption trigger. This way, the local data provider component(s) may trigger consumption of generated digital assets via the decentral communication protocol without requiring direct communication with the local data consumer component(s), avoiding querying of the decentral network to determine digital assets available for consumption via the decentral communication protocol. This allows to more efficiently consume generated digital assets, resulting in a higher data quality of digital product passports generated from such digital assets.

[0074] In an embodiment the digital asset includes a decentral asset identifier associated with the supply chain product and further includes at least one chemical and / or physical property of the supply chain product and / or emission data and / or recycled content data and / or biobased content data and / or renewable content data and / or production data associated with the production of the supply chain product. The decentral asset identifier may not be discoverable and / or accessible for decentral network nodes of the decentral network. This way, the generated digital assets may not be discoverable and / or accessible by querying the decentral network for decentral asset identifier(s) associated with such digital asset(s). The digital asset(s) may only be accessible upon receiving the decentral asset identifier(s), for example based on a request received 241372

[0075] 18 from the orchestration component. This may avoid complicated operation of decentral registries allowing discovery of decentral asset identifiers while still ensuring reliable and secure transfer of digital assets within the decentral network.

[0076] In an embodiment the asset generation trigger is generated by the local data consumer component(s) based on generated or selected configuration data. The generated or selected configuration data may include a representation for accessing a local target data storage of the local data consumer compute and storage environment configured to store processed digital asset(s), a data structure for collecting at least one property associated with the supply chain product and one or more decentral participant identifier(s) associated with decentral provider network node(s) connected to one or more local data provider component(s) requested to generate and provide the digital asset. The data model may have been received via or defined by the request for generating and providing the digital assets. The data model may have been accessed via a representation for accessing the data model. The representation for accessing may have been included in the request received via the local communication protocol from the orchestration component. The configuration data may further include a mapping for mapping the data included in the source data storage to the data included in the structure for collecting properties, and the decentral participant identifier associated with the decentral consumer network node(s). The decentral participant identifier(s) may be included in policy data associated with the digital assets and used for controlling access to the digital asset(s). The configuration data may be associated with a data pipeline for generating and providing digital assets. The configuration data may be associated with the configuration of the data pipeline. The configuration data may be selected based on the data structure and / or the decentral participant identifier(s).

[0077] In an embodiment the asset consumption trigger is generated by the local data provider component(s) based on generated or selected configuration data. The generated or selected configuration data may include a configuration data identifier, a representation for accessing supply chain product data stored in a local source data storage of the local data provider compute and storage environment and being associated with the supply chain product(s), a data model received via or defined by the asset generation trigger for collecting at least one property of the supply chain product(s) and one or more decentral participant identifier(s) associated with the decentral consumer network node(s) requested to consume the generated digital asset(s). The configuration data may be selected based on a data structure defined by the local data consumer compute and storage environment for collecting properties associated with the supply chain product(s). The data structure or a representation for accessing the data structure may be included in the received request. This way, it may be ensured that the digital assets generated in response to the request are generated using the data structure defined by the local data consumer component(s). The digital asset(s) may be generated based on the generated or selected configuration data by transforming supply chain product data accessed according to a representation included in the configuration data based on a data structure defined by the local data consumer compute and storage environment included in the configuration data. The supply chain product data may be transformed using a rule-based engine including one or more rule(s). The rule(s) may be associated with the data structure defined by the local data consumer compute and storage environment. The rule(s) may include instructions, in particular executable instructions, for transforming the accessed supply chain product data. The generated digital asset may be provided for access by storing the generated digital asset in a local target data storage of the local data provider compute and storage environment. The digital asset may be stored in the local target data store for access by the decentral consumer network node(s). Access to the local target data storage by the decentral consumer 241372

[0078] 19 network node(s) connected to the local data consumer component(s) may be controlled based on the decentral asset identifier associated with the digital asset.

[0079] In an embodiment the request for generating and providing the digital asset further includes a data structure for collecting property / ies of the supply chain product or includes a representation for accessing the data structure. The representation for accessing the data structure may include a pointer pointing to the configuration data base storing the data structure. This way, the data structure may be accessed by local data provider component(s) based on the representation while avoiding access to data storages of the local data consumer compute and storage environment, hence improving data security while ensuring reliably access to the data structure. This way, generation of digital assets according to data structures defined by local data consumer component(s) may be ensured without having to grant access to data storages included in the local data consumer compute and storage environments including such local data consumer component(s).

[0080] In an embodiment the request for consumption of generated digital asset(s) includes decentral asset identifier(s) associated with the generated digital asset(s). This way, querying of the decentral network for decentral asset identifiers required to gather the digital assets via the decentral communication protocol from decentral provider network node(s) may be avoided, allowing more efficient generation of digital product passports.

[0081] BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

[0082] In the following, the present disclosure is further described with reference to the enclosed figures. The same reference numbers in the drawings and this disclosure are intended to refer to the same or like elements, components, and / or parts.

[0083] FIG. 1 illustrates an example of a participant network of a product ecosystem including a material loop and being associated with a decentral peer-to-peer network for exchange of data associated with raw materials, chemical product(s), discrete product(s), end product(s) and recycled material(s).

[0084] FIG. 2 illustrates an example of a nested product production chain including production processes, production inputs and production outputs produced by the production processes.

[0085] FIG. 3 illustrates an example of a system architecture including a central orchestration unit, a plurality of data providing and / or consuming components acting as tenants of the central orchestration unit and decentral network components acting as decentral data providing and / or consuming nodes.

[0086] FIG. 4A illustrates an example sequence diagram for accessing digital asset(s) by decentral consumer network node(s) associated with a consumer tenant from decentral data provider network node(s) associated with a provider tenant in response to a request for consumption of the digital asset(s) provided by the provider tenant via an orchestration component to the consumer tenant.

[0087] FIG. 4B illustrates an example sequence diagram for generating and providing digital assets(s) by a data provider for access by decentral consumer network node(s) associated with a consumer tenant in response to a trigger received via an orchestration component from the consumer tenant. 241372

[0088] 20

[0089] FIGs. 5A, 5B illustrate examples of a user interface generated by local data provider component(s) of a provider tenant associated with a data provider for creating a data pipeline to offer digital asset(s) to data consumer(s).

[0090] FIGs. 6A, 6B illustrate examples of user interfaces generated by local data consumer component(s) of a consumer tenant associated with a data consumer for creating a data pipeline to request digital asset(s) from data provider(s)).

[0091] FIG. 7 illustrates an example of data structures stored in a configuration store associated with the orchestration component illustrated in FIG. 3.

[0092] FIG. 8A illustrates a flow chart of an example method for requesting or offering consumption of digital asset(s) associated with supply chain product(s) via a decentral network protocol by one or more decentral consumer network node(s) connected to one or more local data consumer component(s) of one or more local data consumer compute and storage environment(s) associated with one or more data consumer(s).

[0093] FIG. 8B illustrates a flow chart of an example method for requesting generation and provisioning of digital asset(s) by a data provider.

[0094] FIG. 80 illustrates a flow chart of an example method for orchestrating requests received via a local communication protocol for consumption of digital asset(s) via a decentral network protocol and / or for generation of digital asset(s) and provision of such data set(s) via the decentral network protocol.

[0095] FIG. 9A illustrates an example of a user interface displayed by a data providing component acting as a tenant of an orchestration component displaying requests for generating and providing digital asset(s) received from data consumer(s) and / or requests for consumption of digital asset(s) provided to data consumer(s).

[0096] FIG. 9B illustrates details of a request for generating and providing digital asset(s) received from a data consumer shown in FIG. 9A.

[0097] FIG. 10A illustrates an example of a user interface generated by local data consumer component(s) of a consumer tenant for displaying requests for generating and providing digital asset(s) provided to provider tenant(s) and / or requests for consumption of digital asset(s) received from provider tenant(s).

[0098] FIG. 10B illustrates an example of a user interface generated by local data consumer component(s) of a consumer tenant for displaying details of a request for consumption of digital asset(s) illustrated in the user interface of FIG. 10A.

[0099] FIG. 11 illustrates a decentral system for accessing digital asset(s) associated with supply chain product(s) produced or producible by a production by a data consumer via a decentral network.

[0100] FIG. 12 illustrates a block diagram of a system for generating digital asset(s) associated with supply chain product(s) and for providing the generated digital assets(s) for access via a decentral network by decentral 241372

[0101] 21 consumer network node(s) connected to local data consumer component(s) of a local data consumer compute and storage environment(s).

[0102] FIG. 13 illustrates a flow chart of an example method for generating digital asset(s) associated with supply chain product(s) produced or producible by a production and for providing the generated digital asset(s) for access via a decentral network protocol by one or more decentral consumer network node(s) connected to one or more local data consumer component(s) of one or more local data consumer compute and storage environment(s) associated with one or more data consumer(s).

[0103] FIG. 14 illustrates a block diagram of an example system for validating supply digital asset(s) associated with supply chain product(s) used to produce one or more product(s) and for generating digital production passport(s) at least in part based on the validated digital asset.

[0104] FIG. 15 illustrates a block diagram of a system for validating digital asset(s) associated with supply chain product(s) used to produce a product.

[0105] FIG. 16 illustrates a block diagram of an example system for generating and / or updating a digital product passport associated with a product based at least in part on validated supply chain product data associated with supply chain product(s) used to produce the product.

[0106] FIG. 17 illustrates a flow chart of an example method for validating digital asset(s) associated with supply chain product(s) used to produce one or more product(s) based on a request to consume the digital asset(s) received via an orchestration component from a data provider providing the digital asset(s).

[0107] FIG. 18 illustrates a method for generating digital product passport(s) associated with product(s) produced from one or more supply chain product(s) based at least in part on validated supply chain product data associated with such supply chain product(s).

[0108] DETAILED DESCRIPTION

[0109] FIG. 1 illustrates an example of a participant network of a product ecosystem associated with a decentral peer-to-peer network for transfer of data associated with supply chain products and produced products used within the product ecosystem.

[0110] The participant network 130 of the product ecosystem associated may be associated with a decentral peer-to-peer network decentral network 134 for exchange of data associated with or related to raw material(s), chemical intermediate product(s), chemical product(s), discrete product(s), end product(s), recycled material(s) and / or their respective production. The participant network may include one or more network participants 102 to 114 associated with decentral participant nodes 116 to 128. The network participants may be part of an industry or may be part of different industries. The network participants may be part of a product ecosystem including chemical products. The product ecosystem may include production chains to produce one or more end-product(s). The product ecosystem may include recycling chain(s) to recycle at least part of an 241372

[0111] 22 en d-of-life product resulting from the use of the end product(s). The product ecosystem may include re-use chain(s) to re-use at least a part of the end-of-life product(s).

[0112] The product ecosystem may include a raw material producer 104, a chemical product producer 102, a chemical product user 106, an end-product producer 108, an end-product user 110, an EOL product collector 112 and a recycler 114. The product ecosystem illustrated in FIG. 1 is a mere example and may include more or less network participants. For example, the product ecosystem may include a chain of chemical product producers instead of only one chemical product producer 102. The participant network 130 may include a chemical supply chain. The product ecosystem may allow the use of recycled materials resulting from recycling of end-of-life products to produce new products, such as chemical products. The product ecosystem may be associated with the production and / or recycling and / or re-use of physical products. The product may be a chemical product, an intermediate chemical product, a component, a component assembly, an end product, an end-of-life product or a recycled material.

[0113] The participant(s) of the participant network may be associated with the production of products and / or recycling and / or reuse of products. The decentral network participant may refer to a manufacturer of physical products, such as raw material producer 104, chemical product producer 102, chemical product user 106, end-product producer 108, a user of physical goods, such as end-product user 110, and / or a participant of a recycling chain associated with the physical product, such as EOL product collector 112 and recycler 114.

[0114] The participants and associated decentral network nodes of the decentral network may be associated with decentral participant identifiers. Each participant of the decentral network may be associated with one or more decentral participant identifier(s). The decentral participant identifier may comprise any identifier uniquely associated with a participant of the decentral network and / or with a production site of the participant of the decentral network. The decentral participant identifier may include letters and / or numbers. The decentral participant identifier may include one or more Universally Unique Identifier(s) (UUID(s)) and / or one or more Decentralized Identifier(s) (DID(s)). The decentral participant identifier may be associated with or may include a verifiable credential. The verifiable credential may be issued by a central or decentral identity issuer making one or more claims about a subject, such as an entity being a trustworthy participant of the decentral network. The verifiable credential may include at least one proof associated with the identity of the decentral network participant. The verifiable credential may include at least one proof associated with the membership of the decentral network participant in the decentral network. The verifiable credential may include at least one proof associated with an agreement signed by the decentral network participant. The verifiable credential may be presented by a decentral data consuming network node and may be verified by a decentral data providing network node prior to providing access to digital assets, hence ensuring that the digital assets can be exchanged in a secure and controlled manner within the decentral network.

[0115] The network participant may be associated with a participant node 116 to 128 and a decentral participant identifier associated with participant node(s) 116 to 128. The participant node may be associated with an endpoint for accessing the participant node. The decentral participant identifier in combination with the endpoint may uniquely identify the participant node within the decentral network. 241372

[0116] 23

[0117] The participant(s) of the participant network may be connected via material flows. The material flow may be a loop material flow 136. The material flow 136 may correspond to the flow of product from one participant of the participant network to the downstream participant of the participant network. The material flow may refer to a continuous or a discontinuous flow of product. The flow of product may include any means of transportation suitable to transport the product from a participant to the downstream participant. The means of transportation may include pipes, containers, barrels, packages. The material flow may be associated with raw materials used to produce the chemical product, such as virgin raw materials 158. The raw materials may be provided to chemical product producer 102 for producing chemical product(s) and / or intermediate chemical product(s) (not shown). The loop material flow may be associated with chemical product(s) 156. The chemical product(s) may be provided from chemical product producer 102 to chemical product user 106 for producing discrete product(s). In contrast to chemical production, the discrete products being produced are distinct units sold as individual products. The loop material flow 136 may be associated with recycled material 160. The recycled material may be provided from recycler 114 to chemical product producer 102 to produce chemical product(s).

[0118] At least part of the participants of the participant network may be associated with decentral participant network nodes 116 to 128. The decentral participant nodes 116 to 128 may be under control of the respective decentral participant associated with the respective decentral participant node. The decentral participant nodes may form decentral network decentral network. The decentral network decentral network may be a peer-to-peer communication network. The decentral peer-to-peer network decentral network may be configured to perform data transactions 132 according to the decentral network protocol. The decentral network protocol may relate to decentral identifier(s) identifying the digital assets and / or the at least one participant node and / or authentication and / or authorization mechanism(s) authentication and / or authorizing the at least one participant node for data transactions 132. Based on the authentication and / or authorization mechanism(s) a peer-to-peer communication between the decentral network nodes associated with the network participants may be established. The one or more authentication mechanism(s) may be associated with or linked to a decentral asset identifier as described in the context of FIG. 11 . The one or more authentication mechanism(s) associated with the decentral asset identifier may be accessible by the decentral participant nodes as described in the context of FIG. 11. The decentral configuration allows for more efficient use of computing resources and strengthens control by the data owners of the decentral network by allowing for data sovereignty.

[0119] Data transactions between decentral network participant nodes may be based on the decentral asset identifier associated with respective data to be accessed, for example as described in the context of FIG. 3. The decentral identifier may be uniquely associated with the physical entity of the product and associated product data. The decentral asset identifier may uniquely identify the respective product within the decentral network. The decentral asset identifier may be associated with further decentral identifier(s), such as decentral asset identifier(s) of production input(s) used to produce the product. This may allow to track the production input(s) used to produce a product, such as an end-product. The decentral identifier may be included in a digital representation associated with the product data and including a representation for accessing the product data.

[0120] The data flow 132 (e.g. transactions, depicted by dashed lines) between the decentral network participant nodes may be directly or indirectly associated with the material flow (depicted by bold solid lines) between the network participants. For 24 instance, the data flow may be directly associated with the material flow if data associated with a material provided from the raw material producer to the chemical product producer is accessed by decentral participant node 118 associated with said chemical product producer. For instance, the data flow may be indirectly associated with the material flow if data associated with a chemical product produced by the chemical product producer is accessed by decentral participant node 128 associated with the recycler.

[0121] The decentral participant nodes may be decentral computing nodes. The decentral computing node may be any device or system that includes at least one physical and tangible processor, and a physical and tangible memory capable of having thereon computer-executable instructions that are executed by a processor. The memory may take any form of volatile or non-volatile storages and may depend on the nature and form of the computing node.

[0122] At least part of the decentral participant nodes may be configured as decentral data providing nodes. At least part of the participant nodes may be configured as decentral data consuming nodes. A participant of the decentral participant network may be associated with a decentral data providing node and / or a decentral data consuming node depending on whether data is provided to downstream participants and / or consumed from upstream participants. For instance, the chemical product producer may be associated with a decentral data providing node configured to provide chemical product data to a downstream participant (e.g. the chemical product consumer and / or the OEM) for example as described in the context of FIG. 3. In addition to or alternatively, the chemical product producer may be associated with a decentral data consuming node configured to access data associated with material produced by an upstream participant (e.g. the material supplier).

[0123] The decentral network may include further decentral network nodes (not shown in FIG. 1). The further decentral network nodes may not be associated with or operated by a participant 102 to 114 of the product ecosystem. The further decentral network nodes may provide services for the network participants. The further decentral network nodes may be decentral infrastructure service nodes. The decentral infrastructure service nodes may provide services for the decentral participant nodes, such as verifying the identity of the decentral network participant nodes prior to performing a data exchange, providing decentral participant identifier(s) and / or providing endpoint(s) of participant node(s). The decentral network participant nodes may be associated with or include certificate(s), such as X.509 certificate(s). The certificate(s) may be associated with decentral infrastructure service node(s) including e.g. a certificate issuing service and / or a dynamic provisioning service providing dynamic attribute tokens (e.g. OAuth Access Tokens). This way the decentral network participant nodes may be associated with a unique identifier embedded in a X.509 certificate that identifies the respective decentral network participant node. The information required to verify the certificate may be provided via an authentication registry associated with the certificate issuing service and / or the dynamic provisioning service. For instance, in the IDSA Reference Architecture Model, Version 3.0 of April 2019, a decentral data providing node associated with a data owner of data and a decentral data consuming node associated with a data consumer requesting access to such data may use the Certification Authority (CA) and the Dynamic Attribute Provisioning Service (DAPS) to verify the identity of the counter node prior to performing exchange of the data (not shown in FIG. 1).

[0124] FIG. 2 illustrates an example of a nested product production chain including production processes, production inputs and production outputs produced by the production processes. The nested production chain may be part of a product ecosystem, such as the product ecosystem described in the context of FIG. 1. 25

[0125] The product may be produced by multiple production stages. The example in FIG. 2 illustrates three production stages. FIG. 2 illustrates an example of nested production stages for illustrative purposes only and more or less nested production stages may be part of the production chain. Each production stage may be associated with a production chain for producing the product or the supply chain product. Supply chain product(s) may include production inputs for producing the product. Supply chain product(s) may be produced by upstream production stage(s) with respect to the product production stage.

[0126] Production stage 1 202 may be associated with the product producer. The production stage 1 may include one or more production processes 204 to 208 using one or more production inputs per production process. The production stage 1 may produce the product. The production inputs to production stage 1 may be provided by upstream production stages 2-1 210 and 2-2 212. Production stages 2-1 and 2-2 may be associated with producers producing discrete production inputs and / or non-discrete production inputs. The Production stages 2-1 and 2-2 may each include one or more production processes using one or more production inputs per production process. The production inputs to production stages 2-1 and 2-2 may be provided by production stages 3-1 214 and 3-2 216. Production stages 3-1 and 3-2 may be associated with raw material producers. The production stages 3-1 and 3-2 may each include one or more production processes using one or more production inputs per production process. More concretely, production inputs for producing the product of production stage 1 - in this example a tire - may be provided by upstream production stages production stage 2-1 and production stage 2-2- in this example the rubber and metal wires to be used for producing the tire. Moving upstream for the rubber as one production input to production stage 1 producing the tire, production stage 3-1 may provide monomers, such as butadiene, styrene, isoprene and / or acrylonitrile to produce the rubber. Moving upstream for the metal wire as another production input to production stage 1 producing the tire, production stage 3-2 may provide metal containing ores used to produce the metal, such as steel.

[0127] The product produced by production stage 1 may be used as production input in downstream production stage(s) (not shown in FIG. 2) to produce further products, such as end-products.

[0128] The product and / or the supply chain product may be a discrete product. Discrete products may be produced in distinct, countable units. Each of such units may be individually identified. The product may include components, componentassemblies and end-products. The product may include batteries and / or battery components. The supply chain product may include chemical intermediate products, chemical products, components and component assemblies. The supply chain product may include batteries.

[0129] The product may be a chemical product. The supply chain product may be a virgin chemical material, a recycled chemical material and / or an intermediate chemical material used to produce the chemical product. The supply chain product may be a virgin chemical material, a recycled chemical material, an intermediate chemical material and / or a chemical material used to produce the product, such as the discrete product.

[0130] The chemical product may include inorganic chemical products and organic chemical products. Inorganic chemical products may be devoid of carbon atoms and / or carbon-hydrogen bond(s) while organic chemical products may include at least one carbon atom and / or at least one carbon-hydrogen bond. The chemical product may be a naturally occurring chemical product, i.e. any unprocessed chemical substance that is found in nature, such as chemicals from plants, micro-organisms, 241372

[0131] 26 animals, the earth and the sea or any chemical substance that is found in nature and extracted using a process that does not change its chemical composition. The chemical product may be produced via one or more process steps. The process steps may involve chemical reactions and / or physical processes. The physical process(es) may involve the use of chemical production inputs, such as chemical materials. Physical process(es) may include mixing, dispersing, extrusion, molding, casting, weaving, knitting, coating and / or filling.

[0132] The inorganic chemical product may include aluminium, iron, steel, copper, zinc, lead, nickel, titanium, magnesium, chromium, tin, manganese and / or cobalt. The iron may be produced from supply chain products including inorganic chemical materials, such as iron ore, coke and limestone. The steel may be produced from supply chain products including inorganic chemical materials, such as iron, oxygen and limestone. The aluminum may be produced from supply chain products including inorganic chemical materials, such as bauxite ore, sodium hydroxide and cryolite.

[0133] Organic chemical products may include detergents, cosmetic products, paints, lubricants, paper, pulp paper, paper boards and / or polymer products. Polymer products may include chemical products including or consisting of at least one polymer, such as synthetic textiles, footwear, mattresses, absorbent hygiene products, toys, fishing nets and fishing gear. The polymer may be selected from polyolefins, polyvinyls, polystyrenes, polyesters, polyethers, polyurethanes, poly(meth)acrylates, polyamides, polycarbonates, polyacetals, fluoropolymers, epoxides, silicons, polyimides, polylactic acid, cellulose, lignin, copolymers of such polymers and / or blends of such polymers. Organic chemical products may include compositions including alkanes, alkenes and alkynes, aromatic compounds, alcohols, aldeyhdes, ketons, carboxylic acids, esters, ethers, amines, amides, nitriles and / or halides.

[0134] Detergents may include chemical products used to remove dirt, grease and / or oil from surfaces, such as clothes, dishes or the like. Detergents may reduce or lower the surface tension of water to facilitate the removal of the dirt, grease and / or oil from the surfaces. Detergents may include surfactant(s), such as anionic surfactants, nonionic surfactants, cationic surfactants and / or amphoteric surfactants. Detergents may further include solvents, builders, such as phosphates, zeolites and / or citrates, enzymes, bleaching agents, optical brighteners, fragrances and / or preservatives. The detergents may be produced from supply chain products including organic chemical materials, such as surfactants, solvents, builders, enzymes, bleaching agents, optical brighteners, fragrances and / or preservatives.

[0135] Paints may include coating materials used to coat at least a part of the surface of an object. Paints may be used to protect the surface, to improve the appearance (e.g. color and / or texture) of the surface and / or to provide texture to the surface. Paints may include solvents, pigments and physically and / or chemically curable polymer(s). Paints may further include additives, such as thickeners, UV additives, flow additives or the like. Physically curable polymer(s) may form a coating film during release solvent from the paint by interlooping of polymer chains. Chemically curable polymer(s) may form a coating film by crosslinking reactions between complementary functional groups, e.g. chemical groups that can undergo chemical reactions. Crosslinking may be initiated by thermal energy and / or irradiation. Paints may be liquid or solid. The paint may be produced from supply chain products including organic chemical materials, such as solvents, pigments, physically and / or chemically curable polymer(s) and additives. 241372

[0136] 27

[0137] The lubricant may be chemical products capable of reducing friction between surfaces (preferably metal surfaces), such as surfaces of mechanical devices or machines. A mechanical device may be a mechanism consisting of a device that works on mechanical principles, such as the machines previously described. The lubricant may be a lubricating liquid, lubricating oil or lubricating grease. The lubricant may be produced from supply chain products including organic chemical materials, such as base oils, additives and thickeners.

[0138] Textiles, footwear, mattresses, absorbent hygiene products, toys, fishing nets and fishing gear may include or consist of synthetic polymers, e.g. organic polymers produced by chemical reaction(s) and / or mixture of synthetic polymers and naturally occurring polymers. Textiles and footwear may include polyesters, nylon, acrylic polymers, polypropylene, polyurethane, polyethylene and / or polytetrafluoroethylene. Such polymer(s) may be extruded to produce yearn which may then be used in physical knitting and / or weaving processes to produce the textiles and / or parts of the footwear. Soles of footwear may include ethylene-vinyl acetate, polyurethane, natural or synthetic rubber, thermoplastic rubber, thermoplastic polyurethane and / or polyvinyl chloride. The soles may be produced from such polymers using injection molding, compression molding or foaming. The textiles and parts of the footwear may be produced from supply chain products including organic chemical materials, such as polymer(s) produced from chemical reaction(s). Mattresses may include one or more layers of polymer foams produced by polymerizing monomers in the presence of blowing agents. The layers of polymers may be encased in a fabric cover. The fabric cover may be produced from natural polymers, like cotton and / or synthetic polymers, like polyester. The mattresses may be produced from supply chain products including organic chemical materials, such as monomers, blowing agents, natural polymer(s) and / or polymer(s) produced from chemical reaction(s). Tires may be produced by assembling the inner liner made of rubber, the body piles made of fabric cord, such as nylon cord and / or polyester cord, coated with rubber, the rubber sidewalls, the bead rings, e.g. steel wires coated with rubber, the steel belts and the rubber tread and heating the assembly in a mold to vulcanize, e.g. crosslinking, the rubber. The tires may be produced from supply chain products including organic chemical materials, such as rubber and polymer cords, and inorganic chemical materials, such as steel. Absorbent hygiene products may include top sheets of nonwoven fabric, such as polypropylene or polyethylene, acquisition and distribution layers of nonwoven material layers, absorbent cores of cellulose fibers combined with superabsorbent polymers (SAP), back sheets made of polyethylene or bilaminate materials and adhesives. The absorbent hygiene products may be produced from supply chain products including polymers, such as polypropylene, polyethylene, cellulose, polyacrylates and adhesives. Toys may include plastic toys including one or more polymers. The toys may be produced from supply chain products including at least one polymer, such as acrylonitrile butadiene styrene, polyvinyl chloride, polyethylene, polypropylene, polyester, polyamide and / or thermoplastic elastomers. Fishing nets and fishing gear may include synthetic and / or naturally occurring polymers. Supply chain products used to produce the fishing nets and / or fishing gear may include polyethylene, polypropylene, polyester, polyamide, cotton and / or hemp.

[0139] FIG. 3 illustrates an example of a system architecture including a local compute and / or storage environment and a decentral network environment.

[0140] Local compute and / or storage environment: 241372

[0141] 28

[0142] The local compute and / or storage environment may include an orchestration component 302 and a plurality of local data provider compute and / or storage environments and / or local data consumer compute and / or storage environments, such as 306 to 312, acting as tenants of the orchestration component. Each tenant may be associated with a unique identifier (e.g. tenant ID) uniquely identifying the tenant within the local compute and / or storage environment.

[0143] The local compute and / or storage environment may include distributed compute and / or storage environments controlled by the tenants and / or the orchestration component. Local compute and / or storage environment may relate to access controlled distributed compute and / or storage components communicatively connected through local communication protocol(s). Local compute and / or storage environment may relate to access controlled distributed compute and / or storage components communicatively connected through local communication protocol(s). Local may relate to the association of the compute and / or storage environment with the supply chain product data storage or data base and / or the digital asset storage or data base of the supply chain product producer accessible by the supply chain product producer or to the association of the compute and / or storage environment with a storage or data base storing processed digital assets of the digital asset consumer accessible by the digital asset consumer. Local may hence relate to the accessibility of digital assets or processed digital assets, which may be shared by decentral network nodes under control of the supply chain product producer (e.g. the data provider) or the data consumer.

[0144] The local communication protocol may facilitate communication in distributed compute and / or storage environment. The local communication protocol may include web protocols, such as HTTP / HTTPS methods, URI, MIME types or combinations thereof. The local communication protocol may implement stateless communication. Stateless communication may include requests and triggers that include all data required to process the request or trigger by the at least one orchestration component. This way, the orchestration component(s) do not have to retain session information, allowing efficient communication with multiple tenants and improving scalability and reliability. The local communication protocol may be configured to communicatively couple the orchestration component with multiple tenant components. The local communication protocol may be configured to decouple communication between tenant components. The local communication protocol may be configured to open communication channel between the orchestration component and multiple tenant components. The local communication protocol may be configured to close communication channel between the orchestration component and multiple tenant components. The orchestration component may be configured to orchestrate communication channels to multiple tenant components. The orchestration component may be configured to centrally orchestrate communication to multiple tenant components. The orchestration component may be configured to centrally orchestrate communication between multiple tenant components indirectly, e.g. through or via the orchestration component. The tenant components may be configured to communicate with orchestration component directly. The tenant components may be configured to not communicate with other tenant components directly. The tenant components may be configured to communicate with other tenant components indirectly, e.g. through or via the orchestration component. The core feature of the local network protocol includes the local tenant identifiers stored and used by the orchestration component for communication with the tenants, while individual tenants do not have access to tenant identifiers of other tenants and can only communicate with the other tenants through the orchestration component.

[0145] Tenants: 241372

[0146] 29

[0147] The tenant(s) may be configured to communicate with the orchestration component. The tenant(s) may be configured to communicate with other tenant(s) via or by using the orchestration component. The tenant(s) may be configured to communicate with other tenant component(s) solely through the orchestration component. The tenant(s) may not be communicatively coupled to each other. The tenant(s) may be configured to communicate with the orchestration component via peer-to-peer communication according to the local communication protocol(s).

[0148] The local data provider compute and / or storage environments may include one or more data provider component(s) (e.g. tenant component(s)) configured to generate and / or provide digital assets, one or more local data provider component(s) configured to request consumption of generated digital asset(s) and / or one or more local data provider component(s) configured to orchestrate, e.g. to monitor and / or control, generation and / or provision of digital assets. The local data provider compute and / or storage environments may include the local data provider component(s) illustrated in FIG. 12. The one or more local data provider component(s) may be connected to decentral provider network node(s), such as nodes 116, 118 and 120. The local data consumer compute and / or storage environments may include one or more data consumer component(s) (e.g. tenant component(s)) configured to trigger access of digital assets via the decentral network protocol, one or more local data consumer component(s) configured to process accessed digital assets and / or one or more local data consumer component(s) configured to orchestrate, e.g. to monitor and / or control, accessing of digital assets and / or processing of accessed digital assets. The local data consumer compute and / or storage environments may component(s) illustrated in FIG. 14 to FIG. 16.

[0149] The exchange of digital assets may be orchestrated via one or more data pipeline(s) configured by the one or more tenants. The one or more data pipeline(s) configured by the one or more tenants may be orchestrated by orchestration component. The data pipelines may be configured for generating digital assets to be provided and / or consumed via one or more decentral network protocols. The data pipelines may be configured for processing digital assets consumed via the decentral network protocol(s). The data pipeline may be connected or communicatively coupled to or may relate to a local data source associated with the tenant. The local data source may store supply chain product data used to generate the digital asset(s) exchanged via the decentral network. The local data source may store validated supply chain product data obtained by processing (e.g. validating) digital assets received or consumed via the decentral network.

[0150] The configured data pipeline may be associated with any number of computational steps. The computational step(s) may be included in the data pipeline and / or may provide access to data specified by the data pipeline. The computational step(s) may be performed within the respective tenant configured for generating and providing digital assets and / or the respective tenants configured for consuming generated digital assets connected by the data pipeline. The computational step(s) may be defined by the user creating the data pipeline. The user may select one or more computational step(s) from a list of available computational step(s) upon creating the data pipeline. The computational step(s) may be predefined for given data pipeline(s) and the user may select a predefined data pipeline upon creating the data pipeline. A computation step may include a specified computation platform (e.g., JavaScript, Kusto Query Language, SparkQL, Python, C#Linq), a specified input to the computational step, a specified computation for the computational step, a specified output schema, a specified output storage, or a combination thereof. A specified input to a computational may identify a data input or parameters thereof or a data source storing data inputs on which the computational step will operate. A specified computation for a 241372

[0151] 30 computational step may identify one or more executable operations to be performed on a specified input to the computational step. A specified computation can be a template computation (e.g., map, reduce, fuse, unfold, append, filter, split, or the like, or more generally any type of arithmetic operation, aggregation, summarization, filtering, sorting, bounding, or other computation), a custom computation (e.g., identified from an existing set of assets or provided through an associated script editor), or a combination thereof. A specified output schema for a computational step may define the form or structure of the computational result of the step. For example, a specified output schema may include an identification of a particular component of a computational result (e.g., variable, array, vector, matrix, row, column, property) and one or more corresponding attributes (e.g., data type, description, dimensionality). The specified output schema may include a data format for the computational result.

[0152] The configured data pipeline may be associated with a data pipeline identifier uniquely identifying the data pipeline within the respective tenant. The data pipeline may be associated with configuration data. The configuration data may define computational step(s) included in the data pipeline, a specified input to each computational step, a specified computation for each computational step, a specified output schema and / or a specified output storage. The output storage may be predefined. The output storage may be selected by the user upon generation of the data pipeline. The data pipeline identifier and the configuration data may be stored in a data storage included in the tenant setting generating the data pipeline. The data pipeline identifier may be used to generate digital asset(s) according to computational step(s) as defined by the respective data pipeline. The data pipeline identifier may be used to map digital asset(s) to respective data pipeline(s), allowing to process the digital asset(s) according to computational step(s) as defined by the respective data pipeline.

[0153] The one or more local data consumer component(s) may be connected to decentral provider network node(s), such as node 122.

[0154] The decentral provider network nodes and the decentral consumer network nodes may be part of a decentral network, such as the decentral network described in the context of FIG. 1 . The decentral provider and consumer network nodes may be associated with a decentral participant identifier uniquely identifying such decentral network nodes within the decentral network environment. The local data provider and local data consumer components may be associated with the decentral participant identifier uniquely identifying such components within the decentral network environment. The tenants may be associated with the decentral participant identifier uniquely identifying such tenants within the decentral network environment. The decentral participant identifier may include letters and / or numbers. The decentral participant identifier may include one or more Universally Unique Identifier(s) (UUID(s)) and / or one or more Decentralized Identifier(s) (DID(s)). The decentral participant identifier may be associated with or may include a verifiable credential. The verifiable credential may be issued by a central or decentral identity issuer making one or more claims about a subject, such as an entity being a trustworthy participant of the decentral network. The verifiable credential may include at least one proof associated with the identity of the decentral network participant. The verifiable credential may include at least one proof associated with the membership of the decentral network participant in the decentral network. The verifiable credential may include at least one proof associated with an agreement signed by the decentral network participant.

[0155] Orchestration component: 241372

[0156] 31

[0157] The orchestration component may include a local orchestration compute and / or storage environment. The local orchestration compute and / or storage environment may include one or more local orchestration component(s) configured to receive requests via the local communication protocol(s) from local data provider component(s) and / or local data consumer component(s), one or more local orchestration component(s) configured to process the received requests, one or more local orchestration component(s) configured to generate and provide requests via the local communication protocol(s) to local data provider component(s) and / or local data consumer component(s), one or more component(s) configured to store data structure(s) received via the local communication protocol(s) from local data consumer component(s) and / or to store mappings between tenant identifiers and decentral participant identifiers associated with such tenants. The orchestration component may be communicatively connected to the one or more tenants. The orchestration component may be to orchestrate, e.g. control and / or monitor, data exchange via the decentral network by exchanging, receiving and / or sending, requests via the local communication protocol with, from and / or to local data consumer and / or provider component(s). The orchestration component may be communicatively connected to the tenant(s) or tenant component(s). The orchestration component may be configured to communicate with tenant(s) or tenant component(s) based on the local communication protocol. The orchestration component may be configured to communicate with individual tenant(s) or tenant component(s) based on the local communication protocol. The orchestration component may be configured to orchestrate communication channels to multiple tenants or tenant components. The orchestration component may be configured to centrally orchestrate communication to multiple tenants or tenant components. The orchestration component may be configured to centrally orchestrate communication between multiple tenants or tenant components indirectly, e.g. through or via the orchestration component. The orchestration component may implement network interface(s) for communication with the tenants or tenant components via the local communication protocol. The network interface(s) may include API(s), such as a REST API(s).

[0158] The orchestration component may be communicatively connected to one or more databases storing configuration data, such as database 304. The configuration data may relate to the orchestration of data pipelines configured by the one or more tenants. The database may store pairs of decentral participant identifiers and respective tenant identifiers. Examples of data structures stored in database 304 are illustrated in FIG. 7.

[0159] The orchestration component may receive triggers from the local data consuming component(s) for generating digital asset(s) to be provided and / or consumed via the one or more decentral network protocols of the decentral network. In addition or alternatively, the orchestration component may receive requests from the local data providing component(s) for consuming generated digital asset(s) via the one or more decentral network protocols of the decentral network. The triggers and / or requests may be triggered after generation of the data pipeline. The triggers and / or requests may relate to the tenant identifier associated with the tenant component(s) providing the request to the orchestration component and configuration data associated with the data pipeline. The triggers and / or requests may not relate to the digital asset(s) to be provided and / or to be consumed and to the generated digital asset(s). The digital asset(s) may be stored in a local database of the tenant configured for data provisioning and access to such database via the decentral network may be controlled based on the decentral asset identifiers associated with the digital assets stored in such database. Based on the tenant identifier and the decentral participant identifier(s) included in the triggers and / or requests, the orchestration component may identify the tenant the request or trigger was received by and the tenant(s) the request or trigger is to be provided to. Based on the configuration data included in the received requests or triggers, the orchestration component may generate and provide a 241372

[0160] 32 request for generating digital asset(s) to be provided and / or consumed or may generate and provide a request for consumption of generated digital asset(s) to the identified tenant(s). The requests may include at least a part of the configuration data included in the requests or triggers received by the orchestration component. Based on the configuration data the tenant receiving the request may generate a new data pipeline or assign the request to an existing data pipeline. The new data pipeline may be generated based on the configuration data included in the received request. The staged data transfer concept utilizing the orchestration component is described in more detail in FIG. 4A and FIG. 4B.

[0161] Depending on the envisaged data transfer to be executed via the decentral network, the orchestration component orchestrates the data pipeline setup in the local environments of the tenants associated with decentral network nodes. The communication of the actual digital assets is hence not executed via the orchestration component and the orchestration component does not have access to such digital assets. Hence the assets are transferred only in peer-to-peer communication between nodes of the decentral network under full control of the data owner of the digital assets. The orchestration component only enables communication between tenants with respect to requests for digital assets or offers of digital assets and ensures that the digital asset(s) transferred via the decentral network adheres to the formats and content the provider and / or recipient of such digital asset(s) expect. This way, access to the digital assets associated with the supply chain products are controlled by of the respective data owner of such digital assets, such as the supply chain product producers, while enabling secure and efficient transfer of such digital assets via the decentral network based on the orchestration of requests from tenants by the orchestration component.

[0162] Decentral network environment:

[0163] The decentral network environment may include decentral network nodes, such as nodes 116 to 122. The decentral network node(s) may form the decentral network (see also FIG. 1). The decentral network nodes may be configured to communicate with other decentral network nodes via peer-to-peer communication according to decentral communication protocol. The decentral communication protocol may facilitate communication in decentral network environment. In addition, the decentral network nodes may be communicatively coupled to components of the local compute and / or storage environment, such as tenant components. Decentral network nodes may be configured to communicate directly or indirectly, e.g. through bridging component(s) configured to translate between local and decentral communication protocol(s), with tenant components based on the local communication protocol. The decentral network protocol may include the decentral participant identifiers and / or decentral asset identifier(s) associated with digital assets of supply chain products being discoverable and / or accessible by decentral participant nodes, e.g. through, via, in or by decentral storage. Individual decentral network nodes have hence access to decentral participant identifiers related to other decentral network nodes and can communicated directly with other decentral network nodes. In addition at least a part of the decentral network nodes may hence have access to the decentral asset identifiers associated with digital assets and can request access to such digital assets based on the decentral asset identifiers.

[0164] The setup of the local computing and / or storage environment and the decentral network environment illustrated in FIG. 3 are mere examples and shall not be considered limiting. Different numbers of tenants with or without associated decentral network node are feasible. Also different functionalities including the generation of data pipelines configured for data providing or consuming may be executed by a single or multiple tenant(s). 241372

[0165] 33

[0166] FIG. 4A illustrates an example sequence diagram for accessing digital asset(s) by decentral consumer network node(s) associated with a consumer tenant from decentral data provider network node(s) associated with a provider tenant in response to a request for consumption of the digital asset(s) provided by the provider tenant via an orchestration component to the consumer tenant. The digital asset(s) may be associated with supply chain products.

[0167] The provider tenant, such as tenant 306, may be associated with a data provider, such as a supply chain product producer producing the supply chain products. The decentral provider network node(s), such as node 118, may be connected to local data provider component(s) of the provider tenant. The decentral provider network node may connect the provider tenant to the decentral network (see FIG. 3). The consumer tenant, such as tenant 312, may be associated with a data consumer, such as a supply chain product consumer or an entity generating digital product passports. The decentral consumer network node(s), such as node 120, may be connected to local data consuming component(s) of the consumer tenant. The decentral consumer network node may connect the consumer tenant to the decentral network (see FIG. 3). Communication between the decentral network nodes may be based on a decentral network protocol (depicted by thick dashed lines, see also FIG. 3). Each tenant may be associated with a local identifier uniquely identifying the tenant in the local compute and storage environment, such as a tenant identifier. The decentral provider and consumer network nodes may be associated decentral participant identifiers and uniquely identifying the node, tenant component(s) connected to the node, the tenant connected to the node and / or the data provider or data consumer associated with the tenant within the decentral network. The provider tenant and consumer tenant may be communicatively coupled to the orchestration component (see FIG. 3). Communication between the orchestration component and the tenants may be based on a local communication protocol (depicted by thin dashed lines, see also FIG. 3). The tenants may communicate with each other solely via the orchestration component based on the local communication protocol. The digital asset(s) may be associated with supply chain product(s). The supply chain product(s) may include supply chain product(s) described in the context of FIG. 2. The supply chain product(s) may be produced or producible by a production associated with the data provider (see also FIG. 11).

[0168] For generating the request for consumption of the assets(s), a data pipeline for generating the digital asset(s) and for providing the generated digital asset (s) for access via the decentral network based on the decentral network protocol may be generated by one or more local data provider component(s). The data pipeline may be generated as described in the context of FIG. 3 and FIG. 8A. The data pipeline may be associated with configuration data. The configuration data may be provided via a user interface, for example as illustrated in FIG. 5A and FIG. 5B. The configuration data may be associated with the configuration of the data pipeline. The configuration data may include a configuration data identifier uniquely identifying the configuration data within the provider tenant and data pipeline configuration data associated with a configuration of the data pipeline. The data pipeline configuration data may relate to the configuration data identifier and may include a local source data storage storing supply chain product data used to generate the digital asset(s), a data model defined by the data provider for generating the digital asset(s), a mapping the data points included in the defined data model to the data structure of the source data storage and policy data defining access by decentral consumer network node(s) to the generated digital asset(s). The provider tenant may generate the digital asset(s) based on the generated data pipeline, for example as described in the context of FIG. 8A. The generated digital asset may include a decentral asset identifier and transformed supply chain product data. The decentral asset identifier may not be discoverable and / or accessible via the decentral network. The decentral asset identifier may not be provided to the decentral network to be discoverable and / or 241372

[0169] 34 accessible by decentral network nodes of the decentral network. The generated digital asset(s) may be linked via the decentral asset identifier(s) to the policy data (see FIG. 8A). The policy data may be linked to the decentral asset identifier(s) based on the configuration data. This way, access to the digital asset(s) by decentral consumer network node(s) may be controlled via the decentral asset identifier(s) based on the policy data. The provider tenant(s) may provide the generated digital asset(s) for access by the decentral consumer network node(s) associated with the consumer tenant through or via the decentral network based on the decentral network protocol. The generated digital asset(s) may be stored in a local data storage of the provider tenant for access by the decentral consumer network node(s). Access to the local data storage may be controlled by the data owner of the digital asset(s), such as the supply chain product producer, via the decentral asset identifier.

[0170] Generation of digital asset(s) using the data pipeline may trigger generation of the request. The request may include the tenant identifier associated with the provider tenant generating the request, the decentral asset identifier(s) associated with the generated digital asset(s) requested to be consumed by or offered to the data consumer(s) and the decentral participant identifier(s) associated with the decentral consumer network node(s) associated with the data consumer(s). The request may not include the generated digital asset(s). The generated request may be provided via the local communication protocol to the orchestration component.

[0171] Upon receiving the request, the orchestration component may retrieve tenant identifier(s) related to the decentral participant identifier(s) included in the received request from the database storing the mapping data, such as configuration storage 304 (see also FIG. 80). The orchestration component may provide the request to the local data consumer component(s) associated with the determined local identifier(s) via the local communication protocol. Providing the request may include adding further configuration data for decentral network transfer, such as data associated with the provider tenant providing the request, and providing the enriched request. Providing the request may include generating a new request based on the received request and providing the new request. The new request may include data included in the received request and further configuration data for decentral network transfer, such as data associated with the provider tenant providing the request. Data associated with the provider tenant may include the decentral participant identifier associated with the provider tenant and an endpoint of the decentral provider network node associated with the provider tenant. Such data may further include the name of the data provider associated with the provider tenant. The data associated with the provider tenant may may be gathered based on the tenant identifier associated with the provider tenant. The request provided by the orchestration component to local data consumer component(s) may include the decentral asset identifier(s), the decentral participant identifier associated with the decentral provider network node(s) and endpoints of the decentral provider network node(s). The request may further include the name of the data provider.

[0172] The requests received from the orchestration component may be displayed within a graphical user interface generated by the local data consumer component(s) (see for example FIG. 10A). The received requests may be accepted by the data consumer associated with the local data consumer component(s). Accepting may include triggering access of the digital asset(s) associated with the received request.

[0173] Triggering access may include triggering gathering of policy data associated with the digital asset(s) to be consumed via the decentral network from the provider node associated with the provider tenant. Policy data may be gathered by requesting a 241372

[0174] 35 data catalog of decentral provider network node associated with the provider tenant based on the endpoint included in the received request. The request for the data catalog may include the decentral participant identifier associated with the decentral consumer network node and the decentral asset identifier(s) included in the received request. The data catalog may be a collection of digital representations of digital asset(s) accessible for the requesting decentral consumer network node. The decentral provider network node may generate the data catalog based on the received decentral participant identifier and the decentral asset identifier(s). The digital representation(s) may include the policy data associated with the digital asset(s) associated with the decentral asset identifier(s). The gathered policy data may be provided to the local data consumer component(s) for validation. The gathered policy data may be displayed within a user interface generated by the local data consumer component(s) for validation by a user (see for example FIG. 10B). A response indicating acceptance or rejection of the policy data may be generated by the local data consumer component(s) and may be provided to the consumer node. The response may be generated upon receiving a user input indicating acceptance or rejection of the policy data. Upon accepting the policy data, the local data consumer component(s) may generate a data pipeline for processing consumed digital asset(s), for example as described in the context of FIG. 8B. Generation of the data pipeline may trigger generation of a representation of accessing one or more local data consumer component(s) by the decentral consumer network node connected to the local data consumer component(s). The representation may be generated by the local data consumer component(s). The representation may include a locator or pointer to or a communication interface of the local data consumer component(s). The locator or pointer may include the configuration data identifier. The representation may be provided along with decentral asset identifier(s) of digital asset(s) to be provided to the local data consumer component(s) to the decentral consumer network node. Based on representation, the decentral consumer network node may provide digital asset(s) gathered via the decentral network protocol to the local data consumer component(s). Upon accepting the policy data, an existing data pipeline may be selected for processing the consumed digital asset(s).

[0175] The consumer node may initiate negotiation of the policy data according to a decentral negotiation protocol upon receiving a response indicating acceptance of the policy data. The decentral negotiation protocol may be part of the decentral communication protocol. Upon successful negotiations, agreement data including an agreement identifier and the negotiated policy data may be generated. The agreement data may be generated by the decentral provider network node and may be provided to the decentral consumer network node. The decentral consumer network node may request access to the generated data sets via the decentral network at the decentral provider network node. The request may include the decentral participant identifier associated with the decentral consumer network node, the decentral asset identifier(s) and the agreement identifier. The decentral provider network node may authorize the request based on the agreement identifier and the decentral participant identifier(s) and may gather the digital asset(s) based on the decentral asset identifier(s) from the local data storage of the provider tenant storing the digital asset(s). The decentral provider network node may provide the gathered digital asset(s) via the decentral network to the decentral consumer network node. The decentral consumer network node may provide the received digital asset(s) to the local data consumer component(s) for processing based on the received representation for accessing the local data consumer component(s). The data provided to the local data consumer component(s) may include the configuration data identifier and the digital asset(s). The local data consumer component(s) receiving the digital asset(s) may be configured to parse the received data to determine the configuration data identifier. Based on the determined configuration data identifier, the local data consumer component(s) may be configured to determine the data pipeline associated with such configuration data identifier. The data pipeline may be determined using a 241372

[0176] 36 local data pipeline database storing configuration data associated with data pipelines generated by the local data consumer component(s). Configuration data associated with the configuration data identifier may be gathered and the provided digital asset(s) may be processed according to the gathered configuration data by the local data consumer component(s). This way, digital asset(s) received from multiple decentral provider network nodes may be processed using a plurality of data pipelines. This may allow to use different rule(s) for processing the gathered digital asset(s) and / or to persist the processed data in different local target data storages of the consumer tenant. This way, product passports for different products may be generated based on the processed digital assets having been received from multiple decentral provider network nodes.

[0177] By orchestrating communications between provider and consumer tenants via the central orchestration component, consumer tenants can be reliably and efficiently notified with respect to digital asset(s) available for access via the decentral network at provider tenants. This way, consumer tenants may efficiently gather the accessible digital asset(s) via the decentral network under full data sovereignty of the data providers without having to explicitly request generation and provision of such digital asset(s) from multiple data providers. In addition, this allows gathering of digital asset(s) independent from the receipt of supply chain product(s) associated with such digital asset(s) by the data consumer, facilitating generation of digital product passports using such digital asset(s) by downstream participants of the product ecosystem not being directly connected via material flows with the data provider. Efficient gathering of digital asset(s) based on requests received via the local communication protocol ensures a higher quality of the data included in the generated digital product passports and hence allows a more efficient processing of the products and / or production of further products using the product as production input based on the data included in the digital product passport.

[0178] FIG. 4B illustrates an example sequence diagram for generating and providing digital assets(s) by a data provider for access by decentral consumer network node(s) associated with a consumer tenant in response to a trigger received via an orchestration component from the consumer tenant. The digital asset(s) may be associated with supply chain products.

[0179] The consumer tenant, such as tenant 312, may be associated with a data consumer, such as a supply chain product consumer or an entity generating digital product passports. The decentral consumer network node(s), such as node 120, may be connected to local data consuming component(s) of the consumer tenant. The decentral consumer network node(s) may connect the consumer tenant to the decentral network (see FIG. 3). The provider tenant, such as tenant 306, may be associated with the data provider, such as a supply chain product producer. The decentral provider network node(s), such as node 118, may be connected to local data provider component(s) of the provider tenant. The decentral provider network node(s) may connect the provider tenant to the decentral network (see FIG. 3). Communication between the decentral network nodes may be based on a decentral network protocol (depicted by thick dashed lines, see also FIG. 3). Each tenant may be associated with a local identifier uniquely identifying the tenant in the local compute and storage environment, such as a tenant identifier. The decentral provider and consumer network nodes may be associated decentral participant identifiers and uniquely identifying the node, tenant component(s) connected to the node, the tenant connected to the node and / or the data provider or data consumer associated with the tenant within the decentral network. The provider tenant and consumer tenant may be communicatively coupled to the orchestration component (see FIG. 3). Communication between the orchestration component and the tenants may be based on a local communication protocol (depicted by thin dashed lines, see also FIG. 3). The tenants may communicate with each other solely via the orchestration component based on the local 37 communication protocol. The digital asset(s) may be associated with supply chain product(s). The supply chain product(s) may include supply chain product(s) described in the context of FIG. 2. The supply chain product(s) may be produced or producible by a production associated with the data provider (see also FIG. 11). The orchestration component may be configured to orchestrate requests received from provider and / or consumer tenants as described in the context of FIG. 3 and FIG. 4A.

[0180] For generating the trigger a data pipeline for processing the digital asset(s) gathered via the decentral network from the data provider network node(s) may be generated by the one or more local data consumer component(s). The data pipeline may be generated as described in the context of FIG. 3 and FIG. 8B. The data pipeline may be associated with configuration data. The configuration data may be provided via a user interface, for example as illustrated in FIG. 6A and FIG. 6B. The configuration data may be associated with the configuration of the data pipeline. The configuration data may include a configuration data identifier uniquely identifying the configuration data within the consumer tenant, data pipeline configuration data associated with a configuration of the data pipeline and decentral participant identifier(s) associated with the decentral provider network node(s). The data pipeline configuration data may relate to the configuration data identifier and may include a representation for accessing a target data storage configured to store processed digital assets, a data structure or data model for collecting properties associated with the supply chain product(s), a mapping for mapping the data points included in the processed digital assets to the data structure of the target data storage and one or more validation rules for processing, e.g. validating, the digital asset(s) gathered via the decentral network protocol from the decentral provider network node(s). The configuration data may be generated by generating a data providing pipeline for processing digital asset(s) consumed via the decentral network protocol, for example as described in the context of FIG. 3, FIG. 6A, FIG. 6B and FIG. 8B. Upon generation of the data pipeline a representation for accessing the local data consumer component(s) may be generated as described in the context of FIG. 4A.

[0181] Generation of the data pipeline may trigger generation of the trigger. The trigger may include the tenant identifier associated with the consumer tenant generating the trigger, the data structure or data model for collecting properties associated with the supply chain product(s) and the decentral participant identifier(s) associated with the decentral provider network node(s).

[0182] The request may further include the configuration data identifier. The generated trigger may be provided via a local communication protocol to the orchestration component.

[0183] Upon receiving the trigger, the orchestration component may retrieve tenant identifier(s) related to the decentral participant identifier(s) included in the receive trigger from the database storing the mapping data, such as configuration storage 304 (see also FIG. 80). The orchestration component may further provide data included in the trigger, such as the data model or collecting properties associated with the supply chain product(s), to a local data storage associated with the orchestration component, such as configuration storage 304.

[0184] The orchestration component may provide the trigger to one or more local data provider component(s) associated with the determined local identifier(s) via the local communication protocol. Providing the trigger may include adding further configuration data for decentral network transfer, such as data associated with the consumer tenant providing the trigger, and providing the trigger request. Providing the trigger may include generating a new trigger based on the received trigger and providing the new trigger. The new trigger may include data included in the received trigger and further configuration 38 data for decentral network transfer, such as data associated with the consumer tenant. Data associated with the consumer tenant may include the decentral participant identifier associated with the decentral consumer network node(s) and / or the name of the data consumer. The data associated with the consumer tenant may be gathered based on the tenant identifier associated with the consumer tenant. The trigger provided by the orchestration component to the local data provider component(s) may include the data structure or data model for collecting properties associated with the supply chain product(s) or a representation for accessing the data structure or data model and the decentral participant identifier associated with the decentral consumer network node(s). The trigger may further include the name of the data consumer.

[0185] The triggers received from the orchestration component may be displayed within a graphical user interface generated by one or more local data provider component(s) (see for example FIG. 9A and FIG. 9B). The received triggers may be accepted by the data provider associated with the local data provider component(s). Accepting may include triggering generation and provision of the requested digital asset(s).

[0186] Triggering generation and provision may include generating a data pipeline for generating digital asset(s) according to the data structure or data model included in the received trigger or accessible via the representation included in the received trigger. The data pipeline may be generated as described in the context of FIG. 8B. Generating a data pipeline may include gathering the data structure or data model via the local communication protocol from a local data storage associated with the orchestration component, such as configuration storage 304, based on the representation included in the received trigger. The data structure or data model may be gathered before or during generation of the data pipeline. Triggering generation and provision may include selecting an existing data pipeline associated with such data structure or data model.

[0187] The local data provider component(s) may generate the digital asset(s) based on the generated data pipeline, for example as described in the context of FIG. 8A. The generated digital asset may include a decentral asset identifier and transformed supply chain product data. The decentral asset identifier may not be provided to the decentral network to be discoverable and / or accessible for decentral network nodes of the decentral network. The generated digital asset(s) may be linked via the decentral asset identifier(s) to policy data defined during generation of the data pipeline or defined by an existing data pipeline (see FIG. 8A). The policy data may be linked to the decentral asset identifier(s) based on the configuration data. This way, access to the digital asset(s) may be controlled via the decentral asset identifier(s) based on the policy data. The local data provider component(s) may provide the generated digital asset(s) for access by the decentral consumer network node(s) through or via the decentral network. The generated digital asset(s) may be stored in a local data storage of the provider tenant for access by the decentral consumer network node(s). Access to the local data storage may be controlled by the data owner of the digital asset(s), such as the supply chain product producer, via the decentral asset identifier.

[0188] Generation of digital asset(s) using the data pipeline may trigger generation of a request for consumption of the generated digital asset(s), for example as described in the context of FIG. 4A. The request may be triggered upon or after generation of the digital asset(s). The request may be provided via the local communication protocol to the orchestration component. The orchestration component may determine consumer tenants based on the decentral participant identifier(s) associated with the decentral consumer network node(s) included in the received request. The orchestration component may provide the request to the determined consumer tenants, for example as described in the context of FIG. 4A. 241372

[0189] 39

[0190] The requests received from the orchestration component may be displayed within a graphical user interface generated by the local data consumer component(s) (see for example FIG. 10A, FIG. 10B). The received requests may be accepted by the data consumer associated with the local data consumer component(s), for example as described in the context of FIG. 4A. Accepting may include triggering access of the digital asset(s) associated with the received request as described in the context of FIG. 4A.

[0191] By orchestrating communications between provider and consumer tenants via the central orchestration component, provider tenants can be reliably and efficiently notified with respect to digital asset(s) required by the data consumer(s). This way, consumer tenants may efficiently trigger generation and provision of digital asset(s) required for generation of digital product passports, allowing to ensure a higher quality of the data included in the generated digital product passports and hence allowing a more efficient processing of the products and / or production of further products using the product as production input based on the data included in the digital product passport.

[0192] FIG. 5A and FIG. 5B illustrate examples of user interfaces generated by local data provider component(s) of a provider tenant associated with a data provider for creating a data pipeline to offer digital asset(s) to data consumer(s). The digital assets(s) may be associated with supply chain product(s). The supply chain product(s) may include supply chain product(s) described in the context of FIG. 2. The supply chain product(s) may be producible or produced by a production associated with the provider tenant component (see FIG. 11). The local data provider component(s) may be communicatively coupled to an orchestration component as described in the context of FIG. 3.

[0193] The user interface may be displayed in response to selecting generation of a data pipeline on an entry screen. The data pipeline may allow generation of digital assets associated with supply chain products used to produce a product, such as a chemical product, and provision of such digital assets for access by decentral consumer network nodes connected to local data consumer component(s) of a consumer tenant via the decentral network based on the decentral network protocol. The user interface may allow to configure the data pipeline by defining the source data storage storing the data, such as supply chain product data, used to generate the digital assets, a data model for generating the digital assets, a data model for mapping the data structure of the source data base to the data model for generating the digital assets and policy data. With reference to FIG. 5B, policy data may include decentral participant identifier(s) of decentral consumer network node(s) allowed to access the generated digital asset(s). The policy data may further include permission(s), obligation(s) and / or prohibition(s) of data consumer(s) with respect to the processing of the digital asset(s). Processing of the digital asset(s) by local data consumer component(s) of a consumer tenant may be monitored and / or controlled based on such policy data. The data pipeline may relate to a data storage storing the generated assets to be provided via a decentral network 134. The data pipeline may further relate to the data model, the supply chain product data and properties of the digital asset to be provided and / or consumed via the decentral network based on the data pipeline.

[0194] Upon activating, e.g. after finishing configuration of, the data pipeline, digital asset(s) may be generated according to the configuration of the data pipeline. In addition, a request for consuming the digital asset(s) generated based on the data pipeline may be generated and provided to the orchestration component as described in the context of FIG. 3 and FIG. 4A. The request may include the tenant identifier of the provider tenant component, the decentral participant identifier(s) defined in the context of the policy data and the decentral asset identifier(s) of the generated digital asset(s). The orchestration 241372

[0195] 40 component may identify tenant identifier(s) of data consumer(s) associated with the decentral participant identifier(s) and may provide the request as data offer to local data consumer component(s) associated with the identified tenant identifiers, for example as described in the context of FIG. 3 and FIG. 4A.

[0196] FIG. 6A and FIG. 6B illustrate examples of user interfaces generated by local data consumer component(s) of a consumer tenant associated with a data consumer for creating a data pipeline to request digital asset(s) from data provider(s). The digital asset(s) may be associated with supply chain product(s). The supply chain product(s) may be producible or produced by a production associated with the data provider. The local data consumer component(s) may be communicatively coupled to an orchestration component as described in the context of FIG. 3.

[0197] The user interface may be displayed in response to selecting generation of a data pipeline on an entry screen. The data pipeline may allow processing of the digital assets associated with supply chain products used to produce a product, such as a chemical product, gathered by decentral consumer network node(s) connected to the local data consumer component(s) via the decentral network. Processing may include validating the gathered digital asset(s) and optionally using the validated digital asset(s) for generating digital product passports associated with the product. The user interface may allow to configure the data pipeline by defining the target data storage storing the processed, e.g. validated, data, such as validated digital assets, a data model to be used by the data provider for generating the digital assets, a data model for mapping the validated digital asset to the data structure of the target data storage, validation rule(s) for validating the gathered digital assets and decentral participant identifier(s) associated with decentral provider network node(s) the digital assets are to be accessed at. The data pipeline may relate to a target storage storing the validated digital assets.

[0198] Upon activating, e.g. after finishing configuration of, the data pipeline, a trigger may be generated based on configuration of the data pipeline, for example as described in the context of FIG. 3 and FIG. 4B. The trigger may be provided to the orchestration component as described in the context of FIG. 3 and FIG. 4B. The trigger may include the tenant identifier of the local data provider component(s), the decentral participant identifier(s) associated with the decentral provider network node(s) and the data model used to generate the digital assets or a representation for accessing the data model. The orchestration component may identify tenant identifier(s) of local data provider component(s) associated with the decentral participant identifier(s) and may provide the request to the local data provider component(s) associated with the identified tenant identifiers, for example as described in the context of FIG. 3 and FIG. 4B.

[0199] FIG. 7 illustrates an example of data structures stored in a configuration storage associated with the orchestration component illustrated in FIG. 3. The configuration storage may be included in the local computing and / or storage environment of the orchestration component. The configuration storage may be communicatively coupled to the orchestration component (see FIG. 3). The configuration storage may be accessible for the orchestration component. The configuration storage may not be accessible for one or more tenants connected via the local communication protocol to the orchestration component, and / or the decentral network environment connected via decentral network node(s) with the tenants (see FIG. 3). 41

[0200] The configuration storage may include one or more databases. The one or more databases may be relational databases and / or non-relational databases. The example illustrated in FIG. 7 shows data structures stored in a non-relational database, such as a Mongo DB.

[0201] One database, e.g. template storage 712, may store data models received via triggers from local data consumer components, for example as described in the context of FIG. 3, FIG. 4B, FIG. 6A and FIG. 6B. A further database may store tenant data. The tenant data may include mappings between tenant identifiers and respective decentral participant identifiers. The tenant data may further include names, such as company names, associated with the decentral participant identifiers and / or endpoints of decentral network nodes associated with such decentral participant identifiers. In the example illustrated in FIG. 7, the tenant data is stored as JSON documents within non-relational database 714.

[0202] Based on the tenant data, the orchestration component may be able to identify tenant identifiers based on decentral participant identifier(s) included in requests or triggers received from the tenant component(s) and to provide triggers or request for consumption of generated digital assets to tenant components associated with the identified tenant identifiers, for example as described in the context of FIG. 3 to FIG. 4B. Based on the template storage, the data model defined by the local data consumer component(s) may be provided by the orchestration component to the local data provider component(s), avoiding access of the local data provider component(s) of the provider tenants to local storages included in the consumer tenant and hence improving data security.

[0203] FIG. 8A illustrates a flow chart of an example method for requesting or offering consumption of digital asset(s) associated with supply chain product(s) via a decentral network protocol by one or more decentral consumer network node(s) connected to one or more local data consumer component(s) of one or more local data consumer compute and storage environment(s) (e.g. consumer tenant(s)) associated with one or more data consumer(s). The method may be implemented by one or more local data provider component(s) of a local data provider compute and storage environment (e.g. provider tenant) associated with a data provider, for example as described in the context of FIG. 3. The provider tenant may be associated with a unique tenant identifier (see also FIG. 3). The provider tenant may be communicatively coupled to an orchestration component and may communicate with the orchestration component via a local communication protocol. The local data provider component(s) may be connected to a decentral provider network node configured to provide access to digital asset(s) via peer-to-peer communications according to a decentral network protocol with decentral consumer network node(s) connected to the local data consumer component(s).

[0204] The supply chain product(s) may be used to produce a product. The product may be a product as described in the context of FIG. 2. The product may be a chemical product. The chemical product may be a chemical product described in the context of FIG. 2. The supply chain product(s) may be produced by upstream production stage(s) with respect to the product production stage (see FIG. 2). The supply chain product(s) may include supply chain product(s) described in the context of FIG. 2.

[0205] The provider tenant may be associated with a supply chain product producer producing the supply chain product(s). The data consumer may be the product producer. The data consumer may be an entity generating digital product passport(s) associated with the product. The data consumer may be a supply chain product producer of a downstream production stage with respect to the data provider. 42

[0206] Configuration data for requesting consumption of the digital asset via the decentral network protocol by the decentral consumer network node(s) may be provided. The configuration data may include a representation for accessing supply chain product data stored in a local source data storage of the local data provider compute and storage environment and being associated with the supply chain product, a data model associated with the supply chain product or a product produced using the supply chain product and one or more decentral participant identifier(s) associated with at least one of the local data consumer compute and storage environments. The configuration data may further include a configuration data identifier uniquely identifying the configuration data within the provider tenant, a mapping for mapping the data points included in the local source data storage to the data points included in the data model and / or permission(s), prohibition(s) and / or obligation(s) of data consumer(s) with respect to the processing of the digital asset(s). The configuration data may be associated with a configuration of a data pipeline configured to generate digital asset(s) to be consumed via the decentral network protocol. The configuration data may be generated by generating a data pipeline for generating digital asset(s) and providing the generated digital asset(s) for access by decentral consumer network node(s), for example as described in the context of FIG. 3 to FIG. 5B. The data pipeline may relate to a local data source associated with the provider tenant. The local data source may store supply chain product data used to generate the digital asset(s) exchanged via the decentral network protocol.

[0207] The representation for accessing the supply chain product data may include a locator to a source data storage storing the supply chain product data. The source data storage may be a local data storage included in the provider tenant. The source data storage may be a local data storage associated with the provider tenant (e.g. coupled via a communication interface with the provider tenant). The local data storage may store supply chain product data associated with supply chain products produced or producible by a production. Produced supply chain product(s) may be physical entity / ies of supply chain product(s) having been produced by the production. Producible supply chain product(s) may not yet have been produced by the production but may be producible by one or more production process(es) performed within the production. Producible supply chain product(s) may include supply chain product(s) planned to be produced, for example based on demand data received from downstream production stages (see FIG. 2).

[0208] The production may be operated by a supply chain product producer. The supply chain product producer may be associated with the provider tenant. The production may be a chemical production. The production may be a chemical production network. The chemical production network may include multiple interlinked processing steps. The chemical production network may be an integrated chemical production network with connected or interconnected production chains. The chemical production network may include multiple different production chains that have at least one intermediate product in common. The chemical production network may include multiple stages of the chemical value chain. The chemical production network may include the producing, refining, processing and / or purification of chemical products. The chemical production network may include multiple production chains that produce from one or more material(s) chemical products that exit the chemical production network. The chemical production network may include multiple tiers of a chemical value chain. The chemical production network may include physically connected or interconnected supply chains and / or production sites. The production sites may be at the same location or at different locations. In the latter case, the production sites may be connected or interconnected by means of dedicated transportation systems such as pipelines, supply chain vehicles, like trucks, ships or other cargo transportation means. The chemical production or production network may include one or more 241372

[0209] 43 process step(s) involving chemical reaction(s). The chemical production or production network may further include one or more process step(s) involving physical processes described in the context of FIG. 2.

[0210] The supply chain product data stored in the source data base may be linked to a digital supply chain product identifier associated with the supply chain products. The supply chain product data may include measured data and / or data generated from measured data. The supply chain product data may include at least one chemical and / or physical property of the supply chain products. The supply chain product data may further include supply chain product name(s), production data, emission data, safety data, certificates, processing data, handling data, life cycle data, storage instruction(s), processing instructions or any combination thereof. Examples of chemical properties include heat of combustion, enthalpy of formation, toxicity, chemical stability in a given environment, flammability, oxidation state(s), ability to corrode, combustibility, acidity and basicity, chemical composition, recyclate content used for producing or manufacturing the supply chain product, bio-based content used for producing or manufacturing the supply chain product, renewable content used for producing or manufacturing the supply chain product, biodegradability, and / or pH value. Examples of physical properties include absorption, brittleness, boiling point, capacitance, color, concentration, density, ductility, distribution, efficacy, elasticity, electric charge, electrical conductivity, electrical impedance, electric potential, flow rate, fluidity, hardness, heat capacity, inductance, intrinsic impedance, luminance, luminescence, luster, mass, melting point, opacity, permeability, permittivity, plasticity, pressure, radiance, resistivity, reflectivity, refractive index, solubility, specific heat, strength, stiffness, temperature, tension, thermal conductivity, thermal resistance, viscosity, volume and / or wave impedance.

[0211] The data model may include a semantic description of the digital asset associated with the supply chain product or a digital product passport associated with the product. The semantic description may include a semantic description of supply chain product data or passport data. The semantic description may include the structure of at least a portion of the digital asset or the digital product passport, and / or properties of the digital asset or the digital product passport. The properties may include data types. The properties may include possible or allowable values and / or value ranges. The properties may be a physical unit of parameter(s) described by values contained in the digital asset or the digital product passport.

[0212] The configuration data may be generated by providing the representation, the data model and the decentral participant identifier(s). The configuration data may be generated in response to receiving the representation, the data model and decentral participant identifier(s). The representation, data model and decentral participant identifier(s) may be received via a user interface, for example as described in the context of FIG. 5A and FIG. 5B.

[0213] Digital asset(s) associated with the supply chain product(s) may be generated based on the provided configuration data. The digital asset(s) may be generated by transforming the supply chain product data accessed according to the representation based on the data model and the mapping. The digital asset(s) may be generated using a rule-based engine including one or more rule(s) associated with the data model and the mapping, for example as described in the context of FIG. 12. The rule(s) may be executable instruction(s) configured to transform the supply chain product data. The rule(s) may be generated based on the data model and the mapping. The generated digital asset set may include a decentral asset identifier and transformed supply chain product data. The decentral asset identifier may not be provided to the decentral network to be discoverable and / or accessible by decentral network nodes of the decentral network. 241372

[0214] 44

[0215] The generated digital asset(s) may be associated with policy data generated based on the decentral participant identifier(s) and the permission(s), obligation(s) and / or prohibition(s). The policy data may be linked via the decentral asset identifier(s) to the digital asset(s). This way, access to the digital asset(s) may be controlled via the decentral asset identifier(s) based on the policy data.

[0216] The generated digital asset(s) may be provided for access by the decentral consumer network node(s) via the decentral network protocol under control of the data provider, such as the producer of the supply chain product(s). Providing the generated digital asset(s) for access may include storing the digital asset(s) in a local target data storage for access by the decentral consumer network node(s). Providing the generated digital asset(s) for access may further include providing the policy data and a representation for accessing the local target data storage to the decentral provider network node(s) connected to the local data provider component(s) of the provider tenant.

[0217] A request for consumption of the generated digital asset via the decentral network protocol by the decentral consumer network node(s) may be generated based on the provided configuration data. The request may include the tenant identifier associated with the local data provider component(s) generating the request, the decentral asset identifier(s) associated with the generated digital asset(s) requested to be consumed by or offered to the data consumer(s) and the decentral participant identifier(s) associated with the decentral consumer network node(s). The request may further include the configuration data identifier.

[0218] The generated request may be provided via the local communication protocol to the orchestration component configured to determine local identifier(s) associated with consumer tenant(s) based on the received request and to provide a request for consumption of the digital asset(s) via the local communication protocol to the consumer tenant(s) associated with the determined local identifier(s). The local identifier(s) may include tenant identifier(s) associated with the consumer tenant(s). The orchestration component may be configured to determine the local identifier(s) associated with the consumer tenant(s) based on the decentral participant identifier(s) using mappings between decentral participant identifiers and respective tenant identifiers. The orchestration component may be configured to provide the request to the consumer(s) tenants based on the determined local identifier(s) via the local communication protocol, for example as described in the context of FIG. 4A. The request provided by the orchestration component to the consumer tenant(s) may include the decentral asset identifier(s), the decentral participant identifier associated with the provider tenant and the endpoint of the decentral provider network node associated with the provider tenant. The request may further include the name of the supply chain product producer associated with the provider tenant.

[0219] The consumer tenant(s) receiving the request may request access to the digital asset(s) by the decentral consumer network node(s) via the decentral network protocol based on the decentral asset identifier(s) and the endpoint included in the received request. The decentral provider network node(s) may provide the requested digital asset(s) upon successful authentication and / or authorization. Authentication may be based on a certificate or verifiable credential associated with the requesting decentral consumer network node(s). Authorization may be based on the decentral asset identifier and decentral participant identifiers associated with the consumer tenants, for example as described in the context of FIG. 3. 241372

[0220] 45

[0221] The provider tenant(s) may further receive a request for generating and providing digital assets(s) associated with the supply chain product(s) for access via the decentral network protocol by the one or more decentral consumer network node(s) based on a trigger by one or more consumer tenant(s), for example as described in the context of FIG. 4A and FIG. 13. The request may be received from the orchestration component in response to a trigger received by the orchestration component from the consumer tenant(s) (see FIG. 4A). In response to the request, local data provider component(s) of the provider tenant(s) may generate or select configuration data and may generate the requested digital asset(s) based on the generated or selected configuration data, for example as described in the context of FIG. 4A and FIG. 13. The generated digital asset(s) may be provided for access via the decentral network protocol by the decentral consuming network node(s) connected to local data consumer component(s) having provided the trigger to the orchestration component. Providing the digital asset(s) for access may include generating a request for consumption of the generated assets and providing the request to the orchestration component as previously described.

[0222] By orchestrating communication between the provider tenant and the consumer tenant(s) according to a local communication protocol, the data provider associated with the provider tenant may notify the data consumer(s) associated with the consumer tenant(s) on digital asset(s) available for consumption in an efficient and reliable manner without sharing any sensitive data, such as tenant identifier and generated digital asset(s) via the local communication protocol with the orchestration component and the data consumer(s). By using a decentral network protocol to share the digital asset(s) with the data consumer(s), access to the digital asset(s) may be controlled by the data owner of the digital asset(s), such as the supply chain product producer.

[0223] By orchestrating communication between the provider tenant and the consumer tenant(s) according to a local communication protocol and by sharing the digital asset(s) generated by the provider tenant via the decentral network protocol with the consumer tenant(s), more efficient sharing of digital asset(s) under full data sovereignty of the data owner of the digital asset(s), such as the supply chain product producer, is enabled. Since the data consumer(s) can be notified in an efficient yet secure way via the local communication protocol using the orchestration component, inefficient discovery of digital asset(s) accessible within the decentral network may be avoided, reducing the energy consumption associated with the discovery of accessible digital asset (s) and hence also the environmental impact associated with the exchange of digital asset(s) based on the decentral network protocol.

[0224] FIG. 8B illustrates a flow chart of an example method for requesting generation and provisioning of digital asset(s) associated with supply chain product(s) by a local data provider compute and storage environment (e.g. provider tenant) associated with a data provider. The method may be implemented by a local data consumer compute and storage environment (e.g. consumer tenant). The consumer tenant and the provider tenant may be associated with a unique tenant identifier (see also FIG. 3). The consumer tenant may include one or more local data consumer component(s) communicatively coupled to an orchestration component (see FIG. 3). The local data consumer component(s) may communicate with the orchestration component via a local communication protocol. The local data consumer component(s) may be connected to a decentral consumer network node configured to request access to digital asset(s) via peer-to-peer communications according to a decentral network protocol at decentral provider network node(s) connected to local data provider component(s) of the provider tenant. 241372

[0225] 46

[0226] The supply chain product(s) may be used to produce a product as described in the context of FIG. 8A. The supply chain product(s) may be produced by upstream production stage(s) with respect to the product production stage (see FIG. 2). The supply chain product(s) may include supply chain product(s) described in the context of FIG. 2.

[0227] The consumer tenant may be associated with a data consumer. The data consumer may be the product producer. The data consumer may be an entity generating digital product passport(s) associated with the product. The data consumer may be a supply chain product producer of a downstream production stage with respect to the data provider.

[0228] Configuration data for requesting generation of digital asset(s) associated with supply chain product(s) by local data provider component(s) and for provision of generated digital asset(s) for access by the decentral consumer network node(s) via the decentral network protocol may be provided. The configuration data may include a configuration data identifier uniquely identifying the configuration data within the consumer tenant, data pipeline configuration data associated with a configuration of the data pipeline for processing digital asset(s) associated with supply chain product(s) consumed via a decentral network protocol by the decentral consumer network node(s) and decentral participant identifier(s) associated with the decentral provider network node(s). The data pipeline may be configured for processing digital asset(s) consumed via the decentral network protocol. The data pipeline may relate to a local data source associated with the consumer tenant. The local data source may store processed digital asset.

[0229] The data pipeline configuration data may include a representation for accessing a target data storage configured to store processed digital assets, a data structure or data model for collecting properties associated with the supply chain product(s), a mapping for mapping the data points included in the processed digital asset to the data structure of the target data storage and one or more validation rules for processing, e.g. validating, the digital asset(s) gathered via the decentral network protocol from decentral provider network node(s) associated with provider tenant(s). The configuration data may be generated by generating a data consuming pipeline for processing digital asset(s) gathered via the decentral network protocol, for example as described in the context of FIG. 3, FIG. 4B, FIG. 6A and FIG. 6B.

[0230] The representation for accessing the target data storage may include a locator to the target data storage. The target data storage may be a local data storage included in the consumer tenant. The target data storage may be a local data storage associated with the consumer tenant (e.g. coupled via a communication interface with the consumer tenant). The local target storage may store processed, e.g. validated, digital asset. The processed digital asset may be generated by processing digital asset(s) consumed via the decentral network protocol from decentral provider network node(s) associated with provider tenant(s) using the one or more validation rule(s). The processed digital asset may be persisted in the local target data storage based on the data model for mapping the data points included in the processed digital assets to the data structure of the target data storage.

[0231] The data model may include a semantic description of the digital asset(s) to be generated by the data provider. The semantic description may include the structure of at least a portion of the digital asset(s) to be generated by the data provider and / or properties of the digital asset to be collected. The properties may include data types. The properties may include possible or allowable values and / or value ranges. The properties may be a physical unit of parameter(s) described by values contained in the digital asset(s) to be generated. The configuration data may be generated by providing the data pipeline configuration data and the decentral participant identifier(s) associated with the decentral provider network node(s). The configuration data may be generated in response to receiving the data pipeline configuration data and the decentral participant identifier(s). The data pipeline configuration data and the decentral participant identifier(s) may be provided via a user interface, for example as described in the context of FIG. 6A and FIG. 6B.

[0232] A trigger for generating and providing the digital asset(s) may be generated. The trigger may include the tenant identifier associated with local data consumer component(s) generating the trigger, the data structure or data model for collecting properties associated with the supply chain product(s) and the decentral participant identifier(s) associated with the decentral provider network node(s). The trigger may further include the configuration data identifier.

[0233] The generated trigger may be provided via a local communication protocol to the orchestration component configured to determine local identifier(s) associated with the provider tenant(s) based on the received trigger and to provide a request for generating and providing the digital asset(s) via the local communication protocol to the provider tenant(s) associated with the determined local identifier(s). The local identifier(s) may include tenant identifier(s) associated with the provider tenant(s). The orchestration component may be configured to determine the local identifier(s) associated with the provider tenant(s) based on the decentral participant identifier(s) using mappings between decentral participant identifiers and respective tenant identifiers. The orchestration component may be configured to provide the request to the provider tenant(s) based on the determined local identifier(s) via the local communication protocol, for example as described in the context of FIG. 4B. The request provided by the orchestration component to the provider tenant(s) may include the data structure or data model for collecting properties associated with the supply chain product(s) or a representation for accessing the data structure or data model and the decentral participant identifier associated with the local data consumer component(s) having provided the trigger. The request may further include the name of the data consumer.

[0234] The provider tenant(s) receiving the request may generate a data pipeline for generating digital asset(s) according to the data structure or data model included in the received request or being accessible via the representation included in the received request. The provider tenant(s) receiving the request may select an existing data pipeline associated with the data structure. The provider tenant(s) may generate the digital asset(s) based on the generated or selected data pipeline. The generated digital asset(s) may be provided for access via the decentral network protocol, for example as described in the context of FIG. 3.

[0235] A request for consumption of digital asset(s) generated by provider tenant(s) may be received, for example as described in the context of FIG. 4B. The request may be received in response to a trigger generated and provided to the orchestration component as previously described. The request may be received via the local communication protocol from the orchestration component. The request may include the decentral asset identifier(s) associated with the generated digital asset(s), the decentral participant identifier(s) associated with the decentral provider network node(s) associated with the provider tenant(s) and endpoint(s) of such decentral provider network node(s).

[0236] The generated digital asset(s) may be accessed by decentral consumer network node(s) associated with the consumer tenant(s) receiving the request according to the decentral network protocol from the decentral provider network node(s) 241372

[0237] 48 associated with the provider tenant(s). The digital asset(s) may be accessed based on the decentral asset identifier(s) and endpoint(s) included in the received request, for example as described in the context of FIG. 4B.

[0238] By orchestrating communication between the consumer tenant and the provider tenant(s) according to a local communication protocol, the data consumer associated with the consumer tenant may request the data provider(s) associated with the provider tenant(s) to generate and provide digital asset(s) in an efficient and reliable manner while ensuring that the generated digital asset(s) transferred via the decentral network protocol adhere(s) to the formats and content the data consumer associated with the consumer tenant expects. By using a decentral network protocol to share the digital asset(s) generated in response to such request by the data provider(s), access to the generated digital asset(s) may be controlled by the data owner of the digital asset(s), such as the supply chain product producer.

[0239] By orchestrating communication between the provider tenant and the consumer tenant(s) according to a local communication protocol and by sharing the digital asset(s) generated by the provider tenant via the decentral network protocol with the consumer tenant(s), more efficient sharing of digital asset(s) under full data sovereignty of the data owner of the digital asset(s), such as the supply chain product producer, is enabled. Since data generation according to predefined data structures or data models can be requested from data provider(s) in an efficient yet way via the local communication protocol using the orchestration component, missing supply chain product data during generation of a digital product passport associated with a product produced from the supply chain product may be avoided. This way, a higher data quality of the passport data can be ensured, allowing to generate digital product passports having an improved reliability since the passport data is associated with a higher degree of completeness. The higher data quality of the digital product passports may allow more efficient processing of the product(s) based on the passport data, such as more efficient production, more efficient re-use, more efficient sorting and / or recycling of the product.

[0240] FIG. 80 illustrates a flow chart of an example method for monitoring and / or controlling data exchange between decentral provider network node(s) connected to one or more local data provider component(s) of one or local data provider compute and storage environment(s) and decentral consumer network node(s) connected to one or more local data consumer component(s) of one or more local data consumer compute and storage environment(s). The method may be implemented by an orchestration component communicatively coupled to local data provider compute and storage environment(s) (e.g. provider tenants) and / or the local data consumer compute and storage environment(s) (e.g. consumer tenants), for example as described in the context of FIG. 3. The tenants may each be associated with a unique tenant identifier (see also FIG. 3). The tenants may be associated with decentral network nodes configured to transfer data, such as digital asset(s), via peer- to-peer communications according to a decentral network protocol.

[0241] The digital asset(s) may be associated with supply chain product(s). The supply chain product(s) may be used to produce a product as described in the context of FIG. 8A. The supply chain product(s) may be produced by upstream production stage(s) with respect to the product production stage (see FIG. 2). The supply chain product(s) may include supply chain product(s) described in the context of FIG. 2.

[0242] The provider tenant may be associated with a supply chain product producer producing the supply chain product(s). The consumer tenant may be associated with the product producer. The consumer tenant may be associated with an entity 241372

[0243] 49 generating digital product passport(s) associated with the product. The consumer tenant may be associated with a supply chain product producer of a downstream production stage with respect to the data provider.

[0244] Mapping data may be provided. The mapping data may include mappings between local identifiers associated with the local compute and storage environments and decentral participant identifier(s) associated with decentral network node(s) connected to such local compute and storage environments. The mapping may be related to the unique identifiers associated with provider tenants and consumer tenants within the local computing environment and unique identifiers associated with decentral network nodes connected to such tenants. The local computing and storage environments may include distributed compute and storage environments controlled by the tenants. The tenants may communicate with the orchestration component via the local communication protocol. Likewise, the orchestration component may communicate with the tenants via the local communication protocol. The tenants may communicate with each other solely via the orchestration component. The local identifier(s) may include tenant identifiers associated with the tenants.

[0245] Requests for consumption of digital asset(s) via a decentral network protocol and / or triggers for generation of digital asset(s) and provision of such of digital asset (s) via the decentral network protocol may be received by the orchestration component via the local communication protocol. The requests for consumption of digital asset (s) may be received via the local communication protocol from provider tenants. The requests may include the tenant identifier associated with the provider tenants, the decentral asset identifier(s) of the generated digital asset(s) requested to be consumed by decentral consumer network node(s) of consumer tenant(s) and the decentral participant identifier(s) associated with the decentral consumer network node(s). The triggers for generation of digital asset(s) and provision of such digital asset(s) may be received via the local communication protocol from consumer tenants. The triggers may include the tenant identifier associated with the consumer tenants, a data structure or data model for collecting properties associated with the supply chain product(s) and the decentral participant identifier(s) associated with the decentral provider network node(s). The requests may be generated as described in the context of FIG. 3 to FIG. 8B

[0246] The local identifier(s) associated with the decentral participant identifier(s) included in the received requests / triggers may be determined based on the mapping data. The local identifier(s) may be determined as described in the context of FIG. 3, FIG. 8A and FIG. 8B.

[0247] The request for generating and providing the digital asset(s) may be provided via the local communication protocol to provider tenant(s) associated with the determined local identifier(s). Providing the request may include adding further configuration data, for example as described in the context of FIG. 8A. The provided request may include the decentral asset identifier(s) of the generated digital asset(s), the decentral participant identifier associated with the decentral provider network node(s) providing the digital asset(s) and the endpoint of the decentral provider network node(s). The request may further include the name of the data provider.

[0248] The request for consumption of the digital asset(s) may be provided via a local communication protocol to the consumer tenant(s) associated with the determined local identifier(s). Providing the request may include adding further configuration data, for example as described in the context of FIG. 8B. The provided request may include the data structure or data model for collecting properties associated with the supply chain product(s) or a representation for accessing the data structure or 241372

[0249] 50 data model and the decentral participant identifier associated with the decentral consumer network node(s) requesting consumption.

[0250] The tenant(s) receiving the request may accept the request as described in the context of FIG. 3 to FIG. 4B.

[0251] By orchestrating communication between the provider tenant and the consumer tenant(s) by the orchestration component based on a mapping of local identifiers and respective decentral identifiers, received requests may be reliably and efficiently provided to the correct recipient without the requesting tenant being required to know the local identifier of the recipient tenant(s). This prevents direct access of a requesting tenant to the local compute and / or storage environment of the recipient tenant, reducing the risk of unauthorized data access by the requesting tenant and improving data security and data sovereignty. In addition, orchestration of the communication based on the mapping data stored in a central data storage of the orchestration component improves the reliability of the communication between tenants by avoiding incorrect mapping data in local databases of each tenant due to missing or delayed update(s) and / or maintenance. The improved reliability of the communication between tenants allows to consumer tenant(s) to consume a higher amount of digital asset(s), resulting in a lower amount of supply chain product data missing during generation of a digital product passport associated with the product. This way, a higher data quality of the passport data can be ensured, allowing to generate digital product passports having an improved reliability since the passport data is associated with a higher degree of completeness. The higher data quality of the digital product passports may allow more efficient processing of the product(s) based on the passport data, such as more efficient production, more efficient re-use, more efficient sorting and / or recycling of the product.

[0252] FIG. 9A illustrates an example of a user interface displayed by a data providing component acting as a tenant of an orchestration component displaying requests for generating and providing digital asset(s) received from data consumer(s) and / or requests for consumption of digital asset(s) provided to data consumer(s). The provider tenant and consumer tenant(s) may be part of a local computing and / or storage environment 314 as described in the context of FIG. 3. The provider tenant and the consumer tenant(s) may be communicatively coupled to the orchestration component as described in the context of FIG. 3.

[0253] The user interface may be displayed after having received requests from consumer tenants via the orchestration component and / or having generated digital asset(s) based on a data pipeline for generating and providing digital asset(s).

[0254] The user interface may display the requests received from the consumers tenants and / or data pipelines used to generate digital asset(s) offered for consumption to the data consumer(s). The user interface may display a status for each received request and / or data pipeline. The user interface may display the name of the data consumer requesting data or the name of the data consumer requested to consume data along with the decentral participant identifier associated with the data consumer.

[0255] Newly received requests from consumer tenant(s) to generate and provide digital asset(s) may allow the data provider to accept the request, for example as described in the context of FIG. 3, FIG. 4B and FIG. 8A. Requests to consumer tenant(s) to consume digital asset may be displayed as pending until the data consumer initiates accessing of the offered digital assets, for example as described in the context of FIG. 3 and FIG. 4A. 241372

[0256] 51

[0257] The user interface may include buttons for displaying details for received requests and data pipelines. A user interface generated in response to selecting the button for displaying details of a received request is illustrated in FIG. 9B.

[0258] FIG. 9B illustrates details of a request for generating and providing digital asset(s) received from a data consumer shown in FIG. 9A.

[0259] The displayed details may include the name and a digital representation for accessing the data structure or data model provide by the consumer tenant for collection property / ies of the supply chain product(s) the digital asset(s) to be generated are associated with. The details may further include data associated with the requesting consumer tenant, such as the name and the email of the data consumer the consumer tenant is associated with. The details may further include the decentral participant identifier(s) of decentral consumer network node(s) and a name of the data consumer requesting the digital asset. The displayed detail page may indicate whether the request is still active, e.g. has not yet been declined by the provider tenant.

[0260] FIG. 10A illustrates an example of a user interface generated by local data consumer component(s) of a consumer tenant for displaying requests for generating and providing digital asset(s) provided to provider tenant(s) and / or requests for consumption of digital asset(s) received from provider tenant(s). The consumer tenant and the provider tenant(s) may be part of a local computing and / or storage environment 314 as described in the context of FIG. 3. The consumer tenant and the provider tenant(s) may be communicatively coupled to an orchestration component as described in the context of FIG. 3.

[0261] The user interface may be displayed after having received requests from provider tenants via the orchestration component and / or having generated a data pipeline for processing digital asset(s) to be accessed by decentral consumer network node(s) associated with the consumer tenant.

[0262] The user interface may display the requests received from the provider tenants and / or generated data pipelines. The user interface may display a status for each received request or generated data pipeline. The user interface may display the name of the data provider associated with the provider tenant requesting consumption of the digital assets or the name of the data provider associated with the provider tenant requested to generate and provide digital assets along with the decentral participant identifier of such data provider.

[0263] Requests to provider tenant(s) to generate and provide digital assets may be displayed as pending until the provider tenant accepts the request, for example as described in the context of FIG. 3 and FIG. 4B. Newly received requests from provider tenant(s) to consume generated digital asset(s) may allow the data consumer to accept the request, for example as described in the context of FIG. 3, FIG. 4A and FIG. 8B.

[0264] The user interface may include buttons for displaying details for received requests and generated data pipelines. A user interface generated in response to selecting the button for displaying details of a received request is illustrated in FIG. 10B.

[0265] FIG. 10B illustrates an example of a user interface generated by local data consumer component(s) of a consumer tenant for displaying details of a request for consumption of digital asset(s) illustrated in the user interface of FIG. 10A. 241372

[0266] 52

[0267] The displayed details may include data associated with the requesting provider tenant, such as the name and the email of the data provider the provider tenant is associated with. The details may further include the decentral participant identifier associated with the provider tenant and the name of the data provider providing the digital assets. The displayed detail page may indicate whether the request is still active, e.g. has not yet been declined by the consumer tenant. The user interface may include buttons triggering actions. The data consumer may trigger gathering of policy data linked to the offered digital asset(s) by clicking on button 1010. Policy data may be gathered via the decentral network as described in the context of FIG. 4A. The data consumer may reject the request by clicking on button 1012. The data consumer may trigger accessing the offered digital asset(s) by accepting the permission(s), obligation(s) and / or prohibition(s) included in the policy data associated with the offered digital asset(s) (e.g. by clicking on “accept Contract” button).

[0268] FIG. 11 illustrates a decentral system for accessing digital asset(s) associated with supply chain product(s) produced or producible by a production by a data consumer via a decentral network. The supply chain product may be a supply chain product as described in the context of FIG. 2.

[0269] The supply chain product 1114 may be produced or producible using one or more production input(s) by the supply chain product production 1110. The supply chain product may be produced or producible via one or more process steps from the production input(s) within the supply chain product production 1110, for example as described in the context of FIG. 2. The process steps may involve chemical reactions and / or physical processes. The production input may be used in one or more of such production step(s). The production input may include starting material used in a production process performed within the supply chain product production to produce the supply chain product. Production input may include recycled material. The supply chain product production may be operated by a supply chain product producer. The supply chain product production may be a chemical production. The supply chain product production may be a chemical production network (see FIG. 8A).

[0270] The supply chain product production may be associated with a local data provider compute and storage environment 306 (e.g. provider tenant) 306. The provider tenant may communicate via a local communication protocol with an orchestration component as described in the context of FIG. 3. The provider tenant may communicate via the orchestration component with local data consumer compute and storage environment(s), such as consumer tenant 312, based on the local communication protocol. The provider tenant may include asset generation and transfer system 1104 configured to generate digital asset(s) based on supply chain product data stored in data layer 1108 and to provide the generated digital asset(s) for access by decentral consumer network node(s) connected to consumer tenants. Generation of the digital assets may be triggered by trigger event(s), such as request(s) for generating and providing digital assets(s) received via the orchestration component from the consumer tenant(s) (see FIG. 3, FIG. 8B and FIG. 8C) and / or generation of data pipelines for generating digital asset(s) to be offered for consumption to consumer tenant(s) (see FIG. 3 and FIG. 8A). The generated digital asset(s) may be stored in a local data storage of the provider tenant, such as assets DB 1106, for access by the decentral consumer network node(s) connected to the consumer tenants via the decentral network. The asset generation and transfer system may include the components described in the context of FIG. 12. In the example illustrated in FIG. 11 , the provider tenant may further include supply chain product data layer 1108 storing supply chain product data associated with the supply chain products produced or producible by the production. In another example (not shown in FIG. 11), the provider tenant may be 241372

[0271] 53 connected to an operating system associated with the supply chain production and including the supply chain product data layer.

[0272] The supply chain product data stored in the data layer may be generated before, during and / or after production of the supply chain product. The supply chain product data stored in the data layer may be linked to a digital supply chain product identifier associated with the supply chain product. The supply chain product data may include the data described in the context of FIG. 8A.

[0273] The provider tenant may include local data provider component(s), such as the asset generation and transfer system, connected to a decentral provider network node, such as node 118, of the decentral network. The decentral network may be a decentral peer-to-peer network as described in the context of FIG. 1 . Provider node 118 may be configured to gather digital asset(s) from the assets DB in response to request(s) received via the decentral network from decentral consumer network node(s), such as node 120, connected to local data consumer component(s) of the consumer tenant, such as the asset generation and transfer system 1118. Data exchange via peer-to-peer communication between the decentral provider network node and the decentral consumer network node(s) may be based on a decentral network protocol. The decentral network protocol may implement authentication and / or authorization mechanism. Such authentication may be based on data related to an authentication mechanism. The authentication mechanism may be based on certificate(s) and / or token(s), for example a device certificate (X.509v3), a TLS connection certificate (X.509v3) and a 'Dynamic Attribute Token’ (OAuth Access Token), associated with the respective decentral network nodes, e.g. consumer node 120 and provider node 118. If authentication fails, no data, such as digital asset(s), may be provided to the requesting decentral consumer network node(s). Such authorization may be based on or related to an authorization mechanism. The authorization mechanism may relate to or include decentral asset identifier(s) associated with the generated digital assets. The authorization mechanism may be based on policy data linked via the decentral asset identifier(s) to the respective digital assets. The policy data may include decentral participant identifier(s) associated with decentral consumer network node(s) allowed to access the digital asset. The policy data may further include data indicating permission(s), prohibition(s) and / or obligation(s) of consumer tenant(s) with respect to the processing of the digital assets. If authorization fails, no data, such as digital asset(s), may be provided to the requesting decentral consumer network node(s).

[0274] The supply chain product may be provided to a downstream production stage producing product(s) using the supply chain product as production input. The downstream production stage may include product production 1124. The product production may be operated by a product producer. The product production may be associated with the consumer tenant. The consumer tenant may communicate via the local communication protocol with the orchestration component, for example as described in the context of FIG. 3. The consumer tenant may communicate via the orchestration component with provider tenant(s), such as tenant 306, using the local communication protocol. The consumer tenant may include local data consumer component(s), such as asset generation and transfer system 1118 configured to process digital asset(s) gathered via the decentral network from decentral provider network node(s). The gathered digital asset(s) may be processed based on a data pipeline generated by local data consumer component(s) of the consumer tenant, for example as described in the context of FIG. 3 and FIG. 8B. Processing may include validation of gathered digital asset(s), for example as described in the context of FIG. 15 to FIG. 17. Processing may further include generation of digital product passports using validated digital assets and 241372

[0275] 54 product data associated with the produced product stored in product data layer 1122, for example as described in the context of FIG. 16 and FIG. 18. The generated passports may be stored in a local data storage of the consumer tenant, such as passport DB 1120, for access by decentral consumer network nodes via the decentral network. The asset generation and transfer system 1118 may include the components described in the context of FIG. 13. In the example illustrated in FIG. 11 , the consumer tenant may include the product data layer storing product data gathered before, during and / or after production of the product, as described previously. In another example (not shown in FIG. 11), the consumer tenant may be connected to an operating system associated with the product production and including the product data layer. The local data consumer component(s) may be associated with a decentral consumer network node of the decentral network. The decentral consumer network node may be configured to request access to digital asset(s) at decentral provider network nodes associated with such digital asset(s) based on requests received from the orchestration component and to provide the digital asset(s) received from the decentral provider network node(s) to the asset generation and transfer system for processing.

[0276] The digital asset(s) may be accessed based on data included in requests received from the orchestration component (see also FIG. 3 and FIG. 80). The requests may include the decentral asset identifiers, the decentral identifier(s) associated with the decentral provider network node and the endpoint of such node. The digital asset(s) may be accessed at the decentral provider network node based on the decentral asset identifier(s) associated with the digital asset(s). The decentral consumer network node and decentral provider network node may authenticate as previously described. The request to access the digital asset(s) may be authorized as previously described. Upon successful authentication and / or authorization of the request to access to the digital asset(s), the decentral provider network node may gather the digital assets from assets DB 1106 based on the decentral asset identifier(s) received from the decentral consumer network node. The decentral provider network node may provide the gathered digital asset to consumer node 120. The decentral provider network node may apply policy data associated with the digital asset(s) to the gathered digital asset(s) prior to providing such digital asset(s) to the decentral consumer network node. The decentral consumer network node may provide the received digital asset(s) to the asset generation and transfer system. The asset generation and transfer system may be configured to process the received digital assets as previously described.

[0277] FIG. 12 illustrates a block diagram of a system for generating digital asset(s) associated with supply chain product(s) and for providing the generated digital assets(s) for access via a decentral network by decentral consumer network node(s) connected to local data consumer component(s) of a local data consumer compute and storage environment(s) (e.g. consumer tenant(s)). The system, e.g. asset generation and transfer system 1104, may be part of a local data providing compute and storage environment (e.g. provider tenant). The provider tenant may be communicatively coupled to an orchestration component and may communicate with the orchestration component via a local communication protocol. Component(s) (e.g. local data provider component(s) of the system may be connected to a decentral provider network node, such as node 118, configured to provide access to digital asset(s) via peer-to-peer communications according to a decentral network protocol with decentral consumer network node(s) coupled to the local data consumer components of consumer tenants.

[0278] The supply chain product(s) may include supply chain product(s) described in the context of FIG. 2. The supply chain products may be produced or producible by a production (see FIG. 11). The supply chain product may be used by one or 241372

[0279] 55 more downstream participants of the product ecosystem as input material to produce one or more products. The system may be configured to perform the methods described in the context of FIG. 8A and FIG. 13.

[0280] The system may be configured to generate digital asset(s) in response to a trigger. The trigger may be generated in response to generating a data pipeline configured to generate and provide the digital asset(s) or in response to initiating an existing data pipeline configured to generate and provide the digital asset(s). The data pipeline may be generated as described in the context of FIG. 3, FIG. 4A and FIG. 8A. The data pipeline may be associated with configuration data (see FIG. 8A). The configuration data may be stored in a local pipeline data storage of the provider tenant, such as pipeline DB 1240. The configuration data may include a configuration data identifier uniquely identifying the configuration data within the provider tenant and data pipeline configuration data associated with a configuration of a data pipeline. The data pipeline configuration data may relate to the configuration data identifier and may include a representation for accessing a local source data storage storing supply chain product data used to generate the digital asset(s), e.g. data layer 1108, a data model defined by the data provider for generating the digital asset(s) or a data model for collection property / ies of supply chain products provided via the orchestration component by consumer tenants, a mapping for mapping the data points included in the data model or data structure to the data structure of the source data storage and policy data defining access to the generated digital asset(s). The policy data may include decentral participant identifier(s) associated with decentral consumer network node(s) allowed to access the digital asset(s) and permission(s), prohibition(s) and / or obligation(s) of consumer tenant(s) with respect to the processing of the digital asset(s). The trigger may include the configuration data identifier associated with the generated data pipeline or the initiated data pipeline.

[0281] The trigger or trigger data may be received by data gathering unit 1216 of the system. The data gathering unit may be connected to a local source data storage storing supply chain product data, such as data layer 1108. The local source data storage may be associated with the data provider. The local source data storage may be associated with the provider tenant including the system. The local source data storage may include one or more databases, such as DB 1 1210, DB 2 1212 and DB 3 1214. The local source data storage may be owned or controlled by the data owner of the supply chain product data. The local source data storage may be associated with the data owner of the supply chain product data.

[0282] In response to receiving the trigger, the data gathering unit may gather configuration data associated with data pipelines from the pipeline DB 1240 based on the configuration data identifier. The data gathering unit may be configured to gather the supply chain product data based on the configuration data from the local source data storage.

[0283] The supply chain product data gathered by the data gathering unit may be provided to data transforming unit 1218. The gathered supply chain product data may be provided in combination with the configuration data identifier. The data transforming unit may be configured to generate digital asset(s) by transforming the received supply chain product data based on one or more rule(s) stored in a local data storage, such as rule DB 1208. The rule(s) may be gathered from the local data storage based on the configuration data identifier. The rule(s) may include executable instructions for transforming the supply chain product data. The rule(s) may be associated with a data model defined by the data provider (e.g. defined data model), such as a data model of a product or product type producible from the supply chain product(s). The rule(s) may be associated with a data structure or data model (e.g. provided data model) provided via the orchestration component by the consumer tenant for collecting property / ies of the supply chain product(s) (see for example FIG. 3, FIG. 4B and FIG. 8B). 241372

[0284] 56

[0285] The rule(s) may be derived or generated based on the data model of the product or product type and / or based on the data model provided by the consumer tenant.

[0286] The one or more rule(s) may define aggregation rule(s) for aggregating supply chain product data gathered from multiple data sources into a given data structure. The given data structure may be a tabular representation or a structured data structure, such as a JSON document. Aggregation may hence result in filling gathered supply chain product data into a tabular data structure or a structured data structure. The one or more rule(s) may define filters to filter gathered supply chain product data. The filters may be associated with or relate to the defined data model or the provided data model. The filters may define data point(s) to be included in the generated digital asset. A filter may define data point(s) per data category. A filter may define data point(s) for at least two different data categories. A data category may signify property data, declaration data, safety data, emission data, recyclate content data, biobased content data, biodegradability data, production data, certificate of analysis data, certificate data, storage instruction data, assembly instruction data or operating condition data. This may ensure that supply chain product data required by the data model used to generate the digital product passport is included in the generated digital asset. The one or more rule(s) may define attribute construction(s) to create or add new attributes to the gathered supply chain product data. The one or more rule(s) may define manipulation(s) to convert supply chain product data point(s). The one or more rule(s) may include a trigger condition and a corresponding group of one more actions. The trigger conditions may involve a set of variables, sometimes called “working memory”, which may contain data (sometimes called “facts” or “data tuples”) representing the states of pertinent real-world items. The one or more action(s) may include attribute construction, filters and / or manipulations. The rule(s) may be associated with a given order defining the order of execution of the rule(s).

[0287] The received supply chain product data may be transformed using a rule-based engine executing the one or more rule(s). The rule-based engine may generate rule data executable by the rule-based engine. The rule data may include or correspond to executable logic. This may allow to transform rule(s) into code that can be executed by the rule-based engine. Execution of the code may result in applying the executable rule data to the gathered supply chain product data to transform the supply chain product data according to the obtained rule(s). Execution of the logic may result in matching gathered supply chain product data to condition(s) included in the executable logic, evaluating the condition(s) with matched supply chain product data and triggering execution of rule actions based on condition evaluation results.

[0288] The generated digital assets may include at least a part of the received supply chain product data. Use of rule(s) associated with a provided data structure ensures that the content and structure of the generated digital asset adheres to the content and structure the consumer tenant expects. This way, more efficient processing of the consumed digital assets may be enabled, allowing more efficient generation of digital product passports and hence more efficient processing of the products and / or production of further products based on the data included in the digital product passports.

[0289] The generated digital asset(s) may include chemical and / or physical property data point(s), supply chain product identifier data point(s), supply chain product name data point(s), producer data point(s), declaration data point(s), safety data point(s), production data point(s), certificate of analysis data point(s), certificate data point(s), life cycle data point(s), storage instruction data point(s), assembly instruction data point(s) and / or processing condition data point(s). The digital asset(s) may include at least a part of the gathered supply chain product data in a tabular data structure. The tabular data structure 241372

[0290] 57 may be readily consumed via a decentral network by a decentral consume network node connected to local data consumer component(s) of a consumer tenant and may be processed by validating the consumed digital asset for generation of digital product passports (see for example FIG. 14 and FIG. 16).

[0291] The data transforming unit may further be configured to provide the generated digital assets to data provider unit 1238. The data provider unit may be configured to provide the received digital assets to a local target data storage, such as assets DB 1106. The digital asset(s) may include or be associated with decentral asset identifier(s) associated with the supply chain product(s) and the digital asset(s). The local target data storage may be configured to store digital asset(s) generated by the data transforming unit for access by the decentral consumer network node(s). The local target data storage may be configured to provide digital asset(s) to the decentral provider network node(s) connected to the local target data storage. The local target data storage may be a dedicated data storage associated with the data owner of the digital assets. The data owner may own such dedicated data storage. The data owner may have access to such dedicated data storage. The data owner may control access to the local target data storage based on the decentral asset identifiers included in the digital asset, for example as described in the context of FIG. 11.

[0292] The data provider unit may further be configured to provide asset metadata to asset publisher service 1206. Asset metadata may include the decentral asset identifiers. Asset metadata may further include the configuration data identifier associated with the data pipeline used to generate the digital assets. The asset publisher service may be configured to gather policy configuration data associated with the respective digital asset from the local data pipeline data storage, for example based on the configuration data identifier. The policy configuration data may define decentral participant identifier(s) associated with decentral consumer network node(s) permitted to access at the respective digital asset. This way, decentral consumer network node(s) requesting access to the digital asset may be filtered based on the decentral participant identifier associated with such decentral consumer network node(s). The policy configuration data may further define permission(s), prohibition(s) and / or obligation(s) of consumer tenant(s) with respect to processing of the digital asset. Processing may include storing the digital asset, validating the digital asset and / or generating digital product passports using the validated digital asset. The asset publisher service may be configured to generate policy data based on the gathered policy configuration data. The policy data may be generated according to the ODRL Information Model 2.2 from W3C ( https: / / www.w3.org / TR / odrl-model / ).

[0293] The asset publisher service may further be configured to generate metadata for registering the digital assets with the decentral provider network node connected to the system. The metadata may include the decentral asset identifier and a digital representation of the digital asset. The digital representation may include a representation for accessing the digital asset. The representation may include a locator or pointer to the local target data storage storing the digital asset. The policy data and metadata may be generated by the asset publisher service per digital asset. The generated policy data and metadata may be provided to the decentral provider network node.

[0294] The asset publisher service may further be configured to generate digital representations of the digital assets for discovery of the digital assets within the decentral network. The digital representations may include the decentral asset identifier associated with the digital assets and a representation for accessing the digital asset. The representation may include a locator or pointer to the decentral provider network node. The digital representations may be provided to the decentral network for the decentral asset identifier to be discoverable and / or accessible by the decentral network nodes of the 241372

[0295] 58 decentral network. The digital representations may be provided to the decentral network to provide access to the digital assts, e.g. via the locator. The digital representation(s) may be provided to a decentral data storage associated with the provider tenant, such as DT registry 1112. The decentral data storage may be accessible by the further decentral network nodes. Access to the decentral data storage may be controlled by the data owner of the digital assets. Access may be controlled based on policy data associated with the decentral data storage and including decentral participant identifier(s) associated with decentral consumer network node(s) allowed to access the decentral data storage. Access may be controlled via the decentral provider network node.

[0296] The decentral provider network node may be configured to control access to digital asset(s) based on associated policy data. The decentral provider network node may be configured to provide digital asset(s) in response to a request received from decentral consumer network node(s) associated with consumer tenant(s), for example as described in the context of FIG. 11. The digital assets may be gathered or fetched by data transfer service 1202 based on decentral asset identifiers received from the decentral provider network node from the local target data storage. The data transfer service and / or decentral provider network node may be configured to apply policy data associated with the digital asset to such digital asset prior to providing such digital asset to the decentral consuming network node(s).

[0297] FIG. 13 illustrates a flow chart of an example method for generating digital asset(s) associated with supply chain product(s) produced or producible by a production and for providing the generated digital asset(s) for access via a decentral network protocol by one or more decentral consumer network node(s) connected to one or more local data consumer component(s) of one or more local data consumer compute and storage environment(s) (e.g. consumer tenant(s)) associated with one or more data consumer(s). The method may be implemented by a local data provider compute and storage environment (e.g. provider tenant). The local data provider compute and storage environment may include local data provider component(s), such as described in the context of FIG. 12. The provider tenant may be communicatively coupled to an orchestration component and may communicate with the orchestration component via a local communication protocol. The provider tenant may be associated with a decentral provider network node connected to the local data provider component(s).

[0298] The supply chain product(s) may be used to produce a product. The product may be a chemical product. The chemical product may be a chemical product described in the context of FIG. 2. The product may be a product as described in the context of FIG. 2. The supply chain product(s) may be produced by upstream production stage(s) with respect to the product production stage (see FIG. 2). The supply chain product(s) may include supply chain product(s) described in the context of FIG. 2.

[0299] A request to generate and provide digital asset(s) for access via the decentral network protocol by the one or more decentral consumer network node(s) may be received based on a trigger by the one or more local data consumer component(s). The request may be received via the local communication protocol(s) from the orchestration component as described in the context of FIG. 4B. The request may be provided by the orchestration component in response to the trigger received from the local data consumer component(s) of the consumer tenant, for example as described in the context of FIG. 4B. The trigger may include a data structure or data model for collecting property / ies associated with the supply chain product(s) and the decentral participant identifier associated with the decentral provider network node(s) connected to the provider tenant(s), for example as described in the context of FIG. 4B. The orchestration layer may be configured to determine recipient provider 241372

[0300] 59 tenant(s) based on the decentral participant identifier(s) and to provide the request to determined provider tenant(s) via the local communication interface., for example as described in the context of FIG. 3 and FIG. 4B. The request received by the local data provider component(s) of the provider tenant(s) may include the data structure or data model for collecting property / ies associated with the supply chain product(s) defined by the consumer tenant or a representation for accessing the data structure or data model defined by the consumer tenant and the decentral participant identifier associated with the decentral consumer network node(s) connected to the local data consumer component(s). The request may further include the name of the data consumer the local data consumer component(s) are associated with.

[0301] Configuration data associated with the generation and provisioning of the digital asset(s) may be generated or selected based on the received request. The configuration data may be associated with a data pipeline configured for generating digital asset(s) and for providing the digital asset(s) for access via the decentral network protocol by decentral consumer network node(s) connected to consumer tenant(s). The configuration data may include a configuration data identifier uniquely identifying the configuration data within the provider tenant and data pipeline configuration data associated with a configuration of the data pipeline for generating and providing the digital asset(s). The data pipeline may relate to a local data source associated with the provider tenant. The local data source may store supply chain product data used to generate the digital asset(s) exchanged via the decentral network protocol. The data pipeline configuration data may relate to the configuration data identifier and may include a representation for accessing a local source data storage storing supply chain product data used to generate the digital asset(s), e.g. data layer 1108, a data model received via or defined by the trigger for collecting at least one property of the supply chain product(s) and one or more decentral participant identifier(s) associated with the decentral consumer network node(s) connected to the local data consumer component(s) providing the trigger. The data pipeline configuration data may further include a mapping for mapping data points included in the data structure for collecting properties to the data structure of the source data storage. The data pipeline configuration data may further include policy data defining access to and processing of the generated digital asset(s). The policy data may include decentral participant identifier(s) associated at least with the decentral consumer network node(s) connected to the consumer tenant(s) providing the trigger and permission(s), prohibition(s) and / or obligation(s) of data consumer(s) with respect to the processing of the digital asset(s) by local data consumer component(s) of such consumer tenant(s). Configuration data may be selected based on the data structure or data model included in the received request. Selecting configuration data may include selecting existing configuration data based on the data structure or data model included in the received request. The configuration data may be generated as described in the context of FIG. 8A.

[0302] The digital asset(s) may be generated based on the generated or selected configuration data. The s digital asset (s) may be generated as described in the context of FIG. 8A and FIG. 12. The generated digital asset may include a decentral asset identifier and transformed supply chain product data. The decentral asset identifier may not be discoverable and / or accessible for participant nodes of the decentral network. Generating the digital asset (s) may further include linking policy data included in the configuration data to the decentral asset identifier(s) of the generated digital asset(s), for example as described in the context of FIG. 4A.

[0303] The generated digital asset(s) may be provided for access via the decentral network protocol by the decentral consuming network node(s) connected to the local data consumer component(s). The generated digital asset(s) may be provided for 241372

[0304] 60 access under control of the data owner of the digital asset(s). The data owner may be the supply chain product producer. Providing the digital asset(s) for access may include storing the generated digital asset in a local target data storage of or associated with the provider tenant for access by the decentral consumer network node(s). Providing the digital asset(s) for access may include generating a request for consumption of the generated digital asset(s) and providing the request via the orchestration component to the local data consumer component(s) based on the local communication protocol, for example as described in the context of FIG. 4B and FIG. 8A.

[0305] FIG. 14 illustrates a block diagram of an example system for validating digital asset(s) associated with supply chain product(s) used to produce one or more product(s) and for generating digital production passport(s) at least in part based on the validated digital asset. The system, e.g. asset generation and transfer system 1118, may be part of or included in one or more local data consumer compute and storage environment(s) associated with one or more data consumer(s) (e.g. consumer tenant(s)). The consumer tenant(s) may include more local data consumer component(s), such as asset validation system 1406, passport generation system 1408, passport storage 1412 and passport publisher service 1414. The consumer tenant(s) may be communicatively coupled to an orchestration component and may communicate with the orchestration component via a local communication protocol, for example as described in the context of FIG. 3. The local data consumer component(s) may be connected to decentral consumer network node(s), such as node 120, configured to gather or fetch digital asset(s) via peer-to-peer communications according to the decentral network protocol from decentral provider network node(s) connected to local data provider component(s) of one or more local data provider compute and storage environment(s) (e.g. provider tenant(s)).

[0306] The supply chain product may be a supply chain product as described in the context of FIG. 2. The supply chain products may be produced or producible by a production (see FIG. 11). The product may be a chemical product. The chemical product may be a chemical product described in the context of FIG. 2. The product may a product as described in the context of FIG. 2. The supply chain product(s) may be produced by upstream production stage(s) with respect to the product production stage (see FIG. 2).

[0307] The data consumer may be an entity generating digital product passports for product(s) produced or producible from the supply chain product(s). The entity generating digital product passports may be an end-product producer. The entity generating digital product passports may be a third party generating digital product passports on behalf of a participant of the product ecosystem. The data consumer may be a product producer consuming the supply chain product(s) as input material to produce one or more product(s) using the input material.

[0308] The system may be associated with decentral consumer network node 120. The node may be part of a decentral network (see FIG. 1 and FIG. 3). The node may be configured to gather policy data and digital asset(s) via the decentral network, for example as described in the context of FIG. 11. The node may be configured to provide the gathered policy data and the digital asset(s) to the system based on a representation for accessing the local data consumer component(s), for example as described in the context of FIG. 4A.

[0309] The asset validation system may be configured to validate policy data associated with digital asset(s) to be gathered from decentral provider network node(s) via the decentral network. Validating policy data may include comparing permission(s), 241372

[0310] 61 obligation(s) and / or prohibition(s) to pre-defined permission(s), obligation(s) and / or prohibition(s). The predefined permission(s), obligation(s) and / or prohibition(s) may be acceptable or non-acceptable permission(s), obligation(s) and / or prohibition(s). The asset validation system may be configured to provide a validation result to the node. Based on the validation result, the representation for accessing the local data consumer component(s) and the decentral asset identifier(s) associated with the digital asset(s) to be gathered may be provided to the node and the node may request access to the digital asset(s) based on the decentral asset identifier(s).

[0311] The asset validation system may be configured to validate digital asset(s) gathered via the decentral network. The asset validation system may validate the digital asset(s) using a rule-based engine including one or more rule(s) associated with or related to data model(s) of product(s) produced from the supply chain product(s) associated with the digital asset(s). In addition or alternatively, the rule(s) may be associated with the data model for collecting property / ies of the supply chain product(s) provided by the consumer tenant to the provider tenant(s) (see FIG. 4B). The asset validation system may be configured to validate the gathered digital asset(s) as described in the context of FIG. 15 and FIG. 17. The asset validation system may be configured to provide validated digital asset(s) for storage in one or more local target data storages of the system, such as storage general 1402 and / or storage App 1 1404. The asset validation system may be configured to trigger generation of digital product passports by the passport generation system of the system.

[0312] The passport generation system may be configured to generate digital product passports of product(s) at least in part using validated digital asset(s). The passport generation system may be configured to generate digital product passports of product(s) at least in part using validated digital asset(s) stored in storage App 1 1404. The passport generation system may be configured to provide generated digital product passports to a local target data storage, such as the passport storage, included in the system. The passport generation system may be configured to provide passport meta data, such as decentral identifier(s) included in the generated passport(s), to the passport publisher service.

[0313] The passport publisher service may be configured to generate policy data associated with generated digital product passport(s). The policy data may include decentral participant identifier(s) associated with decentral consumer network node(s) allowed to access the digital product passport(s). The policy data may further include permission(s), obligation(s) and / or prohibition(s) with respect to the processing of the accessed digital product passport(s). The generated policy data may be provided to a decentral provider network node connected to the local data consumer component(s). The passport publisher service may further be configured to generate digital representation(s) of passport data based on passport metadata, such as decentral identifier(s) associated with the generated passports. The digital representation(s) may include decentral identifier(s) associated with the passport data and / or part(s) thereof (e.g. asset(s) of the passport) and representation(s) for accessing the passport data and / or the parts thereof. The generated digital representation(s) may be provided to the decentral network, such as the decentral registry 1410, for the decentral identifier(s) to be discoverable and / or accessible by participant nodes of the decentral network.

[0314] The passport publisher service may further be configured to generate data set(s) associated with generated passport(s) for registration of such passport(s) at the decentral provider network node. The data set(s) may include decentral identifier(s) associated with the passport(s) and representation(s) for accessing the respective passport data. The representation(s) may 241372

[0315] 62 point to the local target data storage or a component of the system configured to gather passport(s) from the local target data storage in response to a request received from the decentral provider network node.

[0316] FIG. 15 illustrates a block diagram of an example system for validating digital asset(s) associated with supply chain product(s) used to produce one or more product(s). The system may be included in the asset generation and transfer system 1118 described in the context of FIG. 11. The system may be configured to perform the methods described in the context of FIG. 17.

[0317] The system, e.g. asset validation system 1406, may be connected to a decentral consumer network node, such as node 120, as described in the context of FIG. 11 . The node may provide gathered digital asset(s) based on a representation for accessing the local data consumer component(s), such as data transfer service 1502, to such local data consumer component(s). The representation may include a configuration data identifier associated with a data pipeline configured to process the gathered digital asset(s) (see also FIG. 4A).

[0318] The data transfer service may be configured to receive digital asset(s) and configuration data identifier(s) from the node. The digital asset(s) and associated configuration data identifier(s) may represent a stream of data. Such a stream may be an ordered sequence of records received from the node relatively continuously, i.e. not in accumulated batches or chunks. A record may be defined as data that can be delivered continuously in small chunks or increments. The records may or may not be time-ordered. The data transfer service may be configured to generate data package(s) including the digital asset(s) and configuration data identifier(s) received from the node. A data package may be generated per received digital asset. The data package may include further data, such as a time stamp, a date stamp, the decentral asset identifier associated with digital, the decentral participant identifier associated with the decentral provider network node(s) providing the digital asset or any combinations thereof. The data package may represent a message or an event. The generated data package data may be provided to stream storage system 1512.

[0319] The stream storage system may be configured to store data packages received (e.g. pushed) from the data transfer service. The stream storage system may be configured to provide the stored data to data validation unit 1504. The stream storage system may comprise one or more persistent or non-persistent logs, such as 1514, 1516. Records stored in said logs may be ordered, for example by using IDs. This allows to identify a record within a specific log. A record may include a data package generated by the data transfer service.

[0320] The stream storage system may provide a streaming service or stream processing service between one or more streaming sources (e.g. data transfer service 1502) and one or more streaming sinks (e.g. log 1 1514 and log 2 1516). The stream storage system may act as a persistent or non-persistent stream sink for data, such as output product data sets and verifiable credential(s) and / or presentation(s), received from consumer node 120. For example, open-source software systems such as Apache Kafka ("Kafka") or Azure Event Hubs may act as a persistent stream sink.

[0321] Data validation unit 1504 may include data consuming unit 1508. The data consuming unit may be connected to the one or more persistent or non-persistent logs of the stream storage system to ingest and process data, such as digital asset(s) and configuration data identifier(s), stored within the log(s). The stream storage system may be in a publisher-subscriber 241372

[0322] 63 relationship with the data consuming unit. For instance, data in one or more the logs(s) may be periodically read (e.g. pulled) by the data consuming unit. To avoid consumption of a data package stored in a log several times, such data package may be marked as consumed by the stream storage system. To avoid consumption of a data package stored in a log several times, an integer indicating the offset of the next data package to consume may be used. Such integer may be just one number for each persistent or non-persistent log. Such integer may be periodically checkpointed. Use of such an integer may allow the data consuming unit to re-consume data packages by rewinding the integer to an old offset.

[0323] The data consuming unit may be connected to data validator 1510. The data consuming unit may be configured to provide data packages gathered from the stream storage system to the data validator for validation of digital assets included in said data packages. The data consuming unit may be configured to extract data from the data packages and provide the extracted digital assets and configuration data identifier(s) to the data validator. The data validator may be configured to validate digital assets based on one or more rule(s) stored in a local rule data storage, such as rule DB 1506. The rule(s) may be gathered from the local rule data storage based on the configuration data identifier(s) associated with data pipeline(s) configured to validate the digital assets. This way, it may be ensured that the digital asset(s) are validated according to the rule(s) defined by the data pipeline generated to validate such digital asset(s). The data pipeline may be generated as described in the context of FIG. 4B and FIG. 8B.

[0324] The digital asset(s) may be validated by a rule-based engine based on the gathered rule(s). The one or more rule(s) may be associated with or derived from at least one data model of the product or product type. In addition or alternatively, the one or more rule(s) may be associated with or derived from a data structure for collecting property / ies of the supply chain product(s) defined by the consumer tenant(s). This may allow to verify whether gathered digital assets fulfil the data type(s) and associated value(s) and / or value range(s) required according to the at least one data model. The one or more rule(s) may define data point(s) and / or combination(s) of data point(s) to be present within the consumed digital asset. The one or more rule(s) may be defined by the mandatory supply chain product data point(s) present within the data model(s). The one or more rule(s) may be generated based on the mandatory supply chain product data point(s) present within the data model(s). This may ensure that supply chain product data point(s) required by the data model(s) is / are included in the consumed digital assets. The one or more rule(s) may define one for more supply chain product property data point(s), supply chain product identifier data point(s), supply chain product name data point(s), supply chain product producer data point(s), supply chain product declaration data point(s), supply chain product safety data point(s), supply chain product emission data point(s), supply chain product recyclate content data point(s), supply chain product biobased content data point(s), supply chain product biodegradability data point(s), supply chain product production data point(s) , supply chain product certificate of analysis data point(s), supply chain product certificate data point(s) , supply chain product life cycle data point(s), supply chain product storage instruction data point(s) and / or supply chain product processing condition data point(s). The rule may define data point(s) per data category. The rule may define data point(s) for at least two different data categories. A data category may signify property data, declaration data, safety data, emission data, recyclate content data, biobased content data, biodegradability data, production data, certificate of analysis data, certificate data, storage instruction data, assembly instruction data or operating condition data. The rule(s) and / or instruction(s) may include a hierarchy determining the order of their execution by the rule-based engine. 241372

[0325] 64

[0326] The rule-based engine may generate rule data executable by the rule-based engine. Execution of the code may result in applying the executable rule data to the gathered supply chain product data to validate the digital assets according to the obtained rule(s). Execution of the logic may result in matching consumed digital assets to condition(s) included in the executable logic, evaluating the condition(s) with matched digital assets and triggering execution of rule actions based on condition evaluation results.

[0327] The validated digital assets generated by the data validator may include one or more validated property data point(s), validated identifier data point(s), validated name data point(s), validated producer data point(s), validated declaration data point(s), validated safety data point(s), validated emission data point(s), validated recyclate content data point(s), validated biobased content data point(s), validated biodegradability data point(s), validated production data point(s), validated certificate of analysis data point(s), validated certificate data point(s), validated life cycle data point(s), validated storage instruction data point(s) and / or validated processing condition data point(s).

[0328] The data validator may further be configured to provide the validated digital assets for generating digital product passports associated with the product(s). Providing the validated digital assets may include determining storage location for persisting the validated digital assets and to provide the validated digital asset to such determined storage location. The storage location may be determined based on the configuration data identifier(s) and configuration data stored in a local data pipeline data storage, such as pipeline DB 1518. The configuration data may include configuration data identifiers and data pipeline configuration data. The data pipeline configuration data may include a representation for accessing a local target data storage for storing the validated digital assets. By using different storage locations to persist the validated digital assets, data security may be improved by avoiding unauthorized access to validated digital assets by applications, such as passport generators. Validated digital assets which may not be associated with a given data pipeline may be persisted in a general storage, such as storage general 1402. Non-validated digital assets or data points thereof may be persisted in the general storage.

[0329] The asset validation system may further include an incident data generator configured to generate incident data based on non-validated supply chain product data points and / or data stored in a local target data storage, such as storage general 1402. The non-validated supply chain product data points and / or data may be associated with a classifier indicating non- compliance with one or more applied rule(s). The classifier may include “not validated”, “not valid”, “validation failed” or “failed”. The classifier may be associated with each data point which could not be validated upon application of the one or more rule(s). Each data point which could not be validated may be associated with a respective decentral asset identifier. Each data point which could not be validated may be associated with rule data indicating the rule that resulted in nonvalidation of the respective data point. The rule data may include the rule. The rule data may include the executable logic generated from the rule. The incident data generator may be configured to gather data point(s) associated with the classifier per decentral asset identifier and to assemble gathered supply chain product data points and / or data into incident data. The incident data generator may provide the generated incident data to the data transfer service. The data transfer service may be configured to determine the decentral provider node having provided the non-validated supply chain product data. The data transfer service may be configured to initiate a transfer of the incident data to the determined decentral provider network node connected to local data provider component(s) having generated the non-validated supply chain product data 241372

[0330] 65 points and / or digital assets via the node connected to the data transfer service. The data transfer service may provide the incident data in combination with decentral participant identifier(s) associated with the decentral provider network node(s) via the local communication protocol to the orchestration component for notification of the provider tenant having generated the non-validated data points or digital assets. The incident data may be provided to the node, such as provider node 118, using an endpoint of such node configured to receive data from other nodes of the decentral network. By using the incident data, updated digital asset(s) may be generated and provided for access by the provider tenant(s). This way, non-validated supply chain product data can be corrected, enabling a higher data quality of the digital product passport. This allows more efficient processing of products associated with such digital product passports and / or more efficient production of further products produced using the product based on the data included in the digital product passport.

[0331] FIG. 16 illustrates a block diagram of an example system for generating and / or updating a digital product passport associated with a product based at least in part on validated digital asset(s) associated with supply chain product(s) used to produce the product. The product may be a product as described in the context of FIG. 2. The product may be produced or producible from one or more supply chain product(s) by a production chain (see FIG. 2). The digital product passport may be part of a digital twin of the product. The product passport may correspond to the digital twin of the product. The system illustrated in FIG. 16 may be included in the asset generation and transfer system 1118 illustrated in FIG. 11. The system may be configured to perform the methods described in the context of FIG. 17.

[0332] The digital product passport (also denoted as product passport hereinafter) may be a data set having a defined semantic structure. The defined semantic structure may be obtained by applying a data model to data associated with the production of the product. The data model may define a semantic description of the respective digital product passport. The semantic description may include the structure of at least a portion of the digital product passport, and / or properties of the product passport. The properties of the digital product passport may include data types. The properties of the digital product passport may include possible or allowable values and / or value ranges. The properties of the digital product passport may be a physical unit of parameter(s) described by values contained in the digital product passport. The properties of the digital product passport set may include one or more attribute(s). The data model may define data points, such as data types and values and / or value ranges, to be included in the digital product passport.

[0333] The digital product passport may include at least one decentral identifier and passport data. The decentral identifier may comprise any unique identifier uniquely associated with the product. The decentral identifier may include one or more Universally Unique Identifier(s) (UUID) or Digital Identifier(s) (DID). Via the decentral identifier and its unique association with the product access to the passport data may be controlled by the data owner of the passport data, such as the product producer, the entity generating the digital product passport or the entity on behalf of which the digital product passport is generated. This contrasts with central authority schemes, where identifiers are provided by such central authority and access to data is controlled by such central authority. The decentral identifier may be discoverable and / or accessible for participant node(s) of the decentral network. The decentral identifier may be provided to the decentral network to be discoverable and / or accessible for the participant node(s). The decentral identifier may be stored in decentral registry / ies accessible for the participant node(s). 241372

[0334] 66

[0335] The passport data may include data points defined by the data model used to generate the respective digital product passport. The passport data may include data associated with the production of the product and product identifier(s) associated with the product. This way, the product passport may be uniquely linked to the product. Data associated with the production of the product may include supply chain product data associated with at least a part of the supply chain product(s) used to produce the product. Supply chain product(s) used to produce the product may include supply chain product(s) used in one or more production step(s) of the production chain used to produce the product. Supply chain products(s) may be produced by a supply chain product production, for example as illustrated in FIG. 11. Data associated with the production of the product may include product data associated with the product.

[0336] Supply chain product data and / or product data may include one or more chemical and / or physical property / ies associated with the supply chain product or product, respectively. The chemical and / or physical property / ies may include at least one measured chemical and / or physical property and / or at least one chemical and / or physical property determined from collected data associated with the production and / or the use of the supply chain product and / or product. The collected data may be used to determine the at least one physical and / or chemical property. For instance, the at least one physical and / or chemical property may be determined from sensor data obtained from sensor(s). The data may be collected with a suitable sensor configured to measure the chemical and / or physical property. The measured at least one physical and / or chemical property may be obtained by sensors configured to measure such property. The sensor may be included in a measuring device. The sensor may correspond to the measuring device.

[0337] The digital product passport may include one or more authentication mechanisms associated with the decentral identifier(s) and the passport data. The product passport may relate to one or more authorization mechanisms associated with the decentral identifier(s) and the passport data. The digital product passport and / or the decentral identifier(s) may be associated with a digital representation of the passport data. The digital representation may include representation(s) for accessing the passport data or parts thereof. The representation for accessing the passport data or parts thereof may include a locator or pointer, such as am url or uri, to a data storage storing the passport data for access by data consumer(s). The data storage may be associated with the data owner of the passport data. Access to the data storage may be controlled by the data owner via the decentral identifier. The digital representation(s) may further include at least a part of the decentral identifier(s). The digital representation(s) may be provided to a decentral database. This may allow discovery of and / or access to the decentral identifier(s) by participant node(s) of the decentral network. The decentral database may be associated with the data owner of the passport data and / or the entity generating the digital product passports. Access to the decentral database may be controlled based on decentral participant identifiers associated with decentral consumer network nodes by the data owner of the passport data.

[0338] For generating and / or updating digital product passport(s), the system, e.g. passport generation system 1408, may receive a request to generate and / or update digital product passport(s) for one or more given product(s). The request may include product identifier(s). The request may further include supply chain product identifier(s) associated with supply chain product(s) used to produce the product. Identifier(s) may include batch number(s), LOT number(s), part number(s), serial number(s) or identification number(s). The request may be received from an input device connected to the system. The 241372

[0339] 67 request may be received from asset validation system 1406. The request may be provided to stream storage system 1602 of the system.

[0340] The system may include the stream storage system and data aggregator 1608. The system may be associated with a local target data storage, such as passport storage 1120. The passport storage may store generated and / or updated digital product passports associated with the products. The passport storage may be configured to provide digital product passports upon request, for example upon request of a decentral network node associated with a data consumer and / or upon request of the system.

[0341] The stream storage system may be configured to receive requests for digital product passports, for example from one or more applications and / or asset validation system 1406. Requests may be received via a communication interface, such as an API. The stream storage system may be configured to authenticate such requests, for example based on authentication data contained in such requests. The requests may represent a stream of data. Such a stream may be an ordered sequence of records or data packages received relatively continuously, i.e. not in accumulated batches or chunks. A record may for example comprise a request for a product passport for a given product. The records may or may not be time-ordered.

[0342] The stream storage system may be configured to store received data packages. Data packages may be stored upon successful authentication. The stream storage system may be configured to provide the stored data to the data aggregator. The stream storage system may be configured to provide the stored data to data gathering unit 1610 of the data aggregator. The stream storage system may comprise one or more persistent or non-persistent logs 1604, 1606. In this embodiment, the stream storage system comprises two persistent or non-persistent logs 1604, 1606 (i.e. log 1 1604 and log 2 1606). Records stored in said logs may be ordered, for example by using IDs. This allows to identify a record within a specific log. A record may include a received request. The stream storage system may provide a streaming service or stream processing service between one or more streaming sources (e.g. application providing the request) and one or more streaming sinks (e.g. log 1 1604 and log 2 1606). The stream storage system may act as a persistent or non-persistent stream sink for requests for product passports. For example, open-source software systems such as Apache Kafka ("Kafka") or Azure Event Hubs may act as a persistent stream sink.

[0343] The stream storage system may be configured to determine if the received or pulled data package(s) is / are already contained in the one or more persistent or non-persistent logs as described in the context of FIG. 15.

[0344] The data aggregator may be connected to the stream storage system. The data gathering unit of the data aggregator may be connected to the stream storage system. The data gathering unit may be connected to the one or more persistent or non- persistent logs of the stream storage system to ingest and process data package(s) stored within the log(s). The stream storage system may be in a publisher-subscriber relationship with the data gathering unit. For instance, data in one or more the logs(s) may be periodically read (e.g. pulled) by the data gathering unit. To avoid consumption of a data package stored in a log several times, such data package may be marked as consumed by the stream storage system. To avoid consumption of a data package stored in a log several times, an integer indicating the offset of the next data package to consume may be used. Such integer may be just one number for each persistent or non-persistent log. Such integer may be 241372

[0345] 68 periodically checkpointed. Use of such an integer may allow the data gathering unit to re-consume data packages by rewinding the integer to an old offset.

[0346] The data gathering unit may be configured to gather data associated with the production of the product based on the data ingested from the stream storage system. The data gathering unit may be configured to determine supply chain product identifier(s) associated with supply chain product(s) used to produce the product based on the product identifier included in the ingested data. For example, the data gathering unit may query a database associated with or included in the system (not shown in FIG. 16) for supply chain product identifier(s) based on the product identifier(s) included in the ingested data. In addition or alternatively, the data aggregator may be configured to initiate determination of supply chain product identifier(s) associated with the supply chain product(s) used to produce the product by generating a request including the product identifier(s) and providing such request to via a decentral consumer network node, such as node 120, connected to the system to a decentral node configured to determine decentral identifier(s) associated with supply chain product(s) used to produce the product based on the receive product identifier(s). The decentral node may be a decentral infrastructure node. The determined decentral identifier(s) may be provided via the decentral consumer node to the data gathering unit.

[0347] Data associated with the production may include validated data associated with the production of the product, such as supply chain product sets validated as described in the context of FIG. 14 and FIG. 16. The data gathering unit may be configured to gather such validated data from a database associated with the system, such as storage App 1 1404. The validated data may be gathered based on the product identifier(s) associated with the product and supply chain product identifier(s) associated with supply chain product(s) used to produce the product. The data gathering unit may further be configured to initiate gathering of data associated with the production of the product from a decentral network, such as the decentral network described in the context of FIG. 1, based on the product identifier(s) included in the ingested data and optionally based on decentral supply chain product identifier(s) received from a decentral node as previously described. The node may be configured to gather product data and / or supply chain product data via the decentral network 134, for example as described in the context of FIG. 11. The gathered data may be provided by the node to the data gathering unit. The data gathered from the decentral network may be persisted in a storage, such as storage App 1 1404, and the data gathering unit may be configured to gather such data based on respective identifier(s) from such storage. The gathered data may be validated as described in the context of FIG. 14. The data gathering unit may further be configured to gather product data associated with the product, for example from database(s) storing such product data (not shown in FIG. 16). The data gathering unit may be configured to initiate validation of the product data as described in the context of FIG. 15.

[0348] The data gathering unit may provide the gathered data associated with the production of the product to passport generator 1612. The passport generator may be configured to generate digital product passports associated with products and / or to update existing digital product passports, such as digital product passports stored in the passport storage. The passport generator may be configured to generate and / or update the digital product passports based on data received from the data gathering unit. The data received from the data gathering unit may be validated data associated with the production of the product. Validated data associated with the production of the product may include the product identifier(s), validated supply chain product data associated with supply chain product(s) used to produce the product and product data associated with the product. The product data may be validated product data. 241372

[0349] 69

[0350] The passport generator may be configured to determine whether a digital product passport is already existing in the passport storage for a product associated with product identifier(s) received from the data gathering unit. The passport generator may be configured to query the passport storage using product identifier(s) received from the data gathering unit. If no digital product passport is existing for such product identifier(s) in the passport storage, the passport generator may be configured to generate a decentral identifier associated with the data associated with the production of the product. Alternatively, the passport generator may be configured to request such a decentral identifier from a decentral identifier provider. The decentral identifier provider may be part of the system (not shown). The decentral identifier provider may be associated with the system (not shown).

[0351] The passport generator may be configured to gather a data model associated with the respective product. The data model may be associated with a product type associated with the respective product. The data model may be stored in a database included in or associated with the passport generator (not shown). Such database may include data model(s) and associated model identifier(s). The model identifier(s) may include product type identifier(s). The passport generator may be configured to gather such data model based on the product identifier(s) associated with the product. A mapping table may be used to determine product type identifier(s) based on the product identifier(s) and such product type identifier(s) may be used to gather the respective data model from the database.

[0352] The passport generator may be configured to generate passport data by applying the gathered data model to the data associated with the production of the product received from data the gathering unit and the decentral identifier. Applying the data model to the data associated with the production of the product and the decentral identifier may include transforming the data associated with the production of the product according to such data model. The resulting digital product passport may include the decentral identifier and one or more data point(s) defined according to the data model (e.g. passport data). The passport generator may be configured to provide the generated digital product passport to the passport storage. Alternatively, the passport generator may be configured to generate a data set by applying the gathered data model to the data associated with the production of the product received from the data gathering unit and to provide the generated data set to the passport storage for updating an existing digital product passport associated with the product.

[0353] The passport generator may be configured to provide passport metadata, such as the decentral identifier to passport publisher service 1614.

[0354] The passport publisher service may be configured to generate policy data associated with the digital product passport(s). The policy data may include decentral participant identifier(s) associated with decentral consumer network node(s) allowed to access the passport data. The policy data may further include permission(s), obligation(s) and / or prohibition(s) with respect to processing the passport data. The passport publisher service may be configured to generate the policy data in response to user input(s) received via a client device connected to the system. The passport publisher service may be configured to generate the policy data based on predefined permission(s), obligation(s) and / or prohibition(s). The passport publisher service may further be configured to link the generated policy data to the digital product passport. The policy data may be generated by the passport publisher service per product passport. The policy data linked to the passport data may be provided to a decentral provider network node connected to the system. The decentral provider network node may be 241372

[0355] 70 configured to control access to the digital product passports based on policy data linked to such product passport(s) via the decentral identifier(s).

[0356] The passport publisher service may further be configured to generate digital representation(s) of passport data. The digital representation(s) of the passport data may include the decentral identifier(s) and a representation for accessing the passport data as previously described. The passport publisher service may be configured to provide the digital representation(s) of the passport data to decentral registry 1410 storing such digital representation(s). Via the decentral registry, the decentral identifiers may be discoverable and / or accessible for participant nodes of the decentral network, for example as described in the context of FIG. 11. Access to the decentral registry may be controlled by the data owner of the digital product passport(s) via the decentral provider network node.

[0357] The passport publisher service may be configured to generate a data set (e.g. passport metadata) including decentral identifier(s) of the product passport and a representation for accessing the product passport. The representation for accessing the product passport set may point to the passport storage storing the product passport. The passport publisher service may provide the data set to the decentral provider network node.

[0358] FIG. 17 illustrates a flow chart of an example method for validating digital asset(s) associated with supply chain product(s) used to produce one or more product(s) gathered via a decentral network protocol by decentral consumer network node(s) connected to local data consumer component(s) of a local data consumer compute and storage environment (e.g. consumer tenant) in response to a request to consume digital asset(s) received via a local communication protocol from an orchestration based on a trigger by local data provider component(s) of local data provider compute and storage environment(s) (e.g. provider tenant(s)). The method may be implemented by the local data consumer component(s) of the consumer tenant. The consumer tenant and the provider tenant(s) may be connected via the local communication protocol to the orchestration component, for example as described in the context of FIG. 3. The consumer tenant may include a system as described in the context of FIG. 14 or a system as described in the context of FIG. 15. The local data consumer component(s) may be connected to a decentral consumer network node configured to access the digital asset(s) via peer-to- peer communications according to a decentral network protocol at decentral provider network node(s) connected to the local data provider component(s). The provider tenant may be associated with a data provider, such as a supply chain product producer. The consumer tenant may be associated with a data consumer. The data consumer may be the product producer or an entity generating digital product passports of the products.

[0359] The product may be a product described in the context of FIG. 2. The supply chain product(s) may be produced by upstream production stage(s) with respect to the product production stage (see FIG. 2). The supply chain product(s) may include supply chain product(s) described in the context of FIG. 2.

[0360] A request to consume digital asset(s) may be received based on the trigger by the local data provider component(s) of the local data provider computing and storage environment(s). The request may be received from the orchestration component by the local data consumer component(s) via the local communication protocol(s). The request may be received from the orchestration component as described in the context of FIG. 4A. The request may be provided by the orchestration component in response to a trigger for consuming digital asset(s) provided to the orchestration component by the local data 241372

[0361] 71 provider component(s), for example as described in the context of FIG. 4A. The request may include the decentral asset identifier(s) associated with the digital asset(s) to be consumed, the decentral participant identifier associated with the decentral provider network node(s) providing access to the digital asset(s) to be consumed and endpoint(s) of such decentral provider network node(s). The request may further include the name of the data provider.

[0362] Configuration data associated with the consumption of the digital asset(s) may be generated or selected based on the received request. The configuration data may be associated with a data pipeline configured for processing digital asset(s) gathered via the decentral network from the decentral provider network node(s) based on the decentral network protocol. The configuration data may include a configuration data identifier uniquely identifying the configuration data within the consumer tenant and data pipeline configuration data associated with a configuration of the data pipeline for processing the consumed digital asset(s). The data pipeline may relate to a local target data storage associated with the consumer tenant. The local target data storage may store validated digital asset. The data pipeline configuration data may include a representation for accessing a target data storage configured to store validated supply chain product data, a mapping for mapping the data points included in the validated supply chain product data to the data structure of the target data storage and one or more validation rules for processing, e.g. validating, the digital asset(s) gathered via the decentral network protocol from the decentral provider network node(s) and decentral participant identifier(s) associated with the decentral provider network node(s). The configuration data may be selected based on the decentral participant identifier(s) and / or the provider name included in the received request. Selecting configuration data may include selecting existing configuration data based on the decentral participant identifier(s) and / or the provider name included in the received request. The configuration data may be generated as described in the context of FIG. 8B.

[0363] Digital asset(s) may be gathered via the decentral network based on the decentral asset identifier(s) and endpoint(s) included in the received request. The decentral network may be the decentral network 134 described in the context of FIG. 1. Gathering the digital asset(s) via the decentral network may include accepting permission(s), obligation(s) and / or prohibition(s) related to the processing of such digital asset(s) prior to gathering such digital asset(s) from the decentral provider network node(s) connected to local data provider component(s) of the provider tenant(s). The digital asset(s) may be gathered by the decentral consumer network node connected to local data consumer component(s) of the consumer tenant from the decentral provider network node(s) connected to the local data provider component(s) of the provider tenant, for example as described in the context of FIG. 11 . For gathering the digital asset(s), the decentral asset identifier(s), endpoint(s) and a digital representation for accessing the local data consumer component(s) may be provided to the decentral consumer network node. The digital representation may include the configuration data identifier associated with the generated or selected configuration data. For instance, the configuration data identifier may be appended to an endpoint of the local data consumer component(s). The endpoint may be used by the decentral consumer network node to provide the gathered digital asset(s) along with the configuration data identifier to the local data consumer component(s), for example as described in the context of FIG. 4B. By appending the configuration data identifier to the endpoint, the local data consumer component(s) may determine the configuration data to be used for processing the gathered digital asset(s). This way gathered digital asset(s) may be reliably processed using the correct processing operation(s) despite the presence of multiple data pipelines associated with different processing operation(s) existing within the consumer tenant. Processing the gathered digital asset(s) using the correct processing operations may allow to ensure that the gathered digital asset(s) are 72 validated according to the correct rule(s), e.g. the rule(s) associated with the correct data model(s), allowing to process multiple digital assets(s) gathered via the decentral network from different decentral provider network node(s) in a reliable way. This allows to ensure a high data quality of the generated digital product passports, ensuring reliable processing of the product and / or production of further products using the product based on the digital product passports.

[0364] The gathered digital asset(s) may be processed according to the selected or generated configuration data. Processing may include validating the digital asset (s) using a rule-based engine including one or more rule(s) associated with the product and / or one or more rule(s) associated with the data model for collection property / ies of the supply chain product provided by the consumer tenant to the provider tenant(s), for example as described in the context of FIG. 15. The gathered digital asset(s) may be validated based on the configuration data. The configuration data may include the rule(s) or rule identifier(s) associated with the rule(s). The configuration data may be determined based on the configuration data identifier included in the data received from the decentral consumer network node. Executable logic may be generated from the rule(s) identified by the configuration data. Executable logic may include machine code, interpretable code, bytecode, and / or code that runs on a virtual machine. The logic included in the rule(s) may be encoded in the executable logic. The logic included in the rule(s) may be mirrored in the executable logic. The gathered digital asset(s) may be validated by executing the generated executable logic. The executable logic may be subject to rule execution criteria. Rule execution criteria may include rule execution order, exemptions and conditions. Validation data including the result of the validation may be generated by the rule engine. The validation data may include the supply chain product data points subject to the validation process and associated classifiers. The classifiers may indicate whether the respective supply chain product data point passed or failed the validation process. The validation data may further include rule data associated with data point(s) for which validation failed. The rule data may indicate the applied rule(s) which resulted in a fail of the validation of such data point.

[0365] It may be verified whether the gathered digital asset(s) could be validated according to one or more determined rule(s) (e.g. one or more rule(s) included in or identified by the determined configuration data). If the gathered digital asset(s) could not be validated, e.g. application of such rule(s) did result in error(s), message data may be generated and provided. The message data may include an indication that the digital asset(s) could not be validated. The message data may include validation results indicating the validation failure. The message data may be provided for display to a user. The validation data including the non-validated supply chain product data may be provided to a storage location, for example as described in the context of FIG. 15. The validation data including the non-validated supply chain product data may be used to generate incident data, for example as described in the context of FIG. 14.

[0366] If only a part of the gathered digital asset(s) could be validated, e.g. application of a part of the rule(s) did result in any error, message data may be generated and provided as previously described. The validation data including the non-validated supply chain product data may be provided to a storage location as previously described.

[0367] If the gathered digital asset(s) could be validated according to the determined rule(s), e.g. application of such rule(s) did not result in any error, the validated supply chain product data may be linked to at least one of the product identifiers. This step may be generally optional. This may allow to gather the validated supply chain product data based on at least one of the product identifiers, for example upon generating the product passports. 73

[0368] The validated supply chain product data may be provided for generating digital product passport(s) associated with the product. Providing the validated supply chain product data may include determining storage location(s) for at least a part of the validated supply chain product data. Storage location(s) for at least a part of the validated supply chain product data may be determined based on identifier(s) associated with the validated supply chain product data. The identifier(s) may be included in the validated supply chain product data. The storage location(s) may be determined as described in the context of FIG. 15. Providing the validated supply chain product data to a database used by a defined application to process the validated supply chain product data may allow to sort the validated supply chain product data according to applications processing or consuming the validated supply chain product data. This may improve security since unauthorized data access by applications not processing the validated supply chain product data stored in such database is avoided. Moreover, this may reduce latency to generate digital product passports since the amount of data stored within a particular database is reduced by selectively providing validated supply chain product data to be processed by a given application to database(s) associated with such application. At least a part of the validated supply chain product data optionally linked to at least one of the product identifiers may be provided to determined storage location(s). The validated supply chain product data provided to such storage location(s) may be persisted in such storage location(s).

[0369] By gathering digital asset(s) based on decentral asset identifier(s) included in requests received from local provider component(s) of provider tenant(s) via the orchestration component, querying of the decentral network to locate the required digital asset(s) may be avoided. The requests may serve as a notification to local data consumer component(s) of the consumer tenant on digital asset(s) available for access via the decentral network and may allow to gather the available digital asset(s) via the decentral network more efficiently and reliably based on the data included in the received requests. This way, inefficient and / or repeated querying of the decentral network for digital assets required to generate digital product passports by the decentral consumer network node connected to the consumer tenant may be avoided, allowing to more efficiently generate digital product passports. More efficient generation of digital product passports allows more efficient processing of the product and / or more efficient production of further products using the product based on the digital product passports.

[0370] By validating the gathered digital asset using one or more rule(s) determined based on the configuration data identifier associated with the respective configuration data to be used for the validation, multiple digital assets may be gathered and processed from decentral provider network nodes connected to different provider tenants while ensuring that gathered digital assets are correctly validated and persisted to a database associated with an application consuming the persisted validated supply chain product data. By validating the gathered digital assets by local data consumer component(s) of the consumer tenant, the digital assets can be directly gathered from the decentral provider network nodes connected to the provider tenants without requiring the provider tenants to generate digital assets using complex data model(s) associated with the respective supply chain product. This way, the effort to generate and provide the digital assets by the provider tenants is greatly reduced while maintaining data sovereignty, hence resulting in reliable, quick and secure sharing of digital assets required to generate the digital product passports via the decentral network protocol. This in turn may allow to generate digital product passports associated with products produced from such supply chain products in a more reliable and efficient way, ensuring a high data quality of the digital product passports and avoiding delays in the generation which may lead to delays in the supply of products associated with such digital product passports. 241372

[0371] 74

[0372] FIG. 17 illustrates a method for generating digital product passport(s) associated with product(s) produced or producible from one or more supply chain product(s) based at least in part on validated supply chain product data associated with such supply chain product(s). The supply chain products(s) may be used as production input(s) in one or more production stage(s) associated with the production of the product (see FIG. 2). The production stage(s) may be performed by one or more supply chain participant(s). The product may be a product as described in the context of FIG. 2. The supply chain product may be a product as described in the context of FIG. 2.

[0373] Produced product(s) may be physical entity / ies of product(s) having been produced by the production. Producible product(s) may not yet have been produced by the production but may be producible by one or more production process(es) performed within the production. Producible product(s) may include product(s) planned to be produced, for example based on demand data received from downstream participant(s) (e.g. product consumer(s)). Producible product(s) may include product(s) which can be produced by one or more process step(s) performed within the production.

[0374] Product identifier(s) associated with the product may be provided. The product identifier(s) may be digital product identifier(s). The product identifier(s) may include a product name, a product number, a LOT number, a batch number, a serial number, a product type, an identification number or any combinations thereof. Product identifier(s) may further include one or more supply chain product identifier(s) associated with the supply chain product(s) used to produce the product.

[0375] Supply chain product identifier(s) associated with the supply chain product(s) used to produce the product may be determined. This step may be optional. This step may be performed if the product identifier(s) may not include supply chain product identifier(s). Supply chain product identifier(s) may be determined by querying databases storing product identifier(s) linked to supply chain product identifiers of supply chain product(s) used to produce the product. Supply chain product identifier(s) may be determined by querying infrastructure node(s) of the decentral network 134 based on the product identifier(s), for example as described in the context of FIG. 16. Such infrastructure node(s) may be configured to determine supply chain product identifier(s) associated with a given product identifier based on relationship data indicating relationships between the product identifier and supply chain identifier(s) per production stage used to produce the product.

[0376] Data associated with the production of the product may be data gathered. This step may be optional. Data associated with the production of the product may include product data associated with the product. Product data may include property data associated with the product, product name, product producer, declaration data, safety data, production data associated with the product, certificate of analysis data associated with the product, certificates associated with the product, life cycle data associated with the product, storage instruction data associated with the product, assembly instructions associated with the product, operating conditions associated with the product, handling instructions associated with the product or any combination thereof. Property data may include measured chemical and / or physical property / ies associated with the product and / or chemical and / or physical property / ies determined from data associated with the production of the product and / or the use of the product. The property data may include composition data associated with the chemical composition of the product, emission data associated with the product, recyclate content data associated with the product, biobased content data associated with the product, renewable content data associated with the product, biodegradability data associated with the product or any combinations thereof. 241372

[0377] 75

[0378] Data associated with the production of the product may include digital asset(s) associated with supply chain product(s) which has / have not yet been gathered via the decentral network 134 and validated as described in the context of FIG. 15 and FIG. 16. Such digital asset(s) may be gathered via the decentral network 134 by determining endpoint(s) of decentral providing network node(s) providing such digital asset(s) for access and decentral asset identifier(s) of such supply chain product data and gathering the digital asset(s) based on the determined endpoint(s) and decentral asset identifier(s). The decentral asset identifier(s) may be discoverable and / or accessible for the decentral consumer network node connected to the consumer tenant. Such gathered digital asset(s) may be validated as described in the context of FIG. 15 and FIG. 16. Gathering data associated with the production of the product from the decentral network in addition to gathering the validated supply chain product data allows to increase the degree of compl...

Claims

24137277CLAIMS1 . A method, in particular a computer-implemented method executed by at least one orchestration component of a local orchestration compute and storage environment, for monitoring and / or controlling data exchange between decentral provider network node(s) connected to one or more local data provider component(s) of one or local data provider compute and storage environment(s) and decentral consumer network node(s) connected to one or more local data consumer component(s) of one or more local data consumer compute and storage environment(s), wherein the one or more local data provider components and the one or more local data consumer components are configured to provide triggers to and to receive requests from the at least one orchestration component communicatively coupled to the one or more local data provider component(s) and the one or more local data consumer component(s) via local communication protocol(s), the method comprising:• providing mapping data including mappings between local identifiers associated with local data provider compute and / or storage environments and local data consumer compute and storage environments and decentral participant identifiers associated with such compute and storage environments,• receiving via the local communication protocol an asset generation trigger for generating a digital asset associated with a supply chain product and for providing the generated digital asset for access by one or more of the decentral consumer network node(s) from one or more of the local data consumer component(s) and / or receiving via the local communication protocol an asset consumption trigger for consuming generated digital asset(s) associated with supply chain product(s) by one or more of the decentral consumer network node(s) from one or more of the local data provider component(s), wherein the asset generation trigger includes decentral participant identifier(s) associated with local data provider compute and / or storage environments requested to generate and provide the digital asset and / or wherein the asset consumption trigger for consuming generated includes decentral participant identifier(s) associated with the decentral consumer network node(s) requested to gather the generated digital asset(s);• determining local identifier(s) associated with the local data provider compute and storage environment(s) and / or the local data consumer compute and storage environment(s) based on the received trigger(s) and the mapping data,• generating a request for generating the digital asset and for providing the generated digital asset for access based on the received asset generation trigger and providing the generated request via the local communication protocol to local data provider component(s) associated with the determined local identifier(s) for triggering generation of the digital asset and provision of the generated digital asset for access by the local data provider component(s) and / or generating a request for consuming generated digital asset(s) based on the received asset consumption trigger and providing the generated request via the local communication protocol to local data consumer component(s) associated with the determined local identifier(s) for triggering gathering of the generated digital asset(s) by the decentral consumer network node(s) connected to the local data consumer component(s).

2. The method of claim 1, wherein the at least one orchestration component is configured to orchestrate the one or more local data provider component(s) and the one or more local data consumer component(s), e.g. via the local24137278 communication protocol(s), for data exchange between the decentral provider network node(s) and the decentral consumer network node(s), e.g. via decentral communication protocol(s).

3. The method of claim 1 or 2, wherein the local data consumer compute and storage environment(s) are associated with local identifier(s) identifying the local data consumer compute and storage environment(s) within a local environment associated with the local communication protocol and with decentral participant identifier(s) identifying the data consumer(s) associated with the local data consumer compute and storage environment(s) within a decentral network associated with the decentral network protocol.

4. The method of any one of the preceding claims, wherein the local data provider compute and storage environment(s) are associated with local identifier(s) identifying the local data provider compute and storage environment(s) within a local environment associated with the local communication protocol and with decentral participant identifier(s) identifying the data provider associated with the local data provider compute and storage environment(s) within a decentral network associated with the decentral network protocol.

5. The method of any one of the preceding claims, wherein the local data provider component(s) communicate with the local data consumer component(s) associated based on the local communication protocol via the orchestration component.

6. The method of any one of the preceding claims, wherein the local identifiers identify the local data provider compute and storage environments and the local data consumer compute and storage environments within a local environment and wherein the decentral participant identifiers identify decentral network node(s) connected to such compute and storage environments within a decentral network.

7. The method of any one of the preceding claims, wherein the mapping data is stored in a configuration data base accessible by the at least one orchestration component, wherein the at least one orchestration component is configured to access the mapping of local identifiers to decentral identifiers.

8. The method of any one of the preceding claims, wherein the mapping data further includes endpoint(s) of decentral provider network node(s) associated with at least a part of the decentral participant identifiers.

9. The method of any one of the preceding claims, wherein the asset generation trigger further includes a data structure for collecting property / ies of the supply chain product and / or wherein the asset consumption trigger further includes decentral asset identifier(s) associated with the generated digital asset(s).

10. The method of any one of the preceding claims, wherein the asset generation trigger is received by the orchestration component for providing a request for generating and providing the digital asset via the local communication protocol to one or more of the local data provider component(s), in particular to one or more of the local data provider component(s) associated with the one or more decentral participant identifier(s) included in the received asset generation trigger.2413727911 . The method of any one of the preceding claims, wherein the asset consumption trigger is received by the orchestration component for providing a request for consuming the generated digital asset(s) via the local communication protocol to one or more of the local data consumer component(s), in particular to one or more of the local data consumer component(s) associated with the one or more decentral participant identifier(s) included in the received asset consumption trigger.

12. The method of any one of the preceding claims, wherein the digital asset includes a decentral asset identifier associated with the supply chain product and further includes at least one chemical and / or physical property of the supply chain product and / or emission data and / or recycled content data and / or biobased content data and / or renewable content data and / or production data associated with the production of the supply chain product.

13. The method of any one of the preceding claims, wherein the asset generation trigger is generated by the local data consumer component(s) based on generated or selected configuration data, wherein the generated or selected configuration data includes a representation for accessing a local target data storage of the local data consumer compute and storage environment configured to store processed digital asset(s), a data structure for collecting at least one property associated with the supply chain product and one or more decentral participant identifier(s) associated with decentral provider network node(s) connected to one or more local data provider component(s) requested to generate and provide the digital asset.

14. The method of any one of the preceding claims, wherein the asset consumption trigger is generated by the local data provider component(s) based on generated or selected configuration data, wherein the generated or selected configuration data includes a configuration data identifier, a representation for accessing supply chain product data stored in a local source data storage of the local data provider compute and storage environment and being associated with the supply chain product(s), a data model received via or defined by the asset generation trigger for collecting at least one property of the supply chain product(s) and one or more decentral participant identifier(s) associated with the decentral consumer network node(s) requested to consume the generated digital asset(s).

15. A system for monitoring and / or controlling data exchange according to a decentral communication protocol between decentral provider network node(s) connected to one or more local data provider component(s) of one or local data provider compute and storage environment(s) and decentral consumer network node(s) connected to one or more local data consumer component(s) of one or more local data consumer compute and storage environment(s), wherein the one or more local data provider components and the one or more local data consumer components are connected to at least one orchestration component via local communication protocol(s), the system comprising: the one or more local data provider compute and storage environment(s) including the one or more local data provider components configured to• provide configuration data for generating and providing a digital asset to be consumed via a decentral network protocol by the decentral consumer network node(s), wherein the digital asset is associated with a supply chain product produced or producible by a supply chain production using one or more production input(s) and wherein the configuration data includes a representation for accessing supply chain product data stored in a local source data storage and being associated with the supply chain24137280 product, a data model associated with the supply chain product or a product produced using the supply chain product and one or more decentral participant identifier(s) associated with the one or more decentral consumer network node(s);• generate a digital asset associated with a supply chain product produced or producible by a production from one or more production input(s) based on the configuration data and providing the digital asset for access via the decentral network protocol by the decentral consumer network node(s); wherein a request for consuming the generated digital asset via the decentral network protocol by the decentral consumer network node(s) is triggered by the one or more local data provider component(s), optionally wherein an asset consumption trigger for requesting consumption of the generated digital asset is generated by the one or more local data provider component(s) by selecting and / or providing at least a part of the configuration data, or wherein a request for generating and providing the digital asset for access via the decentral network protocol by the decentral consumer network node(s) is received by one or more of the local data provider component(s) based on a trigger by one or more of the local data consumer component(s); the one or more local data consumer compute and storage environment(s) including the one or more local data consumer component(s) configured to• receive a request for consumption of generated digital asset(s) associated with the supply chain product(s) by the decentral consumer network node(s) via the decentral network protocol based on a trigger by one or more of the local data provider component(s), wherein the request is received from at least one orchestration component by one or more of the local data consumer component(s) via the local communication protocol(s),• generate or select - based on the received request - configuration data associated with the consumption of digital asset(s) and the processing of consumed digital asset(s);• gather the digital asset(s) by the decentral consumer network node(s) from decentral provider network node(s) connected to one or more of the local data provider component(s) based on the received request,• process at least a part of the gathered digital asset(s) based on the generated or selected configuration data and provide the processed digital asset(s) for generating digital product passport(s) associated with the one or more product(s); wherein the request for consumption of generated digital assets(s) associated with the supply chain product(s) is triggered by the one or more local data consumer component(s), or wherein the request for consumption of generated digital assets(s) associated with the supply chain product(s) is received by the one or more local data consumer component(s) based on a trigger by one or more of the local data provider component(s); a local orchestration compute and storage environment including the one or more local orchestration component(s), wherein the local orchestration compute and storage environment includes a configuration24137281 database storing mapping data including mappings between local identifiers associated with local data provider compute and / or storage environments and local data consumer compute and storage environments and decentral participant identifiers associated with such compute and storage environments and wherein the orchestration component is configured to determine local identifier(s) associated with the local data provider compute and storage environment(s) and / or the local data consumer compute and storage environment(s) based on the received trigger(s) and the mapping data and to the received triggers as requests via the local communication protocol to local data provider component(s) associated with the determined local identifier(s) for triggering generation of the digital asset and provision of the generated digital asset for access by the local data provider component(s) and / or to local data consumer component(s) associated with the determined local identifier(s) for triggering gathering of the generated digital asset(s) by the decentral consumer network node(s) connected to the local data consumer component(s).

Images