Information processing method, program, information processing device, and information processing system

Abstract

To provide visitors of a strategy site with information useful for beating a game.SOLUTION: An information processing method for presenting, to visitors of a strategy site providing information to beat a game, recommendation information to be recommended for beating the game causes a computer to execute the steps of: acquiring visitor game information related to a game status of a visitor, and generating recommendation information to be recommended to the visitor based on the visitor game information and the information to beat the game.SELECTED DRAWING: Figure 3

Description

Technical Field

[0001] The present invention relates to an information processing method, a program, an information processing apparatus, and an information processing system.

Background Art

[0002] Generally, a website that provides walkthrough information regarding game playthrough (hereinafter referred to as a "walkthrough site") is known. By browsing the walkthrough information on the walkthrough site, game users can smoothly progress the game.

[0003] Since such a walkthrough site is operated by a walkthrough site provider different from the game vendor that provides the game, objective information can be provided, and information regarding games provided by a plurality of game vendors can be provided. Therefore, compared with the information provided by game vendors, it tends to be viewed by more users.

[0004] Patent Document 1 discloses a technique including storage means for storing the number of paid items and free items owned by a player, and control means for executing a lottery game in which a predetermined number of game items are consumed from the game items owned by the player to give the selected content, and the control means consumes the paid items and free items in a predetermined order and gives preference to the lottery game according to the number of paid items included in the predetermined number of game items.

Prior Art Documents

Patent Documents

[0005]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0006] The technology of Patent Document 1 relates to a lottery game which is one of the elements of a game. Therefore, the technology of Patent Document 1 is applicable to users during the play of the game, but not applicable to users who leave the game play and visit the walkthrough site (i.e., visitors to the walkthrough site).

[0007] An object of the present invention is to provide information useful for game walkthrough to visitors to the walkthrough site.

Means for Solving the Problem

[0008] One aspect of the present invention is an information processing method for presenting recommendation information recommended for game walkthrough to visitors to a walkthrough site that provides game walkthrough information, wherein a computer executes a step of obtaining visitor game information regarding the game situation of the visitor, and executes a step of generating recommendation information to be recommended to the visitor based on the visitor game information and the walkthrough information. This is the information processing method.

Brief Description of the Drawings

[0009]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Figure 23

Figure 24

Mode for Carrying Out the Invention

[0010] Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings. In the drawings for explaining the embodiment, the same components are generally denoted by the same reference numerals, and the repeated description thereof will be omitted.

[0011] (0) Definition of Terms The definitions of the terms in this embodiment are as follows.

[0012] The "walkthrough site" is a website that provides walkthrough information for clearing a game.

[0013] The "recommended information" is information recommended for clearing a game.

[0014] The "visitor to be analyzed" is a visitor who is the subject of analysis.

[0015] The "visitor game information" is information regarding the game situation of the visitor. The "pre-visit game information" is the visitor game information before the execution of the analysis request. The "post-visit game information" is the visitor game information after the execution of the analysis request.

[0016] The "game element" is an element that can be used within a game.

[0017] The "element parameter" is the efficacy (for example, the effect or ability that affects the execution result of the game) possessed by the game element.

[0018] The "goods" are products related to the game and sold outside the game. The "player" is the entity that plays the game and is the game element corresponding to the visitor within the game.

[0019] The "friend" is another player registered as a friend of a certain player within the game.

[0020] (1) Configuration of the information processing system The configuration of the information processing system will be described. FIG. 1 is a block diagram showing the configuration of the information processing system of this embodiment. FIG. 2 is a functional block diagram of the information processing system of FIG. 1.

[0021] As shown in FIG. 1, the information processing system 1 includes a client device 10, a target website server 30, and a game server 50. The client device 10, the target website server 30, and the game server 50 are connected via a network (e.g., the Internet or an intranet) NW.

[0022] The client device 10 is a computer (an example of an "information processing device") that sends requests to the target website server 30 or the game server 50. The client device 10 is, for example, a smartphone, a tablet terminal, or a personal computer.

[0023] The target website server 30 is a computer (an example of an "information processing device") that provides a response according to a request sent from the client device 10 or the game server 50 to the client device 10 or the game server 50. The target website server 30 is, for example, a web server. The target website server 30 is operated, for example, by a target website provider.

[0024] The game server 50 is a computer (an example of an "information processing device") that provides a response according to a request sent from the client device 10 or the target website server 30 to the client device 10 or the target website server 30. The game server 50 is, for example, a server that provides game services. The game server 50 is operated, for example, by a game vendor.

[0025] (1-1) Configuration of the client device The configuration of the client device 10 will be described.

[0026] As shown in FIG. 2, the client device 10 includes a storage device 11, a processor 12, an input / output interface 13, and a communication interface 14.

[0027] The memory device 11 is configured to store programs and data. The memory device 11 is, for example, a combination of a ROM (Read Only Memory), a RAM (Random Access Memory), and a storage (e.g., a flash memory or a hard disk).

[0028] The program includes, for example, the following programs. · A program of an OS (Operating System) · Parameters, functions, and models used in information processing · A program of an application that executes information processing (e.g., a web browser or a game application that executes a game)

[0029] The data includes, for example, the following data. · A database referenced in information processing · Data obtained by executing information processing (i.e., the execution result of information processing)

[0030] The processor 12 is configured to realize the functions of the client device 10 by starting the programs stored in the memory device 11. The processor 12 is, for example, a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or a combination thereof.

[0031] The input / output interface 13 is configured to obtain an instruction from a visitor from an input device connected to the client device 10 and output information to an output device connected to the client device 10. The input device is, for example, a keyboard, a pointing device, a touch panel, or a combination thereof. The output device is, for example, a display.

[0032] The communication interface 14 is configured to control communication between the client device 10 and the target site server 30.

[0033] (1-2) Configuration of the target site server The configuration of the target site server 30 will be described.

[0034] As shown in FIG. 2, the target site server 30 includes a storage device 31, a processor 32, an input / output interface 33, and a communication interface 34.

[0035] The storage device 31 is configured to store programs and data. The storage device 31 is, for example, a combination of a ROM, a RAM, and a storage (e.g., a flash memory or a hard disk).

[0036] The program includes, for example, the following programs. · Program of the OS · Parameters, functions, and models used in information processing · Program of an application that executes information processing

[0037] The data includes, for example, the following data. · Database referred to in information processing · Execution result of information processing

[0038] The processor 32 is configured to realize the functions of the target site server 30 by starting the programs stored in the storage device 31. The processor 32 is, for example, a CPU, a GPU, an ASIC, an FPGA, or a combination thereof.

[0039] The input / output interface 33 is configured to obtain instructions from visitors from an input device connected to the target site server 30 and output information to an output device connected to the target site server 30. The input device is, for example, a keyboard, a pointing device, a touch panel, or a combination thereof. The output device is, for example, a display.

[0040] The communication interface 34 is configured to control communication between the captured site server 30 and the client device 10 or the game server 50.

[0041] (1-3) Configuration of the game server The configuration of the game server 50 will be described. The game server 50 is a server operated by a game vendor.

[0042] As shown in FIG. 2, the game server 50 includes a storage device 51, a processor 52, an input / output interface 53, and a communication interface 54.

[0043] The storage device 51 is configured to store programs and data. The storage device 51 is, for example, a combination of a ROM, a RAM, and a storage (e.g., a flash memory or a hard disk).

[0044] The program includes, for example, the following programs. ·Program of the OS ·Parameters, functions, and models used in information processing ·Program of an application that executes information processing

[0045] The data includes, for example, the following data. ·Database referenced in information processing ·Execution result of information processing

[0046] The processor 52 is configured to realize the functions of the game server 50 by starting the programs stored in the storage device 51. The processor 52 is, for example, a CPU, a GPU, an ASIC, an FPGA, or a combination thereof.

[0047] The input / output interface 53 is configured to obtain an instruction from a visitor from an input device connected to the game server 50 and output information to an output device connected to the game server 50. The input device is, for example, a keyboard, a pointing device, a touch panel, or a combination thereof. The output device is, for example, a display.

[0048] The communication interface 54 is configured to control communication between the game server 50 and the client device 10 or the strategy site server 30.

[0049] (2) Summary of the Embodiment The summary of this embodiment will be described. FIG. 3 is an explanatory diagram of the summary of this embodiment.

[0050] As shown in FIG. 3, the strategy site server 30 stores strategy information and visitor game information.

[0051] The client device 10 transmits a request (hereinafter referred to as a "strategy information presentation request") for causing the strategy site server 30 to present the strategy information stored in the strategy site server 30 in response to an instruction from a visitor.

[0052] The strategy site server 30 generates recommendation information based on the visitor game information of the visitor and the strategy information corresponding to the strategy information presentation request. The strategy site server 30 transmits the recommendation information to the client device 10.

[0053] (3) Database The database of this embodiment will be described. FIGS. 4 to 7 are diagrams showing the data structure of the database of this embodiment. The databases in FIGS. 4 to 7 are stored in the storage device 31.

[0054] (3-1) Walkthrough Site Database The walkthrough site database of this embodiment will be described.

[0055] In the walkthrough site database of FIG. 4, walkthrough site information is stored. The walkthrough site information is information regarding the walkthrough site. The walkthrough site database includes a "walkthrough site ID" field, a "walkthrough site URL" field, a "walkthrough information" field, a "game ID" field, and a "meta tag" field. Each field is associated with each other.

[0056] In the "walkthrough site ID" field, walkthrough site identification information is stored. The walkthrough site identification information is information for identifying the walkthrough site.

[0057] In the "walkthrough site URL" field, walkthrough site URL information is stored. The walkthrough site URL information is the URL (Uniform Resource Locator) of the walkthrough site.

[0058] In the "walkthrough information" field, walkthrough information is stored. The walkthrough information is information regarding the walkthrough of the game.

[0059] In the "game ID" field, game identification information of the game corresponding to the walkthrough information provided on the walkthrough site is stored. The game identification information is information for identifying the game.

[0060] In the "meta tag" field, meta tag information is stored. The meta tag information is tag information regarding the content of the walkthrough site. The meta tag information includes, for example, at least one of the following. · Game name · Page summary · Campaign name (as an example, at least one of the quest name and event name targeted by the campaign) · Campaign period · Campaign evaluation · Campaign recommendation degree · Keyword

[0061] (3-2) Visitor database The visitor database of this embodiment will be described.

[0062] Visitor information is stored in the visitor database of FIG. 4. The visitor information is information about the visitor who visits the conquest site. The visitor database includes a "Visitor ID" field, a "Visitor Name" field, a "Visitor Attribute" field, and a "Player" field. Each field is associated with each other.

[0063] Visitor identification information is stored in the "Visitor ID" field. The visitor identification information is information for identifying the visitor.

[0064] Visitor name information is stored in the "Visitor Name" field. The visitor name information is information about the name of the visitor (for example, the handle name registered on the conquest site).

[0065] Visitor attribute information is stored in the "Visitor Attribute" field. The visitor attribute information is information about the attributes of the visitor. The "Visitor Attribute" field includes a "Gender" field and an "Age" field.

[0066] Gender information is stored in the "Gender" field. The gender information is information about the gender of the visitor.

[0067] Age information is stored in the "Age" field. The age information is information about the age of the visitor.

[0068] Player information is stored in the "Player" field. The player information is information about the player of the game that the visitor plays. The "Player" field includes a "Game ID" field and a "Player ID" field.

[0069] The "Game ID" field stores game identification information. The game identification information is information for identifying a game.

[0070] The "Player ID" field stores player identification information. The player identification information is information for identifying a player.

[0071] (3-3) Vendor Database The vendor database of this embodiment will be described.

[0072] The vendor database in FIG. 4 stores vendor information. The vendor information is information regarding the vendor that provides the game. The vendor database includes a "Vendor ID" field and a "Vendor Name" field. Each field is associated with each other.

[0073] The "Vendor ID" field stores vendor identification information. The vendor identification information is information for identifying a vendor.

[0074] The "Vendor Name" field stores vendor name information. The vendor name information is information regarding the name of the vendor.

[0075] (3-4) Game Database The game database of this embodiment will be described.

[0076] The game database in FIG. 5 stores game information. The game information is information regarding the game. The game database includes a "Game ID" field, a "Game Title" field, a "Game Attribute" field, a "Platform" field, and a "Linked File URL" field. Each field is associated with each other. The game database is associated with vendor identification information.

[0077] The "Game ID" field stores game identification information. Game identification information is information that identifies a game.

[0078] The "Game Title" field stores game title information. Game title information is information regarding the title of the game (i.e., the name of the game).

[0079] The "Game Genre" field stores game genre information. Game genre information is information regarding the genre of the game (e.g., RPG (Role Playing Game), location-based game, or sports).

[0080] The "Platform" field stores platform information. Platform information is information regarding the name of the platform on which the game application is distributed.

[0081] The "Linked File URL" field stores linked file URL information. Linked file URL information is the URL of a file containing content related to the game. The linked file URL includes, for example, at least one of the following. · The URL of the official website of the game · The official SNS (Social Networking Service) account of the game · The URL for downloading the game application on the distribution platform · The URL of the game's privacy policy · The URL of the game's terms of use · The URL of the game's creator distribution agreement

[0082] (3 - 5) Game Element Database The game element database of this embodiment will be described.

[0083] Game element information is stored in the game element database of FIG. 5. The game element information is information regarding game elements. The game element database includes a "game element ID" field, a "game element name" field, a "game element type" field, a "game element parameter" field, and a "game element expiration date" field. Each field is associated with each other. The game element database is associated with game identification information.

[0084] Game element identification information is stored in the "game element ID" field. The game element identification information is information for identifying game elements.

[0085] Game element name information is stored in the "game element name" field. The game element name information is information regarding the name of the game element.

[0086] Game element type information is stored in the "game element type" field. The game element type information is information regarding the type of game element. The types of game elements include, for example, at least one of the following. · Game characters (as an example, characters that can be used in the game) · Game items (as an example, items that support characters) · Game quests (as an example, tasks or missions given in the game) · Game tickets (as an example, tickets required to challenge game quests) · Game campaigns related to at least one of game characters, game items, game quests, and game tickets · Game currency (currency that can be exchanged for at least one of, for example, game characters, game items, game quests, game tickets, and game campaigns)

[0087] Game element parameter information is stored in the "Game element parameter" field. The game element parameter information is information regarding the element parameter.

[0088] Game element expiration information is stored in the "Game element expiration" field. The game element expiration information is information regarding the expiration date of the game element.

[0089] (3-6) Goods database The goods database of this embodiment will be described.

[0090] Goods information is stored in the goods database of FIG. 5. The goods information is information regarding goods manufactured by a game vendor or a third party and manufactured in cooperation with a game. The goods database includes a "Goods ID" field, a "Goods name" field, and an "Inventory" field. Each field is associated with each other. The goods database is associated with game identification information.

[0091] Goods identification information is stored in the "Goods ID" field. The goods identification information is information for identifying goods.

[0092] Goods name information is stored in the "Goods name" field. The goods name information is information regarding the name of the goods.

[0093] Inventory information is stored in the "Inventory" field. The inventory information is information regarding the inventory of goods. The inventory information includes, for example, at least one of the following. · Inventory quantity · Scheduled arrival date

[0094] (3 - 7) Visitor game database The visitor game database of this embodiment will be described.

[0095] Visitor game information is stored in the visitor game database of FIG. 6. The visitor game database includes a "Game ID" field, a "Player ID" field, a "Player Name" field, a "Player Parameter" field, an "Owned Element" field, a "Player Deck" field, a "Friend" field, and a "Game Score" field. Each field is associated with each other. The visitor game database is associated with visitor identification information.

[0096] The guide site server 30 updates the visitor game database using the visitor game information obtained by at least one of the following methods. · Method of obtaining visitor game information from the game server 50 · Method of obtaining visitor game information from the game application of the client device 10 · Method of obtaining visitor game information input by the visitor from the client device 10 · Method of obtaining image information of the screen of the game application input by the visitor from the client device 10 and generating visitor game information by performing image analysis processing on the image information

[0097] Game identification information is stored in the "Game ID" field.

[0098] Player identification information is stored in the "Player ID" field. The player identification information is information for identifying the player.

[0099] Player name information is stored in the "Player Name" field. The player name information is information regarding the name of the player.

[0100] Player parameter information is stored in the "Player Parameter" field. The player parameter information is information regarding the parameters of the player. The "Player Parameter" field includes the "Player Level" field and the "Player Ability" field.

[0101] Player level information is stored in the "Player Level" field. The player level information is information regarding the level of the player.

[0102] Player ability information is stored in the "Player Ability" field. The player ability information is information regarding the ability of the player.

[0103] Held element information is stored in the "Held Element" field. The held element information is information regarding the game elements held by the player. The "Held Element" field includes the "Game Element ID" field and the "Game Element Parameter" field.

[0104] Game element identification information is stored in the "Game Element ID" field.

[0105] Game element parameter information is stored in the "Game Element Parameter" field. The game element parameter information is information regarding the parameters of the game element. The "Game Element Parameter" field includes the "Game Element Level" field and the "Game Element Ability" field.

[0106] The "Game Element Level" field stores game element level information. The game element level information is information regarding the level of the game element.

[0107] The "Game Element Ability" field stores game element ability information. The game element ability information is information regarding the ability of the game element.

[0108] The "Player Deck" field stores player deck information. The player deck information is information regarding the player deck. The player deck includes, for example, at least one of the following. · A combination of in-game characters that the player uses in the game · A combination of in-game items that the player uses in the game

[0109] The "Friend" field stores friend information. The friend information is information regarding the friend. The "Friend" field includes a "Friend ID" field and a "Relation" field.

[0110] The "Friend ID" field stores friend player identification information. The friend player identification information is the player identification information of other players registered as friends.

[0111] The "Relation" field stores relation information. The relation information is information regarding the relationship between the player and the friend. The relationship includes, for example, at least one of the following. · The intimacy between the player and the friend · The number of times the player has acted with the friend · Other information that the visitor has permitted to be saved to the conquest site server 30

[0112] Game result information is stored in the "Game result" field. The game result information is information regarding the player's game result. The game result includes, for example, at least one of the following. · Character parameters (level | ability, etc.) · Number of defeated enemy characters · Quest progress · Items in possession (quantity | level | equipped status) · Remaining currency balance

[0113] (3 - 8) Access log database The access log database of this embodiment will be described.

[0114] Access log information is stored in the access log database of FIG. 7. The access log information is information regarding the history of visits to the walkthrough site by the visitor. The access log database includes an "Access log ID" field, a "Timestamp" field, a "Site URL" field, and a "Search keyword" field. Each field is associated with each other. The access log database is associated with visitor identification information.

[0115] Access log identification information is stored in the "Access log ID" field. The access log identification information is information for identifying the access log.

[0116] Timestamp information is stored in the "Timestamp" field. The timestamp information is information regarding the date and time when the walkthrough site was visited.

[0117] Site URL information of the walkthrough site visited by the visitor is stored in the "Site URL" field.

[0118] Search keyword information is stored in the "Search keyword" field. The search keyword information is information regarding the search keyword. The search keyword includes, for example, at least one of the following. · The keyword entered by the visitor into the search site to access the target site · The keyword entered by the visitor into the search window of the target site to narrow down the target site

[0119] (3-9) Submission log database The submission log database of this embodiment will be described.

[0120] In the submission log database of FIG. 7, submission log information is stored. The submission log information is information regarding the history of submissions to the target site by the visitor. The submission log database includes a "submission log ID" field, a "timestamp" field, a "target site URL" field, and a "submission content" field. Each field is associated with each other. The submission log database is associated with visitor identification information.

[0121] In the "submission log ID" field, submission log identification information is stored. The submission log identification information is information for identifying the submission log.

[0122] In the "timestamp" field, timestamp information is stored. The timestamp information is information regarding the date and time when the submission was executed.

[0123] In the "target site URL" field, the site URL information of the target site associated with the submission is stored.

[0124] In the "submission content" field, submission content information is stored. The submission content information is information regarding the content of the submission.

[0125] (3-10) Location log database The location log database of this embodiment will be described.

[0126] The location log database in FIG. 7 stores location log information. The location log information is information regarding the history of the visitor's location. The location log database includes a "location log ID" field, a "timestamp" field, and a "location" field. Each field is associated with each other. The location log database is associated with visitor identification information.

[0127] The "location log ID" field stores location log identification information. The location log identification information is information for identifying the location log.

[0128] The "timestamp" field stores timestamp information. The timestamp information is information regarding the date and time of the location log.

[0129] The "location" field stores location information. The location information is information regarding the visitor's location. The location information is, for example, at least one of the following. · GPS (Global Positioning System) information transmitted at predetermined time intervals from the GPS module disposed in the client device 10 · Location information specified by the visitor (as an example, at least one of the location (for example, city) visited by the visitor, address, latitude and longitude, direction, altitude, landmark facility, public facility, and store) · Other location information permitted by the visitor to be saved to the conquest site server 30

[0130] (3-11) Purchase log database The purchase log database of the present embodiment will be described.

[0131] The purchase log database in FIG. 7 stores purchase log information. The purchase log information is information regarding the history of goods purchases by the visitor. The purchase log database contains a "Purchase Log ID" field, a "Timestamp" field, and a "Goods ID". Each field is associated with each other. The purchase log database is associated with visitor identification information.

[0132] The "Purchase Log ID" field stores purchase log identification information. The purchase log identification information is information that identifies a purchase log.

[0133] The "Timestamp" field stores timestamp information. The timestamp information is information regarding the date and time of the purchase log.

[0134] The "Goods ID" field stores the goods identification information of the purchased goods.

[0135] (3-12) Healthcare Log Database The healthcare log database of this embodiment will be described.

[0136] The healthcare log database in FIG. 7 stores healthcare log information. The healthcare log information is information regarding the healthcare history of goods by a visitor. The healthcare log database contains a "Healthcare Log ID" field and a "Timestamp" field. Each field is associated with each other. The healthcare log database is associated with visitor identification information.

[0137] The "Healthcare Log ID" field stores healthcare log identification information. The healthcare log identification information is information that identifies a healthcare log.

[0138] The "Timestamp" field stores timestamp information. The timestamp information is information regarding the date and time of the healthcare log.

[0139] In the "healthcare" field, healthcare information is stored. The healthcare information is information related to healthcare. The healthcare information includes, for example, at least one of the following. · Number of steps · Moving distance · Sleep time · Exercise time · Height · Weight · Stride length · Number of times of fluid replenishment · Other information that the visitor has permitted to be stored in the conquest site server 30

[0140] (4) Information processing The information processing of this embodiment will be described.

[0141] (4-1) Overall flow The overall flow of this embodiment will be described. FIG. 8 is a diagram showing the overall flow of this embodiment.

[0142] As shown in FIG. 8, the information processing of this embodiment includes game execution (OP1) and recommendation (OP2).

[0143] Game execution (OP1) is a process for executing a game in response to an instruction from a visitor.

[0144] Recommendation (OP2) is a process of presenting recommendation information to a visitor who has visited the conquest site.

[0145] (4-2) Game execution (OP1) The process of game execution of this embodiment will be described. FIG. 9 is a sequence diagram of the game execution process of this embodiment. FIG. 10 is a diagram showing an example of a screen displayed in the information processing of FIG. 9.

[0146] The trigger for the information processing in FIG. 9 is, for example, an operation by a visitor on a game application installed in the client device 10. Player identification information of a player in the game executed by the game application is assigned to the game application.

[0147] [Game execution request (S1110)] As shown in FIG. 9, the client device 10 executes a game execution request. Specifically, the processor 12 displays the screen P1110 (FIG. 10) on the display.

[0148] The screen P1110 includes a display object A1110 and operation objects B1110a to B1110b.

[0149] The display object A1110 is an object that displays a game screen.

[0150] The operation objects B1110a to B1110b are objects that receive an instruction from a visitor to play the game. The operation object B1110a is an object that receives an instruction from a visitor to specify an attack in the game. The operation object B1110b is an object that receives an instruction from a visitor to specify the use of a game element in the game.

[0151] When the visitor operates the operation object B1110a or B1110b, the processor 12 transmits game execution request data to the attack site server 30. The game execution request data includes, for example, the following information. · Player identification information assigned to the game application · Content of the visitor instruction assigned to the operation object B1110a or B1110b

[0152] [Game processing (S1150)] After step S1110, the game server 50 executes game processing. Specifically, the processor 32 executes the game according to the content of the visitor instruction included in the game execution request data. For example, when the content of the visitor instruction is "attack" (that is, the operation object B1110a is operated), the processor 52 calculates the damage amount and reduces the physical strength of the enemy character. For example, when the content of the visitor instruction is "use of game element" (that is, the operation object B1110b is operated), the processor 52 generates the effect of the game element to be used.

[0153] [Database update (S1151)] After step S1150, the game server 50 executes database update. Specifically, a game execution result database (not shown) is stored in the storage device 51. The game execution result database stores player identification information and game execution result information in association with each other. The game execution result information is information regarding the execution result of the game.

[0154] The processor 52 stores the player identification information included in the game execution request data and the game execution result information that is the execution result of step S1150 in the game execution result database in association with each other.

[0155] [Game execution response (S1152)] After step S1110, the game server 50 executes a game execution response. Specifically, the processor 52 transmits game execution response data to the client device 10. The game execution response data includes, for example, the following information. · Game execution result information that is the execution result of step S1150

[0156] [Presentation of Game Execution Results (S1111)] After step S1110, the client device 10 executes the presentation of the game execution results. Specifically, the processor 12 displays the screen P1111 (FIG. 7) on the display.

[0157] The screen P1111 displays a screen corresponding to the game execution result information included in the game execution response data. For example, when the content of the visitor instruction is "attack" (that is, the operation object B1110a is operated), the screen P1111 displays the damage amount and the remaining health of the enemy character. For example, when the content of the visitor instruction is "use of game element" (that is, the operation object B1110b is operated), the screen P1111 displays the efficacy of the used game element.

[0158] (4-3) Recommendation (OP2) The recommendation process of this embodiment will be described. FIG. 11 is a sequence diagram of the game execution process of this embodiment. FIG. 12 is a diagram showing an example of a screen displayed in the information processing of FIG. 11.

[0159] The trigger for the information processing in FIG. 11 is, for example, that the visitor performs an operation for instructing the activation of the browser application installed in the client device 10.

[0160] [Request for Hint Information (S1210)] As shown in FIG. 11, the client device 10 executes a request for hint information. Specifically, when the visitor performs an operation for instructing access to a walkthrough site (for example, input of an arbitrary search keyword and designation of a walkthrough site URL displayed as a search result), and an operation for logging in to the walkthrough site (for example, input of visitor identification information), the processor 12 transmits hint information request data to the walkthrough site server 30. The walkthrough information presentation request data includes, for example, the following information. · Visitor identification information entered by the visitor · Search key information (at least one of text and image) entered by the visitor · Walkthrough site URL specified by the visitor

[0161] [Database update (S1230)] After step S1210, the walkthrough site server 30 executes a database update (S1230). Specifically, the processor 32 stores the following information in each field of the access log database associated with the visitor identification information included in the walkthrough information presentation request data. · "Timestamp" field... Information regarding the execution date and time of step S1230 · "Siloe URL" field... The walkthrough site URL included in the walkthrough information presentation request data · "Search keyword" field... The search keyword included in the walkthrough information presentation request data

[0162] [Specification of walkthrough information (S1231)] After step S1230, the walkthrough site server 30 executes the specification of walkthrough information. Specifically, the processor 32 specifies the walkthrough information associated with the walkthrough site URL included in the walkthrough information presentation request data.

[0163] [Generation of recommendation information (S1232)] After step S1231, the walkthrough site server 30 executes the generation of recommendation information.

[0164] The first example of the recommendation model in step S1232 is configured to output game element information (an example of "recommendation information") regarding game elements recommended for game walkthroughs based on the combination of the visitor's possessed element information and the walkthrough information.

[0165] Processor 32 inputs the game element information stored in the “game element” field of the visitor game database associated with the visitor identification information included in the strategy information presentation request data and the strategy information identified in step S1231 into the recommendation model. The recommendation model outputs game element information recommended for conquering the game based on a combination of the game element information and the strategy information. The output game element information includes, for example, information on at least one of the following: -Game elements that are missing in the game Events that should be carried out to acquire missing game elements A package of game elements that you should purchase to acquire missing game elements for the game strategy Recommended game elements for strengthening or developing game elements recommended for game strategy Events that should be carried out to strengthen or develop game elements recommended for game strategy

[0166] According to the first example of step S1232, optimal game elements for the visitor are recommended based on a combination of the visitor's possessed element information and strategy information. This allows the visitor to smoothly progress through the game.

[0167] The second example recommendation model in step S1232 is configured to output new strategy information (an example of "recommended information") recommended for winning a game, based on a combination of the visitor's possessed element information and strategy information.

[0168] Processor 32 inputs the game element information stored in the “game element” field of the visitor game database and the strategy information identified in step S1231 into the recommendation model. The recommendation model outputs new strategy information recommended for conquering the game based on a combination of the game element information and the strategy information. The new strategy information includes, for example, at least one of the following: - URL information of strategy sites (i.e., URLs of strategy information recommended for visitors) - Information on recommended game elements for game strategy - Player deck information recommended for game strategies

[0169] According to the second example of step S1232, optimal strategy information for the visitor is recommended from a combination of the visitor's possessed element information and strategy information. This allows the visitor to smoothly progress through the game.

[0170] The third example recommendation model in step S1232 is configured to output strategy information (an example of "recommended information") recommended for winning the game, based on a combination of the visitor's game progress and the strategy information.

[0171] Processor 32 inputs the game performance information (eg, information on the progress of the quest) stored in the "game performance" field of the visitor game database and the walkthrough information identified in step S1231 into the recommendation model. The recommendation model outputs new strategy information recommended for conquering the game based on a combination of the game performance information and the strategy information. The new strategy information includes, for example, at least one of the following: - URL information of strategy sites (i.e., URLs of strategy information recommended for visitors) - Information about the next recommended quest Information about events recommended for gameplay - Player deck information recommended for game strategies

[0172] According to the third example of step S1232, optimal strategy information for the visitor is recommended from the combination of information on the progress of the visitor's quest and strategy information. As a result, the visitor can smoothly clear the game.

[0173] The recommendation model of the fourth example of step S1232 is configured to output strategy information (an example of "recommended information") recommended for clearing the game based on the combination of the progress of the visitor's game, strategy information, and search key information.

[0174] The processor 32 inputs the game score information (for example, information on the progress of the quest) stored in the "game score" field of the visitor game database, the strategy information identified in step S1231, and the search key information included in the strategy information presentation request data into the recommendation model. Based on the combination of the game score information, the strategy information, and the search key information, the recommendation model outputs new strategy information recommended for clearing the game. The new strategy information includes, for example, at least one of the following. · The strength of the enemy character the visitor wants to know about · The strategy article the visitor should read

[0175] According to the fourth example of step S1232, optimal strategy information for the visitor is recommended from the combination of information on the progress of the visitor's quest, strategy information, and search key information. As a result, the visitor can smoothly clear the game.

[0176] [Strategy Information Presentation Response (S1233)] After step S1232, the strategy site server 30 transmits strategy information presentation response data to the client device 10. The strategy information presentation response data includes, for example, the following information. · The strategy information identified in step S1231 The recommendation information generated in step S1232

[0177] [Suggestion of strategy information (S1211)] After step S1233, the client device 10 executes the presentation of the strategy information. Specifically, the processor 12 displays screen P1210 (FIG. 14) on the display.

[0178] Screen P1210 includes display object A1210.

[0179] The display object A 1210 is an object that displays strategy information.

[0180] (5) Summary of the present embodiment According to this embodiment, recommendation information is generated based on visitor game information of a visitor to a strategy site and the strategy information of the strategy site visited by the visitor. This makes it possible to provide the visitor with information that is useful for winning the game.

[0181] (6) Variations A modified example will now be described.

[0182] (6-1) Variation 1 A description will now be given of Modification 1. Modification 1 is an example in which visitor behavior is analyzed.

[0183] (6-1-1) Overview of Modification 1 An overview of Modification 1 will be described below. Fig. 13 is an explanatory diagram of an overview of Modification 1.

[0184] As shown in FIG. 13, the client device 10 transmits a strategy information presentation request to the strategy site server 30 in the same manner as in FIG.

[0185] The walkthrough site server 30 analyzes the visitor's behavior based on the visit log information of the visitor. The visitor's behavior is the play style of the visitor in the game. The play style depends on the visitor's motivation for playing the game. The play style includes, for example, at least one of the following styles. · A style that prioritizes the shortest possible completion of the game · A style that prioritizes the cultivation of game elements (e.g., characters and items) · A style that prioritizes the collection of game elements · A style that prioritizes interaction with friends

[0186] Based on the visitor game information, the walkthrough information corresponding to the walkthrough information presentation request, and the analysis result of the visitor's actions, the walkthrough site server 30 generates recommendation information. The walkthrough site server 30 transmits the recommendation information to the client device 10.

[0187] (6-1-2) Recommendation of Modification Example 1 The recommendation of Modification Example 1 will be described. FIG. 14 is a sequence diagram of the recommendation of Modification Example 1.

[0188] The trigger for the information processing in FIG. 14 is the same as that in FIG. 11.

[0189] [Walkthrough Information Presentation Request (S1210)] As shown in FIG. 14, the client device 10 executes a walkthrough information presentation request in the same manner as in FIG. 11.

[0190] [Game Score Request (S1230)] After step S1210, the walkthrough site server 30 executes a game score request in the same manner as in FIG. 11.

[0191] [Database Update (S1230)] After step S1210, the walkthrough site server 30 executes a database update (S1230) in the same manner as in FIG. 11.

[0192] [Analysis of Visitor Behavior (S2130)] After step S1230, the exploit site server 30 performs an analysis of the visitor's behavior. Specifically, the storage device 31 stores an analytical model. The analysis model is configured to output the play style of the visitor as an analysis result based on a combination of the visitor's possessed element information and visit log information.

[0193] The processor 32 refers to the visit log database associated with the visitor identification information included in the strategy information submission request data, and identifies the visit log information of the visitor. The processor 32 inputs the game element information stored in the “game element” field of the visitor game database associated with the visitor identification information included in the strategy information presentation request data and the identified visit log information into the analysis model. The analysis model generates play style information (an example of an "analysis result of visitor behavior") based on a combination of the game element information and the visit log information. The play style information is information related to the play style of the visitor.

[0194] [Generation of recommendation information (S2131)] After step S2130, the strategy site server 30 executes generation of recommendation information. Specifically, the recommendation model of the first modification outputs game element information (an example of "recommended information") recommended for conquering a game, based on a combination of play style information and strategy information.

[0195] [Strategy information presentation response (S1233)] After step S2130, the strategy site server 30 executes a strategy information presentation response in the same manner as in FIG.

[0196] [Suggestion of strategy information (S1211)] After step S1233, the client device 10 executes presentation of strategy information in the same manner as in FIG.

[0197] (6-1-3) Variation Example 1 Parentheses According to Variation Example 1, the recommendation information optimal for the playing style of the visitor is presented from the combination of the visitor game information and the visit log information of the visitor. As a result, the visitor can smoothly overcome the game along their confident playing style.

[0198] (6-2) Variation Example 2 Variation Example 2 will be described. Variation Example 2 is an example of generating recommendation information by referring to the visitor game information of the visitor and the visitor game information of other visitors similar to the visitor.

[0199] (6-2-1) Outline of Variation Example 2 The outline of Variation Example 2 will be described. FIG. 15 is an explanatory diagram of the outline of Variation Example 2.

[0200] As shown in FIG. 15, the client device 10, similar to FIG. 3, transmits a strategy information presentation request to the strategy site server 30.

[0201] The strategy site server 30 generates recommendation information based on the visitor game information of the visitor (hereinafter referred to as the "target visitor") for whom the recommendation information is to be presented, the strategy information corresponding to the strategy information presentation request, and the visitor game information of visitors similar to the target visitor (hereinafter referred to as "similar visitors"). The strategy site server 30 transmits the recommendation information to the client device 10.

[0202] (6-2-2) Recommendations of Variation Example 2 The recommendations of Variation Example 2 will be described. FIG. 16 is a sequence diagram of the recommendations of Variation Example 2.

[0203] The trigger for the process in FIG. 16 is the same as in FIG. 11.

[0204] [Strategy Information Presentation Request (S1210)] As shown in FIG. 16, the client device 10 executes a conquest information presentation request, similar to FIG. 11.

[0205] [Database Update (S1230) - Conquest Information Identification (S1231)] After step S1210, the conquest site server 30 executes database update (S1230) - conquest information identification (S1231), similar to FIG. 11.

[0206] [Similar Visitor Determination (S3130)] After step S1231, the conquest site server 30 executes a similar visitor determination. Specifically, a similar visitor determination model is stored in the storage device 31. The similar visitor determination model is configured to output visitor identification information of a similar visitor based on a combination of the visitor game information of the target visitor and the visitor game information of visitors other than the target visitor. The visitor game information includes, for example, at least one of the following. · Information regarding the play time of the game (as an example, the number of play days or the continuous play time) · Game element parameter information of the possessed elements · Player deck information · Visitor preference information described later (as an example, information regarding the preference for game elements) · Game element name information of the possessed elements · Information regarding the usage frequency of the possessed elements (as an example, the number of uses, the usage time, or the equipped time) · Information regarding the tags assigned to the possessed elements (as an example, favorite registration or a lock for prohibiting deletion)

[0207] The processor 32 inputs the visitor game information of the target visitor to the similar visitor determination model. The similar visitor determination model determines a similar visitor based on a combination of the visitor game information of the target visitor and the visitor game information of other visitors, and outputs the visitor identification information of the similar visitor.

[0208] [Generation of Recommendation Information (S3131)] After step S3130, the walkthrough site server 30 executes the generation of recommendation information.

[0209] The recommendation model in the first example of step S3131 outputs game element information (an example of "recommendation information") recommended for game walkthrough based on a combination of the visitor's game information (for example, the visitor's owned element information), the game information of similar visitors (for example, the owned element information of similar visitors), and the walkthrough information. The processor 32 identifies the owned element information (hereinafter referred to as "first owned element information") stored in the "owned element" field of the visitor game database associated with the visitor identification information of the target visitor. The processor 32 identifies the owned element information (hereinafter referred to as "second owned element information") stored in the "owned element" field of the visitor game database associated with the visitor identification information of the similar visitors determined in step S3130. The processor 32 inputs the first owned element information, the second owned element information, and the walkthrough information identified in step S1231 into the recommendation model. The recommendation model outputs game element information (an example of "recommendation information") recommended for game walkthrough based on a combination of the first owned element information, the second owned element information, and the walkthrough information. The output game element information includes information related to at least one of the following, for example. · Game elements lacking in game walkthrough · Events to be executed for obtaining game elements lacking in game walkthrough · Game element packages to be purchased for obtaining game elements lacking in game walkthrough · Game elements recommended for strengthening or cultivating game elements recommended for game walkthrough · Events to be executed for strengthening or cultivating game elements recommended for game clearance

[0210] The recommendation model of the second example in step S3131 outputs deck information (an example of "recommendation information") recommended for game clearance based on a combination of the visitor game information of the visitor (for example, the player deck information of the visitor), the visitor game information of similar visitors (for example, the player deck information of similar visitors), and clearance information. The processor 32 identifies the player deck information (hereinafter referred to as "first player deck information") stored in the "player deck" field of the visitor game database associated with the visitor identification information of the target visitor. The processor 32 identifies the player deck information (hereinafter referred to as "second player deck information") stored in the "player deck" field of the visitor game database associated with the visitor identification information of the similar visitors determined in step S3130. The processor 32 inputs the first player deck information, the second player deck information, and the clearance information identified in step S1231 into the recommendation model. The recommendation model outputs deck information (an example of "recommendation information") recommended for game clearance based on a combination of the first player deck information, the second player deck information, and the clearance information. The output deck information includes information regarding at least one of the following, for example. · Combinations of in-game characters recommended for game clearance · Combinations of in-game items recommended for game clearance

[0211] [Clearance information presentation response (S1233)] After step S3131, the clearance site server 30 executes a clearance information presentation response as shown in FIG. 11.

[0212] [Presentation of clearance information (S1211)] After step S1233, the client device 10 executes the presentation of the conquest information as in FIG. 11.

[0213] (6-2-3) Parentheses in Modification Example 2 According to Modification Example 2, the optimal recommendation information for the visitor is presented from the combination of the visitor game information of the target visitor, the conquest information, and the visitor game information of similar visitors. Thereby, the target visitor can smoothly conquer the game. For example, by referring to the visitor game information of a similar visitor whose game progress is faster than that of the target visitor (that is, a player who serves as a model for the target visitor), recommendation information based on the actions in the game of the similar visitor is presented to the target visitor. Thereby, the target visitor can determine the next action in the game of the target visitor with reference to the recommendation information based on the actions in the game of the similar visitor (as an example, the enhancement of the game elements performed by the similar visitor or the clearance of the quest).

[0214] (6-3) Modification Example 3 Modification Example 3 will be described. Modification Example 3 is an example of generating recommendation information by referring to the visitor game information and the location information of the visitor.

[0215] (6-3-1) Outline of Modification Example 3 The outline of Modification Example 3 will be described. FIG. 17 is an explanatory diagram of the outline of Modification Example 3.

[0216] As shown in FIG. 17, the conquest site server 30 stores the conquest information, the visitor game information, and the location information of the visitor.

[0217] The client device 10 transmits a conquest information presentation request to the conquest site server 30 as in FIG. 3.

[0218] The conquest site server 30 generates recommendation information based on the visitor game information of the visitor, the conquest information corresponding to the conquest information presentation request, and the location information of the visitor. The guidance site server 30 transmits the recommendation information to the client device 10.

[0219] (6-3-2) Recommendation of Modification Example 3 The recommendation of Modification Example 3 will be described. FIG. 18 is a sequence diagram of the recommendation of Modification Example 3.

[0220] The trigger for the process in FIG. 18 is the same as that in FIG. 11.

[0221] [Request for presenting guidance information (S1210)] As shown in FIG. 18, the client device 10 executes a request for presenting guidance information in the same manner as in FIG. 11.

[0222] [Update of database (S1230) - Identification of guidance information (S1231)] After step S1210, the guidance site server 30 executes an update of the database (S1230) - identification of guidance information (S1231) in the same manner as in FIG. 11.

[0223] [Identification of current location (S4130)] After step S1231, the guidance site server 30 executes identification of location information. Specifically, the processor 32 identifies a record in the location log database associated with the visitor identification information included in the guidance information presentation request data, in which the latest timestamp information is stored in the "timestamp field". The processor 32 identifies the location information stored in the "location" field of the identified record.

[0224] [Generation of recommendation information (S4131)] After step S4130, the guidance site server 30 executes generation of recommendation information.

[0225] The recommendation model of the first example in step S4130 outputs game element information (an example of "recommendation information") regarding game elements recommended for game clearance based on a combination of the visitor's visitor game information (for example, owned element information), the visitor's location information, and clearance information. The processor 32 identifies the owned element information stored in the "owned elements" field of the visitor game database associated with the visitor identification information included in the clearance information presentation request data. The processor 32 inputs the owned element information of the visitor, the location information of the visitor identified in step S4130, and the clearance information identified in step S1231 into the recommendation model. Based on a combination of the owned element information of the visitor, the location information of the visitor, and the clearance information, the recommendation model outputs game element information (an example of "recommendation information") recommended for game clearance. · A game element lacking for game clearance and obtainable at the visitor's current location · An event to be executed for obtaining a game element lacking for game clearance and executable at the visitor's current location · A package of game elements to be purchased for obtaining a game element lacking for game clearance and purchasable at the visitor's current location · A game element recommended for strengthening or cultivating a game element recommended for game clearance and capable of being strengthened or cultivated at the visitor's current location · An event to be executed for strengthening or cultivating a game element recommended for game clearance and executable at the visitor's current location

[0226] The recommendation model in the second example of step S4130 outputs recommended position information (an example of "recommendation information") regarding positions recommended for game clearance based on a combination of the visitor's visitor game information (for example, possession element information), the visitor's position information, and the clearance information. The processor 32 identifies the possession element information stored in the "possession element" field of the visitor game database associated with the visitor identification information included in the clearance information presentation request data. The processor 32 inputs the possession element information of the visitor, the position information of the visitor identified in step S4130, and the clearance information identified in step S1231 into the recommendation model. Based on a combination of the possession element information of the visitor, the position information of the visitor, and the clearance information, the recommendation model outputs recommended position information (an example of "recommendation information") recommended for game clearance. · A position where a game element lacking for game clearance can be obtained, a movement route to the position, or a circuit route · A position where an event to be executed for obtaining a game element lacking for game clearance can be executed, a movement route to the position, or a circuit route · A position where a package of game elements to be purchased for obtaining a game element lacking for game clearance can be purchased, a movement route to the position, or a circuit route · A position where enhancement or cultivation of a game element recommended for game clearance is possible, a movement route to the position, or a circuit route · A position where an event to be executed for enhancement or cultivation of a game element recommended for game clearance can be executed, a movement route to the position, or a circuit route

[0227] The recommendation model in the third example of step S4130 outputs other player's player information (an example of "recommendation information") recommended for game clearance based on a combination of the visitor's visitor game information (for example, possession element information), the visitor's position information, and the clearance information. The processor 32 identifies the item information stored in the "Owned Items" field of the visitor game database associated with the visitor identification information included in the conquest information presentation request data.

[0228] The processor 32 identifies the visitor identification information (hereinafter referred to as "nearby visitor identification information") of visitors (hereinafter referred to as "nearby visitors") who are within a predetermined range from the current location of the visitor. A nearby visitor is, for example, another visitor who satisfies at least one of the following conditions. · Being at a position within a predetermined distance from the current location of the visitor · The nearest landmark (e.g., a station) from the current location of the visitor is the nearest landmark. · The landmark adjacent to the nearest landmark (e.g., a station) from the current location of the visitor is the nearest landmark.

[0229] The processor 32 inputs the item information of the visitor, the location information of the visitor identified in step S4130, and the conquest information identified in step S1231 into the recommendation model. Based on the combination of the item information of the visitor, the location information of the visitor, and the conquest information, the recommendation model outputs player identification information (an example of "recommendation information") associated with the nearby visitor identification information of the nearby visitor recommended for the conquest of the game from among the nearby visitor identification information. The output player identification information is, for example, at least one of the following. · Player identification information of a player who has game elements lacking for the conquest of the game · Player identification information of a player who should be friend-registered for obtaining game elements lacking for the conquest of the game · Player identification information of a player who should be friend-registered for strengthening or cultivating game elements recommended for the conquest of the game · Player identification information of a player for whom cooperation is recommended for achieving a quest

[0230] The recommendation model in the fourth example of step S4130 outputs friend player identification information (an example of "recommendation information") of a friend recommended for game clearance based on a combination of the visitor's visitor game information (for example, possession element information and friend identification information), the visitor's location information, and clearance information. The processor 32 identifies the possession element information stored in the "possession element" field of the visitor game database associated with the visitor identification information included in the clearance information presentation request data, and the friend player identification information stored in the "friend" field. The processor 32 identifies neighboring visitor identification information in the same manner as in the third example of step S4130. The processor 32 identifies player identification information (hereinafter referred to as "neighboring friend player identification information") that matches the friend player identification information from among the player identification information associated with the neighboring visitor identification information. The processor 32 inputs the possession element information of the visitor, the neighboring friend player identification information, the location information of the visitor identified in step S4130, and the clearance information identified in step S1231 into the recommendation model. The recommendation model outputs player identification information (an example of "recommendation information") of a player recommended for game clearance from among the neighboring friend player identification information based on a combination of the possession element information of the visitor, the location information of the visitor, and the clearance information. The output player identification information is, for example, at least one of the following. · Player identification information of a friend who has a game element lacking for game clearance · Player identification information of a friend for whom cooperation is recommended for quest completion

[0231] [Clearance Information Presentation Response (S1233)] After step S4131, the clearance site server 30 executes a clearance information presentation response in the same manner as in FIG. 11.

[0232] [Suggestion of strategy information (S1211)] After step S1233, the client device 10 executes presentation of strategy information in the same manner as in FIG.

[0233] (6-3-3) Summary of Variation 3 According to the third modification, optimal recommendation information for a visitor is presented based on a combination of the visitor's game information, strategy information, and location information of the visitor. This allows the visitor to smoothly progress through the game.

[0234] (6-4) Variation 4 A description will be given of Modification 4. Modification 4 is an example in which recommendation information is generated by referring to the visitor game information of the visitor and the content posted by the visitor.

[0235] (6-4-1) Overview of Variation 4 An overview of Modification 4 will be described below. Fig. 19 is an explanatory diagram of an overview of Modification 4.

[0236] As shown in FIG. 19, the strategy site server 30 stores strategy information, visitor game information, and posted content information.

[0237] The client device 10 transmits a strategy information presentation request to the strategy site server 30 in the same manner as in FIG.

[0238] The walkthrough site server 30 analyzes the visitor's preferences based on the visitor's posted content information. The visitor's preferences are the games that the visitor is interested in and the degree of the interest. The strategy site server 30 generates recommendation information based on the visitor's game information, the strategy information corresponding to the strategy information presentation request, and the analysis result of the visitor's preferences. The walkthrough site server 30 transmits the recommendation information to the client device 10.

[0239] (6-4-2) Recommendation for Variation 4 A description will now be given of recommendation according to Modification 4. FIG 20 is a sequence diagram of recommendation according to Modification 4.

[0240] The trigger for the process in FIG. 20 is the same as in FIG.

[0241] [Request for strategy information (S1210)] As shown in FIG. 20, the client device 10 executes a strategy information presentation request in the same manner as in FIG.

[0242] [Database update (S1230) ~ Identifying strategy information (S1231)] After step S1210, the strategy site server 30 executes the processes of updating the database (S1230) to identifying strategy information (S1231), similar to those in FIG.

[0243] [Analysis of Visitor Preferences (S5130)] After step S1231, the capture site server 30 performs an analysis of the visitor's preferences. Specifically, the storage device 31 stores a preference determination model.

[0244] The first example preference determination model in step S5130 outputs visitor preference information based on the latest posted content information. The processor 32 refers to the posting log database associated with the visitor identification information included in the strategy information presentation request data, and identifies the posting content information associated with the strategy site URL included in the strategy information presentation request data. The processor 32 inputs the identified post content information into the preference determination model. The preference determination model outputs visitor preference information based on the posted content information. The visitor preference information is, for example, information regarding the subject of interest of the visitor and the level of interest at the time of posting by the visitor.

[0245] The preference determination model of the second example in step S5130 outputs visitor preference information based on the post content information included in the post log information for a predetermined period. The processor 32 refers to the post log database associated with the visitor identification information included in the walkthrough information presentation request data, and among the post content information associated with the walkthrough site URL included in the walkthrough information presentation request data, identifies a plurality of pieces of post content information in which the timestamp information in the "timestamp" field is included within a predetermined period from the execution date and time of step S5130. The processor 32 inputs the identified plurality of pieces of post content information into the preference determination model. The preference determination model outputs visitor preference information based on the plurality of pieces of post content information. The visitor preference information is, for example, information regarding the object of the visitor's interest and changes in the degree of the interest.

[0246] [Generation of recommendation information (S5131)] After step S5130, the walkthrough site server 30 executes generation of recommendation information. Specifically, the recommendation model of Modification Example 4 outputs game element information (an example of "recommendation information") recommended for game walkthrough based on a combination of the visitor's visitor game information, walkthrough information, and visitor preference information. The processor 32 identifies game achievement information (as an example, information regarding the progress of the visitor's quests) stored in the "game achievement" field of the visitor game database associated with the visitor identification information included in the walkthrough information presentation request data. The processor 32 inputs the game achievement information determined in step S3130, the visitor preference information obtained in step S5130, and the walkthrough information identified in step S1231 into the recommendation model. The recommendation model outputs game element information (an example of "recommendation information") recommended for game walkthrough based on a combination of the game achievement information of the visitor, the walkthrough information, and the visitor preference information. The output game element information includes, for example, information regarding at least one of the following. · Game elements preferred by the visitor · Events through which the game elements preferred by the visitor can be obtained

[0247] [Strategy information presentation response (S1233)] After step S5131, the strategy site server 30 executes a strategy information presentation response, as shown in FIG. 11.

[0248] [Presentation of strategy information (S1211)] After step S1233, the client device 10 executes the presentation of strategy information, as shown in FIG. 11.

[0249] (6-4-3) Parentheses in Modification Example 4 According to Modification Example 4, visitor preference information is generated from the visitor's posted content information, and the optimal recommendation information for the visitor is presented from the combination of the visitor's game information, strategy information, and visitor preference information. Therefore, recommendation information corresponding to the preferences of the visitor that cannot be specified only by the history of the strategy sites visited by the visitor (for example, meta tag information) is presented. Thereby, the visitor can smoothly clear the game.

[0250] (6-6) Modification Example 5 Modification Example 5 will be described. Modification Example 5 is an example in which recommendation information is generated with reference to the visitor's game information, visitor preference information, and inventory information.

[0251] (6-5-1) Outline of Modification Example 5 The outline of Modification Example 5 will be described. FIG. 21 is an explanatory diagram of the outline of Modification Example 5.

[0252] As shown in FIG. 21, the strategy site server 30 stores strategy information, visitor game information, and the visitor's purchase log information.

[0253] The client device 10 transmits a conquest information presentation request to the conquest site server 30, similar to FIG. 3.

[0254] The conquest site server 30 analyzes the visitor preferences based on the purchase log information of the visitors. The visitor preferences are goods that are the objects of the visitors' interests or concerns, and the degree of such interests or concerns. The conquest site server 30 generates recommendation information, similar to FIG. 19. The conquest site server 30 transmits the recommendation information to the client device 10.

[0255] (6-5-2) Recommendation of Modification Example 5 The recommendation of Modification Example 5 will be described. FIG. 22 is a sequence diagram of the recommendation of Modification Example 5.

[0256] The trigger for the process in FIG. 22 is the same as that in FIG. 11.

[0257] [Conquest Information Presentation Request (S1210)] As shown in FIG. 22, the client device 10 executes a conquest information presentation request, similar to FIG. 11.

[0258] [Database Update (S1230) - Conquest Information Identification (S1231)] After step S1210, the conquest site server 30 executes database update (S1230) - conquest information identification (S1231), similar to FIG. 11.

[0259] [Visitor Preference Analysis (S6130)] After step S1231, the conquest site server 30 executes visitor preference analysis. Specifically, a preference determination model is stored in the storage device 31.

[0260] The preference determination model in the first example of step S6130 outputs visitor preference information based on game identification information corresponding to the purchase log information of the visitors. The processor 32 refers to the "timestamp" field and the "goods ID" of the purchase log database associated with the visitor identification information included in the conquest information presentation request data, and identifies the goods identification information of the goods purchased by the visitor within a predetermined period (for example, one year back from the execution date and time of step S6130). The processor 32 refers to the goods database and identifies the game identification information associated with the identified goods identification information. The game identification information is information that identifies a game related to the goods that the visitor favorably purchased within a predetermined period. The processor 32 inputs the identified game identification information into the preference determination model. Based on the game identification information, the preference determination model outputs game identification information different from the game identification information (an example of "visitor preference information"). The output game identification information is, for example, information that identifies a game that the visitor prefers and that the visitor does not have player identification information for (that is, a game that the visitor has not played).

[0261] The preference determination model in the second example of step S6130 outputs visitor preference information based on the visitor's purchase log information. The processor 32 refers to the "timestamp" field and the "goods ID" of the purchase log database associated with the visitor identification information included in the conquest information presentation request data, and identifies the goods identification information of the goods purchased by the visitor within a predetermined period (for example, one year back from the execution date and time of step S6130). The processor 32 inputs the identified goods identification information into the preference determination model. Based on the goods identification information, the preference determination model outputs goods identification information different from the goods identification information (an example of "visitor preference information"). The output goods identification information is, for example, information that identifies goods that the visitor prefers and that the visitor does not own.

[0262] The preference determination model of the third example in step S6130 outputs visitor preference information based on the purchase log information and inventory information of the visitor. Similar to the second example in step S6130, the processor 32 outputs goods identification information different from the goods identification information. The processor 32 refers to the "Inventory" field of the goods database to identify the inventory information associated with the output goods identification information. When the identified inventory information meets a predetermined condition, the processor 32 outputs the goods identification information (an example of "visitor preference information") associated with the inventory information that meets the predetermined condition. The predetermined condition is, for example, at least one of the following. · The inventory quantity is equal to or more than a predetermined number (as an example, 1). · The scheduled arrival date is within a predetermined number of days from the execution date of step S6130. The output goods identification information is, for example, information that identifies goods that the visitor prefers, that the visitor does not own, and that are recommended to the visitor from the perspective of inventory (as an example, goods that can be obtained within a certain period of time since the visitor visited the conquest site).

[0263] [Generation of Recommendation Information (S6131)] After step S6130, the conquest site server 30 executes the generation of recommendation information. Specifically, the recommendation model of Modification Example 5 outputs recommendation information (for example, goods information of goods recommended to the visitor) based on the combination of the visitor's visitor game information, conquest information, visitor preference information, and goods information. The processor 32 identifies the game achievement information (as an example, information regarding the progress of the visitor's quests) stored in the "Game Achievements" field of the visitor game database associated with the visitor identification information included in the conquest information presentation request data. The processor 32 inputs the game score information determined in step S3130, the strategy information specified in step S1231, the visitor preference information obtained in step S5130, and the item information stored in the item database into the recommendation model. Based on the combination of the visitor's game information, the strategy information, the visitor preference information, and the item information, the recommendation model outputs item information (an example of "recommendation information") recommended from the perspective of the visitor's preferences. The output item information includes information on at least one of the following, for example. · Information on the sales schedule of items related to the games preferred by the visitor · Inventory information of items related to the games preferred by the visitor · Information on the sales schedule of items according to changes in the visitor's preferences · Inventory information of items according to changes in the visitor's preferences

[0264] [Strategy Information Presentation Response (S1233)] After step S6131, the strategy site server 30 executes a strategy information presentation response as in FIG. 11.

[0265] [Presentation of Strategy Information (S1211)] After step S1233, the client device 10 executes the presentation of strategy information as in FIG. 11.

[0266] (6-5-3) Parentheses in Modification Example 5 According to Modification Example 5, visitor preference information is generated from the visitor's posted content information, and optimal recommendation information for the visitor is presented from the combination of the visitor's game information, strategy information, visitor preference information, and item information. Therefore, recommendation information according to the visitor's preferences that cannot be specified only by the history of the strategy sites visited by the visitor (for example, meta tag information) is presented. Thereby, it is possible to recommend to the visitor to obtain items according to their confident preferences.

[0267] (6-6) Variant Example 6 Variant Example 6 will be described. Variant Example 6 is an example of generating recommendation information by referring to the visitor game information and healthcare information of the visitor.

[0268] (6-6-1) Outline of Variant Example 6 The outline of Variant Example 6 will be described. FIG. 23 is an explanatory diagram of the outline of Variant Example 6.

[0269] As shown in FIG. 23, the walkthrough site server 30 stores walkthrough information, visitor game information, and the visitor's healthcare information.

[0270] The client device 10, as in FIG. 3, sends a walkthrough information presentation request to the walkthrough site server 30.

[0271] The walkthrough site server 30 generates recommendation information based on the visitor game information, the walkthrough information corresponding to the walkthrough information presentation request, and the visitor's healthcare information. The walkthrough site server 30 sends the recommendation information to the client device 10.

[0272] (6-6-2) Recommendations of Variant Example 6 The recommendations of Variant Example 6 will be described. FIG. 24 is a sequence diagram of the recommendations of Variant Example 6.

[0273] The trigger for the process in FIG. 24 is the same as in FIG. 11.

[0274] [Walkthrough Information Presentation Request (S1210)] As shown in FIG. 24, the client device 10, as in FIG. 11, executes a walkthrough information presentation request.

[0275] [Database Update (S1230) ~ Specification of Walkthrough Information (S1231)] After step S1210, the walkthrough site server 30, as in FIG. 11, executes database update (S1230) ~ specification of walkthrough information (S1231).

[0276] [Specifying Healthcare Information (S7130)] After step S1231, the walkthrough site server 30 executes the specification of healthcare information. Specifically, the processor 32 identifies a record in the healthcare log database associated with the visitor identification information included in the walkthrough information presentation request data, in which the latest timestamp information is stored in the "timestamp field". The processor 32 identifies the healthcare information stored in the "location" field of the identified record.

[0277] [Generating Recommendation Information (S7131)] After step S7130, the walkthrough site server 30 executes the generation of recommendation information.

[0278] The recommendation model in the first example of step S7130 outputs game element information (an example of "recommendation information") regarding game elements recommended for clearing the game, based on a combination of the visitor's visitor game information (for example, the owned element information), the visitor's healthcare information, and the walkthrough information. The processor 32 identifies the owned element information stored in the "owned element" field of the visitor game database associated with the visitor identification information. The processor 32 inputs the owned element information of the visitor, the visitor's healthcare information identified in step S7130, and the walkthrough information identified in step S1231 into the recommendation model. The recommendation model outputs game element information (an example of "recommendation information") recommended for clearing the game, based on a combination of the owned element information of the visitor, the visitor's healthcare information, and the walkthrough information. · Game elements lacking for clearing the game and that can be obtained in the visitor's current healthcare information · An event to be executed for obtaining game elements that are lacking in game playthrough, and an event that can be executed based on the current healthcare information of the visitor · A package of game elements to be purchased for obtaining game elements that are lacking in game playthrough, and a package that can be purchased based on the current healthcare information of the visitor · A game element recommended for strengthening or cultivating game elements recommended for game playthrough, and a game element that can be strengthened or cultivated based on the current healthcare information of the visitor · An event to be executed for strengthening or cultivating game elements recommended for game playthrough, and an event that can be executed based on the current healthcare information of the visitor

[0279] [Walkthrough Information Presentation Response (S1233)] After step S7131, the walkthrough site server 30 executes a walkthrough information presentation response, as shown in FIG. 11.

[0280] [Presentation of Walkthrough Information (S1211)] After step S1233, the client device 10 executes the presentation of walkthrough information, as shown in FIG. 11.

[0281] (6-6-3) Parentheses in Modification Example 6 According to Modification Example 6, optimal recommendation information for the visitor is presented based on the combination of the visitor's game information, walkthrough information, and the visitor's healthcare information. As a result, the visitor can smoothly complete the game.

[0282] (7) Other Modification Examples Other modification examples will be described.

[0283] The storage device 11 may be connected to the client device 10 via the network NW. The storage device 31 may be connected to the walkthrough site server 30 via the network NW.

[0284] Each of the above models may be either a trained model (e.g., a large language model) or a rule-based model. In the case of a trained model, it may be either a model generated by supervised learning or a model generated by unsupervised learning.

[0285] As described above, the embodiments of the present invention have been described in detail, but the scope of the present invention is not limited to the above embodiments. Further, the above embodiments can be variously improved and modified without departing from the gist of the present invention. Also, the above embodiments and modifications can be combined.

Description of Reference Numerals

[0286] 1: Information processing system 10: Client device 11: Storage device 12: Processor 13: Input / output interface 14: Communication interface 30: Strategy site server 31: Storage device 32: Processor 33: Input / output interface 34: Communication interface 50: Game server 50: Storage means 50: Game server 51: Storage device 52: Processor 52: Control means 53: Input / output interface 54: Communication interface

Claims

1. An information processing method for presenting recommendation information recommended for game clearance to visitors of a clearance site that provides game clearance information, comprising: a computer executing a step of obtaining visitor game information regarding the game situation of the visitor; executing a step of generating recommendation information to be recommended to the visitor based on the visitor game information and the clearance information; An information processing method.

2. The visitor game information is game element information regarding game elements possessed by the visitor, The recommendation information is game element information regarding game elements recommended for game clearance, The information processing method according to Claim 1.

3. The visitor game information is game element information regarding game elements possessed by the visitor, The recommendation information is new clearance information recommended for game clearance, The information processing method according to Claim 1.

4. The visitor game information is information regarding the progress of the visitor's game, The recommendation information is new clearance information recommended for game clearance, The information processing method according to Claim 1.

5. The generating step generates the recommendation information based on the visitor game information, the clearance information, and search key information input by the visitor to visit the clearance site, The recommendation information is new clearance information recommended for game clearance, The information processing method according to Claim 1.

6. The generating step generates the recommendation information based on the visitor game information, the clearance information, and visitor game information of similar visitors similar to the visitor, The recommendation information is information recommended for game clearance, The information processing method according to Claim 1.

7. The generating step generates the recommendation information based on the visitor game information, the clearance information, and the position information of the visitor, The recommendation information is information recommended for game clearance, The information processing method according to Claim 1.

8. Comprising means for analyzing the preferences of the visitor based on the posted content information of the visitor, The generating step generates the recommendation information based on the visitor game information, the clearance information, and the analysis result of the visitor's preferences, The recommendation information is information recommended for the visitor to play a game according to his / her preferences. The information processing method according to claim 1 .

9. A means for analyzing the preferences of the visitor based on purchase log information of the visitor, The generating step generates the recommendation information based on the visitor game information, the strategy information, and an analysis result of the visitor's preferences, The recommendation information is recommendation information regarding goods according to the preferences of the visitor. The information processing method according to claim 1 .

10. A means for analyzing the behavior of the visitor based on visitor game information and visit log information of the visitor, the generating step generates the recommendation information based on the visitor game information, the strategy information, and an analysis result of the visitor's behavior; The recommendation information is information recommended for a game strategy according to the behavior of the visitor. The information processing method according to claim 1 .

11. A program for causing a computer to execute each of the steps recited in any one of claims 1 to 10.

12. An information processing device that presents recommendation information recommended for game strategy to a visitor of a strategy site that provides game strategy information, means for acquiring visitor game information relating to the status of the visitor's game; a means for generating recommendation information to be recommended to the visitor based on the visitor game information and the strategy information; Information processing device.

13. An information processing system including a client device and a server of a strategy site that provides strategy information for a game, The server, A means for acquiring visitor game information relating to the game status of a visitor to the strategy site, a means for generating recommendation information to be recommended to the visitor based on the visitor game information and the strategy information; The client device is provided with a means for presenting the recommendation information. Information processing system.

Images