A method, apparatus, device, and medium for version control of game applications.

Abstract

This application discloses a method, apparatus, device, and medium for game application version control, comprising: sending a request to a central server so that the central server returns the desired version game information corresponding to the user node; comparing the desired version game information with the current version game information stored locally to determine whether the node meets the installation conditions for the desired version game; if the node meets the installation conditions for the desired version game, then installing the desired version game application based on the desired version game information. This eliminates the need for the central server to send notifications periodically, avoids wasting central server resources, and ensures that the node can immediately install the desired version game application after going online.

Description

Technical Field

[0001] This application relates to the field of game application version control technology, and in particular to a game application version control method, apparatus, device and medium. Background Technology

[0002] Currently, in existing game application version control schemes, when a desired version of a game application is available for a node to install, the central server typically sends a notification to each node to instruct them to install the game application. However, the central server does not know whether a node is online, so it usually sends a notification at regular intervals. This results in a waste of the central server's resources. Furthermore, after a node comes back online, it needs to wait for a notification from the central server and cannot immediately install the desired version. Summary of the Invention

[0003] In view of this, the purpose of this application is to provide a method, apparatus, device, and medium for game application version control, which can avoid the waste of central server resources and ensure that the desired version of the game application can be installed immediately after the node goes online. The specific solution is as follows:

[0004] Firstly, this application discloses a game application version control method, applied to user nodes, including:

[0005] Send a request to the central server so that the central server can return the desired version of the game information corresponding to the user node;

[0006] The desired version of the game information is compared with the current version of the game information stored locally to determine whether this node meets the installation conditions for the desired version of the game.

[0007] If this node meets the installation conditions for the desired version of the game, then the desired version of the game application will be installed based on the desired version of the game information.

[0008] Optionally, comparing the desired game version information with the currently stored game version information to determine whether the current node meets the installation conditions for the desired game version includes:

[0009] The desired version of the game information is compared with the current version of the game information stored locally to obtain the game version comparison result;

[0010] If the version comparison result indicates that the local game version is an older version, then this node is determined to meet the installation conditions for the desired version of the game.

[0011] Optional, also includes:

[0012] If the version comparison result shows that the local game version is the same as the expected version, then this node is determined not to meet the installation conditions of the expected version of the game.

[0013] Optional, also includes:

[0014] If the version comparison result indicates that the local game version is a newer version, then this node is determined not to meet the installation conditions for the desired version of the game; or, this node is determined to meet the installation conditions for the desired version of the game, and a lower version of the game application is installed based on the desired version of the game information.

[0015] Optional, also includes:

[0016] If the version comparison result is that the local game version and the expected version are the same, then the information digest in the expected version game information is compared with the information digest in the current version game information;

[0017] If the information digest in the desired version of the game information is inconsistent with the information digest in the current version of the game information, then this node is determined to meet the installation conditions of the desired version of the game.

[0018] Optionally, after installing the desired version of the game application based on the desired version game information, the method further includes:

[0019] Update the currently stored game version information based on the expected version game information;

[0020] Alternatively, read the application information of the installed game application and update the current version of the game information stored locally based on the application information.

[0021] Optionally, after installing the desired version of the game application based on the desired version game information, the method further includes:

[0022] The updated current version of the game information is reported to the central server so that the central server can determine whether the game application has been installed successfully based on the updated current version of the game information and the expected version of the game information.

[0023] Optional, also includes:

[0024] If the current version of the game information does not exist locally, then the desired version of the game application will be installed based on the desired version of the game information.

[0025] Optionally, sending a request to the central server includes:

[0026] Send requests to the central server periodically.

[0027] Secondly, this application discloses a game application version control device, applied to a user node, comprising:

[0028] The request sending module is used to send a request to the central server so that the central server can return the desired version of the game information corresponding to the user node.

[0029] The installation condition judgment module is used to compare the desired version game information with the current version game information stored locally to determine whether the current node meets the installation conditions of the desired version game.

[0030] If the installation condition judgment module determines that this node meets the installation conditions of the desired version of the game, the game application installation module will install the desired version of the game application based on the desired version of the game information.

[0031] Thirdly, this application discloses an electronic device, including a memory and a processor, wherein:

[0032] The memory is used to store computer programs;

[0033] The processor is used to execute the computer program to implement the aforementioned game application version control method.

[0034] Fourthly, this application discloses a computer-readable storage medium for storing a computer program, wherein the computer program, when executed by a processor, implements the aforementioned game application version control method.

[0035] As can be seen, this application sends a request to the central server so that the central server can return the desired version of the game information corresponding to the user node. Then, the desired version of the game information is compared with the currently stored version of the game information to determine whether the node meets the installation conditions for the desired version of the game. If the node meets the installation conditions, the desired version of the game application is installed based on the desired version of the game information. That is, in this application, the user node actively sends a request to the central server to obtain the desired version of the game information returned by the central server, compares the desired version of the game information with the currently stored version of the game information to determine whether the desired version of the game application needs to be installed. If installation is required, the desired version of the game application is installed based on the desired version of the game information. This eliminates the need for the central server to send notifications periodically, avoids wasting the central server's resources, and ensures that the desired version of the game application can be installed immediately after the node goes online. Attached Figure Description

[0036] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of this application. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0037] Figure 1 This is a flowchart of a game application version control method disclosed in an embodiment of this application;

[0038] Figure 2 This is a schematic diagram of a specific game application version control disclosed in an embodiment of this application;

[0039] Figure 3 This is a schematic diagram of the structure of a game application version control device disclosed in an embodiment of this application;

[0040] Figure 4 This is a structural diagram of an electronic device disclosed in an embodiment of this application. Detailed Implementation

[0041] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0042] Currently, in existing game application version control schemes, when a desired version of the game application is available for a node, the central server typically sends a notification to each node to instruct them to install the application. However, the central server is unaware of whether a node is online, so notifications are usually sent only at regular intervals. This results in wasted resources on the central server. Furthermore, after a node comes back online, it must wait for a notification from the central server and cannot immediately install the desired version. Therefore, this application provides a game application version control scheme that avoids wasting central server resources and ensures that nodes can immediately install the desired version of the game application after coming online.

[0043] See Figure 1 As shown in the figure, this application discloses a game application version control method, including:

[0044] Step S11: Send a request to the central server so that the central server can return the desired version of the game information corresponding to the user node.

[0045] In one implementation, this application embodiment can periodically send requests to a central server. That is, the user node polls the central server for its desired game version information. The desired game version information is the game information set by the central server. During the initial setting, after obtaining the desired game version information, it can be set directly. In subsequent settings, after obtaining the desired game version information, it can be compared with the previously set desired game version information to determine if an update is needed. If an update is needed, the desired game version information is set. For example, if the version number is greater than the version number in the previously set desired game version information, an update is determined to be needed; if the version number is the same and the MD5 value is different from the MD5 value in the previously set desired game version information, an update is determined to be needed.

[0046] Step S12: Compare the desired version game information with the current version game information stored locally to determine whether this node meets the installation conditions for the desired version game.

[0047] This application embodiment compares the desired version game information with the currently stored version game information to obtain a game version comparison result. The desired version information may include a version number, game name, and the time when version control was initiated. The version number in the desired version game information is compared with the version number in the currently stored version game information to obtain the game version comparison result.

[0048] Furthermore, if the version comparison result indicates that the local game version is an older version, then this node is determined to meet the installation requirements for the desired game version. Specifically, this could mean that the local game application version number is lower, and the node needs to upgrade the game application.

[0049] Furthermore, in one implementation, if the version comparison result shows that the local game version and the desired version are the same, then it is determined that this node does not meet the installation conditions for the desired version of the game. In another implementation, the desired version of the game information may further include a message digest. If the version comparison result shows that the local game version and the desired version are the same, then the message digest in the desired version of the game information is compared with the message digest in the current version of the game information; if the message digest in the desired version of the game information is inconsistent with the message digest in the current version of the game information, then it is determined that this node meets the installation conditions for the desired version of the game. The message digest can be an MD5 value.

[0050] Furthermore, in one implementation, if the version comparison result indicates that the local game version is a newer version, then it is determined that this node does not meet the installation conditions for the desired version of the game. That is, if the local game version is a newer version, the current game version is maintained. In another implementation, if the version comparison result indicates that the local game version is a newer version, it can be determined that this node meets the installation conditions for the desired version of the game, and a lower version of the game application can be installed based on the desired version game information. That is, the embodiments of this application can perform version rollback as needed.

[0051] Furthermore, in this embodiment, if the current version of the game information does not exist locally, the desired version of the game application is installed based on the desired version of the game information. This embodiment can determine whether the current version of the game information exists locally before comparing it with the locally stored current version of the game information. If it exists, the step of comparing the desired version of the game information with the locally stored current version of the game information is triggered; if it does not exist, the desired version of the game application is installed based on the desired version of the game information. That is, when this node installs the game application for the first time, it directly installs the desired version of the game application based on the desired version of the game information and saves the desired version of the game information locally as the current version of the game information. During subsequent installations, it compares the new desired version of the game information with the current version of the game information to determine whether to install the desired version of the game application.

[0052] Step S13: If this node meets the installation conditions of the desired version of the game, then install the desired version of the game application based on the desired version of the game information.

[0053] In a specific implementation, the corresponding installation package can be downloaded from a remote server based on the desired version of the game information, and the desired version of the game application can be installed.

[0054] Alternatively, in one implementation, the currently stored game version information can be updated based on the desired game version information. In another implementation, the application information of the installed game application can be read, and the currently stored game version information can be updated based on the application information.

[0055] Furthermore, the updated current version of the game information is reported to the central server, so that the central server can determine whether the game application has been installed successfully based on the updated current version of the game information and the expected version of the game information. The updated current version of the game information can be compared with the expected version of the game information; if the updated current version of the game information matches the expected version of the game information, the installation is considered complete; otherwise, it is considered incomplete.

[0056] For example, see Figure 2 As shown, Figure 2 This is a schematic diagram illustrating a specific game application version control method disclosed in this application. The expected version game information refers to the game information of the game version that a node is expected to install, including the game package name, game version number, game package MD5 value, and the time when game version control was initiated. The granularity of the setting is per node, and each node corresponds to one expected version game information. A node refers to the server operating the game, and each server is identified by its own server ID. This application embodiment does not limit the server architecture; for example, it can use an x86 architecture. That is, the expected version game information is set for each node based on the server ID. The first time it is set, the expected version game information is directly set. For subsequent settings, after obtaining the expected version game information, it can be compared with the previously set expected version game information to determine whether an update is needed. If an update is needed, the expected version game information is set. For example, if the version number is greater than the version number in the previously set expected version game information, an update is determined to be needed; if the version number is the same and the MD5 value is different from the MD5 value in the previously set expected version game information, an update is determined to be needed. In addition, each node runs client software that polls the central server for the desired game version information using the server ID. Upon receiving the desired version information, during the first installation, the node downloads the corresponding installation package from the remote server and executes the game application installation. During subsequent installations, the node compares the game version information with its local storage based on a preset comparison logic. If installation is required, the node downloads the corresponding installation package from the remote server, executes the game application installation, and updates its local game version information. Regardless of whether it's the first or subsequent installations, a successful installation message is reported upon completion. After a successful upgrade, the central server saves the current game version information for that node, completing the installation cycle.

[0057] The current version game information stored locally on the node includes the game package name, game version number, and game package MD5 value. If the node does not have the game installed, it directly downloads the game package from the storage server based on the game package name, game version number, and game package MD5 value. After downloading, it installs the game package, and upon successful installation, records the game package name, game version number, and game package MD5 value as the current version game information in the local table. If the node has already installed the game, it compares the game version number in the expected version game information with the game version number in the local table. If the game version number in the expected version game information is greater than the game version number in the local table, it indicates that an upgrade is needed. Then, it downloads the game package from the storage server, installs it, and upon successful installation, records the game package name, game version number, and game package MD5 value from the expected version game information in the local table. If the two are equal, it compares the MD5 values. If the MD5 values ​​are different, it also indicates that an upgrade is needed. Then, it downloads the game package from the storage server, installs it, and upon successful installation, records the expected version game information in the local table. If the MD5 values ​​are less than the expected version game information, it indicates that no upgrade is needed. The client software can poll for the desired game version information, compare execution information, download the game package, install it, and report successful installation. This way, even if the node is offline, it can still perform game installation and upgrade operations once it is back online.

[0058] As can be seen, in this embodiment, a request is sent to the central server so that the central server can return the desired version of the game information corresponding to the user node. Then, the desired version of the game information is compared with the currently stored version of the game information to determine whether the node meets the installation conditions for the desired version of the game. If the node meets the installation conditions, the desired version of the game application is installed based on the desired version of the game information. That is, in this embodiment, the user node actively sends a request to the central server to obtain the desired version of the game information returned by the central server, compares the desired version of the game information with the currently stored version of the game information to determine whether the desired version of the game application needs to be installed. If installation is required, the desired version of the game application is installed based on the desired version of the game information. This eliminates the need for the central server to send notifications periodically, avoids wasting the central server's resources, and ensures that the node can immediately install the desired version of the game application after going online.

[0059] See Figure 3 As shown in the figure, this application discloses a game application version control device, applied to a user node, including:

[0060] The request sending module 11 is used to send a polling request to the central server so that the central server can return the expected version of the game information corresponding to the user node.

[0061] The installation condition judgment module 12 is used to compare the expected version game information with the current version game information stored locally in order to determine whether the current node meets the installation conditions of the expected version game.

[0062] If the installation condition judgment module determines that this node meets the installation conditions of the desired version of the game, the game application installation module 13 will install the desired version of the game application based on the desired version of the game information.

[0063] As can be seen, in this embodiment, a request is sent to the central server so that the central server can return the desired version of the game information corresponding to the user node. Then, the desired version of the game information is compared with the currently stored version of the game information to determine whether the node meets the installation conditions for the desired version of the game. If the node meets the installation conditions, the desired version of the game application is installed based on the desired version of the game information. That is, in this embodiment, the user node actively sends a request to the central server to obtain the desired version of the game information returned by the central server, compares the desired version of the game information with the currently stored version of the game information to determine whether the desired version of the game application needs to be installed. If installation is required, the desired version of the game application is installed based on the desired version of the game information.

[0064] The installation condition judgment module 12 is specifically used to compare the desired version game information with the current version game information stored locally to obtain the game version comparison result; if the version comparison result is that the local game version is an old version, then it is determined that this node meets the installation conditions of the desired version game.

[0065] In one embodiment, the installation condition judgment module 12 is further configured to determine that the current node does not meet the installation conditions for the desired version of the game if the version comparison result shows that the local game version and the desired version are the same. In another embodiment, the installation condition judgment module 12 is further configured to compare the information digest in the desired version of the game information with the information digest in the current version of the game information if the version comparison result shows that the local game version and the desired version are the same; if the information digest in the desired version of the game information is inconsistent with the information digest in the current version of the game information, then the current node is determined to meet the installation conditions for the desired version of the game.

[0066] Furthermore, in one embodiment, the installation condition judgment module 12 is also used to determine that the current node does not meet the installation conditions for the desired version of the game if the version comparison result indicates that the local game version is a newer version. In another embodiment, the installation condition judgment module 12 is also used to determine that the current node meets the installation conditions for the desired version of the game, and correspondingly, the game application installation module 13 is used to install a lower version of the game application based on the desired version of the game information.

[0067] Furthermore, the device also includes a current version game information update module.

[0068] In one implementation, the current version game information update module is specifically used to update the locally stored current version game information based on the expected version game information after the expected version game application is installed based on the expected version game information.

[0069] In another implementation, the current version game information update module is specifically used to read the application information of the installed game application after the desired version game application is installed based on the desired version game information, and update the locally stored current version game information based on the application information.

[0070] Furthermore, the device also includes a current version game information reporting module, used to report updated current version game information to the central server, so that the central server can determine whether the game application has been installed based on the updated current version game information and the desired version game information.

[0071] Furthermore, the device also includes an initial installation judgment module for determining whether current version game information exists locally. Correspondingly, the game application installation module 13 is used to install the desired version game application based on the desired version game information if the initial installation judgment module determines that current version game information does not exist locally.

[0072] In one implementation, the request sending module 11 is specifically used to periodically send requests to the central server.

[0073] See Figure 4 As shown in the figure, this application discloses an electronic device 20, including a processor 21 and a memory 22; wherein, the memory 22 is used to store a computer program; the processor 21 is used to execute the computer program, namely the game application version control method disclosed in the foregoing embodiment.

[0074] The specific process of the above-mentioned game application version control method can be found in the relevant content disclosed in the foregoing embodiments, and will not be repeated here.

[0075] Furthermore, the memory 22, as a carrier for resource storage, can be a read-only memory, random access memory, disk, or optical disk, and the storage method can be temporary storage or permanent storage.

[0076] In addition, the electronic device 20 also includes a power supply 23, a communication interface 24, an input / output interface 25, and a communication bus 26; wherein, the power supply 23 is used to provide operating voltage for the various hardware devices on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and external devices, and the communication protocol it follows can be any communication protocol applicable to the technical solution of this application, and is not specifically limited here; the input / output interface 25 is used to acquire external input data or output data to the outside world, and its specific interface type can be selected according to specific application needs, and is not specifically limited here.

[0077] Furthermore, this application also discloses a computer-readable storage medium for storing a computer program, wherein the computer program, when executed by a processor, implements the game application version control method disclosed in the foregoing embodiments.

[0078] The specific process of the above-mentioned game application version control method can be found in the relevant content disclosed in the foregoing embodiments, and will not be repeated here.

[0079] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the apparatus disclosed in the embodiments, since it corresponds to the method disclosed in the embodiments, the description is relatively simple; relevant parts can be referred to in the method section.

[0080] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software module executed by a processor, or a combination of both. The software module can be located in random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.

[0081] The above provides a detailed description of a game application version control method, apparatus, device, and medium provided in this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the method and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A method for version control of game applications, characterized in that, Applied to user nodes, including: A request is periodically sent to the central server so that the central server can return the desired version of the game information corresponding to the user node; wherein, the desired version of the game information is the game information set by the central server; The desired version of the game information is compared with the current version of the game information stored locally to determine whether this node meets the installation conditions for the desired version of the game. If this node meets the installation conditions for the desired version of the game, then the desired version of the game application will be installed based on the desired version of the game information. The step of comparing the desired version game information with the currently stored version game information to determine whether the node meets the installation conditions for the desired version game includes: comparing the desired version game information with the currently stored version game information to obtain a game version comparison result; if the version comparison result indicates that the local game version and the desired version are the same, then comparing the information digest in the desired version game information with the information digest in the current version game information; if the information digest in the desired version game information is inconsistent with the information digest in the current version game information, then determining that the node meets the installation conditions for the desired version game.

2. The game application version control method according to claim 1, characterized in that, Also includes: If the version comparison result indicates that the local game version is an older version, then this node is determined to meet the installation conditions for the desired version of the game.

3. The game application version control method according to claim 2, characterized in that, Also includes: If the version comparison result indicates that the local game version is a newer version, then this node is determined not to meet the installation conditions for the desired version of the game; or, this node is determined to meet the installation conditions for the desired version of the game, and a lower version of the game application is installed based on the desired version of the game information.

4. The game application version control method according to claim 1, characterized in that, After installing the desired version of the game application based on the desired version game information, the process further includes: Update the currently stored game version information based on the expected version game information; Alternatively, read the application information of the installed game application and update the current version of the game information stored locally based on the application information.

5. The game application version control method according to claim 4, characterized in that, After installing the desired version of the game application based on the desired version game information, the process further includes: The updated current version of the game information is reported to the central server so that the central server can determine whether the game application has been installed successfully based on the updated current version of the game information and the expected version of the game information.

6. The game application version control method according to any one of claims 1 to 5, characterized in that, Also includes: If the current version of the game information does not exist locally, then the desired version of the game application will be installed based on the desired version of the game information.

7. A game application version control device, characterized in that, Applied to user nodes, including: The request sending module is used to periodically send requests to the central server so that the central server can return the desired version game information corresponding to the user node; wherein, the desired version game information is the game information set by the central server; The installation condition judgment module is used to compare the desired version game information with the current version game information stored locally to determine whether the current node meets the installation conditions of the desired version game. If the installation condition judgment module determines that this node meets the installation conditions of the desired version of the game, the game application installation module will install the desired version of the game application based on the desired version of the game information. The installation condition judgment module is specifically used to: compare the desired version game information with the currently stored version game information to obtain a game version comparison result; if the version comparison result shows that the local game version and the desired version are the same, then compare the information digest in the desired version game information with the information digest in the current version game information; if the information digest in the desired version game information is inconsistent with the information digest in the current version game information, then determine that this node meets the installation conditions for the desired version game.

8. An electronic device, characterized in that, Includes memory and processor, wherein: The memory is used to store computer programs; The processor is configured to execute the computer program to implement the game application version control method as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, Used to store computer programs, wherein the computer programs, when executed by a processor, implement the game application version control method as described in any one of claims 1 to 6.

Images