Classifications

• • A—HUMAN NECESSITIES
  • A63—SPORTS; GAMES; AMUSEMENTS
  • A63F—CARD, BOARD, OR ROULETTE GAMES; INDOOR GAMES USING SMALL MOVING PLAYING BODIES; VIDEO GAMES; GAMES NOT OTHERWISE PROVIDED FOR
  • A63F13/00—Video games, i.e. games using an electronically generated display having two or more dimensions
  • A63F13/60—Generating or modifying game content before or while executing the game program, e.g. authoring tools specially adapted for game development or game-integrated level editor
  • A63F13/69—Generating or modifying game content before or while executing the game program, e.g. authoring tools specially adapted for game development or game-integrated level editor by enabling or updating specific game elements, e.g. unlocking hidden features, items, levels or versions
• • A—HUMAN NECESSITIES
  • A63—SPORTS; GAMES; AMUSEMENTS
  • A63F—CARD, BOARD, OR ROULETTE GAMES; INDOOR GAMES USING SMALL MOVING PLAYING BODIES; VIDEO GAMES; GAMES NOT OTHERWISE PROVIDED FOR
  • A63F13/00—Video games, i.e. games using an electronically generated display having two or more dimensions
  • A63F13/70—Game security or game management aspects
  • A63F13/79—Game security or game management aspects involving player-related data, e.g. identities, accounts, preferences or play histories
• • A—HUMAN NECESSITIES
  • A63—SPORTS; GAMES; AMUSEMENTS
  • A63F—CARD, BOARD, OR ROULETTE GAMES; INDOOR GAMES USING SMALL MOVING PLAYING BODIES; VIDEO GAMES; GAMES NOT OTHERWISE PROVIDED FOR
  • A63F13/00—Video games, i.e. games using an electronically generated display having two or more dimensions
  • A63F13/80—Special adaptations for executing a specific game genre or game mode
• • A—HUMAN NECESSITIES
  • A63—SPORTS; GAMES; AMUSEMENTS
  • A63F—CARD, BOARD, OR ROULETTE GAMES; INDOOR GAMES USING SMALL MOVING PLAYING BODIES; VIDEO GAMES; GAMES NOT OTHERWISE PROVIDED FOR
  • A63F13/00—Video games, i.e. games using an electronically generated display having two or more dimensions
  • A63F13/85—Providing additional services to players
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
  • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
  • G06Q50/10—Services

Definitions

• This disclosure relates to a program, a method, an information processing device, and a system.
• Patent document 1 also envisages rare items and characters being the subject of auctions.
• the purpose of this disclosure is to increase the interest in collecting digital assets.
• the program causes the processor to execute the steps of managing digital items included in digital assets, and generating, in response to a request from a user, information representing the digital items owned by the user to be transferred to the service in order to receive the reward, where a service exists that grants rewards according to the ownership status of the digital items.
• the present disclosure aims to increase the interest in collecting digital assets.
• FIG. 1 is a block diagram showing an example of the overall configuration of a system 1.
• FIG. 2 is a block diagram illustrating an example of the configuration of a terminal device 10 illustrated in FIG. 1.
• FIG. 2 is a diagram illustrating an example of a functional configuration of a first server 20.
• FIG. 2 is a diagram illustrating an example of a functional configuration of a second server 30.
• FIG. 13 is a diagram showing the data structure of card information 182.
• FIG. 2 is a diagram showing the data structure of a user information table 2021.
• FIG. 2 shows the data structure of a card master table 2022.
• a diagram showing the data structure of deck information table 2023. 13 is a diagram showing the data structure of a match information table 2024.
• FIG. 23 shows the data structure of a card management table 2026.
• 13 is a diagram showing the data structure of a privilege information table 3021 stored in the second server 30.
• FIG. 10 is a diagram illustrating an example of the operation of the terminal device 10 and the first server 20 when a user purchases a card.
• 11 is a diagram illustrating an example of the operation of the terminal device 10 and the first server 20 when managing cards used by users in a match.
• FIG. 11 is a diagram illustrating an example of the operation of the terminal device 10 and the first server 20 when managing cards based on user support.
• FIG. 11 is a diagram illustrating an example of the operation of the terminal device 10, the first server 20, and the second server 30 when the second server 30 grants a privilege based on a digital card to a user.
• FIG. 10 is a diagram illustrating an example of the operation of the terminal device 10 and the first server 20 when a user purchases a card.
• 11 is a diagram illustrating an example of the operation of the terminal device 10 and the
• FIG. 2 is a schematic diagram showing a display example of a display 141 of a terminal device 10.
• FIG. 3A and 3B are schematic diagrams illustrating examples of displays on a display 141.
• 3A and 3B are schematic diagrams illustrating examples of displays on a display 141.
• FIG. 2 is a block diagram showing the basic hardware configuration of a computer 90.
• a server that provides digital assets manages digital assets owned by a user.
• the user requests information indicating the ownership status of the user's digital assets from the server.
• the server In response to the user's request, the server generates information indicating the ownership status of the user's digital assets and transmits it to the user.
• the user transfers the generated information to a service provider that provides a specified service, and receives benefits according to the digital assets owned.
• Fig. 1 is a block diagram showing an example of the overall configuration of a system 1.
• the system 1 shown in Fig. 1 includes, for example, a terminal device 10, a first server 20, and a second server 30.
• the terminal device 10, the first server 20, and the second server 30 are communicatively connected via, for example, a network 80.
• the system 1 includes two terminal devices 10, but the number of terminal devices 10 included in the system 1 is not limited to two.
• the number of terminal devices 10 included in the system 1 may be one, or three or more.
• the system 1 shows an example in which the system 1 includes one each of the first server 20 and the second server 30, but the number of the first server 20 and the second server 30 included in the system 1 is not limited to one each.
• the first server 20 and the second server 30 may be composed of multiple servers depending on the functions they have.
• the first server 20 and the second server 30 may be, for example, a collection of multiple devices as one server.
• the method of allocating the multiple functions required to realize the first server 20 and the second server 30 according to this embodiment to one or multiple pieces of hardware can be appropriately determined in consideration of the processing capacity of each piece of hardware and/or the specifications required for the first server 20 and the second server 30.
• the terminal device 10 shown in FIG. 1 is, for example, an information processing device operated by a user playing a digital TCG.
• the terminal device 10 is realized, for example, by a mobile terminal such as a smartphone or a tablet.
• the terminal device 10 may also be realized by a stationary PC (Personal Computer), a laptop PC, or the like, or may be realized by a wearable terminal such as an HMD (Head Mount Display).
• HMD Head Mount Display
• the terminal device 10 comprises a communication IF (Interface) 12, an input device 13, an output device 14, a memory 15, storage 16, and a processor 19.
• the input device 13 is a device (e.g., a touch panel, a touch pad, etc.) for accepting input operations from a user.
• the output device 14 is a device (a display, a speaker, etc.) for presenting information to the user.
• the first server 20 is, for example, an information processing device that manages information related to cards and information related to decks.
• the first server 20 can be said to be, for example, an information processing device that manages digital assets related to the services used by the user.
• the first server 20 is realized, for example, by a computer connected to the network 80. As shown in FIG. 1, the first server 20 includes a communication IF 22, an input/output IF 23, a memory 25, a storage 26, and a processor 29.
• the input/output IF 23 functions as an input device for accepting input operations from the user, and as an interface with an output device for presenting information to the user.
• the second server 30 is, for example, an information processing device that manages information related to a specified service.
• the services provided by the second server 30 are independent of the services provided by the first server 20.
• the second server 30 grants specified benefits to users based on the users' digital assets managed by the first server 20. There may or may not be a specified relationship between the person managing the first server 20 and the person managing the second server 30.
• the second server 30 is realized, for example, by a computer connected to the network 80.
• the second server 30 includes a communication IF 32, an input/output IF 33, a memory 35, a storage 36, and a processor 39.
• the input/output IF 33 functions as an input device for accepting input operations from the user, and as an interface with an output device for presenting information to the user.
• Each information processing device is configured by a computer equipped with an arithmetic unit and a storage device.
• the basic hardware configuration of the computer and the basic functional configuration of the computer realized by the hardware configuration will be described later.
• the terminal device 10 the first server 20, and the second server 30, explanations that overlap with the basic hardware configuration and basic functional configuration of the computer described later will be omitted.
• Fig. 2 is a block diagram showing an example of the configuration of the terminal device 10 shown in Fig. 1.
• the terminal device 10 includes a communication unit 120, an input device 13, an output device 14, an audio processing unit 17, a microphone 171, a speaker 172, a camera 160, a position information sensor 150, a storage unit 180, and a control unit 190.
• the blocks included in the terminal device 10 are electrically connected to each other, for example, by a bus or the like.
• the communication unit 120 performs processes such as modulation and demodulation for the terminal device 10 to communicate with other devices.
• the communication unit 120 performs transmission processing on the signal generated by the control unit 190 and transmits it to the outside (e.g., the first server 20).
• the communication unit 120 performs reception processing on the signal received from the outside and outputs it to the control unit 190.
• the input device 13 is a device for inputting instructions or information by the user operating the terminal device 10.
• the input device 13 is realized, for example, by a touch-sensitive device 131 or the like where instructions are input by touching the operation surface.
• the terminal device 10 is a PC or the like
• the input device 13 may be realized by a reader, keyboard, mouse, or the like.
• the input device 13 converts instructions input by the user into electrical signals and outputs the electrical signals to the control unit 190.
• the input device 13 may also include, for example, a receiving port that receives electrical signals input from an external input device.
• the output device 14 is a device for presenting information to a user operating the terminal device 10.
• the output device 14 is realized, for example, by a display 141 or the like.
• the display 141 displays data according to the control of the control unit 190.
• the display 141 is realized, for example, by an LCD (Liquid Crystal Display) or an organic EL (Electro-Luminescence) display or the like.
• the audio processing unit 17 performs digital-to-analog conversion processing of the audio signal.
• the audio processing unit 17 converts the signal provided by the microphone 171 into a digital signal and provides the converted signal to the control unit 190.
• the audio processing unit 17 also provides the audio signal to the speaker 172.
• the audio processing unit 17 is realized, for example, by a processor for audio processing.
• the microphone 171 accepts audio input and provides an audio signal corresponding to the audio input to the audio processing unit 17.
• the speaker 172 converts the audio signal provided by the audio processing unit 17 into audio and outputs the audio to the outside of the terminal device 10.
• Camera 160 is a device that receives light using a light receiving element and outputs the light as a photographic signal.
• the location information sensor 150 is a sensor that detects the location of the terminal device 10, and is, for example, a GPS (Global Positioning System) module.
• the GPS module is a receiving device used in a satellite positioning system. In a satellite positioning system, signals are received from at least three or four satellites, and the current location of the terminal device 10 in which the GPS module is installed is detected based on the received signals.
• the location information sensor 150 may detect the current location of the terminal device 10 from the location of the wireless base station to which the terminal device 10 is connected.
• the storage unit 180 is realized, for example, by the memory 15 and the storage 16, and stores data and programs used by the terminal device 10.
• the storage unit 180 stores, for example, user information 181, card information 182, and deck information 183.
• User information 181 includes, for example, information about a user who plays a TCG.
• Information about a user includes, for example, a user ID, the user's name, age, address, date of birth, date of registration, etc.
• Card information 182 includes, for example, information about cards. Card information 182 may also include information about cards owned by the user. Details will be described later.
• Deck information 183 includes, for example, information about the deck constructed by the user. Details will be described later.
• the control unit 190 is realized when the processor 19 reads a program stored in the storage unit 180 and executes instructions contained in the program.
• the control unit 190 controls the operation of the terminal device 10.
• the control unit 190 fulfills the functions of an operation reception unit 191, a transmission/reception unit 192, a management unit 193, a display control unit 194, and a battle processing unit 195.
• the operation reception unit 191 performs processing for receiving instructions or information input from the input device 13. Specifically, for example, the operation reception unit 191 receives instructions or information input from the touch-sensitive device 131, etc.
• the operation reception unit 191 also receives images input from the camera 160. Specifically, for example, the operation reception unit 191 receives image data captured by the camera 160.
• the operation reception unit 191 also receives audio information input from the microphone 171. Specifically, for example, the operation reception unit 191 receives audio data that is input from the microphone 171 and converted into digital data by the audio processing unit 17.
• the transmission/reception unit 192 performs processing for the terminal device 10 to transmit and receive data to and from external devices such as the first server 20 in accordance with a communication protocol. Specifically, for example, the transmission/reception unit 192 transmits instructions entered by the user or various pieces of acquired information to the first server 20. The transmission/reception unit 192 also receives information provided from the first server 20. Information provided from the first server 20 includes, for example, information about cards newly acquired by the user, information about decks registered in the first server 20, information created based on cards (digital assets) managed by the first server 20, and the like. The transmission/reception unit 192 also transmits specified information to the second server 30.
• the management unit 193 manages the user information 181, card information 182, and deck information 183 stored in the storage unit 180. For example, when information about a user is edited, the management unit 193 stores the edited information in the user information 181. Furthermore, when the management unit 193 receives information about a card, it updates the card information 182. Specifically, for example, when a match using cards is held, the management unit 193 updates the card information 182. Furthermore, for example, when support is given via a card, the management unit 193 updates the card information 182. Furthermore, when a deck is organized, the management unit 193 updates the deck information 183.
• the display control unit 194 controls the output device 14 to display a predetermined image to the user.
• the display control unit 194 controls the display 141 to display a management screen for cards owned by the user based on the information managed in the card information 182 and the information managed in the deck information 183.
• the display control unit 194 may control the display 141 to display a management screen for cards owned by the user based on the information managed in the first server 20.
• the display control unit 194 also controls the display 141 to display information related to a card selected by the user and related to a match played using the card.
• the display control unit 194 also controls the display 141 to display information related to a card selected by the user and related to support via the card.
• the display control unit 194 also controls the display 141 to display information created in the first server 20 based on cards (digital assets) managed in the first server 20.
• the match processing unit 195 controls processing for a match with another user. For example, the following modes of the match are assumed. - Play against the CPU using a deck built with digital cards - Play against other players using a deck built with digital cards - Play in tournaments
• FIG. 3 is a diagram showing an example of a functional configuration of the first server 20.
• the first server 20 fulfills the functions of a communication unit 201, a storage unit 202, and a control unit 203.
• the communication unit 201 performs processing for the first server 20 to communicate with external devices.
• the memory unit 202 has, for example, a user information table 2021, a card master table 2022, a deck information table 2023, a match information table 2024, and a card management table 2026.
• the user information table 2021 is, for example, a table that stores information about users who have registered for services related to the TCG. Details will be described later.
• the card master table 2022 is, for example, a table that stores information about cards available to users. Details will be described later.
• the deck information table 2023 is, for example, a table that stores information about decks registered by users. Details will be described later.
• the match information table 2024 is, for example, a table that stores information about matches that have been held in the past. Details will be described later.
• the card management table 2026 is, for example, a table that stores information for managing cards acquired by users. Details will be described later.
• the control unit 203 is realized by the processor 29 reading a program stored in the storage unit 202 and executing instructions contained in the program. By operating according to the program, the control unit 203 fulfills the functions of a reception control module 2031, a transmission control module 2032, a management module 2033, a generation module 2034, and a battle processing module 2035.
• the reception control module 2031 controls the process in which the first server 20 receives signals from external devices according to a communication protocol.
• the transmission control module 2032 controls the process in which the first server 20 transmits signals to an external device according to a communication protocol. Specifically, for example, the transmission control module 2032 transmits information based on the owned digital assets, generated by the first server 20, to the terminal device 10.
• the management module 2033 manages the tables stored in the memory unit 202. In other words, the management module 2033 manages the digital assets stored in the first server 20. Specifically, for example, the management module 2033 updates the card management table 2026 in response to an operation related to a card. The management module 2033 also updates the deck information table 2023 in response to an operation related to a deck. When the management module 2033 receives information related to a match, it updates the match information table 2024 and the card management table 2026. When the management module 2033 receives information related to cheering, it updates the card management table 2026.
• the generating module 2034 generates information according to the digital assets managed by the first server 20. For example, when a user requests information indicating that the user has digital assets that satisfy a predetermined condition, the generating module 2034 generates the requested information. Specifically, for example, when a user requests information indicating that the user has two or more predetermined digital cards, the generating module 2034 generates the requested information.
• the digital card desired by the user is not necessarily based on the rarity of the card.
• the digital card desired by the user is set, for example, by the second server 30. Also, for example, when a user requests information indicating that the user has a digital card on which a predetermined record remains, the generating module 2034 may generate the requested information.
• a digital card on which a predetermined record remains refers to, for example, a digital card on which information regarding a predetermined match is stored, a digital card on which information regarding predetermined support is stored, or a digital card on which a predetermined transaction has been made.
• the generation module 2034 when a user requests information indicating that the user has a specific deck, the generation module 2034 generates the requested information.
• the deck desired by the user is set, for example, by the second server 30.
• the generation module 2034 may generate the requested information.
• a deck on which specific records remain refers, for example, to a deck on which information regarding a specific battle is stored.
• the match processing module 2035 controls the processing of matches between users. For example, the match processing module 2035 controls matches between players using decks constructed from digital cards.
• Fig. 4 is a diagram showing an example of a functional configuration of the second server 30.
• the second server 30 fulfills the functions of a communication unit 301, a storage unit 302, and a control unit 303.
• the communication unit 301 performs processing for the second server 30 to communicate with external devices.
• the storage unit 302 has, for example, a bonus information table 3021.
• the bonus information table 3021 is, for example, a table that stores information (bonus information) about bonuses to be granted to users. Details will be described later.
• the control unit 303 is realized by the processor 39 reading a program stored in the storage unit 302 and executing the instructions contained in the program.
• the control unit 303 performs the functions of a reception control module 3031, a transmission control module 3032, and an assignment module 3033 by operating according to the program.
• the reception control module 3031 controls the process in which the second server 30 receives signals from an external device according to a communication protocol. Specifically, for example, the reception control module 3031 receives information from the terminal device 10 indicating that the user owns a specific digital asset.
• the transmission control module 3032 controls the process in which the second server 30 transmits a signal to an external device according to a communication protocol. Specifically, for example, the transmission control module 3032 transmits information related to the benefit to the terminal device 10.
• the granting module 3033 grants a bonus to the user.
• the granting module 3033 refers to the bonus information table 3021 and determines whether the digital asset owned by the user meets the conditions for granting a bonus. If the conditions are met, the granting module 3033 grants the bonus to the user.
• the granting of a bonus to the user may be achieved, for example, by the transmission control module 3032 sending the bonus to the user.
• the granting of a bonus to the user may also be achieved, for example, by the granting module 3033 handing the bonus to the user at a store after confirming that the conditions for granting a bonus are met.
• FIG. 5 and 6 are diagrams showing the data structure of information stored in the terminal device 10. Note that Fig. 5 and Fig. 6 are merely examples, and do not exclude data not shown.
• FIG. 5 is a diagram showing the data structure of card information 182.
• Card information 182 shown in FIG. 5 is a table having columns such as card ID, name, type, attribute, card information, match information, support information, image data, etc., with card management ID as a key.
• Card information 182 may also have information on regulations or rarity, etc.
• the card management ID is an item that stores an identifier for uniquely identifying a card.
• cards with the same name, effect, rarity, and regulations, i.e., exactly the same cards are assigned different card management IDs.
• the card ID is an item that stores an identifier for uniquely identifying the type of card. In this embodiment, the same card ID is assigned to exactly the same cards.
• the name is an item that stores the name of the card.
• the type is an item that stores the type of card. In this embodiment, card types include, for example, character cards that can fight during a match, action cards (energy cards) that are used in association with characters, and effect cards that exert specific effects during a match (support cards, goods cards, stadium cards, etc.).
• An attribute is an item that stores the nature to which a character belongs.
• attributes include, for example, fire, water, lightning, grass, super, steel, evil, fighting, etc.
• Card information is an item that stores information that explains the contents of the card. If the card type is character, the card information includes, for example, the character's attack power, stamina, the amount of energy required to perform a technique, the amount of energy required to escape, weaknesses, resistance, special properties possessed by the character, etc. If the card type is support, goods, or stadium, the card information includes, for example, the requirements for using the card, effects that occur when the card is used, etc.
• the match information is an item that stores information about a TCG match that was conducted by incorporating the corresponding card into a deck.
• a match ID that can identify the match is stored as the match information.
• the first server 20, for example, registers, as the match information, information that identifies a match that was conducted by a user using a deck that incorporated the corresponding card.
• the item "match information" is, for example, match information registered by the first server 20 that is sent to and stored in the terminal device 10.
• the cheering information is an item that stores information about the TCG match that was supported in association with the corresponding card.
• a match ID that can identify the match that was supported is stored as the cheering information.
• the first server 20 manages the cheering provided by the user in association with the corresponding card by linking it to the card management ID.
• the item "cheering information" is the cheering information managed by the first server 20 that is sent to the terminal device 10 and stored therein.
• Image data is an item that stores an image. Image data may also store reference information (path) to an image data file located elsewhere.
• path reference information
• FIG. 6 is a diagram showing the data structure of deck information 183.
• Deck information 183 shown in FIG. 6 is a table with columns such as name, organization cards, completion, update date, and registration information, with the deck ID as a key.
• deck information 183 may also have information related to the deck's nickname, deck usage history, etc.
• the nickname of a deck is a name given based on a common understanding among multiple users, for example, based on characteristic cards used in the deck, succinctly expressing the characteristics of the deck.
• Deck ID is an item that stores an identifier for uniquely identifying a deck.
• Name is an item that stores the name of the deck. The name is given by the user, for example.
• Organization card is an item that stores the cards that make up the deck. In the organization card, for example, the card management ID of the card that makes up the deck is stored.
• Complete is an item that stores whether or not the deck is complete.
• a circle indicates that the deck is complete, and a cross indicates that the deck is not complete.
• a completed deck means, for example, that the deck has been assembled with a specified number of cards and is ready to be used in a match.
• Update date is an item that stores the date on which the deck configuration was changed. In calculating the update date, the use of a card used in one deck in another deck may also be treated as a change.
• Registration information is an item that stores the relationship with a deck registered in the first server 20. The registration information stores, for example, a deck code issued when the deck is registered in the first server 20.
• FIGS. 7 to 11 are diagrams showing the data structure of the information stored in the first server 20. Note that FIGS. 7 to 11 are merely examples and do not exclude data that is not listed.
• FIG. 7 is a diagram showing the data structure of the user information table 2021.
• the user information table 2021 shown in FIG. 7 is a table having columns such as name, age, address, date of birth, and date of registration, with the user ID as a key.
• the user information table 2021 is not limited to the above, and may also have proficiency as a column.
• the user ID is an item that stores an identifier for uniquely identifying a user.
• the name is an item that stores the user's name.
• the age is an item that stores the user's age.
• the address is an item that stores the place where the user lives.
• the date of birth is an item that stores the date the user was born.
• the registration date is an item that stores the date the user started using the TCG-related services.
• Records in the user information table 2021 are added when a new user is registered.
• FIG. 8 is a diagram showing the data structure of the card master table 2022.
• the card master table 2022 shown in FIG. 8 is a table having columns such as name, type, attributes, card information, and image data, with the card ID as a key.
• Card ID is an item that stores an identifier for uniquely identifying the type of card.
• Name is an item that stores the name of the card.
• Type is an item that stores the type of card.
• Attributes is an item that stores the nature to which the character belongs.
• Card Information is an item that stores information that explains the contents of the card.
• Image Data is an item that stores an image.
• Records in the card master table 2022 are added, for example, when a new card is issued.
• FIG. 9 is a diagram showing the data structure of the deck information table 2023.
• the deck information table 2023 shown in FIG. 9 is a table having columns such as name, user ID, registration date, first organization card, second organization card, and publication, with the deck code as the key. In addition to these, the deck information table 2023 may also have information regarding the nickname of the deck.
• the deck code is an item that stores an identifier for uniquely identifying a registered deck.
• the deck code is issued by the management module 2033 when a user registers a new deck.
• the deck code shown in FIG. 9 is an identifier that is different from the deck ID shown in FIG. 6, for example. This is because the deck code shown in FIG. 9 is for managing publicly available decks, while the deck ID shown in FIG. 6 is for managing one's own deck.
• the name is an item that stores the name of the deck. The name is given by the user.
• the user ID is an item that stores the user ID of the user who registered the deck.
• the registration date is an item that stores the date the deck was registered.
• the first organization card and the second organization card are items that store the cards that will be used to organize the deck.
• the card IDs of the cards that will be used to organize the deck are stored.
• the card management IDs of the cards that will be used to organize the deck are stored.
• "Public" is an item that stores whether or not the deck is publicly available to other users.
• a circle indicates that the deck is publicly available to other users, and a cross indicates that the deck is not publicly available to other users.
• a deck that is not public means that it can only be viewed by the player himself.
• FIG. 10 is a diagram showing the data structure of the match information table 2024.
• the match information table 2024 shown in FIG. 10 is a table that uses a match ID as a key and has columns such as date and time, opponent, deck code, winner, match log information, and tournament information.
• the match ID is an item that stores an identifier for uniquely identifying a match.
• a match ID is issued by the management module 2033 when new information about a match is registered.
• the date and time is an item that stores the date and time when the match took place.
• the opponents is an item that stores information about the players who played the match. In this embodiment, for example, the user IDs of the players who played the match are stored in the opponents.
• the deck code is an item that stores a code that identifies the deck used in a match.
• the player who played the match is associated with the deck code of the deck used by that player.
• the deck code does not necessarily have to be stored. In other words, the deck code does not necessarily have to be registered.
• Match log information is an item that stores the moves adopted by players during a match. Specifically, for example, the match log information stores when a player draws a card from a designated placement area (such as the deck or win/lose condition cards), when a player places a card in a designated placement area, when a player uses the effect of a designated card, etc.
• the moves adopted by players during a match may be referred to as deck rotation during a match.
• Tournament information is an item that stores information about a match. For example, tournament information includes the name of the tournament in which the match was held, and the number of rounds in the match in the tournament.
• the tournament information may include match information in privately held tournaments, regardless of whether the tournament was officially held.
• tournament information is not limited to tournaments, and may include match information in private matches.
• FIG. 11 is a diagram showing the data structure of the card management table 2026.
• the card management table 2026 shown in FIG. 11 is a table that uses the card management ID as a key and has columns such as card ID, match information, support information, owner, transferee, transferor, transaction date, and value.
• the owner is an item that stores information about the user who owns the card.
• the owner stores the user ID of the user who owns the card.
• Transferee, Transferor, Transaction Date, and Consideration are items that store information about the transaction of the card identified by the card management ID. Transferee, Transferor, Transaction Date, and Consideration are added for each transaction. Transferee represents the person who received the card in the transaction. Transferor represents the person who transferred the card in the transaction. Transaction Date represents the date the transaction was carried out. Consideration represents the cost paid by the transferee to the transferor when trading the card.
• FIG. 12 is a diagram showing the data structure of the bonus information table 3021 stored in the second server 30. Note that FIG. 12 is an example, and does not exclude data that is not listed.
• the bonus information table 3021 shown in FIG. 12 is a table that uses the bonus ID as a key and has columns for bonus content, conditions, etc.
• the benefit ID is an item that stores an identifier for uniquely identifying a benefit.
• the benefit content is an item that stores the content of the benefit.
• the condition is an item that stores the condition for granting the benefit.
• the benefit content may be, for example, a coupon, a specific product, points, etc.
• the condition may be possession of a digital card related to water, and the benefit content may be a discount on the fee.
• the first server 20 sells, for example, digital cards.
• the first server 20 sells, for example, cards in a manner in which the user can grasp the contents of the cards.
• the first server 20 may also sell cards in a manner in which the user cannot grasp the contents of the cards.
• the first server 20 sells cards in units of one card.
• the first server 20 may also sell cards in units of multiple cards.
• the first server 20 may also function as a platform for users to sell cards to other users.
• the first server 20 makes cards available to other users for purchase, for which sales conditions such as price have been set by the user. If a user agrees to the sales conditions set by the other user, he or she can select the card and purchase it.
• FIG. 13 is a diagram illustrating an example of the operation of the terminal device 10 and the first server 20 when a user purchases a card.
• the user uses the terminal device 10 to access the first server 20.
• the terminal device 10 obtains information about cards being sold by the first server 20 and displays it on the display 141.
• the user refers to the cards displayed on the display 141 and selects the desired card.
• the user inputs a request to purchase the selected card into the terminal device 10.
• step S11 the terminal device 10 accepts a card purchase request input by the user through the operation acceptance unit 191.
• the terminal device 10 transmits the accepted purchase request to the first server 20 through the transmission/reception unit 192.
• the first server 20 acquires a card based on a purchase request from the user. Specifically, for example, the first server 20 acquires a card selected by the user by consuming a predetermined asset associated with the user through the management module 2033.
• the predetermined asset is, for example, the following: ⁇ Game media used in the game ⁇ Crypto assets ⁇ Tokens ⁇ Information about currencies
• the management module 2033 acquires the card ID of the card selected by the user. If the user selects a card that is being sold in a manner that allows the contents of the card to be ascertained, the management module 2033 executes a card lottery and acquires the card ID of the card selected by the lottery. If the user selects a card sold by another user, the management module 2033 acquires the card management ID of the card selected by the user from the card management table 2026.
• the management module 2033 updates the card management table 2026 based on the acquired card ID. Specifically, for example, when the management module 2033 acquires a card ID of a card that is sold in a manner that allows the card contents to be ascertained, or when the management module 2033 acquires a card ID of a card selected by lottery, the management module 2033 issues a card management ID for the corresponding card. The management module 2033 issues a record in the card management table 2026 using the card management ID as a key, and stores information on the card ID and owner in the record.
• the management module 2033 when the management module 2033 acquires the card management ID of a card being sold by another user, the management module 2033 changes the owner of the card in the card management table 2026. Furthermore, the management module 2033 stores information about the transaction in a record that uses the acquired card management ID as a key. Specifically, for example, the management module 2033 stores the transferee, transferor, transaction date, and consideration in a record that uses the acquired card management ID as a key.
• the first server 20 transmits information about the card purchased by the user to the terminal device 10.
• the management module 2033 reads information about the card purchased by the user from the card master table 2022 based on the card ID.
• the management module 2033 reads, for example, the name, type, attributes, card information, and image data as information about the card from the card master table 2022.
• the transmission control module 2032 transmits the card ID, the read information, and the card management ID to the terminal device 10.
• step S15 the terminal device 10 receives the information transmitted from the first server 20 and updates the card information 182 based on the received information. Specifically, for example, the terminal device 10 creates a new record in the card information 182 using the management unit 193, and stores the card management ID, card ID, name, type, attributes, card information, and image data.
• the control unit 203 of the first server 20 manages, by the management module 2033, information on which cards have been used in a match for each card.
• the user builds a deck by combining cards managed in card information 182.
• the management unit 193 manages information related to the decks built by the user in deck information 183.
• the user also registers the deck that he or she has constructed in the first server 20. Specifically, the user accesses the first server 20 using the terminal device 10.
• the terminal device 10 displays a deck registration form set in the first server 20 on the display 141.
• the user uses the form displayed on the display 141 to select cards to construct the deck.
• the user inputs a request to the terminal device 10 to register the deck constructed from the selected cards and the name of the deck.
• the user may set whether or not to make the registered deck public to other users.
• the management module 2033 When a deck registration request is input by the user, the management module 2033 issues a new deck code and creates a record in the deck information table 2023 with the issued deck code as a key.
• the management module 2033 stores, for example, the name of the created record, the user ID, the registration date, the first organization card, the second organization card, and the publication based on the information input by the user.
• FIG. 14 is a diagram illustrating an example of the operation of the terminal device 10 and the first server 20 when managing cards used by users in a match.
• the user uses the terminal device 10 to access the first server 20.
• the terminal device 10 displays on the display 141 a registration form for match information that has been set in the first server 20.
• the user uses the form displayed on the display 141 to input information about the match.
• Information about the match includes, for example, the date and time when the match will be held, the opponents, information about the decks to be used in the match, tournament information, etc.
• the user After inputting the information about the match, the user inputs a request to register the match information into the terminal device 10.
• step S21 the terminal device 10 accepts a registration request for battle information input by the user via the operation reception unit 191.
• the terminal device 10 transmits the input battle information and the registration request to the first server 20 via the transmission/reception unit 192.
• the first server 20 updates the card management table 2026 based on the match information input by the user. Specifically, for example, when the management module 2033 receives a request to register match information from the user, it issues a match ID and creates a record in the match information table 2024 with the issued match ID as a key. The management module 2033 stores the date and time, opponent, deck code, and tournament information of the created record based on the information input by the user.
• the date, time, opponents, and tournament information may be entered in advance by the tournament organizer.
• a battle ID has already been issued, and a record has been created in the battle information table 2024.
• Information regarding the decks to be used in the battle may also be registered in advance by the user. For example, multiple decks to be used in the tournament may be registered before the battle, and the user may select one of the registered decks at the start of the battle.
• the management module 2033 When the management module 2033 stores information in the match information table 2024, it updates the card management table 2026. Based on the card management IDs of the cards included in the deck, the management module 2033 stores information about the match in which the deck is used, such as the match ID, in the "match information" item of the corresponding record in the card management table 2026. The more matches there are, the more information is stored in the match information. This makes it possible to know in which match a card was used.
• the first server 20 transmits the information managed in the card management table 2026 to the terminal device 10. Specifically, for example, when a new battle ID is stored in the "Battle Information" item of the card management table 2026, the management module 2033 reads out the newly stored battle ID, the card management ID, and the user ID of the owner. The transmission control module 2032 transmits the read battle ID and card management ID to the terminal device 10 owned by the user identified by the user ID.
• step S24 the terminal device 10 receives the information transmitted from the first server 20 and updates the card information 182 based on the received information. Specifically, for example, the terminal device 10 stores the battle information received from the first server 20, for example, the battle ID, in the "battle information" item of the record identified by the card management ID, via the management unit 193.
• the control unit 203 controls the match processing between players using the match processing module 2035.
• the match processing module 2035 stores information about the moves used by the players during the match in the memory unit 202.
• the management module 2033 stores information about the moves used by the players during the match in the match information table 2024 as match log information.
• the match processing module 2035 recognizes the player who won the match as the winner.
• the management module 2033 stores the winner in the match information table 2024.
• the control unit 203 of the first server 20 manages, by the management module 2033, information on supporting the deck related to the card for each card.
• FIG. 15 is a diagram illustrating an example of the operation of the terminal device 10 and the first server 20 when managing cards based on user support.
• the terminal device 10 displays the support form set in the first server 20 on the display 141.
• the user uses the form displayed on the display 141 to select a card that will be the basis of the support, and inputs other players who use the deck they will support in association with the selected card. After inputting the support information, the user inputs a request to register the support information to the terminal device 10.
• the support information includes, for example, the card management ID of the selected card and the user ID of the player they will support.
• the user ID of the player they will support may be the participant ID when participating in the tournament.
• the support information may include, for example, information identifying the tournament and information identifying the match in the tournament.
• the card that is the basis for cheering is, for example, a card that has the same effect as the cards that make up the deck being cheered for. If a user has an attachment to a particular card, they may feel a desire to cheer for a player who is using a deck that includes cards that have the same effect as this card. Based on the cards they own, users will cheer for a player who is using a deck that includes those cards. Note that the cards that are the subject of cheering may be of different rarities. If a deck does not include any cards with the same effect as the cards they own, it may be possible to prevent the user from cheering for the player who is using that deck.
• only one player can be supported based on one card.
• the number of players that can be supported may be limited to one regardless of the number of cards.
• a player may be supported throughout the tournament, or the supported player may be changed for each match.
• the target of support can be a deck instead of a player.
• the control unit 190 may set, via the management unit 193, that the card that is the basis of the support cannot be used in the deck by the user while the deck is being supported. This allows the user to take more care in selecting the deck to support, since the selected deck cannot be used while the deck is being supported.
• step S31 the terminal device 10 receives a request to register cheering information input by the user through the operation reception unit 191.
• the terminal device 10 transmits the input cheering information and the registration request to the first server 20 through the transmission/reception unit 192.
• the first server 20 updates the card management table 2026 based on the cheering information input by the user. Specifically, for example, when a cheering information registration request is input by the user, the management module 2033 reads out information about the match from the match information table 2024. Based on the card management ID included in the cheering information input by the user, the management module 2033 stores information based on the information about the match in the "cheering information" item of the corresponding record in the card management table 2026.
• the specified information stored in the "cheering information" item includes, for example, the match ID and the user ID of the cheering player. As the number of cheers increases, the amount of cheering information stored increases. This makes it possible to understand that cheering has been done based on the card.
• step S33 the first server 20 transmits the information managed in the card management table 2026 to the terminal device 10. Specifically, for example, when a new battle ID and user ID are stored in the "support information" item of the card management table 2026, the management module 2033 reads out the newly stored battle ID and user ID, the card management ID, and the user ID as the owner. The transmission control module 2032 transmits the read battle ID and user ID, and the card management ID to the terminal device 10 owned by the user identified by the user ID.
• step S34 the terminal device 10 receives the information transmitted from the first server 20 and updates the card information 182 based on the received information. Specifically, for example, the terminal device 10 causes the management unit 193 to store the cheering information received from the first server 20, such as the battle ID and user ID, in the "cheering information" item of the record identified by the card management ID.
• the control unit 203 controls the match processing between players using the match processing module 2035.
• the match processing module 2035 stores information about the hands used by the players during the match in the storage unit 202.
• the management module 2033 stores information about the hands used by the players during the match in the match information table 2024 as match log information.
• the match processing module 2035 recognizes the player who won the match as the winner.
• the management module 2033 stores the winner in the match information table 2024.
• the management module 2033 may store information about the win or loss in the "support information" item of the card management table 2026.
• the management module 2033 may store the results of the tournament in the match information table 2024. For example, if a player wins the final of a tournament, the winner may be stored in the match information table 2024, and the fact that the player won the tournament may be stored in the match information table 2024 as the result of the tournament.
• the second server 30 provides a service independent of the service related to the TCG.
• the second server 30 provides a service separate from the service related to the TCG.
• the second server 30 is, for example, an aquarium, a museum, a retail store, or a restaurant.
• the services provided by the second server 30 are independent of the services provided by the first server 20, but have a predetermined relationship with the services provided by the first server 20.
• the predetermined relationship means, for example, providing a part of the services provided by the second server 30 to the user in accordance with the digital assets owned by the user for the services provided by the first server 20.
• the second server 30 provides services such as an aquarium, museum, retail store, or restaurant, the second server 30 distributes coupons (discount coupons or product exchange vouchers) that can be used at the store in accordance with the digital assets related to the first server 20.
• a predetermined period may be set for the service of the second server 30 to have a predetermined relationship with the service of the first server 20.
• the predetermined period for having the predetermined relationship may be set in advance, or may vary according to predetermined requirements.
• the predetermined period may be set as a campaign period, for example. In other words, during the campaign period, the second server 30 provides the user with a portion of the service provided by the second server 30, for example, in accordance with the digital assets owned by the user for the service provided by the first server 20.
• the specified requirement that changes the specified period means, for example, the number of products provided in a specified relationship, or the number of users related to the specified relationship. Specifically, for example, if the benefit is a campaign product with a limited number of products, the period ends when the products run out. In other words, the second server 30 provides the user with campaign products according to the digital assets owned by the user for the service provided by the first server 20, for example, until the campaign products run out. Also, if the benefit is a campaign experience with a limited number of people, the period ends when the number of people is reached. In other words, the second server 30 provides the user with a campaign experience according to the digital assets owned by the user for the service provided by the first server 20, for example, until the number of applicants reaches a specified number.
• the following explanation uses as an example a case in which the second server 30 grants a privilege to a user according to the digital card the user possesses.
• FIG. 16 is a diagram illustrating an example of the operation of the terminal device 10, the first server 20, and the second server 30 when the second server 30 grants a user a benefit based on a digital card.
• step S41 the second server 30 sets the bonus information.
• the control unit 303 of the second server 30 sets the bonus content and its conditions using the granting module 3033.
• the granting module 3033 may set any conditions regarding the ownership of the digital assets.
• the grant module 3033 may use the total number of digital cards as a condition.
• the grant module 3033 may also use the number of digital cards with a specified card ID as a condition.
• the grant module 3033 may also use a combination of specified card IDs as a condition.
• the grant module 3033 may also include information linked to the digital cards as a condition.
• the grant module 3033 may use information related to a match as a condition.
• the grant module 3033 may use information related to cheering as a condition.
• the grant module 3033 may use information related to a transaction as a condition.
• the grant module 3033 may use ownership of a specified deck as a condition.
• the granting module 3033 sets the condition that product AAAA will be granted on the possession of digital cards with card IDs: C0001, C0002, and C0003.
• step S42 the second server 30 makes the set bonus information public using a predetermined method. Any existing method may be used as the method of disclosure.
• step S43 the terminal device 10 acquires the bonus information related to the second server 30.
• the control unit 190 of the terminal device 10 causes the display control unit 194 to display a list of the bonus information on the display 141.
• FIG. 17 is a schematic diagram showing an example of the display on the display 141 of the terminal device 10.
• the display control unit 194 displays an area 1411.
• Area 1411 is an area for displaying information related to benefits.
• a search window 14111 is displayed in area 1411. When a user finds a desired benefit or a digital asset that appears to meet the conditions, the user inputs keywords, etc., into the search window 14111.
• the display control unit 194 displays the bonus information in a list in area 1411, for example.
• the display order can be set arbitrarily, such as by product name, identification number, product value, or difficulty of collecting digital assets.
• the difficulty of collecting digital assets can be calculated, for example, based on the rarity of the digital card.
• the display control unit 194 displays information about one bonus in object 14112.
• the display control unit 194 displays the product name and the digital assets required as a condition.
• the display control unit 194 may display in the area 1411 only information related to the perks that satisfy the conditions for the digital assets. Specifically, for example, the management unit 193 compares the conditions for the perks with the digital assets owned by the user. The management unit 193 extracts information about the perks that satisfy the conditions. The display control unit 194 displays the information about the extracted perks on the display 141. As a result, the perks displayed on the display 141 are available to the user, and the user does not need to check which of the displayed perks they can acquire.
• the user selects the desired benefit and touches the object that displays the selected benefit.
• the display control unit 194 of the terminal device 10 displays a screen for confirming that the user wishes to obtain the selected benefit.
• FIG. 18 is a schematic diagram showing an example of the display on the display 141.
• the display control unit 194 displays a window 14113 for confirming that the selected bonus is to be acquired.
• Buttons 141131 and 141132 for inputting the user's intention are displayed in the window 14113. If there is no mistake in acquiring the bonus, the user presses the Yes button 141131. In this embodiment, pressing the button 141131 signifies a request to generate information about the digital asset to be displayed on the object, and input of a request to grant the bonus.
• step S44 the terminal device 10 accepts the generation request and the grant request input by the user through the operation acceptance unit 191.
• the terminal device 10 transmits the generation request to the first server 20 through the transmission/reception unit 192.
• the generation request includes, for example, the user's identification information (e.g., user ID, a specific address set for the user) and information related to the conditions (e.g., card ID).
• step S45 the first server 20 checks the digital assets owned by the user based on the user's request. Specifically, for example, the control unit 203 of the first server 20 acquires the user's identification information and information related to the conditions from the received generation request via the management module 2033.
• the management module 2033 refers to the card management table 2026 based on the acquired information, and checks whether the user owns the digital card presented as a condition.
• step S46 the first server 20 generates information about the digital assets. Specifically, if the user has a digital card that is presented as a condition, for example, the control unit 203 of the first server 20 generates, via the generation module 2034, certification information that certifies that the user owns the digital card, as information about the digital assets.
• the certification information is, for example, information indicating that the required number of cards with the target card ID are possessed.
• the certification information is also, for example, information indicating that the required number of digital cards with required additional information are possessed.
• the certification information is also, for example, information indicating that the target deck is possessed.
• the generation module 2034 may include the generation date and time in the certification information.
• Information about digital assets is not the digital items contained in the digital assets themselves. In other words, information about digital assets does not maintain the data structure of the digital items related to that information. Therefore, even if information about digital assets is transferred to another service, the transferee cannot use the corresponding digital items. Furthermore, even if information about digital assets is transferred to another service, the owner of the corresponding digital items does not change. In other words, there is no change to the data structure of the digital items managed by the first server 20.
• the generation module 2034 determines that the owner of the information about the generated digital asset is the user who input the generation request.
• the control unit 203 of the first server 20 transmits the information about the generated digital asset to the terminal device 10 via the transmission control module 2032.
• step S47 the terminal device 10 transfers the information about the digital asset generated by the first server 20 to the second server 30.
• the control unit 190 of the terminal device 10 receives the information about the digital asset via the transmission/reception unit 192.
• the transmission/reception unit 192 transmits the information about the digital asset and a grant request to the second server 30.
• the transmission/reception unit 192 transmits an instruction to the first server 20 to change the owner of the information about the digital asset to the second server 30 (which can also be said as the service provider).
• the first server 20 changes the owner of the information about the digital asset to the second server 30.
• the grant request includes, for example, user identification information (for example, a user ID, a specific address set for the user) and information identifying the benefit selected by the user.
• the second server 30 grants a bonus to the terminal device 10.
• the control unit 303 of the second server 30 receives information about the digital asset and a bonus request via the granting module 3033.
• the granting module 3033 obtains the user's identification information and the identification information of the selected bonus from the bonus request.
• the granting module 3033 reads the conditions for the bonus selected by the user from the bonus information table 3021.
• the granting module 3033 compares the information about the digital asset with the conditions for the bonus. If the information about the digital asset matches the conditions for the bonus, the granting module 3033 grants the bonus to the user.
• the display control unit 194 displays a screen to notify the user that a bonus has been granted.
• FIG. 19 is a schematic diagram showing an example of the display on the display 141.
• the display control unit 194 displays a window 14114 for notifying the user that a special benefit has been granted.
• a button 141141 for inputting the user's intention is displayed.
• the user confirms that a special benefit has been granted he or she presses the Yes button 141141.
• the control unit 203 of the first server 20 manages the digital items included in the digital assets using the management module 2033.
• the control unit 203 In response to a request from a user, the control unit 203 generates, using the generation module 2034, information that represents the digital items owned by the user and that is to be transferred to the service in order to receive a benefit. This allows the user to receive a benefit based on the digital items they own.
• this embodiment can increase the interest in collecting digital assets.
• the generation module 2034 receives from the user the specification of the digital items for which ownership status is to be confirmed, and generates information indicating that the specified digital items are owned. This reduces the number of digital items for which ownership is to be confirmed when generating information, making it possible to reduce the processing load of the generation module 2034.
• the generation module 2034 generates information indicating the possession of a digital item with predetermined associated information. This makes it possible to set bonus information based on not only the number of digital items, but also on what was done with the digital items. This makes it possible to increase the interest in using digital items.
• the generation module 2034 even if the generation module 2034 generates information about digital assets, it does not affect the digital items being managed. As a result, even if information is generated, the digital items are not reduced, so that benefits can be received without hesitation.
• the data structure of the digital items related to the information about digital assets is not maintained. As a result, even if the information is transferred, the transferee cannot use it as a digital item. This makes it possible to prevent the increase in digital items.
• the digital items can be used in games provided by a specified entity.
• the service that grants benefits depending on the ownership status of digital items is a service separate from the game. This makes it easy to associate the acquisition of a digital item related to a game with a service separate from the game, and can provide motivation to play the game. Furthermore, it becomes possible for the service provider to reduce the burden of linking the service with the game.
• the user information table 2021, the card master table 2022, the deck information table 2023, the battle information table 2024, and the card management table 2026 are stored in the first server 20.
• the information stored in these tables does not have to be stored in the first server 20.
• at least the card information stored in the card management table 2026 may be stored in a block chain (distributed ledger) formed by a P2P computer network.
• each digital card is traded on the blockchain as a non-fungible token (NFT).
• NFT non-fungible token
• the card management ID in the above embodiment corresponds to, for example, a unique identifier (NFT-ID) for identifying the NFT.
• information on the digital assets is traded on the blockchain as an NFT.
• the generation module 2034 may be realized by a smart contract implemented on the blockchain. Upon receiving a generation request, the smart contract generates proof information as an NFT based on information on the conditions included in the generation request.
• Transactions for NFTs are executed, for example, by smart contracts implemented on the blockchain.
• the transaction history for NFTs is stored on the blockchain as transactions. This allows the history of NFT owners to be stored on the blockchain.
• NFT usage is carried out, for example, by a smart contract implemented on the blockchain.
• the history of NFT usage is stored on the blockchain as transactions. This allows the history of NFTs used in matches and the history of supporting other players based on NFTs to be stored on the blockchain.
• the granting of rewards related to the usage history of NFTs is executed, for example, by a smart contract implemented on the blockchain.
• the owner of the NFT at that time is granted a specified reward.
• the owner of the NFT at that time is granted a specified reward.
• the granting module 3033 may be realized, for example, by a smart contract implemented on the blockchain.
• the smart contract receives the granting request and information about the digital asset, it compares the information about the digital asset with the conditions for the reward. If the information about the digital asset matches the conditions for the reward, the smart contract grants the reward to the user.
• control unit 203 of the first server 20 uses the management module 2033 to store information about multiple digital cards in a distributed ledger formed by a computer network.
• the control unit 190 of the terminal device 10 may also use the management unit 193 to store information about multiple digital cards in a distributed ledger formed by a computer network. This makes it possible to treat digital cards as NFTs. It also makes it possible to keep transparent records about the digital cards.
• the management module 2033 also stores information regarding card usage in the distributed ledger as a transaction of the corresponding digital card.
• the management unit 193 may also store information regarding card usage in the distributed ledger as a transaction of the corresponding digital card. This makes it possible to keep a transparent record of the usage history of the digital card.
• the management module 2033 or the management unit 193 stores information about the match in the distributed ledger as a transaction of the corresponding digital card. This makes it possible to keep a transparent record of information about the match between digital cards.
• the management module 2033 or the management unit 193 stores information about cheering in the distributed ledger as a transaction of the corresponding digital card. This makes it possible to keep a transparent record of information about cheering based on the digital card.
• management module 2033 or the management unit 193 stores information about the transaction in the distributed ledger as a transaction of the transacted digital card. This makes it possible to keep a transparent record of the digital card transaction.
• the first server 20 stores the match information table 2024.
• the user's own match information may be stored in the storage unit 180 of the terminal device 10.
• the management unit 193 may update the match information in the card information 182 based on the match information stored in the storage unit 180.
• the transmission/reception unit 192 transmits information related to the card to the first server 20.
• the management module 2033 of the first server 20 updates the card master table 2022 based on the information transmitted from the terminal device 10. This makes it possible for the terminal device 10 to grasp the match information.
• card uses were described as battles using decks of cards and cheering based on cards.
• card uses are not limited to these.
• card uses may also include displaying cards.
• the digital items included in the digital assets are described as digital cards.
• the digital items are not limited to digital cards.
• the digital items may be digital characters, etc.
• the second server 30 grants a bonus based on the digital assets owned by the user.
• the granting of bonuses from the second server 30 is not limited to being based on the owned digital assets.
• the management means of the system stores the events caused by the user.
• the generation means of the system generates information related to the occurrence of an event at the request of the user.
• the management module 2033 of the first server 20 that provides the game manages the events (game progress) generated by the player.
• the generation module 2034 generates information about the occurrence of events (game progress, digital item acquisition status) upon request from the user.
• the second server 30 sets the occurrence status of the event as a condition for the benefit.
• the granting module 3033 may, for example, use the extent to which the event has occurred as a condition.
• the granting module 3033 may also use the number of occurrences of a specified event as a condition.
• the granting module 3033 may also use a combination of specified events as a condition.
• the granting module 3033 may also include information linked to a specified event as a condition.
• the granting module 3033 may use the state of the player when the event occurred as a condition.
• the granting module 3033 may also use the state and number of other players when the event occurred as a condition.
• the second server 30 grants a benefit to a user based on information related to the occurrence of the event provided by the user.
• information about events generated by users may be stored on the blockchain as NFTs.
• users can receive rewards from a system independent of the system in question based on the log of events that have occurred, users are more motivated to cause events to occur.
• users can receive rewards from a service provider other than the game based on their progress in a specific game, players are more motivated to progress in the game.
• the second server 30 also grants rewards based on information related to events caused by the user. Therefore, when granting rewards, the second server 30 does not need to start the target game one by one and check the progress status within the game.
• the second server 30 only needs to check the existence of information proving progress (including, for example, NFT), which reduces operational effort. Also, complex conditions can be set without much effort.
• the management module 2033 is capable of allocating record slots in the card management table 2026 to a user in response to a request from the user.
• the management module 2033 allocates to the user the number of record slots requested by the user.
• the management module 2033 may request a specified amount of assets from the user in accordance with the number of record slots allocated.
• the user stores the desired digital card in the allocated record slot.
• the user instructs the first server 20 to store the data of a specific digital card in one of the allocated record slots.
• the management module 2033 stores information about a digital card specified by a user in a record frame. When a digital card stored in a record frame is used, the management module 2033 stores information about use in a specified item in the record frame. On the other hand, when a digital card not stored in a record frame is used, no information about use is stored, or less information is stored compared to the digital card stored in the record frame. The management module 2033 may allow other users to view only the digital cards stored in the record frame. Note that a specified number of record frames are assigned to each user, but the record frames assigned to a user may increase as the user pays a fee or progresses through the game.
• the first server 20 may generate information about the digital asset owned by the user by referring to the card management table 2026. In other words, the first server 20 may generate information about the digital asset without receiving any conditions for the digital asset from the user.
• the generated information about the digital asset is transmitted to the second server 30.
• the second server 30 compares the received information about the digital asset with the conditions stored in the benefit information table 3021, and determines the benefit that can be granted to the user.
• the digital card may also be acquired by reading an analog card.
• Basic hardware configuration of computer> 20 is a block diagram showing the basic hardware configuration of a computer 90.
• the computer 90 includes at least a processor 91, a main storage device 92, an auxiliary storage device 93, and a communication IF (interface) 99. These are electrically connected to each other by a bus.
• the processor 91 is hardware for executing a set of instructions written in a program.
• the processor 91 is composed of an arithmetic unit, registers, peripheral circuits, etc.
• the main memory device 92 is used to temporarily store programs and data processed by the programs.
• it is a volatile memory such as a DRAM (Dynamic Random Access Memory).
• the auxiliary storage device 93 is a storage device for saving data and programs.
• it is a flash memory, HDD (Hard Disc Drive), optical magnetic disk, CD-ROM, DVD-ROM, semiconductor memory, etc.
• the communication IF 99 is an interface for inputting and outputting signals for communicating with other computers over a network using wired or wireless communication standards.
• Networks are composed of the Internet, LANs, various mobile communication systems constructed using wireless base stations, etc.
• networks include 3G, 4G, and 5G mobile communication systems, LTE (Long Term Evolution), wireless networks that can connect to the Internet via designated access points (e.g., Wi-Fi (registered trademark)), etc.
• communication protocols include, for example, Z-Wave (registered trademark), ZigBee (registered trademark), Bluetooth (registered trademark), etc.
• networks also include those that are directly connected using USB (Universal Serial Bus) cables, etc.
• computers 90 can be virtually realized by distributing all or part of each hardware configuration across multiple computers 90 and connecting them together via a network.
• the concept of computer 90 includes not only a computer 90 housed in a single housing or case, but also a virtualized computer system.
• the computer includes at least the functional units of a control unit, a storage unit, and a communication unit.
• the functional units of the computer 90 can also be realized by distributing all or part of each functional unit across multiple computers 90 that are connected to each other via a network.
• the concept of computer 90 includes not only a single computer 90 but also a virtualized computer system.
• the control unit is realized by the processor 91 reading out various programs stored in the auxiliary storage device 93, expanding them in the main storage device 92, and executing processing in accordance with the programs.
• the control unit can realize functional units that perform various information processing depending on the type of program.
• the computer is realized as an information processing device that performs information processing.
• the storage unit is realized by a main storage device 92 and an auxiliary storage device 93.
• the storage unit stores data, various programs, and various databases.
• the processor 91 can secure a storage area corresponding to the storage unit in the main storage device 92 or the auxiliary storage device 93 in accordance with a program.
• the control unit can cause the processor 91 to execute processes for adding, updating, and deleting data stored in the storage unit in accordance with the various programs.
• database refers to a relational database, which is used to manage sets of data called tables, which are structured in a tabular format defined by rows and columns, by relating them to each other.
• a table is called a table
• a column in a table is called a column
• a row in a table is called a record.
• each table has a column set as a key for uniquely identifying a record, but setting a key to a column is not essential.
• the control unit can cause the processor 91 to add, delete, or update records in a specific table stored in the memory unit according to various programs.
• the communication unit is realized by the communication IF 99.
• the communication unit realizes the function of communicating with other computers 90 via a network.
• the communication unit can receive information sent from other computers 90 and input it to the control unit.
• the control unit can cause the processor 91 to execute information processing on the received information in accordance with various programs.
• the communication unit can transmit information output from the control unit to other computers 90.
• Appendix 1 A program to be executed by a computer having a processor and a memory, the program causing the processor to execute the steps of managing digital items included in digital assets, and generating, in response to a request from a user, information representing the digital items owned by the user to be transferred to the service in order to receive the grant of a bonus, where a service exists that grants bonuses based on the ownership status of the digital items.
• Appendix 2 A program as described in claim 1, in which in the generating step, a specification of a digital item for which ownership status is to be confirmed is accepted from a user, and information indicating ownership of the specified digital item is generated.
• (Appendix 3) The program according to (Supplementary Note 1) or (Supplementary Note 2), wherein in the generating step, information indicating possession of a digital item to which predetermined related information is attached is generated.
• (Appendix 4) A program as described in any one of (Supplementary Note 1) to (Supplementary Note 3), wherein even if the information is generated in the generating step, it does not affect the digital item being managed.
• (Appendix 5) A program described in any one of (Appendix 1) to (Appendix 4), wherein the data structure of the digital item related to the information is not maintained.
• (Appendix 6) A program described in any one of (Appendix 1) to (Appendix 5), wherein in the managing step, the digital items are usable in a game provided by a specified entity, and in the generating step, the service is a service separate from the game.
• (Appendix 7) A program described in any of (Appendix 1) to (Appendix 6), in which in the management step, events generated by the user are managed, and in the generation step, a service exists that grants benefits depending on the occurrence circumstances of the event, and in response to a request from the user, information representing the event generated by the user is generated to be transferred to the service to receive the grant of a benefit.
• (Appendix 8) A program according to claim 7, wherein in the generating step, information indicating that an event to which the specified information is linked has occurred is generated.
• (Appendix 9) A program described in any one of (Appendix 1) to (Appendix 8), in which in the managing step, the digital items are managed in a distributed ledger formed by a computer network.
• (Appendix 10) A program described in any one of (Appendix 1) to (Appendix 9), in which, in the generating step, the generated information is managed in a distributed ledger formed by a computer network.
• (Appendix 11) A program as described in Appendix 7, in which, in the management step, events generated by the user are managed in a distributed ledger formed by a computer network.
• Appendix 12 A program to be executed by a computer having a processor and a memory, the program causing the processor to execute the steps of: receiving information representing a digital item owned by a specified user, the digital item being issued by a specified game service, usable in the game service, and included in a digital asset; and granting the user a benefit related to a service separate from the game service based on the information representing the digital item owned by the specified user that has been received.
• Appendix 13 A method executed by a computer having a processor and a memory, the method comprising the steps of: managing digital items included in digital assets; and, in a service that grants rewards based on the ownership status of digital items, generating, in response to a request from a user, information representing the digital items owned by the user to be transferred to the service in order to receive the rewards.
• Appendix 14 An information processing device having a control unit and a memory unit, wherein the control unit executes a step of managing digital items included in digital assets, and a step of generating, in response to a request from a user, information representing the digital items owned by the user to be transferred to the service in order to receive the grant of a bonus, where a service exists that grants bonuses depending on the ownership status of the digital items.
• a system comprising: means for managing digital items included in digital assets; means for setting conditions for granting a bonus according to the ownership status of the digital items; means for generating information representing the digital items owned by a user in response to a request from the user; means for changing the owner of the information from the user to a bonus provider; and means for granting a bonus when the user's ownership status of the digital items satisfies the conditions based on the information with the changed owner.

Landscapes

• Engineering & Computer Science (AREA)
• Multimedia (AREA)
• Business, Economics & Management (AREA)
• Tourism & Hospitality (AREA)
• General Business, Economics & Management (AREA)
• General Health & Medical Sciences (AREA)
• Health & Medical Sciences (AREA)
• Economics (AREA)
• Computer Security & Cryptography (AREA)
• Human Resources & Organizations (AREA)
• Marketing (AREA)
• Primary Health Care (AREA)
• Strategic Management (AREA)
• Physics & Mathematics (AREA)
• General Physics & Mathematics (AREA)
• Theoretical Computer Science (AREA)
• Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Applications Claiming Priority (2)

Publications (1)

Family

ID=90830824

Family Applications (1)

Country Status (2)

Families Citing this family (1)

Citations (3)

Family Cites Families (1)

• 2022
  • 2022-10-27 JP JP2022172297A patent/JP7689940B2/ja active Active
• 2023
  • 2023-10-19 WO PCT/JP2023/037799 patent/WO2024090317A1/ja not_active Ceased
• 2025
  • 2025-05-28 JP JP2025089132A patent/JP2025122172A/ja active Pending

Patent Citations (3)

Also Published As

Similar Documents

Legal Events