System, method, and program for managing content

Abstract

To support management of digital contents using NFTs.SOLUTION: A content management server 10 according to one embodiment of the present invention is communicably connected to a token management server 22 and a user terminal 30 via a communication network 20, and provides users operating the user terminal 30 with a content management service for managing contents. The server 10 issues a token (NFT) with an image associated with a content owned by a user as a reference image, changes and saves the image, and changes the reference image of the token from an image before change to an image after change, thereby, enabling the image associated with the content managed using the token to be easily changed.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a system, a method, and a program for managing content. [Background technology]

[0002] Conventionally, in online games and the like, digital content such as items is sometimes given to users (see, for example, Patent Document 1 below). In recent years, such content has been managed using non-fungible tokens (NFTs). NFTs are non-fungible tokens issued using blockchain technology, and, for example, NFTs that refer to digital content are traded on token exchanges and the like. Such a mechanism can increase the value of content such as items in online games. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2014-087666 Summary of the Invention [Problem to be solved by the invention]

[0004] However, depending on the type of digital content, it is possible that some changes may be made to the content while the user owns it. If an NFT is issued every time the content is changed, managing the NFTs will become cumbersome.

[0005] One of the objects of the embodiments of the present invention is to support the management of digital content using NFTs. Other objects of the embodiments of the present invention will become apparent by reference to the entire specification. [Means for solving the problem]

[0006] A system according to one embodiment of the present invention is a system for managing content, comprising one or more computer processors and a storage device for storing information, wherein the storage device stores one or more images associated with each of a plurality of contents, and the one or more computer processors, in response to execution of readable instructions, execute the following steps: issuing a specific token, as a non-fungible token owned by a token management account of a first user for managing tokens issued on a blockchain, the specific token having a first image associated with a specific content held by the first user as a reference image; associating a second image, which is a modified version of the first image, with the specific content and storing it; and changing the reference image of the specific token from the first image to the second image.

[0007] A method according to one embodiment of the present invention is a method for managing content, executed by one or more computers that can access a storage device that stores one or more images associated with each of a plurality of contents, and includes the steps of issuing a specific token, as a non-fungible token owned by a token management account of a first user for managing tokens issued on a blockchain, with a first image associated with a specific content held by the first user as a reference image; storing a second image, which is a modified version of the first image, in association with the specific content; and changing the reference image of the specific token from the first image to the second image.

[0008] A program according to one embodiment of the present invention is a program for managing content, which causes one or more computers that can access a storage device that stores one or more images associated with each of a plurality of contents to execute the following steps: issuing a specific token, which has a first image associated with a specific content held by a first user as a reference image, as a non-fungible token owned by the first user's token management account for managing tokens issued on a blockchain; storing a second image, which is a modified version of the first image, in association with the specific content; and changing the reference image of the specific token from the first image to the second image, on one or more computers that can access a storage device that stores one or more images associated with each of a plurality of contents. [Effects of the Invention]

[0009] Various embodiments of the present invention support the management of digital content using NFTs. [Brief explanation of the drawings]

[0010] [Figure 1] 1 is a diagram showing a schematic configuration of a network including a content management server 10 according to an embodiment of the present invention. [Figure 2] FIG. 3 is a diagram illustrating an example of information managed by a user information table 151. [Figure 3] FIG. 3 is a diagram illustrating information managed by a content information table 152. [Figure 4] FIG. 3 is a diagram illustrating an example of information managed by an object information table 153. [Figure 5] FIG. 3 is a diagram illustrating an example of information managed by a owned content management table 154. [Figure 6] FIG. 10 is a diagram illustrating an example of information managed by a owned object management table 155. [Figure 7] FIG. 2 is a diagram illustrating an example of a home screen 50. [Figure 8] FIG. 6 is a diagram illustrating a card purchase screen 60. [Figure 9] 10 is a flowchart illustrating a process executed by the server 10 in response to selection of a purchase button 621 on the card purchase screen 60. [Figure 10] 10A and 10B are diagrams illustrating basic images of player cards. [Figure 11] FIG. 2 is a diagram for explaining two basic images stored in a content image database 156. [Figure 12] FIG. 2 is a sequence diagram illustrating a process performed between the content management server 10 and the token management server 22 when issuing a token. [Figure 13] FIG. 7 is a diagram illustrating a signature input screen 70. [Figure 14] FIG. 10 is a diagram illustrating a stamp acquisition screen 80. [Figure 15] FIG. 10 is a diagram illustrating a stamp acquisition screen 80 after a two-dimensional code is detected. [Figure 16] FIG. 10 is a diagram illustrating a card list screen 90. [Figure 17] FIG. 2 is a diagram illustrating a card editing screen 200. [Figure 18] FIG. 10 is a diagram illustrating an example of an image of a player card to which an additional object has been added. [Figure 19] 10 is a flowchart illustrating a process executed by the server 10 in response to selection of the confirm button 208. [Figure 20] 10A and 10B are diagrams for explaining basic images, signed images, stamped images, and images for tokens stored in a content image database 156. [Figure 21] 10 is a flowchart illustrating a process executed by the server 10 in response to the establishment of a trade of a player card between users. DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, embodiments of the present invention will be described with reference to the drawings. In the drawings, the same reference numerals may be used to designate the same or similar components.

[0012] FIG. 1 is a diagram illustrating a schematic configuration of a network including a content management server 10 according to an embodiment of the present invention. As illustrated, the server 10 is communicatively connected to a token management server 22 and a user terminal 30 via a communication network 20 such as the Internet. Although only one user terminal 30 is illustrated in FIG. 1, the server 10 is communicatively connected to a plurality of user terminals 30. The server 10 provides a content management service for managing content to a user operating the user terminal 30. The content management server 10 is an example of a device that implements all or part of the system of the present invention.

[0013] In this embodiment, the content managed in the content management service includes various types of digital content, such as cards, characters, and items, which are typically provided to users within the service.

[0014] First, we will explain the hardware configuration of the content management server 10. The content management server 10 is configured as a general computer, and as shown in Fig. 1, it includes a computer processor 11, a main memory 12, an input / output I / F 13, a communication I / F 14, and a storage (storage device) 15, and these components are electrically connected via a bus or the like (not shown).

[0015] The computer processor 11 is configured as a CPU, a GPU, or the like, and loads various programs stored in a storage 15 or the like into a main memory 12 and executes various instructions included in the programs. The main memory 12 is configured, for example, by a DRAM or the like.

[0016] The input / output I / F 13 includes various input / output devices for exchanging information with an operator, etc. The input / output I / F 13 includes, for example, information input devices such as a keyboard and a pointing device (e.g., a mouse, a touch panel, etc.), a voice input device such as a microphone, and an image input device such as a camera. The input / output I / F 13 also includes an image output device such as a display, and an audio output device such as a speaker.

[0017] The communication I / F 14 is implemented as hardware such as a network adapter, various communication software, or a combination of these, and is configured to enable wired or wireless communication via the communication network 20 or the like.

[0018] The storage 15 is configured, for example, with a magnetic disk, a flash memory, etc. The storage 15 stores various programs, including an operating system, and various data. For example, as shown in FIG. 1 , the storage 15 includes a user information table 151 for managing information about users, a content information table 152 for managing information about content managed in the content management service, an object information table 153 for managing information about objects added to content, a owned content management table 154 for managing information about content owned by the user, a owned object management table 155 for managing information about objects owned by the user, and a content image database 156 for storing images associated with content owned by the user. The storage 15 also stores, for example, a server-side program 40 according to an embodiment of the present invention. The program 40 is a program that causes the content management server 10 to function as all or part of a system for providing a content management service. At least a portion of the server-side program 40 may be configured to be executed on the user terminal 30 via a terminal-side program 42, which will be described later.

[0019] In this embodiment, the content management server 10 may be configured using a plurality of computers each having the above-described hardware configuration. For example, the server 10 may be configured by one or more server devices.

[0020] The content management server 10 configured in this manner can be configured to function as a web server and an application server, and executes various processes in response to requests from a terminal-side program 42 installed in the user terminal 30, and transmits screen data (e.g., HTML data) and control data according to the results of the processes to the user terminal 30. The user terminal 30 outputs a web page or other screen based on the received data.

[0021] Next, we will explain the hardware configuration of the user terminal 30. The user terminal 30 is configured as a general computer, and as shown in Fig. 1, it includes a computer processor 31, a main memory 32, an input / output I / F 33, a communication I / F 34, and a storage (storage device) 35, and these components are electrically connected via a bus or the like (not shown).

[0022] The computer processor 31 is configured as a CPU, a GPU, or the like, and loads various programs stored in a storage 35 or the like into the main memory 32 and executes various instructions included in the programs. The main memory 32 is configured, for example, by a DRAM or the like.

[0023] The input / output I / F 33 includes various input / output devices for exchanging information with an operator, etc. The input / output I / F 33 includes, for example, information input devices such as a keyboard and a pointing device (e.g., a mouse, a touch panel, etc.), an audio input device such as a microphone, and an image input device such as a camera. The input / output I / F 33 also includes an image output device such as a display, and an audio output device such as a speaker.

[0024] The communication I / F 34 is implemented as hardware such as a network adapter, various communication software, or a combination thereof, and is configured to be able to realize wired or wireless communication via the communication network 20 or the like.

[0025] The storage 35 is configured, for example, by a magnetic disk or a flash memory. The storage 35 stores various programs including an operating system, various data, and the like. The programs stored in the storage 35 can be downloaded and installed from an application market or the like. The storage 35 also stores a terminal-side program 42. The program 42 can be configured as a web browser or other application (for example, an application for the content management service of this embodiment), and can be configured to execute at least a part of the server-side program 40, as described above.

[0026] In this embodiment, the user terminal 30 may be configured as a smartphone, a tablet terminal, a wearable device, a personal computer, a game terminal, or the like.

[0027] A user operating a user terminal 30 configured in this manner can use the content management service provided by the server 10 by communicating with the server 10 via a terminal-side program 42 installed in storage 35 or the like.

[0028] Next, we will explain the functions of the content management server 10 configured as above. As shown in Figure 1, the computer processor 11 of the server 10 is configured to function as a management function control unit 111 and a content management unit 113 by executing instructions included in a program (for example, at least a part of the server-side program 40) loaded into the main memory 12.

[0029] The management function control unit 111 is configured to execute various processes related to the control of the management functions of the service. For example, the management function control unit 111 transmits screen data and control data of various screens related to the management functions to the user terminal 30, executes various processes in response to operation input by the user via the screens output on the user terminal 30, and transmits screen data and control data according to the results of the processes to the user terminal 30. The management functions controlled by the management function control unit 111 include, for example, login processing (user authentication), billing control, and user account management.

[0030] The content management unit 113 is configured to execute various processes related to content management. For example, the content management unit 113 transmits screen data and control data of various screens related to content management to the user terminal 30, executes various processes in response to operation input by the user via the screens output on the user terminal 30, and transmits screen data, control data, etc. according to the results of the processes to the user terminal 30.

[0031] In this embodiment, the content management unit 113 is configured to issue a token, which uses a first image associated with content held by the user as a reference image, as an NFT (non-fungible token issued on a blockchain) owned by the user's token management account. The image associated with the content is stored in the content image database 156. For example, the content management unit 113 requests the token management server 22 to issue such a token. The token management server 22 has a hardware configuration as a general computer and has a function of managing fungible and non-fungible tokens issued on a blockchain. Such tokens are managed on, for example, the Ethereum platform. The user's token management account is managed, for example, in the user information table 151.

[0032] Furthermore, the content management unit 113 is configured to store a second image, which is a modified version of a first image associated with a content, in the content image database 156 in association with the content.

[0033] The content management unit 113 is also configured to change the reference image of a token issued with a first image as the reference image from the first image to a second image. The reference of the token is typically a URL of the corresponding image file, and is recorded on the blockchain as part of the token's metadata. For example, the content management unit 113 changes the image with the file name corresponding to the token's reference URL in the content image database 156 from the first image to the second image.

[0034] In this way, the content management server 10 in this embodiment issues a token (NFT) that uses an image associated with content owned by a user as a reference image, modifies and saves the image, and changes the image referenced by the token from the image before the change to the image after the change, thereby enabling easy modification of images associated with content managed using tokens. In other words, the server 10 supports management of digital content using NFTs.

[0035] In this embodiment, the content management unit 113 may be configured to grant content to a user. For example, a user may acquire content for a fee or free of charge. In this case, the content management unit 113 may be configured to issue a corresponding token (a token owned by the user's token management account and having an image associated with the granted content as a reference image) in conjunction with granting content to a user (e.g., before or after the granting). This configuration makes it possible to issue a corresponding token in conjunction with granting content.

[0036] Furthermore, the content management unit 113 may be configured to change the image referenced by the corresponding token to the second image when a changed second image is saved. For example, when saving the second image, the content management unit 113 saves it with a path and file name corresponding to the URL referenced by the corresponding token, or saves the second image separately and then overwrites the image with the path and file name corresponding to the URL referenced by the corresponding token with the second image. This configuration makes it possible to change the image referenced by the corresponding token when an image associated with content is changed.

[0037] In this embodiment, the user may be allowed to individually select the image referenced by the token. That is, the content management unit 113 may be configured to change the image referenced by the token to an image selected by the user from among multiple images associated with the corresponding content. Information regarding the multiple images associated with the content is managed, for example, in the owned content management table 154. For example, the user selects the image referenced by the token from among multiple images via a screen output on the user terminal 30. This configuration allows the user to individually select the image referenced by the token.

[0038] In this embodiment, the change of an image can be realized in various ways. For example, the content management unit 113 can be configured to generate, as a second image, an image in which an object is added to a first image. For example, the object to be added can be selected by a user from among multiple objects, or can be automatically identified by the server 10. Such a configuration enables the change of an image by adding an object.

[0039] In this embodiment, the added objects include various types of objects. For example, the added objects include objects having images that are individually identifiable among multiple objects. Individually identifiable objects include, for example, objects that include identification information (such as a number or code). This configuration enables the generation of images to which individually identifiable images are added, which can increase the value of the content.

[0040] Furthermore, for example, the object to be added may include a person's signature. In this case, the image of the signature may be an image common to multiple objects, or may be an image that can be individually identified (for example, an image that has actually been individually handwritten). This configuration makes it possible to generate an image to which a person's signature has been added.

[0041] Furthermore, for example, the added object may include an object created by the user, such as a photograph taken by the user, etc. This configuration allows the user to add an object created by the user to an image, which may encourage the user to enjoy creating images.

[0042] The content management unit 113 may also be configured to grant an object to a user who satisfies a predetermined condition. For example, the user may acquire the object for a fee or free of charge. This configuration allows the user to enjoy acquiring the object.

[0043] The content may also include content related to an event. In this case, the content management unit 113 may be configured to assign objects related to the event and / or the venue to the user in response to the user's actions (such as input of information) at the event venue. For example, the content may include a sports player's card. In this case, objects related to the game and / or the venue are assigned to the user in response to the user's actions at the stadium of a sports match (such as reading and inputting data embedded in a code or the like available at the stadium using the user terminal 30, entering a geographical area corresponding to the stadium (including location information of the user terminal 30), and inputting user identification information via an information processing device installed at the stadium). This configuration enables the assignment of objects in response to the user's actions at the event venue, helping to, for example, create excitement for the event.

[0044] Furthermore, the content management unit 113 can be configured to issue a predetermined notification to the user in response to the addition of an object. This configuration can prompt the user to whom the object has been added to add the object to the image.

[0045] In this embodiment, when the owner of content changes, the owner of the corresponding token may also change. That is, when the owner of content changes from a first user to a second user, the content management unit 113 may be configured to change the owner of a token corresponding to the content (a token referencing an image of the content) from the token management account of the first user to the token management account of the second user. For example, the content management unit 113 requests the token management server 22 to change the owner of the token. This configuration makes it possible to easily synchronize a change in the owner of content with a change in the owner of the corresponding token.

[0046] Furthermore, in this embodiment, the owner of the corresponding content may be changed in accordance with a change in the owner of the token. That is, the content management unit 113 may be configured to change the owner of the content corresponding to the token from the first user to the second user in accordance with a change in the owner of the token from the token management account of a first user to the token management account of a second user. For example, the content management unit 113 executes such a change in the content owner in response to a request from the token management server 22. This configuration makes it possible to easily synchronize a change in the token owner with a change in the owner of the corresponding content.

[0047] Next, a specific example of one aspect of the content management server 10 of this embodiment having such functions will be described. In this example, the content management server 10 provides a player card management service that manages player cards of a specific professional sports team. Note that, in addition to managing such player cards, the server 10 may also provide various services for fans of the target team.

[0048] First, the information managed by each table in this example will be described. FIG. 2 illustrates information managed by the user information table 151 in this example. The user information table 151 in this example manages information about users who use the player card management service, and as shown in the figure, manages information such as "basic information" including account name, gender, date of birth, etc., "number of owned points" which is the number of owned points that can be exchanged for various items including player cards, "number of owned coins" which is the number of owned coins that can also be exchanged for various items, and "token management account" in association with a "user account" that identifies an individual user. Points are free items that are granted to users at various times (for example, as a login bonus). Coins are paid items that are purchased with real currency.

[0049] The token management account is an account for the token management service provided by the token management server 22. In this example, the token management service manages tokens using the Ethereum platform, and the token management account is associated with the Ethereum address of the corresponding user. The token management account is also called a wallet.

[0050] 3 illustrates information managed by the content information table 152 in this example. The content information table 152 in this example manages information related to the design of each player card provided in the player card management service, and as shown in the figure, manages information such as a "player ID" that identifies the corresponding player, an "image URL" that is the URL of the corresponding image file, and "rarity," in association with a "card design ID" that identifies an individual card design. The image files of the card designs are managed in storage 15 or the like. Also, in this example, there are multiple different card designs for the same player.

[0051] 4 illustrates information managed by object information table 153 in this example. Object information table 153 in this example manages information related to additional objects that can be added to a basic image of a player card, which will be described later, and as shown, manages information such as an "object type" that is a classification of the additional object, a "player ID" that identifies the corresponding player, and an "image URL" that is the URL of the corresponding image file, in association with an "object ID" that identifies each individual additional object. Image files of the additional objects are managed in storage 15 or the like.

[0052] In this example, the additional objects are classified into three categories: "common signature," "autograph," and "stamp," and the object type is set to a value corresponding to one of these categories. A common signature is an image of a signature created by a player by hand, but is an additional object that has an image that is common (copied) among multiple objects. An autograph is an image of a signature created by a player by hand individually, and is an additional object that has an image that can be individually identified among multiple objects. If the additional object is a common signature or autograph, the player ID is set to the value of the corresponding player, but if it is a stamp, nothing is set.

[0053] 5 illustrates information managed by the owned content management table 154 in this example. The owned content management table 154 in this example manages information related to player cards owned by users, and as shown in the figure, manages information such as an "owning user account" which is the user account of the user who owns this player card, an "applied card design ID" which identifies the applied card design, a "basic image URL" which is the URL of the basic image, a "signed image URL" which is the URL of the signed image, a "stamped image URL" which is the URL of the stamped image, a "token ID" of the corresponding token, and a "token reference URL" which is the URL of the image referenced by the corresponding token, in association with a "serial number" which identifies an individual player card.

[0054] Although details will be described later, in this example, three variations of images, a basic image, an image with a signature, and an image with a stamp, are associated with one individual player card identified by a serial number. Image files corresponding to these images are managed in the content image database 156 (a predetermined folder in the storage 15). In addition, one of these three variations of images is set as the image referenced by the token corresponding to the player card.

[0055] 6 illustrates information managed by owned object management table 155. In this example, owned object management table 155 manages information related to objects to be added that are owned by users, and as shown in the figure, manages combinations of "user accounts" that identify individual users and "object IDs" that identify objects to be added that are owned by the corresponding users.

[0056] The information managed by each table in this example has been described above. Next, the processing executed by the content management server 10 and the screens output on the user terminal 30 in this example will be described. FIG. 7 illustrates an example of a home screen 50 output on the user terminal 30. The screen 50 is the starting point for using the player card management service of this example, and as shown in the figure, has a card menu button 521, a shop menu button 522, a gacha menu button 523, and an other menu button 524. The card menu button 521 is a screen element for viewing and editing player cards owned by the user. Functions related to these player cards will be described later.

[0057] The shop menu button 522 is a screen element that allows the user to purchase items such as player cards (in exchange for points or coins). When this button 522 is selected, a screen (not shown) for selecting the type of item to purchase is displayed. The user selects the type of item to purchase via this screen.

[0058] When a player card is selected as the type of item to be purchased, a card purchase screen 60 shown in Fig. 8 is output. This screen 60 is a screen for purchasing a player card, and as shown in the figure, a plurality of individual display areas 62, each corresponding to an individual card design, are arranged in two columns.

[0059] The individual display area 62 displays an image of the corresponding card design, information about the corresponding player, and the like, and also has a purchase button 621. The user selects the purchase button 621 in the area 62 corresponding to the card design to be purchased.

[0060] Here, the processing when a user purchases a player card will be described. FIG. 9 is a flowchart illustrating the processing executed by the server 10 in response to selection of the purchase button 621 on the card purchase screen 60. As shown in the figure, the server 10 first assigns a serial number to the purchased player card (step S100). The serial number is a number that identifies an individual player card, and different numbers are assigned even to player cards with the same card design. A new serial number is issued based on the latest serial number (identified by referencing the owned content management table 154).

[0061] The server 10 then generates a basic image of the purchased player card (step S110). Specifically, an image of the selected card design to which the assigned serial number is added is generated as the basic image. As described above, the basic image is one of the three variations of the image associated with the player card.

[0062] 10 shows an example of the basic image of a player card. As shown in the figure, the basic image is composed of an image CD of the card design and an image SR indicating the serial number added to the upper left corner of the image CD.

[0063] 9, the server 10 then saves the generated basic image (step S120). The image file of the basic image is stored in the content image database 156.

[0064] The server 10 then sets the saved basic image as the image referenced by the token (step S130). Specifically, a URL referenced by the token corresponding to the purchased player card is set, and the basic image is saved as the image for the token according to the path and file name included in the URL. The image file of the image for the token is stored in the content image database 156. The URL referenced by the token is set according to a predetermined rule, and for example, the path and file name are set based on the user account, serial number, etc.

[0065] 11 is a diagram for explaining two basic images stored in the content image database 156. As shown in the figure, the content image database 156 separately stores an image file (file name "AAA1") of the basic image for the player card management service saved in step S120, and an image file (file name "AAA") of the basic image for the token (as the image referenced by the token) saved in step S130.

[0066] 9, the server 10 then issues a corresponding token (step S140). Specifically, the issuance of the token is performed in conjunction with communication with the token management server 22.

[0067] 12 is a sequence diagram illustrating the processing performed between the content management server 10 and the token management server 22 when issuing a token. First, the content management server 10 transmits a token issuance request to the token management server 22 (step S200). As shown in the figure, the token issuance request is made along with the token management account of the corresponding user (the user who purchased the player card) and the URL of the token reference destination. The token management account of the corresponding user is managed in the user information table 151.

[0068] Next, the token management server 22, which has received the token issuance request, issues a token (step S210). Specifically, an NFT is issued that is owned by the token management account received from the content management server 10 and references the URL also received. The referenced URL is recorded on the blockchain as part of the NFT's metadata. In addition, in response to the issuance of the NFT, the token management server 22 transmits a token ID that identifies the issued NFT to the content management server 10. The content management server 10 receives the token ID from the token management server 22 (step S220).

[0069] 9, the server 10 then registers information about the player cards owned by the user (step S150). Specifically, a new record is created in the owned content management table 154, and corresponding values ​​are set for each of the data items: serial number, owning user account, applied card design ID, basic image URL, token ID, and token reference URL.

[0070] The above describes the process when a user purchases a player card. Returning to the home screen 50 in FIG. 7, the gacha menu button 523 is a screen element that allows the user to acquire items such as player cards through a lottery. When the button 523 is selected, a screen (not shown) for conducting a lottery is output, and the user can conduct a lottery via the screen. In the lottery, a winning item is determined according to the winning probability of each item to be selected, and the determined winning item is granted to the user.

[0071] Here, when a player card is awarded to a user as a winning item, the same process as that shown in the flowchart in Fig. 9 is executed as when a user purchases a player card. Specifically, a serial number is assigned to the player card awarded to the user, a basic image is generated and saved, and then a corresponding token is issued.

[0072] Here, the process of granting an additional object to a user will be described. Of the additional objects described above, a common signature is granted to a user as a reward such as a login bonus. The granting of an additional object to a user is registered in the owned object management table 155.

[0073] Furthermore, among the additional objects, the handwritten autograph is provided to the user via an operation on a screen displayed on the user terminal 30. FIG. 13 illustrates an example of a signature input screen 70 displayed on the user terminal 30. The screen 70 is a screen for generating and acquiring an additional object for a player's handwritten autograph, and is displayed via selection of the Other menu button 524 on the top screen 50. As shown in the figure, the signature input screen 70 has a signature input area 72, a player selection area 74 for selecting a player for whom to input a handwritten autograph, and a Send button 76. The signature input area 72 is configured as an area for accepting handwritten input. For example, at an event such as a player autograph session, a user will display the signature input screen 70 on the user terminal 30 and request the player to input a handwritten autograph in the signature input area 72.

[0074] When the send button 76 is selected, the autograph entered via the autograph input area 72 is registered as an additional object and given to the user. Specifically, an image file of the entered autograph is stored in the storage 15 or the like, information about the autograph is registered in the object information table 153, and furthermore, the autograph given to the user is registered in the owned object management table 155. The player ID in the object information table 153 is set to a value corresponding to the player selected via the player selection area 74.

[0075] Furthermore, among the additional objects, stamps are also given to the user through operations on a screen output on the user terminal 30. FIG. 14 illustrates a stamp acquisition screen 80 output on the user terminal 30. The screen 80 is a screen for acquiring stamps related to a sports game venue, and is output via selection of the other menu button 524 on the top screen 50. As shown in the figure, the stamp acquisition screen 80 has an image display area 82 that displays an image input via a camera. In response to the output of the stamp acquisition screen 80, a two-dimensional code included in the image input via the camera is detected. For example, a two-dimensional code corresponding to a stamp is posted at a game venue, and the user outputs the stamp acquisition screen 80 to detect the two-dimensional code.

[0076] FIG. 15 illustrates an example of the stamp acquisition screen 80 after the detection of the two-dimensional code. As shown in the figure, the stamp acquisition screen 80 in this state has an image display area 84 that displays an image of the stamp corresponding to the two-dimensional code, and a send button 86. The two-dimensional code has embedded therein a URL for the stamp image, and the image of the stamp identified by the URL is displayed in the image display area 84. When the send button 86 is selected, the corresponding stamp image is assigned to the user as an object to be added. Specifically, the assignment of the stamp to the user is registered in the owned object management table 155.

[0077] In this example, when the user terminal 30 is located within a predetermined geographical range corresponding to a game venue (for example, determined by the location information of the user terminal 30), a stamp related to the game venue may be assigned to the corresponding user.

[0078] The above has described the processing when adding an additional object. Returning to the home screen 50 of FIG. 7, the card menu button 521 is a screen element for viewing and editing player cards owned by the user. When the button 521 is selected, a card list screen 90 shown in FIG. 16 is output. The screen 90 is a screen for displaying a list of player cards owned by the user, and as shown in the figure, individual display areas 92, each displaying information about an individual player card, are arranged in two columns. The player cards owned by the user are identified by referring to the owned content management table 154.

[0079] The individual display area 92 displays an image of the corresponding player card and information about the corresponding player, and also has an edit button 921. The image of the player card displayed is the image currently set as the reference image for the token, from among the basic image, the image with a signature, and the image with a stamp. The user selects the edit button 921 of the individual display area 92 corresponding to the player card to be edited.

[0080] 17 shows an example of a card editing screen 200 that is output in response to selection of the edit button 921. The screen 200 is a screen for editing a selected player card, and as shown in the figure, has an image display area 202 that displays an image of the player card, a signed image button 204 with the character string "Signature" added, a stamped image button 205 with the character string "Stamp" added, a basic image button 206 with the character string "None" added, and a confirm button 208.

[0081] Buttons 204 to 206 are configured so that only one of them can be selected. The autograph image button 204 can be selected when the user has an additional object for the autograph (a common autograph or an autograph) of the player corresponding to the selected player card. In response to the selection of button 204, an image in which the autograph additional object is added to the basic image of the player card is displayed in the image display area 202 as an autograph-added image. Note that if the user has multiple autograph additional objects, they can also select the object to add.

[0082] Furthermore, the stamp-added image button 205 can be selected when the user has an additional stamp object. In response to the selection of this button 205, an image in which the additional stamp object is added to the basic image of the player card is displayed as an image with stamp in the image display area 202. Note that if the user has multiple additional stamp objects, the user can also select the object to add.

[0083] FIG. 18 illustrates an example of an image of a player card to which an additional object has been added. The top row of FIG. 18(A) is an image with a signature in which an additional object for a signature has been added to a basic image, and as shown, a signature image SG has been added to the lower right corner of the card. The bottom row of FIG. 18(B) is an image with a stamp in which an additional object for a stamp has been added to a basic image, and as shown, a stamp image ST has been added to the lower right corner of the card. Note that the user may be able to adjust the position at which the additional object is added.

[0084] Returning to the card editing screen 200 of FIG. 17, when the basic image button 206 is selected, the basic image is displayed in the image display area 202.

[0085] 19 is a flowchart illustrating a process executed by the server 10 in response to selection of the confirm button 208 on the card editing screen 200. As shown in the figure, the server 10 first saves the displayed image as the latest image (step S310) if the image displayed in the image display area 202 is not the same as the latest image saved at that time (NO in step S300). Specifically, if the displayed image with the signature or the stamp is different from the corresponding image saved at that time (for example, if the added object has been changed), or if these images have not yet been saved, it is determined that the displayed image is not the same as the latest image, and the displayed image is saved.

[0086] Next, the server 10 sets the displayed image as the image referenced by the token (step S320). Specifically, the displayed image (either the signed image, the stamped image, or the basic image) overwrites the image of the path and file name included in the URL referenced by the corresponding token.

[0087] 20 is a diagram illustrating the basic image, autographed image, stamped image, and token image stored in the content image database 156. As shown in the figure, the content image database 156 stores, as images for the player card management service, an image file for an autographed image (file name "AAA2") and an image file for a stamped image (file name "AAA3") in addition to an image file for a basic image (file name "AAA1"), and any of these three images is set as the token image (the corresponding image file (file name "AAA") is overwritten). The card editing screen 200 can also be said to be a screen for editing the autographed image and stamped image for the player card management service and setting any of the three variation images as the token image (changing the token image).

[0088] In this example, player cards are traded between users within the player card management service provided by the content management server 10. A player card transaction is completed, for example, when a transferor user specifies the serial number of the target player card and the transferee user account, applies for the transaction, and the transferee user approves the transaction. Such a transaction is carried out via a screen (not shown) displayed on the user terminal 30.

[0089] 21 is a flowchart illustrating a process executed by the server 10 in response to the completion of a trade of a player card between users. As shown in the figure, the server 10 first changes the owner of the player card in the service to be traded (step S400). Specifically, the owner user account of the corresponding record in the owned content management table 154 is changed from the transferor to the transferee.

[0090] Next, the server 10 changes the owner of the corresponding token (step S410). Specifically, the content management server 10 transmits a request to change the owner of the corresponding token to the token management server 22. The change request is made along with the token ID of the target token and the token management account of the transferee. Upon receiving this request, the token management server 22 changes the owner of the target token to the token management account of the transferee. This change of token owner is recorded on the blockchain.

[0091] In the above example, changes to the image referenced by the token may also be recorded on the blockchain. For example, when the content management server 10 notifies the token management server 22 of a change to the image, the token management server 22 records the change on the blockchain as part of the metadata of the NFT.

[0092] In the above example, either a signature or a stamp can be added as an additional object to the base image, but both may be added. Also, additional objects other than signatures and stamps may be added to the base image. For example, a user-generated object (e.g., a photograph) may be added to the base image as an additional object. Also, the serial number may be excluded from the base image and treated as an additional object.

[0093] In the above example, the holder of the player card within the player card management service may be changed in response to a request from the token management server 22. For example, in the token management service provided by the token management server 22, when the owner of the token is changed and a request accompanied by the token ID and the token management account of the transferee is received, the holder of the player card corresponding to the received token ID may be changed to the user corresponding to the token management account also received.

[0094] In the above example, the token management server 22 has the function of managing tokens, but the content management server 10 may have the function of managing tokens.

[0095] In the above example, the signed image and stamped image are edited and the token image is changed via the card editing screen 200, but such editing and / or changing may be performed automatically. For example, when an additional object is assigned to a user, an image in which the additional object is added to a basic image may be automatically generated, and the generated image may be automatically set as the token image.

[0096] In the above example, the player cards to which additional objects can be added to the basic image may be limited. For example, additional objects may be added to player cards whose rarity is equal to or greater than a predetermined value, while additional objects may not be added to player cards whose rarity is less than the predetermined value.

[0097] In the example described above, the image for the player card management service and the image for the token are stored separately, but it is not necessary to manage the images separately in this manner. For example, the player card management service may manage only the basic image, and generate an image with a signature or an image with a stamp each time an image is set as an image for a token.

[0098] In the above example, player cards are exemplified as digital content managed by the content management server 10, but in other examples of this embodiment, various digital content other than player cards may be subject to management.

[0099] The content management server 10 according to the present embodiment described above issues a token (NFT) that uses an image associated with content owned by a user (e.g., a player card) as a reference image, modifies and saves the image, and changes the image referenced by the token from the image before the change to the image after the change, thereby enabling easy modification of images associated with content managed using tokens. In this way, the server 10 supports the management of digital content using NFTs.

[0100] In other embodiments of the present invention, some or all of the functions of the content management server 10 in the above-described embodiments may be realized by cooperation between the content management server 10 and the user terminal 30, or may be realized by the user terminal 30.

[0101] The processes and procedures described herein, other than those explicitly described, may be implemented by software, hardware, or any combination thereof. For example, the processes and procedures described herein may be implemented by implementing logic corresponding to the processes and procedures in media such as integrated circuits, volatile memory, non-volatile memory, and magnetic disks. The processes and procedures described herein may also be implemented as computer programs corresponding to the processes and procedures and executed by various computers.

[0102] Although processes and procedures described herein are described as being performed by a single device, software, component, or module, such processes or procedures may be performed by multiple devices, software, components, and / or modules. Also, the software and hardware elements described herein may be implemented by combining them into fewer components or breaking them down into more components.

[0103] In this specification, even if a component of the invention is described as either singular or plural, or is described without limitation as either singular or plural, the component may be either singular or plural unless the context requires otherwise. [Explanation of symbols]

[0104] 10 Content Management Server 11. Computer Processor 111 Management function control section 113 Content Management Department 15. Storage 151 User Information Table 152 Content Information Table 153 Object Information Table 154 Owned Content Management Table 155 Retained Object Management Table 156 Content Image Database 22 Token Management Server 30 User terminals 40 Server-side programs 42 Terminal side program 50 Home Screen 60 Card purchase screen 70 Signature input screen 80 Stamp acquisition screen 90 Card List Screen 200 Card editing screen

Claims

1. 1. A system for managing content, comprising one or more computer processors and a storage device for storing information, the system comprising: the storage device stores one or more images associated with each of a plurality of contents; The one or more computer processors, in response to execution of the readable instructions: A step of issuing a specific token having a first image associated with specific content owned by the first user as a reference image as a non-fungible token owned by a token management account of the first user for managing tokens issued on a blockchain; storing a second image obtained by modifying the first image in association with the specific content; changing the image referred to by the specific token from the first image to the second image; system.

2. The one or more computer processors further perform the step of providing the specific content to the first user; The step of issuing the specific token includes issuing the specific token in association with the provision of the specific content to the first user. The system of claim 1.

3. the step of changing the image referred to by the specific token to the second image includes changing the image referred to by the specific token to the second image in association with saving the second image.

3. The system of claim 1 or 2.

4. The one or more computer processors further perform the step of changing an image referred to by the specific token to an image selected by the first user from a plurality of images associated with the specific content.

4. The system of any one of claims 1 to 3.

5. The one or more computer processors further execute a step of generating, as the second image, an image in which an image of a specific object is added to the first image.

5. A system according to any one of claims 1 to 4.

6. the specific object is selected by the first user from among a plurality of objects; The system of claim 5.

7. The specific object includes an object having an image that can be individually identified among a plurality of objects.

7. The system of claim 5 or 6.

8. The specific object includes a person's signature.

8. A system according to any one of claims 5 to 7.

9. The specific object includes an object created by the first user.

9. A system according to any one of claims 5 to 8.

10. The one or more computer processors further execute a step of granting the specific object to the first user who satisfies a predetermined condition.

10. A system according to any one of claims 5 to 9.

11. the specific content is content related to an event, the step of assigning the specific object includes assigning the specific object related to the event and / or the venue to the first user in response to an action by the first user at the venue of the event. The system of claim 10.

12. The one or more computer processors further execute a step of changing the owner of the specific token from the token management account of the first user to the token management account of the second user when the holder of the specific content changes from the first user to the second user.

12. A system according to any one of claims 1 to 11.

13. The one or more computer processors further execute a step of changing the owner of the specific content from the first user to the second user in response to a change in the owner of the specific token from the token management account of the first user to the token management account of a second user.

13. A system according to any one of claims 1 to 12.

14. 1. A method for managing content, executed by one or more computers having access to a storage device storing one or more images associated with each of a plurality of pieces of content, comprising: A step of issuing a specific token having a first image associated with specific content owned by the first user as a reference image as a non-fungible token owned by a token management account of the first user for managing tokens issued on a blockchain; storing a second image obtained by modifying the first image in association with the specific content; changing the image referred to by the specific token from the first image to the second image; method.

15. A program for managing content, the program comprising: one or more computers that can access a storage device that stores one or more images associated with each of a plurality of pieces of content; A step of issuing a specific token having a first image associated with specific content owned by the first user as a reference image as a non-fungible token owned by a token management account of the first user for managing tokens issued on a blockchain; storing a second image obtained by modifying the first image in association with the specific content; changing the image referred to by the specific token from the first image to the second image; program.

Images