CN112604295A

Movatterモバイル変換

Info

Publication number: CN112604295A
Application number: CN202011603987.8A
Authority: CN
Inventors: 叶川; 梁波
Original assignee: Zhuhai Seasun Mobile Game Technology Co ltd; Zhuhai Kingsoft Online Game Technology Co Ltd
Current assignee: Zhuhai Seasun Mobile Game Technology Co ltd; Zhuhai Kingsoft Online Game Technology Co Ltd
Priority date: 2020-12-29
Filing date: 2020-12-29
Publication date: 2021-04-06

Abstract

The present specification provides a method and an apparatus for reporting a game update failure, a method for managing the game update failure, and a server, wherein the method for reporting the game update failure includes: determining whether a target updating stage of a game to be updated is updated successfully, wherein the target updating stage is any updating stage included in an updating process of the game to be updated; under the condition that the target updating stage fails to update, generating updating failure information according to the target updating stage; and reporting the update failure information to a server. Therefore, the game client fails at any update stage in the game update process, which causes the failure of game update, and reports the failed target update stage in real time, so that the specific update stage of the game client which fails in the game update process can be known in time, and the specific reason of the failure of game update can be determined quickly and accurately.

Description

Method and device for reporting game update failure, management method and server

Technical Field

The present disclosure relates to the field of internet technologies, and in particular, to a method and an apparatus for reporting a game update failure, a method for managing the game update failure, and a server.

Background

With the rapid development of internet technology and computer technology, the game technology is mature, more and more games are produced, and the games become essential life and entertainment for most people. As the memory occupied by the game client side is larger and larger, the game update is easy to fail due to some reasons in the game update process.

In the prior art, if a game fails to be updated, a player needs to manually seek help from a worker through a game client, and specifically, the worker can remotely assist the player to obtain a game update log of the game client after obtaining the consent of the player; alternatively, the player packages the game update log via a game diagnostic tool attached to the game client. And then, the player can transmit the obtained game update log to the equipment of the staff through the communication software, and the staff analyzes the update data in the game update log to determine the reason of the failure of the game update.

However, in the above manner, after the game update fails, the client reports the game update log to the device of the staff, and subsequently, the staff needs to analyze the game update log one by one to determine the reason of the game update failure, which results in a complex process of analyzing the reason of the game update failure, and a simpler and more convenient method is further needed to perform reporting operation or processing of the game update failure, so that the reason of the game update failure can be determined simply and quickly.

Disclosure of Invention

In view of this, an embodiment of the present disclosure provides a method for reporting a game update failure. The present specification also relates to a device for reporting a game update failure, a method and a server for managing a game update failure, a computing device, and a computer-readable storage medium, so as to solve technical defects in the prior art.

According to a first aspect of the embodiments of the present specification, there is provided a method for reporting a game update failure, including:

determining whether a target updating stage of a game to be updated is updated successfully, wherein the target updating stage is any updating stage included in an updating process of the game to be updated;

under the condition that the target updating stage fails to update, generating updating failure information according to the target updating stage;

and reporting the update failure information to a server.

According to a second aspect of embodiments of the present specification, there is provided a management method of a game update failure, including:

receiving update failure information reported by a game client, wherein the update failure information carries attribute information of a target update stage, attribute information of a game to be updated and user information, and the target update stage is an update stage of update failure in an update process of the game to be updated;

classifying and storing the update failure information;

and under the condition of receiving an update failure query instruction, acquiring and returning corresponding update failure information according to query parameters carried by the update failure query instruction.

According to a third aspect of the embodiments of the present specification, there is provided an apparatus for reporting a game update failure, including:

the game updating method comprises a determining module, a judging module and a processing module, wherein the determining module is configured to determine whether a target updating stage of a game to be updated is updated successfully or not, and the target updating stage is any updating stage included in an updating process of the game to be updated;

the first generation module is configured to generate update failure information according to the target update stage under the condition that the target update stage fails to update;

and the reporting module is configured to report the update failure information to a server.

According to a fourth aspect of embodiments herein, there is provided a game update failure management server including:

the game updating system comprises a receiving module, a processing module and a processing module, wherein the receiving module is configured to receive updating failure information reported by a game client, the updating failure information carries attribute information of a target updating stage, attribute information of a game to be updated and user information, and the target updating stage is an updating stage of updating failure in an updating process of the game to be updated;

the storage module is configured to classify and store the update failure information;

the obtaining module is configured to obtain and return the update failure information corresponding to the update failure query instruction under the condition that the update failure query instruction is received.

According to a fifth aspect of embodiments herein, there is provided a computing device comprising:

a memory and a processor;

the memory is configured to store computer-executable instructions, and the processor is configured to execute the computer-executable instructions to implement the method of:

determining whether a target updating stage of a game to be updated is updated successfully, wherein the target updating stage is any updating stage included in an updating process of the game to be updated; under the condition that the target updating stage fails to update, generating updating failure information according to the target updating stage; reporting the update failure information to a server; or,

receiving update failure information reported by a game client, wherein the update failure information carries attribute information of a target update stage, attribute information of a game to be updated and user information, and the target update stage is an update stage of update failure in an update process of the game to be updated; classifying and storing the update failure information; and under the condition of receiving an update failure query instruction, acquiring and returning update failure information corresponding to the update failure query instruction.

According to a sixth aspect of the embodiments of the present specification, there is provided a computer-readable storage medium storing computer-executable instructions, which when executed by a processor, implement the steps of the method for reporting a game update failure or the method for managing a game update failure.

The method for reporting game update failure provided by the present specification can determine whether a target update stage of a game to be updated is successfully updated, where the target update stage is any update stage included in an update process of the game to be updated; under the condition that the target updating stage fails to update, generating updating failure information according to the target updating stage; and reporting the update failure information to a server. Under the condition, the game client fails at any update stage in the game update process, so that the game update failure is caused, and the failed target update stage is reported in real time, so that a worker can timely know the specific update stage of the game client which fails in the game update process through the server, quickly and accurately determine the specific reason of the game update failure, timely take corresponding measures, and ensure the user experience.

The management method for the update failure of the game provided by the specification can receive update failure information reported by a game client, wherein the update failure information carries attribute information of a target update stage, attribute information of the game to be updated and user information, and the target update stage is an update stage of the update failure in an update process of the game to be updated; and then, classifying and storing the update failure information, and acquiring and returning the corresponding update failure information according to the query parameters carried by the update failure query instruction under the condition of receiving the update failure query instruction. Under the condition, the server can receive and store the update failure information reported by each game client, an inquiry interface is provided, and a worker can directly inquire the required update failure information through the server, and can quickly and accurately know which specific update stage fails in the game update process without checking and analyzing the game update logs of each game client one by one, so that the specific reason of the game update failure can be quickly and accurately determined, the countermeasure can be timely taken, and the user experience is ensured.

Drawings

Fig. 1 is a flowchart of a method for reporting a game update failure according to an embodiment of the present disclosure;

FIG. 2 is a flowchart of a method for managing failure of game update according to an embodiment of the present disclosure

Fig. 3 is a flowchart of a method for reporting and managing a game update failure according to an embodiment of the present disclosure;

fig. 4 is a schematic structural diagram of a device for reporting a game update failure according to an embodiment of the present disclosure;

FIG. 5 is a schematic structural diagram of a management server for a game update failure according to an embodiment of the present disclosure;

fig. 6 is a block diagram of a computing device according to an embodiment of the present disclosure.

Detailed Description

In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present description. This description may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein, as those skilled in the art will be able to make and use the present disclosure without departing from the spirit and scope of the present disclosure.

The terminology used in the description of the one or more embodiments is for the purpose of describing the particular embodiments only and is not intended to be limiting of the description of the one or more embodiments. As used in one or more embodiments of the present specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used in one or more embodiments of the present specification refers to and encompasses any and all possible combinations of one or more of the associated listed items.

It will be understood that, although the terms first, second, etc. may be used herein in one or more embodiments to describe various information, these information should not be limited by these terms. These terms are only used to distinguish one type of information from another. For example, a first can also be referred to as a second and, similarly, a second can also be referred to as a first without departing from the scope of one or more embodiments of the present description. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.

In the present specification, a method for reporting a game update failure is provided, and the present specification relates to a device for reporting a game update failure, a method and a server for managing a game update failure, a computing device, and a computer-readable storage medium, which are described in detail in the following embodiments one by one.

Fig. 1 is a flowchart illustrating a method for reporting a game update failure according to an embodiment of the present disclosure, which is applied to a game client, and specifically includes the following steps:

step 102: determining whether a target updating stage of the game to be updated is updated successfully, wherein the target updating stage is any updating stage included in an updating process of the game to be updated.

In practical application, if a game fails to be updated, a player needs to manually seek help from a staff through a game client, the staff acquires a game update log in the game client, and determines the reason of the game failure by analyzing update data in the game update log, wherein the process of analyzing and determining the reason of the game failure is complex.

Therefore, in order to accurately and quickly determine the specific reason of the game update failure, the description provides a method for reporting the game update failure, a game client can determine whether a target update stage of a game to be updated is successfully updated, and the target update stage is any update stage included in an update process of the game to be updated; under the condition that the target updating stage fails to update, generating updating failure information according to the target updating stage; and reporting the update failure information to a server. Under the condition, the failure of the game updating is caused by the failure of the game client at any updating stage in the game updating process, and the target updating stage with the failure is reported in real time, so that a worker can timely know the specific updating stage with the failure of the game client in the game updating process through the server, and quickly and accurately determine the specific reason of the failure of the game updating.

Specifically, the update flow of the game refers to a complete process of updating a certain game, that is, an overall flow from when a player triggers an update of a certain game through a game client to when the game completes the update. The update stage refers to each stage included in the whole update process, that is, each update stage is combined in sequence to form a complete update process, for example, the update stage of the game to be updated may be searching for an update file, downloading an update file, checking an update file, installing an update file, checking a game update, and the like.

It should be noted that searching for the update file refers to searching for a file corresponding to a new game version to be updated of the game to be updated, downloading the update file after searching for the update file, verifying the downloaded update file after completing downloading, determining whether data in the downloaded update file is correct, updating the game to be updated to the corresponding version (i.e., installing the downloaded update file) according to a corresponding rule by using the downloaded update file when determining that the downloaded update file is correct (i.e., the update file passes verification), and after installing the downloaded update file, verifying to determine whether the installed update file is correct and complete, completing game update after the installed update file passes verification (i.e., after the game update passes verification), and ending the whole game update process.

In an optional implementation manner of this embodiment, a game client often experiences multiple update stages when a game is updated, and a problem occurring in any update stage in a complete update process will cause a failure of updating the game, so that in this specification, the whole update process may be divided into multiple small update stages first, which is convenient for separately monitoring update results of the update stages subsequently, that is, before determining whether an update of a target update stage of a game to be updated is successful, the method further includes:

dividing the updating process of the game to be updated to obtain at least two updating stages;

and coding the at least two updating stages to obtain stage identifiers corresponding to the at least two updating stages.

Specifically, the stage identifier is used for uniquely identifying one updating stage, the complete game updating process usually includes a plurality of updating stages, and each updating stage can be distinguished through the stage identifier, so that whether a certain updating stage is updated successfully or not can be further judged subsequently.

It should be noted that, when a game client triggers and updates a game through a preset operation, the game client detects that there is a game to be updated that needs to be updated, and then the game client executes an update operation in sequence according to each update stage in a game update flow, and if a failure occurs in a certain update stage, the update cannot be performed, thereby causing an update failure of the whole game to be updated. Therefore, in order to monitor the updating process of the game to be updated in real time, in this specification, it may be monitored whether the updating is successful in real time for each updating stage of the game to be updated, that is, whether the target updating stage of the game to be updated is updated successfully is determined.

In an optional implementation manner of this embodiment, each update stage returns a corresponding update return value when the update is successful or fails, and the returned update return values are different, and the game client may determine, according to the update return value, whether the current update stage (i.e., the target update stage) is successfully updated, that is, a specific implementation process for determining whether the target update stage of the game to be updated is successfully updated may be as follows:

acquiring a first updating return value of a target updating stage according to a stage identifier of the target updating stage;

determining an update type to which the first update return value belongs;

determining that the target update phase is updated successfully when the first update return value belongs to a first update type;

determining that the target update phase update fails if the first update return value is of a second update type.

It should be noted that, after the update task of each update stage is executed, an update return value of the first update type is returned, so that if the obtained update return value of the target update stage (current update stage) is the first update type, it indicates that all the update tasks of the target update stage are executed, that is, the target update stage is updated successfully; if a fault occurs during the execution of the update task of a certain update stage and the update task is not successfully executed, the update return value of the second update type is returned, so that if the obtained update return value of the target update stage (current update stage) is the second update type, it indicates that the update task of the target update stage is not successfully executed, that is, the update of the target update stage fails. Therefore, through the type of the update return value in the target update stage, the game client can timely know that the target update stage fails, so that the update fails.

In an optional implementation manner of this embodiment, in order to perform more detailed monitoring on each update stage of the update flow, after the update flow is divided to obtain a plurality of update stages, each update stage may be further subdivided, and each update stage is divided into a plurality of smaller update sub-stages, that is, after the update flow of the game to be updated is divided to obtain at least two update stages, the method further includes:

dividing each of the at least two update stages to obtain at least two update sub-stages;

and coding the at least two updating sub-stages to obtain sub-stage identifications corresponding to the at least two updating sub-stages.

Specifically, the sub-phase identifier is used for uniquely identifying one updating sub-phase, each updating phase often includes a plurality of updating sub-phases, each updating sub-phase can be distinguished through the sub-phase identifier, and the updating sub-phases refer to each updating step included in the whole updating phase, that is, each updating sub-phase is a complete updating phase after being combined in sequence, so that it is convenient for further judging which updating sub-phase fails to update in the updating phase in which updating fails. For example, the update stage for installing the update file may be further subdivided into update sub-stages of decompressing, searching for a module to be updated, verifying the module to be updated, attempting to write in the module to be updated, completing installation and verification, and the like.

In the specification, a game client usually experiences a plurality of updating stages when a game is updated, and a problem in any updating stage in a complete updating process can cause the game to be updated unsuccessfully, so that the whole updating process can be divided into a plurality of small updating stages, and the updating result of each updating stage is monitored in real time, so that the related information of updating failure can be fed back in time when the updating failure is caused by the failure in any updating stage subsequently. In addition, each update stage can be further divided more finely in the present specification, so that it is convenient to determine in detail which update sub-stage fails in the update stage in which the update fails.

Step 104: and under the condition that the target updating stage fails to update, generating updating failure information according to the target updating stage.

Specifically, on the basis of determining whether the target updating stage of the game to be updated is successfully updated, further, under the condition that the target updating stage is unsuccessfully updated, updating failure information is generated according to the target updating stage.

In an optional implementation manner of this embodiment, in order to facilitate obtaining information related to a target update stage in which update fails, attribute information related to the target update stage needs to be carried when generating the update failure information, that is, according to the target update stage, the generating of the update failure information includes:

determining attribute information of the target updating stage according to the first updating return value of the target updating stage;

acquiring attribute information and user information of the game to be updated;

and generating the update failure information according to the attribute information of the target update stage, the attribute information of the game to be updated and the user information.

Specifically, the attribute information of the target update stage includes a stage identifier of the target update stage, a target file name, a failure reason, and a target updater version number, where the target file name refers to a file name related to a failure in the update process of the game, and the target updater version number is an updater version number that is failed in the update (i.e., an updater version number used in the update at this time); the attribute information of the game to be updated comprises a game version number before updating and a game version number to be updated; the user information includes a user unique identifier, such as a user account.

In actual implementation, the version number of the updater used by the game to be updated is stored in a public data structure, the updating process is exited after the game to be updated is determined to fail to be updated, and the version number of the updater used by the update can be acquired from the public data structure when the game to be updated is exited. In addition, if the update of the target update stage fails, the returned update return value carries the target file name related to the failed update, so that the corresponding target file name and the failure reason can be obtained directly through the update return value under the condition that the update failure of the target update stage is determined according to the update return value of the target update stage.

After the game client determines the target updating stage with an error in updating, error information such as the name of an error target file, the version number of a target updater, the fault reason and the like can be determined according to the target updating stage with the error, and then updating failure information is generated according to detailed error information. That is, if it is determined that the update of the target update stage fails, it indicates that the target update stage fails, and the game cannot be updated normally, so that update failure information can be generated according to the related attribute information of the failed target update stage, and after receiving the update failure information, the subsequent server can directly acquire the failed target update stage, and quickly and accurately locate the reason of the update failure.

In an optional implementation manner of this embodiment, if the update sub-phase is further subdivided for the update phase, the update failure information may also be generated according to the target update sub-phase, and at this time, the generating the update failure information according to the target update phase includes:

a target updating sub-stage for updating failure in the target updating stage is obtained;

and generating the updating failure information according to the target updating sub-stage.

It should be noted that, if the update sub-phases are further subdivided for the update phase, when it is determined that the target update phase fails to update, it may be further determined which update sub-phase in the target update phase fails to update, and then update failure information is generated according to the specific update sub-phase, so that the subsequent server may directly determine the failed target update sub-phase according to the update failure information, and quickly and accurately locate the reason of the update failure.

In an optional implementation manner of this embodiment, a target update sub-phase in which update fails in the target update phase is obtained, and a specific implementation process may be as follows:

acquiring a second updating return value of the target updating stage according to the stage identifier of the target updating stage, wherein the second updating return value carries the sub-stage identifier of the updating sub-stage and the corresponding sub-stage return value;

and determining a target updating sub-stage with failed updating in the target updating stage according to the sub-stage return value of the updating sub-stage.

In actual implementation, after the update task of each update sub-phase is executed, a sub-phase return value of a first type is generated, and if a fault occurs during execution of the update task of a target update sub-phase (current update sub-phase), a sub-phase return value of a second type is generated. And if the target updating sub-phase fails, the target updating phase fails, updating is stopped, and a second updating return value of a second type is returned, at this time, the second updating return value carries the sub-phase return values of each updating sub-phase which is executed and failed to be executed, so that the target updating sub-phase which is failed to be updated in the target updating phase can be determined according to the sub-phase identifier in the second updating return value and the corresponding sub-phase return value.

It should be noted that, whenever an update phase update error occurs, it can be considered that an error occurs in a certain update sub-phase in the update phase, which results in an error in the entire update phase. In practical implementation, the step coding of subdivision can be performed for each updating sub-phase to determine whether the updating fails, and one possible implementation manner is to determine whether the updating fails according to the running result return value (i.e. the sub-phase return value) directly through a simple function; another possible implementation manner is to segment the function through a complex function (i.e., a relatively long function, including a parent function and a child function), allocate one code to each segment, modify the current code to which segment, and finally use the current code as a running result return value (i.e., a child-stage return value), where for the nested relationship of the parent function and the child function, the running result return value adopts a splicing manner, such as parent function return code-child function 1 return code-child function 2 return code-child function 3 return code, and the like.

In an optional implementation manner of this embodiment, the update failure information is generated according to the target update sub-phase, and a specific implementation process may be as follows:

determining attribute information of the target updating stage and attribute information of the target updating sub-stage according to a second updating return value of the target updating stage;

acquiring attribute information and user information of the game to be updated;

and generating the update failure information according to the attribute information of the target update stage, the attribute information of the target update sub-stage, the attribute information of the game to be updated and the user information.

Specifically, the attribute information of the target update sub-phase includes a phase identifier of the target update sub-phase.

For example, the game client generates the update failure information according to the target update sub-phase, and the structure of the update failure information is shown in table 1 below.

Table 1 structure of update failure information

Each updating sub-stage included in any updating stage in the description generates a corresponding sub-stage return value when executing an updating task of the corresponding updating sub-stage, and according to the sub-stage return values generated by the updating sub-stages, which specific updating sub-stage in a target updating stage has a fault can be determined, so that the specific reason of the updating failure is determined in a finer granularity, and the follow-up query processing of a worker is facilitated.

Step 106: and reporting the update failure information to a server.

Specifically, under the condition that the target update stage fails to update, on the basis of generating update failure information according to the target update stage, the update failure information is further reported to a server.

In actual implementation, the game client may initiate a POST request to the server through HTTP (Hyper Text Transfer Protocol), so as to upload the update failure information to the server. The hypertext transfer protocol (HTTP) is designed to ensure communication between a client and a server, and works as a request-response protocol between the client and the server. A method commonly used when making request-responses between a client and a server is a POST request, specifically the submission of data to be processed to a specified resource (i.e., server).

It should be noted that the game client reports the generated update failure information to the server, so that the server can receive and store the update failure information reported by each game client, and provide an inquiry interface, so that a worker can directly inquire the required update failure information through the server, quickly and accurately know which update stage fails in the game update process, further quickly and accurately determine the specific reason of the game update failure, and take countermeasures in time to ensure user experience.

Fig. 2 is a flowchart illustrating a management method of game update failure according to an embodiment of the present disclosure, applied to a server, and specifically includes the following steps:

step 202: receiving update failure information reported by a game client, wherein the update failure information carries attribute information of a target update stage, attribute information of a game to be updated and user information, and the target update stage is an update stage of update failure in an update process of the game to be updated.

Therefore, in order to determine the specific reason of the game update failure accurately and quickly, the present specification provides a management method of the game update failure, which can receive the update failure information reported by the game client, where the update failure information carries the attribute information of the target update stage, the attribute information of the game to be updated, and the user information, and the target update stage is the update stage of the update failure in the update process of the game to be updated; and then, classifying and storing the update failure information, and acquiring and returning the corresponding update failure information according to the query parameters carried by the update failure query instruction under the condition of receiving the update failure query instruction. Under the condition, the server can receive and store the update failure information reported by each game client, an inquiry interface is provided, and a worker can directly inquire the required update failure information through the server, and can quickly and accurately know which specific update stage fails in the game update process without checking and analyzing the game update logs of each game client one by one, so that the specific reason of the game update failure can be quickly and accurately determined, the countermeasure can be timely taken, and the user experience is ensured.

Step 204: and classifying and storing the update failure information.

Specifically, on the basis of receiving the update failure information reported by the game client, the update failure information is further classified and stored.

In an optional implementation manner of this embodiment, the update failure information is classified and stored, and a specific implementation process may be as follows:

analyzing the update failure information to acquire attribute information of a target update stage, attribute information of a game to be updated and user information carried in the update failure information;

determining a target updating stage, a game to be updated and a target user corresponding to the updating failure information according to the attribute information of the target updating stage, the attribute information of the game to be updated and the user information carried in the updating failure information;

and storing the update failure information according to preset classification parameters, a target update stage, the game to be updated and a target user.

Specifically, the preset classification parameter refers to a parameter for classifying and storing the update failure information, and if the update failure information needs to be stored according to different users, the classification parameter is a user; if the update failure information needs to be stored according to different update stages, classifying the parameters into the update stage; if the update failure information needs to be stored according to different games, the classification parameter is the game.

It should be noted that, after receiving the update failure information, the server may analyze the update failure information to obtain corresponding update error detailed information, and then may store the update failure information in a classified manner according to the update error detailed information, that is, insert the update failure information into a corresponding type of location in the database.

In addition, the server can collect the information of the target update stage by adopting a mode that the game client reports the error target update stage through the network in the update process, the update is finished or the update fails, so that the reason of the update failure of a single game can be quickly inquired. If the problem of the system is a problem of a single player, the player can be prompted by an error in time, and if the problem of the single player is a problem of the single player, the reason for the update failure of the player can be searched according to the unique identifier of the player, so that a countermeasure can be taken.

In an optional implementation manner of this embodiment, the error number of each update stage may also be counted, so as to find out which update stage in the update flow is prone to error from the statistical perspective, that is, after the update failure information is classified and stored, the method further includes:

determining target updating stages included in the updating failure information, and counting the number of each target updating stage aiming at different target updating stages;

and sequencing the target updating stages from high to low according to the number to generate a stage sequencing table with updating failure.

It should be noted that, when an update fails in a certain update stage, the game client generates corresponding update failure information, that is, each update failure information includes a target update stage (i.e., a stage of update failure). Thus, the server may determine the target update phases that it includes for each piece of received update failure information, and then count the number of each target update phase.

Illustratively, the server receives 10 pieces of update failure information, which are respectively update failure information 1, and the target update stage includes searching for an update file; updating failure information 2, wherein the target updating stage is downloading an updating file; updating failure information 3, wherein the target updating stage is downloading an updating file; updating failure information 4, wherein the target updating stage is downloading an updating file; updating failure information 5, wherein a target updating stage is a verification updating file; updating failure information 6, including target updating stage of installing updating file; update failure information 7, including a target update stage of installing an update file; updating failure information 8, including target updating stage of installing updating file; update failure information 9, including a target update stage of downloading an update file; the update failure information 10 includes a target update stage of verifying the update file. Thus, for the search update file, the number thereof is counted as 1; counting the number of the downloaded update files to be 4; counting the number of the verification update files to be 2; for the installation update files, the number thereof is counted as 3. And sequencing the target updating stages from high to low according to the number to obtain a stage sequencing table with updating failure as shown in the following table 1.

TABLE 1 phase order table for update failure

Target update phase	Number of
		Downloading update files	4
Installing update files	3
		Verifying update files	2
Finding update files	1

In the present specification, the target update stages included in each received update failure information may be determined first, and then the number of each update stage is counted, so as to lock the detailed update stage with a high probability of error, and it is found from the point of statistics which update stage in the update flow is more likely to have an error, after the number sorting, the corresponding update problem may be solved according to the number of errors, that is, the worker may repair the problem related to game update from the direction of big data.

In an optional implementation manner of this embodiment, because the update failure information received long before is likely to have been processed by the staff, that is, the update failure information with an earlier time has no statistical significance, the update failure information may further carry a generation timestamp, and at this time, the target update stages within a period of time may be sorted, so as to avoid performing statistics on the premature update failure information and waste processing resources, that is, before determining the target update stage included in the update failure information, and counting the number of each target update stage for different target update stages, the method further includes:

determining whether the update failure information is update failure information within a preset time period or not according to a generation timestamp carried in the update failure information aiming at each update failure information in the received update failure information;

if yes, executing an operation step of determining target updating stages included in the updating failure information and counting the number of each target updating stage according to different target updating stages.

Along the above example, it is assumed that the generation timestamp carried by the update failure information 1 is 1 month and 1 day, the generation timestamp carried by the update failure information 2 is 1 month and 2 days, the generation timestamp carried by the update failure information 3 is 1 month and 3 days, the generation timestamps carried by the update failure information 4 and the update failure information 5 are both 1 month and 4 days, the generation timestamps carried by the update failure information 6, the update failure information 7 and the update failure information 8 are all 1 month and 5 days, and the generation timestamps carried by the update failure information 9 and the update failure information 10 are both 1 month and 6 days. Assuming that the current time is 1 month and 6 days, and the preset time period is within 3 days from the current time, the update failure information 1, the update failure information 2, and the update failure information 3 are not within the preset time period, so that statistics is not performed subsequently, and only the update failure information 4-the update failure information 10 within the preset time period are counted, so as to obtain a stage ranking table of update failure within the preset time period as shown in the following table 2.

TABLE 2 phase sequence table for failed update within preset time period

Target update phase	Number of
		Installing update files	3
Downloading update files	2
		Verifying update files	2

In the application, the server can screen out the update failure information within the preset time period from the received update failure information, and then sort the target update stages included in the update failure information within the preset time period, so that the statistical analysis processing on the premature update failure information is avoided, the processing resources are saved, and the management efficiency and accuracy of the game update failure can be improved.

In an optional implementation manner of this embodiment, if the update failure information also carries attribute information of a target update sub-phase, the error number of each update sub-phase may also be counted, so as to find out which update sub-phase in the update phases is prone to error from a statistical perspective, where the target update sub-phase is an update sub-phase in which update in the target update phase fails;

after the classification storage of the update failure information, the method further includes:

counting the number of updating failure information corresponding to each target updating sub-stage aiming at different target updating sub-stages;

and sequencing the target updating sub-stages from high to low according to the number to generate a sub-stage sequencing table with failed updating.

It should be noted that, for the target update sub-phase, the same method as the target update sub-phase may also be adopted for statistics, so as to lock the detailed update sub-phase with a high probability of error, find out which update sub-phase in the target update phase is more likely to have an error from the viewpoint of statistics, and after performing quantity sorting, may solve the corresponding update problem from many to many according to the number of errors, and the detailed process is similar to the above statistical process type of the target update phase, and this application is not described herein again.

Step 206: and under the condition of receiving an update failure query instruction, acquiring and returning corresponding update failure information according to query parameters carried by the update failure query instruction.

Specifically, on the basis of classifying and storing the update failure information, further, under the condition that an update failure query instruction is received, the corresponding update failure information can be obtained and returned according to the query parameters carried by the update failure query instruction.

In an optional implementation manner of this embodiment, the server may provide a query window to receive the update failure query instruction, and then obtain and return corresponding update failure information according to a query parameter carried by the update failure query instruction, where a specific implementation process may be as follows:

displaying a query window of the update failure information;

receiving a query instruction triggered in the query window, wherein the query instruction carries query parameters;

and returning corresponding updating failure information according to the query parameters.

It should be noted that the server, after receiving the update failure information, inserts the update failure information into the database under the corresponding category, and provides an interactive window of a web page to enable the staff to query the details of the update error according to the requirements. The interactive window is an inquiry webpage for summarizing update failure information, and the interactive window can include information such as the number of successful updates, the number of failed updates, and the reason classification of the failed updates, that is, the game client can report the update failure information to the server except when the updates fail, and can also report the update success information to the server when the updates succeed, so that the server can count the number of successful updates, and can conveniently know the update condition of the more comprehensive game to be updated in time.

The management method for the update failure of the game provided by the specification can receive update failure information reported by a game client, wherein the update failure information carries attribute information of a target update stage, attribute information of the game to be updated and user information, and the target update stage is an update stage of the update failure in an update process of the game to be updated; and then, classifying and storing the update failure information, and acquiring and returning the corresponding update failure information according to the query parameters carried by the update failure query instruction under the condition of receiving the update failure query instruction. Under the condition, the server can receive and store the update failure information reported by each game client, an inquiry interface is provided, and a worker can directly inquire the required update failure information through the server, and can quickly and accurately know which specific update stage fails in the game update process without checking and analyzing the game update logs of each game client one by one, so that the specific reason of the game update failure can be quickly and accurately determined, the countermeasure can be timely taken, and the user experience is ensured. In addition, the server can count the update failure information of each category of update stage, so that the update stage with problems probably occurring in the game update process is locked, and the problems related to the updated game are repaired from the big data direction.

Fig. 3 is a flowchart illustrating a method for reporting and managing a game update failure according to an embodiment of the present disclosure, which specifically includes the following steps:

step 302: the game client divides the updating process of the game to be updated to obtain at least two updating stages.

Step 304: and the game client encodes the at least two updating stages to obtain stage identifiers corresponding to the at least two updating stages.

Step 306: the game client determines whether a target updating stage of the game to be updated is updated successfully, wherein the target updating stage is any updating stage included in an updating process of the game to be updated.

Step 308: and the game client generates update failure information according to the target update stage under the condition that the update of the target update stage fails, and reports the update failure information to the server.

Step 310: and the server receives the update failure information reported by the game client and stores the update failure information in a classified manner.

Step 312: and under the condition that the server receives the update failure query instruction, acquiring and returning corresponding update failure information according to the query parameters carried by the update failure query instruction.

In this specification, a game client fails at any update stage in a game update process, which results in a game update failure, and reports a target update stage (i.e., update failure information) with a problem in real time, a server can receive and store the update failure information reported by each game client, and provides an inquiry interface, a worker can directly inquire the required update failure information through the server, and can quickly and accurately know which update stage fails in the game update process without checking and analyzing game update logs of each game client one by one, so that specific reasons of the game update failure can be quickly and accurately determined, countermeasures can be taken in time, and user experience is guaranteed. In addition, the server can count the update failure information of each category of update stage, so that the update stage with problems probably occurring in the game update process is locked, and the problems related to the updated game are repaired from the big data direction.

Corresponding to the above method embodiment, this specification further provides an embodiment of a device for reporting a game update failure, and fig. 4 shows a schematic structural diagram of the device for reporting a game update failure provided in an embodiment of this specification. As shown in fig. 4, the apparatus includes:

a determining module 402, configured to determine whether a target update phase of a game to be updated is updated successfully, where the target update phase is any update phase included in an update flow of the game to be updated;

a first generating module 404, configured to generate update failure information according to the target update stage in a case that the target update stage fails to update;

a reporting module 406 configured to report the update failure information to a server.

Optionally, the apparatus further comprises:

the first division module is configured to divide the updating process of the game to be updated to obtain at least two updating stages;

the first encoding module is configured to encode the at least two update stages to obtain stage identifiers corresponding to the at least two update stages.

Optionally, the determining module 402 is further configured to:

acquiring a first updating return value of the target updating stage according to the stage identifier of the target updating stage;

determining an update type to which the first update return value belongs;

Optionally, the first generating module 404 is further configured to:

acquiring attribute information and user information of the game to be updated;

Optionally, the apparatus further comprises:

a second dividing module configured to divide each of the at least two update phases to obtain at least two update sub-phases;

and the encoding module is configured to encode the at least two updating sub-phases to obtain sub-phase identifications corresponding to the at least two updating sub-phases.

Optionally, the first generating module 404 is further configured to:

acquiring attribute information and user information of the game to be updated;

The device for reporting the game update failure provided by the present specification can determine whether the target update stage of the game to be updated is successfully updated, where the target update stage is any update stage included in the update process of the game to be updated; under the condition that the target updating stage fails to update, generating updating failure information according to the target updating stage; and reporting the update failure information to a server. Under the condition, the game client fails at any update stage in the game update process, so that the game update failure is caused, and the target update stage with the problem is reported in real time, so that the staff can timely know the specific update stage with the failure in the game update process of the game client through the server, quickly and accurately determine the specific reason of the game update failure, timely take corresponding measures, and ensure the user experience.

The above is an exemplary scheme of the device for reporting a game update failure according to this embodiment. It should be noted that the technical solution of the reporting device for game update failure and the technical solution of the reporting method for game update failure belong to the same concept, and details of the technical solution of the reporting device for game update failure, which are not described in detail, can be referred to the description of the technical solution of the reporting method for game update failure.

Corresponding to the above method embodiment, the present specification further provides an embodiment of a management server for a game update failure, and fig. 5 shows a schematic structural diagram of a management server for a game update failure provided in an embodiment of the present specification. As shown in fig. 5, the server includes:

a receiving module 502, configured to receive update failure information reported by a game client, where the update failure information carries attribute information of a target update stage, attribute information of a game to be updated, and user information, and the target update stage is an update stage of update failure in an update process of the game to be updated;

a storage module 504 configured to perform classified storage on the update failure information;

the obtaining module 506 is configured to, in a case that an update failure query instruction is received, obtain and return update failure information corresponding to the update failure query instruction.

Optionally, the server further includes:

a first statistical module configured to determine target update stages included in the update failure information, and count the number of each target update stage for different target update stages;

and the second generation module is configured to sort the target updating stages from high to low according to the number and generate a stage sorting table with failed updating.

Optionally, the update failure information also carries a generation timestamp; the server further comprises:

the operation module is configured to determine, for each piece of the received update failure information, whether the update failure information is update failure information within a preset time period according to a generation timestamp carried in the update failure information; and if so, operating the first statistical module.

Optionally, the update failure information also carries attribute information of a target update sub-stage, where the target update sub-stage is an update sub-stage of update failure in the target update stage;

the server further comprises:

the second counting module is configured to count the number of updating failure information corresponding to each target updating sub-phase aiming at different target updating sub-phases;

and the third generation module is configured to sort the target updating sub-phases from high to low according to the number and generate a sub-phase sorting table with failed updating.

The management server for the failure of game update provided by the present specification can receive update failure information reported by a game client, where the update failure information carries attribute information of a target update stage, attribute information of a game to be updated, and user information, and the target update stage is an update stage of update failure in an update process of the game to be updated; and then, classifying and storing the update failure information, and acquiring and returning the corresponding update failure information according to the query parameters carried by the update failure query instruction under the condition of receiving the update failure query instruction. Under the condition, the server can receive and store the update failure information reported by each game client, an inquiry interface is provided, and a worker can directly inquire the required update failure information through the server, and can quickly and accurately know which specific update stage fails in the game update process without checking and analyzing the game update logs of each game client one by one, so that the specific reason of the game update failure can be quickly and accurately determined, the countermeasure can be timely taken, and the user experience is ensured.

The above is an illustrative scheme of a management server for a game update failure of the present embodiment. It should be noted that the technical solution of the management server for the game failure update belongs to the same concept as the technical solution of the management method for the game failure update, and details of the technical solution of the management server for the game failure update, which are not described in detail, can be referred to the description of the technical solution of the management method for the game failure update.

Fig. 6 illustrates a block diagram of a computing device 600 provided according to an embodiment of the present description. The components of the computing device 600 include, but are not limited to, a memory 610 and a processor 620. The processor 620 is coupled to the memory 610 via a bus 630 and a database 650 is used to store data.

Computing device 600 also includes access device 640, access device 640 enabling computing device 600 to communicate via one or more networks 660. Examples of such networks include the Public Switched Telephone Network (PSTN), a Local Area Network (LAN), a Wide Area Network (WAN), a Personal Area Network (PAN), or a combination of communication networks such as the internet. Access device 640 may include one or more of any type of network interface (e.g., a Network Interface Card (NIC)) whether wired or wireless, such as an IEEE802.11 Wireless Local Area Network (WLAN) wireless interface, a worldwide interoperability for microwave access (Wi-MAX) interface, an ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a bluetooth interface, a Near Field Communication (NFC) interface, and so forth.

In one embodiment of the present description, the above-described components of computing device 600, as well as other components not shown in FIG. 6, may also be connected to each other, such as by a bus. It should be understood that the block diagram of the computing device architecture shown in FIG. 6 is for purposes of example only and is not limiting as to the scope of the present description. Those skilled in the art may add or replace other components as desired.

Computing device 600 may be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (e.g., tablet, personal digital assistant, laptop, notebook, netbook, etc.), mobile phone (e.g., smartphone), wearable computing device (e.g., smartwatch, smartglasses, etc.), or other type of mobile device, or a stationary computing device such as a desktop computer or PC. Computing device 600 may also be a mobile or stationary server.

Wherein the processor 620 is configured to execute the following computer-executable instructions to implement the following method:

The above is an illustrative scheme of a computing device of the present embodiment. It should be noted that the technical solution of the computing device and the technical solutions of the above-mentioned game failure reporting method and game failure management method belong to the same concept, and details of the technical solutions of the computing device, which are not described in detail, can be referred to in the description of the technical solutions of the above-mentioned game failure reporting method and game failure management method.

An embodiment of the present specification also provides a computer readable storage medium storing computer instructions that, when executed by a processor, are operable to:

The above is an illustrative scheme of a computer-readable storage medium of the present embodiment. It should be noted that the technical solution of the storage medium and the technical solutions of the above-mentioned method for reporting a game update failure and method for managing a game update failure belong to the same concept, and details of the technical solution of the storage medium, which are not described in detail, can be referred to the descriptions of the technical solutions of the above-mentioned method for reporting a game update failure and method for managing a game update failure.

The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.

The computer instructions comprise computer program code which may be in the form of source code, object code, an executable file or some intermediate form, or the like. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution medium, etc. It should be noted that the computer readable medium may contain content that is subject to appropriate increase or decrease as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, computer readable media does not include electrical carrier signals and telecommunications signals as is required by legislation and patent practice.

It should be noted that, for the sake of simplicity, the foregoing method embodiments are described as a series of acts or combinations, but those skilled in the art should understand that the present disclosure is not limited by the described order of acts, as some steps may be performed in other orders or simultaneously according to the present disclosure. Further, those skilled in the art should also appreciate that the embodiments described in this specification are preferred embodiments and that acts and modules referred to are not necessarily required for this description.

In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.

The preferred embodiments of the present specification disclosed above are intended only to aid in the description of the specification. Alternative embodiments are not exhaustive and do not limit the invention to the precise embodiments described. Obviously, many modifications and variations are possible in light of the above teaching. The embodiments were chosen and described in order to best explain the principles of the specification and its practical application, to thereby enable others skilled in the art to best understand the specification and its practical application. The specification is limited only by the claims and their full scope and equivalents.

Claims

1. A method for reporting game update failure is characterized in that the method comprises the following steps:

and reporting the update failure information to a server.

2. The method as claimed in claim 1, wherein before determining whether the target update stage of the game to be updated is updated successfully, the method further comprises:

3. The method according to claim 1 or 2, wherein the determining whether the target update stage of the game to be updated is updated successfully comprises:

determining an update type to which the first update return value belongs;

4. The method of claim 3, wherein the generating of the update failure information according to the target update stage comprises:

acquiring attribute information and user information of the game to be updated;

5. The method according to claim 2, wherein the step of dividing the update flow of the game to be updated into at least two update stages further comprises:

6. The method of claim 5, wherein the generating of the update failure information according to the target update stage comprises:

7. The method as claimed in claim 6, wherein the sub-stage of obtaining the target update failed in the target update stage comprises:

8. The method of claim 5, wherein the generating the update failure information according to the target update sub-phase comprises:

acquiring attribute information and user information of the game to be updated;

9. A method for managing game update failure, the method comprising:

classifying and storing the update failure information;

10. The method for managing game update failure according to claim 9, further comprising, after storing the update failure information in a sorted manner:

11. The method of managing a game update failure of claim 10, wherein the update failure information further carries a generation time stamp;

before the determining the target update stages included in the update failure information and counting the number of each target update stage for different target update stages, the method further includes:

12. The method of claim 9, wherein the update failure information further carries attribute information of a target update sub-phase, and the target update sub-phase is an update sub-phase of an update failure in the target update phase;

13. An apparatus for reporting game update failure, the apparatus comprising:

14. A management server for a game update failure, the server comprising:

15. A computing device, comprising:

a memory and a processor;

16. A computer-readable storage medium storing computer instructions, which when executed by a processor, implement the steps of the method for reporting a game update failure according to any one of claims 1 to 8 or the method for managing a game update failure according to any one of claims 9 to 12.