Game version update prompting method and device, equipment and storage medium

Abstract

The embodiment of the invention discloses a game version update prompting method and device, equipment and a storage medium, and the method comprises the steps: obtaining a target request parameter of a target user, and analyzing the target request parameter based on a preset parameter category to determine a target parameter corresponding to each parameter category; performing condition adaptation on each target parameter according to a preset configuration recall rule to determine a plurality of target update configurations, and performing aggregation processing on the plurality of target update configurations to generate a structured configuration parameter; and determining a page template and an update link corresponding to a game port in the structured configuration parameters, filling the structured configuration parameters and the update link into the page template to generate a game update page, and pushing the game update page to the target user. And the touch conversion rate of the game version update prompt is improved.

Description

TECHNICAL FIELD

[0001] Embodiments of the present application relate to the technical field of computer, and particularly relate to a game version update prompting method and device, equipment and a storage medium. BACKGROUND

[0002] In the context of fast-paced game iteration, it is often necessary to update and upgrade the functions of the game and the levels of the game. On the one hand, it is to improve the overall game competitiveness and constantly improve the game ecology and user experience. On the other hand, for some new play and hot spot, the corresponding game version prompt information is generated and sent to the target user in time, and the update status of the target user is continuously followed up to ensure the competitiveness and advancement of the product.

[0003] In related technologies, when a game version update prompt is performed, the same game version update prompt information is usually pushed to all port users for the same version update. The version update prompt information cannot accurately match the actual needs of different user groups, resulting in a low conversion rate of game version update prompts. SUMMARY

[0004] Embodiments of the present application provide a game version update prompting method, device, equipment and storage medium, which solves the problem of low conversion efficiency of game version update prompts due to the inability of version update prompt information to accurately match the actual needs of different user groups. The target parameters are conditionally adapted according to the preset configuration recall rule to determine a plurality of target update configurations, which improves the matching accuracy of the update configurations and different user needs. The structured configuration parameters and update links are filled into the page template to generate a game update page, and the game update page is sent to the target user to prompt the target user to update the game version, thereby improving the conversion rate of game version update prompts.

[0005] In a first aspect, embodiments of the present application provide a game version update prompting method, comprising: obtaining a target request parameter of a target user, and analyzing the target request parameter based on a preset parameter category to determine a target parameter corresponding to each parameter category; conditionally adapting each target parameter according to a preset configuration recall rule to determine a plurality of target update configurations, and aggregating the plurality of target update configurations to generate structured configuration parameters; determining a page template and an update link corresponding to a game port in the structured configuration parameters, filling the structured configuration parameters and the update link into the page template to generate a game update page, and pushing the game update page to the target user.

[0006] Optionally, the step of determining multiple target update configurations by conditionally adapting each target parameter according to a preset configuration recall rule includes: Based on the preset first configuration recall rule, the target parameters are basically adapted to determine multiple basic update conditions. The basic update conditions are combined in multiple dimensions to obtain multiple combined conditions. Based on the preset second configuration recall rule, the combined conditions are adapted to the scenario. Based on the scenario adaptation result, multiple target update configurations are determined.

[0007] Optionally, the preset second configuration recall rule includes parameter label mapping rules and condition matching rules, and the scenario adaptation of each combination condition based on the preset second configuration recall rule includes: The combination condition label set corresponding to each combination condition is determined according to the parameter label mapping rule. The combination condition label set is compared with the multidimensional label corresponding to the condition matching rule. The scene label overlap rate is determined based on the comparison result. Scene adaptation is performed on each of the combined conditions based on the scene label overlap rate.

[0008] Optionally, the determination of multiple target update configurations based on the scenario adaptation results includes: Conflict identification is performed on the configuration information in the scenario adaptation results to determine multiple first target update configurations and / or conflicting configurations; The conflicting configurations are effectively filtered according to preset priority rules to obtain the second target update configuration.

[0009] Optionally, the parameter categories include basic identifier categories, environmental feature categories, and user attribute categories. The step of parsing the target request parameters based on preset parameter categories to determine the target parameters corresponding to each category includes: Determine the condition parameters corresponding to the basic identifier class, the environmental feature class, and the user attribute class respectively; The target request parameters are matched with the condition parameters to determine the target parameters corresponding to each parameter category, where different parameter categories correspond to different data dimensions.

[0010] Optionally, after sending the game update page to the target user, the method further includes: In response to the version update operation of the target user, the target configuration corresponding to the game port of the target user is executed, and the operation data of the version update operation is tracked to generate the game version update information of the target user.

[0011] Optionally, before obtaining the target user's target request parameters, the method further includes: Collecting a game request parameter in real time, identifying version information in the game request parameter, comparing the version information with local application version information, determining a version type of the user version information based on a comparison result, the version type including a to-be-updated version, a forced-updated version and a latest version; In a case where the version type is the to-be-updated version or the forced-updated version, the game request parameter is determined as a target request parameter of a target user.

[0012] In a second aspect, an embodiment of the present application provides a game version update prompting device, including: A target parameter determination module is configured to obtain a target request parameter of a target user, analyze the target request parameter based on a preset parameter category, and determine a target parameter corresponding to each parameter category; A structured configuration parameter generation module is configured to conditionally adapt each target parameter based on a preset configuration recall rule, determine a plurality of target update configurations, aggregate the plurality of target update configurations, and generate a structured configuration parameter; A game version update prompting module is configured to determine a page template and an update link corresponding to a game port in the structured configuration parameter, fill the structured configuration parameter and the update link into the page template to generate a game update page, and push the game update page to the target user.

[0013] In a third aspect, an embodiment of the present application provides an electronic device, including one or more processors, and a storage device configured to store one or more programs, when the one or more programs are executed by the one or more processors, the one or more processors implement the game version update prompting method in the first aspect.

[0014] In a fourth aspect, an embodiment of the present application provides a storage medium containing computer executable instructions, when the computer executable instructions are executed by a computer processor, the computer executable instructions are used to execute the game version update prompting method in the first aspect.

[0015] The embodiment of the application obtains a target request parameter of a target user, analyzes the target request parameter based on a preset parameter category to determine a target parameter corresponding to each parameter category, performs conditional adaptation on each target parameter according to a preset configuration recall rule to determine a plurality of target update configurations, aggregates the plurality of target update configurations to generate a structured configuration parameter, determines a page template and an update link corresponding to a game port in the structured configuration parameter, fills the structured configuration parameter and the update link into the page template to generate a game update page, and pushes the game update page to the target user. The plurality of target update configurations are determined by performing conditional adaptation on the target parameter according to the preset configuration recall rule, the matching precision of the update configuration and different user demands is improved, the game update page is generated by filling the structured configuration parameter and the update link into the page template, the game update page is sent to the target user to prompt the target user to update the game version, and the touch conversion rate of the game version update prompt is improved. BRIEF DESCRIPTION OF DRAWINGS

[0016] Figure 1 is a flowchart of a game version update prompt method provided by the embodiment of the application; Figure 2 is a schematic diagram of an update prompt page provided by the embodiment of the application; Figure 3 is a flowchart of a target update configuration determination method provided by the embodiment of the application; Figure 4 is a flowchart of a target update configuration determination method provided by the embodiment of the application; Figure 5 is a structural schematic diagram of a game version update prompt device provided by the embodiment of the application; Figure 6 is a structural schematic diagram of a game version update prompt device provided by the embodiment of the application. DETAILED DESCRIPTION

[0017] To make the objectives, technical solutions, and advantages of this application clearer, specific embodiments of this application will be described in further detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are merely for explaining this application and not for limiting it. It should also be noted that, for ease of description, only the parts relevant to this application are shown in the drawings, not all of them. Before discussing exemplary embodiments in more detail, it should be mentioned that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although the flowcharts describe operations (or steps) as sequential processes, many of these operations can be performed in parallel, concurrently, or simultaneously. Furthermore, the order of the operations can be rearranged. The process can be terminated when its operation is completed, but may also have additional steps not included in the drawings. The process can correspond to a method, function, procedure, subroutine, subprogram, etc.

[0018] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0019] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such use of data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," etc., are generally of the same class and the number of objects is not limited; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0020] The following description, in conjunction with the accompanying drawings, details the game version update notification method, apparatus, device, and medium provided in this application through specific embodiments and application scenarios.

[0021] The game version update notification method provided in this application is used by game operators to deliver version update information to users who have installed the game when the game client starts up, during operation, or through mobile / PC push channels. This guides users to complete the update and ensures that users experience new game features, bug fixes, or device environment adaptations using the latest version. Based on the above application scenarios, it is understood that the executing entity for each step can be a computer device. This computer device refers to any electronic device with data computing, processing, and storage capabilities, such as mobile phones, PCs (Personal Computers), tablets, and other terminal devices. It can also be a server or other similar device; this application does not limit this.

[0022] Figure 1 This is a flowchart of a game version update notification method provided in an embodiment of this application, such as... Figure 1 As shown, it includes: Step S101: Obtain the target request parameters of the target user, and parse the target request parameters based on the preset parameter categories to determine the target parameters corresponding to each parameter category.

[0023] The target user can be a user whose current game version is not the latest version. The target request parameters refer to the core set of parameters transmitted from the client to the server when a user logs into the game from different ports or triggers version-related operations. These parameters are used to accurately identify the user / device status and determine the scope and strategy of version updates. The target request parameters may include user and account identifier parameters, device and port attribute parameters, version status parameters, etc. The parameter category refers to a set of rules used to classify the target request parameters, so as to more accurately parse the specific values ​​corresponding to each type of parameter. The target parameter can refer to the specific parameter values ​​corresponding to each data dimension extracted from the target request parameters according to the preset parameter category. For example, when the parameter category includes a basic identifier class, the target parameter may include the user's unique identifier, account type, etc.

[0024] In one embodiment, the target request parameters of the game user whose current game version is not the most recent are obtained, the parsing dimensions of the target request parameters are determined according to the preset parameter categories, and the target parameters corresponding to each dimension are extracted.

[0025] Step S102: Based on the preset configuration recall rules, perform conditional adaptation on each target parameter to determine multiple target update configurations, and aggregate the multiple target update configurations to generate structured configuration parameters.

[0026] The preset configuration recall rules refer to the precise association rules between different target parameters and corresponding version update configurations defined in advance in the system, such as the association rules between different port identifiers and corresponding version update protocols. The target update configuration is the configuration associated with each target parameter determined based on the preset configuration recall rules, and may include version update protocols, update benefits / packages, and new feature descriptions. Aggregation processing refers to integrating scattered target update configurations, removing redundant or conflicting parts, and ultimately generating a structured configuration parameter. A structured configuration parameter can refer to a set of configuration information with a clear data structure and semantics, which can accurately reflect the request parameters corresponding to different configuration types. For example, the request parameters corresponding to a version protocol may include protocol ID, port used, operating system, etc., while the request parameters corresponding to an update benefit package may include package ID, applicable user level, payment type, and port, etc.

[0027] In one embodiment, after determining each target parameter, the target update configuration associated with each target parameter is determined according to the preset configuration recall rules. That is, the configuration information such as the version update protocol, update package size, and expected update time suitable for the target user is determined, and this information is aggregated into a set of structured configuration parameters.

[0028] Step S103: Determine the page template and update link corresponding to the game port in the structured configuration parameters, fill the structured configuration parameters and update link into the page template to generate the game update page, and push it to the target user.

[0029] In this context, "game portal" refers to the entry point for users to access the game, such as native apps, H5 games, PC platforms, mini-games, and channel packages. Different game portals may require different page templates to display version update information to ensure clear communication and a good user experience. The page template can be a pre-designed HTML page framework containing various elements and layouts necessary to display version update information. The update link is the URL address that redirects users directly to the game update page when clicked. The game update page can refer to an update notification page containing the target update configuration and the update link.

[0030] In one embodiment, the page template corresponding to the game port in the structured configuration parameters is determined according to the pre-set mapping relationship between the game port and the page template, and the update link is determined according to the pre-set mapping relationship between the game port and the jump link. The structured configuration parameters and the update link are then filled into the corresponding positions of the page template to generate a complete game update page. The generated game update page is then sent to the target user through the game client, SMS, email, or in-app push, ensuring that the user can receive the version update information in a timely manner, thereby guiding the user to complete the game version update. Figure 2This is a schematic diagram of an update prompt page provided in an embodiment of this application, such as... Figure 2 As shown, the update notification page includes new feature introductions, update benefit packages, version update agreements, and environment adaptation prompts, as well as target update configurations and jump links. The jump links can include "Update Now" and "Remind Me Later" update reminder links.

[0031] This application embodiment obtains the target request parameters of the target user, parses the target request parameters based on preset parameter categories to determine the target parameters corresponding to each parameter category, performs conditional adaptation on each target parameter according to preset configuration recall rules to determine multiple target update configurations, aggregates the multiple target update configurations to generate structured configuration parameters, determines the page template and update link corresponding to the game port in the structured configuration parameters, fills the structured configuration parameters and update link into the page template to generate a game update page, and pushes it to the target user. It can determine multiple target update configurations by conditionally adapting the target parameters according to preset configuration recall rules, improving the matching accuracy between update configurations and different user needs. By filling the structured configuration parameters and update link into the page template to generate a game update page and sending the game update page to the target user to prompt the target user to update the game version, it improves the reach and conversion rate of the game version update prompt.

[0032] In one embodiment, the parameter categories include basic identifiers, environmental features, and user attributes. The target request parameters are parsed based on the preset parameter categories to determine the target parameters corresponding to each parameter category, including: determining the conditional parameters corresponding to the basic identifiers, environmental features, and user attributes, respectively; and matching the target request parameters with the conditional parameters to determine the target parameters corresponding to each parameter category, wherein different parameter categories correspond to different data dimensions.

[0033] Among these, the basic identifier class refers to the parameter categories used to identify users. The environmental characteristic class may cover parameters related to the user's current network environment, device type, operating system version, etc. The user attribute class refers to the parameter categories used to represent identity rights, behavioral habits, update-related historical status, and welfare-related characteristics.

[0034] In one embodiment, conditional parameters corresponding to the basic identifier class, environmental feature class, and user attribute class are determined according to the pre-set mapping relationship between parameter types and conditional parameters. For example, the target parameters corresponding to the basic identifier class are game ID, login port type, current version number, and target version number, etc.; the target parameters corresponding to the user attribute class are user ID, registration duration, payment level, historical update records, and account status, etc.; and the target parameters corresponding to the environmental feature class are device type, operating system, device model, and network type, etc. The target request parameters are matched with each conditional parameter to determine the target parameters corresponding to each parameter category. For example, matching the target request parameters with the conditional parameters corresponding to the basic identifier class determines the corresponding target parameters as: channel package port, current version number is V2.1, target version number is V2.3; matching the target request parameters with the conditional parameters corresponding to the environmental feature class determines the corresponding target parameters as: mobile phone, iOS, WiFi; and matching the target request parameters with the conditional parameters corresponding to the user attribute class determines the corresponding target parameters as: monthly card, new user, normal account.

[0035] In another embodiment, if different parameter categories correspond to different data dimensions, when the basic update conditions are combined in multiple dimensions to obtain multiple combined conditions, they can be combined as: Port = Channel Package + User Level ≥ 50, and the corresponding target update configuration is determined as: Channel Exclusive High-Level Gift Pack, or combined as: Operating System = iOS 16 + Device Model = iPhone 14, and the corresponding target update configuration is determined as: "iOS 16 Adaptation Instructions".

[0036] This application embodiment determines the condition parameters corresponding to the basic identifier class, environmental feature class, and user attribute class respectively, and matches the target request parameters with the condition parameters to determine the target parameters corresponding to each parameter category. This can accurately extract key information under different data dimensions, provide an accurate basis for subsequent version update configuration, and flexibly adapt to various complex user scenarios.

[0037] In one embodiment, after sending the game update page to the target user, the method further includes: responding to the target user's version update operation, executing the target configuration corresponding to the target user's game port, and performing data tracking on the operation data of the version update operation to generate the target user's game version update information.

[0038] The target configuration refers to the specific configuration content that matches the target user's game port and is used to complete the version update, such as the target upgrade version or pending benefits. Tracking operations refer to recording key behavioral data through code tracking when a user performs a version update operation, such as the time the update button is clicked, download progress, installation time, and success / failure status. The generated version update information includes user identifier, operation timestamp, operation type, device environment data, and update results.

[0039] In one embodiment, after sending the game update page to the target user, the system responds in real time to the user's actions. Upon receiving a click on the update link, it's considered that the user has performed a version update. Then, based on the user's game port, the system determines the matching target upgrade version, pending benefits, and other target configurations, and executes these configurations. Simultaneously, while the user is performing the version update, the system records key user behavior data in real time and generates the target user's game version update information based on this recorded data.

[0040] This application embodiment, in response to the version update operation of the target user, executes the target configuration corresponding to the target user's game port, and performs data tracking on the operation data of the version update operation to generate the target user's game version update information. This enables game developers to evaluate the effect of the version update and thus adjust and optimize subsequent version update strategies in a timely manner.

[0041] In one embodiment, before obtaining the target user's target request parameters, the method further includes: collecting game request parameters in real time, identifying version information in the game request parameters, comparing the version information with local application version information, determining the version type of the user's version information based on the comparison result, where the version type includes a version to be updated, a forced update version, and the latest version; and determining the game request parameters as the target user's target request parameters if the version type is a version to be updated or a forced update version.

[0042] Among them, game request parameters are the core parameters transmitted from the client to the server by all game users on the game platform when logging into the game or triggering version-related operations. These parameters are used to accurately identify the user / device status and determine the scope and strategy of version updates. Version information refers to the data carried in the game request parameters that identifies the current game version status, such as version number and version type identifier. Local application version information refers to the latest version data of the current game application stored locally on the server or client. A version pending update can refer to a version where a new version exists but is not mandatory to update to, while a version requiring a mandatory update can refer to a version that must be updated to the latest version to continue playing the game.

[0043] In one embodiment, by collecting game request parameters in real time and identifying the current game version number corresponding to each game user, and comparing the current game version number of each user with the latest version number of the current game stored locally, the current game version type of the user can be accurately determined. If the version type is determined to be a version awaiting update or a version requiring a forced update, it can be considered that the user has a need for a version update. Therefore, the game request parameters are determined as the target request parameters for the target user, so as to provide version update prompts and processing in the future.

[0044] This application embodiment collects game request parameters in real time and compares the version information therein with the local application version information to accurately determine the user's version type. When an update is required, the game request parameters are processed as target request parameters, thereby achieving accurate identification of the target user and version update prompts.

[0045] Figure 3 This is a flowchart of a target update configuration determination method provided in an embodiment of this application, such as... Figure 3 As shown, it includes: Step S1021: Perform basic adaptation on each target parameter according to the preset first configuration recall rule, and determine multiple basic update conditions.

[0046] Step S1022: Combine the basic update conditions in multiple dimensions to obtain multiple combined conditions, and adapt each combined condition to the scenario based on the preset second configuration recall rule, and determine multiple target update configurations based on the scenario adaptation results.

[0047] The first configuration recall rule refers to the basic adaptation standards set for each target parameter, used to initially filter out configuration conditions that meet the basic requirements for version updates. This can include matching basic information such as user device type, operating system version, and current game version number. For example, when it detects that a user's device is an iOS system and the game version is lower than the latest version, the first configuration recall rule will trigger the corresponding basic update condition, such as "iOS system update condition." Multi-dimensional combination refers to cross-combining the basic update conditions according to different dimensions, such as user level, payment status, and in-game behavior, to form more refined combination conditions. The preset second configuration recall rule is a rule for further scenario adaptation of these combination conditions, such as a high-value user-specific update strategy during a specific event. Based on the scenario adaptation results, the system can accurately determine multiple target update configurations applicable to the current target user, such as update package size, update time window, and post-update reward mechanism, to ensure the personalization and effectiveness of version update prompts.

[0048] In one embodiment, according to a preset first configuration recall rule, each target parameter obtained from the target user is compared one by one to determine whether each target parameter meets predefined basic update conditions, such as whether the user's device type is compatible with the version to be updated, whether the operating system version meets the minimum requirements, and whether the current game version is lower than the latest version. After obtaining multiple basic update conditions, according to preset dimension classification standards, such as user level, payment status, in-game activity, and historical update behavior, the basic update conditions are cross-combined according to preset dimensions to obtain multiple combined conditions. According to a second configuration recall rule, the specific size of the update package corresponding to each combined condition, the expected update time range, the introduction of new features after the update, and the exclusive reward mechanism for different user groups are determined as multiple target update configurations.

[0049] This application embodiment performs basic adaptation on each target parameter according to a preset first configuration recall rule to determine multiple basic update conditions, combines each basic update condition in multiple dimensions to obtain multiple combined conditions, and performs scenario adaptation on each combined condition based on a preset second configuration recall rule. Based on the scenario adaptation results, multiple target update configurations are determined. This allows for refined adaptation by combining basic update conditions in multiple dimensions, ensuring that each target user receives a version update notification that is highly matched to their needs and preferences.

[0050] In one embodiment, the preset second configuration recall rule includes parameter label mapping rule and condition matching rule. Based on the preset second configuration recall rule, scene adaptation is performed on each combination condition, including: determining the combination condition label set corresponding to each combination condition according to the parameter label mapping rule, comparing the combination condition label set with the multi-dimensional label corresponding to the condition matching rule, determining the scene label overlap rate based on the comparison result, and performing scene adaptation on each combination condition based on the scene label overlap rate.

[0051] Among them, parameter label mapping rules refer to the rules that map each combined condition to a corresponding set of combined condition labels. These label sets can reflect the characteristics of the combined conditions in multiple dimensions. For example, a combined condition can simultaneously include labels such as "high-paying user," "active player," and "iOS device." Condition matching rules define all the condition labels that need to be matched in each adaptation scenario. For example, for the update scenario of high-paying active iOS users, the condition matching rules may include labels such as "high-paying user," "iOS device," and "recently active."

[0052] In one embodiment, each combined condition is converted into a corresponding combined condition label set based on the parameter label mapping rule, and these label sets are compared with the multi-dimensional labels corresponding to each scenario in the condition matching rule. The number of overlapping labels corresponding to each scenario is determined based on the comparison results, and the scenario label overlap rate is calculated based on the number of overlapping labels and the total number of labels corresponding to the corresponding scenario. The scenario with the highest label overlap rate with each combined condition is determined as the corresponding update adaptation scenario.

[0053] This application embodiment determines the set of combined condition tags corresponding to each combination of conditions according to the parameter tag mapping rules, compares the set of combined condition tags with the multidimensional tags corresponding to the condition matching rules, and determines the scene tag overlap rate based on the comparison results; and performs scene adaptation for each combination of conditions based on the scene tag overlap rate, thereby improving the personalization and efficiency of version update prompts.

[0054] Figure 4 This is a flowchart of a target update configuration determination method provided in an embodiment of this application, such as... Figure 4 As shown, it includes: Step SS10221: Analyze the configuration information in the scene adaptation results to identify multiple first target update configurations and / or conflicting configurations.

[0055] Step SS10222: Filter the conflicting configurations according to the preset priority rules to obtain the second target update configuration.

[0056] Conflict identification refers to comparing and analyzing multiple configuration information in the scenario adaptation results to determine situations where multiple conflicting configuration information is simultaneously satisfied, i.e., the same target user simultaneously satisfies multiple conflicting configuration information. For example, the same user might be matched with both "general benefits" and "port-specific benefits." The first target update configuration refers to the update configuration that can be directly determined through conflict identification to be conflict-free. Conflicting configuration refers to the update configuration that initially determines to be conflicting through conflict identification; the number of conflicting configurations must include at least two. Preset priority rules refer to pre-defined rules for filtering and sorting conflicting configurations. These rules can be set according to multiple dimensions such as business needs, user value, and update importance, and may include port priority, user value priority, and effectiveness priority. For example, port priority: channel package > native APP > PC > mini-game; user value priority: high-paying users > ordinary paying users > free users.

[0057] In one embodiment, each configuration item in the scenario adaptation result is checked one by one using a preset conflict identification algorithm or rule to determine whether a conflict exists. Configurations without conflicts are marked as the first target update configuration, and configurations with conflicts are marked as conflicting configurations. Multiple conflicting configurations are prioritized according to a preset priority rule, and the conflicting configuration with the highest priority is determined as the second target update configuration.

[0058] This application embodiment identifies multiple first target update configurations and / or conflicting configurations by performing conflict identification on the configuration information in the scenario adaptation results, and effectively filters the conflicting configurations according to preset priority rules to obtain the second target update configuration. This can avoid the problem of inaccurate update prompt information caused by configuration conflicts during the version update prompt process, and improve the accuracy and reliability of version update prompts.

[0059] Figure 5 This is a schematic diagram of the structure of a game version update notification device provided in an embodiment of this application, such as... Figure 5 As shown, it includes: The target parameter determination module 21 is used to obtain the target request parameters of the target user and parse the target request parameters based on the preset parameter categories to determine the target parameters corresponding to each parameter category; The structured configuration parameter generation module 22 is used to perform conditional adaptation on each of the target parameters according to the preset configuration recall rules to determine multiple target update configurations, and to perform aggregation processing on the multiple target update configurations to generate structured configuration parameters. The game version update notification module 23 is used to determine the page template and update link corresponding to the game port in the structured configuration parameters, fill the structured configuration parameters and the update link into the page template to generate a game update page, and push it to the target user.

[0060] This application embodiment obtains the target request parameters of the target user, parses the target request parameters based on preset parameter categories to determine the target parameters corresponding to each parameter category, performs conditional adaptation on each target parameter according to preset configuration recall rules to determine multiple target update configurations, aggregates the multiple target update configurations to generate structured configuration parameters, determines the page template and update link corresponding to the game port in the structured configuration parameters, fills the structured configuration parameters and update link into the page template to generate a game update page, and pushes it to the target user. It can determine multiple target update configurations by conditionally adapting the target parameters according to preset configuration recall rules, improving the matching accuracy between update configurations and different user needs. By filling the structured configuration parameters and update link into the page template to generate a game update page and sending the game update page to the target user to prompt the target user to update the game version, it improves the reach and conversion rate of the game version update prompt.

[0061] In one possible embodiment, the structured configuration parameter generation module 22 is specifically used for: Based on the preset first configuration recall rule, the target parameters are basically adapted to determine multiple basic update conditions. The basic update conditions are combined in multiple dimensions to obtain multiple combined conditions. Based on the preset second configuration recall rule, the combined conditions are adapted to the scenario. Based on the scenario adaptation result, multiple target update configurations are determined.

[0062] In one possible embodiment, the preset second configuration recall rule includes parameter label mapping rules and condition matching rules, and the structured configuration parameter generation module 22 is specifically used for: The combination condition label set corresponding to each combination condition is determined according to the parameter label mapping rule. The combination condition label set is compared with the multidimensional label corresponding to the condition matching rule. The scene label overlap rate is determined based on the comparison result. Scene adaptation is performed on each of the combined conditions based on the scene label overlap rate.

[0063] In one possible embodiment, the structured configuration parameter generation module 22 is specifically used for: Conflict identification is performed on the configuration information in the scenario adaptation results to determine multiple first target update configurations and / or conflicting configurations; The conflicting configurations are effectively filtered according to preset priority rules to obtain the second target update configuration.

[0064] In one possible embodiment, the parameter categories include basic identifier classes, environmental feature classes, and user attribute classes, and the target parameter determination module 21 is specifically used for: Determine the condition parameters corresponding to the basic identifier class, the environmental feature class, and the user attribute class respectively; The target request parameters are matched with the condition parameters to determine the target parameters corresponding to each parameter category, where different parameter categories correspond to different data dimensions.

[0065] In one possible embodiment, the game version update information module is used for: In response to the version update operation of the target user, the target configuration corresponding to the game port of the target user is executed, and the operation data of the version update operation is tracked to generate the game version update information of the target user.

[0066] In one possible embodiment, the target request parameter determination module is used to: The system collects game request parameters in real time, identifies version information in the game request parameters, compares the version information with local application version information, and determines the version type of the user version information based on the comparison result. The version type includes version to be updated, forced update version, and latest version. If the version type is a version awaiting update or a version that is forced to update, the game request parameters will be determined as the target request parameters for the target user.

[0067] This application also provides an electronic device that can integrate a game version update notification device provided in this application. Figure 6 This is a schematic diagram of the structure of a game version update notification device provided in an embodiment of this application, with reference to... Figure 6 The game version update notification device includes: an input device 33, an output device 34, a memory 32, and one or more processors 31; the memory 32 is used to store one or more programs; when one or more programs are executed by one or more processors 31, the one or more processors 31 implement the game version update notification method as provided in the above embodiment. The input device 33, output device 34, memory 32, and processor 31 can be connected via a bus or other means. Figure 6 Taking the example of a connection between China and Israel via a bus.

[0068] The memory 32, as a computing device readable storage medium, can be used to store software programs, computer-executable programs, and modules, such as the program instructions / modules corresponding to the game version update prompt method provided in any embodiment of this application. The memory 32 may primarily include a program storage area and a data storage area. The program storage area may store the operating system and at least one application program required for a function; the data storage area may store data created based on the use of the device. Furthermore, the memory 32 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state storage device. In some instances, the memory 32 may further include memory remotely located relative to the processor 31, and these remote memories can be connected to the device via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0069] Input device 33 can be used to receive input digital or character information, and to generate key signal inputs related to user settings and function control of the device. Output device 34 may include display devices such as a display screen.

[0070] The processor 31 executes various functional applications and data processing of the device by running software programs, instructions and modules stored in the memory 32, thereby realizing the game version update prompt method described above.

[0071] The game version update notification device, equipment, and computer provided above can be used to execute the game version update notification method provided in any of the above embodiments, and have corresponding functions and beneficial effects.

[0072] This application embodiment also provides a storage medium for storing computer-executable instructions. When executed by a computer processor, the computer-executable instructions are used to execute the game version update notification method provided in the above embodiment. The game version update notification method includes: obtaining target request parameters of a target user; parsing the target request parameters based on preset parameter categories to determine target parameters corresponding to each parameter category; performing conditional adaptation on each target parameter according to preset configuration recall rules to determine multiple target update configurations; aggregating the multiple target update configurations to generate structured configuration parameters; determining a page template and update link corresponding to the game port in the structured configuration parameters; filling the structured configuration parameters and the update link into the page template to generate a game update page, which is then pushed to the target user.

[0073] Storage medium – any type of memory device or storage device. The term “storage medium” is intended to include: mounting media, such as CD-ROMs, floppy disks, or magnetic tape devices; computer system memory or random access memory, such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; non-volatile memory, such as flash memory, magnetic media (e.g., hard disks or optical storage); registers or other similar types of memory elements, etc. Storage media may also include other types of memory or combinations thereof. Furthermore, storage media may reside in a first computer system in which a program is executed, or may reside in a different second computer system connected to the first computer system via a network (such as the Internet). The second computer system can provide program instructions to the first computer for execution. The term “storage medium” can include two or more storage media that may reside in different locations (e.g., in different computer systems connected via a network). Storage media may store program instructions (e.g., specifically implemented as a computer program) executable by one or more processors.

[0074] Of course, the computer-executable instructions provided in the embodiments of this application are not limited to the game version update notification method described above, but can also execute related operations in the game version update notification method provided in any embodiment of this application.

[0075] The game version update notification device, equipment, and storage medium provided in the above embodiments can execute the game version update notification method provided in any embodiment of this application. For technical details not described in detail in the above embodiments, please refer to the game version update notification method provided in any embodiment of this application.

[0076] The above description is merely a preferred embodiment and the technical principles employed in this application. This application is not limited to the specific embodiments described herein, and various obvious changes, readjustments, and substitutions that can be made by those skilled in the art will not depart from the scope of protection of this application. Therefore, although this application has been described in detail through the above embodiments, this application is not limited to the above embodiments, and may include more other equivalent embodiments without departing from the concept of this application, the scope of which is determined by the scope of the claims.

Claims

1. A game version update prompting method characterized by comprising: include: Obtain the target request parameters of the target user, and parse the target request parameters based on the preset parameter categories to determine the target parameters corresponding to each parameter category; According to the preset configuration recall rules, conditional adaptation is performed on each of the target parameters to determine multiple target update configurations, and the multiple target update configurations are aggregated to generate structured configuration parameters; Determine the page template and update link corresponding to the game port in the structured configuration parameters, fill the page template with the structured configuration parameters and the update link to generate a game update page, and push it to the target user.

2. The game version update prompting method according to claim 1, wherein The step of determining multiple target update configurations by conditionally adapting each target parameter according to a preset configuration recall rule includes: Based on the preset first configuration recall rule, the target parameters are basically adapted to determine multiple basic update conditions. The basic update conditions are combined in multiple dimensions to obtain multiple combined conditions. Based on the preset second configuration recall rule, the combined conditions are adapted to the scenario. Based on the scenario adaptation result, multiple target update configurations are determined.

3. The game version update prompting method according to claim 2, wherein The preset second configuration recall rule includes parameter label mapping rules and condition matching rules. The scenario adaptation of each combination condition based on the preset second configuration recall rule includes: The combination condition label set corresponding to each combination condition is determined according to the parameter label mapping rule. The combination condition label set is compared with the multidimensional label corresponding to the condition matching rule. The scene label overlap rate is determined based on the comparison result. Scene adaptation is performed on each of the combined conditions based on the scene label overlap rate.

4. The game version update prompting method according to claim 2, wherein The determination of multiple target update configurations based on scenario adaptation results includes: Conflict identification is performed on the configuration information in the scenario adaptation results to determine multiple first target update configurations and / or conflicting configurations; The conflicting configurations are effectively filtered according to preset priority rules to obtain the second target update configuration.

5. The game version update prompting method according to claim 1, wherein The parameter categories include basic identifier categories, environmental feature categories, and user attribute categories. The process of parsing the target request parameters based on preset parameter categories to determine the target parameters corresponding to each category includes: Determine the condition parameters corresponding to the basic identifier class, the environmental feature class, and the user attribute class respectively; The target request parameters are matched with the condition parameters to determine the target parameters corresponding to each parameter category, where different parameter categories correspond to different data dimensions.

6. The game version update prompting method according to claim 1, wherein After sending the game update page to the target user, the process further includes: In response to the version update operation of the target user, the target configuration corresponding to the game port of the target user is executed, and the operation data of the version update operation is tracked to generate the game version update information of the target user.

7. The game version update prompting method according to claim 1, wherein Before obtaining the target user's target request parameters, the method further includes: Real-time game request parameters are collected, version information in the game request parameters is identified, the version information is compared with local application version information, a version type of the user version information is determined based on a comparison result, and the version type includes a to-be-updated version, a forced-updated version, and a latest version. In a case where the version type is the to-be-updated version or the forced-updated version, the game request parameters are determined as target request parameters of a target user.

8. A game version update prompting device characterized by comprising: The method comprises: A target parameter determination module is configured to obtain target request parameters of a target user, and analyze the target request parameters based on a preset parameter category to determine target parameters corresponding to each parameter category. A structured configuration parameter generation module is configured to conditionally adapt each target parameter according to a preset configuration recall rule to determine a plurality of target update configurations, aggregate the plurality of target update configurations, and generate structured configuration parameters. A game version update prompt module is configured to determine a page template and an update link corresponding to a game port in the structured configuration parameters, fill the structured configuration parameters and the update link into the page template to generate a game update page, and push the game update page to the target user.

9. An electronic device, comprising: The device comprises one or more processors, and a storage apparatus configured to store one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the game version update prompt method according to any one of claims 1-7.

10. A storage medium storing computer-executable instructions, wherein: The computer executable instructions, when executed by a computer processor, are configured to implement the game version update prompt method according to any one of claims 1-7.

Images