Program, method, information processing device, and system

Abstract

To efficiently manage a digital card even if one digital card is adopted simultaneously in multiple decks.SOLUTION: A program is executed by a computer having a processor and a memory. The program allows a processor to execute the steps of: storing information regarding multiple digital cards; storing information regarding multiple decks constructed by combining at least some of multiple digital cards while relating the information to the multiple digital cards; and displaying a list of information regarding multiple digital cards to a user, displaying a digital card adopted by a single deck such that its adoption in the deck can be grasped in the list, and displaying a digital card adopted in multiple decks so as to be capable of grasping a deck that stores the digital card currently and a deck that adopts but does not store digital card.SELECTED DRAWING: Figure 16

Description

[Technical field]

[0001] The present disclosure relates to a program, a method, an information processing device, and a system. [Background technology]

[0002] 2. Description of the Related Art Analog trading card games (TCGs) that are played using analog cards are popular, but in recent years digital trading card games (TCGs) that are played using digital cards have also become popular.

[0003] Patent Document 1 proposes a card usage system that can suppress the proliferation of digital cards corresponding to trading cards in the digital world while enabling them to be used digitally. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent Publication No. 2021-37199 Summary of the Invention [Problem to be solved by the invention]

[0005] Patent Document 1 describes the management of digital cards based on analog cards, but does not describe the simultaneous use and management of one digital card in multiple decks.

[0006] An object of the present disclosure is to efficiently manage digital cards even when a single digital card is used in multiple decks at the same time. [Means for solving the problem]

[0007] A program to be executed by a computer having a processor and a memory. The program causes the processor to execute the steps of: storing information about a plurality of digital cards; storing information about a plurality of decks constructed by combining at least any of the plurality of digital cards in association with the plurality of digital cards; and displaying a list of information about the plurality of digital cards to a user, displaying in the list digital cards used in a single deck so that the user can understand that the digital cards are used in the deck, and displaying digital cards used in the plurality of decks so that the decks currently contain the cards and the decks that have been used but are not contained in the cards can be understood. Effect of the Invention

[0008] According to the present disclosure, digital cards can be efficiently managed even when a single digital card is used in multiple decks at the same time. [Brief description of the drawings]

[0009] [Figure 1] FIG. 2 is a diagram showing a situation in which a TCG match is being prepared according to the present embodiment. [Diagram 2] FIG. 2 is a diagram showing a situation in which a TCG match according to the present embodiment is about to begin. [Diagram 3] FIG. 2 shows a situation in which each user is progressing in a TCG match. [Figure 4] 1 is a block diagram showing an example of the overall configuration of a system 1. FIG. [Diagram 5] 5 is a block diagram illustrating an example of the configuration of a terminal device 10 shown in FIG. 4. [Figure 6] FIG. 2 is a diagram illustrating an example of a functional configuration of a server 20. [Figure 7] FIG. 13 is a diagram showing the data structure of card information 182. [Figure 8] FIG. 13 is a diagram showing the data structure of deck information 183. [Figure 9] FIG. 2 is a diagram showing the data structure of a user information table 2021. [Figure 10]FIG. 23 is a diagram showing the data structure of a card information table 2022. [Figure 11] FIG. 23 is a diagram showing the data structure of a deck information table 2023. [Figure 12] 13 is a diagram showing the data structure of a Q&A information table 2024. FIG. [Figure 13] 2 is a schematic diagram showing an example of a card list displayed on the terminal device 10. FIG. [Figure 14] 13 is a schematic diagram showing another example of a card list displayed on the terminal device 10. FIG. [Figure 15] 2 is a schematic diagram showing an example of a deck list displayed on the terminal device 10. FIG. [Figure 16] 1 is a schematic diagram showing an example of an editing screen for deck 2 displayed on the terminal device 10. FIG. [Figure 17] 1 is a schematic diagram showing an example of an editing screen for deck 3 displayed on the terminal device 10. FIG. [Figure 18] 13 is a flowchart showing an example of the operation of the control unit 190 when a card is removed from a deck during editing of the deck. [Figure 19] 13 is a flowchart showing an example of the operation of the control unit 190 when a card is added to a deck during editing of the deck. [Figure 20] 13 is a schematic diagram showing an example of a desired card notification screen displayed on the terminal device 10. FIG. [Figure 21] 13 is a schematic diagram showing another example of the editing screen for the deck 2 displayed on the terminal device 10. FIG. [Figure 22] FIG. 13 is a schematic diagram illustrating an example of a display screen for Q&A information. [Figure 23] FIG. 2 is a block diagram showing the basic hardware configuration of a computer 90. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] Hereinafter, an embodiment of the present disclosure will be described with reference to the drawings. In the following description, the same components are denoted by the same reference numerals. Their names and functions are also the same. Therefore, detailed description thereof will not be repeated.

[0011] <Summary> The program according to this embodiment is a program for managing cards owned by users who play a TCG (Trading Card Game). Users build decks by combining cards to be used in TCG matches. Users use the decks they have built to play against decks built by other users. Decks have various characteristics depending on the cards they combine. Since each deck has good and bad compatibility, some users own multiple decks.

[0012] Although there are multiple unique cards, there are also common general-purpose cards that are necessary for deck construction. Since it is difficult to prepare general-purpose cards for each deck, cards are sometimes shared between decks. In such cases, it may become difficult to know which deck currently contains a card that is shared between multiple decks. Also, if a card shared with another deck is removed, it may become difficult to know what card was in the deck.

[0013] The program according to this embodiment stores cards used in multiple decks in association with the currently incorporated deck and decks that have been used but are not currently housed. This makes it easy to know which cards are in which decks when constructing multiple decks.

[0014] First, an overview of the TCG according to this embodiment will be described, followed by a description of a support system that allows users to manage cards they own.

[0015] <0 Overview of TCG> Fig. 1 is a diagram showing a situation in which a TCG match according to the present embodiment is being prepared. Fig. 2 is a diagram showing a situation in which a TCG match according to the present embodiment is about to start. Fig. 3 is a diagram showing a situation in which each user is progressing in a TCG match.

[0016] A user places a play mat 30 and plays a TCG match using a deck constructed by combining cards to be used in the TCG match.

[0017] <0.1 Composition of 30 playmats> With reference to Fig. 1, various items used by each user in a TCG match will be described. As shown in Fig. 1, when a user 5A (first user) and a user 5B (second user) start a TCG match, a play mat 30 is placed between the user 5A and the user 5B. The play mat 30 is for placing cards included in a deck. Each user places cards on the play mat 30 as a deck or the like, and proceeds with the TCG match while adding cards from the deck to their hand.

[0018] The configuration of the play mat 30 will be described. The play mat 30 includes, for example, a mat on which the positions for placing cards are indicated. The play mat 30 includes, for example, a deck placement section 31A and a deck placement section 31B (hereinafter, sometimes collectively referred to as the "deck placement section 31"); a preparation card placement section 32A and a preparation card placement section 32B (hereinafter, sometimes collectively referred to as the "preparation card placement section 32"); a win / lose condition card placement section 33A and a win / lose condition card placement section 33B (hereinafter, sometimes collectively referred to as the "win / lose condition card placement section 33"); a battle card placement section 34A and a battle card placement section 34B (hereinafter, sometimes collectively referred to as the "battle card placement section 34"); and a consumption card placement section 35A and a consumption card placement section 35B (hereinafter, sometimes collectively referred to as the "consumption card placement section 35"). The play mat 30 may be arranged for each user. In this case, for example, the play mat 30 includes an area related to one user. Specifically, for example, the play mat 30 includes a deck card placement area 31A, a preparation card placement area 32A, a win / lose condition card placement area 33A, a battle card placement area 34A, and a consumption card placement area 35A.

[0019] As shown in Fig. 3, in a TCG match, each user replenishes their hand with cards from the deck while progressing through a card battle. In the example of Fig. 3, user 5A has hand 93A (two cards in the hand in the example of Fig. 3). User 5B has hand 93B (three cards in the hand in the example of Fig. 3).

[0020] The deck placement section 31 is an area for placing any of the cards constituting the deck owned by each user as a deck. The deck placement section 31A is an area for the user 5A to place cards as a deck. The deck placement section 31B is an area for the user 5B to place cards as a deck.

[0021] 2, when each user starts a TCG match, each user shuffles the cards that make up the deck and places the cards face down in the deck placement section 31. User 5A places cards in the deck placement section 31A as a deck 91A. User 5B places cards in the deck placement section 31B as a deck 91B.

[0022] The preparation card placement section 32 is an area for preparing cards that can be used to fight against the opponent's cards. Each user switches the cards placed in the preparation card placement section 32 with the cards placed in the battle card placement section 34, and makes the cards placed in the battle card placement section 34 fight each other.

[0023] As shown in Fig. 2, before the start of a TCG match, no cards are placed in the preparation card placement unit 32 and the battle card placement unit 34. On the other hand, as shown in Fig. 3, as the TCG match progresses, each user places cards in the preparation card placement unit 32 and the battle card placement unit 34, and the cards are made to fight each other in the battle card placement unit 34. Each user places cards to be used in the battle from their hand in the preparation card placement unit 32 and the battle card placement unit 34 while replenishing their hand from the deck. User 5A places cards in the preparation card placement unit 32A. User 5B places cards in the preparation card placement unit 32B.

[0024] The win / loss condition card placement section 33 is an area showing to what extent each player has satisfied the win condition. In this embodiment, each player places a predetermined number of cards from the deck face down in the win / loss condition card placement section 33. As shown in FIG. 2, user 5A places cards in the win / loss condition card placement section 33A. User 5B places cards in the win / loss condition card placement section 33B.

[0025] The battle card placement section 34 is an area for placing cards that will fight against the opponent's cards. The user 5A places cards in the battle card placement section 34A. The user 5B places cards in the battle card placement section 34B. In this embodiment, the cards placed in the battle card placement section 34A and the cards placed in the battle card placement section 34B basically fight based on the vitality, attack power, character attributes shown on the cards, weak point attributes, and other parameters set for each card. The cards placed in the battle card placement section 34 are given damage according to the attack power, card attributes, weak points, etc., and the given damage is reduced from the vitality. When the vitality set for a card is lost due to being attacked, etc., the card is removed from the battle card placement section 34 and placed in the consumption card placement section 35.

[0026] The consumed card placement section 35 is an area for placing cards consumed in a TCG match. For example, cards that have lost vitality in a battle, cards that have activated their effects, etc. are placed in the consumed card placement section 35. As shown in FIG. 3, user 5A places cards consumed in a match as cards 92A in the consumed card placement section 35A. User 5B places cards consumed in a match as cards 92B in the consumed card placement section 35B.

[0027] <0.2 Types of cards used in TCG> In the TCG of this embodiment, the types of cards include: (i) character cards that can be used in battle, (ii) action cards (energy cards) that are used in association with character cards, and (iii) effect cards (support cards, goods cards, stadium cards, etc.) that exert specific effects during battle.

[0028] (i) Character cards include cards that can be placed in the preparation card placement area 32 or the battle card placement area 34 when a user draws a card from the deck and adds it to their hand (also referred to as “unconditional cards”), and cards that can be placed in the preparation card placement area 32 or the battle card placement area 34 by satisfying certain conditions (also referred to as “conditional cards”).

[0029] (iA) For example, a conditional card can be placed on the condition that an unconditional card related to the conditional card is placed. For example, in analogy with character evolution, an unconditional card is first presented to an opponent user by placing it on the play mat 30, and then a conditional card related to the unconditional card is placed on the play mat 30. Such a conditional card is sometimes called an "evolved character" as it is evolved from an unconditional card. In addition, the unconditional card is sometimes called a "seed character" because it can be said to be a character that is the source of the "evolved character" to be placed.

[0030] (iB) For example, a conditional card can be placed in the preparation card placement section 32 or the battle card placement section 34 by consuming a specific card and moving it to the consumption card placement section 35. Specifically, it may be possible to consume an unconditional card placed on the play mat 30 as a specific card (by moving it to the consumption card placement section 35) and place the conditional card in the preparation card placement section 32 or the battle card placement section 34.

[0031] For example, a conditional card can be placed in the preparation card placement section 32 or the battle card placement section 34 in exchange for one or more character cards placed by the user on the play mat 30. For example, if each character card is provided with a parameter (e.g., an evolution level) indicating the overall performance of the character in addition to individual parameters such as the attack power of the character shown on the card, a conditional card having an evolution level corresponding to the evolution level value of the character card placed by the user may be placed. For example, with a character of evolution level 1 and a character of evolution level 2 placed on the play mat 30, a conditional card of evolution level 3 can be placed on top of the cards of these characters (or in exchange for these character cards).

[0032] In addition, the conditional card may be allowed to participate in the battle in exchange for a plurality of character cards defined by the conditional card. In this case, the conditional card may be allowed to participate in the battle by consuming an auxiliary card, which will be described later, different from the character card. For example, the effect indicated by the auxiliary card may be set such that a specific conditional card can be allowed to participate in the battle in exchange for a specific unconditional card in the battle card arrangement section 34, the consumption card arrangement section 35, or the like of the play mat 30.

[0033] (iC) These cards include cards that serve as multiple of the above-mentioned character cards, action power cards, and support cards described below. For example, special cards that can be used as both character cards and support cards may be included. When the user places the special card in a position where a character card should be placed (e.g., the preparation card placement area 32, the battle card placement area 34), the user can use the special card as a character card.

[0034] (ii) An action power card (energy card) is a card that a user draws from a deck and adds to his / her hand, and then associates it with a character card and places it on the play mat 30, thereby enabling the user to perform a predetermined action indicated on the character card. The operation of associating an action power card with a character card may be performed, for example, during the user's turn. For example, the action power card may be associated with a character card by placing the action power card near the character card placed on the play mat 30. In addition, the number of times that an action power card can be associated with a character card during a turn may be limited. For example, once during the user's turn, an action power card in the hand may be associated with any of the character cards placed on the play mat 30. For example, a first attack action and a second attack action are set to the character card. The first attack action may be available when one action power card is associated with the character card, and the second attack action may be available when one action power card is not enough and two action power cards are associated with the character card.

[0035] When a character card is removed from the battle card placement section 34 due to the exhaustion of its vitality value in a battle, the action power card associated with the character card may be made unusable during the battle. Also, the action power card associated with the character card may be moved to the consumption card placement section 35.

[0036] (iii) Support cards that assist in a match include card types that a user can use any number of times during a turn as long as they are in the user's hand, and card types that a user can use only one card during a turn. These support cards also include cards that have their effect activated when the user declares that they will use the effect of the support card.

[0037] In addition, the auxiliary card may be placed face down in advance in a predetermined position on the play mat 30 (in this embodiment, the predetermined position is not shown), and the effect of the auxiliary card may be exerted when the user declares the use of the auxiliary card by vocalization or the like.

[0038] <0.3 Overview of TCG battle rules> The play mat 30 and the types of cards used in the TCG match have been explained above. Next, the TCG match rules will be explained in detail.

[0039] In the TCG shown in this embodiment, as described above, each user performs an attack or defense (battle) based on the cards placed in the battle card placement section 34A and the battle card placement section 34B to progress the TCG battle. The TCG battle progresses as the users take turns to act. For example, when a first user acts and ends his turn, it becomes the second user's turn. The second user acts during his turn, and when he ends his action, it becomes the first user's turn.

[0040] Each time a turn comes, each user draws a predetermined number of cards from the deck and adds them to their hand.

[0041] Each user places, from among the cards in his / her hand, candidates for cards (character cards) to be used in attack or defense against the opponent user's cards in the preparation card placement section 32.

[0042] The user 5A can switch between the cards arranged in the preparation card placement unit 32A and the cards arranged in the battle card placement unit 34A during the turn of the user 5A. Also, the user 5B can switch between the cards arranged in the preparation card placement unit 32A and the cards arranged in the battle card placement unit 34A during the turn of the user 5B.

[0043] As described above, the win / loss condition card placement section 33A and the win / loss condition card placement section 33B are areas for notifying each user of the degree of progress toward the conditions for winning the match. Here, the condition for a user to win the match may be, for example, that all cards placed in the win / loss condition card placement section 33A or the win / loss condition card placement section 33B are collected. In other words, the outcome of the match may be decided when all cards are collected in either the win / loss condition card placement section 33A or the win / loss condition card placement section 33B.

[0044] For example, each user places a predetermined number of cards from the deck in the win / lose condition card placement section 33 before a TCG match. That is, the user 5A removes a predetermined number of cards from the deck 91A and places them in the win / lose condition card placement section 33A. The user 5B removes a predetermined number of cards from the deck 91B and places them in the win / lose condition card placement section 33B. The user 5A and the user 5B make the character card placed in the battle card placement section 34A and the character card placed in the battle card placement section 34B battle each other, and when the exit condition set for the character card is satisfied (for example, when the vitality value set for the character card is subtracted based on the attack power set for the opponent's character card and runs out), the character of the character card is considered to have fainted, and the character card is moved to the consumption card placement section 35 (also called "trash").

[0045] As a result, the user who has won the battle and dismissed the opponent's character card adds the cards placed in the win / loss condition card placement section 33A or the win / loss condition card placement section 33B to his / her hand. For example, when the user 5B dismisses the cards placed in the battle card placement section 34A by attacking the character card of the user 5A in his / her turn, he / she takes a predetermined number of cards from the cards placed in the win / loss condition card placement section 33B and adds them to his / her hand. On the other hand, when the user 5A dismisses the cards placed in the battle card placement section 34B by attacking the character card of the user 5B in his / her turn, he / she takes a predetermined number of cards from the cards placed in the win / loss condition card placement section 33A and adds them to his / her hand. By repeating these operations, when the user 5B collects all the cards placed in the win / loss condition card placement section 33B, or when the user 5A collects all the cards placed in the win / loss condition card placement section 33A, the user who has collected all the cards may be determined to be the user who won the TCG battle.

[0046] Alternatively, the winning condition of the match may be that a user loses if there is no character card in either the battle card placement unit 34 or the preparation card placement unit 32. Alternatively, the winning condition of the match may be that a user loses if he or she is unable to draw a deck from the deck placement unit 31 during his or her turn.

[0047] 1 to 3 illustrate an example in which users face each other to play a TCG match. However, the TCG match is not limited to one in which users face each other. Users may connect to each other via the Internet and play a match by acquiring the opponent's voice and the opponent's card arrangement, etc., via the Internet. Specifically, for example, a user plays a match while taking a picture of his / her own area on the play mat 30 with a camera or the like. The taken image is transmitted to the opponent in real time. The user receives an image of the opponent's area sent from the opponent, and displays the received image on a display. This allows the user to check the opponent's cards in real time through the screen while handling his / her own cards in reality. In this way, the user may play a TCG match using analog cards online.

[0048] If there are multiple cameras or if there is a device that allows the viewing angle of the camera to be adjusted, the user's face may be photographed and the photographed image may be sent to the opponent. This allows the opponent's facial expression to be confirmed during the match, making it possible to obtain the same level of satisfaction in an online TCG match as in a face-to-face match.

[0049] <1 Overall system configuration> Fig. 4 is a block diagram showing an example of the overall configuration of the system 1. The system 1 shown in Fig. 4 includes, for example, a terminal device 10 and a server 20. The terminal device 10 and the server 20 are communicatively connected via a network 80, for example.

[0050] 4 shows an example in which the system 1 includes three terminal devices 10, but the number of terminal devices 10 included in the system 1 is not limited to three. The number of terminal devices 10 included in the system 1 may be two or less, or may be four or more.

[0051] 4 shows an example in which the system 1 includes one server 20, but the number of servers 20 included in the system 1 is not limited to one. The server 20 may be composed of multiple servers depending on the functions it has. Also, the server 20 may be, for example, a collection of multiple devices that constitutes one server. The method of allocating multiple functions required to realize the server 20 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 server 20.

[0052] 4 is, for example, an information processing device operated by a user who owns a TCG card. The terminal device 10 is realized by, for example, 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 a wearable terminal such as an HMD (Head Mount Display).

[0053] The terminal device 10 includes a communication IF (Interface) 12, an input device 13, an output device 14, a memory 15, a storage 16, and a processor 19. The input device 13 is a device (e.g., a touch panel, a touch pad, etc.) for receiving an input operation from a user. The output device 14 is a device (a display, a speaker, etc.) for presenting information to a user.

[0054] The server 20 is, for example, an information processing device that manages information related to cards and information related to decks.

[0055] The server 20 is realized by, for example, a computer connected to a network 80. As shown in Fig. 4, the 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 interface with an input device for receiving an input operation from a user and an output device for presenting information to the user.

[0056] Each information processing device is configured by a computer equipped with a calculation device 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. For each of the terminal device 10 and the server 20, descriptions that overlap with the basic hardware configuration and basic functional configuration of the computer described later will be omitted.

[0057] <1.1 Terminal device configuration> Fig. 5 is a block diagram showing a configuration example of the terminal device 10 shown in Fig. 4. As shown in Fig. 5, 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.

[0058] The communication unit 120 performs processing such as modulation and demodulation processing for the terminal device 10 to communicate with other devices. The communication unit 120 performs transmission processing on a signal generated by the control unit 190 and transmits the signal to the outside (for example, the server 20). The communication unit 120 performs reception processing on a signal received from the outside and outputs the signal to the control unit 190.

[0059] The input device 13 is a device for inputting instructions or information by a user who operates the terminal device 10. The input device 13 is realized, for example, by a touch-sensitive device 131 or the like in which an instruction is input by touching an operation surface. In the case where the terminal device 10 is a PC or the like, the input device 13 may be realized by a reader, a keyboard, a mouse, or the like. The input device 13 converts an instruction input by a user into an electrical signal, and outputs the electrical signal to the control unit 190. Note that the input device 13 may include, for example, a receiving port that receives an electrical signal input from an external input device.

[0060] The output device 14 is a device for presenting information to a user who operates 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.

[0061] The audio processing unit 17 performs, for example, digital-analog conversion processing of an audio signal. The audio processing unit 17 converts a signal provided from 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 from the audio processing unit 17 into audio and outputs the audio to the outside of the terminal device 10.

[0062] The camera 160 is a device for receiving light with a light receiving element and outputting the received light as an image capturing signal.

[0063] The position information sensor 150 is a sensor that detects the position 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 the satellite positioning system, signals are received from at least three or four satellites, and the current position of the terminal device 10 equipped with the GPS module is detected based on the received signals. The position information sensor 150 may detect the current position of the terminal device 10 from the position of the wireless base station to which the terminal device 10 is connected.

[0064] The storage unit 180 is realized by, for example, the memory 15, the storage 16, etc., 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.

[0065] The user information 181 includes, for example, information about a user who plays the TCG. The information about the user includes, for example, a user ID, the user's name, age, address, date of birth, and date of registration. The card information 182 includes, for example, information about cards. The card information 182 may include information about cards owned by the user. Details will be described later. The deck information 183 includes, for example, information about a deck constructed by a user, which will be described in detail later.

[0066] The control unit 190 is realized by the processor 19 reading a program stored in the storage unit 180 and executing instructions included in the program. The control unit 190 controls the operation of the terminal device 10. The control unit 190 operates according to the program to fulfill the functions of an operation reception unit 191, a transmission / reception unit 192, a management unit 193, a display control unit 194, an auxiliary unit 195, and a notification unit 196.

[0067] 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 or the like.

[0068] Furthermore, operation acceptance unit 191 accepts an image input from camera 160. Specifically, operation acceptance unit 191 receives image data captured by camera 160, for example.

[0069] Furthermore, the operation reception unit 191 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.

[0070] The transmitting / receiving unit 192 performs processing for the terminal device 10 to transmit and receive data to and from an external device such as the server 20 in accordance with a communication protocol. Specifically, for example, the transmitting / receiving unit 192 transmits instructions input by the user or various pieces of acquired information to the server 20. The transmitting / receiving unit 192 also receives information provided from the server 20. The information provided from the server 20 includes, for example, information about a new card acquired by the user or information about a deck published on a predetermined site.

[0071] Management unit 193 manages user information 181, card information 182, and deck information 183 stored in storage unit 180. For example, when information about a user is edited, management unit 193 stores the edited information in user information 181. Furthermore, when information about a card is updated, management unit 193 updates card information 182. Furthermore, when information about a deck is updated, management unit 193 updates deck information 183.

[0072] The support unit 195 supports the construction of a deck. For example, the support unit 195 extracts cards suitable for constructing a deck from cards owned by the user. For example, the support unit 195 extracts cards that constitute a deck that can be constructed from owned cards based on information input by the user. The information input by the user is, for example, the following: Main Attributes Main character name Reference deck composition

[0073] The support unit 195 extracts the remaining cards up to a prescribed number from the owned cards, for a deck that the user has partially constructed, based on the cards included in the deck being constructed. The support unit 195 extracts cards based on, for example, the balance of the number of cards for each type, the match of attribute-related information, cards that are estimated to be necessary based on a typical pattern of deck construction, etc. Also, the support unit 195 removes cards that exceed a prescribed number from a deck that the user has partially constructed, based on the cards included in the deck being constructed. The support unit 195 removes cards from the deck, for example, based on the balance of the number of cards for each type, the match of attribute-related information, cards that are estimated to be unnecessary based on a typical pattern of deck construction, etc.

[0074] The support unit 195 manages cards (desired cards) required to strengthen the deck. Desired cards include, for example, the following cards. A card that you own one of but need multiple copies of A card that has some but not others in a group of character cards that are linked in use (for example, pre-evolved and post-evolved character cards). Some cards that are recommended to be used in the same deck that you do not own

[0075] The support unit 195 may set a card designated by the user as the desired card, or may set an unowned card based on a constructed deck as the desired card. For example, the support unit 195 may compare a deck published on the Internet with a constructed deck, and set a card that is missing from the published deck as the desired card.

[0076] The display control unit 194 controls the output device 14 to display a predetermined image for the user. For example, the display control unit 194 controls the display 141 to display a management screen for cards owned by the user based on information managed in the card information 182 and information managed in the deck information 183. Specifically, the display control unit 194 controls the display 141 to display cards owned by the user in a manner that allows the user to ascertain which deck the cards belong to.

[0077] The display control unit 194 controls the output device 14 to display information to the user to assist in constructing a deck.

[0078] The notification unit 196 notifies the user of information related to the deck in a manner that allows the user to easily confirm the information.

[0079] <1.2 Functional configuration of the server> 6 is a diagram showing an example of a functional configuration of the server 20. As shown in FIG. 6, the server 20 exerts the functions of a communication unit 201, a storage unit 202, and a control unit 203.

[0080] The communication unit 201 performs processing for the server 20 to communicate with external devices.

[0081] The storage unit 202 includes, for example, a user information table 2021, a card information table 2022, a deck information table 2023, and a Q&A information table 2024.

[0082] The user information table 2021 is a table that stores information about users who have registered for services related to the TCG, for example. Details will be described later.

[0083] The card information table 2022 is, for example, a table that stores information about cards, and will be described in detail later.

[0084] The deck information table 2023 is a table that stores, for example, information about decks registered by users. Details will be described later.

[0085] The Q&A information table 2024 is a table that stores, for example, questions about how to use cards and the answers to those questions, as will be described in detail later.

[0086] The control unit 203 is realized by the processor 29 reading a program stored in the storage unit 202 and executing instructions included in the program. The control unit 203 functions as a reception control module 2031, a transmission control module 2032, a management module 2033, and an execution module 2034 by operating according to the program.

[0087] The reception control module 2031 controls the process in which the server 20 receives a signal from an external device in accordance with a communication protocol.

[0088] The transmission control module 2032 controls the process in which the server 20 transmits signals to external devices in accordance with a communication protocol.

[0089] The management module 2033 manages the tables stored in the storage unit 202 .

[0090] The execution module 2034 executes processing related to a predetermined service based on information provided by the user.

[0091] <2 Data Structure> 7 and 8 are diagrams showing the data structure of information stored in the terminal device 10. Note that Figs. 7 and 8 are merely examples and do not exclude data not shown.

[0092] Fig. 7 is a diagram showing the data structure of card information 182. Card information 182 shown in Fig. 7 is a table having columns such as name, type, attribute, card information, image data, number of cards, etc., with a card ID as a key. In addition to these, card information 182 may also have information on regulations or rarity, etc.

[0093] The card ID is an item that stores an identifier for uniquely identifying a card. 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, the types of cards include, for example, character, energy, support, goods, etc.

[0094] The attribute is an item that stores the nature to which the character belongs. In this embodiment, the attributes include, for example, fire, water, lightning, grass, super, steel, evil, fighting, etc. There are attributes that are advantageous when facing against, and attributes that are disadvantageous. The card information is an item that stores information that explains the contents of the card. When the type of the card is a 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 characteristics that the character has, etc. When the type of the card is support or goods, the card information includes, for example, the requirements for using the card, effects that occur when the card is used, etc. The image data is an item that stores an image. The image data may store reference information (path) for an image data file located in another location.

[0095] The number of cards is an item that stores the number of cards that the user possesses and that are assigned the same card ID. In this embodiment, cards with the same name but different effects are assigned different card IDs. Furthermore, cards with the same name but different rarities are assigned different card IDs. Furthermore, cards with the same name but different regulations are assigned different card IDs.

[0096] A record for a card is read from the server 20, for example, when a user acquires a corresponding card. Specifically, for example, when a user acquires a card, the terminal device 10 acquires the card ID of the card using a predetermined method. The card ID may be acquired, for example, by reading a number or code printed on the surface of the card, or by performing image analysis on a photographed card. The terminal device 10 requests information about the acquired card from the server 20 based on the card ID. The server 20 transmits the requested information about the card to the terminal device 10.

[0097] Image analysis of cards is not limited to one by one, but may be performed on multiple cards at once. Specifically, for example, a user places multiple cards he owns so that each card can be seen, and takes a picture of the placed cards so that the angle of view includes the multiple cards. In this case, the multiple cards may be 60 cards included in a deck. The terminal device 10 analyzes the image of the multiple cards and acquires the card ID of each card.

[0098] The terminal device 10 may obtain the card ID by a method other than reading. For example, the terminal device 10 may obtain the card ID by accepting an input of a number, a card name, or the like from the user.

[0099] Information regarding cards not owned by the user may also be stored in the terminal device 10 from the beginning. When the user acquires a card and acquires the card ID of the acquired card, the terminal device 10 sets a flag indicating that the card has been acquired. When the number of cards reaches "1", it may be determined that the card has been acquired.

[0100] Fig. 8 is a diagram showing the data structure of deck information 183. Deck information 183 shown in Fig. 8 is a table having columns such as name, number, organization cards, shared cards, loan cards, desired cards, completion, and update date, with a deck ID as a key. In addition to these, deck information 183 may also have information on the nickname of the deck, the deck usage history, and the like. The nickname of the deck is a name given based on, for example, a characteristic card used in the deck, succinctly expresses the characteristics of the deck, and is given based on a common understanding among multiple users.

[0101] The deck ID is an item that stores an identifier for uniquely identifying a deck. The name is an item that stores the name of the deck. The name is given by the user. The number is an item that stores the number of cards that make up the deck. The number may store the number of cards of each type. The organization card is an item that stores the cards that organize the deck. In the organization card, for example, the card ID is stored.

[0102] A shared card is an item that stores a card shared with another deck. In a shared card, for example, the deck ID of the deck that shares the card and the card ID of the card shared with this deck are stored in association with each other. In the example shown in FIG. 8, for example, in the record of deck ID: D0002, "C0050-D0001, -D0003" is written as a shared card. This indicates that the card "C0050" organized in the deck with deck ID: D0002 is also used in the deck with deck ID: D0001 and the deck with deck ID: D0003, but is currently organized in the deck with deck ID: D0002.

[0103] A loaned card is an item that stores cards that are loaned to other decks. For example, the card ID of the loaned card and the deck ID of the deck to which this card is loaned are stored in association with each other in the loaned card. In the example shown in FIG. 8, for example, "C0050-D0002" is listed as a loaned card in the record of deck ID: D0001. This indicates that card "C0050" is loaned from deck ID: D0001 to deck ID: D0002.

[0104] Desired Cards is an item that stores cards that are necessary to strengthen the deck. Completed is an item that stores whether or not the deck is complete. In this embodiment, a circle indicates that the deck is complete, and a cross indicates that the deck is not complete. In this embodiment, a deck being complete means, for example, that the deck has been assembled with a specified number of cards and is ready to be used in a battle. 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.

[0105] A record about a deck is added when a new deck is created in the terminal device 10 in response to an instruction from the user. Although not shown in Fig. 8, the deck information 183 may store past information about the construction of a deck and the movement of cards as a log.

[0106] 9 to 12 are diagrams showing data structures of information stored in the server 20. Note that, Figs. 9 to 12 are merely examples, and do not exclude data that is not shown.

[0107] Fig. 9 is a diagram showing the data structure of a user information table 2021. The user information table 2021 shown in Fig. 9 is a table having columns such as name, age, address, date of birth, and date of registration, with a user ID as a key. The user information table 2021 is not limited to the above, and may also have a column for proficiency.

[0108] The user ID is an item that stores an identifier for uniquely identifying a user. The name is an item that stores the name of the user. The age is an item that stores the age of the user. 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 began using services related to the TCG.

[0109] A record in the user information table 2021 is added when a new user is registered.

[0110] Fig. 10 is a diagram showing the data structure of the card information table 2022. The card information table 2022 shown in Fig. 10 is a table having columns such as name, type, attribute, card information, and image data, with the card ID as a key.

[0111] Card ID is an item that stores an identifier for uniquely identifying a 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 a character belongs. Card Information is an item that stores information that describes the contents of the card. Image Data is an item that stores an image.

[0112] Records in the card information table 2022 are added when a new card is issued.

[0113] Fig. 11 is a diagram showing the data structure of the deck information table 2023. The deck information table 2023 shown in Fig. 11 is a table having columns such as name, user ID, registration date, and organization card, with the deck ID as a key. In addition to these, the deck information table 2023 may also have information regarding the nickname of the deck, etc.

[0114] The deck ID is an item that stores an identifier for uniquely identifying a registered deck. The deck ID is issued by the management module 2033 when a new deck is registered by a user. The deck ID shown in FIG. 11 is, for example, a different identifier from the deck ID shown in FIG. 8. This is because the deck ID shown in FIG. 11 is for managing a public deck, and the deck ID shown in FIG. 8 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 organization cards are an item that stores the cards that organize the deck.

[0115] Records in the deck information table 2023 are added when a new deck is registered.

[0116] Fig. 12 is a diagram showing the data structure of the Q&A information table 2024. The Q&A information table 2024 shown in Fig. 12 is a table having columns such as content, related decks, related cards, and registration date, with the Q&A ID as a key.

[0117] The Q&A ID is an item that stores an identifier for uniquely identifying the Q&A. The Q&A ID is issued by the management module 2033 when a new Q&A is registered. The content is an item that stores the content of the Q&A. For example, the content of the Q&A includes a question related to the card and an answer to the question. The related deck is an item that stores information about the deck to which the Q&A is related. In the example shown in FIG. 12, the nickname of the deck is stored. The related card is an item that stores information about the card to which the Q&A is related. In the example shown in FIG. 12, the card ID is stored. The registration date is an item that stores the date on which the Q&A was registered. A record in the Q&A information table 2024 is added when a new deck is registered.

[0118] <3 operations> The operation of the terminal device 10 and the server 20 in the system 1 will be described. As a premise of the following description, it is assumed that the terminal device 10 imports an analog card owned by a user as digital data (digital card). The terminal device 10 may use any existing method for importing an analog card owned by a user as digital data. For example, the terminal device 10 may obtain a card ID by reading a number or code printed on the surface of the card, or may recognize the card by performing image analysis on a photographed card. The number or code printed on the surface of the card may be visible or invisible. In addition, when a card with a card ID written thereon is enclosed in a pack in which a card is enclosed, the terminal device 10 may obtain the card ID by reading the enclosed card. This allows the analog card owned by the user to be managed as digital data.

[0119] (Displays a list of cards) The user inputs an instruction to the terminal device 10 to display a list of cards owned by the user. Specifically, for example, the user executes a TCG management support app installed in the terminal device 10. In the launched app, the user inputs an instruction to the terminal device 10 to display the owned cards. The control unit 190 of the terminal device 10 causes the display control unit 194 to display the list of cards on the display 141 based on the card information 182 and deck information 183.

[0120] Fig. 13 is a schematic diagram showing an example of a card list displayed on the terminal device 10. In Fig. 13, the display control unit 194 displays an area 1411 and an area 1412. The area 1411 is an area in which display conditions and the like are entered. The area 1412 is an area in which cards owned by the user are displayed in a format conforming to the display conditions entered in the area 1411.

[0121] In the example shown in FIG. 13, display order and deck display are displayed as display conditions in area 1411. Display order indicates a rule of sequence. The display order is selected by the user from among, for example, number order, name order, rarity order, acquisition date order, etc. Deck display indicates whether or not information about the deck in which the card is stored is displayed. The deck display is selected by the user from, for example, yes or no.

[0122] In the example shown in Fig. 13, "Display order: numerical order" is selected, and cards are arranged in the order of their card IDs in area 1412. Also, in the example shown in Fig. 13, "Deck display: none" is selected, and no information about the deck in which the card is stored is displayed.

[0123] A search window 14111 is displayed in area 1411. When a user finds a desired card, the user inputs a keyword or the like into search window 14111 to search for the desired card.

[0124] The display order and deck display can be switched based on an instruction from the user. For example, the user can switch the display order from number order to name order, rarity order, acquisition date order, etc.

[0125] Furthermore, the user can switch the deck display from "no" to "yes." When the display control unit 194 is switched to "deck display: yes," the display control unit 194 refers to the deck information 183 and displays a list of cards on the display 141 so that the user can see which decks contain cards and which decks have been adopted but are not contained therein.

[0126] 14 is a schematic diagram showing another example of a card list displayed on the terminal device 10. When the display control unit 194 is switched to "deck display: yes", it adds information to the card displayed on the display 141 that enables identification of the deck that contains the card. Also, when the display control unit 194 is switched to "deck display: yes", it adds information to the card displayed on the display 141 that enables identification of decks that use but do not contain the card.

[0127] In the example shown in FIG. 14, the display control unit 194 assigns a tag 14121 indicating deck 2 to a card accommodated in deck 2. Moreover, the display control unit 194 assigns a tag 14121 indicating deck 1 to a card accommodated in deck 1. Moreover, the display control unit 194 assigns a tag 14122 indicating deck 1 to a card that is used in deck 1 but is not accommodated in deck 1. The tag representing the accommodated deck and the tag representing the adopted but not accommodated deck may be distinguishable. In the example shown in FIG. 14, the tag representing the accommodated deck is represented by a solid line, and the tag representing the adopted but not accommodated deck is represented by a dashed line.

[0128] The user can switch the priority of cards displayed in area 1412. For example, the user can preferentially display cards contained in a deck in area 1412. In other words, the display control unit 194 can preferentially display cards tagged with a solid line.

[0129] Furthermore, the user can preferentially display cards that are included in one deck and are also used in other decks in area 1412. In other words, the display control unit 194 can preferentially display cards with solid line tags and dashed line tags.

[0130] The identifiable information is not limited to a tag, and may be, for example, information that changes the display mode of the card itself.

[0131] (Deck list) The user inputs an instruction to the terminal device 10 to display a list of decks owned by the user. Specifically, for example, the user executes a TCG management support app installed in the terminal device 10. In the launched app, the user inputs an instruction to the terminal device 10 to display the decks owned by the user. The control unit 190 of the terminal device 10 causes the display control unit 194 to display a list of decks on the display 141 based on the deck information 183.

[0132] Fig. 15 is a schematic diagram showing an example of a deck list displayed on the terminal device 10. In Fig. 15, the display control unit 194 displays an area 1411 and an area 1413. The area 1413 is an area that displays decks owned by the user in a format conforming to the display conditions described in the area 1411.

[0133] 15, a display order is displayed as a display condition in an area 1411. The display order indicates a rule for the order. The display order is selected by the user from among, for example, number order, name order, update date order, and the like.

[0134] In the example shown in FIG. 15, the display order is set to "by name," and the decks are arranged in area 1413 in the order of their names.

[0135] In the example shown in Fig. 15, the display control unit 194 displays decks that are completed but have not yet reached the specified number of cards contained therein in a manner that makes them distinguishable from decks that are completed and have the specified number of cards contained therein. In other words, the display control unit 194 displays decks that are completed but have cards contained in other decks in a manner that makes them distinguishable from decks that are completed and have some of their cards shared with other decks. Specifically, for example, the display control unit 194 displays decks 1, 3, and 5 that are completed but have cards contained in other decks in a dashed line, and decks 2 and 4 that are completed and have some of their cards shared with other decks in a solid line.

[0136] In the example shown in Fig. 15, the display control unit 194 displays the movement of cards in a way that makes it possible to grasp the movement. For example, the display control unit 194 displays the deck from which the card is lent and the deck to which the card is lent in such a way that they are associated with each other. Specifically, the display control unit 194 displays an arrow from the deck from which the card is lent to the deck to which the card is lent. This causes an arrow to be drawn from the deck represented by the dashed line to the deck represented by the solid line, and the user can visually see at a glance which deck's cards are lent to which deck and stored therein.

[0137] 15, the display control unit 194 displays the incomplete deck 6 in a manner that allows it to be distinguished from the completed deck. Specifically, for example, the display control unit 194 displays the incomplete deck 6 in a dashed line.

[0138] (Deck editing display 1) A user inputs an instruction to the terminal device 10 to display an editing screen of a deck owned by the user. Specifically, for example, the user selects one of the decks shown in Fig. 15, and inputs an instruction to the terminal device 10 to display an editing screen of the selected deck. The control unit 190 of the terminal device 10 causes the display control unit 194 to display the deck editing screen on the display 141 based on the card information 182 and deck information 183.

[0139] FIG. 16 is a schematic diagram showing an example of an editing screen for deck 2 displayed on the terminal device 10. Deck 2 is a deck that accepts cards to be shared from deck 1 and deck 3. In FIG. 16, the display control unit 194 displays an area 1411, an area 1414, and an area 1415. The area 1414 is an area that displays cards constituting the deck in a manner conforming to the display conditions described in the area 1411. The area 1415 is an area that displays a list of cards owned by the user in a manner conforming to the display conditions described in the area 1411. In the area 1415, cards are displayed that can be replaced with cards displayed in the area 1414. The cards displayed in the area 1414 may be displayed in a manner that allows them to be distinguished from the cards displayed in the area 1415. In the example shown in FIG. 16, the cards displayed in the area 1414 are displayed larger than the cards displayed in the area 1415.

[0140] In the example shown in FIG. 16, display order, deck display, and adoption display are displayed as display conditions in area 1411. Display order indicates a rule of sequence. The display order is selected by the user from, for example, number order, name order, rarity order, acquisition date order, etc. Deck display indicates whether or not to display information related to the deck in which the card is stored. Adoption display indicates whether or not to display information related to decks that use the card. Adoption display is selected by the user from, for example, yes or no. When "Adoption display: yes" is selected, the display control unit 194 displays information related to decks that use the card, and when "Adoption display: no" is selected, it does not display information related to decks that use the card.

[0141] In the example shown in FIG. 16, "display order: numerical order" is set, and cards are arranged in areas 1414 and 1415 in the order of their card IDs. Also, in the example shown in FIG. 16, "deck display: yes" is set, and cards displayed in area 1415 display information about the deck in which the card is contained. Also, in the example shown in FIG. 16, "deck display: yes" is set, and some cards displayed in area 1415 are not contained, but display information about the deck in which they are used. Also, in the example shown in FIG. 16, "adoption display: yes" is set, and some cards displayed in area 1414 display information about the deck in which they are used.

[0142] 16, the display control unit 194 assigns tags 14141 indicating "Deck 1" and "Deck 3" to cards shared with decks 1 and 3 in the area 1414. This allows the user to intuitively understand cards that are contained in the deck but have been brought from other decks.

[0143] 16, the display control unit 194 assigns a tag 14151 indicating "deck 1" to cards contained in deck 1 in the area 1415. The display control unit 194 assigns a tag 14151 indicating "deck 3" to cards contained in deck 3 in the area 1415. The display control unit 194 assigns a tag 14151 indicating "deck 4" to cards contained in deck 4 in the area 1415.

[0144] 16, the display control unit 194 assigns a tag 14152 indicating deck 1 to cards that are used in deck 1 but cannot be contained in deck 1 in the area 1415. The display control unit 194 may display decks that can contain cards differently from decks that are used but cannot contain cards. In FIG. 16, the display control unit 194 displays decks that can contain cards using solid lines and displays decks that are used but cannot contain cards using dashed lines.

[0145] (Deck editing display part 2) A user inputs an instruction to the terminal device 10 to display an editing screen of a deck owned by the user. Specifically, for example, the user selects one of the decks shown in Fig. 15, and inputs an instruction to the terminal device 10 to display an editing screen of the selected deck. The control unit 190 of the terminal device 10 causes the display control unit 194 to display the deck editing screen on the display 141 based on the card information 182 and deck information 183.

[0146] Fig. 17 is a schematic diagram showing an example of an editing screen for deck 3 displayed on the terminal device 10. Deck 3 is a deck that lends out cards used in decks 2 and 4. In Fig. 17, the display control unit 194 displays areas 1411, 1414, and 1415.

[0147] In the example shown in Fig. 17, display order, deck display, and adoption display are displayed as display conditions in area 1411. Display order indicates the rules of sequence. Deck display indicates whether or not to display information about the deck in which the card is stored. Adoption display indicates whether or not to display information about the deck in which the card is used.

[0148] In the example shown in Fig. 17, "display order: numerical order" is set, and cards are arranged in areas 1414 and 1415 in the order of their card IDs. Also, in the example shown in Fig. 17, "deck display: yes" is set, and some cards displayed in area 1415 have information displayed about the deck in which the card is stored. Also, in the example shown in Fig. 17, "adoption display: yes" is set, and some cards displayed in area 1414 have information displayed about the deck in which the card is adopted.

[0149] Specifically, in the example shown in FIG. 17, the display control unit 194 indicates in the area 1414 that the card lent to deck 2 is not stored in deck 3. The display control unit 194 indicates that the card is used in deck 3 but is not stored in deck 3 by, for example, displaying the card transparently or with a dashed line. The display control unit 194 may indicate that the card is used in deck 3 but is not stored in deck 3 by, for example, displaying the back of the card. The display control unit 194 assigns a tag 14142 indicating "deck 2" to the card lent to deck 2. In addition, the display control unit 194 assigns a tag 14142 indicating "deck 4" to the card lent to deck 4. This allows the user to intuitively grasp the cards that are used in the deck but are lent to other decks.

[0150] 17, the display control unit 194 assigns a tag 14151 indicating "deck 2" to cards contained in deck 2 in the area 1415. The display control unit 194 assigns a tag 14151 indicating "deck 4" to cards contained in deck 4 in the area 1415. The display control unit 194 assigns a tag 14151 indicating "deck 5" to cards contained in deck 5 in the area 1415.

[0151] (Deck editing process) The operation of the control unit 190 of the terminal device 10 when the user edits the deck will be described.

[0152] Fig. 18 is a flowchart showing an example of the operation of the control unit 190 when a card is removed from a deck during editing of the deck. For example, assume that the user removes a card organized in the deck from the deck on the screen shown in Fig. 16 or 17. In other words, assume that the user moves the card displayed in area 1414 to area 1415.

[0153] In step S11, the control unit 190 determines whether or not a card has been removed from the deck by the management unit 193. A card being removed from the deck means, for example, that the card has been moved from area 1414 to area 1415. If the card has been removed from the deck (Yes in step S11), the management unit 193 transitions the process to step S12.

[0154] In step S12, the management unit 193 determines whether the card removed from the deck is a card that was contained in the target deck and shared with another deck. A card that was contained in the target deck and shared with another deck refers to a card with a tag 14141 attached in the area 1414 of Fig. 16, for example. If the card removed from the deck is a card that was contained in the target deck and shared with another deck (Yes in step S12), the management unit 193 transitions the process to step S13.

[0155] In step S13, the management unit 193 determines whether the number of decks on the lending side is one. If the number of decks on the lending side is one (Yes in step S13), the management unit 193 transitions the process to step S14.

[0156] In step S14, the management unit 193 removes the card from the target deck and updates the deck information 183 to store the card in the deck from which it was lent. The display control unit 194 attaches a tag 14151 indicating the deck in which the card was stored to the card removed from the deck in the area 1415. The display control unit 194 displays a notification to the user urging them to return the card removed from the deck (the shared card) to the deck from which it was lent.

[0157] In step S13, if the number of decks from the lending source is two or more, the management unit 193 transitions the process to step S15.

[0158] In step S15, the management unit 193 determines which deck to include the card removed from the target deck in. Specifically, the control unit 190 causes the display control unit 194 to display on the display 141 a screen that allows the user to select which deck to include the card removed from the target deck in. The user selects which deck to include the card in according to the displayed screen. The management unit 193 determines to include the card in the deck selected by the user.

[0159] The management unit 193 may determine the deck that contains the card in accordance with a predetermined rule, without accepting a selection from the user. The predetermined rule is, for example, as follows. -Favorite decks Most popular decks Decks with high priority Recently updated decks ·random

[0160] In step S16, the management unit 193 stores the card in the determined deck and updates the deck information 183 so as to lend the card from another deck to the determined deck. The display control unit 194 attaches a tag 14151 indicating the deck in which the card was stored to the card removed from the deck in the area 1415. The display control unit 194 also attaches a tag 14152 indicating the deck from which the card was lent to the card removed from the deck in the area 1415. The display control unit 194 displays a notification to the user urging them to move the card removed from the deck (the shared card) to the determined deck.

[0161] In step S12, if the card removed from the deck is not a card that was contained in the target deck or shared with another deck, management unit 193 transitions the process to step S17.

[0162] In step S17, the management unit 193 judges whether or not the card removed from the deck is a card lent to another deck. A card lent to another deck refers to, for example, a card with a tag 14142 attached in the area 1414 of Fig. 17. If the card removed from the deck is a card lent to another deck, the management unit 193 transitions the process to step S18.

[0163] In step S18, the management unit 193 removes the card from the target deck and updates the deck information 183 to remove the card from being lent to other decks. In the area 1415, the display control unit 194 attaches a tag 14151 indicating the deck in which the card was placed to the card removed from the deck.

[0164] In step S17, if the card removed from the deck is neither a card shared with other decks nor a card lent to another deck, the management unit 193 moves the process to step S19. A card that is neither a card shared with other decks nor a card lent to another deck refers to, for example, a card that does not have a tag attached in area 1414 of FIG.

[0165] In step S19, the management unit 193 updates the deck information 183 to remove the card from the target deck. The display control unit 194 displays in the area 1415 the card that has been removed from the deck.

[0166] Fig. 19 is a flowchart showing an example of the operation of the control unit 190 when a card is added to a deck during deck editing. For example, assume that the user organizes an unorganized card into a deck on the screen shown in Fig. 16 or 17. In other words, assume that the user moves the card displayed in area 1415 to area 1414.

[0167] In step S21, control unit 190 determines whether or not a card has been placed in the deck by management unit 193. A card being placed in the deck means, for example, that the card has been moved from area 1415 to area 1414. If the card has been placed in the deck (Yes in step S21), management unit 193 transitions the process to step S22.

[0168] In step S22, the management unit 193 determines whether the inserted card is a card contained in another deck. If the inserted card is a card contained in another deck, the management unit 193 transitions the process to step S23.

[0169] In step S23, the management unit 193 judges whether or not to remove the inserted card from the other deck. Specifically, the control unit 190 causes the display control unit 194 to display on the display 141 a screen that prompts the user to confirm that the card inserted by the user will be removed from the other deck and stored in the target deck. The user judges whether or not to remove the card from the other deck according to the displayed screen. When the user agrees to remove the card from the other deck, the management unit 193 judges that the inserted card will be removed from the other deck. When it is judged that the inserted card will be removed from the other deck, the management unit 193 shifts the process to step S24.

[0170] In step S24, the management unit 193 stores the inserted card in the target deck and updates the deck information 183 so as to remove the card from the original deck. The display control unit 194 attaches a tag 14141 indicating the deck from which the card was lent to the newly stored card in the area 1414 shown in FIG.

[0171] In step S23, if the user does not consent to removing the card from the other deck, the management unit 193 determines that the inserted card will not be removed from the other deck. If it is determined that the inserted card will not be removed from the other deck, the management unit 193 transitions the process to step S25.

[0172] In step S25, the management unit 193 judges whether or not the inserted card is to be lent to another deck. Specifically, the control unit 190 causes the display control unit 194 to display on the display 141 a screen that prompts the user to confirm that the card inserted by the user is to be lent from the target deck to another deck. The user judges whether or not to lend the card to another deck according to the displayed screen. When the user agrees to lend the card to another deck, the management unit 193 judges that the inserted card is to be lent to another deck. When it is judged that the inserted card is to be lent to another deck, the management unit 193 shifts the process to step S26.

[0173] In step S26, the management unit 193 updates the deck information 183 so that the inserted card is shared with the original deck and the card is lent from the target deck to the original deck. The display control unit 194 adds a tag 14142 indicating the deck that contains the card to the card that has been lent to the original deck in the area 1414 shown in FIG.

[0174] In step S25, if the user does not consent to lending the inserted card to another deck, the management unit 193 determines that the inserted card is not to be lent to another deck. If it is determined that the inserted card is not to be lent to another deck, the management unit 193 shifts the process to step S27.

[0175] In step S27, the management unit 193 decides not to organize the inserted card into a deck. The display control unit 194 returns the card inserted into the area 1414 to the area 1415.

[0176] In step S22, if the inserted card is not a card contained in another deck, management unit 193 transitions the process to step S28.

[0177] In step S28, the management unit 193 updates the deck information 183 so that the cards are organized into the target deck. The display control unit 194 displays in the area 1414 the cards that have been inserted from the deck.

[0178] (Deck building support in the early stages of construction) The user inputs an instruction to provide assistance with deck construction to the terminal device 10. For example, when starting to build a deck, the user inputs an instruction to provide assistance with deck construction to the terminal device 10. The control unit 190 of the terminal device 10 causes the assistance unit 195 to extract cards necessary for organizing a deck from the cards owned.

[0179] Specifically, for example, the support unit 195 creates a deck plan that can be constructed from owned cards based on information input by the user. The support unit 195 may create multiple deck plans. The display control unit 194 controls the display 141 to display the created deck plan to the user.

[0180] The user considers whether or not to adopt the displayed deck plans. The user selects the deck to be adopted and inputs to the terminal device 10 that the selected deck will be constructed.

[0181] When a user inputs that he or she will build a deck, the support unit 195 extracts cards included in the proposed deck from the cards owned. The display control unit 194 displays the extracted cards in the area 1414 of the display 141.

[0182] The support unit 195 may create a deck using cards that the user does not own as a proposed deck. The user acquires, for example, information about decks that is publicly available on the Internet. The support unit 195 extracts cards necessary to build the deck from the cards owned based on the acquired deck-related information. The display control unit 194 displays the extracted cards in the area 1414 of the display 141. The management unit 193 stores the missing cards as desired cards in the deck information 183 in association with the deck.

[0183] (Deck building support in progress) The user inputs an instruction to the terminal device 10 to provide assistance with deck construction. For example, the user inputs an instruction to provide assistance with deck construction to the terminal device 10 while the user is in the middle of editing a deck. The assistance unit 195 extracts cards necessary for organizing the deck from the cards owned. The assistance unit 195 also removes cards not necessary for organizing the deck from the deck.

[0184] Specifically, for example, the user inputs an instruction to the terminal device 10 to provide assistance with deck construction on a screen during deck editing as shown in Fig. 16 or 17. The assistance unit 195 extracts the remaining cards up to a specified number from the owned cards based on the cards included in the deck being constructed for a deck that the user has partially constructed. The assistance unit 195 extracts suitable cards from the owned cards based on, for example, the balance of the number of cards by type, matching of attribute information, cards estimated to be necessary based on typical patterns of deck construction, etc.

[0185] The display control unit 194 displays the extracted cards in the area 1414 of the display 141. The display control unit 194 may display the extracted cards in the area 1414 so that they can be distinguished from the cards organized by the user.

[0186] Furthermore, for a deck that has been partially constructed by the user, the support unit 195 removes cards that exceed a prescribed number based on cards included in the deck being constructed. The support unit 195 removes cards from the deck based on, for example, the balance of the number of cards per type, matching of attribute information, cards that are estimated to be unnecessary based on typical patterns of deck construction, etc.

[0187] The display control unit 194 displays the removed cards in an area 1415 of the display 141. The display control unit 194 may display the cards removed from the deck in the area 1415 so that they can be distinguished from cards that were not originally used.

[0188] (Deck building support, post-construction implementation) The user inputs an instruction to implement deck construction assistance to the terminal device 10. For example, the user inputs an instruction to implement deck construction assistance for a deck after it has been constructed to the terminal device 10. The assistance unit 195 sets cards (desired cards) necessary to strengthen the deck.

[0189] Specifically, the support unit 195 receives, for example, a designation of an unowned card from the user. The support unit 195 sets the designated card as a desired card. The display control unit 194 displays the desired card on the display 141. The management unit 193 stores information about the desired card in the deck information 183 in association with the deck ID.

[0190] Furthermore, the support unit 195 may set an unowned card as a desired card based on a constructed deck without designation from the user. Specifically, the support unit 195 acquires, for example, information about decks published on the Internet. The support unit 195 compares the published deck with the constructed deck, and extracts cards that are missing from the published deck. The support unit 195 determines whether the extracted card is owned, and sets the unowned card as a desired card. The display control unit 194 causes the display 141 to display the desired card. The management unit 193 stores information about the desired card in the deck information 183 in association with the deck ID.

[0191] (Notification of desired card) The display control unit 194 notifies the user of the desired card stored in association with the deck in the card information 182 in a manner that is easy for the user to confirm. Information notified about the desired card is, for example, the deck name associated with the desired card, the name of the desired card, an image of the desired card, etc. Examples of the easy-to-confirm method are as follows. Send by email Post to social media Send via contact tools · Post to the TCG Service Member Portal

[0192] FIG. 20 is a schematic diagram showing an example of a desired card notification screen displayed on the terminal device 10. The display control unit 194 notifies the user of information related to the desired card by using a predetermined communication tool. In FIG. 20, a box 1416 is displayed that displays the deck name, the desired card, the name of the card, and an image of the card. The user can check the desired card by launching the communication tool. Therefore, the desired card can be checked immediately as necessary.

[0193] (Show Q&A) The user inputs an instruction to request Q&A information to the terminal device 10. For example, the user inputs an instruction to the terminal device 10 to request Q&A information about a card related to a deck while the deck is being constructed.

[0194] FIG. 21 is a schematic diagram showing another example of the editing screen for the deck 2 displayed on the terminal device 10. In FIG. 21, the display control unit 194 displays a button 1417 for requesting Q&A information. When the user requests Q&A information related to the deck being edited, the user presses the button 1417. The control unit 190 transmits, for example, a signal requesting Q&A information and information about the cards forming the deck to the server 20 via the transmission / reception unit 192. The transmission / reception unit 192 may transmit the name of the deck to the server 20. The transmission / reception unit 192 may request the user to input keywords for constructing the deck, and transmit the input keywords to the server 20.

[0195] When the control unit 203 of the server 20 receives a request for Q&A information, the control unit 203 extracts Q&A information related to the deck in which the user is interested from the Q&A information table 2024 using the management module 2033. Specifically, for example, the management module 2033 extracts Q&A information from the Q&A information table 2024 based on information transmitted from the user regarding the cards that constitute the deck, the name of the deck, keywords for constructing the deck, and the like. The control unit 203 transmits the extracted Q&A information to the terminal device 10 using the transmission control module 2032.

[0196] The display control unit 194 displays the Q&A information transmitted from the server 20 on the display 141 .

[0197] Fig. 22 is a schematic diagram showing an example of a display screen for Q&A information. In Fig. 22, Q&A information related to deck 2 is arranged in a list in an area 1418. The information displayed in the list is, for example, an outline of the Q&A information, the name of a related card, and the like in the Q&A information. When any piece of Q&A information is selected by the user, the display control unit 194 displays details of the selected Q&A information on the display 141.

[0198] (External data output) When a user uploads his / her own deck information 183 to the server 20, the user inputs an instruction to the terminal device 10 to upload the deck information 183. When the instruction to upload is input, the terminal device 10 transmits the deck information 183 to the server 20 via the transmitting / receiving unit 192.

[0199] When the control unit 203 of the server 20 receives the deck information 183 from the user, the execution module 2034 executes processing related to a predetermined service. For example, the execution module 2034 calculates the rank of the user's deck based on the deck information 183 sent from the user. The rank may be expressed as a level or the like. Specifically, the execution module 2034 stores, for example, multiple pieces of deck information linked to achievements in tournaments and the like. For example, the execution module 2034 compares the stored deck information with the deck information 183 sent from the user to calculate the rank of the user's deck.

[0200] The execution module 2034 may calculate a rank for each attribute of the user. The user attributes are, for example, age, TCG proficiency, etc. When calculating a rank for each attribute, the execution module 2034 refers to pre-stored deck information, deck information of other users, user information of other users, etc., to calculate a rank for each attribute of the user.

[0201] Also, for example, the execution module 2034 may compare the deck information of the user previously transmitted to check whether there is a surplus or deficiency. For example, in a TCG tournament or the like, players may check the number of cards in the deck before the start of the match. Since the number of cards that constitute a deck is, for example, 60, it takes a certain amount of effort to check the number of cards. The execution module 2034 receives deck information related to the current deck and determines whether there is a surplus or deficiency in the deck. If there is a surplus or deficiency in the current deck, the execution module 2034 notifies the user of this fact and informs the user that a card needs to be added or a card needs to be removed in order to start the match. This makes it unnecessary to check the deck before the match, making it easier to manage the match.

[0202] The support unit 195 may support the user when there is a surplus or shortage of cards in the deck. The support unit 195 estimates the cards that are lacking based on, for example, the balance of the number of cards by type, the match of information related to attributes, cards that are estimated to be necessary based on a typical pattern of deck construction, etc., and suggests suitable cards from among the cards owned. The support unit 195 also estimates which cards are present in large numbers based on, for example, the balance of the number of cards by type, the match of information related to attributes, cards that are estimated to be unnecessary based on a typical pattern of deck construction, etc., and suggests to the user to remove the cards.

[0203] Also, the deck to be used in the actual match may be registered in advance, and at the start of the match, the deck to be used in the match may be checked to see if it is the same as the deck registered in advance. At the start of the match, the execution module 2034 receives deck information about the deck to be used in the match and determines whether it is the same as the deck registered in advance. If it is not the same as the deck registered in advance, the execution module 2034 notifies the user of this fact and informs the user that in order to start the match, it is necessary to revert to the deck registered in advance. This makes it easier to manage the match, as it is no longer necessary to check the deck at the start of the match.

[0204] As described above, in the above embodiment, the control unit 190 of the terminal device 10 stores information about a plurality of digital cards by the management unit 193. The management unit 193 stores information about a plurality of decks constructed by combining at least one of a plurality of digital cards in association with the plurality of digital cards. The control unit 190 displays a list of information about the plurality of digital cards to the user by the display control unit 194, and displays a digital card used in a single deck in the list so that the user can understand that the digital card is used in the deck, and displays a digital card used in a plurality of decks so that the deck currently contains the digital card and the deck that uses the digital card but does not contain the digital card can be understood. This makes it possible to use the digital card and understand the deck in which the analog card corresponding to the digital card is contained, even if there is an analog card shared by a plurality of decks.

[0205] Therefore, according to this embodiment, even if a single digital card is used in multiple decks at the same time, the digital cards can be efficiently managed. Also, analog cards can be efficiently managed using digital technology.

[0206] In the above embodiment, the display control unit 194 displays a list of the digital cards used in the deck, which allows the user to check the analog cards that make up the deck as digital information.

[0207] In the above embodiment, the display control unit 194 displays digital cards that are used in a deck but are not contained in the deck because they are contained in another deck in a manner that makes it possible to grasp the digital cards. This makes it possible to visually grasp the expected deck configuration using the digital cards when analog cards are shared among multiple decks.

[0208] In the above embodiment, the display control unit 194 switches between a state in which digital cards not stored are displayed and a state in which they are not displayed when displaying a list of decks. This makes it possible to switch between the state of the deck when it is actually used in a match and the current state of the deck for confirmation. By checking the current state of the deck, it becomes possible to flexibly imagine how to rearrange the cards.

[0209] In the above embodiment, when displaying a list of decks, the display control unit 194 displays an uncontained digital card in such a way that the deck containing the digital card can be distinguished. This allows the user to visually grasp, by using the digital card, which deck contains the analog card, even if the analog card is shared by multiple decks.

[0210] In addition, in the above embodiment, when displaying a list of decks, the display control unit 194 displays digital cards that are used in other decks but are not contained in the other decks in a form that allows the user to grasp the state of the deck. This allows the user to edit the deck while imagining the state of the other decks.

[0211] In the above embodiment, the control unit 190 suggests digital cards suitable for constructing a deck through the assistance unit 195. This allows the terminal device 10 to use digital data to reduce the burden on the user when constructing a deck.

[0212] In the above embodiment, the support unit 195 determines the proposed digital card from among the digital cards owned by the user. This reduces the user's effort to search for cards suitable for the corresponding deck from among the cards owned by the user.

[0213] In the above embodiment, the support unit 195 determines the proposed digital card from among digital cards that the user does not own. This allows the user to know which cards he or she needs to acquire to strengthen the deck.

[0214] In the above embodiment, the control unit 190 notifies the user of information on digital cards that are suitable for constructing a deck and that the user does not own in an easily recognizable manner through the notification unit 196. This allows the user to easily check the necessary cards when necessary.

[0215] In the above embodiment, when the number of digital cards constituting the deck is less than or exceeds the specified number, the support unit 195 suggests adding or removing cards to make the number of cards equal to the specified number. This makes it possible to reduce the effort of the user to select cards when the deck is almost complete. It also makes it possible to reduce the effort required to restore the deck when a card other than the cards constituting the deck gets mixed in or when a card constituting the deck is lost.

[0216] In the above embodiment, the control unit 190 acquires information about Q&A for the digital cards used in the deck selected by the user through the transmission / reception unit 192. The display control unit 194 displays the acquired information about Q&A to the user. This allows the user to easily acquire information about Q&A related to the deck.

[0217] <Modification> In the above embodiment, an example has been described in which all cards are managed as cards shared with other decks and cards lent to other decks. However, the cards managed as cards shared with other decks and cards lent to other decks do not have to be all cards. For example, the management unit 193 may manage only cards of a predetermined classification as cards shared with other decks and cards lent to other decks. Examples of cards of a predetermined classification are as follows. Cards with a specified rarity or higher Cards with special effects (for example, cards that have unique "characteristics") -Cards of a specified type - User selected card

[0218] In this way, when displaying a list of decks, the display control unit 194 regards the digital cards whose storage destinations are managed as digital cards of a predetermined classification. This makes it possible to avoid excessive information because the decks in which cards that do not need to be concerned about the number of cards owned are stored are not listed.

[0219] In addition, when displaying the list of decks, the classification of the digital cards whose storage locations are to be managed is specified by the user. This allows information about the decks that use the digital cards and the decks that store them to be displayed for the digital cards that the user is interested in, making it possible to provide the information that the user desires.

[0220] In addition, when displaying a list of decks, the classification of digital cards whose storage locations are managed is set based on the rarity of the digital cards, which allows the user to obtain information about rare cards about which the user may need to be concerned about the number of cards.

[0221] It is also possible that a user may switch digital cards between decks in the application but forget to switch analog cards between them. In such a case, the user must figure out which cards are missing from the deck and which cards are in excess, which makes checking the deck time-consuming.

[0222] For example, the terminal device 10 photographs a card incorporated in a deck. The support unit 195 compares a card identified from the photographed image with a card incorporated in the corresponding deck stored in the deck information 183. The support unit 195 extracts information about a predetermined card based on the comparison result. Specifically, for example, when the number of cards incorporated in the current deck is less than the number of cards stored, the support unit 195 extracts the missing card. The support unit 195 acquires in which deck the extracted card is contained based on the deck information 183. The display control unit 194 presents to the user a card that should be incorporated in a deck but is not actually contained therein, and the deck in which this card is contained. The support unit 195 may refer to a movement log of cards between decks stored in the deck information 183.

[0223] Also, for example, when the number of cards incorporated in the current deck is greater than the number of cards stored, the support unit 195 extracts the excess cards. The support unit 195 acquires, based on the deck information 183, which deck the extracted card should be removed from and housed in, or should simply be removed from the deck. The display control unit 194 presents to the user cards that should not be incorporated into a deck but are actually included, and how to handle these cards. The support unit 195 may refer to a movement log of cards between decks stored in the deck information 183.

[0224] <4 Basic hardware configuration of computer> 23 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.

[0225] The processor 91 is hardware for executing an instruction set described in a program, and is composed of an arithmetic unit, a register, a peripheral circuit, and the like.

[0226] The main storage device 92 is for temporarily storing programs, data to be processed by the programs, etc. For example, it is a volatile memory such as a DRAM (Dynamic Random Access Memory).

[0227] The auxiliary storage device 93 is a storage device for saving data and programs, such as a flash memory, a hard disk drive (HDD), a magneto-optical disk, a CD-ROM, a DVD-ROM, or a semiconductor memory.

[0228] The communication IF 99 is an interface for inputting and outputting signals for communicating with other computers via a network using a wired or wireless communication standard.

[0229] The network is composed of the Internet, a LAN, various mobile communication systems constructed by wireless base stations, etc. For example, the network includes 3G, 4G, 5G mobile communication systems, LTE (Long Term Evolution), wireless networks that can connect to the Internet via a specified access point (e.g., Wi-Fi (registered trademark)), etc. In the case of wireless connection, communication protocols include, for example, Z-Wave (registered trademark), ZigBee (registered trademark), Bluetooth (registered trademark), etc. In the case of wired connection, the network also includes a network that is directly connected by a USB (Universal Serial Bus) cable or the like.

[0230] It should be noted that the computer 90 can be virtually realized by distributing all or part of each hardware configuration among multiple computers 90 and connecting them together via a network. In this way, the computer 90 is a concept that includes not only a computer 90 housed in a single housing or case, but also a virtualized computer system.

[0231] <Basic functional configuration of computer 90> A description will now be given of the functional configuration of a computer realized by the basic hardware configuration of a computer 90 shown in Fig. 23. The computer includes at least the functional units of a control unit, a storage unit, and a communication unit.

[0232] The functional units of the computer 90 can also be realized by distributing all or part of the functional units among multiple computers 90 connected to each other via a network. The computer 90 is a concept that includes not only a single computer 90 but also a virtualized computer system.

[0233] The control unit is realized by the processor 91 reading out various programs stored in the auxiliary storage device 93, expanding the programs in the main storage device 92, and executing processes according to the programs. The control unit can realize functional units that perform various information processing depending on the type of program. In this way, the computer is realized as an information processing device that performs information processing.

[0234] 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. Furthermore, 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. Furthermore, the control unit can cause the processor 91 to execute processes of adding, updating, and deleting data stored in the storage unit in accordance with the various programs.

[0235] A database refers to a relational database, which is used to manage data sets called tables, which are structured according to rows and columns, by relating them to each other. In a database, a table is called a table, a column in a table is called a column, and a row in a table is called a record. In a relational database, it is possible to set relationships between tables and associate them.

[0236] Usually, a column is set in each table as a key for uniquely identifying a record, but setting a key in the 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 storage unit according to various programs.

[0237] The communication unit is realized by the communication IF 99. The communication unit realizes a function of communicating with other computers 90 via a network. The communication unit can receive information transmitted from other computers 90 and input the information 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. In addition, the communication unit can transmit information output from the control unit to other computers 90.

[0238] Although several embodiments of the present disclosure have been described above, these embodiments can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and modifications are within the scope of the invention and its equivalents as described in the claims, as well as the scope and spirit of the invention.

[0239] <Additional Notes> The matters described in the above embodiments will be supplemented below. (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: storing information relating to a plurality of digital cards; storing information relating to a plurality of decks constructed by combining at least any of the plurality of digital cards in association with the plurality of digital cards; and displaying a list of information relating to the plurality of digital cards to a user, displaying in the list digital cards used in a single deck so that the user can understand that they are used in that deck, and displaying digital cards used in a plurality of decks so that the deck currently contains the cards and the decks that have been used but are not contained in the cards can be understood. (Appendix 2) A program as described in (Appendix 1) that causes a processor to execute a step of displaying a list of digital cards to be used in a deck. (Appendix 3) A program described in Appendix 2, in which in the step of displaying a list of decks, digital cards that are used in a deck but are not contained in the deck because they are contained in other decks are displayed in an understandable manner. (Appendix 4) A program as described in (Appendix 3), in which, in the step of displaying a list of decks, a state in which uncontained digital cards are displayed is switched to a state in which they are not displayed. (Appendix 5) A program as described in claim 3, in which in the step of displaying a list of decks, a digital card that is not housed is displayed in such a way that the deck that houses the digital card can be distinguished. (Appendix 6) A program described in any one of (Appendix 2) to (Appendix 5), in which, in the step of displaying a list of decks, digital cards contained in the deck that are also used in other decks but are not contained in those other decks are displayed in an understandable manner. (Appendix 7) The program according to any one of (Supplementary Note 3) to (Supplementary Note 5), wherein in the step of displaying a list of decks, the digital cards whose storage destinations are managed are digital cards of a predetermined classification. (Appendix 8) The program according to claim 7, wherein in the step of displaying a list of decks, a classification of digital cards whose storage locations are to be managed is designated by a user. (Appendix 9) A program according to claim 7, wherein in the step of displaying a list of decks, classification of the digital cards whose storage locations are managed is based on the rarity of the digital cards. (Appendix 10) A program described in any one of (Appendix 1) to (Appendix 9) that causes a processor to execute a step of suggesting digital cards suitable for building a deck. (Appendix 11) The program according to claim 10, wherein in the proposing step, the proposed digital card is included in a digital card owned by the user. (Appendix 12) The program according to claim 10, wherein in the proposing step, the proposed digital card is a digital card that the user does not own. (Appendix 13) A program described in any of (Appendix 1) to (Appendix 12) that causes a processor to execute a step of notifying a user in a manner that is easily recognizable by the user of information regarding digital cards that are suitable for building a deck and that the user does not own. (Appendix 14) A program described in any one of (Appendix 1) to (Appendix 13), which suggests adding or removing cards to make the deck contain the specified number of digital cards if the number of digital cards constituting the deck is less than or exceeds a specified number. (Appendix 15) A program described in any of (Appendix 1) to (Appendix 14) that causes a processor to execute the steps of obtaining information regarding Q&A about digital cards to be used in a deck selected by a user, and displaying the obtained information regarding Q&A to the user. (Appendix 16) A method executed by a computer having a processor and a memory, the method comprising the steps of: storing information relating to a plurality of digital cards, storing information relating to a plurality of decks constructed by combining at least any of the plurality of digital cards in association with the plurality of digital cards, and displaying a list of information relating to the plurality of digital cards to a user, displaying in the list digital cards used in a single deck so that the user can understand that they are used in that deck, and displaying digital cards used in a plurality of decks so that the deck currently contains the digital cards and the decks that have been used but are not contained in the digital cards can be understood. (Appendix 17) An information processing device having a control unit and a memory unit, wherein the control unit executes the steps of: storing information about a plurality of digital cards; storing information about a plurality of decks constructed by combining at least any of the plurality of digital cards in association with the plurality of digital cards; and displaying a list of information about the plurality of digital cards to a user, displaying in the list digital cards used in a single deck so that the user can understand that they are used in that deck, and displaying digital cards used in a plurality of decks so that the deck currently contains the cards and the decks that have been used but not contained the cards can be understood. (Appendix 18) The system comprises: a means for storing information about a plurality of digital cards; a means for storing information about a plurality of decks constructed by combining at least one of the plurality of digital cards in association with the plurality of digital cards; and a means for displaying a list of information about the plurality of digital cards to a user, displaying in the list a digital card employed in a single deck so that the digital card is grasped as being employed in that deck, and displaying digital cards employed in the plurality of decks so that the deck currently containing the card and the deck which has employed the card but does not contain the card are grasped. [Explanation of symbols]

[0240] 1. System 10...Terminal device 12…Communication Interface 120…Communications Department 13...Input device 131...Touch-sensitive devices 14...Output device 141…Display 15…Memory 150...Location information sensor 16…Storage 160…Camera 17...Audio processing unit 171…Mike 172…Speaker 180...Storage section 19…Processor 190...Control unit 20…Server

Claims

1. A program to be executed by a computer having a processor and a memory, the program causing the processor to: storing ownership information regarding digital cards corresponding to a plurality of analog cards owned by the user based on an input operation by the user; acquiring deck configuration information configured by combining at least any of a plurality of digital cards based on an input operation from the user; comparing the ownership information with the deck configuration information, and identifying missing cards among the plurality of digital cards included in the deck configuration information, where the number of analog cards in the ownership information is insufficient; displaying a list based on the deck configuration information to a user, and displaying the missing cards in the list so that the user can grasp the missing cards; A program that executes the following.

2. The processor, The program according to claim 1 , further comprising a step of making the information about the missing card available to other users other than the user.

3. The processor, acquiring an image captured by a camera; a step of identifying an analog card appearing in the image and storing information about the identified analog card as analog card deck information about cards that constitute an analog card deck constructed by the user using the analog cards; a step of comparing the deck configuration information with the analog card deck information to identify at least one of uncontained cards that are insufficient in the analog card deck compared to the deck configuration related to the deck configuration information and excess cards that are in excess in the analog card deck compared to the deck configuration related to the deck configuration information as difference cards that are a difference between the deck configuration related to the deck configuration information and the analog card deck; displaying information about the difference card to a user; The program according to claim 1 ,

4. The ownership information includes information about a deck in which the analog card owned by the user is stored, the processor, When the unhoused card is identified as the difference card, referring to the ownership information, identifying another deck in which an analog card corresponding to the unhoused card is housed; displaying information about the identified other deck together with information about the uninserted card to the user; The program according to claim 3, wherein the program executes the following.

5. A method executed on a computer having a processor and a memory, wherein the processor: storing ownership information regarding digital cards corresponding to a plurality of analog cards owned by the user based on an input operation by the user; acquiring deck configuration information configured by combining at least any of a plurality of digital cards based on an input operation from the user; comparing the ownership information with the deck configuration information, and identifying missing cards among the plurality of digital cards included in the deck configuration information, where the number of analog cards in the ownership information is insufficient; displaying a list based on the deck configuration information to a user, and displaying the missing cards in the list so that the user can grasp the missing cards; How to do it.

6. An information processing device comprising a control unit and a storage unit, wherein the control unit: storing ownership information regarding digital cards corresponding to a plurality of analog cards owned by the user based on an input operation by the user; acquiring deck configuration information configured by combining at least any of a plurality of digital cards based on an input operation from the user; comparing the ownership information with the deck configuration information, and identifying missing cards among the plurality of digital cards included in the deck configuration information, where the number of analog cards in the ownership information is insufficient; displaying a list based on the deck configuration information to a user, and displaying the missing cards in the list so that the user can grasp the missing cards; An information processing device that executes the above.

7. A means for storing ownership information regarding digital cards corresponding to multiple analog cards owned by a user based on an input operation from the user; a means for acquiring deck configuration information formed by combining at least one of a plurality of digital cards based on an input operation from the user; a means for comparing the ownership information with the deck configuration information and identifying missing cards among the plurality of digital cards included in the deck configuration information, the number of analog cards being insufficient in the ownership information; a means for displaying a list based on the deck configuration information to a user and displaying the missing cards in the list in a way that the user can grasp the missing cards; A system comprising:

Images