JP7801205B2 - Token management device, token management method, and token management system - Google Patents

Description

The present invention relates to a token management device, a token management method, and a token management system.

Technology for creating data assets using so-called blockchain-based non-fungible tokens (NFTs) is being widely developed.

For example, by issuing NFTs to participants of events such as sports games or concerts that can prove they attended the event, participants can boast about their experience at the event and gain empathy with others.

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

International Publication No. 2021/246498

However, the content of the experiences that event participants have varies greatly depending on the specific form of participation. Meanwhile, event organizers also have experiences that they would like participants to share. Patent Document 1 fails to fully take such circumstances into consideration.

The present invention was made in light of these 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 experiences that are in line with their intentions.

One aspect of the present invention for solving the above-mentioned 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 that stores information of users who plan to participate in an event; and a control device that executes the following operations: a user identification process that identifies users who participated in the event based on the stored information and acquires information indicative of video of the event that was shot at the started event; an original video token issuance process that generates a token including the acquired information indicative of the video of the event and information about an administrator of the event , and issues the generated token to the blockchain system; a metadata generation process that accepts designation of information that is associated with the identified user and indicates at least a partial range of the video of the started event, and generates metadata that is data including the designated information and information indicative of the video of the started event; a token generation process that generates a token including information indicative of the generated metadata and ownership information of the identified user; and a token issuance process that issues the generated token to the blockchain system.

Another aspect of the present invention for solving the above-mentioned problems is a management system for tokens in a blockchain system configured including a plurality of information processing devices managed by each user, in which the tokens are shared and stored by each information processing device and ownership information is recorded, the management system including an operator terminal having a communication device for transmitting information of users who plan to participate in an event, a user terminal having a communication device for transmitting request information for the issuance of a token related to the event, a storage device for storing information received from the operator terminal, and a user identification process for, when the request information is received from the user terminal, identifying a user who participated in the event and related to the request information based on the stored information, and acquiring information showing video of the event that was taken at the event that has started, and and a token management device having a control device that executes an original video token issuance process that generates a token including information indicating the video of the started event and information about an administrator of the event, and issues the generated token to the blockchain system; a metadata generation process that accepts designation of information that is associated with the specified user and indicates at least a partial range of the video of the started event, and generates metadata, which is data including the designated information and information indicating the video of the started event; a token generation process that generates a token including information indicating the generated metadata and ownership information of the specified user; and a token issuance process that issues the generated token to the blockchain system.

According to the present invention, it is possible to generate a token that allows the event organizer and the event participants to share an experience that is in line with their intentions.
Configurations and effects other than those described above will become apparent from the following description of the embodiments.

FIG. 1 is a diagram illustrating an example of a configuration of a token management system according to an embodiment of the present invention. 1 is a diagram illustrating the configuration of a venue where an event according to an embodiment of the present invention is held. FIG. 10 is a diagram illustrating an example of an NFT issuing authority management table. FIG. 10 is a sequence diagram illustrating an example of processing performed in a token management system. FIG. 10 illustrates an example of a data configuration of an event management table. FIG. 10 is a diagram showing an example of metadata related to an original video NFT. FIG. 10 is a diagram showing an example of an additional information specification screen. FIG. 10 is a diagram showing another example of the additional information specification screen. FIG. 10 is a diagram showing an example of metadata related to a user NFT.

Embodiments of the present invention will be described in detail below with reference to the drawings.

<Configuration, Function>
1 is a diagram illustrating an example of the configuration of a token management system 1 according to this embodiment. The token management system 1 includes an operator client terminal 10 (operator terminal) managed by an operator who hosts and manages a predetermined 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 of the user's experience at the event, and a blockchain system 40 (BC: Block Chain
) and

The blockchain system 40 is composed of multiple BC terminals 50 (information processing devices), each of which shares and stores user NFTs. This blockchain system 40 includes terminals managed by each user and a terminal managed by the operator. Note that the operator client terminal 10 or the user client terminal 20 may also function as a BC terminal 50.

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

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 by a wired or wireless communication network 5 such as the Internet, a LAN (Local Area Network), a WAN (Wide Area Network), or a dedicated line.

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:

The management client terminal 10 also has a functional unit called a management wallet storage unit 121. The management wallet storage unit 121 stores the manager's account (address) and its private key in the blockchain system 40.

The user client terminal 20 includes a control device 21 such as a CPU (Central Processing Unit), a RAM (Random Access Memory), a ROM (Read Only Memory), and a HDD (Hard Drive).
The communication device 2 includes 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 25 configured with a NIC (Network Interface Card), a wireless communication module, a USB (Universal Serial Interface) module, a serial communication module, or the like.
5.

The user client terminal 20 also has a functional unit called 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 user may also be stored by the server terminal 30.

The BC terminal 50 includes a control device 51 such as a CPU (Central Processing Unit), a storage device 52 such as a RAM (Random Access Memory), a ROM (Read Only Memory), a HDD (Hard Disk Drive), or an SSD (Solid State Drive), and a NIC (Network Interface Card).
), and a communication device 53 configured with a wireless communication module, a USB (Universal Serial Interface) module, a serial communication module, etc. The BC terminal 50 may also 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.

The BC terminal 50 also has a functional unit called a token information storage unit 521. The token information storage unit 521 stores each NFT in a shared manner between the BC terminals 50.

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 also 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.

The server terminal 30 also has 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 issuance unit 325, and a partial video generation unit 326.

The user identification unit 321 identifies users 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 participating in the event, determines whether the location indicated by the received location information corresponds to the event's location (such as a seating area at the venue), and if the location indicated by the location information corresponds to the event's location, identifies the user associated with the user client terminal 20 as a user who participated in the event.

As will be described in more detail below, the server terminal 30 stores footage of the event filmed by the organizer (hereinafter referred to as original footage). In this embodiment, there are multiple original videos for one event. That is, in this embodiment, multiple camera devices are installed 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 captures footage of the match from a different angle. The placement of the camera devices will be described in more detail below.

The BC management unit 322 performs processing to generate and issue NFTs. For example, the BC management unit 322 issues user NFTs generated by the processing described below to the blockchain system 40.

The metadata generation unit 323 generates metadata for the user NFT. That is, the metadata generation unit 323 receives from the user a specification of information indicating at least a partial range of the original video, 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.

For example, the metadata generation unit 323 identifies, from multiple original videos, an original video that corresponds to the event participation location of the user identified by the user identification unit 321. The metadata generation unit 323 then accepts specification of information indicating at least a partial range of the identified original video, and generates metadata including the specified information and information indicating the original video.

Furthermore, for example, the metadata generating unit 323 accepts designation of information about a time period in an event (in this embodiment, the start time and end time of the time period) as information indicating at least a partial range of the original video.

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.

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

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.

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

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.

The event management table storage unit 327 stores an event management table that manages events held by the administrator (details will be described later). Note that the event management table may also be stored in the administrator client terminal 10.

The original video storage unit 328 stores video of the event (original video) filmed by the organizer.

The issuance authority memory unit 329 stores an NFT issuance authority management table, which is a table that determines 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.

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

(Venue configuration)
2 is a diagram illustrating the configuration of a venue where an event according to this embodiment is held. As shown in the figure, the 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 in the event area 210 is seated. The seating area 220 is an area consisting of a plurality of seats, and specifically includes 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").

In addition, the venue 200 is provided by the operator with a plurality of camera devices 230 for shooting original images, each corresponding to one of the seating areas 220 . Specifically, there are provided a first camera 230a for capturing first original video, the shooting direction of which is set to the direction of the line of sight (direction of the pitch) of users watching in the first seating area 221; a second camera 230b for capturing second original video, the shooting direction of which is set to the direction of the line of sight (direction of the pitch) of users watching in the second seating area 222; a third camera 230c for capturing third original video, the shooting direction of which is set to the direction of the line of sight (direction of the pitch) of users watching in the third seating area 223; a fourth camera 230d for capturing fourth original video, the shooting direction of which is set to the direction of the line of sight (direction of the pitch) of users watching in the fourth seating area 224; and a fifth camera 230e for capturing fifth original video, the shooting direction of which is set to the direction of the line of sight (direction of the pitch) of users watching in the fifth seating area 225. Each of the image capturing devices 230 captures original video from a different angle during the event (during the match).

(NFT Issuance Authority Management Table)
3 shows an example of an NFT issuance authority management table 300. The NFT issuance authority management table 300 shows the relationship between the type of seating area 220 assigned to each user at the venue and the original video that the user watching from that seating area 220 can use as material for a partial video (user NFT).

In the case of the NFT issuance authority management table 300 shown in the figure, users watching in each seating area 220 can use one or more original videos 320 specified in the NFT issuance authority management table 300 as material for their partial videos. For example, a user watching in the first seating area 221 ("A") can use all original videos 320 (320a-320f) as material for their partial videos (premium seats). A user watching in the second seating 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 material for their partial videos. A user watching in the fourth seating 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 camera device closest to their seat) as material for their partial videos (regular seats, which only use original videos from the camera device set up on the home side). The NFT issuance authority management table 300 is set in advance by the operator, etc.

The functions of the functional units of each of the information processing devices described above are realized by the control devices 11, 21, 31, and 51 reading predetermined programs that realize the respective functional units from the storage devices 12, 22, 32, and 52. Furthermore, each program can be recorded on, for example, a portable or fixed recording medium and distributed. Note that all or part of these programs may be realized using virtual information processing resources provided using virtualization technology, process space separation technology, or the like, such as a virtual server provided by a cloud system. Furthermore, all or 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.

<Processing explanation>
FIG. 4 is a sequence diagram illustrating an example of processing performed by the token management system 1.

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

For example, the management client terminal 10 receives information about participation in the event in advance from the user client terminal 20 of each user who wishes to make a reservation to participate in the event. Then, the management client terminal 10 transmits the information to the server terminal 30. Note that these processes may also be executed by the server terminal 30.

(Event management table)
5 is a diagram showing an example of the data configuration of the event management table 500. The event management table 500 has the following data items: event ID 501, in which information identifying the event (e.g., an ID) is set; user ID 502, in which information identifying the user participating in the event (e.g., an ID) is set; ticket 503, in which information identifying the type of event ticket purchased by the user (e.g., seat area and seat number) is set; event location 504, in which information about 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.

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

When the server terminal 30 receives application information from each user client terminal 20, it references the event management table 500 to determine whether the application information for each user is authentic (s23). Specifically, the server terminal 30 references the event management table 500 to determine whether there is a record in which the event ID, user ID, ticket information, and event location in the application information are set to event ID 501, user ID 502, ticket 503, and location 504, respectively. Furthermore, the server terminal 30 determines whether the location indicated by the application information is within a certain distance from the location indicated by the location information 505 of that record.

The server terminal 30 sends a notification (acceptance completion notification) to the user client terminal 20 of the user (confirmed user) whose application information is authentic, indicating that the application information has been confirmed (s25).

After that, when the event starts, the operator (for example, the operator client terminal 10) takes pictures using each camera device 230 and generates original video of the event. The server terminal 30 acquires and stores these original videos. In this embodiment, an ID is assigned to each original video.

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

Specifically, the server terminal 30 first generates and stores metadata including information (such as a URL) indicating the location of the original video. The server terminal 30 then generates an NFT that includes, as block data, information indicating this metadata (for example, a URL, account name, or address, or other information that can identify the location of the metadata) and the wallet address of the operator's management client terminal 10 as ownership information, and issues the generated NFT to the blockchain system 40.

(Metadata related to original video NFT)
6 shows an example of metadata associated with an original video NFT. This metadata 600 includes the date, time, and name of the event 610 (identified from an event ID or the like), the name of the event location or venue 620, confirmed user information 630, and information 640 indicating the original video.

Confirmed user information 630 includes information 631 about the seating area (and seat number) of each confirmed user, and information 632 about the wallet address associated with that confirmed user. Information 640 indicating original video includes an ID 641 for each original video and information 642 about the storage location of each original video (URL in the figure).

Note that this metadata 600 may include information about a serial number assigned to each original video NFT to increase its rarity. Furthermore, the seating area (and seat number) information 631 in this metadata 600 may be set to the location information received in s23 (e.g., latitude, longitude, altitude, time, etc.).

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 video of the original video (s31).

For example, when the server terminal 30 receives information requesting the 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.

Then, once the input of the additional information specification on the additional information specification screen is completed, the user client terminal 20 requests the server terminal 30 to issue a user NFT (s33).

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

The additional information specification screen 700 accepts the user's selection of one original video from the displayed list of original videos. The additional information specification screen 700 then further accepts the user's input of the start time 730 and end time 740 of the time period for 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 seating area corresponds to only one original video.

The additional information specification 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.

Figure 8 shows another example of an additional information specification screen. This additional information specification screen 800 accepts the user's selection of multiple original videos. The additional information specification screen 800 then further accepts input from the user of the start time 830 and end time 840 (e.g., specified in hours, minutes, seconds, and milliseconds) of the time period for each video portion to be extracted as a partial video from each of the selected original videos 810a, b, and c.

The additional information specification screen 800 may also accept input of information regarding the ranking or order of each selected original video 810, to be reflected in the metadata described below. The additional information specification screen 800 may also accept multiple selections of a certain original video 810.

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

(Metadata related to user NFT)
9 is a diagram showing an example of metadata related to a user NFT. This metadata 900 includes information 910 (a 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.

This metadata 900 includes information 921 (ID in the figure) that identifies each original video selected on the additional information specification screen 700, 800, and the start time 922 and end time 923 of the partial video in that original video.

Note that this metadata 900 may also include information about a serial number assigned to each original video NFT, thereby increasing the rarity of the NFT.

Then, as shown in FIG. 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 that includes, as block data, information indicating the metadata generated in s35 (e.g., information that can identify the location of the metadata, such as a URL, account name, or address) and, as ownership information, the wallet address of the user client terminal 20 associated with the verified user who applied for the issuance of the NFT in s31, and issues the generated NFT to the blockchain system 40.

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.

For example, the server terminal 30 references the URL of the original video in the metadata generated in processing s27 and checks whether the original video file exists. The server terminal 30 then compares the duration of the original video at that URL with the start time and end time selected on the additional information specification screens 700 and 800.

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).

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).

For example, the server terminal 30 acquires the 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 specification screen 700, 800. The server terminal 30 stores the trimmed part of the video, i.e., the partial video, in a predetermined URL. The server terminal 30 stores the URL
The information is sent to each user's client terminal 20 or to each user's BC terminal 50 in the blockchain system 40.

After that, each user can access the partial video released in s41 and watch it (s43).

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

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

Furthermore, for example, if a user attends an event in a premium seat, other users can relive the event from various perspectives.

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

In other words, the token management device of this embodiment accepts from users who participated in the event a specification of the portion (additional information) of the original video of the event provided by the event administrator that corresponds to that user, and issues an NFT linked to that additional information.

In this way, the token management device of this embodiment can generate tokens that allow event organizers and event participants to share experiences in line with their intentions.

In addition, the token management device of this embodiment receives current location information from the user client terminal 20 of a user participating in an event, and if the location indicated by the received location information corresponds to the location of the event venue, identifies that 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.

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

In addition, the token management device of this embodiment accepts specification of time period information (start time and end time) for the event as information indicating the range of the original video.

This allows the experiences of users who participate in the event to become more concrete, increasing the value of the user NFTs generated based on this.

In addition, the token management device of this embodiment identifies an original video corresponding to the user's event participation location from multiple original videos, accepts from the user a specification of the part of the original video that corresponds to the user who participated in the event (additional information), and generates metadata including that additional information.

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

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.

This allows the authenticity of the original video that forms the basis of the user NFT to be proven, increasing the value of the user NFT.

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

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

In addition, the token management device of this embodiment generates a partial video based on the original video and metadata (additional information).

This allows each user, including verified users associated with the User NFT, to relive the experience they had by participating in the event.

The token management system 1 of this embodiment also includes an operator client terminal 10 that transmits information about users who plan to participate in an event, a user client terminal 20 that transmits application information for the issuance of a token related to the event, and a token management device. The token management device stores information received from the operator 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.

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

The present invention is not limited to the above-described embodiments, and can be implemented using any components within the scope of the gist of the invention. The embodiments and modifications described above are merely examples, and the present invention is not limited to these contents as long as the characteristics of the invention are not impaired. Furthermore, while various embodiments and modifications have been described above, the present invention is not limited to these contents. Other aspects conceivable within the technical spirit of the present invention are also included within the scope of the present invention.

For example, some of the hardware provided in each device in this embodiment may be provided in another device.

Furthermore, each program of each device may be provided on another device, a program may consist of multiple programs, or multiple programs may be integrated into a single program.

Furthermore, in this embodiment, a soccer match was described as the event, but the present invention can be applied to any other type of event.

Furthermore, in this embodiment, the event location is a soccer stadium with seating, but the present invention can also be applied when there are no seats (for example, standing room only). For example, instead of seat information, the server terminal 30 identifies each user's participation location based on information about the area within the venue that has been pre-assigned to each user.

In addition, in this embodiment, the user NFT includes information (address) indicating metadata as block data, but the metadata itself may also be included in the block data.

In addition, in this embodiment, the server terminal 30 identifies a user (confirmed user) based on 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 enter a specific login ID and password.

In addition, in this embodiment, the method for specifying the range of the partial video on the additional information specification screen is to specify the start time and end time, but other ranges may also be specified. For example, the server terminal 30 or the like may set scenes with a predetermined duration for the event in advance (for example, scenes of each goal), and each scene may be specified on the additional information specification screen.

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

1. Token management system, 10. Management client terminal, 20. User client terminal, 30. Server terminal, 40. Blockchain system,

Claims (8)

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 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 about the administrator of the event , and issues the generated token to the blockchain system;
a metadata generation process for receiving designation of information associated with the identified user and indicating at least a partial range of video of the started event, and generating metadata that is data including the designated information and information indicating 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 issuance process to issue the generated token to the blockchain system. The token management device of claim 1, wherein the control device, during the metadata generation process, accepts specification of information about a time period during the event as information indicating at least a portion of the range of the video. the storage device stores the location of the event;
The control device
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 the location indicated by the received location information corresponds to the 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 the acquired video of the event, and the location information in the metadata generation process;
The token management device according to claim 1 . the storage device stores the participation location of each user at the venue of the event;
The control device
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 the 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 . 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 associated with the identified user. The token management device of claim 1, wherein the control device executes a partial video generation process that generates information showing at least a partial range of the video of the started event based on the video of the started event and the specified information. A method for managing tokens in a blockchain system including a plurality of information processing devices managed by each user, in which the tokens are shared and stored by each information processing device and whose ownership information is recorded,
The information processing device
Store information about users who plan to attend the event,
a user identification process for identifying users who 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 about the administrator of the event , and issues the generated token to the blockchain system;
a metadata generation process for receiving designation of information associated with the identified user and indicating at least a partial range of video of the started event, and generating metadata that is data including the designated information and information indicating 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 token issuance process for issuing the generated token to the blockchain system. A management system 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,
an administrator terminal having a communication device for transmitting information on users who plan 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 related to the request information based on the stored information when the request information is received from the user terminal, and acquiring information showing 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 about the administrator of the event , and issues the generated token to the blockchain system;
a metadata generation process for receiving designation of information associated with the identified user and indicating at least a partial range of video of the started event, and generating metadata that is data including the designated information and information indicating 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.