System, computer device, program, and method

Abstract

To provide a system for issuing an NFT in association with data related to a flower bed.SOLUTION: A system that has at least one computer device, includes: flower bed data generation means for generating flower bed data related to a flower bed; and NFT issue means for controlling an issuance of an NFT (non-fungible token) associated with the generated flower bed data. The flowerbed data includes information on flowerbed shape, flowerbed size, plant color, plant type, and / or plant arrangement.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a system, a computer device, a program, and a method. [Background technology]

[0002] 2. Description of the Related Art Traditionally, flower beds have been created by designing the colors, types, and arrangement of plants to be planted in the flower bed.

[0003] Also, a flower bed can be designed using a system. For example, Patent Document 1 discloses a system that allows a user terminal to determine the shape, size, color, type, and / or layout of a flower bed.

[0004] Furthermore, in recent years, businesses have been established that sell digital data such as digital art. In order to prove the non-fungibility of digital data, non-fungible tokens (NFTs) are being issued in association with the digital data. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] JP 2019-36145 A Summary of the Invention [Problem to be solved by the invention]

[0006] The object of the present invention is to provide a system for issuing NFTs in association with data regarding flower beds. [Means for solving the problem]

[0007] According to the present invention, the above object is achieved by: [1] A system comprising at least one computer device, the system comprising: a flowerbed data generating means for generating flowerbed data relating to a flowerbed; and an NFT issuing means for controlling the issuance of an NFT (non-fungible token) associated with the generated flowerbed data, the flowerbed data including information on a shape of the flowerbed, a size of the flowerbed, a color of the plants, a type of the plants, and / or an arrangement of the plants; [2] The system according to [1], comprising an NFT sales means for controlling the NFT and the flowerbed data to be made available for purchase; [3] The system according to [1] or [2], further comprising an owner storage means for storing information about an owner of the NFT in association with the NFT; [4] A system according to any one of [1] to [3], comprising an information transmission means for transmitting information from a terminal operated by an NFT holder to a terminal operated by a flowerbed designer corresponding to the flowerbed data associated with the NFT; [5] The system according to any one of [1] to [4], comprising a flowerbed order receiving means for receiving orders from an NFT holder for goods and / or services corresponding to the flowerbed data associated with the NFT; [6] A system according to any one of [1] to [5], comprising an order benefit storage means for storing information regarding the granting of benefits to the flowerbed designer corresponding to the flowerbed data, the generator of the flowerbed data, and / or a holder who previously held the NFT, when an order for a product and / or service corresponding to the flowerbed data associated with the NFT is received by the flowerbed order receiving means; [7] A system according to any one of [1] to [6], comprising a purchase benefit storage means for storing information regarding the granting of benefits to the designer of the flowerbed corresponding to the flowerbed data, the generator of the flowerbed data, and / or a holder who previously held the NFT, when an NFT and flowerbed data are purchased; [8] A system described in any of [1] to [7], further comprising a determination means for determining whether the generated flowerbed data has a predetermined relationship with flowerbed data associated with a previously issued NFT, and controlling the NFT issuing means to issue an NFT associated with the generated flowerbed data when the determination means determines that the predetermined relationship does not exist; [9] A computer device comprising: a flowerbed data generation means for generating flowerbed data relating to a flowerbed; and an NFT issuance means for controlling the issuance of an NFT (non-fungible token) associated with the generated flowerbed data, wherein the flowerbed data includes information regarding a shape of the flowerbed, a size of the flowerbed, a color of the plants, a type of the plants, and / or an arrangement of the plants;

[10] A program for causing a computer device to function as a flowerbed data generating means for generating flowerbed data relating to a flowerbed, and an NFT issuing means for controlling the computer device to issue an NFT (non-fungible token) associated with the generated flowerbed data, the flowerbed data including information on the shape of the flowerbed, the size of the flowerbed, the color of the plants, the type of the plants, and / or the arrangement of the plants;

[11] A method comprising: a flowerbed data generation step of generating flowerbed data relating to a flowerbed; and an NFT issuance step of controlling the issuance of an NFT (non-fungible token) associated with the generated flowerbed data, wherein the flowerbed data includes information on the shape of the flowerbed, the size of the flowerbed, the color of the plants, the type of the plants, and / or the arrangement of the plants; This can be achieved by: Effect of the Invention

[0008] According to the present invention, a system can be provided for issuing NFTs in association with data regarding flower beds. [Brief description of the drawings]

[0009] [Figure 1] 1 is a block diagram showing a configuration of a system according to an embodiment of the present invention; [Diagram 2] FIG. 2 is a block diagram showing a hardware configuration of a designer terminal according to the embodiment of the present invention. [Diagram 3]FIG. 2 is a block diagram showing a hardware configuration of a server device according to an embodiment of the present invention. [Figure 4] 11 is a flowchart of a flowerbed data generation process according to an embodiment of the present invention. [Diagram 5] FIG. 13 is a diagram illustrating an example of an execution screen according to an embodiment of the present invention. [Figure 6] FIG. 13 is a diagram illustrating an example of an execution screen according to an embodiment of the present invention. [Figure 7] FIG. 13 is a diagram illustrating an example of an execution screen according to an embodiment of the present invention. [Figure 8] FIG. 13 is a diagram illustrating an example of an execution screen according to an embodiment of the present invention. [Figure 9] 1 is a flowchart of an NFT issuing process according to an embodiment of the present invention. [Figure 10] 1 is a flowchart of an NFT listing process according to an embodiment of the present invention. [Figure 11] 1 is a flowchart of an NFT purchasing process according to an embodiment of the present invention. [Figure 12] 11 is a flowchart of a privilege providing process according to an embodiment of the present invention. [Figure 13] 4 is a flowchart of information transmission and reception processing according to an embodiment of the present invention. [Figure 14] 11 is a flowchart of an order receiving process according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] The following describes an embodiment of the present invention, but the present invention is not limited to the following embodiment, as long as it does not go against the spirit of the present invention. The order of each process constituting the flowchart described below is random as long as there is no contradiction or inconsistency in the process content, and it is also possible to omit a part of each process constituting the flowchart or add a new process to each process constituting the flowchart, as long as there is no contradiction or inconsistency in the process content. In addition, the device that executes each process constituting the flowchart can be changed to another device, as long as it does not go against the spirit of the present invention. In that case, the process content can be changed so that there is no contradiction or inconsistency in the process content.

[0011] Fig. 1 is a block diagram showing a configuration of a system according to an embodiment of the present invention. In Fig. 1, the system 1 includes a designer terminal 2, a user terminal 3, a server device 4, and a block chain 5. The designer terminal 2, the user terminal 3, the server device 4, and the block chain 5 may be communicatively connected to each other via a communication network 6.

[0012] The designer terminal 2 may be operated by a designer who designs a flower bed. The designer may be a user who uses the system 1, an administrator who manages the system 1, or a designer who designs a flower bed at the request of the administrator who manages the system 1. The designer terminal 2 may be operated by a person who receives a request from the designer. A dedicated application (hereinafter also referred to as a dedicated app) for using the system 1 may be installed in the designer terminal 2.

[0013] Here, a "flower bed" refers to a place where plants are planted or a place where plants are planted. The plants may include flowers, grass, trees, etc. Furthermore, the purpose of planting plants may be to grow them or to appreciate them. The flower bed may be separated by a partition material such as bricks, stones, wood, synthetic resin, etc., or it may not be separated. Furthermore, the flower bed may have a step from the soil adjacent to the flower bed, or it may not have a step. The flower bed may be at least a part of a garden, a park, etc. Furthermore, the flower bed may refer to the entire flower bed, or it may refer to a part of the flower bed.

[0014] The user terminal 3 may be operated by a user who uses the system 1. In addition, the user terminal 3 may have a dedicated application installed therein.

[0015] A user of system 1 can use the same terminal to design a flower bed and purchase flower bed data relating to a flower bed designed by another designer. When the user designs a flower bed, the terminal operated by the user can be considered to function as a designer terminal 2. On the other hand, when the user purchases flower bed data relating to a flower bed designed by another designer, the terminal operated by the user can be considered to function as a user terminal 3.

[0016] The server device 4 may function in a distributed manner across multiple computer devices. For example, a distributed ledger technology such as a blockchain may be used instead of the server device 4. In this case, the blockchain that performs the function instead of the server device 4 may be the same as the blockchain 5 or may be different from the blockchain 5.

[0017] There are no particular limitations on the blockchain 5, and any known blockchain can be used. The blockchain 5 may be a public blockchain or a private blockchain.

[0018] The server device 4 and the blockchain 5 may be managed by the same administrator, or may be managed by different administrators.

[0019] Although not shown, the system 1 may also include an administrator terminal operated by an administrator. The administrator terminal may be capable of communicating with the designer terminal 2, the user terminal 3, the server device 4, and the blockchain 5 via a communication network 6. An application for managing the system 1 may also be installed in the administrator terminal.

[0020] Furthermore, although not shown, the system 1 may include a plurality of designer terminals 2, user terminals 3, and / or manager terminals.

[0021] 2 is a block diagram showing a hardware configuration of a designer terminal according to an embodiment of the present invention. The designer terminal 2 includes a control unit 21, a RAM 22, a storage unit 23, an input unit 24, a display unit 25, and a communication interface 26, which are all connected to each other via a bus.

[0022] The control unit 21 is composed of a CPU and a ROM. The control unit 21 executes programs stored in the storage unit 23 and controls the designer terminal 2. The RAM 22 is a work area for the control unit 21. The storage unit 23 is a storage area for saving programs and data. In other words, the storage unit 23 functions as a recording medium that stores programs. The control unit 21 performs arithmetic processing based on the programs and data read from the RAM 22 and the data inputted by the input unit 24.

[0023] The display unit 25 has a display screen. The control unit 21 outputs a video signal for displaying an image on the display screen according to the result of the arithmetic processing. Here, the display screen of the display unit 25 may be a touch panel equipped with a touch sensor. In this case, the touch panel functions as the input unit 24.

[0024] The communication interface 26 can be connected to the communication network 6 wirelessly or via a wire, and can transmit and receive data to and from other computer devices via the communication network 6. Data received via the communication interface 26 is loaded into the RAM 22, and the control unit 21 performs arithmetic processing on the data.

[0025] The hardware configuration of the user terminal 3 may be appropriately adapted from the description of the hardware configuration of the designer terminal 2. In addition, if the system 1 includes an administrator terminal, the hardware configuration of the administrator terminal may be appropriately adapted from the description of the hardware configuration of the designer terminal 2.

[0026] 3 is a block diagram showing a hardware configuration of a server device according to an embodiment of the present invention. The server device 4 includes at least a control unit 41, a RAM 42, a storage unit 43, and a communication interface 44, which are connected to each other via an internal bus.

[0027] The control unit 41 is composed of a CPU and a ROM, and executes the programs stored in the storage unit 43 to control the server device 4. The control unit 41 also has an internal timer that measures time. The RAM 42 is the work area of ​​the control unit 41. The storage unit 43 is a storage area for saving programs and data. In other words, the storage unit 43 functions as a recording medium that stores programs. The control unit 41 reads out the programs and data from the RAM 42, and performs program execution processing based on information received from the designer terminal 2, the user terminal 3, the block chain 5, the administrator terminal, etc.

[0028] The program may be stored in a recording medium such as a CD-ROM. In this case, the program stored in the recording medium may be installed in the designer terminal 2, the user terminal 3, the server device 4, the block chain 5, and / or the administrator terminal to execute a predetermined function.

[0029] Alternatively, the program may be distributed from a computer device outside the system. In this case, the program distributed from the computer device outside the system may be installed in the designer terminal 2, the user terminal 3, the server device 4, the blockchain 5, and / or the administrator terminal to execute a predetermined function.

[0030] An example will be described below in which a user designs a flower bed, generates flower bed data, buys and sells flower bed data, etc., on a dedicated app. A user (designer) can start up the dedicated app and log in to the system 1. When a user logs in to the system 1 for the first time, the user may perform user registration. When performing user registration, the user may input information about the user, such as the user's name, sex, age, date of birth, and address. By performing user registration, the system 1 may assign identification information for identifying the user to the user. When a user logs in to the system 1, the user may be required to input identification information, a password, etc. The password may be set by the user.

[0031] [Flowerbed data generation process] First, a description will be given of an aspect in which a user (designer) designs a flowerbed on a dedicated application and generates flowerbed data. Fig. 4 is a flowchart of a flowerbed data generation process according to an embodiment of the present invention.

[0032] First, the designer terminal 2 accepts input of information regarding the shape and / or size of the flower bed (step S101). Next, the designer terminal 2 accepts input of information regarding the color of the plants, the type of the plants, and / or the arrangement of the plants (step S102). The input information regarding the flower bed is transmitted from the designer terminal 2 to the server device 4 (step S103). The server device 4 receives the transmitted information regarding the flower bed (step S104). The server device 4 generates flower bed data based on the received information regarding the flower bed (step S105). The server device 4 stores the generated flower bed data (step S106). The server device 4 transmits information regarding the flower bed data from the server device 4 to the designer terminal 2 (step S107). The designer terminal 2 receives the transmitted information regarding the flower bed data (step S108). The designer terminal 2 outputs the received information regarding the flower bed data (step S109), and the flower bed data generation process ends.

[0033] The shape of the flower bed in step S101 may be the shape of the flower bed when viewed from above, the shape of the flower bed when viewed obliquely, the shape of the flower bed when viewed from the side, or the three-dimensional shape of the flower bed. Also, the size of the flower bed in step S101 may include the width (horizontal length), depth (vertical length), height, etc. of the flower bed.

[0034] The arrangement of the plants in step S102 may be the arrangement of the plants in the flower bed corresponding to the information input in step S101.

[0035] The information on the flower bed shape, the size of the flower bed, the color of the plants, the type of the plants, and / or the arrangement of the plants input in steps S101 to S102 is information on the flower bed. The information on the flower bed may be information that enables the flower bed to be actually created. The input of the information on the flower bed in steps S101 to S102 may be performed on a screen for designing a flower bed, such as those shown in Figs. 5 to 7.

[0036] Fig. 5 is a diagram showing an example of an execution screen according to an embodiment of the present invention. The execution screen 100 shown in Fig. 5 is an example of a screen for inputting information on the shape and size of a flower bed (hereinafter, also referred to as a flower bed shape input screen).

[0037] When a designer designs a flowerbed, a flowerbed shape input screen as shown in Fig. 5 may first be displayed as an execution screen 100 on the display screen of the designer terminal 2. The flowerbed shape input screen shown in Fig. 5 is made up of a plurality of square cells 101, and displays a flowerbed shape input area 102 for inputting the shape of the flowerbed, a length input field 103 for inputting the actual length corresponding to the length of one side of the cells 101, and a decision button 104 for finalizing the input information.

[0038] The designer may input the shape of the flower bed by selecting at least one of the squares 101 constituting the flower bed shape input area 102. For example, the shape formed by the selected squares 101 may be input as the shape of the flower bed.

[0039] In Fig. 5, it is assumed that a total of six squares 101a to 101f, three horizontally and two vertically, are selected. The selected squares 101 may be displayed in a manner different from that of the unselected squares 101. In Fig. 5, the selected squares 101a to 101f are displayed in a color different from that of the unselected squares 101.

[0040] The six selected squares 101a to 101f form a rectangle with a ratio of width to length of 3:2 (width:length). Therefore, in this case, a rectangle with a ratio of width to length of 3:2 (width:length) may be input as the shape of the flower bed. It is assumed here that a rectangle with a ratio of width to length of 3:2 (width:length) has been input as the shape of the flower bed when viewed from above. Although not shown, the flower bed shape input screen may display a field for inputting the angle from which the shape is viewed.

[0041] The designer may also input the size of the flower bed by inputting an actual length corresponding to the length of one side of the square 101 in the length input field 103. For example, the size of the flower bed when the length input in the length input field 103 is the length of one side of the selected square 101 may be input as the size of the flower bed.

[0042] 5, the length input field 103 displays that the actual length corresponding to the length of one side of the square 101 is 50 cm. Therefore, in this case, the size of the flower bed entered is 150 cm in width when viewed from above, and 100 cm in length when viewed from above. The length input field 103 may be one in which the length can be entered by selecting the number 1 from the numbers displayed in a pull-down menu, or one in which the length can be entered by directly entering the number.

[0043] When the decision button 104 is pressed after input has been made in the flowerbed shape input area 102 and the length input field 103, input of information regarding the shape and size of the flowerbed may be accepted in step S101.

[0044] Fig. 6 is a diagram showing an example of an execution screen according to an embodiment of the present invention. The execution screen 200 shown in Fig. 6 is an example of a screen for inputting information regarding the color of a plant and the arrangement of the plant (hereinafter, also referred to as a plant arrangement input screen).

[0045] After the input is accepted in step S101, a plant arrangement, etc. input screen as shown in Fig. 6 may be displayed as an execution screen 200 on the display screen of the designer terminal 2. The plant arrangement, etc. input screen shown in Fig. 6 displays square cells 201 (201a to 201f) corresponding to the shape of the flower bed input in step S101, a color selection start button 202 for starting color selection for the cells 201, a color palette 203 for selecting the color of the cells 201, and a confirmation button 204 for finalizing the input information.

[0046] A color palette 203 may be displayed by pressing a color selection start button 202 in a state where at least one of square cells 201 corresponding to the shape of the flower bed is selected on the plant arrangement input screen. The designer can select a color to be assigned to the selected cell 201 from the colors displayed as the color palette 203. The cell 201 to which a color has been assigned may be displayed with the assigned color. In the flower bed, a plant having the assigned color may be placed in the position of the cell 201 to which a color has been assigned.

[0047] For example, in FIG. 6, the same color is assigned to the three upper squares 201a to 201c among the six squares 201a to 201f. The same color is assigned to the two lower squares 201d to 201e on the left and in the center. The colors assigned to the squares 201a to 201c are different from the colors assigned to the squares 201d to 201e. Therefore, in the flower bed, different plant colors are input at the positions corresponding to the squares 201a to 201c and the positions corresponding to the squares 201d to 201e. The arrangement of the squares 201a to 201c or the squares 201d to 201e in the six squares 201a to 201f is input as the arrangement of the respective plants.

[0048] 6, no color is assigned to the square 201f on the right side of the lower row. Plants may not be placed in positions corresponding to the squares 201 to which no color is assigned. Alternatively, colors may be assigned to all the squares 201.

[0049] When a color has been assigned to at least one of the squares 201, the enter button 204 may be pressed to confirm the input information regarding the color of the plants and the arrangement of the plants.

[0050] Fig. 7 is a diagram showing an example of an execution screen according to an embodiment of the present invention. The execution screen 300 shown in Fig. 7 is an example of a screen for inputting information about the type of plant (hereinafter, also referred to as a plant type input screen).

[0051] After the color of the plant and the information on the arrangement of the plant are confirmed, a plant type input screen as shown in Fig. 7 may be displayed as an execution screen 300 on the display screen of the designer terminal 2. The plant type input screen shown in Fig. 7 displays a selection target color display field 301 that displays the color of the plant being selected, a plant image display field 302 that displays an image of the plant, a plant information display field 303 that displays information about the plant, and a confirmation button 304 for confirming the displayed information.

[0052] The color of the plant to be selected may be displayed in a manner that allows the designer to understand the color in the selection target color display field 301. In Fig. 7, a comment "Please select a yellow flower" is displayed in the selection target color display field 301. Therefore, the designer knows that he or she should select a type of plant that has a yellow color.

[0053] The color of the plant to be selected may be any of the colors of the plants input on the plant arrangement input screen. Also, on the plant type input screen, it may be possible to change the color of the plant to be selected, which is displayed in the selection target color display field 301. For example, when the selection target color display field 301 is pressed, the colors of the plants input on the plant arrangement input screen may be displayed in a list. The designer can select any color from the displayed list.

[0054] The plant image display field 302 may display an image of a plant having the color displayed in the selection target color display field 301. Furthermore, the plant information display field 303 may display information about the plant displayed in the plant image display field 302.

[0055] Here, the "color of a plant" may be any color that is contained in at least a part of the plant. For example, the "color of a plant" may be the color of the petals, leaves, or sepals of the plant. The "color of a plant" may be the color of a prominent part of the plant. The prominent part of the plant may be a part located at the top of the plant, a part located on the surface of the plant, a part that occupies a large volume of the plant, or a part that occupies a large surface area of ​​the plant.

[0056] The plant information displayed in the plant information display field 303 is not particularly limited and can be designed as appropriate. The plant information displayed in the plant information display field 303 may be information that is useful when actually creating a flower bed. For example, in FIG. 7, the plant information display field 303 displays the name of the plant as "yellow cosmos", the plant's sowing season as "April to August", the plant's flowering season as "July to October", the plant's height as "70 cm", the area required for the plant's growth as "XX cm", and so on. 2 " and the ratio of flowers to leaves of the plant is "4:5." For example, in addition to the above, the plant's information may also include the shade tolerance of the plant, the difficulty of cultivating the plant, and the price of the plant.

[0057] Furthermore, the type of plant displayed in the plant image display field 302 and the plant information display field 303 may be changeable by an operation of the designer. For example, when the plant type input screen is swiped, the type of plant displayed in the plant image display field 302 and the plant information display field 303 may be changed. The designer can select any type of plant by changing the type of plant displayed.

[0058] Alternatively, the plant type input screen may display a plurality of plant image display fields 302 and plant information display fields 303. The designer can select any plant type from the plurality of displayed plant types.

[0059] The plant image displayed in the plant image display field 302 and the plant information displayed in the plant information display field 303 may be stored in the storage unit 43 of the server device 4. It is preferable that the plant image and the plant information are stored in association with each other. It is also preferable that the "color of the plant" is stored in association with the plant image and the plant information.

[0060] Although not shown, the designer may be able to input a desired plant sowing time and / or flowering time of the plant on the plant type input screen. Then, the plant image display field 302 and the plant information display field 303 may display an image of the plant and information of the plant according to the input plant sowing time and / or flowering time of the plant.

[0061] When the decision button 304 is pressed, the type of plant displayed in the plant image display field 302 and the plant information display field 303 may be input as a plant having the color displayed in the selection target color display field 301. Also, the input type of plant may be arranged in the square 201 corresponding to the color displayed in the selection target color display field 301.

[0062] When two or more plant colors are input on the plant arrangement input screen, after one type of plant is input for one color, it may be possible to select the type of plant corresponding to the other color.

[0063] It may also be possible to input two or more types of plants for one color. In this case, it may be possible to further input how to arrange the two or more types of plants that have been input.

[0064] When plant types have been entered for all plant colors entered on the plant placement, etc. input screen, that is, when the decision button 304 is pressed with the plant corresponding to the last color that can be selected being displayed, input of information regarding the plant color, plant type, and plant placement may be accepted in step S102.

[0065] After input of information regarding the flower bed, such as the shape of the flower bed, the size of the flower bed, the color of the plants, the type of plants, and / or the arrangement of the plants, has been accepted, the designer may be able to check the input information regarding the flower bed on the designer terminal 2.

[0066] Fig. 8 is a diagram showing an example of an execution screen according to an embodiment of the present invention. The execution screen 400 shown in Fig. 8 is an example of a screen for confirming the input information about the flower bed (hereinafter, also referred to as an input content confirmation screen).

[0067] After step S102, an input content confirmation screen as shown in Fig. 8 may be displayed as an execution screen 400 on the display screen of the designer terminal 2. The input content confirmation screen shown in Fig. 8 displays an image display field 401 that displays an image of a flower bed to confirm the inputted information about the flower bed, a time change meter 402 for changing the time corresponding to the displayed image of the flower bed, viewpoint change buttons 403 (403a to 403d) for changing the viewpoint from which the image of the flower bed is displayed, and a save button 404 for storing the inputted information about the flower bed.

[0068] The image of the flower bed displayed in the image display field 401 may be drawn based on the input information about the flower bed. When drawing the image of the flower bed, photo data of corresponding plants may be arranged for each area constituting the flower bed based on the input shape of the flower bed, size of the flower bed, color of the plants, type of the plants, and / or arrangement of the plants. Then, the image of the flower bed may be drawn by performing perspective transformation with a virtual camera on the virtual space in which the photo data is arranged.

[0069] The photo data may be stored in the storage unit 43 of the server device 4. The photo data may be the same as or different from the image of the plant displayed in the plant image display field 302. When the photo data and the image of the plant displayed in the plant image display field 302 are different, it is preferable that the photo data and the image of the plant displayed in the plant image display field 302 are stored in association with each other.

[0070] Photo data of plants photographed at multiple time periods and photo data of plants photographed from multiple viewpoints may be stored in storage unit 43. By storing photo data of plants photographed at multiple time periods and photo data of plants photographed from multiple viewpoints as photo data, it becomes possible to display an image of a flower bed corresponding to a predetermined time period and an image of a flower bed shot from a predetermined viewpoint in image display field 401.

[0071] The designer may be able to change the time corresponding to the image of the flowerbed displayed in the image display field 401 by operating the time change meter 402. For example, the designer may be able to change the time by operating, for example, swiping on the time change meter 402. Also, a display for understanding the time corresponding to the image of the flowerbed may be provided on the time change meter 402. For example, in FIG. 8, the time change meter 402 is displayed in the shape of a double-headed arrow. Also, in FIG. 8, a short line segment is displayed slightly to the left of the center of the double-headed arrow so as to overlap perpendicularly with the line segment of the double-headed arrow. When the line segment of the double-headed arrow corresponds to a time of year, and the left end of the double-headed arrow indicates January and the right end of the double-headed arrow indicates December, the designer can understand that the image of the flowerbed displayed corresponds to the time of April.

[0072] Also, the designer may be able to change the viewpoint for displaying the image of the flower bed displayed in the image display field 401 by operating the viewpoint change button 403. For example, the designer may be able to change the viewpoint by operating the viewpoint change button 403 or the like. In FIG. 8, the viewpoint may be moved to the left by pressing the viewpoint change button 403a. Also, the viewpoint may be moved up by pressing the viewpoint change button 403b. Furthermore, the viewpoint may be moved down by pressing the viewpoint change button 403c. Also, the viewpoint may be moved to the right by pressing the viewpoint change button 403d. The viewpoint may be changed discontinuously or continuously at a predetermined angle.

[0073] Alternatively, the image of the flower bed may be drawn by computer graphics based on the inputted shape of the flower bed, the size of the flower bed, the color of the plants, the type of the plants, and / or the arrangement of the plants. Also, the image display field 401 may display an image of the flower bed corresponding to a predetermined time drawn by computer graphics, and an image of the flower bed taken from a predetermined viewpoint.

[0074] The designer can determine whether there is any problem with the input information about the flower bed by checking the image of the flower bed displayed in image display field 401. If there is no problem with the input information about the flower bed, the designer may press save button 404. When save button 404 is pressed, the input information about the flower bed may be transmitted in step S103.

[0075] In the above example, the shape of the grid for inputting the shape of the flower bed is a square, but the shape of the grid is not particularly limited and can be designed appropriately. The shape of the grid may be, for example, a rectangle, a triangle, or a hexagon.

[0076] In the above, an example was given in which the shape of a flower bed was input by selecting a square, but the manner in which the shape of a flower bed is input is not particularly limited and can be designed as appropriate. For example, the shape of a flower bed may be input by drawing the flower bed using computer graphics. The flower bed drawn using computer graphics may be two-dimensional or three-dimensional. In this case, the actual length of each side of the drawn flower bed may be input as the size of the flower bed. Furthermore, the arrangement of plants may be input by arranging and drawing plants using computer graphics. In this case, the color and / or type of plants may be input by appropriately changing the color and / or type of the arranged plants using computer graphics.

[0077] In addition, in the above, an embodiment has been described in which information regarding the shape of the flower bed and / or the size of the flower bed is input in step S101, and information regarding the color, type of plant, and / or arrangement of plants is input in step S102, but the order in which information regarding the shape of the flower bed, the size of the flower bed, the color, type of plant, and / or arrangement of plants is input is not particularly limited and can be designed as appropriate.

[0078] Also, at least a part of the information on the shape of the flower bed, the size of the flower bed, the color of the plants, the type of the plants, and the arrangement of the plants may not be input. For example, the information on the flower bed may be information on the color of the plants and the arrangement of the plants, information on the type of the plants and the arrangement of the plants, information on the color of the plants, the type of the plants, and the arrangement of the plants, information on the size of the flower bed, the color of the plants, and the arrangement of the plants, information on the size of the flower bed, the type of the plants, and the arrangement of the plants, or information on the size of the flower bed, the color of the plants, the type of the plants, and the arrangement of the plants.

[0079] Further, in the above, a mode of inputting information about a flower bed on a screen for designing the flower bed has been described, but the mode of inputting information about the flower bed is not particularly limited and can be designed as appropriate. For example, a designer may actually design and create a flower bed, and input an image of the flower bed taken as information about the flower bed. The image may be a still image or a moving image. It is sufficient that the image includes at least a part of the flower bed. In this case, images of a plurality of flower beds may be input as information about the flower bed. The images of the plurality of flower beds may be a plurality of images taken at different angles of the flower bed, or a plurality of images taken at different times of the flower bed.

[0080] In addition, the image of the flower bed input as the information about the flower bed may be generated by AI (Artificial Intelligence). The AI ​​used in this case is not particularly limited as long as it is capable of generating images.

[0081] When an image of a flower bed is input as information about a flower bed, information about the shape of the flower bed, the size of the flower bed, the color of the plants, the type of plants, and / or the arrangement of the plants may be automatically extracted from the input image of the flower bed. Alternatively, when an image of a flower bed is input as information about a flower bed, information about the shape of the flower bed, the size of the flower bed, the color of the plants, the type of plants, and / or the arrangement of the plants may be input together with the image of the flower bed.

[0082] Furthermore, information other than the shape of the flower bed, the size of the flower bed, the color of the plants, the type of plants, and the information on the arrangement of the plants may be input as information on the flower bed. For example, the amount of plants required to create the flower bed (the number of seeds, the number of seedlings, etc.), the type of soil preferably used for the flower bed, the type of fertilizer preferably used for the flower bed, the partition material used to create the flower bed, the type of pot used to create the flower bed, the type of decoration used to create the flower bed, etc. may be input as information on the flower bed.

[0083] In addition, although the above describes an embodiment in which the designer designs a flower bed from scratch, the designer may design a flower bed based on a basic flower bed design. For example, the designer may input the shape of the flower bed, the size of the flower bed, the color of the plants, the type of plants, and / or the arrangement of the plants by modifying the basic flower bed design. The basic flower bed design may be input by the administrator, input by another designer, or automatically generated by the system 1.

[0084] The input information about the flowerbed is transmitted to the server device 4 in step S103. In step S103, identification information of the designer may be transmitted together with the information about the flowerbed.

[0085] In step S105, the server device 4 generates flowerbed data based on the received information on the flowerbed. The flowerbed data includes information on the shape of the flowerbed, the size of the flowerbed, the color of the plants, the type of the plants, and / or the arrangement of the plants. The flowerbed data may also include information on the amount of plants required to create the flowerbed (the number of seeds, the number of seedlings, etc.), the type of soil preferably used for the flowerbed, the type of fertilizer preferably used for the flowerbed, the partition material used to create the flowerbed, the type of pot used to create the flowerbed, the type of decoration used to create the flowerbed, and the like. Furthermore, the flowerbed data may include an image of the flowerbed. The image of the flowerbed may be drawn based on the information on the flowerbed, or may be input as an image.

[0086] The flower bed data may be data that enables handling of information about the flower bed in the dedicated app. Handling information about the flower bed may mean viewing information about the flower bed or storing information about the flower bed.

[0087] In step S106, the flowerbed data may be stored in the storage unit 43 of the server device 4 in association with information about the designer of the flowerbed corresponding to the flowerbed data. The information about the designer may be the same as the above-mentioned description of the information about the user to the extent necessary. The information about the designer may be stored in advance in the storage unit 43 of the server device 4.

[0088] Furthermore, in step S106, information relating to the date and time when the flowerbed data was generated in step S105 may be stored in association with the flowerbed data.

[0089] The information on the flowerbed data transmitted in step S107 may be at least a part of the information on the flowerbed data stored in step S106. Also, in step S107, information for outputting the information on the flowerbed data at the designer terminal 2 may be transmitted together with the information on the flowerbed data.

[0090] The manner in which the information on the flowerbed data is output in step S109 is not particularly limited and can be designed appropriately. For example, the information on the flowerbed data may be displayed on the display screen of the designer terminal 2.

[0091] The designer may be able to view the flowerbed data corresponding to the flowerbed he / she designed on a dedicated app at any time. The designer may be able to display multiple pieces of flowerbed data corresponding to flowerbeds he / she designed in the past on the display screen of the designer terminal 2.

[0092] Furthermore, the information on the flowerbed data may be viewable on a terminal other than the designer terminal 2. For example, the information on the flowerbed data may be viewable on the user terminal 3, the administrator terminal, or the like.

[0093] The flowerbed data stored in the server device 4 may be able to be modified by the designer as appropriate.

[0094] In the above, an embodiment has been described in which flowerbed data is generated based on information about the flowerbed input by the designer, but the flowerbed data may be generated without the designer having to input information about the flowerbed. For example, the flowerbed data may be generated by AI. The type of AI that generates the flowerbed data is not particularly limited and can be designed as appropriate. When the flowerbed data is generated by AI, the flowerbed data may be generated according to instructions input from an administrator terminal.

[0095] [NFT issuance process] According to the system 1, it is possible to issue an NFT (non-fungible token) in association with the generated flowerbed data. Fig. 9 is a flowchart of an NFT issuance process according to an embodiment of the present invention.

[0096] First, the designer selects the flowerbed data to be associated with the NFT. The designer terminal 2 accepts the selection of the flowerbed data (step S201). Next, the designer terminal 2 accepts the input of a request to issue an NFT in association with the selected flowerbed data (hereinafter also referred to as an NFT issuance request) (step S202). The NFT issuance request is transmitted from the designer terminal 2 to the server device 4 (step S203). The server device 4 receives the transmitted NFT issuance request (step S204). The server device 4 determines whether the flowerbed data corresponding to the received NFT issuance request has a predetermined relationship with flowerbed data associated with a previously issued NFT (hereinafter, past NFT flowerbed data) (step S205).

[0097] If it is determined in step S205 that the flowerbed data corresponding to the received NFT issuance request has a predetermined relationship with past NFT flowerbed data (YES in step S205), information indicating that the NFT cannot be issued is transmitted from the server device 4 to the designer terminal 2 (step S206). The designer terminal 2 receives the transmitted information indicating that the NFT cannot be issued (step S207). The designer terminal 2 outputs information indicating that the NFT cannot be issued (step S208), and the NFT issuance process ends.

[0098] On the other hand, if it is not determined in step S205 that the flowerbed data corresponding to the received NFT issuance request has a predetermined relationship with past NFT flowerbed data (NO in step S205), a request to issue an NFT is made in the server device 4 (step S209). Then, in the blockchain 5, an NFT associated with the flowerbed data is issued (step S210). In the blockchain 5, the issued NFT is stored (step S211). Information about the NFT is transmitted from the blockchain 5 to the server device 4 (step S212). In the server device 4, information about the transmitted NFT is received (step S213). In the server device 4, information about the received NFT is stored (step S214). Information about the NFT is transmitted from the server device 4 to the designer terminal 2 (step S215). In the designer terminal 2, information about the transmitted NFT is received (step S216). Information regarding the received NFT is output at the designer terminal 2 (step S217), and the NFT issuance process ends.

[0099] In step S201, the designer can select flowerbed data to be associated with the NFT from among the flowerbed data corresponding to the flowerbeds that the designer has designed. For example, the designer may select the flowerbed data to be associated with the NFT by displaying information on the flowerbed data corresponding to the flowerbeds that the designer has designed on the display screen of the designer terminal 2.

[0100] When displaying information on flowerbed data corresponding to a flowerbed designed by the designer himself / herself, a button for inputting an NFT issuance request may be displayed on the display screen of the designer terminal 2 together with information on the flowerbed data. When the button for inputting an NFT issuance request is pressed, input of the NFT issuance request may be accepted in step S202. In this case, when the button for inputting an NFT issuance request is pressed, the NFT issuance request may be input in association with the flowerbed data corresponding to the information on the flowerbed data displayed on the display screen of the designer terminal 2.

[0101] The "predetermined relationship" in step S205 is not particularly limited as long as it is a relationship used to determine whether or not to issue an NFT. For example, the "predetermined relationship" may be an "identical or similar relationship."

[0102] Two flower bed data being in the same relationship may mean, for example, that all of the information on the shape of the flower bed, the size of the flower bed, the color of the plants, the type of the plants, and / or the arrangement of the plants contained in the two flower bed data is the same. Also, two flower bed data being in a similar relationship may mean, for example, that more than half of the information on the shape of the flower bed, the size of the flower bed, the color of the plants, the type of the plants, and / or the arrangement of the plants contained in the two flower bed data is the same.

[0103] Alternatively, whether two pieces of flowerbed data are identical or similar may be determined by a program for determining images, such as AI. For example, the AI ​​may calculate the similarity of flowerbed images drawn based on two pieces of flowerbed data, and if the similarity is equal to or greater than a predetermined value, it may be determined that the two pieces of flowerbed data are identical or similar.

[0104] In step S205, it may be determined whether or not some or all of the past NFT flowerbed data has a predetermined relationship with the flowerbed data corresponding to the NFT issuance request received in step S204. The past NFT flowerbed data may be stored in the storage unit 43 of the server device 4.

[0105] The information indicating that the NFT cannot be issued in step S206 is not particularly limited and can be designed as appropriate. For example, the information indicating that the NFT cannot be issued may include information on the fact that the NFT cannot be issued, the reason why the NFT cannot be issued, and past NFT flowerbed data determined to be in a predetermined relationship. In addition, in step S206, information for outputting information indicating that the NFT cannot be issued in the designer terminal 2 may be transmitted together with the information indicating that the NFT cannot be issued.

[0106] The manner in which the information indicating that the NFT cannot be issued in step S208 is output is not particularly limited and can be designed as appropriate. For example, information indicating that the NFT cannot be issued may be displayed on the display screen of the designer terminal 2.

[0107] In step S209, the server device 4 requests that an NFT be issued in association with the flowerbed data corresponding to the NFT issuance request. That is, the server device 4 controls to issue an NFT in association with the flowerbed data corresponding to the NFT issuance request.

[0108] At this time, the server device 4 may also request that the flowerbed data be associated with the designer of the flowerbed corresponding to the flowerbed data and that an NFT be issued. Note that "associating with the designer of the flowerbed" includes "associating with the account of the designer of the flowerbed."

[0109] The issuance of the NFT in step S210 may be performed by an NFT administrator who manages the issuance of the NFT. The NFT administrator may manage, for example, a digital work storage server, a metadata recording server, a blockchain 5, and the like. Here, the digital work storage server may be one that stores the digital work associated with the NFT and information about the digital work as work information. The metadata recording server may be one that records metadata including information about the work, the storage location of the digital work, and the NFT to be issued. The blockchain 5 may be one that records index data about the metadata and tokens. In this case, it can be said that the work information is associated with the NFT in a metadata-converted state. The work information may be associated with data associated with the NFT, as long as it is possible to trace the association from the NFT.

[0110] Alternatively, for example, work information may be associated with the NFT and recorded on the blockchain 5.

[0111] In this case, the digital work may refer to flowerbed data.

[0112] Information about the designer of the flowerbed corresponding to the flowerbed data may be stored as information about the creator of the digital work, i.e., work information. Information about the designer of the flowerbed corresponding to the flowerbed data may be recorded on the blockchain 5 as information about the holder of the NFT.

[0113] In step S211, information regarding the holder of the issued NFT may be stored in the blockchain 5 in association with the issued NFT. The holder of the NFT may be the designer of the flowerbed. Alternatively, in cases where the flowerbed is designed by a designer, where the flowerbed is designed by AI, or where the flowerbed data is generated by AI, the holder of the NFT may be the administrator. In other words, the holder of the NFT may be the same as the holder of the flowerbed data.

[0114] The information about the NFT transmitted in step S212 is not particularly limited as long as it is information about the NFT issued in step S211. The information about the NFT may include the token ID of the NFT, the transaction history of the NFT, information about the holder of the NFT, and the like.

[0115] In step S214, information about the NFT may be stored in the storage unit 43 of the server device 4. The server device 4 may store, as information about the NFT, the token ID of the NFT, the transaction history of the NFT, information about the holder of the NFT, and the like, in association with each other. In addition, the information about the NFT may be stored in association with information about the flowerbed data corresponding to the NFT.

[0116] The information about the NFT transmitted in step S215 may be the same as or different from the information about the NFT received in step S213. It is preferable that the information about the NFT transmitted in step S215 is at least a part of the information about the NFT received in step S213. Also, in step S215, information for outputting the information about the NFT on the designer terminal 2 may be transmitted together with the information about the NFT.

[0117] The manner in which the information about the NFT is output in step S217 is not particularly limited and can be designed as appropriate. For example, the information about the NFT may be displayed on the display screen of the designer terminal 2.

[0118] In addition, in step S217, information regarding the NFT and information regarding the flowerbed data corresponding to the NFT may be output.

[0119] In the above, a request to issue an NFT in response to an NFT issuance request from a designer has been described, but the server device 4 may request to issue an NFT without an NFT issuance request from the designer. For example, the server device 4 may request to issue an NFT in response to an NFT issuance request from an administrator. Alternatively, for example, the server device 4 may request to automatically issue an NFT after generating flowerbed data. In this case, step S209 and subsequent steps of the NFT issuance process may be executed after step S105 or step S106 of the flowerbed data generation process described above.

[0120] Issuing an NFT in association with flowerbed data is also referred to as converting flowerbed data into an NFT. NFT-converted flowerbed data can be circulated within a dedicated app and / or in other NFT markets. When NFT-converted flowerbed data is circulated, the NFT and the flowerbed data are bought and sold as a set. In other words, the subject of circulation may be the flowerbed data associated with an NFT, or may be an NFT associated with the flowerbed data. Here, a manner in which flowerbed data associated with an NFT (hereinafter also referred to as NFT flowerbed data) is circulated will be described.

[0121] [NFT listing process] The designer can select the NFT flowerbed data to be distributed from the NFT flowerbed data he / she owns and put it up for sale. Figure 10 is a flowchart of the NFT listing process according to the embodiment of the present invention.

[0122] First, the designer terminal 2 accepts the selection of NFT flowerbed data (step S301). Next, the designer terminal 2 accepts input of a request to put up for sale the selected NFT flowerbed data (hereinafter also referred to as an exhibition request) (step S302). The exhibition request is transmitted from the designer terminal 2 to the server device 4 (step S303). The server device 4 receives the transmitted exhibition request (step S304). The server device 4 stores the received exhibition request (step S305). The server device 4 executes a sales start process for the NFT flowerbed data corresponding to the exhibition request (step S306), and the NFT exhibition process ends.

[0123] In step S301, the designer can select NFT flowerbed data to put up for sale from among the NFT flowerbed data he or she owns. For example, the designer may select the NFT flowerbed data to put up for sale by displaying information on the NFT flowerbed data he or she owns on the display screen of the designer terminal 2.

[0124] When displaying information on NFT flowerbed data held by the designer, a button for inputting an exhibition request may be displayed on the display screen of the designer terminal 2 together with the information on the NFT flowerbed data. When the button for inputting an exhibition request is pressed, the input of the exhibition request may be accepted in step S302. In this case, when the button for inputting an exhibition request is pressed, an exhibition request may be input for NFT flowerbed data corresponding to the information on the NFT flowerbed data displayed on the display screen of the designer terminal 2.

[0125] In step S303, together with the listing request, information on the NFT flowerbed data corresponding to the listing request, the designer's identification information, the selling price desired by the designer, the selling period desired by the designer, etc. The selling price desired by the designer, the selling period desired by the designer, etc. may be input by the designer.

[0126] In step S305, together with the listing request, information regarding the NFT flowerbed data corresponding to the listing request, identification information of the designer, the selling price desired by the designer, the sales period desired by the designer, etc. may be stored in the storage unit 43 of the server device 4.

[0127] In step S306, the sale start process is executed, and the sale of the NFT flowerbed data corresponding to the listing request is started. That is, the server device 4 controls the NFT flowerbed data corresponding to the listing request to be made available for purchase. Making the NFT flowerbed data available for purchase may mean, for example, making the system 1 available for a user to view the NFT flowerbed data and input a request to purchase it.

[0128] [NFT purchase process] FIG. 11 is a flowchart of an NFT purchasing process according to an embodiment of the present invention.

[0129] The user terminal 3 accepts the selection of NFT flowerbed data being sold (step S401). The user terminal 3 accepts the input of a request to purchase the selected NFT flowerbed data (hereinafter also referred to as a purchase request) (step S402). The input purchase request is transmitted from the user terminal 3 to the server device 4 (step S403). The server device 4 receives the transmitted purchase request (step S404). The server device 4 executes a payment process for the NFT flowerbed data corresponding to the received purchase request (step S405). The server device 4 stores information about the holder of the NFT flowerbed data for which payment has been processed (step S406). The server device 4 makes a request to change the holder of the NFT (step S407). Then, the holder of the NFT is changed in the blockchain 5 (step S408). Also, the transaction history of the NFT is updated in the blockchain 5 (step S409).

[0130] Meanwhile, in the server device 4, after step S407, a process of granting a reward to the designer of the flowerbed corresponding to the NFT flowerbed data for which the payment process has been performed is executed (step S410). Then, information regarding the completion of the purchase of the NFT flowerbed data corresponding to the purchase request (hereinafter also referred to as information regarding the completion of the purchase) is transmitted from the server device 4 to the user terminal 3 (step S411). The transmitted information regarding the completion of the purchase is received in the user terminal 3 (step S412). The received information regarding the completion of the purchase is output in the user terminal 3 (step S413), and the NFT purchase process ends.

[0131] In step S401, the user can select NFT flowerbed data to purchase from among the NFT flowerbed data being sold. For example, the user may select the NFT flowerbed data to purchase by displaying information about the NFT flowerbed data being sold on the display screen of the user terminal 3.

[0132] When displaying information about NFT flowerbed data being sold, a button for inputting a purchase request may be displayed on the display screen of the user terminal 3 together with the information about the NFT flowerbed data. When the button for inputting a purchase request is pressed, the input of the purchase request may be accepted in step S402. In this case, when the button for inputting a purchase request is pressed, a purchase request may be input for NFT flowerbed data corresponding to the information about the NFT flowerbed data being displayed on the display screen of the user terminal 3.

[0133] In step S403, information regarding the NFT flowerbed data corresponding to the purchase request, the user's identification information, information regarding the payment method desired by the user, etc. may be transmitted together with the purchase request.

[0134] The payment method may be a method using a credit card, a method using a bank account, a method using electronic money, or a method using virtual currency. The user terminal 3 may receive input of information regarding the payment method desired by the user.

[0135] The content of the payment process in step S405 is not particularly limited and can be designed appropriately. The payment process may be executed in a manner desired by the user.

[0136] Once the payment process is completed, the owner of the NFT flowerbed data may change from the designer who put the NFT flowerbed data up for sale to the user who purchased the NFT flowerbed data.

[0137] In step S406, information about the user who purchased the NFT flowerbed data may be stored as information about the owner of the NFT flowerbed data.

[0138] In step S407, the server device 4 may request the user to change the owner of the NFT corresponding to the NFT flowerbed data purchased. Changing the owner of the NFT may mean changing the information about the owner stored in association with the NFT to information about the new owner and storing it. When requesting to change the owner of the NFT, the server device 4 may transmit information about the new owner to the blockchain 5. In this case, the server device 4 may transmit information about the user who purchased the NFT flowerbed data to the blockchain 5.

[0139] In step S408, information about the holder stored in association with the NFT corresponding to the NFT flowerbed data purchased by the user may be changed from information about the designer to information about the user and stored.

[0140] In step S409, information regarding changes in the owner of the NFT may be additionally stored as the transaction history of the NFT. The transaction history of the NFT may include changes in the owner of the NFT, information about past owners of the NFT, the selling price of the NFT in each past transaction, the date and time of each past transaction, etc.

[0141] Details of the reward granting process in step S410 will be described later. In step S410, a reward is granted to the designer of the flowerbed corresponding to the NFT flowerbed data for which the payment process has been performed.

[0142] The information regarding the completion of the purchase in step S411 may be information indicating that the purchase of the NFT flowerbed data corresponding to the purchase request has been completed. For example, the information regarding the completion of the purchase may include information indicating that the purchase of the NFT flowerbed data has been completed, that the payment process for the NFT flowerbed data has been completed, that the user has become the owner of the NFT flowerbed data, etc.

[0143] The manner in which the information regarding the completion of the purchase is output in step S413 is not particularly limited and can be designed as appropriate. For example, the information regarding the completion of the purchase may be displayed on the display screen of the user terminal 3.

[0144] In this way, users of the system 1 can purchase NFT flowerbed data that is on sale. In addition, when NFT flowerbed data is purchased, a bonus may be given to the designer of the flowerbed that corresponds to the NFT flowerbed data.

[0145] [Benefits Granting Process] FIG. 12 is a flowchart of the privilege granting process according to the embodiment of the present invention.

[0146] In the server device 4, a reward is granted to the designer of the flowerbed (step S501). In the server device 4, information relating to the granting of the reward is stored (step S502). The information relating to the granting of the reward is transmitted from the server device 4 to the designer terminal 2 (step S503). In the designer terminal 2, the transmitted information relating to the granting of the reward is received (step S504). In the designer terminal 2, the received information relating to the granting of the reward is output (step S505), and the reward granting process ends.

[0147] The reward given in step S501 is not particularly limited and can be designed as appropriate. The reward given may be, for example, a reward equivalent to money or a reward not equivalent to money. Rewards equivalent to money include, for example, electronic money, virtual currency, and cash. Rewards not equivalent to money include, for example, points.

[0148] The content of the benefit to be granted may be determined according to the sales price of the purchased NFT flowerbed data, or may be determined regardless of the sales price of the purchased NFT flowerbed data.

[0149] Granting a reward to a designer refers to processing to allow the designer to obtain the reward. Granting a reward to a designer may mean, for example, sending the reward to the designer, linking the reward to the designer's account and storing the reward, or performing processing to transfer money equivalent to the reward to the designer's bank account or the like.

[0150] The information regarding the granting of the privilege stored in step S502 is not particularly limited and can be designed as appropriate. The information regarding the granting of the privilege may be the contents of the granted privilege, may be the fact that the privilege was granted, may be the date and time when the privilege was granted, may be information regarding the designer to whom the privilege was granted, may be information regarding the sale and purchase of the NFT flowerbed data that triggered the granting of the privilege, or may be information regarding the NFT flowerbed data.

[0151] The information regarding the grant of the reward transmitted in step S503 may be the same as or different from the information regarding the grant of the reward stored in step S502. The information regarding the grant of the reward transmitted in step S503 may be at least a part of the information regarding the grant of the reward stored in step S502.

[0152] In step S503, information indicating that the NFT flowerbed data put up by the designer has been purchased may be transmitted together with information regarding the provision of the bonus. The information indicating that the NFT flowerbed data has been purchased may include information regarding the purchase of the NFT flowerbed data, the date and time when the NFT flowerbed data was purchased, the selling price of the NFT flowerbed data, information regarding the user who purchased the NFT flowerbed data, and the like.

[0153] In step S503, information for outputting the information regarding the granting of the privilege at the designer terminal 2 may be transmitted together with the information regarding the granting of the privilege.

[0154] The manner in which the information regarding the award of the privilege is output in step S505 is not particularly limited and can be designed appropriately. For example, the information regarding the award of the privilege may be displayed on the display screen of the designer terminal 2.

[0155] In addition, in step S505, information indicating that the NFT flowerbed data put up for sale by the designer has been purchased may be output along with information regarding the granting of the bonus.

[0156] In the above, an example in which a reward is given to the designer of the flowerbed corresponding to the NFT flowerbed data has been described, but the reward may be given to someone other than the designer of the flowerbed. For example, the reward may be given to the creator of the flowerbed data corresponding to the NFT flowerbed data, or to a holder who previously held an NFT corresponding to the NFT flowerbed data.

[0157] Users who purchase NFT flowerbed data will be able to ask questions about the flowerbed to the designer of the flowerbed that corresponds to the NFT flowerbed data via a dedicated app.

[0158] [Information transmission and reception processing] FIG. 13 is a flowchart of information transmission and reception processing according to the embodiment of the present invention.

[0159] First, the user selects NFT flowerbed data corresponding to a flowerbed about which the user wants to ask a question. The user terminal 3 accepts the selection of NFT flowerbed data (step S601). The user terminal 3 accepts an input of a question about the flowerbed corresponding to the selected NFT flowerbed data (step S602). The user terminal 3 accepts an input of a request to transmit the input question (hereinafter also referred to as a transmission request) (step S603). The input question is transmitted from the user terminal 3 to the server device 4 (step S604). The server device 4 receives the transmitted question (step S605). The server device 4 stores the received question (step S606). The server device 4 transmits the question to the designer terminal 2 (step S607). The designer terminal 2 receives the transmitted question (step S608). The designer terminal 2 outputs the received question (step S609).

[0160] The designer can check and answer questions about the flowerbed he or she designed. The designer terminal 2 accepts input of an answer to the question (step S610). The designer terminal 2 accepts input of a request to send the input answer (step S611). The designer terminal 2 transmits the input answer to the server device 4 (step S612). The server device 4 receives the transmitted answer (step S613). The server device 4 stores the received answer (step S614). The server device 4 transmits the answer to the user terminal 3 (step S615). The user terminal 3 receives the transmitted answer (step S616). The user terminal 3 outputs the received answer (step S617), and the information transmission and reception process ends.

[0161] In step S601, the user can select NFT flowerbed data corresponding to the flowerbed about which the user wants to ask a question from among the NFT flowerbed data the user owns. For example, the user may select the NFT flowerbed data corresponding to the flowerbed about which the user wants to ask a question by displaying information about the NFT flowerbed data the user owns on the display screen of the user terminal 3.

[0162] When information on NFT flowerbed data owned by the user is selected, the display screen of the user terminal 3 may display information on the selected NFT flowerbed data, as well as a button (hereinafter also referred to as a question button) for displaying a screen for inputting a question to the designer corresponding to the NFT flowerbed data (hereinafter also referred to as a question input screen). When the user presses the question button, the display screen of the user terminal 3 may display a question input screen including a field for inputting a question (hereinafter also referred to as a question input field) and a button for inputting a request to transmit the input question (hereinafter also referred to as a transmission request button). The question input in the question input field may be accepted in step S602.

[0163] The content input in step S602 is not particularly limited. In other words, the content input by the user does not have to be a question for the flowerbed designer. The content input by the user may be any information that the user wishes to send to the flowerbed designer. For example, the user may input a message of support for the flowerbed designer. Here, it is assumed that the content input by the user is a question.

[0164] When a transmission request button is pressed with a question entered in the question input field, input of a transmission request for the question entered in the question input field may be accepted in step S603.

[0165] In step S604, information regarding the NFT flowerbed data corresponding to the question, the user's identification information, etc. may be transmitted together with the question.

[0166] In step S606, information related to the NFT flowerbed data corresponding to the question, the user's identification information, the date and time when the question was received, and the like may be stored in the storage unit 43 of the server device 4 together with the question.

[0167] In step S607, together with the question, information on the NFT flowerbed data corresponding to the question, information on the user who asked the question, the date and time when the question was received, etc. may be transmitted to the designer terminal 2. Also, in step S607, together with the question, information for outputting the question at the designer terminal 2 may be transmitted.

[0168] The manner in which the question is output in step S609 is not particularly limited and can be designed appropriately. For example, the question may be displayed on the display screen of the designer terminal 2.

[0169] On the display screen of the designer terminal 2, together with a question from the user, a field for inputting an answer to the question (hereinafter also referred to as an answer input field) and a button for inputting a request to transmit the input answer (hereinafter also referred to as a transmission request button) may be displayed. The answer inputted in the answer input field may be accepted in step S610.

[0170] When the transmission request button is pressed with an answer entered in the answer input field, input of a transmission request for the answer entered in the answer input field may be accepted in step S611.

[0171] In step S612, together with the answer, information regarding the question corresponding to the answer, information regarding the NFT flowerbed data corresponding to the question, identification information of the designer, etc. may be transmitted.

[0172] In step S614, together with the answer, information regarding the question corresponding to the answer, information regarding the NFT flowerbed data corresponding to the question, identification information of the designer, the date and time when the answer was received, etc. may be stored in the storage unit 43 of the server device 4.

[0173] In step S615, together with the answer, information on the question corresponding to the answer, information on the NFT flowerbed data corresponding to the question, information on the designer, the date and time when the answer was received, and the like may be transmitted to the user terminal 3. Also, in step S615, together with the question, information for outputting the answer in the user terminal 3 may be transmitted.

[0174] The manner in which the answer is output in step S617 is not particularly limited and can be designed as appropriate. For example, the answer may be displayed on the display screen of the user terminal 3. In addition, the display screen of the user terminal 3 may display information on the question corresponding to the answer, information on the NFT flowerbed data corresponding to the question, information on the designer, the date and time when the answer was received, and the like, together with the answer.

[0175] In addition, a user who purchases NFT flowerbed data may be able to order products and / or services corresponding to the NFT flowerbed data via a dedicated app.

[0176] The product and / or service corresponding to the NFT flower bed data may be a product and / or service related to the creation of a flower bed corresponding to the NFT flower bed data. The product and / or service corresponding to the NFT flower bed data may be a product and / or service for actually creating a flower bed corresponding to the NFT flower bed data.

[0177] Products corresponding to NFT flower bed data may be, for example, plants required to create a flower bed, soil suitable for use in a flower bed, fertilizer suitable for use in a flower bed, partition materials or pots used to create a flower bed, decorative items used to create a flower bed, etc. Furthermore, a service corresponding to NFT flower bed data may be a service in which a professional such as a gardener creates a flower bed.

[0178] Products and / or services corresponding to the NFT flowerbed data may be stored in the storage unit 43 of the server device 4 in association with the NFT flowerbed data.

[0179] The person who actually provides the ordered goods and / or services to the user may be the administrator of the system 1 or another vendor.

[0180] [Order acceptance processing] FIG. 14 is a flowchart of an order receiving process according to an embodiment of the present invention.

[0181] First, the user terminal 3 accepts the selection of NFT flowerbed data (step S701). The user terminal 3 accepts the input of a request to order a product and / or service corresponding to the selected NFT flowerbed data (hereinafter also referred to as an order request) (step S702). The input order request is transmitted from the user terminal 3 to the server device 4 (step S703). The server device 4 receives the transmitted order request (step S704). The server device 4 executes a payment process for the product and / or service corresponding to the received order request (step S705). The server device 4 stores information regarding the order of the product and / or service for which payment has been processed (step S706). The server device 4 executes a process of granting a reward to the designer of the flowerbed corresponding to the NFT flowerbed data (step S707).

[0182] Information regarding the order of the product and / or service corresponding to the NFT flowerbed data is transmitted from the server device 4 to the user terminal 3 (step S708). The transmitted information regarding the order is received by the user terminal 3 (step S709). The received information regarding the order is output by the user terminal 3 (step S710), and the order acceptance process ends.

[0183] In step S701, the user can select NFT flowerbed data for which the user wishes to order goods and / or services from among the NFT flowerbed data the user owns. For example, the user may select NFT flowerbed data for which the user wishes to order goods and / or services by displaying information on the NFT flowerbed data the user owns on the display screen of the user terminal 3.

[0184] When information about NFT flowerbed data owned by the user is selected, a button for making an order request for a product and / or service corresponding to the NFT flowerbed data (hereinafter also referred to as an order request button) may be displayed on the display screen of the user terminal 3 together with information about the selected NFT flowerbed data. The contents of the product and / or service corresponding to the NFT flowerbed data may be displayed on the display screen of the user terminal 3 as information about the NFT flowerbed data. When the order request button is pressed, input of an order request for a product and / or service corresponding to the NFT flowerbed data displayed on the display screen may be accepted in step S702.

[0185] In step S703, together with the order request, information on the NFT flowerbed data corresponding to the order request, user identification information, information on the payment method desired by the user, information on the shipping destination of the product desired by the user, information on the shipping date and time of the product desired by the user, information on the location where the service desired by the user is provided, information on the date and time of the service desired by the user, etc. may be transmitted. Information on the shipping destination of the product desired by the user, information on the shipping date and time of the product desired by the user, information on the location where the service desired by the user is provided, information on the date and time of the service desired by the user, etc. may be input by the user.

[0186] The payment method may be a method using a credit card, a method using a bank account, a method using electronic money, or a method using virtual currency. The user terminal 3 may receive input of information regarding the payment method desired by the user.

[0187] The contents of the payment process in step S705 are not particularly limited and can be designed as appropriate. The payment process may be executed in a manner desired by the user. The payment process does not have to be executed in the system 1. For example, the payment process may be executed in a system managed by a business that actually provides the product and / or service corresponding to the order request.

[0188] The information on ordering goods and / or services stored in step S706 is not particularly limited and can be designed as appropriate. The information on ordering goods and / or services may include, for example, information indicating that ordering goods and / or services has been completed, that payment processing for goods and / or services has been completed, etc. Furthermore, the information on ordering goods and / or services may include, for example, information on shipping goods, information on provision of services, etc.

[0189] The above description can be adopted to the extent necessary for the reward granting process in step S707. The reward may be granted to the designer of the flowerbed corresponding to the NFT flowerbed data, the creator of the flowerbed data corresponding to the NFT flowerbed data, or the holder who previously held the NFT corresponding to the NFT flowerbed data.

[0190] The information related to the order of the product and / or service transmitted in step S708 is not particularly limited and can be designed as appropriate. The information related to the order of the product and / or service transmitted in step S708 may be the same as or different from the information related to the order of the product and / or service stored in step S706. The information related to the order of the product and / or service transmitted in step S708 may be at least a part of the information related to the order of the product and / or service stored in step S706.

[0191] The manner in which information regarding the order of the product and / or service is output in step S710 is not particularly limited and can be designed as appropriate. For example, information regarding the order of the product and / or service may be displayed on the display screen of the user terminal 3.

[0192] A user who purchases NFT flowerbed data may place orders for products and / or services corresponding to the NFT flowerbed data for themselves, and may also place orders for products and / or services corresponding to the NFT flowerbed data for other users.

[0193] Furthermore, a user who has purchased NFT flowerbed data may resell the NFT flowerbed data. When reselling NFT flowerbed data, the user may put up for sale the purchased NFT flowerbed data. The manner in which the NFT flowerbed data is put up for sale may adopt the description of the NFT listing process described above to the extent necessary.

[0194] In addition, the above description of the NFT purchase process may be adopted to the extent necessary for the manner in which the resold NFT flowerbed data is purchased by another user. Even when the resold NFT flowerbed data is purchased by another user, a benefit may be given to the designer of the flowerbed corresponding to the NFT flowerbed data, the creator of the flowerbed data corresponding to the NFT flowerbed data, and / or the holder who previously held the NFT corresponding to the NFT flowerbed data.

[0195] In addition, other users who have purchased the resold NFT flowerbed data may also be able to ask questions to the designer of the flowerbed corresponding to the NFT flowerbed data, and place orders for products and / or services corresponding to the NFT flowerbed data. For the manner of asking questions to the designer of the flowerbed corresponding to the NFT flowerbed data, the description of the information transmission and reception process described above may be adopted to the extent necessary. For the manner of placing orders for products and / or services corresponding to the NFT flowerbed data, the description of the order acceptance process described above may be adopted to the extent necessary.

[0196] In addition, a user who purchases NFT flowerbed data may or may not be able to modify the flowerbed data corresponding to the NFT flowerbed data. If the flowerbed data is modifiable, the user may be able to order products and / or services corresponding to the modified flowerbed data. Whether or not the flowerbed data can be modified may be set by the flowerbed designer and / or the holder of the NFT flowerbed data.

[0197] In this way, a system having at least one computer device can be provided that includes a flowerbed data generation means for generating flowerbed data related to a flowerbed, and an NFT issuance means for controlling the issuance of an NFT (non-fungible token) associated with the generated flowerbed data, and the flowerbed data includes information regarding the shape of the flowerbed, the size of the flowerbed, the color of the plants, the type of plants, and / or the arrangement of the plants, thereby providing a system for issuing NFTs in association with data related to a flowerbed.

[0198] Furthermore, by providing the system with an NFT sales means that controls the system to make the NFT and flower bed data available for purchase, the NFT and flower bed data can be circulated.

[0199] Furthermore, by having the system include an owner storage means that associates an NFT with information about the owner of the NFT, it becomes easier to demonstrate that the information about the owner of the NFT is reliable.

[0200] Furthermore, by having the system equipped with an information transmission means for transmitting information from a terminal operated by the NFT holder to a terminal operated by the flowerbed designer corresponding to the flowerbed data associated with the NFT, the user can have the advantage of being able to interact with the flowerbed designer, thereby increasing the user's motivation to hold NFTs.

[0201] Furthermore, by providing the system with a flowerbed order acceptance means that accepts orders from NFT holders for products and / or services that correspond to the flowerbed data associated with the NFT, the system can increase users' motivation to hold NFTs by providing the benefit of being able to order products and / or services that correspond to the flowerbed data.

[0202] In addition, when the system receives an order for products and / or services corresponding to flowerbed data associated with an NFT through the flowerbed order receiving means, the system is provided with an order bonus storage means that stores information regarding the granting of bonuses to the flowerbed designer corresponding to the flowerbed data, the generator of the flowerbed data, and / or a holder who has previously held the NFT, thereby increasing the user's motivation to design flowerbeds, generate flowerbed data, and / or hold NFTs.

[0203] Furthermore, in this way, when an NFT and flowerbed data are purchased, the system is provided with a purchase bonus storage means that stores information regarding the granting of bonuses to the flowerbed designer corresponding to the flowerbed data, the generator of the flowerbed data, and / or the holder who previously held the NFT, thereby increasing the user's motivation to design flowerbeds, generate flowerbed data, and / or hold NFTs.

[0204] In this way, the system is equipped with a determination means for determining whether the generated flowerbed data has a specified relationship with flowerbed data associated with previously issued NFTs, and controls the NFT issuing means to issue an NFT associated with the generated flowerbed data when the determination means determines that there is no specified relationship, making it possible to issue an NFT for flowerbed data that was previously determined not to have a specified relationship with NFT flowerbed data. [Explanation of symbols]

[0205] 1 System 2. Designer terminal 3. User terminal 4. Server equipment 5. Blockchain 6. Communication Network 21 Control section 22 RAM 23 Storage Department 24 Input section 25 Display section 26 Communication Interface 41 Control section 42 RAM 43 Storage Department 44 Communication Interface 100 Execution screen 101 squares 102 Flowerbed shape input area 103 Length input field 104 Decision button 200 Execution screen 201 squares 202 Color selection start button 203 Color Palette 204 Confirmation button 300 Execution screen 301 Selection color display field 302 Plant image display field 303 Plant information display field 304 Decision button 400 Execution screen 401 Image display column 402 Time change meter 403 Viewpoint change button 404 Save button

Claims

1. A system comprising at least one computing device, A flowerbed data generating means for generating flowerbed data relating to a flowerbed; An NFT issuing means for controlling the issuance of an NFT (non-fungible token) associated with the generated flowerbed data; Equipped with The flower bed data includes information regarding the shape of the flower bed, the size of the flower bed, the color of the plants, the type of the plants, and / or the arrangement of the plants. system.

2. NFT sales instrument that controls NFT and flowerbed data to make them available for purchase Equipped with The system of claim 1 .

3. an owner storage means for storing information about the owner of the NFT in association with the NFT; Equipped with 3. A system according to claim 1 or 2.

4. An information transmission means for transmitting information from a terminal operated by the holder of the NFT to a terminal operated by a flowerbed designer corresponding to the flowerbed data associated with the NFT. Equipped with 3. A system according to claim 1 or 2.

5. a flowerbed order acceptance means for accepting orders by holders of NFTs for goods and / or services corresponding to the flowerbed data associated with the NFTs; Equipped with 3. A system according to claim 1 or 2.

6. an order privilege storage means for storing information regarding the granting of privileges to the designer of the flowerbed corresponding to the flowerbed data, the creator of the flowerbed data, and / or a holder who previously held the NFT, when an order for a product and / or service corresponding to the flowerbed data associated with the NFT is received by the flowerbed order receiving means; Equipped with 3. A system according to claim 1 or 2.

7. A purchase benefit storage means for storing information regarding the provision of benefits to a designer of a flowerbed corresponding to the flowerbed data, a creator of the flowerbed data, and / or a holder who previously held the NFT, when the NFT and the flowerbed data are purchased. Equipped with 3. A system according to claim 1 or 2.

8. A determination means for determining whether the generated flowerbed data has a predetermined relationship with flowerbed data associated with a previously issued NFT. Equipped with and controlling an NFT issuing means to issue an NFT associated with the generated flowerbed data when the determining means determines that the predetermined relationship does not exist.

3. A system according to claim 1 or 2.

9. A flowerbed data generating means for generating flowerbed data relating to a flowerbed; An NFT issuing means for controlling the issuance of an NFT (non-fungible token) associated with the generated flowerbed data; Equipped with The flower bed data includes information regarding the shape of the flower bed, the size of the flower bed, the color of the plants, the type of the plants, and / or the arrangement of the plants. Computer equipment.

10. A computer device, A flower bed data generating means for generating flower bed data relating to a flower bed; An NFT issuing means for controlling the issuance of a non-fungible token (NFT) associated with the generated flowerbed data. Function as a The flower bed data includes information regarding the shape of the flower bed, the size of the flower bed, the color of the plants, the type of the plants, and / or the arrangement of the plants. program.

11. A flowerbed data generation step of generating flowerbed data relating to a flowerbed; An NFT issuing step for controlling the issuance of a non-fungible token (NFT) associated with the generated flowerbed data; having The flower bed data includes information regarding the shape of the flower bed, the size of the flower bed, the color of the plants, the type of the plants, and / or the arrangement of the plants. method.

Images