Game management method, management device, server and program product

Abstract

The invention discloses a game management method, a management device, a server and a program product. The management method is used for a server deployed with a game platform, and the server can respond to a starting instruction for any racking target game on the game platform and run a downloader execution file corresponding to the target game so as to start the target game after downloading of a resource package is completed. A downloader development tool provided by a platform side opens variable information related to a target game to be supplemented by a third side, so that a downloader development mode is changed from platform side / third side independent development to platform side and third side cooperative development, and therefore, even if the third side does not have downloader development experience, the downloader development mode can be changed into the platform side and third side cooperative development mode. And a corresponding downloader execution file can be efficiently and independently generated based on the mastered game description information. And the server completes resource downloading and game starting by relying on the downloader execution file, so that the threshold of developing the downloader by a third party is obviously reduced, the game online efficiency is improved, and the user experience is further optimized.

Description

Technical Field

[0001] The present application belongs to the field of computer technology, and in particular relates to a game management method, a game management device, a server, and a computer program product. Background Art

[0002] Currently, when third parties (such as game developers, publishers, and joint operation partners) release games on gaming platforms, they typically need to develop a corresponding game downloader to complete the download and launch process of game resources after the player clicks "Start Game." However, developing a game downloader involves multiple technologies, and many third parties lack relevant experience. This often leads to inefficient development, incomplete functionality, or even non-implementation, which in turn impacts the game's launch progress and user experience. Summary of the Invention

[0003] The present application provides a game management method, a game management device, a server, and a computer program product, which can improve the efficiency of game launch and optimize the user experience.

[0004] In a first aspect, the present application provides a game management method, which is applied to a server deployed with a game platform, and the management method includes:

[0005] In response to a launch command for any target game listed on the game platform, the downloader execution file of the target game is run to download the resource package of the target game; the downloader execution file is independently generated by a third party based on the description information of the target game and a downloader development tool; the downloader development tool is provided by the platform corresponding to the game platform;

[0006] After the resource pack is downloaded, launch the target game.

[0007] Optionally, the description information is game attribute information, and the game attribute information includes the uniform resource locator of the game background image of the target game, the uniform resource locator of the game resource package, and the game name.

[0008] Optionally, before responding to a start instruction for any target game listed on the game platform, the method further includes:

[0009] Get the downloader executable file;

[0010] Launch the target game based on the downloader executable file.

[0011] Optionally, the downloader execution file is generated by a third party by writing description information into a pre-acquired downloader development tool and then packaging it.

[0012] Optionally, before responding to a start instruction for any target game listed on the game platform, the method further includes:

[0013] In response to a request to obtain the downloader development tool, the downloader development tool is sent to a third party so that the third party can independently generate a downloader execution file based on the description information of the target game and the downloader development tool.

[0014] Optionally, the downloader development tool is a universal downloader SDK, which is configured with a game download function and a game launch function. The universal downloader SDK that completes the game attribute information of the target game is the downloader execution file.

[0015] In a second aspect, the present application provides a game management device, which is applied to a server deployed with a game platform. The management device includes a game startup module, which is used to:

[0016] In response to a launch command for any target game listed on the game platform, the target game's downloader executable file is run to download the target game's resource package; the downloader executable file is independently generated by a third party based on the target game's description information and a downloader development tool; the downloader development tool is provided by the platform corresponding to the game platform;

[0017] After the resource pack is downloaded, launch the target game.

[0018] In a third aspect, the present application provides a server comprising a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the steps of the method according to the first aspect are implemented.

[0019] In a fourth aspect, the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the method of the first aspect are implemented.

[0020] In a fifth aspect, the present application provides a computer program product, which includes a computer program. When the computer program is executed by one or more processors, it implements the steps of the method of the first aspect.

[0021] The beneficial effect of the first aspect mentioned above compared to the prior art is that the server can respond to the startup instruction for any target game listed on the game platform, run the downloader execution file corresponding to the target game, and start the target game after completing the resource package download. Among them, the third party can generate the downloader execution file corresponding to the target game based on the downloader development tools provided by the platform and the description information of the target game. In this way, even if the third party does not have experience in downloader development, it can also efficiently and independently generate the corresponding downloader execution file based on the description information of the game it has. The server relies on the downloader execution file to complete resource downloads and game startup, which not only significantly lowers the threshold for third-party development of game downloaders, improves the efficiency of game launch, but also further optimizes the user experience.

[0022] It can be understood that the beneficial effects of the second to fifth aspects mentioned above can be found in the relevant description of the first aspect mentioned above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the embodiments or descriptions of the prior art. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0024] Figure 1 This is a flowchart of a game management method provided by an embodiment of the present application;

[0025] Figure 2 This is a schematic diagram of the interaction between the game developer and the game platform when launching the target game A provided by the embodiment of the present application;

[0026] Figure 3a This is a schematic diagram of the development of the downloader in the related art provided by the embodiment of the present application;

[0027] Figure 3b This is a schematic diagram of the development of the downloader in this application provided by the embodiment of this application;

[0028] Figure 4 This is a schematic diagram of the interaction between a game player and a game platform when experiencing target game A provided by an embodiment of the present application;

[0029] Figure 5 1 is a schematic diagram of the structure of a game management device provided in an embodiment of the present application;

[0030] Figure 6 It is a structural diagram of the server provided in an embodiment of the present application. DETAILED DESCRIPTION

[0031] In the following description, specific details such as specific system structures and techniques are provided for purposes of illustration rather than limitation to facilitate a thorough understanding of the embodiments of the present application. However, it will be apparent to those skilled in the art that the present application may be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to avoid obscuring the description of the present application with unnecessary detail.

[0032] In related technologies, games generally support two service models: one is the official service model deployed by a third party (such as a game developer or licensor), and the other is the service model provided by the game platform. In the game platform-based service model, the platform shares revenue with the third party based on the traffic generated by the game. The statistics of this traffic are usually achieved through downloaders, so each game listed by a third party must be equipped with a corresponding downloader.

[0033] This presents a technical challenge: if a downloader is developed solely by a third party, it can be challenging to develop due to the multiple platform adaptation and resource scheduling techniques involved. This is particularly challenging for third parties lacking relevant experience. This often leads to low development efficiency, incomplete functionality, and even inability to run the downloader smoothly, ultimately impacting the game's launch schedule and overall user experience. Furthermore, during debugging, third-party downloaders may face issues such as poor compatibility and integration difficulties, significantly increasing the debugging workload for the gaming platform.

[0034] To lower these barriers, centrally developing downloaders by game platforms could improve access efficiency and simplify the process when the number of games is limited. However, as the number of games continues to grow, game platforms will face significant testing pressure. To alleviate this issue, platforms typically grant third-party game testing access, allowing them to participate in functional verification and pre-launch testing.

[0035] However, this approach also has certain drawbacks: First, open testing permissions increase the complexity of platform management, requiring strict control over testing processes, permission scope, and data access. Second, varying third-party testing capabilities can lead to risks such as inconsistent test results and insufficient feedback, impacting overall testing quality and platform stability. Furthermore, open permissions can introduce security risks, such as unexpected calls to platform interfaces or sensitive resources, requiring additional permission isolation and monitoring mechanisms, further increasing the burden on platform operations and maintenance.

[0036] To address the issues presented by the aforementioned downloader development model, this application proposes a game management method from the perspective of a gaming platform, aiming to balance the flexibility of third-party downloader development with the controllability of unified platform management. This method effectively lowers the barrier to entry for third-party downloader development while alleviating the pressure on gaming platforms during debugging and testing, thereby improving the overall efficiency of game access and launch, and further optimizing the user experience. The control method proposed in this application will be illustrated below through specific examples.

[0037] The game management method provided in the embodiments of the present application can be applied to a server deployed with a game platform, which can be a mobile phone, a tablet computer, a vehicle-mounted device, an augmented reality (AR) / virtual reality (VR) device, a laptop computer, an ultra-mobile personal computer (UMPC), a netbook, a personal digital assistant (PDA), and other electronic devices. The embodiments of the present application do not impose any restrictions on the specific type of electronic device.

[0038] In order to illustrate the technical solution proposed in this application, each embodiment will be described below with the server as the execution entity.

[0039] Figure 1 A schematic flow chart of a game management method provided by the present application is shown, and the game management method includes:

[0040] Step 110: The server responds to a start instruction for any target game listed on the game platform and runs the downloader executable file of the target game to download a resource package of the target game.

[0041] Step 120: After the resource package is downloaded, the server starts the target game.

[0042] The gaming platform can host its own games and also support access to gaming resources provided by third parties. Given that the platform's traffic monetization and revenue sharing primarily rely on third-party games, this embodiment primarily discusses third-party games. For ease of description, these games can be collectively referred to as target games. Each target game requires a corresponding downloader executable file to download game resources and launch the game, which also provides a basis for subsequent traffic statistics.

[0043] To balance the flexibility of third parties in downloader development with the controllability of the game platform in operation and management, this embodiment proposes a collaborative downloader development model, breaking away from the traditional model of downloader development by the platform or third parties. In this development model, the platform (i.e., the entity responsible for the development, management, and / or operation of the game platform) and the third party collaborate to create the downloader.

[0044] Specifically, the downloader development tool provided by the platform encapsulates the common functional modules required by the downloader, such as game downloading and game launching, while also retaining the information configuration interface associated with the target game. This allows third parties, based on the downloader development tool, to efficiently generate the corresponding downloader executable file simply by completing the corresponding configuration based on the target game description information they have (such as the game name, resource package URL, etc.).

[0045] Using the downloader development tool, third parties can efficiently and independently build a downloader executable file that meets their requirements, without the need for game platform involvement or in-depth understanding of the downloader's internal implementation logic. Based solely on the target game's description, they can efficiently and independently build a downloader executable file that meets their requirements. This collaborative development model not only effectively lowers the barrier to entry for third-party downloader development, but also reduces the debugging and maintenance burden on game platforms, thereby improving the launch efficiency of target games and further optimizing the user experience.

[0046] It's worth noting that the resulting downloader executable file remains functionally identical to traditional downloaders, possessing the basic capabilities for downloading and launching games. The core difference lies in a shift in the downloader's development model. To adapt, the platform has adjusted the existing game downloader architecture: Firstly, common functional modules within the downloader (such as download logic and launch mechanisms) have been unified and encapsulated; secondly, necessary configuration interfaces have been opened to accommodate different target games.

[0047] Based on these improvements, the platform has further launched a downloader development tool to assist third-party developers or game providers. Third parties no longer need to master the underlying implementation of the downloader; they only need to provide familiar target game description information. With the tool's support, they can quickly generate a downloader executable file ready for actual deployment, significantly lowering the barrier to entry for third-party game downloader development and improving access efficiency.

[0048] Based on the above mechanism, when the server detects a startup instruction for any target game, it can call and run the downloader execution file corresponding to the target game; the downloader execution file will complete the download of the target game resource package, and after the download is completed, start the target game based on the downloaded resource package.

[0049] For example, the startup command can be issued by a game player through his PC terminal to start the game and actually experience it; it can also be triggered by a third party through its PC terminal to test the functional integrity and compatibility of the generated downloader executable file.

[0050] In this embodiment, thanks to the improved development model, the development of the downloader is neither entirely dependent on a third party nor entirely on the game platform. Instead, it fully integrates the advantages of both in the downloader development process: on the one hand, the game platform has a deep understanding of the platform interface and downloader architecture, and can provide a highly adaptable downloader development tool that does not require additional debugging; on the other hand, the third party is more familiar with the resource structure, startup logic, and testing requirements of the target game, and has the key information needed to build and verify the downloader. Based on this, the platform provides a stable and highly compatible downloader development tool, shielding the underlying development details and encapsulating the necessary interface logic. This allows the third party to rely solely on the description information of the target game it has mastered to efficiently and independently generate the corresponding downloader executable file through this tool. This model not only reduces the development and adaptation difficulty of the third party, but also avoids the debugging and testing pressure faced by the platform due to large-scale game access, thereby improving overall access efficiency and ensuring the stability and consistency of platform operation.

[0051] In some embodiments, before responding to a launch instruction for any target game listed on the game platform, the method further includes:

[0052] Step A1: The server obtains the downloader execution file.

[0053] As can be seen from the aforementioned embodiments, the downloader executable file is generated and provided by a third party. The server can obtain the downloader executable file in two ways, including but not limited to the following: one is for the third party to directly interact with the game platform through a PC terminal and complete the upload; the other is for the third party to send the downloader executable file to the game platform staff, who then upload it to the server on their behalf. This flexible upload method facilitates third parties in different collaboration modes to complete the submission of the downloader executable file, improving the access efficiency of the target game.

[0054] Step A2: The server puts the target game on the shelves based on the downloader execution file.

[0055] To protect the rights and interests of the gaming platform, servers are configured and managed based on the target game's corresponding downloader executable file when listing it. By relying on the downloader executable file to list the target game, the gaming platform can effectively control the acquisition and launch process of the target game's resources, ensuring that the connected target game complies with platform specifications. This facilitates subsequent traffic statistics, revenue calculations, and operational monitoring, thereby ensuring the security and compliance of platform operations.

[0056] In this embodiment, after obtaining the downloader executable file corresponding to the target game, the server can complete the target game's listing process based on this file. Using the downloader executable file, the server can configure the target game's resource acquisition path and launch method, ensuring the game's normal distribution and operation on the platform, and providing support for subsequent traffic statistics and revenue settlement.

[0057] In some embodiments, a third party generates a downloader executable file by writing description information into a pre-acquired downloader development tool and then packaging it. This approach eliminates the need for the third party to understand the specific implementation logic of the downloader; they only need to provide the necessary game description information to quickly generate a downloader executable file that meets platform requirements, streamlining the development process and improving access efficiency.

[0058] In some embodiments, before responding to a launch instruction for any target game listed on the game platform, the method further includes:

[0059] Step B1: The server responds to the request for obtaining the downloader development tool and sends the downloader development tool to a third party so that the third party can independently generate a downloader execution file based on the description information of the target game and the downloader development tool.

[0060] After receiving a request from a third party to obtain the downloader development tool (for example, when the third party is listing the target game, or by clicking the download button provided by the game platform to trigger the request), the server can send the downloader development tool to the third party. Of course, the third party can also obtain the downloader development tool directly from the game platform staff or by visiting a specific link.

[0061] After obtaining the tool, the third party can complete the corresponding configuration and packaging operations in the downloader development tool based on the description information of the target game it has, thereby generating a downloader executable file corresponding to the target game.

[0062] In this embodiment, the acquisition of downloader development tools serves as a prerequisite for the downloader execution file generation process, which not only reduces the technical and operation and maintenance burden of the game platform in downloader development, but also improves the access autonomy and efficiency of third parties, further accelerating the launch process of the target game.

[0063] In some embodiments, the downloader development tool can be a universal downloader software development kit (SDK). As the name implies, "universal" means that the universal downloader SDK has good platform compatibility and target game adaptability, and can support the access and downloader construction of any target game. This universal downloader SDK has pre-built game download and game launch functions. Its core functional framework does not require third-party modification and is ready for use out of the box.

[0064] The SDK is missing only the descriptive information related to the specific target game (such as the resource package address). Third parties simply need to complete the target game's descriptive information to obtain the corresponding downloader executable file. While retaining the SDK's stability, this downloader executable file has specialized adaptation capabilities for the target game and can be directly called by the server to download the resource package and launch the game.

[0065] In some embodiments, to further reduce the difficulty of generating the downloader executable file, the required target game description information is simplified to game attribute information. The game attribute information includes: the uniform resource locator of the game background image (GameBackground Image URL), the uniform resource locator of the game resource package (Game Resource Package URL), and the game name.

[0066] By only filling in the above game attribute information, the third party can complete the configuration of the downloader development tool and then efficiently generate the corresponding downloader execution file without having to pay attention to the internal implementation logic of the downloader, thereby effectively lowering the threshold for third-party development of game downloaders.

[0067] For example, to improve the configuration efficiency of the downloader development tool, the downloader development tool can be equipped with a visual configuration tool or game attribute information template. The visual configuration tool allows third parties to intuitively fill in the required information in a graphical interface, reducing the risk of formatting errors or omissions caused by manual input. Pre-set game attribute information templates allow third parties to quickly complete information by referring to a standard structure, thereby streamlining the operation process and improving configuration efficiency and accuracy.

[0068] For example, in order to ensure the accuracy of the downloader development tool configuration, the visualization tool can also support parameter verification, field prompts and real-time preview functions to ensure the completeness and validity of the filled content.

[0069] In some embodiments, assuming that the third party is a game developer, see Figure 2 , Figure 2 The diagram shows the interaction between the game developer and the game platform when launching the target game A.

[0070] The game platform can be divided into two sub-platforms: the game publishing platform and the game center. The game publishing platform is primarily for third parties (such as game developers and licensors), and is used for obtaining the universal downloader SDK, uploading and managing game versions, and other publishing-related operations. The game center, on the other hand, is primarily for game players, and is used to list games and display a list of listed games, respond to player launch commands, and execute game download and launch processes, among other player-side interaction and operational functions. This division of labor between the platforms allows for functional decoupling between access parties and end users, improving the overall maintainability and operational efficiency of the system.

[0071] Specifically, when a game developer wants to release target game A, they can first request a universal downloader SDK from the game publishing platform. After the game publishing platform returns the universal downloader SDK, the developer can write the relevant description information of target game A, including the URL of the game background image, the URL of the game resource package, and the game name, into the universal downloader SDK.

[0072] The Universal Downloader SDK features a built-in universal download engine that highly abstracts the game download and launch process, eliminating the complexity associated with varying game types. By standardizing the download link format for game resource packages and specifying a default path for game launch files, the Universal Downloader SDK is compatible with any game.

[0073] Exemplarily, the structure of the universal downloader SDK may include the main program **GameDownloader.exe; the dynamic library links libcrypto-1_1.dll, libcurl.dll, libexpat.dll, libssl-1_1.dll, minizip.dll and zlib1.dll that the main program depends on; the configuration file congfig (including json file); and the resource folder (including the default game background image).

[0074] When using the Universal Downloader SDK, game developers simply configure the target game's resource package download address and launch entry file path according to established specifications to complete parameter filling and integration. Subsequently, through packaging, the downloader executable file for target game A is obtained. In other words, the packaged Universal Downloader SDK becomes a ready-to-run downloader executable file that can be used to download and launch the corresponding target game A. This approach effectively reduces development complexity for game developers, improves game access efficiency, and enhances the platform's unified management capabilities.

[0075] For example, during configuration, the content of the internal configuration file (such as config.json) of the Universal Downloader SDK is usually edited by the game developer. The following is a sample code, where the bold part represents the configuration information that the game developer needs to fill in based on the target game A. The text after " / / " is a comment for the corresponding code:

[0076]

[0077] Through the above configuration method, game developers only need to focus on filling in specific information related to their target game without worrying about the underlying logic of the downloader, thereby achieving efficient collaboration between development and access processes.

[0078] Typically, background can provide a default game background image. Thus, if the game developer updates the path pointed to by the game background image, the game background image of the target game A can be stored in the updated path.

[0079] After the configuration is completed, the game developer can independently download the packaging program and complete the packaging through the packaging guide of the corresponding packaging program, and then package the universal downloader SDK with the updated config.json to obtain an exe file, which is the downloader executable file of the target game A.

[0080] After the game developer generates the downloader executable file and uploads it to the game center, the game center uses it to launch the target game A, thereby releasing the target game and displaying it in the list of available games. This approach eliminates the need for the game center to review or redevelop the downloader logic, ensuring the integrity and reliability of game download and launch functions, improving game launch efficiency and reducing operational costs.

[0081] from Figure 3a and 3b It can be seen that compared with the two existing downloader development methods - that is, independent development of downloaders by third parties, or centralized development of downloaders by game platforms - the downloader development method proposed in this application significantly lowers the threshold for third-party downloader development while maintaining platform uniformity and compatibility. By providing downloader development tools with general capabilities (such as a universal downloader SDK), the game platform standardizes the core functional modules in the downloader (such as the download engine and startup logic). Only the third party needs to supplement the game attribute information of the target game to quickly generate a usable downloader executable file.

[0082] This approach not only avoids the development and debugging difficulties caused by the lack of technical accumulation of third parties, but also alleviates the testing pressure and resource bottlenecks brought about by the centralized development of game platforms as the number of games increases, thereby achieving a reasonable sharing of downloader development responsibilities, improving game launch efficiency, and further optimizing user experience.

[0083] Figure 4 A schematic diagram showing the interaction between a game player and a game center when experiencing target game A is shown.

[0084] When a game player clicks on target game A presented in the game center, the game platform invokes and runs the corresponding downloader executable file. Upon launch, the downloader executable file first checks to see if the game resource package link it has configured has been downloaded. If not, it automatically invokes the built-in download engine to download the target game's content package from the specified address. Once the download is complete, the downloader launches the target game's executable file according to the pre-set launch entry file path, enabling the game to run normally.

[0085] For example, the terminal corresponding to the game player (such as a PC or mobile phone) can access the client corresponding to the game platform. When the game player clicks on the target game A through the game center interface in the client, the client can first download the downloader executable file of the target game A to the "target game download path / **Game / download / game platform ID / " directory; then the client can start the downloader executable file, and the zip compressed package of the target game A will be downloaded to the "target game download path / **Game / download / game platform ID / game" directory, and the compressed package will be unzipped to the same directory; finally, the client can open the exe file of the target game according to the relative path start_path pointing to the main program of the game to complete the startup of the target game A.

[0086] Among them, if the target game A is in the root directory of the zip compression package of the game developer and the file name is game.exe, then start_path is game.exe; if the target game A is in the bin folder of the zip compression package of the game developer and the file name is game.exe, then start_path is bin / game.exe.

[0087] This process automates and standardizes game downloads and launches, improving the player experience while ensuring the unified management of traffic statistics and operation control by the gaming platform.

[0088] It should be understood that the size of the serial numbers of the steps in the above embodiments does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0089] Corresponding to the game management method of the above embodiment, Figure 5 A structural block diagram of a game management device 5 provided in an embodiment of the present application is shown. For ease of explanation, only the parts related to the embodiment of the present application are shown.

[0090] Reference Figure 5 The management device 5 is applied to a server where a game platform is deployed. The management device 5 includes a game startup module, which is used to:

[0091] In response to a launch command for any target game listed on the game platform, the target game's downloader executable file is run to download the target game's resource package; the downloader executable file is independently generated by a third party based on the target game's description information and a downloader development tool; the downloader development tool is provided by the platform corresponding to the game platform;

[0092] After the resource pack is downloaded, launch the target game.

[0093] Optionally, the description information is game attribute information, and the game attribute information includes the uniform resource locator of the game background image of the target game, the uniform resource locator of the game resource package, and the game name.

[0094] Optionally, the management device 5 further includes a game listing module, which is used to:

[0095] Before responding to a launch instruction for any target game listed on the game platform, obtaining a downloader execution file;

[0096] Launch the target game based on the downloader executable file.

[0097] Optionally, the downloader execution file is generated by a third party by writing description information into a pre-acquired downloader development tool and then packaging it.

[0098] Optionally, the management device 5 further includes a development tool management module, which is used to:

[0099] Before responding to the launch instruction of any target game listed on the game platform, respond to the request to obtain the downloader development tool and send the downloader development tool to a third party so that the third party can independently generate a downloader execution file based on the description information of the target game and the downloader development tool.

[0100] Optionally, the downloader development tool is a universal downloader SDK, which is configured with a game download function and a game launch function. The universal downloader SDK that completes the game attribute information of the target game is the downloader execution file.

[0101] It should be noted that the information interaction and execution process between the above-mentioned devices / units are based on the same concept as the method embodiment of this application. Their specific functions and technical effects can be found in the method embodiment section and will not be repeated here.

[0102] Figure 6 This is a schematic diagram of the physical structure of a server provided in one embodiment of the present application. Figure 6 As shown, the server 6 of this embodiment includes: at least one processor 60 ( Figure 6 Only one processor is shown), a memory 61, and a computer program 62 stored in the memory 61 and executable on at least one processor 60. When the processor 60 executes the computer program 62, the steps of any of the above-mentioned game management method embodiments are implemented, such as Figure 1 Steps 110-120 are shown.

[0103] The processor 60 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. A general-purpose processor may be a microprocessor or any conventional processor.

[0104] In some embodiments, the memory 61 may be an internal storage unit of the server 6, such as a hard disk or memory of the server 6. In other embodiments, the memory 61 may also be an external storage device of the server 6, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the server 6.

[0105] Furthermore, the memory 61 may include both an internal storage unit of the server 6 and an external storage device. The memory 61 is used to store operating devices, applications, boot loaders, data, and other programs, such as program code of computer programs. The memory 61 may also be used to temporarily store data that has been output or is about to be output.

[0106] Those skilled in the art can clearly understand that, for the convenience and brevity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In actual applications, the above-mentioned functions can be distributed and completed by different functional units and modules as needed, that is, the internal structure of the above-mentioned device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiment can be integrated into one processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application. The specific working process of the units and modules in the above-mentioned system can refer to the corresponding process in the aforementioned method embodiment, which will not be repeated here.

[0107] An embodiment of the present application further provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, it can implement the steps in the above-mentioned various method embodiments.

[0108] An embodiment of the present application provides a computer program product. When the computer program product runs on a server, the server can implement the steps in the above-mentioned method embodiments when executing the computer program product.

[0109] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application implements all or part of the processes in the above-mentioned embodiment method by instructing the relevant hardware through a computer program. The above-mentioned computer program can be stored in a computer-readable storage medium. When the computer program is executed by the processor, it can implement the steps of the above-mentioned various method embodiments. Among them, the above-mentioned computer program includes computer program code, and the above-mentioned computer program code can be in source code form, object code form, executable file or some intermediate form. The above-mentioned computer-readable medium may at least include: any entity or device that can carry the computer program code to the camera / server, a recording medium, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electrical carrier signal, a telecommunication signal and a software distribution medium. For example, a USB flash drive, a mobile hard disk, a magnetic disk or an optical disk.

[0110] In the above embodiments, the description of each embodiment has its own focus. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant description of other embodiments.

[0111] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0112] In the embodiments provided in this application, it should be understood that the disclosed devices / network equipment and methods can be implemented in other ways. For example, the device / network equipment embodiments described above are merely illustrative. For example, the division of the above modules or units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0113] The units described above as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0114] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the various embodiments of the present application, and should all be included in the scope of protection of the present application.

Claims

1. A game management method, characterized in that: Applied to a server deployed with a gaming platform, the management method includes: In response to a launch instruction for any target game listed on the game platform, the downloader execution file of the target game is run to download the resource package of the target game; the downloader execution file is independently generated by a third party based on the description information of the target game and a downloader development tool; the downloader development tool is provided by the platform corresponding to the game platform; After the resource package is downloaded, the target game is started.

2. The management method according to claim 1, wherein: The description information is game attribute information, and the game attribute information includes the uniform resource locator of the game background image of the target game, the uniform resource locator of the game resource package, and the game name.

3. The management method according to claim 1, wherein: Before responding to the start instruction of any target game listed on the game platform, the method further includes: Obtaining the downloader execution file; The target game is launched based on the downloader execution file.

4. The management method according to claim 1, wherein: The downloader execution file is generated by the third party after writing the description information into the pre-acquired downloader development tool and then packaging it.

5. The management method according to any one of claims 1 to 4, characterized in that: Before responding to the start instruction of any target game listed on the game platform, the method further includes: In response to the acquisition request for the downloader development tool, the downloader development tool is sent to the third party, so that the third party can independently generate the downloader execution file based on the description information of the target game and the downloader development tool.

6. The management method according to any one of claims 1 to 4, characterized in that: The downloader development tool is a universal downloader SDK, which is configured with a game download function and a game startup function. The universal downloader SDK that completes the game attribute information of the target game is the downloader execution file.

7. A game management device, characterized in that: Applied to a server deployed with a game platform, the management device includes a game startup module, which is used to: In response to a start instruction for any target game listed on the game platform, running a downloader execution file of the target game to download a resource package of the target game; The downloader execution file is independently generated by a third party based on the description information of the target game and the downloader development tool; the downloader development tool is provided by the platform corresponding to the game platform; After the resource package is downloaded, the target game is started.

8. The management device according to claim 7, wherein: The description information is game attribute information, the downloader development tool is a universal downloader SDK, the universal downloader SDK is configured with game download function and game startup function, and the universal downloader SDK that only completes the game attribute information of the target game is the downloader executable file.

9. A server comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the computer program, the game management method according to any one of claims 1 to 6 is implemented.

10. A computer program product, wherein the computer program product stores a computer program, characterized in that: When the computer program is executed by a processor, the game management method according to any one of claims 1 to 6 is implemented.

Images