Raw Material and/or Recycling System

Abstract

A raw material and/or recycling system, including at least one tagging unit configured to provide at least one recyclable material element with at least one identifier. The system also includes at least one first peer-to-peer module assigned to the tagging unit and at least one peer-to-peer network having at least one peer-to-peer application. The first peer-to-peer module is configured to provide the provided identifier and at least one status parameter data set related to the recyclable material element to the peer-to-peer application. The peer-to-peer application includes at least one registering means executable upon provision of the provided identifier by at least a part of the nodes of the peer-to-peer network. The registering means is configured to register at least the recyclable material element by storing at least the provided identifier and the provided status parameter data set in at least one registry storage.

Claims

1. A raw material and/or recycling system, comprising: at least one tagging unit configured to provide at least one recyclable material element with at least one identifier, at least one first peer-to-peer module assigned to the tagging unit, at least one peer-to-peer network comprising at least one peer-to-peer application, wherein the first peer-to-peer module is configured to provide the provided identifier and at least one status parameter data set related to the recyclable material element to the peer-to-peer application, wherein the peer-to-peer application comprises at least one registering means executable upon provision of the provided identifier by at least a part of the nodes of the peer-to-peer network, wherein the registering means is configured to register at least the recyclable material element by storing at least the provided identifier and the provided status parameter data set in at least one registry storage and to monitor the registering process by executing the registering means by at least two nodes of the peer-to-peer network.

2. The system according to claim 1, wherein the tagging unit comprises at least one tagging tool configured to attach at least one readable code element comprising the identifier to the recyclable material element, and/or wherein the tagging unit comprises at least one status detecting tool configured to detect at least one status parameter related to the recyclable material element.

3. The system according to claim 1, wherein the system further comprises: at least one further recyclable material element processing unit, wherein the recyclable material element processing unit comprises at least one of a further status detecting tool and a reading tool configured to detect the identifier provided to the recyclable material element, and at least one further peer-to-peer module assigned to the further recyclable material element processing unit and configured to provide at least the detected identifier and at least one further status parameter data set to the peer-to-peer application.

4. The system according to claim 1, wherein the peer-to-peer application is configured to receive at least one treatment parameter data set related to the recyclable material element, wherein the registering means is further configured to store at least one treatment parameter data set related to the recyclable material element together with the identifier of the recyclable material element in the registry storage.

5. The system according to claim 4, wherein the system further comprises: at least one recycling unit comprising at least one recycling tool configured to process a provided recyclable material element during at least one recycling step, wherein a further peer-to-peer module assigned to the recycling unit is at least configured to receive the stored treatment parameter data set related to the recyclable material element from the peer-to-peer application, and wherein at least the recycling tool is configured to process the recyclable material element at least based on the received treatment parameter data set.

6. The system according to claim 1, wherein the system further comprises: at least one delivery unit comprising at least one dispensing tool configured to dispense at least one recyclable material element to at least one recipient, wherein the delivery unit comprises at least one recipient identifier detecting unit configured to detect at least one recipient identifier assigned to the recipient of the dispensed recyclable material element, wherein a further peer-to-peer module assigned to the delivery unit is at least configured to provide the recipient identifier and the identifier of the dispensed recyclable material element to the peer-to-peer application.

7. The system according to claim 6, wherein the peer-to-peer application is configured to generate a delivery transaction agreement about the delivery and/or return of a recyclable material element between a providing entity and the recipient at least based on the recipient identifier.

8. The system according to claim 7, wherein the generated delivery transaction agreement comprises at least the recipient identifier, the identifier of the recyclable material element and at least one delivery/return transaction criterion.

9. The system according to claim 8, wherein the system further comprises: at least one return unit comprising at least one receiving tool configured to receive at least one recyclable material element, wherein a further peer-to-peer module assigned to the return unit is at least configured to provide the identifier of the returned recyclable material element to the peer-to-peer application.

10. The system according to claim 9, wherein the peer-to-peer application comprises at least one accounting means, wherein the accounting means is executable upon provision of the provided identifier of the returned recyclable material element, and wherein the accounting means is at least configured to conduct an accounting process based on the provided identifier of the returned recyclable material element and at least one delivery transaction criterion stored in the delivery transaction agreement.

11. The system according to claim 1, wherein the peer-to-peer application is a decentralized register or a shared database, and wherein data is stored by the peer-to-peer application with given certain proofs or signatures.

12. The system according to claim 1, wherein the at least one peer-to-peer application is a block chain or decentral ledger comprising at least two blocks coupled to each other.

13. A recyclable material element processing unit for a raw material and/or recycling system, in particular, a raw material and/or recycling system according to claim 1, the unit comprising: at least one status detecting tool configured to detect at least one status parameter related to at least one recyclable material element, at least one reading tool configured to detect an identifier provided to the recyclable material element, and at least one peer-to-peer module configured to provide at least the detected identifier and at least one status parameter data set comprising at least the detected status parameter to at least one peer-to-peer application of at least one peer-to-peer network such that the identifier and the status parameter data set are stored in at least one registry storage by at least one registering means of the peer-to-peer application, wherein the registering means is executed by at least two nodes of the peer-to-peer network, wherein the registering process is monitored by executing the registering means by the two nodes.

14. A method for operating a raw material and/or recycling system, in particular, a raw material and/or recycling system according to claim 1, the method comprising: providing at least one recyclable material element, providing at least one identifier to the provided recyclable material element, and registering the recyclable material element by storing at least the provided identifier and the provided status parameter data set in at least one registry storage by means of at least one registering means of at least one peer-to-peer application of at least one peer-to-peer network, wherein the registering means is executed upon provision of the provided identifier by at least a part of the nodes of the peer-to-peer network, wherein the registering means is executed by at least two nodes of the peer-to-peer network, and wherein the registering process is monitored by executing the registering means by the two nodes.

15. A peer-to-peer application of at least one peer-to-peer network, comprising: at least one registering means configured to register at least one recyclable material element by storing at least one received identifier of the recyclable material element and at least one received status parameter data set related to the recyclable material element in at least one registry storage controlled by the peer-to-peer application, wherein the registering means is executed by at least two nodes of the peer-to-peer network, and wherein the registering process is monitored by executing the registering means by the two nodes.

Description

BRIEF DESCRIPTION OF THE DRAWING

[0088] In the figures:

[0089] FIG. 1 shows a schematic view of an embodiment of a raw material and/or recycling system according to prior art;

[0090] FIG. 2 shows a schematic view of a further embodiment of a raw material and/or recycling system according to the present application;

[0091] FIG. 3 shows a schematic view of a further embodiment of a raw material and/or recycling system according to the present application;

[0092] FIG. 4 shows a schematic view of an embodiment of a peer-to-peer application 424 according to the present application;

[0093] FIG. 5 shows a schematic view of a further embodiment of a raw material and/or recycling system according to the present application;

[0094] FIG. 6 shows a diagram of an embodiment of a method according to the present application; and

[0095] FIG. 7 shows a diagram of a further embodiment of a method according to the present application.

DETAILED DESCRIPTION

[0096] Like reference numerals in different figures indicate like elements.

[0097] FIG. 2 shows a schematic view of an embodiment of a raw material and/or recycling system 200 according to the present application. The system 200 comprises at least one recyclable material element processing unit 204 in form of a tagging unit 204. The tagging unit 204 is configured to provide a (unique) identifier to a recyclable material element 206. In particular, as can be seen from FIG. 2, the tagging unit 204 comprises a tagging tool 210 configured to attach a code element 216, such as an RFID transponder tag 216, a NFC transponder tag 216, a QR code 216, or a barcode 216, to a recyclable material element 206. The code element 216 can be read out by a reading tool of e.g. a further recyclable material element processing unit. For instance, if the identifier is stored in a memory of a code element 216 in form of a (passive) RFID transponder 216, the identifier can be read out by a RFID reader. The identifier may be also stored the peer-to-peer application or a further storage arrangement 226.

[0098] Furthermore, preferably the recyclable material element processing unit 204 comprises a status detecting tool 212 configured to detect at least one status parameter related to the (tagged) recyclable material element 206. For instance, the status detecting tool 212 can detect the successful attachment of a code element 216 to the recyclable material element 206. This detection may result in a changed status or condition of the recyclable material element, e.g. new, damaged, changed or unused.

[0099] Further status parameter(s) can be detected and/or stored in the peer-to-peer application 222 (or a further storage 226). Examples of status parameters are the (current) location of the code element 216, a time stamp, an identifier of the tagging unit 204, etc. For instance, the tagging unit 204 may be a stationary unit arranged at a known location (e.g. an address, geographic coordinates (e.g. GPS coordinates)). Then, as a location parameter the identifier of the tagging unit 204 (and a look-up table e.g. stored in the peer-to-peer application) may be sufficient to detect a location parameter. Alternatively or additionally, a tagging unit 204 may comprise a location sensor (e.g. GPS sensor). In particular, a mobile recyclable material element processing unit can be provided with such a sensor.

[0100] Preferably, one or more of these status parameters can be combined in a status parameter data set related to said recyclable material element 206.

[0101] It shall be understood that generally a status detecting tool may be a separate module or may be (implicitly) incorporated in another tool, such as a tagging tool. For instance, after a code element is successfully attached to a recyclable material element the status of the recyclable material element, e.g. new and/or unused, is (implicitly) detected by the tool, such as the tagging tool.

[0102] Preferably, at least a current status parameter data set can be additionally stored in the code element 216. For instance, the tagging tool 210 can be configured to store the respective data set into the code element 216. The code element 216 may be updatable. In other words, in each case a status change is detected, the respective current status parameter data set can be provided to the peer-to-peer application and, preferably, stored in the code element 216.

[0103] It shall be understood that the status parameters can be stored in the peer-to-peer application 222 (or a further storage 226). A status parameter release transaction agreement can be generated upon successful storage of status parameter(s) in the peer-to-peer application 222 (or a further storage 226) that was read out of a code element 216. For instance, the tagging tool 210 can be configured to control a data storage release process in the code element 216 upon receiving the status parameter release transaction agreement from the peer-to-peer application 222. This approach may ensure that the limited data storage size in a code element is used effectively.

[0104] Further, the system 200 comprises a peer-to-peer network 218. According to the depicted preferred embodiment of the present application, no central instance and/or third party organization is provided. In the present case, the system 200 comprises a so called peer-to-peer network 218 or a computer-computer network 218. The peer-to-peer network 218 comprises a plurality of nodes 220.1, 220.2, 220.3 (only three nodes are depicted for sake of clarity) and computers 220.1, 220.2, 220.3, respectively. A peer-to-peer network 218 is characterized in the present case in that each node 220.1, 220.2, 220.3 and/or participant 214 is preferably connectable at least to every other node 220.1, 220.2, 220.3 and/or participant 214. For instance, at least one physical standard network (wired and/or wireless) can be used for connection. For communicating via the at least one physical standard network suitable transceiver modules may be arranged in the respective entities/devices.

[0105] In addition, the computers 220.1, 220.2, 220.3 have equal rights, something which distinguishes them from a server-client structure.

[0106] The depicted nodes 220.1, 220.2, 220.3 (each) comprise a peer-to-peer application 222. As can be seen from FIG. 2, the same peer-to-peer application 222 is preferably implemented on each node 220.1, 220.2, 220.3. This means, in particular, that the same content is comprised on each node 220.1, 220.2, 220.3 and that the same code (including one or more executable means 224) can be executed on each node 220.1, 220.2, 220.3.

[0107] The peer-to-peer application 222 may preferably be a public register 222 that can, in particular, be inspected by all participants 220.1, 220.2, 220.3, 214 (not only the nodes 220.1, 220.2, 220.3) of the peer-to-peer network 218. Each of the 220.1, 220.2, 220.3 preferably has the (entire) public register 222. It may also be envisaged that only part of the register can be provided on a node (light node). In a particularly preferred embodiment, the peer-to-peer application 222 may be a block chain 222, which will be explained in more details hereinafter. It shall be understood that a peer-to-peer network may comprise further nodes. In addition, it shall be understood that also a recyclable material element processing unit can be formed as or comprise a node of the peer-to-peer network.

[0108] The peer-to-peer application 222 comprises a registering means 224, in particular, in form of a smart contract 224. The registering means 224 is configured to register one or more recyclable material element(s) 206 in the peer-to-peer application 222. In particular, the registering means 224 is configured to store the identifier of a recyclable material element 206 and a status parameter data set related to said recyclable material element 206. It shall be understood that a plurality of recyclable material elements 206 can be registered, as will be described hereinafter.

[0109] The peer-to-peer application 224 may be configured to manage and control the raw material and/or recycling system 200.

[0110] Further, a first peer-to-peer module 214 assigned to the recyclable material element processing unit 204 in form of a tagging unit 204 is provided. In the present example, the first peer-to-peer module 214 is integrated in the tagging unit 204, e.g. within a computing element of the tagging unit 204.

[0111] A peer-to-peer module 214 is (generally) configured to communicate at least with the peer-to-peer network 218, i.e. the nodes 220.1, 220.2, 220.3 of the peer-to-peer network 218. In other words, the first peer-to-peer module 214 or the tagging unit 204 corresponding or assigned to the respective peer-to-peer module 214 is at least a participant of the peer-to-peer network 218. Preferably, all participants 220.1, 220.2, 220.3, 214 (including all nodes) of the peer-to-peer network 218 are known to each participant 220.1, 220.2, 220.3, 214 of the peer-to-peer network 218.

[0112] In the present case, all peer-to-peer modules 214 are not nodes of the peer-to-peer network 218 but only a participant 214. While nodes 220.1, 220.2, 220.3 in the peer-to-peer network 218 comprise at least a part of the peer-to-peer application 222 itself, a participant of a peer-to-peer network 218, like the present peer-to-peer module 214, does not comprise the peer-to-peer application 222. Such a peer-to-peer module 214 is configured to provide (only) access to the peer-to-peer application 222 e.g. via an API (application programming interface). Each peer-to-peer module 214 (also a node or light node) may comprise a decentral application and at least an API.

[0113] In the case the peer-to-peer module is formed as a node of the peer-to-peer network the peer-to-peer module (also) comprises at least partly the peer-to-peer application. It shall be understood that a peer-to-peer module might be a node of the peer-to-peer network. It shall be understood that a peer-to-peer module may have access or may be connected to a gateway running a node of the peer-to-peer network (so called remote node).

[0114] The tagging tool 210 and/or the status detecting tool 212 may have a (internal) communication connection to the peer-to-peer module 214. For instance, after a code element 216 comprising an (unique) identifier is attached to the recyclable material element 206 and e.g. after one or more status parameter related to said recyclable material element 206 are detected, the identifier and/or e.g. one status parameter data set can be forwarded to the peer-to-peer module 214. The peer-to-peer module 214 is configured to provide the identifier and the status parameter data set related to the recyclable material element 206 to the peer-to-peer application 222 e.g. by sending one or more messages to the peer-to-peer application 222.

[0115] The reception of such a message may automatically cause the execution of the registering means 224 by a part (e.g. all nodes) 220.1, 220.2, 220.3 of the nodes 220.1, 220.2, 220.3.

[0116] Preferably, each message can be provided with a signature or the like. Prior to processing a message, a message can be validated by checking the signature of the message e.g. by comparing the signature with valid signatures stored e.g. in the peer-to-peer application. Preferably, a part 220.1, 220.2, 220.3 of the nodes 220.1, 220.2, 220.3 can conduct the validation process. Only in case of a positive result, e.g. in case of a match between the received signature and the stored signatures, a message may be further processed. It shall be understood that other means than signatures (e.g. communication addresses, certificates, etc.) can be used for a validation process or authentication process, respectively.

[0117] For instance, upon a positive authentication process, the registering means 224 is executed such that the received identifier and the status parameter data set is stored in a registry storage 229 in order to register the recyclable material element 206 in the system 200.

[0118] In the present case, an off-chain storage arrangement 226 comprises the registry storage 229. The off-chain storage arrangement 226 is controlled by the peer-to-peer application 222. In particular, the access to data stored in the storage arrangement 226 can be controlled/permitted by the peer-to-peer application 222 e.g. depending on access transaction agreement(s).

[0119] Preferably, the storage arrangement 226 comprising a plurality of decentral storage units 228 may be formed as a decentral file system (such as IPFS) or a decentral object store (such as storj) or a decentral distributed database (such as BigchainDB) controlled by the peer-to-peer application 222.

[0120] In a further embodiment an (not shown) analysis means may conduct processes e.g. by accessing the storage 226. Access can be granted based on an access transaction agreement controlled by the peer-to-peer application 222 (e.g. via a smart contract). The analysis means may be executable upon an analysis request message. The analysis means may comprise algorithm(s) for processing data stored in the storage 226.

[0121] In other embodiments, the peer-to-peer application can comprise a registry storage.

[0122] FIG. 3 shows a schematic view of a further embodiment of a raw material and/or recycling system 300. In the present example, the recyclable material element 306 is a container 306 e.g. in form of a bottle 306 or the like. The depicted recyclable material element processing units 304, 330, 332, 334, 336 are configured to process a container 306, as will be described hereinafter. However, the present embodiment can be easily transferred and e.g. adapted to any other kind of recyclable material elements and respective recyclable material element processing units needed to process said recyclable material elements.

[0123] The depicted system 300 comprises a peer-to-peer network 318 with a plurality of nodes 320.1, 320.2 (for sake of clarity, only two nodes are depicted). Each of the depicted nodes 320.1, 320.2 comprises a peer-to-peer application 322 having at least a registering means 324, as described hereinbefore.

[0124] Furthermore, the system 300 comprises a plurality of recyclable material element processing units 304, 330, 332, 334, 336. It shall be understood that there may be more or less recyclable material element processing units.

[0125] In the present embodiment, each of the recyclable material element processing units 304, 330, 332, 334, 336 comprises a peer-to-peer module 314.1, 314.2, 314.3, 314.4, 314.5 configured to communicate with the peer-to-peer application 322. It shall be understood that it is also possible that a peer-to-peer module is shared by two or more recyclable material element processing units and/or that a recyclable material element processing unit comprises two or more peer-to-peer modules. Preferably, each of the recyclable material element processing units 304, 330, 332, 334, 336 can comprise a (not shown for sake of clarity) reading tool, respectively, for detecting or reading out an identifier of a container 306 to 306.4.

[0126] Further, in the present embodiment, each of the recyclable material element processing units 304, 330, 332, 334, 336 comprises at least one status detecting tool 312, 333, 338, 344, 350. As described hereinbefore, a status detecting tool may be also (implicitly) integrated in another tool 331, 310, 338, 344, 350 of a respective recyclable material element processing unit 304, 330, 332, 334, 336.

[0127] A first recyclable material element processing unit 330 may be a production unit 330. The production unit 330 of a production entity (e.g. fabric) may comprise one or more producing tool(s) 331 configured to produce one or more container(s) 306. A produced container 306 can be forwarded to a further recyclable material element processing unit 304 in form of a tagging unit 304. It shall be understood that the tagging unit 304 can be part of the production unit 330 or of a filling system configured to fill the container with e.g. a liquid to be consumed.

[0128] As described above, the tagging unit 304 may comprise a tagging tool 310 configured to provide an identifier to a container 306.1, e.g. by attaching a code element 316 having the unique identifier to the container 306.1. Attaching can include integrating the coding element 316 in e.g. a wall or bottom of the container 306 or mounting the coding element 316 at a wall or bottom of the container 306 e.g. by gluing or the like.

[0129] The first peer-to-peer module 314.1 may provide the identifier and a first status parameter data set (e.g. used or unused, location, time-stamp, identifier of the tagging unit 304, etc.) to the peer-application 322. Then, the registering means 324 may be executed to register the container 306.1 by storing the received identifier and the first status parameter data set.

[0130] A further peer-to-peer module 314.2 to 314.5 may provide a further status parameter data set (e.g. newly produced, identifier of the production unit 330, identifier(s) of the used production tool(s), etc.) and, preferably, at least one treatment parameter data set to the peer-to-peer application 322. A treatment parameter data set can comprise information about the used starting material(s) of a produced container 306 (e.g. chemical formula of each starting material/ingredient and their respective portion (e.g. percent by weight)), decomposition rule(s), allowed decomposition physical, chemical or biological processes, treating rule(s) or parameter(s), such as maximum allowed (cleaning) temperature, allowed cleaning material(s), physical material storage or transportations rules (e.g. for sensible or dangerous materials), etc. The registering means 324 can associate the received data set to the respective container 306.1 by means of the identifier of the container 306.1 and can store said additional data together with the identifier in the registry storage e.g. formed by a storage arrangement 326, as described above.

[0131] It shall be understood that the tagging unit can be part of the production unit and production chain, respectively.

[0132] In the present embodiment, one or more container(s) 306.1, which might be filled with a liquid (e.g. water, beer, etc.), can be forwarded to a delivery unit 332 (e.g. using transport units).

[0133] The delivery unit 332, e.g. a shop or a beverage dispenser, may be configured to deliver/dispense a container 306.2 to a recipient 358, e.g. a user 358. Other recyclable material elements might be also dispensed to a machine. For instance, the delivery unit 332 comprises a dispensing tool 340 configured to dispense a container 306.2. Further, the delivery unit 332 comprises a recipient identifier detecting tool configured to detect an identifier assigned to a recipient 358 (byer). The identifier may be a ticket identifier of the recipient 358, an identifier of the recipient registered in the peer-to-peer application 322 (or a wallet ID), a credit card number or the like. Besides a current status parameter data set comprising, e.g. sold, identifier of the delivery unit 332, location of the delivery unit 332, time stamp and/or the identifier of the container 306.2, the identifier of the recipient 358 can be provided to the peer-to-peer application 322 and stored, as described hereinbefore. The identifier of the recipient 358 might be used for at least one accounting process, as will be described hereinafter.

[0134] Furthermore, an empty (and thus used/consumed) container 306.2 can be returned at a return unit 334, such as a shop or a return machine. In a preferred embodiment, the return unit 334 may be a (smart) waste bin 334. The return unit 334 can have a receiving tool 346 for receiving a container 306.2 and an optional recipient identifier detecting tool 348.

[0135] For instance, if the (used) container 306 is retuned using the receiving tool 346 the identifier of the returned container can be detected. The identifier of the returned container 306.3 can be provided from the peer-to-peer module 314.4 to the peer-to-peer application 322. For instance, upon receipt of an identifier of the returned container 306.3, a (not shown) accounting means can be executed by a part of the nodes 320.1, 320.2. The accounting means may be configured to conduct an accounting process e.g. based on the identifier of the returned container 306.3 and a corresponding delivery transaction agreement, as will be described hereinafter.

[0136] The status detecting tool 344 may be configured to detect whether the returned container comprises crack(s), dirt particle(s), weight of the container or other undesired element(s) or conditions or the like. The peer-to-peer module 314.4 is configured to transmit the previously described data to the peer-to-peer application 322. The registering means 324 may store said data in the registry storage of the storage arrangement 326, as described above. Algorithms can be run on top of the data stored in the storage arrangement 326. The current status parameter data set of a returned container 306.3 may be taken into account by an accounting means based on a stored delivery transaction agreement.

[0137] The returned container 306.3 can be forwarded to a recycling unit 336 (e.g. by transporting units). The recycling unit 336 may have one or more recycling tools 352. For instance, a recycling tool 352 may be a cleaning tool configured to clean a used/returned container 306.3. Preferably, the peer-to-peer module 314.5 is configured to receive a treatment parameter data set related to the container 306.3 to be cleaned. For instance, a reading tool of the recycling unit 336 can detect the identifier of the container 306.3 to be cleaned. The detected identifier can be provided to the peer-to-peer application 322 by sending a treatment parameter request message by the peer-to-peer module 314.5. The peer-to-peer application 322 may comprise a (not shown) retrieving means configured to retrieve the treatment parameter data set stored in the registry storage and corresponding to the received identifier. Then, the retrieved treatment parameter data set can be provided to the requesting peer-to-peer module 314.5.

[0138] In a further embodiment the recycling unit 336 may store recycling and treatment process data sets about the recycling process or recycling tool activities in the peer-to-peer application 322 (e.g. material input parameters, treatment parameters, material output parameters). The recycling and treatment process data sets can be used for reporting purposes, optimization purposes or for analytical purposes.

[0139] It shall be understood that a recycling unit may have one or more (different) recycling tool(s).

[0140] Then, the recycling tool 352 can be (automatically) operated at least based on the received treatment parameter data set e.g. comprising allowed (and/or optimal) cleaning agent(s), maximum allowed (and/or optimal) cleaning temperature, or any other physical, chemical, biological treatment rules, etc.

[0141] Another example of a recycling tool 352 may be a tool for regaining the used starting materials 354 from the used container 306.3 e.g. by a heating and sorting process. Such a tool may (also) be operated at least based on the received treatment parameter data set e.g. comprising the originally used starting material, weighting specifications (e.g. percent by weight), etc.

[0142] Status parameter data, such as cleaned, location, time stamp, identifier of the unit and/or tool(s), etc. can be forwarded to the peer-to-peer application 322 by the peer-to-peer module 314.5 and stored, as described hereinbefore. A cleaned container 306.4 can e.g. be forwarded to the tagging unit e.g. in order to re-register the container 306.4 or to a filling station (then the same code element and identifier, respectively, can be maintained). A regained starting material 354 can e.g. be forwarded to the production unit 330 in order to produce a new container 306.

[0143] Furthermore, an entity 358, 356 can get access to data stored in the registry storage. The access to the data can be controlled by the peer-to-peer application 322. For instance, a computing entity 356 (e.g. a mobile phone 356) comprising a peer-to-peer module 314.6 can send an access request message comprising e.g. a recipient identifier and/or a container identifier. Based on the received identifier(s) and e.g. based on predefined access rule(s), the peer-to-peer application 322 (e.g. by means of an access means) may allow or deny access to the desired data which might be also specified in the access request. Thereby, a user (e.g. customer) 358 can track the way (e.g. life cycle) of the container e.g. used by him from the production to recycling of said container.

[0144] It shall be understood that there may be several intermediate units, such as transport units, storage units and the like. In a preferred embodiment, also these units can comprise a peer-to-peer module and one or more status detecting tool(s), in particular, configured to detect one or more current status parameter(s) of the container(s). The respective peer-to-peer modules may be configured to transmit the respective status parameter data sets and the respective (read out) identifier(s) of the container(s) to the peer-to-peer application 322 in order to log this data in the registry storage by the registering means 324.

[0145] FIG. 4 shows a schematic view of an embodiment of a peer-to-peer application 422 according to the present application.

[0146] The depicted peer-to-peer application 422 is a register readable, in particular, by the participants of the peer-to-peer network. Thereby, data set(s) e.g. in form of messages can be written and/or read into/from the register 422 by a peer-to-peer module assigned to a recyclable material element processing unit and/or any other participants in the peer-to-peer network. In a preferred embodiment, the peer-to-peer application 422 may be a block chain 422.

[0147] Hereinafter, it is assumed in the following description of the present embodiment that the at least one peer-to-peer application 422 is a block chain 422. However, the following remarks can be easily transferred to other peer-to-peer applications, such as a Directed Acyclic Graph (DAG). A directed acyclic graph, such as IOTA or Tangle, means that blocks (or nodes of the graph) are coupled to each other via directed edges. Thereby, direct means that the (all) edges have (always) a same direction similar to time. In other words, it is not possible to step back. Eventually, acyclic means that loops do not exist.

[0148] In further embodiments of the peer-to-peer application, the block chain can be a permissionless or permissioned block chain. In a specific case the block chain can be public, consortium or private block chain.

[0149] In a further embodiment, the peer-to-peer application can be formed with multiple block chains which are connected via mechanisms, such as side chains or smart contracts. Interoperability among block chains can be established.

[0150] The block chain 422 is formed by at least one block 451, 453, 455, preferably by a plurality of interconnected blocks 451, 453, 455. The first block 451 may also be called genesis block 451. As can be seen, a block 453, 455 (except for the first block 451) refers to each previous block 451, 453. A new block can be created by a computationally intensive process (for example, so called mining or through another appropriate process, such as voting) and will be particularly provided to all participants of the peer-to-peer network.

[0151] The present block chain 422 is particularly adapted to receive messages, such as messages comprising an identifier (provided to a recyclable material element or detected from a recyclable material element) and/or status parameter data set(s), treatment parameter data set(s), authentication result(s), etc., from a peer-to-peer module of a previously described recyclable material element processing unit, (off-chain) computing entity or from another peer-to-peer device/unit of another participant of the peer-to-peer network. Further, the block chain 422 is particularly adapted to save these messages in the block chain 422. Furthermore, the block chain 422 is configured to generate messages e.g. based on a registering process, accounting process, retrieving process and/or caused by a peer-to-peer module and/or the execution of code of e.g. a registering means 466, an accounting means 468, etc. In particular, the block chain 422 is at least configured to control and manage a raw material and/or recycling system, such as shown in FIG. 2 or 3.

[0152] In particular, a (newly) received message can be saved and published in the current block 455 of the block chain 424. Due to the configuration of a block chain 424 as a public register 424, said data message of e.g. a peer-to-peer module can be read by preferably all participants of the peer-to-peer network. Alternatively or additionally, data of a message may be stored in a registry storage e.g. on a decentral file service or distributed block chain database controlled by the block chain 422.

[0153] As already described, in the present block chain 422 different types of messages and data sets, respectively, for example, within a smart contract (algorithm and/or storage at the block chain 422) can be processed and/or stored. In the present example, the block chain 422 comprises a registering means 466 in form of a smart contract 466. As previously described, the registering means 466 may be configured to at least register at least one recyclable material element in the raw material and/or recycling system.

[0154] Furthermore, in the block chain 422 one or more delivery transaction agreement(s) 470 may be stored. A delivery transaction agreement 470 may be generated between at least one provider of a recyclable material element and a recipient of the recyclable material element in order to define and store the details about the dispense, use and/or return of a (used) recyclable material element. An example of a generation of such a delivery transaction agreement 470 will be described in the following:

[0155] A delivery transaction agreement 470 may comprise at least one of the following data: [0156] Identifier(s): Identifier of the dispensed recyclable material element; identifier of the recipient; identifier of a provider. [0157] Delivery/return transaction criterion(s): Criterion(s) that must be fulfilled for allowing a dispense of a recyclable material element (e.g. deposit, consumption fee) or for a return of a deposit (e.g. a specific status parameter data set of the returned recyclable material element). [0158] Operating detail(s): Detail(s) about delivery and/or return, such as return time, return location, etc.

[0159] The delivery transaction criterion may be an amount of cryptocurrency for a temporarily use/consumption of a recyclable material element, an use/consumption e.g. of a content (e.g. beverage) of a recyclable material element or the like. Another delivery transaction criterion may be a deposit for the use of the recyclable material element. Another delivery transaction criterion may be a specific status parameter data set of the returned recyclable material element. It may be possible that an amount has to be transferred prior to, during and/or after the use/consumption.

[0160] Preferably, at least a part of the said amount of cryptocurrency can be locked by the peer-to-peer application 422 prior to dispensing a recyclable material element e.g. as a deposit. In an embodiment, the delivery transaction criterion may be a payment channel for streaming small amounts of crypto tokens per each time and/or data unit. It shall be understood that other transaction criteria and further information can be included in an delivery transaction agreement. More information/criteria can be, for example, a time stamp, an ID of the transaction and the like.

[0161] In order to generate a delivery transaction agreement 470, a peer-to-peer module of a delivery unit can transmit a request message 472 to the peer-to-peer application comprising an identifier of a recyclable material element to be dispensed and a recipient identifier. The peer-to-peer application 422 (e.g. according to predefined rule(s)) or a peer-to-peer module of a provider of the recyclable material element and/or the content of the recyclable material element can transmit a response (acceptance) messages via the peer-to-peer application 422. A request message 472 may comprise indications about the above data (identifications, delivery/return transaction criteria, etc.). Prior to generating a delivery transaction agreement 470, an authentication process for checking the authentication of the recipient can be conducted. After a positive result, the process for generating the agreement 470 can be continued.

[0162] Another message 474 may be an acceptance message 474 of e.g. a provider or peer-to-peer application. An acceptance message 474 may comprise identical or at least similar data details as compared with a request message 472. Additionally, the acceptance message 474 can comprise a reference indication to a previous message, such as the ID of the message 472. The acceptance message 474 can be provided by a peer-to-peer module of a provider or by the peer-to-peer application (e.g. according to preset rules).

[0163] If, for example, the acceptance message 474 comprises a higher or other further transaction criterion and/or other desired operational detail(s), the acceptance message 474 can be called a counter-offer message. This can be accepted by the peer-to-peer module of the dispensing unit (e.g. after a further inquiry) through an acceptance message.

[0164] A further message can an analysis request message 478 to get access to data stored in a storage arrangement 476. Analysis requests messages can be checked against registered units with the respective access rights to access data in a storage arrangement.

[0165] In particular, there can be multiple request messages and/or accepting messages. Each entity (recipient) and unit can give guidelines, according to which at least one delivery transaction agreement 470 or other agreements can be generated. In a preferably automated, such as iterative process, each request/offer message can be associated to an optimally corresponding acceptance message. The block chain 422 may be configured to generate, based on the messages of a peer-to-peer module, a delivery transaction agreement 470.

[0166] Moreover, a block chain 422 may comprise a further registering means (not shown) configured to register a (new) entity, recyclable material element processing unit, recipient, etc. in the block chain 422 as a smart asset.

[0167] FIG. 5 shows a schematic view of a further embodiment of a system 500 of the present application. In the present embodiment, only nodes and participants 504.1, 504.2, 520.1, 520.2, 536.1, 536.2 of the peer-to-peer network 518 are shown. In the present example, it is assumed that all nodes participants 504.1, 504.2, 520.1, 520.2, 536.1, 536.2 comprise the peer-to-peer application (not shown).

[0168] The nodes 504.1, 504.2 may correspond to tagging units and e.g. be formed by the respective first peer-to-peer modules of tagging units. The nodes 536.1, 536.2 may correspond to recycling units and e.g. be formed by the respective peer-to-peer modules of recycling units. Nodes 520.1 and 520.2 may be other nodes. It shall be understood that nodes can be full, remote or light nodes.

[0169] As can be seen, two different types of peers or node computers 504.1, 504.2, 520.1, 520.2, 536.1, 536.2 are presently illustrated. All 504.1, 504.2, 520.1, 520.2, 536.1, 536.2 are comprised by the peer-to-peer network 518. In the present embodiment, however, only a part of the nodes 504.1, 504.2, 520.1, 520.2, 536.1, 536.2 in the present case, the peers (nodes) 504.1, 536.1, 520.1 may execute a registering means and may check the validity of e.g. a message received by the peer-to-peer-application and/or the validity of further data stored in the peer-to-peer application, such as agreements, status parameter data set(s), and the like.

[0170] Furthermore, only a part of the entire peers can be configured to store the peer-to-peer application and/or only a part of the peers can be configured to execute the algorithms of a smart/private contract. Since the validation/verification of e.g. identification data requires a considerable computational effort, it may be advantageous for reasons of efficiency, if only a part of the nodes 504.1, 536.1, 520.1, especially particularly powerful nodes 504.1, 536.1, 520.1 perform the execution of executable means and/or validation algorithm(s) and/or authentication algorithm(s).

[0171] Validation, analytics and optimization can be done on-chain or off-chain, as described hereinbefore. Off-chain validation, analysis and/or optimization can be managed by the peer-to-peer application, like the code on the block chain. Powerful means, in particular, a high computing power. In other words, in the present case a valid entry in the peer-to-peer application, such as a block chain, is assumed if (only) a part of the peers 504.1, 536.1, 520.1 comes to a positive result. It shall be understood that only a single, especially particularly powerful peer can perform the validation, analytics and/or optimization process while further nodes may be configured as monitoring nodes.

[0172] Similarly, in a further (not shown) embodiment, a particularly large peer-to-peer network may be divided in two or more clusters. In a corresponding peer-to-peer network, for example, a validation will only be carried out by the members of one cluster (e.g. sharding of a block chain to improve the scalability). In a further embodiment, the peer-to-peer application can be formed using multiple block chains. These block chains are connected via frameworks such as sidechains or smart contracts or interlegder.

[0173] FIG. 6 shows a diagram of an embodiment of a method according to the present application. The method can be used e.g. for operating a previously described system 200, 300 or 500.

[0174] In a first step 601, an (unique) identifier is provided to a recyclable material element. Preferably, a code element comprising said identifier is attached to the recyclable material element. It may be also possible that an identifier is written into a memory of an already attached code element or the identifier may be generated by a crypto ID chip of a code element and written into the peer-to-peer application. It may be also possible that a (second) identifier and a digital product memory may be set-up in the peer-to-peer application. Identifier in the code element and in the peer-to-peer application might be mapped via the registry storage. The identifier can be provided to the peer-to-peer application by means of a first peer-to-peer module. Then, in step 602, at least one status parameter can be at least implicitly detected. The detected status parameter can be provided to the peer-to-peer application e.g. by sending a status parameter data set comprising at least said detected status parameter. Steps 601 and 602 may be conducted at least partly in parallel.

[0175] Further, in step 603, the recyclable material element is registered in the peer-to-peer application and system, respectively. In particular, the peer-to-peer application may comprise at least one registering means executable by at least a part (e.g. >1) of the nodes of the peer-to-peer application. By executing the registering means, at least the provided identifier and the provided status parameter data set are stored in at least one (updateable and/or inspectable) registry storage at least controlled by the peer-to-peer application.

[0176] FIG. 7 shows a diagram of a further embodiment of a method according to the present application. The method can be used e.g. for operating a previously described system 200, 300 or 500.

[0177] In a first step, a delivery or dispense of a recyclable material element, e.g. a container having a specific content, can be detected and registered by means of the peer-to-peer application. For instance, the peer-to-peer application can receive a message from a delivery unit, wherein the message comprises at least one of: [0178] identifier of the delivered recyclable material element, [0179] identifier of the recipient of the delivered recyclable material element.

[0180] Further data, such as status parameter(s), can be included in the message.

[0181] In step 702, an accounting process can be conducted. For instance, the peer-to-peer application can comprise at least one accounting means. For instance, the accounting process can be conducted based on a delivery transaction agreement comprising e.g. two delivery/return transaction criterions (e.g. a price for (temporarily) using the recyclable material element or consuming e.g. its content and a deposit for the recyclable material element).

[0182] While during the accounting process the first amount of e.g. cryptocurrency can be transferred from an account of the recipient (at least based on the received recipient identifier) to an account of the provider of the recyclable material element (e.g. based on the received identifier of the recyclable material element), a deposit in form of cryptocurrency can be merely locked by the accounting means. It shall be understood that the deposit can also be transferred. In an embodiment, the at least one transaction criterion may be a payment channel for streaming small amounts of crypto tokens per each time and/or data unit. It shall be understood that other transaction criteria and further information can be included in a delivery transaction agreement. More information/criteria can be, for example, a time stamp, an ID of the transaction and the like.

[0183] In step 703, a return of the recyclable material element can be detected and registered by means of the peer-to-peer application. For instance, a return unit, such as a smart bin, can detect an identifier of a returned recyclable material element. The return unit can transmit a message to the peer-to-peer application, wherein the message comprises at least the identifier and an information about the return of the recyclable material element. Further data, such as status parameter(s), can be included in the message. Upon receipt of such a message, the registering means can detect and register the return of the recyclable material element, as described above.

[0184] In step 704, a further accounting process can be conducted. In particular, according to a delivery transaction agreement comprising a transaction criterion in form of a deposit, the deposit can be unlocked and/or retransferred to the account of the recipient. In order to determine the correct recipient, based on the received identifier of the recyclable material element, the recipient identifier (and e.g. its account data) can be retrieved from the registry storage.

[0185] It may be possible that the full deposit is only returned if the status of the returned recyclable material element meets predefined requirement(s). Otherwise, only a part or none of the deposit might be returned.

[0186] It may also be possible to run analytical algorithms on the data stored in the peer-to-peer application at any process step.

[0187] All references, including publications, patent applications, and patents cited herein are hereby incorporated by reference to the same extent as if each reference were individually and specifically indicated to be incorporated by reference and were set forth in its entirety herein.

[0188] The use of the terms a and an and the and similar referents in the context of describing the invention (especially in the context of the following claims) is to be construed to cover both the singular and the plural, unless otherwise indicated herein or clearly contradicted by context. The terms comprising, having, including, and containing are to be construed as open-ended terms (i.e., meaning including, but not limited to,) unless otherwise noted. Recitation of ranges of values herein are merely intended to serve as a shorthand method of referring individually to each separate value falling within the range, unless otherwise indicated herein, and each separate value is incorporated into the specification as if it were individually recited herein. All methods described herein can be performed in any suitable order unless otherwise indicated herein or otherwise clearly contradicted by context. The use of any and all examples, or exemplary language (e.g., such as) provided herein, is intended merely to better illuminate the invention and does not pose a limitation on the scope of the invention unless otherwise claimed. No language in the specification should be construed as indicating any non-claimed element as essential to the practice of the invention.

[0189] Preferred embodiments of this invention are described herein, including the best mode known to the inventors for carrying out the invention. Variations of those preferred embodiments may become apparent to those of ordinary skill in the art upon reading the foregoing description. The inventors expect skilled artisans to employ such variations as appropriate, and the inventors intend for the invention to be practiced otherwise than as specifically described herein. Accordingly, this invention includes all modifications and equivalents of the subject matter recited in the claims appended hereto as permitted by applicable law. Moreover, any combination of the above-described elements in all possible variations thereof is encompassed by the invention unless otherwise indicated herein or otherwise clearly contradicted by context.