Method and system for manufacturing products packaged with packaging materials

Abstract

To provide a manufacturing technique of a commodity product which allows a purchaser of a commodity product to obtain a token in a blockchain by utilizing a package of the commodity product.SOLUTION: A disclosed method is a manufacturing method of a commodity product packaged by a packaging material and includes the steps of: preparing a commodity product body packaged by the packaging material; preparing the packaging material; and packaging the commodity product body by the packaging material. The step of preparing the packaging material comprises the steps of: generating a unique code for each commodity product; storing the code in a storage device for a printing system of the packaging material and storing the code in a token distribution system as a registered code; printing the code stored in the storage device on the packaging material by the printing system; and packaging the commodity product body by the packaging material. The token distribution system is configured to transmit the token in the blockchain to the code transmission source when receiving a reception code that is the same as the registered code from the code transmission source via the network.SELECTED DRAWING: Figure 3

Description

Technical Field

[0001] The present disclosure relates to a method and a manufacturing system for manufacturing a product packaged with a packaging material.

Background Art

[0002] Patent Document 1 discloses a heating device for a shrink film as a packaging material for a product. The shrink film is a film having heat shrinkability formed of polyethylene, polypropylene, PVC, or the like. The shrink film is heated while being attached to an object to be packaged and shrinks to adhere to the object. Thereby, the packaging of the product is easily and firmly performed. The object is, for example, a product body packaged with a shrink label or a container (other packaging material) in which a product body such as a liquid is contained. Since the shrink film is also used as a label for a product, it may be called a shrink label.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

[0004] Now, the inventors have obtained an idea of increasing the added value of a product by enabling a purchaser of the product to obtain a token in a blockchain. However, a technology for manufacturing a product so that a purchaser of a product, which is an object in the real world, can obtain a digital asset called a token in the digital world of a blockchain has not yet been proposed. Therefore, a manufacturing technology for a product that enables a purchaser of the product to obtain a token in a blockchain is desired.

[0005] To solve the above problems, the inventors focused on product packaging. Specifically, one of the objectives of the present invention is to provide a product manufacturing technology that utilizes product packaging to enable product purchasers to obtain tokens on the blockchain.

[0006] One aspect of this disclosure is a method for manufacturing a product packaged by a packaging material. The method of disclosure comprises the steps of preparing a product body to be packaged by the packaging material, preparing the packaging material, and packaging the product body with the packaging material, wherein the step of preparing the packaging material comprises the steps of generating a unique code for the product, storing the code in a storage device for a printing system for the packaging material and storing it in a token distribution system as a registered code, printing the code stored in the storage device onto the packaging material using the printing system, and packaging the product body with the packaging material, wherein the token distribution system is configured to send a token in the blockchain to the code sender when it receives a receiving code identical to the registered code from a code sender via a network.

[0007] Another aspect of this disclosure is a manufacturing system for products packaged by packaging material. The system of the disclosure comprises means for generating a unique code for each individual product; a storage device for storing the code as a printable code; a token distribution system for storing the code as a registered code; means for printing the code stored in the storage device onto packaging material; and means for manufacturing packaged products by packaging them with the packaging material on which the code has been printed. The token distribution system, on which the registered code is stored, is configured to send a token in the blockchain to the code sender when it receives a receiving code identical to the registered code from a code sender via the network.

[0008] Further details will be described in the embodiments below. [Brief explanation of the drawing]

[0009] [Figure 1] Figure 1 is an overview diagram of the product manufacturing equipment and token distribution system. [Figure 2] Figure 2 shows the manufacturing process, including the printing process. [Figure 3] Figure 3 is a flowchart showing the product manufacturing procedure. [Figure 4] Figure 4 is an overview diagram of code generation, transmission, reception, and storage. [Figure 5] Figure 5 is an explanatory diagram of URI generation. [Figure 6] Figure 6 is a flowchart showing the token distribution procedure. [Figure 7] Figure 7 is an explanatory diagram of token distribution using smart contracts. [Figure 8] Figure 8 is a schematic diagram showing an example of shrink film. [Figure 9] Figure 9 is a schematic diagram showing an example of shrink film. [Figure 10] Figure 10A is a plan view showing an example of shrink film. Figure 10B is a cross-sectional view of shrink film attached to a container. [Figure 11] Figure 11A is a perspective view of the shrink film. Figure 11B is a perspective view of the shrink film after it has been removed from the container. [Figure 12] Figure 12A is a plan view showing an example of shrink film. Figure 12B is a longitudinal cross-sectional view of shrink film attached to a container. [Figure 13] Figure 13 is a schematic diagram showing the state of the cap area after removal. [Figure 14] Figure 14 is a schematic diagram of a container with a cap and a two-dimensional code. [Figure 15] Figure 15 is a schematic diagram of shrink film with a backing card. [Figure 16] Figure 16 is a schematic diagram of a product in which the container is fixed to a backing card via shrink film. [Modes for carrying out the invention]

[0010] <1. Overview of the manufacturing method and manufacturing system for products packaged with packaging materials>

[0011] (1) An embodiment of the method is a method for manufacturing a product packaged with packaging material, comprising: a step of preparing a product body to be packaged with packaging material; a step of preparing the packaging material; and a step of packaging the product body with the packaging material, wherein the step of preparing the packaging material comprises: a step of generating a unique code for the product; a step of storing the code in a storage device for a printing system of the packaging material and storing it in a token distribution system as a registered code; a step of printing the code stored in the storage device onto the packaging material using the printing system; and a step of packaging the product body with the packaging material, wherein the token distribution system is configured to send a token in the blockchain to the code sender when it receives a receiving code identical to the registered code from a code sender via the network.

[0012] (2) Preferably the code is positioned so that it is not visible in the product when it is packaged with the packaging material, but becomes visible when at least a part of the packaging is removed by the packaging material.

[0013] (3) The token may be a non-fungible token associated with the registered code in the token distribution system. Preferably, the token distribution system is configured to send the non-fungible token associated with the same registered code as the received code to the code sender.

[0014] (4) The token distribution system preferably determines whether the received code is the same as the registered code, determines the token to be transmitted when the received code is the same as the registered code, and is configured to transmit the determined token to the code sender.

[0015] (5) The token distribution system preferably determines whether the received code is the same as the registered code, generates a non-fungible token as the token to be transmitted when the received code is the same as the registered code, and is configured to transmit the generated non-fungible token to the code sender.

[0016] (6) The token distribution system preferably determines whether the received code is the same as the registered code, determines the quantity of fungible tokens corresponding to the received code as the token to be transmitted when the received code is the same as the registered code, and is configured to transmit the determined quantity of fungible tokens to the code sender.

[0017] (7) The system according to the embodiment is a manufacturing system for products packaged by a packaging material, and includes means for generating a unique code for each individual product, a storage device for storing the code as a printing code, a token distribution system for storing the code as a registered code, means for printing the code on the packaging material, and means for manufacturing a packaged product by packaging with the packaging material on which the code is printed. The token distribution system in which the registered code is stored is configured to transmit a token in a blockchain to the code sender when receiving a received code identical to the registered code from a code sender via a network.

[0018] (8) The token is preferably a non-fungible token or a fungible token.

[0019] <2. Examples of manufacturing methods and manufacturing systems for products packaged with packaging materials>

[0020] Figure 1 shows a manufacturing system according to an embodiment. The manufacturing system according to the embodiment comprises a product manufacturing facility 609 and a token distribution system 10. The product manufacturing facility 609 is equipment that manufactures products to be sold to consumers, etc. The product manufacturing facility 609 works in conjunction with the token distribution system 10 to manufacture products from which purchasers can obtain tokens.

[0021] The product according to this embodiment is packaged by packaging material. Here, the object packaged by the packaging material is referred to as the product itself. The product itself is something that is consumed or used by the purchaser. The product itself is, for example, food, beverages, confectionery, seasonings, alcohol, cosmetics, or medicine. The packaging material is a component for housing the product itself or wrapping the product itself. The packaging material is used, for example, to decorate the product, to provide necessary labeling, to protect the product, or to provide additional functions. The packaging material can be separated from the product itself when the product is consumed or used. The packaging material becomes unnecessary once the product itself is consumed or used. Once the product itself is consumed or used, the packaging material is collected for recycling or disposed of as waste.

[0022] The packaging material may be a container. The container is suitable for, for example, storing the liquid product itself. The container may be, for example, a PET bottle or other plastic container, a paper container, a glass container, or a metal container. The packaging material may wrap the product itself with plastic film or paper. Alternatively, the packaging material may wrap the container containing the product itself. In other words, the packaging material may consist of a first packaging material which is a container and a second packaging material which wraps the container.

[0023] Packaging materials may include accessories. Accessories are, for example, seals affixed to the packaging materials. Accessories may also include items attached to the packaging materials by means other than adhesive.

[0024] In this embodiment, a code used by the purchaser of a product to obtain tokens on the blockchain is affixed to the packaging. Hereinafter, the code affixed to the product may also be referred to as the token code or unique code. The token code is used for token distribution by the token distribution system 10. The token code is, for example, a multi-digit code consisting of numbers, letters, or symbols. The token code is affixed to the packaging in a machine-readable format, for example. A machine-readable format is, for example, a two-dimensional code or a barcode. Preferably, the code affixed to the product is different for each product so that only the purchaser of the product can obtain tokens. Packaging is suitable for affixing token codes because it is possible to affix different codes to each product by printing. Also, since packaging is generally printed, a printing system 610 for packaging can be used to affix token codes.

[0025] In the following example, packaging materials will consist of a container in which the product is placed (first packaging material) and a shrink film attached to the container (second packaging material). The container will be a PET bottle, for example. The shrink film used here will be a shrink label. A shrink label is a shrink film with the label content printed on it, and it can be used to add a desired design to a plain container such as a transparent PET bottle. In the following example, the token code will be attached to the shrink film (label).

[0026] For the purpose of recycling the container after the product (e.g., beverage) inside has been consumed, it is desirable that the container and the label, such as shrink film, be separated. Therefore, consumers are required to remove the label from the container. As an example, in one embodiment, in order to encourage consumers to remove the label, such as shrink film, from the container, the product is configured such that when the label is removed, a token code is revealed and the token becomes available. With this configuration, consumers who wish to obtain the token are expected to actively remove the label, such as shrink film, from the container.

[0027] The product manufacturing equipment 609 shown in Figure 1 may include a printing system 610. The printing system 610 prints on the shrink film, which is the second packaging material. The product manufacturing equipment 609 may also include a product body manufacturing device 620 and a bottling system 621. The product body manufacturing device 60 is a food manufacturing device if the product body is food, and a beverage manufacturing device if the product body is a beverage. The manufacturing device 620 may be equipped with appropriate equipment depending on the product body to be manufactured. The bottling system 621 is a device for putting the manufactured product body into a container, and more specifically, for example, a device for filling a container with a liquid product body.

[0028] Product manufacturing equipment 609 may be equipped with a shrink wrap device 622. The shrink wrap device 622 is a device that applies shrink film (shrink label) to a container by heating. When heated, the shrink film shrinks and adheres tightly to the container. Note that the label is not limited to a shrink label, but may be a stretch label or a roll label. The label may also be a seal label that is affixed to the container. In other words, the shrink wrap device 622 may be any other type of label application device. Note that the shrink wrap device 622 is a type of label application device. The shrink wrap device 622 can also be said to be a type of packaging device. The shrink wrap device 622 can also be said to be a type of equipment for manufacturing packaged products.

[0029] The printing system 610 provided in the product manufacturing equipment 609 forms printed shrink labels by, for example, printing labels onto a transparent, plain shrink film body. The printing system 610 is also used for printing token codes. The printing system 610 shown in Figure 1 comprises a print management device 611 connected to a network 15 and a printing device 613 connected to the print management device 611. The printing device 613 may also be connected to the print management device 611 via the network 15. The printing device 613 is, for example, a digital printing device. Digital printing does not require printing plates as required in offset printing, etc., and is therefore suitable for printing a large number of non-identical printed materials, such as labels, each with a different token code. More specifically, the printing device 613 is, for example, a laser printer or an inkjet printer.

[0030] The print management device 611 is connected to the token distribution system 10 via a network 15 such as the Internet. The print management device 611 may be composed of a computer comprising a processor 611A and a storage device 611B. The storage device 611B is connected to the processor 611A. The storage device 611B comprises, for example, a primary storage device and a secondary storage device. The primary storage device is, for example, RAM. The secondary storage device is, for example, a hard disk drive (HDD) or a solid-state drive (SSD). The storage device 611B contains a computer program 611C executed by the processor 611A. The processor 611A reads and executes the computer program 611C stored in the storage device 611B. The computer program 611C has program code that indicates instructions to be executed by the computer functioning as the print management device 611.

[0031] The print management device 611 is connected to the print device 613 via interface 611E. The computer program 611C is configured to cause the computer to execute, for example, a process for label printing (print process 611D). When the print process is executed, the print device 613 performs printing. This printing imparts a design and a token code to the film itself.

[0032] As described above, the token distribution system 10 is connected to the printing system 610 via the network 15. The printing system 610 according to this embodiment works in cooperation with the token distribution system 10 to execute the printing process 611D. The token distribution system 10 is also configured in cooperation with the printing system 610 to distribute tokens to product purchasers using the token codes printed by the printing system 610.

[0033] The token distribution system 10 of the embodiment may include a server 51. Furthermore, the token distribution system 10 of the embodiment may include a smart contract 22.

[0034] The server 51 may be composed of a computer comprising a processor 51A and a storage device 51B. The storage device 51B is connected to the processor 51A. The storage device 51B comprises, for example, a primary storage device and a secondary storage device. The primary storage device is, for example, RAM. The secondary storage device is, for example, a hard disk drive (HDD) or a solid-state drive (SSD). The storage device 51B contains a computer program 51C executed by the processor 51A. The processor 51A reads and executes the computer program 51C stored in the storage device 51B. The computer program 51C has program code that indicates instructions to cause the computer to execute a process for distributing tokens (distribution process 51D).

[0035] In this embodiment, the tokens distributed by the token distribution system 10 are tokens on the blockchain 20. On the blockchain 20, tokens can be traded (sent and received) between accounts (blockchain addresses). Token transaction records are recorded on the distributed ledger of the blockchain 20. Tokens that can be traded on the blockchain 20 include fungible tokens (FTs) and non-fungible tokens (NFTs). A fungible token is, for example, a cryptocurrency such as Ether in Ethereum. A fungible token may also be a proprietary fungible token issued on the blockchain by a company or individual.

[0036] Non-fungible tokens (NFTs), unlike fungible tokens (FTs), are tokens that do not possess fungibility. To ensure non-fungibility, NFTs have a unique identifier on Blockchain 20 that allows them to be distinguished from other NFTs. Hereafter, this identifier will be referred to as the NFT identifier.

[0037] Blockchain 20 may include smart contracts 22. Smart contracts 22 consist of software (computer programs) implemented in a way that makes them executable on the blockchain. Smart contracts 22 automatically execute predetermined protocols, such as automated transactions.

[0038] Smart contract 22 may work with server 51 to perform the process for distributing tokens. Alternatively, smart contract 22 may perform the process for distributing tokens without working with server 51. In other words, token distribution may be performed by server 51, by smart contract 22, or through the cooperation of server 51 and smart contract 22. Below, we will describe an example in which smart contract 22 works with server 51 to distribute tokens. In this example, server 51, which receives a token code sent by the purchaser of a product for the purpose of token distribution, calls smart contract 22, and the called smart contract 22 sends the tokens to the recipient (the purchaser of the product; the sender of the token code).

[0039] Figures 2 and 3 show an example of the procedure for manufacturing a product using the manufacturing system according to the embodiment. For product manufacturing, the product body is prepared (step S31) and the packaging materials are prepared (steps S32, S33). Preparing the product body may be, for example, manufacturing the product body using the manufacturing apparatus 620. Preparing the product body may also be obtaining the manufactured product body. Preparing the packaging materials may include, for example, preparing a container (first packaging material) (step S32) and preparing shrink film (second packaging material) (step S33). Preparing a container may be manufacturing the container or obtaining the manufactured container. The execution order of steps S31, S32, and S33 is not particularly limited.

[0040] Preparing the shrink film in step S33 may include printing on the shrink film body using the printing device 613 to produce a printed shrink film. The shrink film body can be purchased. The shrink film body is a heat-shrinkable transparent film made of polyethylene, polypropylene, PVC, etc.

[0041] The prepared product body is placed in container 103 (step S34). Step S34 may include, for example, filling container 103 (see Figure 2) with the product body using a bottling system 621 (first packaging device).

[0042] The container 103 is wrapped in shrink film (step S35). Step S35 includes, for example, loosely attaching the shrink film to the container 103, and then using the shrink device 622 (second packaging device) to tightly attach the shrink film 101 to the container 103. As a result, the product 105 wrapped with packaging materials 101 and 103 is completed (see Figure 2). In addition, multiple products 105 may be further wrapped in packaging material such as paper or plastic in order to bundle multiple products 105 together.

[0043] In this embodiment, a code for the purchaser of product 105 to obtain tokens is attached to product 105, so the ability to obtain tokens increases the incentive to purchase product 105. To increase the value of product 105, it is preferable that the code attached to product 105 is a unique code different for each individual product 105. In this embodiment, the purchaser of product 105 can send the code attached to product 105 to the token distribution system 10 and receive tokens distributed from the token distribution system 10.

[0044] In this embodiment, the packaging of product 105 is used to assign a code to product 105. More specifically, a shrink film 101 (label 101) attached to the container is used to assign a code to product 105. The shrink film 101 is printed with images and characters that make up the label, and the code is also printed during the label printing process, resulting in a shrink film 101 with a code assigned to it.

[0045] As shown in Figure 3, a token code is generated in order to prepare the shrink film 101 having the token code (step S331). The generated token code is stored, for example, in the storage device 51B of the token distribution system 10 and the storage device 611B of the printing system 610 (steps S332, S333). The token code is a unique code different for each product 105. The token code may be generated each time the shrink film 101 is printed, or the required number of codes (for example, the required number according to the number of products to be manufactured) may be prepared in advance.

[0046] The token code may be generated by the token distribution system 10, as shown in Figure 4(A) (see step S41 in Figure 4(A)), or by the printing system 610, as shown in Figure 4(B) (see step S41 in Figure 4(B)). In other words, the entity that generates the token is not particularly limited. The token may be generated by a computer, such as the server 51 of the token distribution system 10 or the print management device 611 of the printing system 610, according to an algorithm for generating a code consisting of a unique string. Thus, the token generation means may be provided by the token distribution system 10 or by the printing system 610.

[0047] In this embodiment, the generated token code is shared and stored in both the token distribution system 10 and the printing system 610. Therefore, as shown in Figure 4(A), when a code is generated in the token distribution system 10 (step S41), the token distribution system 10 transmits the code to the printing system 610 (step S42). The printing system 610 receives the code (step S44) and stores the received code in the storage device 611B as a code for printing (steps S45, S332). The transmission and reception of the code may be performed via the network 15. The token distribution system 10 also stores the generated code in the storage device 51B as a registered code (steps S43, S333). Step S43 may be performed before step S42.

[0048] As shown in Figure 4(B), when a code is generated in the printing system 610 (step S41), the printing system 610 transmits the code to the token distribution system 10 (step S42). The token distribution system 10 receives the code (step S44) and stores the received code in the storage device 51B as a registered code (steps S45, S333). The transmission and reception of the code may be performed via the network 15. The printing system 610 also stores the generated code in the storage device 611B as a printing code (steps S43, S332). Step S43 may be performed before step S42.

[0049] The token code (printing code) stored in the printing system 610 is used by the printing system 610 to print the code. The token code (registered code) stored in the token distribution system 10 is used by the token distribution system 10 to determine whether or not to distribute tokens. When the token distribution system 10 receives a code from a code sender, such as a purchaser of product 105 to which a code has been assigned, and the code is the same as the code (registered code) assigned to product 105, it sends a token to the code sender. The token distribution system 10 does not distribute a token if the code sent from the code sender is different from the code (registered code) assigned to product 105.

[0050] Returning to Figure 3, the printing system 610 prints the token code onto the shrink film body to obtain the printed shrink film 101 (step S334). The shrink film 101 is then processed into a shape suitable for mounting onto the container 103 (step S335). A suitable shape for mounting onto the container 103 is, for example, a cylindrical shape. If the printed shrink film 101 is a flat sheet, the shrink film 101 can be made cylindrical by bonding the ends of the film together.

[0051] The shrink film 101 processed in step S335 is placed in the shrinking device 622 while loosely attached to the container 103 and heated. Upon heating, the shrink film 101 shrinks and becomes tightly attached to the container 103 (step S35).

[0052] Now, steps S21 to S23 in Figure 2 show the procedure for generating print data for printing in step S334 of Figure 3.

[0053] As shown in Figure 2, in one embodiment, the printing system 610 uses the token code list 51E and URI table 51F stored in the storage device 611B for printing the codes (steps S21, S22). Label data stored in the storage device 611B may also be used for printing (step S23).

[0054] In one embodiment, the printing of the code is performed in the form of a two-dimensional code representing a Uniform Resource Identifier (URI) that includes a token code. A two-dimensional code is a type of machine-readable code. The URI comprises a scheme and an authority. Here, the URI is, for example, a Uniform Resource Locator (URL). The scheme is, for example, https:. The authority is written following the scheme 121 and indicates the location of the resource, etc. Note that the generated URI 120 does not necessarily include a scheme.

[0055] In one embodiment, the authority may comprise, for example, a host 123A, contract information 123B, and a token code 123C, as shown in URI 120 in Figure 5. Host 123A represents the name (domain name) of server 51. Contract information 123B and token code 123C may be, for example, a path described after host 123A. In the authority shown in Figure 5, contract information 123B is, for example, "receive-link / ", and token code 123C is, for example, "qC2oFsNKrHimID6u". Token code 123C may be sent to blockchain 20 for the invocation of smart contract 22.

[0056] Contract information 123B may be used to identify the caller. If the caller is a smart contract 22, contract information 123B may include the contract address where the smart contract 22 is stored or information for the server 51 to identify the contract address. For example, contract information 123B may be converted by the server 51 into data (such as the contract address of the smart contract 22) that is sent to the blockchain 20 to identify the smart contract being called.

[0057] Furthermore, if the server 51 already knows the smart contract 22 to be called, the contract information 123B may be omitted in the URI 120.

[0058] Now, the storage device 611B of the printing system 610 stores a token code list 51E having multiple token codes, as shown in Figure 5. The token code list 51E is a list of print codes generated and stored in step S331 of Figure 3. The printing system 610 refers to the token code list 51E and selects the token code (print code) to be printed. Since the token code is different for each product 105, the selection of token codes is performed for each shrink film (each label). The selection of token codes may be, for example, in the order of the code numbers associated with the token codes.

[0059] The printing system 610 may have multiple token code lists 51E. For example, a first campaign and a second campaign different from the first campaign may be planned for token distribution. In this case, it may be desirable to distinguish between the tokens distributed in the first campaign and the tokens distributed in the second campaign. When distinguishing between tokens distributed in both campaigns, it is preferable to distinguish the token codes as well. To distinguish the token codes, the printing system 610 may have a token code list for the first campaign and a token code list for the second campaign. In this case, the printing system 610 can select a token code list prior to selecting the token codes to be printed.

[0060] Furthermore, the storage device 611B stores a URI table 51F having one or more URI bodies. The URI table 51F shown in Figure 5 is configured by associating specified data with URI bodies.

[0061] For example, in URI table 51F, the designated data "campaign / 1" representing the first campaign is associated with "bbb....com / receive-link / " as the body of the second URI. Similarly, the designated data "campaign / 2" representing the second campaign is associated with "bbb....com / receive_NFT-link / " as the body of the second URI. The designated data "campaign / 3" representing the third campaign is associated with "bbb....com / receive_FT-link / " as the body of the second URI.

[0062] The second URI body for the first campaign has "receive-link / " as contract information 123B for the first campaign. In other words, the specified data "campaign / 1" is associated with "receive-link / " for the first campaign as contract information 123B.

[0063] The second URI body for the second campaign contains "receive_NFT-link / " as contract information 123B for the second campaign. In other words, the specified data "campaign / 2" is associated with "receive_NFT-link / " for the second campaign as contract information 123B.

[0064] The second URI body for the third campaign contains "receive_FT-link / " as contract information 123B for the third campaign. In other words, the specified data "campaign / 3" is associated with "receive_FT-link / " for the third campaign as contract information 123B.

[0065] The administrator of the printing system 610 may provide the printing system 610 with specified data for the selection of an appropriate URI body. The printing system 610 selects a URI body corresponding to the given specified data based on the URI table 51F. For example, if the specified data "campaign / 1" is given, "bbb....com / receive-link" will be selected as the URI body.

[0066] Furthermore, the printing system 610 (URI generation means) can select a token code from the token code list 51E associated with the specified data "campaign / 1" and determine a single token code. Here, as an example, the token code "qC2oFsNKrHimID6u" with code number 1 is selected. In this case, the selection of token codes is carried out in order of code number.

[0067] The printing system 610 (URI generation means) generates a URI 120 by combining the selected URI body and the token code (step S21 in Figures 2 and 5). For example, the printing system 610 can add the token code to the URI body as part of the path that follows the URI body. For example, if 10,000 products 105 are generated for a campaign, 10,000 different URIs 120 with a common URI body can be generated by combining each of the 10,000 token codes 123C with a common URI body for that campaign.

[0068] Furthermore, if there is only one campaign, or if the URI body is fixed to a single value, the determination of the URI body using URI table 51F and the selection of the token code list may be omitted.

[0069] Each generated URI is converted into a two-dimensional code (step S22 in Figure 2). This generates data representing the two-dimensional code 51H. Since the token code is different for each product 105, the two-dimensional code 51H may also be different for each product 105.

[0070] The printing system 610 (print data generation means) combines the label design data 51G stored in the storage device 611B with the data representing the two-dimensional code 51H to generate print data for shrink film printing (label printing) (step S23 in Figure 2). The label design data 51G is data representing the design, characters, etc. that will be recognized by the purchaser as the label surface. The label design may be common to multiple products of the same type. By printing using the print data that combines the label design data 51G and the data representing the two-dimensional code 51H, the two-dimensional code 51H will appear on the printed shrink film 101 (label 101). Since the two-dimensional code 51H is different for each product 105, even if the label design data 51G is common, each product 105 will have a different two-dimensional code 51H. A shrink film 101 (label 101) is obtained. Therefore, each product 105 with the shrink film 101 attached will have a different two-dimensional code 51H (token code).

[0071] Furthermore, combining the label design data 51G and the data representing the two-dimensional code 51H may result in the generation of image data in which the label design data 51G and the two-dimensional code 51H are inseparable, or it may result in the generation of image data comprising a print layer having the label design data 51G and another print layer having the data for the two-dimensional code 51H.

[0072] Figure 6 shows the procedure by which a purchaser of product 105 accesses the token distribution system 10 to obtain a token. The purchaser reads the two-dimensional code 51H attached to product 105 using their terminal 31. The terminal 31 is, for example, a mobile device such as a smartphone equipped with a camera for reading the two-dimensional code 51H.

[0073] First, terminal 31 reads the two-dimensional code 51H attached to product 105 and obtains the URI 120 represented by the two-dimensional code 51H. In order to call the smart contract 22 of the token distribution system 10, terminal 31 uses the read URI 120 to access the server 51 of the token distribution system 10 (step S61). Upon receiving the access from terminal 31, server 51 calls the smart contract 22 to send tokens in order to distribute tokens to the user with terminal 31 (the purchaser of product 105) (step S63). The called smart contract 22 performs predetermined processing (steps S64, S65) in order to send the tokens.

[0074] Furthermore, when accessing or after accessing server 51, terminal 31 may sign in to server 51 with an account held by the user (purchaser of product 105) on server 51. The account held by the user may be the same as the user's account (blockchain address) on the blockchain.

[0075] The server 51 can obtain the data necessary to invoke the smart contract 22 prior to invoking the smart contract 22 (step S63). The data necessary to invoke the smart contract 22 is, for example, the contract address of the smart contract 22 to be invoked. The server 51 identifies the contract address corresponding to the contract information 123B contained in the URI 120. The server 51 invokes the smart contract 22 stored at the identified contract address.

[0076] Figure 7 shows an example of processing performed by the smart contract 22 that receives the call. The smart contract 22 shown in Figure 7 is configured to cause the computers constituting the blockchain 20 to execute the process of sending tokens from the contract address (0x8888) of the smart contract 22 to the blockchain accounts 25A and 25B of the user (product purchaser; sender of the token code) that called the smart contract 22. The user's blockchain accounts 25A and 25B may be used by the server 51 to identify the user (product purchaser; sender of the token code). Furthermore, the contract address 21 of the smart contract 22 may be used to identify the smart contract 22 that is being called.

[0077] The smart contract 22 is invoked, for example, by the server 51, with account 25A or 25B as the calling account (step S71). Account 25A or 25B is the sending account of URI 120 containing the token code.

[0078] When an invocation is made, token codes C1 and C2 are sent from accounts 25A and 25B to the contract address 21 of smart contract 22. When an invocation is made, the contract address 21 of smart contract 22 may also be sent from accounts 25A and 25B to identify the smart contract 22 to be invoked. Server 51 has correspondence data (not shown) between contract information 123B and contract address 21, and can identify the contract address 21 of the smart contract 22 to be invoked from the contract information 123B included in the URI used to access server 51. The smart contract 22 shown in Figure 7 is configured to send tokens when it receives token codes C1 and C2, triggering the transmission of tokens.

[0079] Here, the token code can be used by smart contract 22 to identify the object to which smart contract 22 operates. The token code can be used, for example, by smart contract 22 to identify a non-fungible token (NFT) to be operated by smart contract 22. For example, smart contract 22 can use the received token code C1 to identify the NFT to be sent and send the identified NFT.

[0080] Furthermore, the token code can be used by smart contract 22 to identify the number of fungible tokens (FTs) to be manipulated by smart contract 22. For example, smart contract 22 can use the received token code C2 to identify the number of FTs (token count) to send and send the identified number of FTs.

[0081] The token code may be used to identify the type of token being manipulated by the smart contract 22. For example, the token code may be used to identify whether the token being manipulated by the smart contract 22 is a non-fungible token or a fungible token. Furthermore, if multiple types of fungible tokens exist, the token code may be used to identify the type of non-fungible token being manipulated.

[0082] The smart contract 22 may include a token table 310, as shown in Figure 7, for identification using the received token codes C1 and C2. The token table 310 is also a table where the aforementioned registered codes are stored. The token codes generated in step S331 in Figure 3 (step S41 in Figure 4) are stored in this token table 310 as registered codes. The token table 310 in this embodiment is data that associates token codes with the identification content associated with those token codes. The identification content associated with the token codes is, for example, a token identifier or the number of tokens, as shown in Figure 7. The token table 310 is generated by associating the generated token codes with the identification content associated with the tokens. The token table 310 is saved, for example, by the server 51 writing the token table 310 to the contract address of the smart contract 22.

[0083] The information identified by the token code in smart contract 22 (the information identified by the token code) could be, for example, the identifier of the non-fungible token to be sent (NFT identifier). Alternatively, the information identified by the token code could be, for example, the number of fungible tokens. Furthermore, the information identified by the token code could be the type of fungible token and the number of those fungible tokens.

[0084] In the token table 310 shown in Figure 7, for example, token code C1 is associated with the NFT identifier "NFT_id01". Also, token code C2 is associated with "10_tokens", where "10_tokens" indicates that there are 10 of a certain type of fungible token. Token code C3 is associated with "1_tokens", where "1_tokens" indicates that there is 1 of a certain type of fungible token.

[0085] The token table 310 shown in Figure 7 can also be used by the smart contract 22 to determine whether the received token code (received code) is identical to a registered code. As shown in Figure 6, the smart contract 22, upon receiving a token code, can determine whether the received token code (received code) is identical to a registered code (step S64). If a token code identical to the received code is included in the token table 310, it is determined that the received code is identical to a registered code. If the received code is identical to a registered code, the smart contract 22 sends the token to the blockchain account that sent the code (step S65). If the received code is not identical to a registered code, an error occurs (step S66), and the smart contract 22 does not send the token.

[0086] The token transmission in step S65 is, for example, the transmission of an NFT associated with a registered code identical to the received code in the token table 310 shown in Figure 7.

[0087] In this embodiment, if the received code is the same as a registered code, the token to be transmitted is determined and transmitted; otherwise, the token is not transmitted. Determining the token to be transmitted may include, for example, identifying an NFT associated with a registered code identical to the received code. Determining the token to be transmitted may also include generating the token to be transmitted after step S64 and designating the generated token as the target for transmission. Furthermore, determining the token to be transmitted may include identifying a quantity pre-associated with a registered code identical to the received code and transmitting the identified quantity of FTs. Furthermore, determining the token to be transmitted may include determining the quantity of FTs to be transmitted after step S64 and transmitting the determined quantity of FTs.

[0088] The determination of whether the received code is the same as a registered code may be performed by the server 51. In this case, if the token code (received code) received by the server 51 from the terminal 31 is the same as a registered code, the smart contract 22 is called; otherwise, the smart contract 22 is not called. The server 51 can save the token code generated in step S331 in Figure 2 (step S41 in Figure 4) as a registered code.

[0089] Furthermore, smart contract 22 may pre-exist tokens 410, 420, 430, and 450, which are the targets of operation (transmission targets) identified by the token code. Upon receiving a token code, smart contract 22 identifies the target token from among the held tokens 410, 420, 430, and 450, and transmits the identified token. In other words, when smart contract 22 of the token distribution system 10 receives a token code identical to a registered code registered in the token table 310, it identifies the token, such as a non-fungible token, associated with that received code C1, and transmits the identified token.

[0090] The smart contract 22 receives, for example, token code C1 from account 25A (step S71). Account 25A is the blockchain account (blockchain address) of the person who purchased a certain product, and is the account (token sender) of the person who accessed server 51 (token distribution system 10) using a URI containing token code C1. Upon receiving token code C1, the smart contract 22 refers to table 310 and identifies a non-fungible token 410 with the identifier "NFT_id01" as the target of operation corresponding to token code C1. Then, the smart contract 22 sends the non-fungible token 410 to account 25A (step S72). Since there is only one non-fungible token 410 with the identifier "NFT_id01", if the target of operation (sending target) is a non-fungible token, the target of operation (sending target) can be identified by the NFT identifier.

[0091] Furthermore, smart contract 22 receives token code C2 from account 25B, for example (step S71). Smart contract 22 then refers to table 310 and identifies "10_tokens" as the target of the operation corresponding to token code C2. That is, smart contract 22 identifies that the number of non-fungible tokens to be sent is 10 units. Smart contract 22 then sends the identified number (10 units) of fungible tokens from its holdings of fungible tokens 450 to account 25B (step S72). Here, one fungible token is considered as one unit.

[0092] Fungible tokens are fungible, and each individual token does not have an identifier. Therefore, smart contract 22 identifies the number of tokens to be sent by token code C2, rather than identifying individual fungible tokens. If smart contract 22 can handle multiple types of fungible tokens, smart contract 22 may also identify the type of fungible token to be sent by token code C2.

[0093] It is preferable that token codes C1, C2, and C3 are data configured in such a way that they cannot identify the type or number of tokens being manipulated (sent) by anyone other than the smart contract 22. For example, it is preferable that token codes C1, C2, and C3 are data that represent values ​​that appear meaningless or random at first glance.

[0094] The smart contract 22 shown in Figure 7 supports the sending of both non-fungible and fungible tokens, but it may also support the sending of only non-fungible tokens or only fungible tokens.

[0095] In this case, with regard to non-fungible tokens, token code C1 functions as an identifier for the non-fungible token being sent. However, the smart contract 22 shown in Figure 7 does not receive the non-fungible token identifier (e.g., "NFT_id01") recorded on the blockchain 20 to identify the non-fungible token to be sent.

[0096] Here, smart contract 22 may be configured to send the non-fungible token indicated by the identifier ("NFT_id01") when it receives the identifier (e.g., "NFT_id01") of a non-fungible token recorded on the blockchain.

[0097] However, by using a token code that has a different identifier from the non-fungible token identifier recorded on the blockchain (for example, "NFT_id01"), it is possible to avoid unintentionally sending non-fungible tokens. In other words, if the non-fungible token identifier recorded on the blockchain ("NFT_id01") is used to send non-fungible tokens, and if the non-fungible token identifier recorded on the blockchain ("NFT_id01") is known to a third party, that third party can use that identifier ("NFT_id01") to illegally obtain non-fungible tokens from smart contract 22.

[0098] In contrast, when using a token code, even if the identifier of the non-fungible token ("NFT_id01") recorded on the blockchain is known to a third party, that third party will not be able to illegally acquire the non-fungible token.

[0099] Furthermore, regarding fungible tokens, token codes C2 and C3 function as identifiers for fungible tokens that do not have identifiers to distinguish each individual fungible token. For example, if we want smart contract 22 to send 10 units of fungible tokens, for example, 100 times, we only need to prepare 100 unique token codes. In this case, when smart contract 22 receives a token code, it will send 10 units of fungible tokens. In this case, the total number of fungible tokens sent is 1000 units, and each of these 1000 fungible tokens does not have an identifier. However, since the token codes function as identifiers for every 10 units of fungible tokens, it becomes easy to handle fungible tokens individually in units of 10.

[0100] Furthermore, it becomes possible to vary the number of fungible tokens sent for each token code, such as token codes C2 and C3.

[0101] Here, smart contract 22 may be configured to send the number of fungible tokens indicated in the received data (fungible token request) upon receiving data indicating the number of fungible tokens to be sent. However, in that case, there is no guarantee that the data indicating the number of fungible tokens to be sent (fungible token request) is appropriate. In other words, there is no guarantee that the fungible token request is appropriate.

[0102] Allowing inappropriate fungible token requests would enable third parties to fraudulently obtain non-fungible tokens from smart contract 22. In other words, there is a risk that fungible tokens could be unintentionally leaked from smart contract 22.

[0103] In contrast, when using token codes C2 and C3 (registered codes), those who do not possess token codes C2 and C3 (registered codes), i.e., non-purchasers of product 105, cannot obtain fungible tokens from smart contract 22, thus preventing unintended outflow of fungible tokens. Furthermore, when using token codes C2 and C3, even if a third party learns the type of fungible token sent by smart contract 22, a third party who does not know the token code cannot illegally obtain the fungible tokens.

[0104] The smart contract 22 shown in Figure 7 already holds the non-fungible token to be sent, but the smart contract 22 may generate the non-fungible token to be sent after receiving the token code (step S71). In other words, the token code associated with the NFT does not need to be pre-associated with a specific NFT identifier. The generated NFT may be generated based on predetermined generation rules or may be generated randomly.

[0105] Furthermore, the token code associated with the NF does not need to have a pre-associated number of tokens to be sent. The number of tokens to be sent may be determined by a predetermined rule or randomly.

[0106] Now, if a two-dimensional code is attached to the surface of a product, there is a risk that the two-dimensional code 51H may be illegally read before the product is purchased, for example, while the product is on display in a store. Therefore, it is desirable to prevent illegal reading. Below, we will describe a film 101 that is suitable for preventing illegal reading.

[0107] Figure 8 shows an example of a shrink film 101 (label 101) with a two-dimensional code 51H printed on it. The film 101 shown in Figure 8 comprises a transparent film body 200 and one or more printed layers 201, 202, 203, 204, 205 formed on the film body 200. The film body 200 has a front surface 200A and a back surface 200B. The back surface 200B is the side facing the container 103 to which the film 101 is attached. The front surface 200A is the side opposite to the back surface 200B and is the side that can become the front surface of the product 105 when the film 101 is attached to the container 103. The printed layers 201, 202, 203, 204, 205 shown in Figure 8 are formed on the back surface 200B of the film body 200 as an example. The printed layer 201 formed on the back surface 200B is visible from the front surface 200A side through the transparent film body. The film 101 shown in Figure 8 is processed into a cylindrical shape with the surface 200A facing outwards and the back surface 200B facing inwards, and can be attached to the container 103.

[0108] The film 101 shown in Figure 8 comprises, as an example, five printing layers 201, 202, 203, 204, and 205. Here, the printing layer 201 closest to the film body 200 is referred to as the first printing layer 201. Moving away from the film body 200, the layers are arranged in the order of the first printing layer 201, second printing layer 202, third printing layer 203, fourth printing layer 204, and fifth printing layer 205. The multiple printing layers are formed by printing image data containing multiple printing layer data.

[0109] The first printing layer 201 is a layer for representing a label design that includes text, graphics, etc. The first printing layer 201 is formed on the back surface 200B of the film body 200 and is visible from the front surface 200A side through the film body 200. The first printing layer 201 can be formed, for example, over almost the entire surface of the film body 200.

[0110] The second printing layer 202 is a base layer for the first printing layer 201. The second printing layer 202 serves as a base for the first printing layer 201 and enhances its aesthetic appearance. The second printing layer 202 is, for example, a white layer. The second printing layer 202, like the first printing layer 201, can be formed over almost the entire surface of the film body 200.

[0111] The third printing layer 203 is a shielding layer. The third printing layer 203 has a darker color than the fifth printing layer 205 or the same color as the fifth printing layer 205 so that the printed content (two-dimensional code 51H) of the fifth printing layer 205 is not visible from the surface 200A of the film body 200. The third printing layer 203 is, for example, a black layer. The third printing layer 203 may be printed on a portion of the film body 200 in correspondence with the printing of the fifth printing layer 205 on a portion of the film body 200.

[0112] The fourth printing layer 204 is a base layer for the fifth printing layer 205. The fourth printing layer 204 serves as a base for the fifth printing layer 205, improving its aesthetic appearance. The fourth printing layer 204 is, for example, a white layer. The third printing layer 203 may be printed on a portion of the film body 200 in correspondence with the printing of the fifth printing layer 205 on a portion of the film body 200.

[0113] The first print layer 201, the second print layer 202, the third print layer 203, and the fourth print layer 204 may correspond to the printed label design data 51G shown in Figure 2.

[0114] The fifth printing layer 205 is the layer that represents the two-dimensional code 51H. In other words, the fifth printing layer 205 is the layer on which data representing the two-dimensional code 51H is printed. The fifth printing layer 205 is not visible from the surface 200A side. In other words, the two-dimensional code 51H is not visible from the front side of the film 101. Therefore, when the film 101 is attached to the container 103, the two-dimensional code 51H cannot be read.

[0115] On the other hand, the two-dimensional code 51H is visible from the back of the film 101. When the film 101 is removed from the container 103, the two-dimensional code 51H can be read.

[0116] When a customer purchases the product, the film 101 is removed from the container 103, a two-dimensional code 51H is revealed, which can then be read by the terminal 31. Furthermore, since the two-dimensional code 51H does not appear unless the film 101 is removed from the container 103, it is possible to prevent the two-dimensional code 51H of the product 105 on the store shelves from being read illegally.

[0117] Figure 9 shows shrink film 101 (label 101) with a two-dimensional code 51H printed on it. Another example is shown. The film 101 shown in Figure 9 comprises a transparent film body 200 and one or more printed layers 201, 202, 203 formed on the film body 200. The film body 200 has a front surface 200A and a back surface 200B. The back surface 200B is the side facing the container 103 to which the film 101 is attached. The front surface 200A is the side opposite to the back surface 200B and is the side that can become the surface of the product 105 when the film 101 is attached to the container 103. The printed layers 201, 202, 203 shown in Figure 9 are formed on the back surface 200B of the film body 200 as an example. The printed layer 201 formed on the back surface 200B is visible from the front surface 200A side through the transparent film body. The film 101 shown in Figure 9 can be processed into a cylindrical shape with the front surface 200A being the outer surface and the back surface 200B being the inner surface, and can be attached to the container 103.

[0118] The film 101 shown in Figure 9 comprises, as an example, three printing layers 201, 202, and 203. The first printing layer 201 has an area 201B for representing a label design with characters, figures, etc., and an area 201A that serves as a shielding area for the third printing layer 203. The area 201A that serves as a shielding area for the third printing layer 203 has a color that is darker than or the same as the third printing layer 203 so that the printed content (two-dimensional code 51H) of the third printing layer 203 cannot be seen from the surface 200A of the film body 200. Area 201A is, for example, a black area. Area 201A may be a part of the first printing layer 201, corresponding to the third printing layer 203 being printed on a part of the film body 200. The first printing layer 201 is formed on the back surface 200B of the film body 200 and is visible from the front surface 200A side through the film body 200. The first printing layer 201 may be formed on, for example, substantially the entire surface of the film body 200.

[0119] The second printing layer 202 is a base layer for the first printing layer 201. The second printing layer 202 serves as a base for the first printing layer 201 and enhances its aesthetic appearance. The second printing layer 202 is, for example, a white layer. The second printing layer 202, like the first printing layer 201, can be formed over almost the entire surface of the film body 200.

[0120] The first print layer 201 and the second print layer 202 may correspond to the printed label design data 51G shown in Figure 2.

[0121] The third printing layer 203 is the layer that represents the two-dimensional code 51H. In other words, the third printing layer 203 is the layer on which data representing the two-dimensional code 51H is printed. The third printing layer 203 is not visible from the surface 200A side. In other words, the two-dimensional code 51H is not visible from the front side of the film 101. Therefore, when the film 101 is attached to the container 103, the two-dimensional code 51H cannot be read. On the other hand, the two-dimensional code 51H is visible from the back side of the film 101. When the film 101 is removed from the container 103, it becomes possible to read the two-dimensional code 51H.

[0122] Figures 10 and 11 show other examples of shrink film 101 (label 101) printed with a two-dimensional code 51H. The film 101 shown in Figure 10A comprises a transparent film body 500 having a front surface 500A and a back surface 500B, and one or more printed layers formed on the back surface 500B of the film body 500. The printed layer formed on the back surface 500B includes the two-dimensional code 51H and is visible from the front surface 500A side through the transparent film body. The film body 500 is rectangular and has a pair of first sides 501 and second sides 502 in the horizontal direction, and a pair of third sides 503 and fourth sides 504 in the vertical direction. The third side 503 may be the side corresponding to the top side of the container 103. The fourth side 504 may be the side corresponding to the bottom side of the container 103.

[0123] The film 101 shown in Figure 10A can be processed into a cylindrical shape and attached to the container 103, as shown in Figure 10B. The film 101 comprises a first region 530 and a second region 540. The first region 530 and the second region 540 are arranged side by side in the lateral direction of the film body 500. The first region 530 is the region that appears as the outer surface of the cylinder when the film 101 is processed into a cylindrical shape. The second region 540 is located closer to the container 103 than the first region 530 and overlaps with the first region 530. The first region 530 has an overlapping region 530A (overlap region 530A) with the second region 540. When the film 101 is attached to the container 103, the second region 540 on which the two-dimensional code 51H is attached is covered and hidden by the printed overlap region 530A. Therefore, when the film 101 is attached to the container 103, the two-dimensional code 51H cannot be read.

[0124] When processing the film 101 shown in Figure 10A into a cylindrical shape, for example, the second side 502 of the film 101 is bonded to the boundary 505 between the first region 530 and the second region 540 with an adhesive. At this time, the second side 502 is bonded to the boundary 505 such that the overlapping region 530A of the first region 530 overlaps the surface 500A of the second region 540. By processing the film 101 into a cylindrical shape in this way, the first region 530 appears as the outer surface of the cylinder, and the second region 540 is hidden inside the cylinder. Therefore, the two-dimensional code 51H is hidden.

[0125] Preferably, the first side 501 is a free end that is not adhered to the first region 530. If the first side 501 is a free end, it becomes easier to remove the film 101 from the container 103. However, the first side 501 may be peelably adhered to the first region 530. To achieve peelable adhesion, for example, a weakly adhesive adhesive (tack) can be used.

[0126] Furthermore, the film 101 has a removal section 510 formed in the overlapping region 530A of the first region 530, consisting of a pair of perforations 551 and 552 formed in the vertical direction. The removal section 510 is formed, for example, in the overlapping region 530A of the first region 530. The removal section 510 is for removing the film 101 attached to the container 103 from the container 103 using the perforations 551 and 552. By using the removal section 510, the film 101 can be easily removed from the container 103 by cutting it in the vertical direction of the container 103.

[0127] As shown in Figures 11A and 11B, when the perforations 551 and 552 are cut, the second region 540, which was covered by the overlap region 530A, is revealed. That is, the two-dimensional code 51H is revealed, and it becomes possible to read the two-dimensional code 51H. Moreover, by cutting the outer part 510 in a way that exposes the two-dimensional code 51H, the film 101 can be removed from the container 103. In other words, the process of removing the film 101 from the container 103 also serves to expose the two-dimensional code 51H. Therefore, the ability to read the two-dimensional code 51H can be used as an incentive to remove the film 101 from the container 103 for sorting. Note that if the first edge 501 is not a free end but is glued, the film 101 can be removed from the container 103 by peeling off the first edge 501 after cutting the outer part 510.

[0128] Furthermore, the outer part 510 does not need to be composed of perforations 511 and 512. For example, the outer part 510 may be configured such that the second side 502 is detachably bonded to the boundary 505. In this case, by peeling the second side 502 away from the boundary 505, the film 101 can be removed from the container 103 and the two-dimensional code 51H can be exposed.

[0129] Figures 12 and 13 show other examples of shrink film 101 (label 101) printed with a two-dimensional code 51H. The film 101 shown in Figure 12A comprises a transparent film body having a front surface 600A and a back surface 600B, and one or more printed layers formed on the back surface 500B of the film body. The printed layers may be formed in the same manner as in the examples of Figure 8 or 9. That is, the printed layer formed on the back surface 600B includes the two-dimensional code 51H, is not visible from the front surface of the film 101, and is visible from the back surface. The film body 500 is rectangular and has a pair of first sides 601 and second sides 602 in the horizontal direction, and a pair of third sides 603 and fourth sides 604 in the vertical direction. The third side 603 may be the side corresponding to the top side of the container 103. The fourth side 504 may be the side corresponding to the bottom side of the container 103. The container 103 is a container with a cap 107. The cap 107 closes the opening of the container 103. The cap 107 is, for example, a screw cap.

[0130] As shown in Figure 12A, the film 101 is attached to the container 103 with a cap 107, so as shown in Figure 12B, that it covers the container 103, including the cap 107. Therefore, the film 101 shown in Figure 12A comprises a main body region 630 that covers the container 103 and a cap region 640 that covers the cap 107. The main body region 630 and the cap region 640 are arranged side by side in the vertical direction of the film body 600. That is, in the film 101, the cap region 640 is formed above the main body region 630.

[0131] As shown in Figure 12A, the film 101 has perforations (first perforations) forming a first take-off portion 650 in the vertical direction of the film 101. Also, as shown in Figure 12B, perforations (second perforations) forming a second take-off portion 660 are formed in the horizontal direction of the film 101. The perforations forming the take-off portion 660 are intended to separate the cap portion 640 of the film 101 from the main portion 630 so that the cap 107 can be removed from the container 103 when the product is first used or consumed. Even if the cap portion 640 is removed, the main portion 630 remains attached to the container 103. Therefore, when storing the product 105 after opening the cap 107, consumers can refer to the contents printed on the main portion 630 (for example, product description, product name, expiration date, etc.).

[0132] The first removal section 650 is for removing the main body area 630 attached to the container 103 for disposal or recycling after use or consumption of the product body. In Figure 12A, the perforations constituting the removal section 650 are formed up to the cap area 640, but the perforations constituting the removal section 650 may be formed only on the main body area 630. Alternatively, instead of perforations, the removal section 650 may be constructed by detachably bonding the first side 601 and the second side 602.

[0133] In the examples shown in Figures 12 and 13, the two-dimensional code 51H is formed on the back surface 600B of the cap area 640. Therefore, before removing the cap area 640, the two-dimensional code 51H is not visible from the front side of the film 101. Consequently, the two-dimensional code 51H cannot be read before opening the cap 107.

[0134] On the other hand, when the cap area 640 is separated from the main body area 630 by the handle part 660 to open the cap 107, it becomes possible to read the two-dimensional code 51H formed on the back surface 600B of the cap area 640, as shown in Figure 13. Therefore, in the examples shown in Figures 12 and 13, it is possible to read the two-dimensional code 51H when the main body area 630 is attached to the container 103 at the start of use or consumption of the product.

[0135] Figure 14 shows an example in which a two-dimensional code 51H is attached to the cap 107. The two-dimensional code 51H is attached to the cap 107 by printing, for example. The film 101 attached to the container 103 with the cap 107 may be the same film 101 as in the examples in Figures 12 and 13. That is, the film 101 comprises a main body area 630 and a cap area 640, and is attached to the container 103 with the cap 107 attached so as to cover the cap 107. The cap area 640 can be separated from the main body area 630 by an outer part 660.

[0136] In the example shown in Figure 14, the two-dimensional code 51H attached to the cap 107 is hidden by the printed cap area 640. Therefore, before removing the cap area 640, the two-dimensional code 51H is not visible from the front side of the film 101. Consequently, the two-dimensional code 51H cannot be read before opening the cap 107.

[0137] On the other hand, when the cap area 640 is separated from the main body area 630 by the handle part 660 to open the cap 107, the two-dimensional code 51H attached to the cap 107 is revealed, making it possible to read the two-dimensional code 51H. Therefore, in the examples shown in Figures 12 and 13, the two-dimensional code 51H can be read when the main body area 630 is attached to the container 103 at the start of use or consumption of the product.

[0138] Figure 15 shows a shrink film 101 with a backing board 700 as a type of packaging material. The shrink film 101 is processed into a tubular shape and attached to the backing board 700 by adhesives 710 and 720. As shown in Figure 16, the shrink film 101 covers, for example, a container 103 containing the product itself. The container 103 is placed inside the shrink film 101 and heated together with the backing board 700 by a shrinking device, causing it to shrink and adhere tightly to the container 103. The shrink film 101 adheres tightly to the container 103, fixing the container 103 to the backing board 700. The shrink film 101 does not need to be printed and can be transparent. The backing board has the product name, product description, etc. printed on it, allowing for more freedom in decorative expression compared to the container 103 alone. If the shrink film 101 is transparent, the container 103 fixed to the backing board 700 is visible from outside the shrink film 101.

[0139] A two-dimensional code 51H is attached to the backing sheet 700. The two-dimensional code 51H may be printed, for example, at the same time as printing other parts of the backing sheet 700 (such as product descriptions). A shrink film 101 is attached to the backing sheet 700 on which the two-dimensional code 51H is printed. In Figure 15, the two-dimensional code 51H is formed on the backing sheet 700 in a position where it will be covered by the shrink film 101. In other words, as shown in Figure 16, the two-dimensional code 51H is formed in a position where it will be covered by the container 103 which is fixed to the backing sheet 700 via the shrink film 101.

[0140] As shown in Figure 16, when the container 103 is fixed to the backing paper 700 via the shrink film 101, the two-dimensional code 51H is unreadable because the container 103 is located on the two-dimensional code 51H. The two-dimensional code 51H cannot be read while the container 103 is fixed to the backing paper 700.

[0141] On the other hand, when the container 103 is removed from the backing 700 for use or consumption of the product, the two-dimensional code 51H attached to the backing 700 becomes visible, and the two-dimensional code 51H can be read. In other words, in the examples shown in Figures 15 and 16, the two-dimensional code 51H can be read by removing the container 103 from the backing 700.

[0142] <3. Addendum>

[0143] The present invention is not limited to the above embodiments, and various modifications are possible. [Explanation of symbols]

[0144] 1: Code number 10: Token distribution system 15: Network 20: Blockchain 21: Contract Address 22: Smart Contracts 25A: Blockchain Account 25B: Blockchain Account 31: Terminal 51: Server 51A: Processor 51B: Storage device 51C: Computer Program 51D: Distribution process 51E: Token Code List 51F: URI Table 51G: Label design data 51H: QR code 60: Manufacturing equipment 101: Shrink film 103: Container 105: Product 107: Cap 120 :URI 121: Scheme 123A: Host 123B: Contract Information 123C: Token code 200: Film body 200A: Surface 200B: Back side 201: First print layer 201A :Area 201B :Area 202: Second Print Layer 203: Third Print Layer 204: Fourth print layer 205: Fifth Print Layer 310: Token Table 410: Non-fungible tokens 420: Token 430: Token 450: Fungible Token 500: Film body 500A: Surface 500B: Back side 501: First side 502: Second side 503: Third side 504: Fourth side 505: Boundary 510: External part 511: Perforation 512: Perforation 530: 1st area 530A: Overlap area 540:Second area 551: Perforation 552: Perforation 600: Film body 600A: Surface 600B: Back side 601: First side 602: Second side 603: Third side 604: Fourth side 609:Product manufacturing equipment 610: Printing System 611:Print management device 611A: Processor 611B: Storage device 611C: Computer program 611D: Printing process 611E: Interface 613 :Printing device 620: Manufacturing equipment 621: Bottling System 622: Shrink wrapper 630: Body area 640: Cap area 650: 1st removal area 660: 2nd extraction part 700: Cardboard backing 710: Adhesive 720: Adhesive C1: Token code C2: Token code C3: Token code

Claims

1. A method for manufacturing multiple identical products packaged with packaging material, The process of preparing the product itself to be packaged with packaging materials, The process of preparing the aforementioned packaging material, A step of packaging the product body with the aforementioned packaging material, Equipped with, The process of preparing the packaging material is as follows: The process of generating multiple unique codes, The process includes storing the aforementioned multiple unique codes in a storage device for the printing system of the packaging material, and storing them in a token distribution system as registered codes. A step of printing the plurality of unique codes stored in the storage device onto the packaging material using the printing system, Equipped with, The process of packaging the product body with the packaging material includes packaging the product body with each of the multiple different packaging materials on which the unique code is printed, thereby manufacturing multiple identical products each having the unique code. The aforementioned token distribution system Determine whether the received code received from the code sender via the network is the same as the registered code. If the received code is the same as the registered code, the system is configured to use a table that associates the registered code with the non-fungible token identifier to determine which non-fungible token in the blockchain having the non-fungible token identifier corresponding to the received code should be sent, and then send the determined token to the code sender. The manufacturing method of the product.

2. The aforementioned table further associates the registered code with the quantity of fungible tokens. The token distribution system is configured to determine, using the table, the non-fungible tokens or the specified quantity of fungible tokens in the blockchain as the tokens to be sent when the received code is the same as the registered code. A method for manufacturing the product described in claim 1.

3. The token distribution system comprises a server and a smart contract executed on the blockchain. The aforementioned server, The system receives the received code via the network and determines whether the received code is the same as the registered code. If the received code is the same as the registered code, the smart contract is invoked to send the token to be sent as determined by the smart contract to the code sender. A method for manufacturing the product according to claim 1 or 2.

4. A method for manufacturing multiple identical products packaged with packaging material, The process of preparing the product itself to be packaged with packaging materials, The process of preparing the aforementioned packaging material, A step of packaging the product body with the aforementioned packaging material, Equipped with, The process of preparing the packaging material is as follows: The process of generating multiple unique codes, The process includes storing the aforementioned multiple unique codes in a storage device for the printing system of the packaging material, and storing them in a token distribution system as registered codes. A step of printing the plurality of unique codes stored in the storage device onto the packaging material using the printing system, Equipped with, The process of packaging the product body with the packaging material includes packaging the product body with each of the multiple different packaging materials on which the unique code is printed, thereby manufacturing multiple identical products each having the unique code. The aforementioned token distribution system Determine whether the received code received from the code sender via the network is the same as the registered code. If the received code is the same as the registered code, the system is configured to generate a non-fungible token as the token to be sent, and to send the generated non-fungible token to the code sender. The manufacturing method of the product.

5. The aforementioned token distribution system comprises a server and a smart contract executed on the blockchain. The aforementioned server, The system receives the received code via the network and determines whether the received code is the same as the registered code. If the received code is the same as the registered code, the smart contract is invoked to send the token generated by the smart contract to the code sender. A method for manufacturing the product described in claim 4.

6. The unique code is not visible in the product when it is packaged by the packaging material, and is positioned to become visible when at least a portion of the packaging is removed. A method for manufacturing the product according to any one of claims 1 to 5.

7. A manufacturing system for multiple identical products packaged with packaging material, A means of generating multiple unique codes, A storage device for storing the aforementioned multiple unique codes as printable codes, A token distribution system that stores the aforementioned code as a registered code, Means for printing the plurality of unique codes stored in the memory device onto the packaging material, A means for manufacturing a plurality of identical products, each having the unique code printed on it, by packaging the product body with a plurality of different packaging materials on which the unique code is printed, Equipped with, The token distribution system in which the registered code is stored is: Determine whether the received code received from the code sender via the network is the same as the registered code. If the received code is the same as the registered code, the system is configured to use a table that associates the registered code with the non-fungible token identifier to determine which non-fungible token in the blockchain having the non-fungible token identifier corresponding to the received code should be sent, and then send the determined token to the code sender. Product manufacturing system.

8. A manufacturing system for multiple identical products packaged with packaging material, A means of generating multiple unique codes, A storage device for storing the aforementioned multiple unique codes as printable codes, A token distribution system that stores the aforementioned code as a registered code, Means for printing the plurality of unique codes stored in the memory device onto the packaging material, A means for manufacturing a plurality of identical products, each having the unique code printed on it, by packaging the product body with a plurality of different packaging materials on which the unique code is printed, Equipped with, The token distribution system in which the registered code is stored is: Determine whether the received code received from the code sender via the network is the same as the registered code. If the received code is the same as the registered code, the system is configured to generate a non-fungible token as the token to be sent, and to send the generated non-fungible token to the code sender. Product manufacturing system.

Images