CN112827180A

CN112827180A - Game updating method, device, equipment and storage medium

Info

Publication number: CN112827180A
Application number: CN202110083287.9A
Authority: CN
Inventors: 杜晶; 林顺
Original assignee: Xiamen Yaji Software Co Ltd
Current assignee: Xiamen Yaji Software Co Ltd
Priority date: 2021-01-21
Filing date: 2021-01-21
Publication date: 2021-05-25

Abstract

The embodiment of the application discloses a game updating method, a game updating device, game updating equipment and a storage medium. In at least one embodiment of the present application, game update information is added to a game update request, and then after the game update request is obtained, at least one channel to be updated can be determined based on the game update information, so that for each channel to be updated, a game to be updated is placed on the shelf, game information of the game to be updated is updated based on the game update information, and a deployment notification is sent to a plurality of game servers under the jurisdiction of the channel, so that the game servers deploy resources required by the game to be updated, and thus, in the game update process, a user can see the placement state of the game, and further know that the game is being updated, and avoid using an incorrect version of the game in the game update process.

Description

Game updating method, device, equipment and storage medium

Technical Field

The application relates to the technical field of cloud games, in particular to a game updating method, device, equipment and storage medium.

Background

The cloud game is that a game instance originally running at a user side is moved to a cloud game server side to run, the user side only transmits the operation of the user side to the cloud game server side in real time through a network, so that the game instance of the cloud game server side responds to the operation, the running result of the game is transmitted to the user side in real time, and pictures and sound are displayed on the user side.

When a game a is updated, all resources corresponding to the game a in each channel need to be updated, so that in the updating process of the game a, all resources corresponding to the game a in each channel cannot be used by other games (i.e., games that do not need to be updated, such as games B and C), and the game a also has to wait until all resources corresponding to the game a are updated, and then can normally use the resources.

In addition, even if all the resources corresponding to the game a are updated one by one, although the resources corresponding to the game a that are not updated can still be used by other games, the start and completion of the update of the game a cannot be known correctly, and the resources that are not updated may provide the wrong version of the game a to the user for use, which may cause confusion, for example, the user cannot normally play.

Disclosure of Invention

The purpose of the present application is to solve at least one of the above technical drawbacks, and to provide the following solutions:

in a first aspect, at least one embodiment of the present application provides a game update method, the method comprising:

acquiring a game updating request, wherein the game updating request comprises game updating information;

determining at least one channel to be updated based on the game updating information and preset one or more channel information;

for each channel to be updated:

putting off the shelf the game to be updated corresponding to the channel to be updated;

updating the game information of the game to be updated based on the game updating information;

and sending a deployment notice to a plurality of game servers belonging to the channel to be updated, so that each game server deploys resources required by the game to be updated based on the deployment notice.

In some embodiments, the game update information includes a game identification of a game to be updated; the channel information comprises a first game list of channels, wherein the first game list comprises game identification of each game;

the determining at least one channel to be updated based on the game update information and preset one or more channel information includes:

searching a first game list with the game identification of the game to be updated;

and determining the channel corresponding to the searched first game list as a channel to be updated.

In some embodiments, the first game list further comprises a game state for each game;

the step of putting off the game to be updated corresponding to the channel to be updated comprises the following steps:

and setting the game state of the game to be updated in the first game list of the channel to be updated as the off-shelf state.

In some embodiments, the game update information further includes first game information of the game to be updated, and the first game list further includes second game information of each game;

the updating the game information of the game to be updated based on the game update information includes: and replacing the second game information of the game to be updated in the first game list of the channel to be updated with the first game information.

In some embodiments, the game update information further includes first configuration information and a game deployment script; the deployment notification comprises first game information of the game to be updated, the first configuration information and the game deployment script;

the deploying, by each game server, the resources required for deploying the game to be updated based on the deployment notification includes:

each game server generates second configuration information based on the first game information and the first configuration information of the game to be updated, and executes the game deployment script; and the second configuration information is the configuration information stored on the resources required by the game to be updated.

In some embodiments, the sending of the deployment notification to the plurality of game servers governed by the channel to be updated includes:

batching a plurality of game servers belonging to the channel to be updated;

and sending the deployment notification to each game server of the same batch each time based on a preset sending strategy.

In some embodiments, the transmission policy comprises: and if the number of the game servers returning the deployment result is less than that of the game servers administered by the channel to be updated, continuing to send deployment notification to the game servers belonging to the same batch.

In some embodiments, after the sending the deployment notification, the method further comprises:

and modifying the state of the corresponding game server to be the deployment state.

In some embodiments, the method further comprises:

acquiring a deployment result of each game server to the resources required by the game to be updated;

and updating the information and the state of the corresponding game server based on the deployment result.

In some embodiments, the deployment result comprises:

the information used for describing the successful deployment, the identification of the game server, the game identification and the second configuration information; or the like, or, alternatively,

information for describing deployment failure and failure information.

In some embodiments, the obtaining the game update request comprises: receiving a game updating request sent by a request terminal;

the method further comprises the following steps: sending a game updating response to the request terminal based on the deployment result; the game update response includes the updated channel identification and the updated game identification.

In some embodiments, the sending a game update response to the requesting end based on the deployment result comprises:

and sending a game updating response to the request terminal based on the deployment result being the first successful deployment result.

In some embodiments, the method further comprises:

acquiring a game listing request, wherein the game listing request comprises a channel identifier and a game identifier;

counting the number of game servers aiming at the deployment result of the game identifier returned under the channel corresponding to the channel identifier;

and if at least one deployment result is successful, setting the game corresponding to the game identifier under the channel corresponding to the channel identifier as an on-shelf state.

In a second aspect, at least one embodiment of the present application provides a game update apparatus, the apparatus comprising:

an acquisition unit configured to acquire a game update request including game update information;

the determining unit is used for determining at least one channel to be updated based on the game updating information and preset one or more channel information;

for each channel to be updated:

the shelving unit is used for shelving the game to be updated corresponding to the channel to be updated;

an updating unit for updating the game to be updated based on the game update information

Game information;

and the sending unit is used for sending a deployment notice to a plurality of game servers administered by the channel to be updated so that each game server deploys the resources required by the game to be updated based on the deployment notice.

In a third aspect, at least one embodiment of the present application provides an electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor implements any of the above-mentioned game update methods when executing the computer program.

In a fourth aspect, at least one embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon, the computer program, when executed by a processor, implementing any of the above-described game update methods.

In at least one embodiment of the present application, game update information is added to a game update request, and then after the game update request is obtained, at least one channel to be updated can be determined based on the game update information, so that for each channel to be updated, a game to be updated is placed on the shelf, game information of the game to be updated is updated based on the game update information, and a deployment notification is sent to a plurality of game servers under the jurisdiction of the channel, so that the game servers deploy resources required by the game to be updated, and thus, in the game update process, a user can see the placement state of the game, and further know that the game is being updated, and avoid using an incorrect version of the game in the game update process.

Additional aspects and advantages of the present application will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the present application.

Drawings

The foregoing and/or additional aspects and advantages of the present application will become apparent and readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings of which:

fig. 1 is a schematic diagram of an application scenario provided in an embodiment of the present application;

FIG. 2 is a block diagram of a game update apparatus according to an embodiment of the present disclosure;

FIG. 3 is a multi-end interaction diagram in a game update process according to an embodiment of the present disclosure;

fig. 4 is a block diagram of an electronic device provided in an embodiment of the present application;

fig. 5 is a flowchart of a game updating method according to an embodiment of the present application.

Detailed Description

Reference will now be made in detail to the embodiments of the present application, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar function throughout. The embodiments described below with reference to the drawings are exemplary only for the purpose of explaining the present application and are not to be construed as limiting the present application.

As used herein, the singular forms "a", "an", "the" and "the" include plural referents unless the context clearly dictates otherwise. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. It will be understood that when an element is referred to as being "connected" or "coupled" to another element, it can be directly connected or coupled to the other element or intervening elements may also be present. Further, "connected" or "coupled" as used herein may include wirelessly connected or wirelessly coupled. As used herein, the term "and/or" includes all or any element and all combinations of one or more of the associated listed items. Relational terms such as "first" and "second," and the like, may be used herein only to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions.

The following describes the technical solutions of the present application and how to solve the above technical problems with specific embodiments. The following several specific embodiments may be combined with each other, and details of the same or similar concepts or processes may not be repeated in some embodiments. To make the objects, technical solutions and advantages of the present application clearer, embodiments of the present application will be described below with reference to the accompanying drawings.

Fig. 1 is a schematic diagram of an application scenario provided in an embodiment of the present application. In fig. 1, a request end 11 may perform data interaction with an operation and maintenance service end 12 through a network; the operation and maintenance server 12 can perform data interaction with a plurality of game servers belonging to the channel to be updated 13 through a network. The network can be 4G network, 5G network and other networks for data interaction. In some embodiments, there may be multiple requesters 11 accessing the operation and maintenance server 12; a plurality of operation and maintenance service terminals 12 can also serve different request terminals 11; there may be a plurality of channels to be updated 13, and a plurality of game servers governed by each channel to be updated 13 perform data interaction with the operation and maintenance server 12 through a network.

Request terminal

The request end 11 may be any end that can perform authentication through the operation and maintenance server 12, for example, the request end 11 may be an operation and maintenance page, the operation and maintenance server 12 itself, an operation server, a User Agent (UA), and the like. The user side is any device capable of accessing the cloud game server, for example, the user side may be any device installed with software (for example, cloud game client software) for accessing the cloud game server, and the software for accessing the cloud game server may also be understood as software implementation of the user side.

In some embodiments, the user side may include, but is not limited to: thin clients, general purpose computers, special purpose computers, gaming consoles, personal computers, laptop computers, tablet computing devices, mobile computing devices, portable gaming devices, cellular phones, smart phones, notebook computers, head mounted displays, smart wearable devices, set-top boxes, streaming media interfaces/devices, smart televisions or networked displays, and the like.

In some embodiments, the user side is at least used for accessing a cloud game of the cloud game server side, receiving a game operation input by a user, generating a corresponding operation instruction, and uploading the operation instruction to the cloud game server side. The user can access the cloud game list of the cloud game server through the user side to select the cloud game. In some embodiments, when there are multiple cloud game servers, the multiple cloud game servers may be distributed in different regions, and the user accesses the cloud game server corresponding to the region where the user is located through the user side.

In some embodiments, the cloud game server may be any device capable of running the cloud game program, for example, any device installed with the cloud game program and software providing the cloud game service, where the software providing the cloud game service may also be understood as a software implementation of the cloud game server.

In some examples, the cloud game server may be a single server or a server cluster, and the server group may be centralized or distributed. In some embodiments, the cloud gaming server may be a remote server, virtual computer, cloud gaming server, cloud application server, remote application server, digital media server, server for providing a game developer/game sponsor storefront (storefront), website server, terminal server, console server, or the like.

In some embodiments, a cloud game server may deploy a cloud game in a cloud game service cluster, a node server of the cloud game service cluster may run a cloud game program, and a plurality of cloud game servers belong to the cloud game server cluster. In this embodiment, the user can access the cloud game server through the user side, and schedule the node server corresponding to the area where the user is located for the user side to log in the cloud game, and the user performs game operation on the user side, so that the user side can upload a corresponding operation instruction to the node server. Then, the node server can calculate and generate a game picture by combining the operation instruction based on the execution logic of the cloud game program, and then feed the game picture back to the user side for display.

Operation and maintenance server

The operation and maintenance server 12 is at least used for updating the game. In some embodiments, the operation and maintenance server 12 may receive a game update request sent by the request terminal 11, where the game update request includes game update information, and then determine at least one channel to be updated 13 based on the game update information. In some embodiments, the operation and maintenance server 12 may put down the game to be updated for each channel 13 to be updated, so that the user can see the putting-down status of the game during the game updating process, and further know that the game is being updated, thereby avoiding using the wrong version of the game during the game updating process. In some embodiments, the operation and maintenance server 12 may update the game information of the game to be updated based on the game update information, where the game to be updated may be a game on the shelf or a game to be updated specified in the game update request. In some embodiments, the operation and maintenance server 12 may send the deployment notification to a plurality of game servers under the jurisdiction of the channel to be updated 13, so that the game servers deploy resources required by the game to be updated.

Game server

The channel to be updated 13 manages a plurality of Game servers, wherein the Game servers, i.e. Game Service components (GS), operate in the cloud Game server, i.e. the Game servers belong to a part of the cloud Game server. The game server is used for controlling game examples and providing cloud game services for the user side. In some embodiments, the game server configures (through the operation and maintenance system or a person) channel identifiers of channels supported by the game server, area information of an area to which the game server belongs and corresponding operator information, and a list of game identifiers supported by the game server before starting.

In some embodiments, the game server is configured to control game instances, provide cloud service resources for the client to execute a cloud game, encode video frame audio frames of the cloud game, and stream the encoded video frame audio frames to the cloud game client for rendering and user interaction. In some embodiments, the game server is at least configured to obtain an operation instruction uploaded by the cloud game client, calculate and generate a game screen in combination with the operation instruction based on execution logic of the cloud game program, and then feed back the game screen to the user side for display. In some embodiments, the game server may be a software device, a hardware device, or a combination of software and hardware.

Fig. 2 is a block diagram of a game update apparatus 20 according to an embodiment of the present disclosure. In some embodiments, the game update apparatus 20 may be implemented as the operation and maintenance server 12 or a part of the operation and maintenance server 12 in fig. 1. As shown in FIG. 2, the game update apparatus 20 may include, but is not limited to, the following elements: an acquisition unit 21, a determination unit 22, a shelving unit 23, an update unit 24, and a transmission unit 25. The units are described in detail as follows:

acquisition unit

An obtaining unit 21 is configured to obtain a game update request, where the game update request includes game update information. The game update request is sent by the request terminal 11 shown in fig. 1. If the request end 11 is the operation and maintenance server 12 itself, the obtaining unit 21 directly obtains the game update obtaining request generated by the operation and maintenance server 12 itself, and there is no need to send an action; if the request end 11 is not the operation and maintenance server 12 itself, the obtaining unit 21 receives the game update request sent by the request end 11.

In some embodiments, the game update information may include a game identification of the game to be updated. After acquiring the game update request, the acquiring unit 21 may further acquire the game identifier of the game to be updated included in the game update information, and further definitely update the game whose object is the game corresponding to the game identifier.

In some embodiments, the game update information may include first game information for the game to be updated. The first game information may include, but is not limited to, one or more of the following: game-self information and game-related information. The game itself information may include, but is not limited to, one or more of the following: game description, game version, game installation package information, etc. Game related information may include, but is not limited to, one or more of the following: the GS comprises a current cloud control simulation mode, a cloud rendering mode, a video and audio capturing mode, a coding mode, coding parameters and the like.

In some embodiments, the game update information may include first configuration information. It should be noted that, whether updating or not, each game has configuration information corresponding to itself, and each game has only one type of configuration information at the same time before or after updating. In some embodiments, the configuration information is in a one-to-one correspondence with the game identification.

In some embodiments, the first configuration information may include, but is not limited to: the information of each configuration item of the game and the related service components thereof is to be updated. It should be noted that each game and its related service components constitute an environment necessary for each game to be able to normally run on the cloud game service end and normally provide the cloud game service. In some embodiments, relevant service components may include, but are not limited to, one or more of the following: GS, game virtual device component, service QoS data collection component, and service log component, among others. In some embodiments, the information for each configuration item may include, but is not limited to, one or more of the following: version of the component, target configuration (such as source, resolution of the video capture component, frequency, channel of the audio capture component, algorithm to encode the component, bitrate, etc.), deployment script of the component, etc.

In some embodiments, the game update information may include game deployment scripts. The game deployment script is an executable file. After the game deployment script is executed, a game deployment task may be triggered. Game deployment tasks include, for example, but are not limited to, one or more of the following: downloading, upgrading and/or installing the game to be updated, and downloading, upgrading and/or installing the service components related to the game to be updated.

In some embodiments, the game update information may include a channel identifier (i.e., a channel ID) that specifies a channel for which the game update is intended, i.e., the game to be updated is updated in the channel corresponding to the channel identifier. Even if other channels have the game to be updated, the game cannot be updated. For example, if channel a, channel B, and channel C all have game a, but the game update information includes the channel identifier of channel a, only game a in channel a is updated, and game a in channel B and channel C is not updated. In some embodiments, if the game update information does not include a channel identification, the game to be updated in all channels containing the game to be updated is updated by default.

Determining unit

The determining unit 22 is configured to determine one or more channels to be updated. The channel to be updated is a channel containing the game to be updated. In some embodiments, the determination unit 22 determines at least one channel to be updated based on the game update information and preset one or more channel information. It should be noted that, if only one channel is preset by the operation and maintenance server, the determining unit 22 determines at most one channel to be updated based on the game update information and the preset channel information.

In some embodiments, if the determining unit 22 determines that all the preset channels are not channels to be updated, the update failure information is fed back as the game update response to the requesting end. It should be noted that, if the request end is the operation and maintenance server itself, the operation and maintenance server may directly obtain the game update response generated by the determining unit 22, and the determining unit 22 does not need to send an action (game update response); if the request end is not the operation and maintenance service end, the determining unit 22 sends a game update response to the request end.

In some embodiments, the channel information includes a first game list of channels, the first game list including a game identification for each game. Typically there are multiple games under a channel, then the first game list for that channel includes the game identification for each of the multiple games. The determining unit 22 may determine the game identifier of the game to be updated included in the game update information, and further search for the game identifier of the game to be updated from the one or more first game lists, that is, search for the first game list having the game identifier of the game to be updated, so as to determine the channel corresponding to the searched first game list as the channel to be updated.

In some embodiments, the channel information includes a second channel identification, and if the game update request includes a first channel identification, the determining unit 22 determines the channel information matching the first channel identification, e.g., the determining unit 22 determines whether the first channel identification is the same as the second channel identification of any of the channel information, and if so, determines that the channel information matches the first channel identification. Further, the determining unit 22 searches the first game list included in the channel information matched with the first channel identifier to determine whether the first game list includes the game identifier of the game to be updated, and if the game identifier of the game to be updated is found, determines the channel matched with the first channel identifier as the channel to be updated.

In some embodiments, the first game list may include a game status for each game in addition to the game identification for each game. The game state is, for example, a lower state, an upper state or a running state. The off-shelf status indicates that the game is being updated. The on shelf status indicates that the game is updated and can be run. The running state indicates that the game is running.

In some embodiments, the first game list may include second game information for each game, which may include, but is not limited to, one or more of the following: game-self information and game-related information. The game itself information may include, but is not limited to, one or more of the following: game description, game version, game installation package information, etc. Game related information may include, but is not limited to, one or more of the following: the GS comprises a current cloud control simulation mode, a cloud rendering mode, a video and audio capturing mode, a coding mode, coding parameters and the like.

Lower rack unit, update unit and transmission unit

And the shelving unit 23 is configured to, for each channel to be updated, shelving the game to be updated corresponding to the channel to be updated. In some embodiments, the shelving unit 23 sets the game state of the game to be updated in the first game list of the channel to be updated to a shelving state, so that the user determines that the game is shelved and is being updated based on the shelving state, and further does not request the game, thereby avoiding the problem of poor user experience caused by the game not being played.

In some embodiments, for each channel to be updated, the channel to be updated may correspond to one or more User Agents (UAs). After the shelving unit sets the game state of the game to be updated to be the shelving state, each UA displays that the game is being updated when acquiring the game to be updated. The method for acquiring the game to be updated includes, but is not limited to, one or more of the following: the first method is as follows: sending a cloud game request to a cloud game service end, wherein the cloud game request carries a game identifier of the game to be updated; the second method comprises the following steps: and acquiring the state of the game to be updated, such as acquiring a game list, wherein the game list comprises the game identifier and the game state of the game to be updated. It should be noted that all the acquisition behaviors related to the game during the game update process should show that the game is being updated.

And the updating unit 24 is used for updating the game information of the game to be updated based on the game updating information for each channel to be updated. In some embodiments, the updating unit 24 may update the game information of the game to be updated after the off-shelf unit 23 off-shelves the game to be updated based on the game update information. In some embodiments, the updating unit 24 replaces the second game information of the game to be updated in the first game list of the channel to be updated with the first game information in the game update information. For example, the updating unit 24 may determine second game information that matches the first game information in the game update information, and then replace the second game information with the first game information. For example, the matching is that the game identifier corresponding to the first game information is the same as the game identifier corresponding to the second game information. The second game information is the game information of the game to be updated in the first game list of the channel to be updated.

And a sending unit 25, configured to send, for each channel to be updated, a deployment notification to a plurality of game servers governed by the channel to be updated, so that each game server deploys resources required by the game to be updated based on the deployment notification. The resources are servers used by the cloud game server to install and run games, and the game server is responsible for deploying the servers. In some embodiments, the resource may be a virtual machine or a physical machine. For example, for a game of the android system, the resource may be an android simulator, a physical cloud phone, or a virtual cloud phone.

In some embodiments, the deployment notification may include, but is not limited to: the method comprises the steps of updating first game information, first configuration information, a game deployment script and the like of a game to be updated. The process that each game server deploys the resources required by the game to be updated based on the deployment notification is as follows: and generating second configuration information based on the first game information and the first configuration information of the game to be updated, and executing the game deployment script. The second configuration information is configuration information stored in resources required by the game to be updated, that is, the second configuration information may be understood as local configuration information of the game to be updated, and "local" refers to a server which is responsible for deployment by the game server. As can be seen, the second configuration information may be understood as local configuration information generated by the deployment process based on the first configuration information. In addition, the game server executes the game deployment script, and can complete local downloading, upgrading, and/or installation of the game to be updated and the related service components thereof, namely the game server completes the deployment of the server responsible for the game to be updated.

It should be noted that, due to different versions of the machine environment or the game server, the second configuration information generated by the concurrent deployment of each game server may be different. If the version of the machine environment is the same as that of the game server, the second configuration information generated by the simultaneous and parallel deployment of each game server may be the same.

In some embodiments, the second configuration information may include, but is not limited to: the information of each configuration item of the game and the related service components thereof is to be updated. In some embodiments, relevant service components may include, but are not limited to, one or more of the following: GS, game virtual device component, service QoS data collection component, and service log component, among others. In some embodiments, the information for each configuration item may include, but is not limited to, one or more of the following: version of the component, target configuration (such as source, resolution of the video capture component, frequency, channel of the audio capture component, algorithm to encode the component, bitrate, etc.), deployment script of the component, etc.

In some embodiments, the sending unit 25 may obtain, for each channel to be updated, a game server list governed by the channel to be updated, where the game server list includes GS information of each game server governed by the channel to be updated, and the GS information may include, but is not limited to, one or more of the following: GS identification (GSID), GS state, GS version number, GS command line, second game list (i.e., list of games that GS has now deployed), etc. Further, the sending unit 25 sends a deployment notification to each game server in the game server list governed by the channel to be updated, for each channel to be updated.

In some embodiments, the sending unit 25 may, for each channel to be updated, batch a plurality of game servers belonging to the channel to be updated, and send the deployment notification to each game server belonging to the same batch each time. The batch can be one game server or a plurality of game servers. Therefore, in the process of updating the game to be updated, the game server which is administered by the channel to be updated and does not receive the deployment notification can still provide other games (namely games not to be updated) for the user to play, and meanwhile, the user can also see the off-shelf state of the game to be updated, so that the user can know that the game to be updated is updated, and the wrong version of the game to be updated is prevented from being used in the process of updating the game to be updated.

In some embodiments, after the sending unit 25 batches, for each channel to be updated, a plurality of game servers governed by the channel to be updated, the deployment notification may be sent to each game server of the same batch each time based on a preset sending policy. The sending policy is, for example: and if the number of the game servers returning the deployment result is less than that of the game servers administered by the channel to be updated, continuing to send deployment notification to the game servers belonging to the same batch. In some embodiments, the sending unit 25 may wait for that a batch of the deployment notifications sent last time all have corresponding deployment results, that is, after all the game servers that receive the deployment notifications all return the deployment results, the sending unit 25 sends the deployment notifications to the game servers of the next batch that is the same as the batch. For example, if the waiting time length exceeds a preset time length and the game server does not return the deployment result, the sending unit 25 sends a deployment notification to each game server of the same subordinate next batch. For another example, if the preset time length is infinite, the sending unit 25 may wait until all game servers receiving the deployment notification return the deployment result, and the sending unit 25 sends the deployment notification to the next group of game servers belonging to the same category. For another example, if the preset time length is zero, the sending unit 25 does not wait, and directly sends the deployment notification to each game server in the next batch of the same category.

After receiving the deployment notification, the game service end (GS) may directly notify a User end (UA) that the game service is currently being serviced, so that the UA requests another GS to continue the cloud game service of the current game from the cloud game service end. Furthermore, when the GS receiving the deployment notification receives a successful connection between the UA and another GS or reaches a predetermined timeout value, the GS disconnects the connection with the UA, that is, the cloud game service is ended this time, and the GS receiving the deployment notification starts processing the current deployment notification. In some embodiments, the GS receiving the deployment notification first determines whether its own state is idle, and if the cloud game service is being provided to the outside, the deployment notification is cached to the end of the local deployment scheduling queue, and when the cloud game service to the outside is finished, that is, the GS receiving the deployment notification has its own state idle, the GS processes the cached deployment notifications one by one from the local deployment queue.

In some embodiments, after the sending unit 25 sends the deployment notification, the state (i.e., the GS state) of each game server receiving the deployment notification is modified to the in-deployment state. It should be noted that before the game server receives the deployment notification, the GS state may be idle, occupied, or other state that is not being deployed, and after the sending unit 25 sends the deployment notification to the game server, the state of the game server is modified to be the deployment state.

In some embodiments, after sending the deployment notification, the sending unit 25 may obtain a deployment result of each game server receiving the deployment notification on resources required by the game to be updated. Wherein the deployment result is a result of successful deployment or a result of failed deployment. The results of successful deployment may include, but are not limited to: information for describing successful deployment, identification of the Game Server (GSID), game identification, second configuration information and the like. The results of the deployment failure may include, but are not limited to: and information for describing deployment failure and failure information, wherein the failure information comprises an error code or error information. When the game server detects that any abnormity exists in the deployment process and the deployment cannot be completed smoothly, a result of failed deployment can be generated.

In some embodiments, the sending unit 25 may update the information (i.e., the GS information) and the status (i.e., the GS status) of the corresponding game server based on the deployment result. Wherein, the corresponding game server can be understood as the game server which sends the deployment result.

For example, the deployment result is a successful deployment result, the second configuration information in the deployment result is updated to the second game list of the GS information of the corresponding game server, and the state of the corresponding game server is set to the idle state.

For another example, the deployment result is a result of a failed deployment, the specific situation or classification of the failed deployment is determined based on the error code or the error information, and accordingly, if the corresponding game server can continue to provide external services, the state of the corresponding game server is set to be an idle state; and if the corresponding game server cannot continuously provide the service to the outside, setting the state of the corresponding game server to be an abnormal state.

In some embodiments, the sending unit 25 may send a game update response to the requesting end based on the deployment result, the game update response including the updated channel identification and the updated game identification. It should be noted that, if the request end is the operation and maintenance server itself, the operation and maintenance server may record the updated channel identifier and the updated game identifier, that is, the sending unit 25 does not need to send the action; if the request end is not the operation and maintenance server end itself and the request end sends the game update request, the sending unit 25 sends a game update response to the request end. In some embodiments, the sending unit 25 sends a game update response to the requesting end based on the deployment result being the first successful deployment result, where the game update response includes the updated channel identifier and the updated game identifier. Therefore, as long as at least one game server finishes deployment, the request end can be informed of finishing the updating of the game to be updated, the cloud game service of the game to be updated can be provided for the user without waiting for other game servers to finish deployment, and the time for the user to wait for the updating of the game is shortened.

In some embodiments, the sending unit 25 may count, for each channel to be updated, the number of GS of the deployment result returned in the channel to be updated, and if the number of GS is equal to the number of GS governed by the channel to be updated, indicate that all GS governed by the channel to be updated have completed deployment of resources required by the game to be updated, and end the GS batch sending of the deployment notification to the channel to be updated.

Racking unit

In some embodiments, the game update apparatus 20 may also include a racking unit not shown in FIG. 2. And the shelving unit is used for acquiring a game shelving request, and the game shelving request comprises a channel identifier and a game identifier. In some embodiments, the requesting end sends the game listing request after receiving the game update response. In some embodiments, an operation and maintenance person can directly send a request for obtaining a GS information list of a certain channel to an operation and maintenance server through a request end, then test a manual or automatic script on GS with updated games, and send a game listing request according to a test result.

In this way, the listing unit determines that the game corresponding to the game identifier needs to be listed on the channel corresponding to the channel identifier based on the channel identifier and the game identifier included in the game listing request. It should be noted that the channel identifier and the game identifier included in the game listing request may not be the updated channel identifier and the updated game identifier included in the game update response, that is, the game listing request may be initiated for any game in any channel.

In some embodiments, the shelving unit may count the number of game servers for the deployment result of the game identifier returned under the channel corresponding to the channel identifier. Furthermore, the shelving unit sets the game corresponding to the game identifier in the channel corresponding to the channel identifier to be in a shelving state based on at least one successful deployment result. In addition, the shelving unit keeps the game corresponding to the game identifier in the channel corresponding to the channel identifier in a shelving status based on the result that the deployment is not successful.

Therefore, after the shelving unit sets the game corresponding to the game identifier under the channel corresponding to the channel identifier to be in a shelving state, any User Agent (UA) belonging to the channel corresponding to the channel identifier displays that the game corresponding to the game identifier is normally available when the game information or the game state of the game identifier is acquired. Similarly, when the other channels UA acquire the game information or the game state of the game identifier, the current state of the game corresponding to the game identifier in the channel to which the channel belongs is correspondingly displayed.

In some embodiments, the division of each unit in the game update apparatus 20 is only one logical function division, and there may be another division manner when the actual implementation is performed, for example, at least two units of the obtaining unit 21, the determining unit 22, the shelving unit 23, the updating unit 24 and the sending unit 25 may be implemented as one unit; the acquisition unit 21, the determination unit 22, the shelving unit 23, the update unit 24, or the transmission unit 25 may also be divided into a plurality of sub-units. It will be understood that the various units or sub-units may be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application.

Fig. 3 is a multi-end interaction diagram in a game updating process according to an embodiment of the present application, and as shown in fig. 3, a game updating process includes the following steps 301 to 311:

in step 301, the request end sends a game update request to the operation and maintenance service end, where the game update request includes game update information. The game update information may include a game identification of the game to be updated, first game information, first configuration information, and a game deployment script.

In step 302, the operation and maintenance service end determines at least one channel to be updated based on the game update information and preset one or more channel information. The channel information comprises a first game list of the channel, and the first game list comprises a game identifier of each game, a game state of each game and second game information of each game. For example, the operation and maintenance server searches a first game list with game identifiers of the games to be updated; and determining the channel corresponding to the searched first game list as the channel to be updated.

In step 303, the operation and maintenance service end puts down the games to be updated corresponding to each channel to be updated. For example, the operation and maintenance service end sets the game state of the game to be updated corresponding to each channel to be updated to be the off-shelf state.

In step 304, the operation and maintenance server updates the game information of the game to be updated based on the game update information. For example, the operation and maintenance server replaces the second game information of the game to be updated in the first game list of the channel to be updated with the first game information for each channel to be updated.

In step 305, the operation and maintenance server sends a deployment notification to a plurality of game servers governed by the channel to be updated for each channel to be updated. For example, two game servers are administered by one channel to be updated, and the operation and maintenance server can respectively send deployment notifications to the two game servers. The deployment notification comprises first game information, first configuration information and a game deployment script of the game to be updated.

In step 306, the game server deploys the resources required for the game to be updated based on the deployment notification. For example, the game server generates second configuration information based on first game information and first configuration information of a game to be updated, and executes a game deployment script; the second configuration information is the configuration information stored in the resources needed by the game to be updated.

In step 307, if the game server is successfully deployed, the game server sends a deployment result to the operation and maintenance server, where the deployment result is successful and includes: information for describing successful deployment, identification of the Game Server (GSID), game identification, second configuration information and the like. If the game server fails to deploy, sending a deployment result to the operation and maintenance server, wherein the deployment result is a failure, and comprises: information for describing a deployment failure and failure information, wherein the failure information includes, for example, an error code or error information.

In step 308, the operation and maintenance server updates the information and status of the corresponding game server based on the deployment result. For example, the deployment result is a successful deployment result, the second configuration information in the deployment result is updated to the second game list of the GS information of the corresponding game server, and the state of the corresponding game server is set to the idle state. For another example, the deployment result is a result of a failed deployment, the specific situation or classification of the failed deployment is determined based on the error code or the error information, and accordingly, if the corresponding game server can continue to provide external services, the state of the corresponding game server is set to be an idle state; and if the corresponding game server cannot continuously provide the service to the outside, setting the state of the corresponding game server to be an abnormal state.

In step 309, the operation and maintenance service end sends a game update response to the request end based on the deployment result being the first successful deployment result. The game update response includes the updated channel identification and the updated game identification. Therefore, as long as at least one game server finishes deployment, the request end can be informed of finishing the updating of the game to be updated, the cloud game service of the game to be updated can be provided for the user without waiting for other game servers to finish deployment, and the time for the user to wait for the updating of the game is shortened.

In step 310, the request end sends a game listing request to the operation and maintenance service end, wherein the game listing request comprises a channel identifier and a game identifier. It should be noted that the channel identifier and the game identifier included in the game listing request may not be the updated channel identifier and the updated game identifier in step 309, that is, the game listing request may be initiated for any game in any channel.

In step 311, based on the channel identifier and the game identifier in the game listing request, the operation and maintenance server counts the number of game servers corresponding to the deployment result of the game identifier returned by the channel corresponding to the channel identifier. And further, the operation and maintenance server sets the game corresponding to the game identifier in the channel corresponding to the channel identifier to be in an on-shelf state based on at least one deployment result as success.

Therefore, after the operation and maintenance server sets the game corresponding to the game identifier in the channel corresponding to the channel identifier to be in the on-shelf state, any User Agent (UA) belonging to the channel corresponding to the channel identifier displays that the game corresponding to the game identifier is normally available when the game information or the game state of the game identifier is acquired.

The embodiment of the application also provides the electronic equipment. In some embodiments, the electronic device may be implemented as the operation and maintenance server 12 or a portion of the operation and maintenance server 12 in fig. 1. As shown in fig. 4, the electronic apparatus 40 includes: a processor 41 and a memory 43. Wherein the processor 41 is coupled to the memory 43, such as via the bus 42. Further, the electronic device 4 may also include a transceiver 44. It should be noted that the transceiver 44 is not limited to one in practical application, and the structure of the electronic device 4 is not limited to the embodiment of the present application.

The processor 41 is applied to the embodiment of the present application, and is used to implement the functions of the game update apparatus 20 shown in fig. 2.

Processor 41 may be a CPU, general purpose processor, DSP, ASIC, FPGA or other programmable logic device, transistor logic device, hardware component, or any combination thereof. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. Processor 41 may also be a combination of computing functions, e.g., comprising one or more microprocessors, DSPs, and microprocessors, among others.

Bus 42 may include a path that transfers information between the aforementioned components. The bus 42 may be a PCI bus or an EISA bus, etc. The bus 42 may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown in FIG. 4, but this does not indicate only one bus or one type of bus.

The memory 43 may be, but is not limited to, a ROM or other type of static storage device that can store static information and instructions, a RAM or other type of dynamic storage device that can store information and instructions, an EEPROM, a CD-ROM or other optical disk storage, optical disk storage (including compact disk, laser disk, optical disk, digital versatile disk, blu-ray disk, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.

The memory 43 is used for storing application program codes for executing the scheme of the application, and is controlled by the processor 41 to execute. The processor 41 is configured to execute application code stored in the memory 43 to implement the actions of the game update apparatus 20.

The electronic device provided by the embodiment of the application comprises a memory, a processor and a computer program which is stored on the memory and can run on the processor, when the processor executes the program, compared with the prior art, by adding game update information to a game update request, and further, after obtaining the game update request, at least one channel to be updated can be determined based on the game update information, thereby, for each channel to be updated, the game to be updated is off-shelf, the game information of the game to be updated is updated based on the game update information, and sending the deployment notification to a plurality of game servers under the jurisdiction of the channel so as to enable the game servers to deploy the resources required by the game to be updated, thus, in the process of updating the game, the user can see the off-shelf state of the game, further know that the game is being updated and avoid using the wrong version of the game in the process of updating the game.

Embodiments of the present application provide a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and the computer program, when executed by a processor, implements steps of each embodiment of a game update method, and is not described herein again to avoid repetition.

Fig. 5 is a flowchart of a game updating method provided in an embodiment of the present application, where the method is applied to an operation and maintenance server, and may include the following steps 501 to 505:

in step 501, the operation and maintenance server obtains a game update request, where the game update request includes game update information.

In step 502, the operation and maintenance service end determines at least one channel to be updated based on the game update information and preset one or more channel information.

In some embodiments, the game update information includes a game identification of the game to be updated; the channel information includes a first game list of channels, the first game list including a game identification of each game. And when the operation and maintenance service terminal determines at least one channel to be updated based on the game updating information and the preset one or more channel information, determining the channel corresponding to the found first game list as the channel to be updated by searching the first game list with the game identifier of the game to be updated.

In step 503, the operation and maintenance server puts down the game to be updated corresponding to each channel to be updated.

In some embodiments, the first game list further includes a game state for each game. When the operation and maintenance server puts the game to be updated corresponding to the channel to be updated off shelf, the game state of the game to be updated in the first game list of the channel to be updated can be set to be the off shelf state.

In step 504, the operation and maintenance server updates the game information of the game to be updated based on the game update information for each channel to be updated.

In some embodiments, the game update information further includes first game information of the game to be updated; the first game list further includes second game information for each game. And when the operation and maintenance server updates the game information of the game to be updated on the basis of the game updating information, replacing the second game information of the game to be updated in the first game list of the channel to be updated with the first game information.

In step 505, the operation and maintenance server sends a deployment notification to a plurality of game servers governed by the channel to be updated, so that each game server deploys resources required by the game to be updated based on the deployment notification.

In some embodiments, the game update information further includes the first configuration information and the game deployment script. The deployment notification includes first game information, first configuration information, and a game deployment script for the game to be updated. When each game server deploys resources required by the game to be updated based on the deployment notification, generating second configuration information based on the first game information and the first configuration information of the game to be updated, and executing a game deployment script; the second configuration information is the configuration information stored in the resources needed by the game to be updated.

In some embodiments, when the operation and maintenance server sends the deployment notification to the plurality of game servers belonging to the channel to be updated, the plurality of game servers belonging to the channel to be updated are batched, and the deployment notification is sent to each of the game servers belonging to the same batch each time based on a preset sending strategy.

In some embodiments, the sending policy comprises: and if the number of the game servers returning the deployment result is less than that of the game servers administered by the channel to be updated, continuing to send deployment notification to the game servers belonging to the same batch.

In some embodiments, after the operation and maintenance server sends the deployment notification, the state of the corresponding game server may be further modified to be the deployment state.

In some embodiments, the operation and maintenance server can also obtain the deployment result of each game server on the resources required by the game to be updated; and then updating the information and the state of the corresponding game server based on the deployment result.

In some embodiments, the deployment result comprises: the information used for describing the successful deployment, the identification of the game server, the game identification and the second configuration information; or, information for describing deployment failure and failure information.

In some embodiments, the operation and maintenance server receives a game update request sent by the request end, and further sends a game update response to the request end based on the deployment result; the game update response includes the updated channel identification and the updated game identification. In some embodiments, when the operation and maintenance server sends the game update response to the request terminal based on the deployment result, the operation and maintenance server sends the game update response to the request terminal based on the deployment result as the first successful deployment result.

In some embodiments, the operation and maintenance server may further obtain a game listing request, where the game listing request includes a channel identifier and a game identifier; further counting the number of game servers aiming at the deployment result of the game identifier returned under the channel corresponding to the channel identifier; and thus, if at least one deployment result is successful, setting the game corresponding to the game identifier in the channel corresponding to the channel identifier as the on-shelf state.

It can be seen that, by adding the game update information to the game update request, and then after obtaining the game update request, determining at least one channel to be updated based on the game update information, for each channel to be updated, shelving the game to be updated, updating the game information of the game to be updated based on the game update information, and sending a deployment notification to a plurality of game servers under the jurisdiction of the channel, so that the game servers deploy resources required by the game to be updated, in this way, in the game update process, a user can see the shelving state of the game, and further know that the game is being updated, and avoid using an incorrect version of the game in the game update process.

It should be understood that, although the steps in the flowcharts of the figures are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and may be performed in other orders unless explicitly stated herein. Moreover, at least a portion of the steps in the flow chart of the figure may include multiple sub-steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, which are not necessarily performed in sequence, but may be performed alternately or alternately with other steps or at least a portion of the sub-steps or stages of other steps.

The foregoing is only a partial embodiment of the present application, and it should be noted that, for those skilled in the art, several modifications and decorations can be made without departing from the principle of the present application, and these modifications and decorations should also be regarded as the protection scope of the present application.

Claims

1. A game update method, the method comprising:

for each channel to be updated:

2. The method of claim 1, wherein the game update information includes a game identifier of a game to be updated; the channel information comprises a first game list of channels, wherein the first game list comprises game identification of each game;

3. The method of claim 2, wherein the first game list further comprises a game status for each game;

4. The method according to claim 2, wherein the game update information further includes first game information of the game to be updated, and the first game list further includes second game information of each game;

5. The method of claim 2, wherein the game update information further comprises first configuration information and a game deployment script; the deployment notification comprises first game information of the game to be updated, the first configuration information and the game deployment script;

6. The method of claim 1, wherein said sending a deployment notification to a plurality of game servers governed by the channel to be updated comprises:

batching a plurality of game servers belonging to the channel to be updated;

7. The method of claim 6, wherein the transmission policy comprises: and if the number of the game servers returning the deployment result is less than that of the game servers administered by the channel to be updated, continuing to send deployment notification to the game servers belonging to the same batch.

8. A game update apparatus, the apparatus comprising:

for each channel to be updated:

an updating unit configured to update game information of the game to be updated based on the game update information;

9. An electronic device comprising a processor and a memory;

the processor is adapted to perform the steps of the method of any one of claims 1 to 7 by calling a program or instructions stored in the memory.

10. A non-transitory computer-readable storage medium storing a program or instructions for causing a computer to perform the steps of the method according to any one of claims 1 to 7.