Token management device, token management method, and token management system

Abstract

To provide a token management device, method, and system that generate a token with which experiences based on intentions of both an event operator and event participants can be shared.SOLUTION: There is provided a token management system including a client terminal for operation, a client terminal for users, a token management device, and a blockchain system, wherein the token management device includes: a user identification unit that stores information of users scheduled to participate in an event and identifies users having participated in the event on the basis of the stored information; a metadata generation unit that, upon receiving designation of information associated with the identified user and indicating at least a partial range of event video, generates metadata that includes the designated information and the information indicating the event video; a token generation unit that generates a token including information indicating the generated metadata and information regarding proprietary rights of the identified user; and a token issuance unit that issues the generated token to the blockchain system.SELECTED DRAWING: Figure 1

Description

[Technical field]

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

[0002] Technologies for creating data assets using so-called non-fungible tokens (NFTs) that use blockchain are being widely developed.

[0003] For example, by issuing NFTs to participants of an event such as a sports game or concert that prove they attended the event, participants can boast about their experience at the event and empathize with others.

[0004] As an example of such NFT technology, Patent Document 1 discloses a live streaming system that includes an acquisition unit that acquires live footage filmed of a live performance, a distribution unit that distributes the live footage, an extraction unit that extracts partial footage that is part of the live footage, a sales unit that sells the extracted partial footage to users, an issuance unit that issues non-fungible tokens containing information that identifies the user, and a transmission unit that transmits the partial footage and the non-fungible tokens. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] International Publication No. 2021 / 246498 Summary of the Invention [Problem to be solved by the invention]

[0006] However, the content of the experiences of event participants varies greatly depending on the specific form of participation. On the other hand, event organizers also have experiences that they would like participants to share. Patent Document 1 does not take such circumstances into sufficient consideration.

[0007] The present invention has been made in consideration of the above circumstances, and its purpose is to provide a token management device, a token management method, and a token management system that are capable of generating tokens that allow event organizers and event participants to share an experience that is in line with their intentions. [Means for solving the problem]

[0008] One of the present inventions for solving the above problems is a token management device in a blockchain system including a plurality of information processing devices managed by each user, in which tokens are shared and stored by each information processing device and ownership information is recorded, the token management device comprising: a storage device for storing information of users who plan to participate in an event; and a control device that executes a user identification process for identifying users who participated in the event based on the stored information, a metadata generation process for accepting designation of information associated with the identified user and indicating at least a partial range of the video, and generating metadata, which is data including the designated information and information indicating the video of the event, a token generation process for generating a token including information indicating the generated metadata and ownership information of the identified user, and a token issuance process for issuing the generated token to the blockchain system.

[0009] Another aspect of the present invention for solving the above problem is a method for controlling a plurality of information processing devices managed by each user. a token management device having a control device that executes the following operations: a user identification process for identifying a user who participated in the event and who is related to the request information based on the stored information when the request information is received from the user terminal; a metadata generation process for receiving information associated with the identified user and indicating at least a partial range of the video, and generating metadata, which is data including the specified information and information indicating the video of the event; a token generation process for generating a token including information indicating the generated metadata and ownership information of the identified user; and a token issuance process for issuing the generated token to the blockchain system. Effect of the Invention

[0010] According to the present invention, a token can be generated that allows an experience to be shared in accordance with the intentions of both the event organizer and the event participants. Configurations and effects other than those described above will become apparent from the following description of the embodiments. [Brief description of the drawings]

[0011] [Figure 1] FIG. 1 is a diagram illustrating an example of a configuration of a token management system according to an embodiment of the present invention. [Diagram 2] FIG. 1 is a diagram illustrating the configuration of a venue where an event according to an embodiment of the present invention is held. [Diagram 3] A figure showing an example of an NFT issuing authority management table. [Figure 4] FIG. 11 is a sequence diagram illustrating an example of a process performed in the token management system. [Diagram 5] FIG. 13 illustrates an example of a data configuration of an event management table. [Figure 6] A figure showing an example of metadata related to an original video NFT. [Figure 7] FIG. 13 is a diagram showing an example of an additional information specification screen. [Figure 8] FIG. 11 is a diagram showing another example of the additional information specification screen. [Figure 9] A figure showing an example of metadata related to a user NFT. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings.

[0013] <Configuration, Function> 1 is a diagram for explaining an example of the configuration of a token management system 1 according to the present embodiment. The token management system 1 includes an operation client terminal 10 (operator terminal) managed by an operator who holds and manages a specific event (a soccer match in this embodiment), one or more user client terminals 20 (user terminals) owned by each participant (user) who participates in the event, a server terminal 30 (token management device) that generates and issues non-fungible tokens (NFTs) whose value is the content experienced by the user at the event, and a blockchain system 40 (BC: Block Chain System) that constitutes a blockchain system related to the NFTs (hereinafter referred to as user NFTs) and stores the NFTs. )

[0014] The blockchain system 40 is composed of multiple BC terminals 50 (information processing devices) that each share and store user NFTs. This blockchain system 40 includes terminals managed by each user and a terminal managed by an operator. Note that the operator client terminal 10 or the user client terminal 20 may also function as the BC terminal 50.

[0015] The blockchain system 40 is an information processing system using distributed ledger technology. That is, each BC terminal 50 of the blockchain system 40 stores information on user NFTs as block data (the same applies to original video NFTs described later). The block data includes data on the owner (history) of the user NFT, hash data, and nonce data. When the owner is changed, new block data is added to the existing block data. At this time, these block data are shared by each BC terminal 50 after a predetermined consensus formation process by each node (BC terminal 50) at regular intervals. Note that the blockchain system 40 may be a system in which nodes (users) are not limited by an administrator (management terminal) or the like (public type), or may be a system in which nodes (users) are limited by an administrator (for example, the server terminal 30 manages users (blockchain system 40)) (private type). In this embodiment, Ethereum is used among the former, but the type (platform) of the blockchain system 40 is not limited as long as the functions described in this embodiment can be realized.

[0016] In addition, the management client terminal 10, the user client terminal 20, the server terminal 30, and each BC terminal 50 of the blockchain system 40 are connected to each other via a network such as the Internet, a LAN (Local Area Network), a WAN (Wide Area Network), or a dedicated line. They are connected by a wired or wireless communication network 5.

[0017] The management client terminal 10 includes a control device 1 such as a CPU (Central Processing Unit). 1, a storage device 12 such as a RAM (Random Access Memory), a ROM (Read Only Memory), a HDD (Hard Disk Drive), or an SSD (Solid State Drive), a display device 13 such as a display or a touch panel, an input device 14 such as a keyboard, a mouse, or a touch panel, and a communication device 15 configured with a NIC (Network Interface Card), a wireless communication module, a USB (Universal Serial Interface) module, a serial communication module, or the like. It is equipped with.

[0018] In addition, the management client terminal 10 has a functional unit of a management wallet storage unit 121. The management wallet storage unit 121 stores the account (address) of the manager in the blockchain system 40 and its private key.

[0019] The user client terminal 20 includes a control device such as a CPU (Central Processing Unit). 21, RAM (Random Access Memory), ROM (Read Only Memory), HDD (Hard A storage device 22 such as a hard disk drive (HDD) or a solid state drive (SSD), a display device 23 such as a display or a touch panel, an input device 24 such as a keyboard, a mouse, or a touch panel, and a communication device 22 configured with a NIC (Network Interface Card), a wireless communication module, a USB (Universal Serial Interface) module, a serial communication module, or the like. Equipped with 5.

[0020] In addition, the user client terminal 20 has a functional unit of a user wallet storage unit 231. The user wallet storage unit 231 stores the user's account (address) and its private key in the blockchain system 40. The private keys of the operator and the user may be stored in the server terminal 30.

[0021] The BC terminal 50 includes a control device 51 such as a central processing unit (CPU), a storage device 52 such as a random access memory (RAM), a read only memory (ROM), a hard disk drive (HDD), or a solid state drive (SSD), and a network interface card (NIC). ), wireless communication module, USB (Universal Serial Interface) module, or serial and a communication device 53 configured with a network communication module, etc. The BC terminal 50 may include a display device such as a display or a touch panel, and an input device such as a keyboard, a mouse, or a touch panel.

[0022] In addition, the BC terminal 50 has a functional unit of a token information storage unit 521. The token information storage unit 521 stores each NFT in a shared manner between the BC terminals 50.

[0023] The server terminal 30 includes a control device 31 such as a CPU (Central Processing Unit), a RAM, (Random Access Memory), ROM (Read Only Memory), HDD (Hard Disk Drive) or a solid state drive (SSD), and a communication device 33 configured with a network interface card (NIC), a wireless communication module, a universal serial interface (USB) module, a serial communication module, etc. The BC terminal 50 may include a display device such as a display or a touch panel, and an input device such as a keyboard, a mouse, or a touch panel.

[0024] The server terminal 30 also includes the following functional units: a user identification unit 321, a BC management unit 322, a metadata generation unit 323, a token generation unit 324, a token issuing unit 325, and a partial video generation unit 326.

[0025] The user identification unit 321 identifies a user who participated in an event held by the administrator. For example, the user identification unit 321 receives current location information from the user client terminal 20 of a user who participates in the event, determines whether or not the location indicated by the received location information corresponds to the location where the event is held (such as a seating area in the venue), and identifies the user related to the user client terminal 20 as a user who participated in the event if the location indicated by the location information corresponds to the location where the event is held.

[0026] Although details will be described later, the server terminal 30 stores video of the event taken by the organizer (hereinafter referred to as original video). In this embodiment, it is assumed that there are multiple original videos for one event. That is, in this embodiment, multiple camera devices are provided at various locations in the venue where the event, i.e., the soccer match, is held, with each camera device facing the event area (pitch), and each camera device takes video of the match from its own angle. Details of the arrangement of the camera devices will be described later.

[0027] The BC management unit 322 performs processing to generate and issue an NFT. For example, the BC management unit 322 issues a user NFT generated by processing described below to the blockchain system 40.

[0028] The metadata generating unit 323 generates metadata for the user NFT. That is, the metadata generating unit 323 receives information indicating at least a part of the range of the original video from the user, and generates metadata, which is data including the specified information and information indicating the original video. Note that the information indicated by the metadata may be referred to as additional information below.

[0029] For example, the metadata generating unit 323 identifies, from a plurality of original videos, an original video that corresponds to the event participation position of the user identified by the user identifying unit 321. Then, the metadata generating unit 323 receives designation of information indicating at least a partial range of the identified original video, and generates metadata including the designated information and information indicating the original video.

[0030] Also, for example, the metadata generating unit 323 may generate at least a part of the original video. As the information to be displayed, information on the time period of the event (in this embodiment, the start time and end time of the time period) is accepted.

[0031] The token generation unit 324 generates a token (i.e., a user NFT) that includes information indicating the metadata generated by the metadata generation unit 323 (in this embodiment, an address) and ownership information of the user identified by the user identification unit 321.

[0032] The token issuing unit 325 issues the token (user NFT) generated by the token generating unit 324 to the blockchain system 40.

[0033] In addition, the token issuing unit 325 generates an NFT (original video NFT) that includes information indicating the event video (original video) acquired by the user identification unit 321 and information about the event organizer as ownership information, and issues the generated NFT to the blockchain system 40.

[0034] The partial video generating unit 326 generates video data (hereinafter, referred to as a partial video) corresponding to the user NFT. That is, the partial video generating unit 326 generates a video of at least a part of the original video based on the original video and the metadata (additional information) generated by the metadata generating unit 323.

[0035] The server terminal 30 also includes an event management table storage unit 327 , an original video storage unit 328 , an issuing authority storage unit 329 , and a metadata storage unit 330 .

[0036] The event management table storage unit 327 stores an event management table for managing events held by the administrator (details will be described later). The event management table may be stored in the administrator client terminal 10.

[0037] The original video storage unit 328 stores video of the event taken by the organizer (original video).

[0038] The issuance authority memory unit 329 stores an NFT issuance authority management table, which is a table for determining the relationship between the area (seat) assigned to each user and the configuration of the user NFT that can be generated corresponding to that area.

[0039] The metadata storage unit 330 stores the metadata generated by the metadata generation unit 323. Note that the function of the metadata storage unit 330 may be provided in an information processing device other than the server terminal 30 (such as a database).

[0040] (Venue configuration) Here, Fig. 2 is a diagram for explaining the configuration of a venue where an event according to this embodiment is held. As shown in the figure, this venue 200 includes an event area 210 (pitch) where the event (soccer match) is held, and a seating area 220 where each user watching the event area 210 is located and where seats are provided. The seating area 220 is an area consisting of a plurality of seats, and specifically, consists of a first seating area 221 ("A"), a second seating area 222 ("B"), a third seating area 223 ("C"), a fourth seating area 224 ("D"), and a fifth seating area 225 ("E").

[0041] In addition, in the venue 200, a plurality of imaging devices 230 for capturing original images are provided by the administrator in correspondence with each seat area 220. Specifically, the first imaging device 230 is set to capture the original images in the direction of the line of sight (the direction of the pitch) of the user watching the game in the first seat area 221. The system includes a first camera 230a for shooting a first original video, a second camera 230b for shooting a second original video with the direction of the line of sight (the direction of the pitch) of a user watching in the second seating area 222 set as its shooting direction, a third camera 230c for shooting a third original video with the direction of the line of sight (the direction of the pitch) of a user watching in the third seating area 223 set as its shooting direction, a fourth camera 230d for shooting a fourth original video with the direction of the line of sight (the direction of the pitch) of a user watching in the fourth seating area 224 set as its shooting direction, and a fifth camera 230e for shooting a fifth original video with the direction of the line of sight (the direction of the pitch) of a user watching in the fifth seating area 225 set as its shooting direction. Each camera 230 shoots original video with a different shooting angle during the event (during the match).

[0042] (NFT issuing authority management table) Next, Fig. 3 is a diagram showing an example of an NFT issuance authority management table. The NFT issuance authority management table 300 is a table showing the relationship between the type of seat area 220 assigned to each user at the venue and the original video that the user watching in that seat area 220 can use as material for a partial video (user NFT).

[0043] In the case of the NFT issuing authority management table 300 in the figure, users watching in each seat area 220 can use one or more original videos 320 specified by the NFT issuing authority management table 300 as materials for partial videos. For example, a user watching in the first seat area 221 ("A") can use all original videos 320 (320a to 320f) as materials for partial videos (premium seats). A user watching in the second seat area 222 ("B") can use the first original video 320a, the second original video 320b, the fourth original video 320d, and the fifth original video 320e as materials for partial videos. A user watching in the fourth seat area 224 ("D", home side seats) can use only the first original video 320a and the second original video 320b (only original videos from the shooting device close to the user's seat) as materials for partial videos (regular seats where only original videos from the shooting device set on the home side are the target). The NFT issuing authority management table 300 is set in advance by an operator or the like.

[0044] The functions of the functional units of each information processing device described above are realized by the control devices 11, 21, 31, and 51 reading out a predetermined program for realizing each functional unit from the storage devices 12, 22, 32, and 52. Each program can be recorded on a portable or fixed recording medium and distributed. Note that all or a part of these programs may be realized using virtual information processing resources provided using a virtualization technique or a process space separation technique, such as a virtual server provided by a cloud system. Also, all or a part of these programs may be realized by a service provided by a cloud system via an API (Application Programming Interface), for example. Next, the processing performed by the token management system 1 will be described.

[0045] <Processing explanation> FIG. 4 is a sequence diagram illustrating an example of a process performed by the token management system 1. As shown in FIG.

[0046] First, before an event is held, the server terminal 30 receives information about users who plan to participate in the event held by the manager from the management client terminal 10 (s10), and stores the received information in the event management table 500 (s11).

[0047] For example, the management client terminal 10 may receive in advance the information from each person who wishes to make a reservation to participate in the event. The management client terminal 10 receives information about the participation in the event from the user's client terminal 20. Then, the management client terminal 10 transmits the information to the server terminal 30. Note that these processes may be executed by the server terminal 30.

[0048] (Event management table) 5 is a diagram showing an example of the data configuration of event management table 500. Event management table 500 has the following data items: event ID 501 in which information identifying an event (e.g., ID) is set, user ID 502 in which information identifying a user participating in the event (e.g., ID) is set, ticket 503 in which information identifying the type of ticket for the event purchased by the user (e.g., seat area and seat number) is set, event location 504 in which information on the location where the event is held (such as the name of the venue) is set, and location information 505 in which information identifying the location of the seat identified by ticket 503 (seat location information) is set.

[0049] Then, on the day of the event, each user who has made a reservation for the event goes to the event venue bringing their own user client terminal 20. Then, based on the operation of each user, each user client terminal 20 attaches a predetermined electronic signature to the event ID, user ID, ticket (seat) information, event venue, and the current location information of the user (user client terminal 20), and transmits request information for issuing a user NFT (hereinafter, referred to as application information) with this electronic signature attached to the server terminal 30 (s21).

[0050] When the server terminal 30 receives application information from each user's client terminal 20, it judges whether or not the application information of each user is authentic by referring to the event management table 500 (s23). Specifically, the server terminal 30 judges whether or not there is a record in which the event ID, user ID, ticket information, and event venue in the application information are set in event ID 501, user ID 502, ticket 503, and venue 504, respectively. Furthermore, the server terminal 30 judges whether or not the location indicated by the application information is within a certain distance from the location indicated by location information 505 of the record.

[0051] The server terminal 30 transmits a notification (acceptance completion notification) to the user client terminal 20 associated with the user whose application information is genuine (confirmed user) that the application information has been confirmed (s25).

[0052] After that, when the event starts, the manager (for example, the management client terminal 10) takes pictures using each of the photographing devices 230 and generates original videos of the event. The server terminal 30 acquires and stores these original videos. In this embodiment, an ID is set for each original video.

[0053] Then, when the event ends, the server terminal 30 issues a token (original video NFT) related to the original video (s27).

[0054] Specifically, first, the server terminal 30 generates and stores metadata including information (such as a URL) indicating the location of the original video. Then, the server terminal 30 generates an NFT including, as block data, information indicating this metadata (for example, information capable of identifying the location of the metadata, such as a URL, an account name, or an address) and the wallet address of the management client terminal 10 related to the manager as ownership information, and issues the generated NFT to the blockchain system 40.

[0055] (Metadata related to original video NFT) 6 is a diagram showing an example of metadata related to an original video NFT. This metadata 600 includes the date and name of the event 610 (identified from an event ID or the like), the name of the location or venue of the event 620, information about confirmed users 630, and information 640 indicating the original video.

[0056] The confirmed user information 630 includes information 631 on the seat area (and seat number) of each confirmed user, and wallet address information 632 associated with the confirmed user. The information 640 indicating the original video includes ID 641 of each original video and information 642 on the storage location of each original video (URL in the figure).

[0057] The metadata 600 may increase rarity by including information on a serial number assigned to each original video NFT. The location information (for example, latitude, longitude, altitude, or time) received in s23 may be set in the seat area (and seat number) information 631 of the metadata 600.

[0058] Next, as shown in FIG. 4, after the event ends, the server terminal 30 accepts input from each confirmed user (user client terminal 20) specifying information (additional information) for identifying a partial image from the original image (s31).

[0059] For example, when the server terminal 30 receives information requesting input of additional information from a user client terminal 20 related to a confirmed user, it creates an additional information specification screen described below and displays the created additional information specification screen on the screen of the user client terminal 20.

[0060] Then, when the input of the additional information specification on the additional information specification screen is completed, the user's client terminal 20 applies to the server terminal 30 for the issuance of a user NFT (s33).

[0061] (Additional information specification screen) 7 is a diagram showing an example of an additional information designation screen. This additional information designation screen 700 displays a list 710 (710a-c) of original videos captured by the imaging device 230 corresponding to the confirmed user, and videos 720 (720a1, 720a2, . . ., 720b1, 720b2, . . ., 720c1, 720c2, . . .) of each original video 710 at each timing. The original video corresponding to the confirmed user is identified by the NFT issuing authority management table 300.

[0062] The additional information selection screen 700 accepts the user's selection of one original video from the displayed list of original videos. The additional information selection screen 700 further accepts the user's input of the start time 730 and end time 740 of the time period of each video portion to be extracted as a partial video from the selected original video 710a. This is the case, for example, when the user's seat area corresponds to only one original video.

[0063] The additional information designation screen 700 includes an issuance request button 750 for requesting the issuance of a user NFT. When the issuance request button 750 is selected by a confirmed user, the server terminal 30 issues the user NFT.

[0064] 8 is a diagram showing another example of an additional information designation screen. This additional information designation screen 800 accepts the selection of multiple original videos from the user. The additional information designation screen 800 further accepts input from the user of start time 830 and end time 840 (specified, for example, in hours, minutes, seconds, and milliseconds) of the time period of each video portion to be extracted as a partial video from each of the selected original videos 810a, b, and c.

[0065] The additional information designation screen 800 may accept input of information on the ranking or order of the selected original videos 810, to be reflected in metadata, which will be described later. The additional information designation screen 800 may also accept multiple selections of a certain original video 810.

[0066] Next, as shown in FIG. 4, the server terminal 30 generates metadata (additional information) based on the information set on the additional information designation screen (s35).

[0067] (Metadata related to user NFTs) 9 is a diagram showing an example of metadata related to a user NFT. This metadata 900 includes information 910 (URL in the figure) on the storage location of the metadata corresponding to the original video NFT, and additional information 920 set on the additional information designation screen.

[0068] This metadata 900 includes information 921 (ID in the figure) for identifying each original video selected on the additional information designation screen 700, 800, and start time 922 and end time 923 of a partial video in that original video.

[0069] In addition, this metadata 900 may include information about a serial number assigned to each original video NFT, thereby increasing the rarity of the NFT.

[0070] 4, the server terminal 30 issues a user NFT corresponding to the generated metadata to the blockchain system 40 (s37). For example, the server terminal 30 generates an NFT including, as block data, information indicating the metadata generated in s35 (for example, information capable of identifying the location of the metadata, such as a URL, an account name, or an address) and the wallet address of the user client terminal 20 related to the confirmed user who applied for the issuance of the NFT in s31 as ownership information, and issues the generated NFT to the blockchain system 40.

[0071] In addition, when issuing a user NFT, the server terminal 30 may determine whether or not an original video selected on the additional information specification screen 700, 800 exists, or whether or not the start time and end time selected on the additional information specification screen 700, 800 fall within the duration of the corresponding original video, and issue the user NFT only if these conditions are met.

[0072] For example, the server terminal 30 refers to the URL of the original video in the metadata generated in the process of s27, and checks whether or not the original video file exists. Then, the server terminal 30 compares the duration of the original video at the URL with the start time and end time selected on the additional information designation screen 700, 800.

[0073] After issuing the user NFT, the server terminal 30 sends a notification indicating that the user NFT has been issued (issuance completion notification) to the user client terminal 20 associated with the confirmed user who applied for the issuance of the user NFT in s33 (s39).

[0074] Furthermore, the server terminal 30 generates a partial video related to the user NFT issued in s37 and makes the generated partial video public (s41).

[0075] For example, the server terminal 30 acquires an original video that is the source of the partial video related to the user NFT, and trims the acquired original video from the start time to the end time selected on the additional information designation screen 700, 800. The server terminal 30 stores the trimmed part of the video, i.e., the partial video, in a specified URL. The server terminal 30 accesses the URL. The information is transmitted to each user's client terminal 20 or to each user's BC terminal 50 in the blockchain system 40.

[0076] Thereafter, each user can access the partial video that was made public in s41 and view the partial video (s43).

[0077] For example, each user client terminal 20 accesses the URL published in s41 and plays back the partial video.

[0078] This allows, for example, other users to relive the event from a perspective similar to that of a user who participated in an event in a standard seat on the day of the event.

[0079] Furthermore, for example, with respect to a user who participated in an event in a premium seat, other users can relive the event from various perspectives.

[0080] As described above, the token management device of this embodiment identifies users participating in the event based on the event management table 500 (confirmed users), accepts specification from the user of information associated with the confirmed user and indicating the desired range in the original video (i.e., the range in the original image of the camera 230 corresponding to the confirmed user's ticket), generates metadata (additional information), which is data including the specified information and information indicating the original video, generates an NFT including information indicating the generated metadata and ownership information of the confirmed user, and issues the generated token to the blockchain system 40.

[0081] In other words, the token management device of this embodiment accepts from the user himself / herself a specification of a part (additional information) of the original video of the event provided by the operator that corresponds to the user who participated in the event, and issues an NFT linked to that additional information.

[0082] In this way, the token management device of this embodiment can generate a token that allows the event organizer and event participants to share an experience that is in line with their intentions.

[0083] In addition, the token management device of this embodiment receives current location information from the user client terminal 20 of a user participating in the event, and if the location indicated by the received location information corresponds to the location of the event venue, identifies the user as a user who participated in the event, and generates metadata including additional information related to the identified user, information indicating video of the event, and location information.

[0084] In this way, by generating metadata that includes the location information of users who actually participated in the event, the value of the user NFT generated by this metadata can be increased.

[0085] Furthermore, the token management device of this embodiment accepts designation of information on the time period (start time and end time) of an event as information indicating the range of the original video.

[0086] This will make the experiences of users who participate in the event more concrete, thereby increasing the value of the user NFTs generated based on this.

[0087] The token management device of this embodiment also identifies an original video corresponding to the user's event participation position from among a plurality of original videos, accepts from the user a specification of a portion (additional information) of the original video corresponding to the user who participated in the event, and Generates metadata that includes additional information.

[0088] In this way, by generating metadata based on original video corresponding to the event participation location of a user who actually participated in the event (e.g., the seating area indicated by the ticket), the value of the user NFT generated by this metadata can be increased.

[0089] In addition, the token management device of this embodiment generates an original NFT that includes information indicating the location of the original video and information about the event administrator as ownership information, and issues the generated original NFT to the blockchain system 40.

[0090] This makes it possible to prove the authenticity of the original video that forms the basis of the user NFT, thereby increasing the value of the user NFT.

[0091] In addition, the token management device of this embodiment sends an issuance completion notification indicating that the generated user NFT has been issued to the blockchain system 40 to the user client terminal 20 relating to the confirmed user.

[0092] This allows verified users to know that their user NFT has been issued, and they can take steps such as publicizing this fact and sharing their experience widely.

[0093] Moreover, the token management device of this embodiment generates a partial video based on the original video and metadata (additional information).

[0094] This allows each user, including verified users associated with user NFTs, to relive the experience they had by participating in the event.

[0095] In addition, the token management system 1 of this embodiment includes an operation client terminal 10 that transmits information about users who plan to participate in the event, a user client terminal 20 that transmits application information for the issuance of tokens related to the event, and a token management device, and the token management device stores information received from the operation terminal (event management table 500), and when application information is received from the user client terminal 20, generates metadata related to the user NFT based on the event management table 500.

[0096] This allows user NFTs to be generated based on the respective intentions of the event organizer and the event participants.

[0097] The present invention is not limited to the above-described embodiment, and can be implemented using any components without departing from the scope of the present invention. The above-described embodiments and modifications are merely examples, and the present invention is not limited to these contents as long as the features of the invention are not impaired. In addition, although various embodiments and modifications have been described above, the present invention is not limited to these contents. Other aspects conceivable within the scope of the technical idea of ​​the present invention are also included in the scope of the present invention.

[0098] For example, part of the hardware included in each device of this embodiment may be provided in another device.

[0099] Furthermore, each program of each device may be provided in another device, a program may consist of multiple programs, or multiple programs may be integrated into one program.

[0100] Furthermore, in this embodiment, a soccer match has been described as an event, but the present invention can be applied to any other type of event.

[0101] In addition, in this embodiment, the location of the event is a soccer stadium with seats, but the present invention can be applied even if there are no seats (for example, standing room only). For example, the server terminal 30 identifies the participation position of each user based on information on the area in the stadium that is assigned to the user in advance, instead of the seat information.

[0102] Also, in this embodiment, the user NFT includes information (address) indicating metadata as block data, but the metadata itself may be included in the block data.

[0103] In addition, in the present embodiment, the server terminal 30 identifies a user (confirmed user) by the user's location information, but the user may be identified by other methods. For example, the server terminal 30 may identify a user by requesting the user to input a predetermined login ID and password.

[0104] In the present embodiment, the method of specifying the range of the partial image on the additional information specification screen is to specify the start time and end time, but other ranges may be specified. For example, the server terminal 30 or the like may set scenes having a predetermined time length for the event (for example, scenes of each goal), and each scene may be specified on the additional information specification screen.

[0105] Furthermore, the configuration of the additional information or metadata described in this embodiment is merely an example, and for example, other attribute data may be added. [Explanation of symbols]

[0106] 1 Token management system, 10 Operation client terminal, 20 User client terminal, 30 Server terminal, 40 Blockchain system,

Claims

1. A management device for tokens in which ownership information is recorded and shared by each information processing device in a blockchain system including a plurality of information processing devices managed by each user, A storage device that stores information about users who plan to participate in the event; and a user identification process for identifying users who have participated in the event based on the stored information and acquiring information indicating video of the event captured at the event that has started; An original video token issuing process that generates a token including information indicating the acquired video of the event and information on the ownership of the identified user, and issues the generated token to the blockchain system; a metadata generation process for receiving designation of information associated with the specified user and indicating at least a partial range of a video of the started event, and generating metadata, which is data including the designated information and information indicating the video of the started event; a token generation process for generating a token including information indicating the generated metadata and information on the ownership of the identified user; and a control device that executes a token issuing process for issuing the generated token to the block chain system. A token management device comprising:

2. The token management device according to claim 1 , wherein the control device receives, in the metadata generation process, designation of information on a time period during the event as information indicating at least a portion of the range of the video.

3. The storage device stores the location of the event; The control device includes: In the user identification process, current location information is received from an information processing device related to the identified user, and it is determined whether or not a location indicated by the received location information corresponds to a location of a venue of the event. If the location indicated by the location information corresponds to the location of the venue of the event, the user related to the information processing device is identified as a user who participated in the event; generating metadata including the specified information related to the identified user, information indicating a video of the acquired event, and the location information in the metadata generation process; The token management device according to claim 1 .

4. The storage device stores the participation position of each user in the venue of the event, The control device includes: In the user identification process, a plurality of images of the event captured at the started event are acquired; In the metadata generation process, a video associated with an event participation position of the identified user is identified from the plurality of videos, a designation of information associated with the identified user and indicating at least a partial range of the identified video is accepted, and metadata including the designated information and information indicating the video of the started event is generated. The token management device according to claim 1 .

5. The token management device of claim 1, wherein the control device generates a token including information indicating a video of the started event and information about an administrator of the event as ownership information in the token issuance process, and issues the generated token to the blockchain system.

6. The token management device according to claim 1, wherein the control device executes a notification process to send information indicating that the generated token has been issued to the blockchain system to an information processing device related to the identified user.

7. The token management device of claim 1, wherein the control device executes a partial image generation process to generate information indicating at least a partial range of the image of the started event based on the image of the started event and the specified information.

8. A method for managing tokens in a blockchain system including a plurality of information processing devices managed by each user, the tokens being shared and stored by each information processing device and having ownership information recorded therein, comprising: An information processing device, Store information about users who are planning to attend the event, a user identification process for identifying users who have participated in the event based on the stored information and acquiring information indicating video of the event captured at the event that has started; An original video token issuing process that generates a token including information indicating the acquired video of the event and information on the ownership of the identified user, and issues the generated token to the blockchain system; a metadata generation process for receiving designation of information associated with the specified user and indicating at least a partial range of a video of the started event, and generating metadata, which is data including the designated information and information indicating the video of the started event; a token generation process for generating a token including information indicating the generated metadata and information on the ownership of the identified user; and executing a token issuing process for issuing the generated token to the block chain system. Token management methods.

9. A management system for tokens in which each information processing device stores and shares ownership information in a blockchain system including a plurality of information processing devices managed by each user, the system comprising: an administrator terminal including a communication device for transmitting information on users who are scheduled to participate in the event; A user terminal including a communication device for transmitting request information for issuing a token related to the event; A storage device that stores information received from the operator terminal; and a user identification process for identifying a user who participated in the event and who is related to the request information, based on the stored information, when the request information is received from the user terminal, and acquiring information indicating a video of the event that was shot at the event that has started; An original video token issuing process that generates a token including information indicating the acquired video of the event and information on the ownership of the identified user, and issues the generated token to the blockchain system; a metadata generation process for receiving designation of information associated with the specified user and indicating at least a partial range of a video of the started event, and generating metadata, which is data including the designated information and information indicating the video of the started event; a token generation process for generating a token including information indicating the generated metadata and information on the ownership of the identified user; A token management system comprising: a token management device having a control device that executes a token issuance process to issue the generated token to the blockchain system.

Images