Task processing method and device, computing equipment, storage medium and program product

Abstract

Embodiments of the invention provide a task processing method and apparatus, a computing device, a storage medium and a program product, the task processing method comprising: in response to a task request for a target item, determining a to-be-processed target sub-item in the target item; target metadata of the target sub-project is queried, and the metadata is constructed based on an attribute field in a project information table of the target sub-project; based on the target metadata of the target sub-project, querying a project information table of the target sub-project to obtain project information of the target sub-project; and based on the project information of the target sub-project, executing a target task corresponding to the task request. By inquiring and utilizing the unique metadata and the information table of each sub-project in the project, the dynamic loading and unified processing of the configuration information of different sub-projects are realized, each task can be executed based on correct project information, the task processing accuracy and efficiency are improved, and the expandability and adaptability of the system are enhanced.

Description

Technical Field

[0001] The embodiments of this specification relate to the field of computer technology, and in particular to a task processing method and apparatus, a computing device, a storage medium, and a program product. Background Art

[0002] With the diversification of business and the continuous advancement of technology, the differences between various projects have increased significantly, making project management increasingly complex.

[0003] The existing solution is to simplify the task processing process by standardizing the configuration of all projects. This method manages multiple projects by defining a set of common standard configuration templates, so that the same task processing methods and processes can be used when executing tasks, thereby simplifying the management difficulty.

[0004] However, standardizing the configuration of all projects through a unified standard configuration template ignores the uniqueness of the project itself, resulting in the inability to implement some projects that require differential configurations, thereby limiting the establishment and development of new projects. It also lacks flexibility, and standardized configurations cannot quickly and easily adjust project configurations to adapt to new needs and changes. Therefore, a new task processing method is urgently needed that can obtain project information and complete corresponding processing tasks without affecting the normal operation of the project when the target project configurations of multiple tasks are different. Summary of the invention

[0005] In view of this, an embodiment of this specification provides a task processing method. One or more embodiments of this specification also relate to a task processing device, a computing device, a computer-readable storage medium and a computer program product to solve the technical defects existing in the prior art.

[0006] According to a first aspect of an embodiment of this specification, a task processing method is provided, including: In response to a task request for a target project, determining a target sub-project to be processed in the target project; Determining target metadata of the target subproject, wherein the metadata is constructed based on attribute fields in a project information table of the target subproject; Based on the target metadata of the target sub-project, query the project information table of the target sub-project to obtain the project information of the target sub-project; Based on the project information of the target sub-project, the target task corresponding to the task request is executed.

[0007] Optionally, before determining the target metadata of the target sub-item, the method further includes: For each sub-project in the target project, constructing a project information table corresponding to each sub-project based on the project information of each sub-project, wherein the data structure of the project information of each sub-project is different; Extract the information table identifier and attribute fields of the project information table corresponding to each sub-project; The metadata of each sub-item is constructed according to the information table identifier and the attribute field of the project information table corresponding to each sub-item.

[0008] Optionally, constructing a project information table corresponding to each sub-project based on the project information of each sub-project includes: Identifying an environment topology architecture of the target project, wherein the environment topology architecture represents an environment distribution of the target project; Preprocessing the environment topology of the target project according to a preset topology, wherein the preset topology is used to constrain the environment distribution level of the target project; Determine the sub-environment nodes corresponding to the target levels of the preprocessed environment topology architecture for each of the sub-projects; Based on the project information of each sub-project, a corresponding project information table is constructed in the sub-environment node corresponding to each sub-project.

[0009] Optionally, preprocessing the environment topology architecture of the target project according to the preset topology architecture includes: When the number of environment distribution levels in the environment topology architecture is less than the number of environment distribution levels indicated by the preset topology architecture, a sub-environment layer is added to the environment topology architecture.

[0010] Optionally, the task processing method further includes: In response to a request to create a new project, creating an environment topology architecture of the new project according to the preset topology architecture; Determine the sub-environment node corresponding to the target level in the environment topology architecture of the newly added project for each sub-project in the newly added project; Based on the project information of each sub-project in the newly added project, a corresponding project information table is constructed in the sub-environment node corresponding to each sub-project in the newly added project.

[0011] Optionally, querying a project information table of the target subproject based on the target metadata of the target subproject to obtain the project information of the target subproject includes: Determining a project information table of the target sub-project based on an information table identifier included in the target metadata of the target sub-project; Constructing a query statement according to the attribute fields contained in the target metadata; According to the query statement, the project information of the target sub-project is queried from the project information table of the target sub-project.

[0012] Optionally, executing the target task corresponding to the task request based on the project information of the target sub-project includes: Based on the task request, searching for a target processing strategy corresponding to the target task in a preset processing strategy library; The target processing strategy is called to execute the target task based on the project information of the target sub-project.

[0013] Optionally, the target item is a target game, and the target sub-item is a target zone or server of the target game.

[0014] Optionally, determining the target metadata of the target sub-item includes: Rendering each metadata of the target sub-item to obtain an information page containing each metadata of the target sub-item; Displaying the information page; In response to a metadata selection event, target metadata of the target sub-item is determined.

[0015] According to a second aspect of an embodiment of this specification, there is provided a task processing device, including: A determination module, configured to determine a target sub-project to be processed in the target project in response to a task request for the target project; A metadata determination module is configured to determine target metadata of the target sub-project, wherein each metadata of the target sub-project is constructed based on an attribute field in a project information table of the target sub-project; A target information query module is configured to query a project information table of the target sub-project based on the target metadata of the target sub-project to obtain the project information of the target sub-project; The execution module is configured to execute the target task corresponding to the target task request based on the project information of the target sub-project.

[0016] According to a third aspect of an embodiment of this specification, a computing device is provided, including: Memory and processor; The memory is used to store computer programs / instructions, and the processor is used to execute the computer programs / instructions. When the computer programs / instructions are executed by the processor, the steps of the above-mentioned task processing method are implemented.

[0017] According to a fourth aspect of the embodiments of this specification, a computer-readable storage medium is provided, which stores a computer program / instruction, and when the computer program / instruction is executed by a processor, the steps of the above-mentioned task processing method are implemented.

[0018] According to a fifth aspect of the embodiments of this specification, a computer program product is provided, including a computer program / instruction, which implements the steps of the above-mentioned task processing method when executed by a processor.

[0019] An embodiment of the present specification implements a task processing method, including determining a target project to be processed in response to a target task request; querying the project metadata of the target project, wherein the project metadata is constructed based on the attribute fields in the project information table of the target project; querying the project information table of the target project based on the project metadata of the target project to obtain the project information of the target project; and executing the target task corresponding to the target task request based on the project information of the target project. By querying and utilizing the metadata and information table specific to each sub-project in the project, without affecting the normal operation of each sub-project in the project, sub-projects with different configurations can be flexibly responded to, and dynamic loading and unified processing of different sub-project configuration information are achieved, ensuring that each task can be executed based on the correct project information, which not only improves the accuracy and efficiency of task processing, but also enhances the scalability and adaptability of the system, allowing the introduction of more diverse and complex projects without sacrificing management quality. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 is a flowchart of a task processing method provided by an embodiment of this specification; Figure 2 is a processing flow chart of a task processing method provided by an embodiment of this specification; Figure 3 It is a schematic diagram of a task processing method provided by an embodiment of this specification for preprocessing a game environment topology in a game development scenario; Figure 4 It is a flowchart of a newly added item of a task processing method provided by an embodiment of this specification; Figure 5 It is a schematic diagram of an operation and maintenance interface of a task processing method provided by an embodiment of this specification; Figure 6 This is a processing flow chart of a task processing method provided by an embodiment of this specification in a game development scenario; Figure 7 This is a schematic diagram of a processing process of a task processing method provided by an embodiment of this specification in a game development scenario; Figure 8 This is a schematic diagram of a query method of a task processing method provided by an embodiment of this specification in a game development scenario; Fig. 9 It is a product interface diagram of a task processing method provided by an embodiment of this specification in a game development scenario; Fig.10 is a structural diagram of a task processing device provided by an embodiment of this specification; Fig.11 It is a structural block diagram of a computing device provided by an embodiment of this specification. DETAILED DESCRIPTION

[0021] Many specific details are described in the following description to facilitate a full understanding of this specification. However, this specification can be implemented in many other ways than those described herein, and those skilled in the art can make similar generalizations without violating the connotation of this specification, so this specification is not limited to the specific implementation disclosed below.

[0022] The terms used in one or more embodiments of this specification are only for the purpose of describing specific embodiments, and are not intended to limit one or more embodiments of this specification. The singular forms of "a", "said" and "the" used in one or more embodiments of this specification and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings. It should also be understood that the term "and / or" used in one or more embodiments of this specification refers to and includes any or all possible combinations of one or more associated listed items.

[0023] It should be understood that although the terms first, second, etc. may be used to describe various information in one or more embodiments of this specification, this information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of one or more embodiments of this specification, the first may also be referred to as the second, and similarly, the second may also be referred to as the first. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".

[0024] In addition, it should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in one or more embodiments of this specification are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0025] First, the terms involved in one or more embodiments of this specification are explained.

[0026] Metadata: Metadata is data about other data, used to describe, define and explain the structure, attributes, content and other characteristics of data sets, so that the system can understand and process the information in these data sets.

[0027] Schema: Schema is a metadata structure used to define and describe attribute fields in a data set and their mapping relationships. It is widely used in various information systems to achieve standardized description and dynamic processing of data.

[0028] Environment topology architecture: Environment topology architecture is a structural design that describes the hierarchical relationship and connection between grouped environments and their sub-environments in a system. It is used to define the distribution and organization of different environment levels to facilitate system management and resource allocation.

[0029] Information islands: Information islands refer to the phenomenon of data isolation between different systems or projects. These data cannot be effectively shared and communicated, resulting in the formation of independent information areas, making information scattered and difficult to integrate and utilize, which in turn affects overall decision-making efficiency and resource coordination.

[0030] Structured Query Language: SQL (Structured Query Language) is a standard computer language for managing and processing databases. It is mainly used to store, query, operate and manage data in relational database management systems.

[0031] Object-Relational Mapping: Object-Relational Mapping (ORM) is a programming technique used to map the object model defined in an object-oriented programming language to the table structure in a relational database. Through ORM, developers can use an object-oriented approach to operate the database in their applications without having to write SQL statements directly.

[0032] MS SQL database: MS SQL database (Microsoft SQL Server) is a relational database management system developed by Microsoft. It is used to store, manage and retrieve structured data and is widely used in enterprise-level applications to provide data services and support.

[0033] CMDB database: CMDB database (Configuration Management Database) is a database specifically used for IT service management. It is used to store configuration items related to IT infrastructure and their relationship information to help organizations better manage their IT assets and service configurations.

[0034] At present, the existing technical solutions usually adopt a unified and standardized configuration format for each sub-project in each project to achieve the management of different types of sub-projects. Although this method can standardize data management to a certain extent, due to the lack of flexibility, each sub-project is limited to a single modeling and is difficult to adapt to diverse needs, especially when the overall project is expanded or the sub-project is upgraded. In addition, since the configuration information of different projects is isolated from each other, the problem of information islands is caused, which increases the complexity of information acquisition and hinders the formulation of cross-project strategies and the effective allocation of resources.

[0035] In response to the above problems, a task processing method is provided in this specification. This specification also involves a task processing device, a computing device, and a computer-readable storage medium, which are described in detail one by one in the following embodiments.

[0036] See also Figure 1 , Figure 1 A flowchart of a task processing method provided according to an embodiment of the present specification is shown, which specifically includes the following steps.

[0037] Step 102: In response to a task request for a target project, determine a target sub-project to be processed in the target project.

[0038] The target project can be a game project, a financial processing system, a logistics network, etc., which includes multiple sub-projects. The target sub-project can be a game server, a financial business module, a logistics distribution route, etc. The task request is a request to process a target sub-project in the target project, including but not limited to monitoring the status of the sub-project, changing the configuration information of the sub-project, adding or deleting the sub-project, etc. Among them, the number of target projects and target sub-projects can be one or more, and this specification does not make specific restrictions on this.

[0039] Exemplarily, in a game development scenario, the target project is a game project A, and the sub-projects are different servers such as game server 1 and game server 2 included in game project A. When the task request is to change the server configuration of game server 1 in game project A, the target sub-project to be processed is determined to be game server 1; when the task request is to merge game server 1 and game server 2 in game project A, the target sub-projects to be processed are determined to be game server 1 and game server 2; the target projects are a game project A and a game project B, and the sub-projects are different servers such as game server 1 and game server 2 included in game project A and different servers such as game server 1 and game server 2 included in game project B. When the task request is to monitor the status of game server 1 and game server 2 in game project A and game server 1 and game server 2 in game project B, the target sub-projects to be processed are determined to be game server 1 and game server 2 included in game project A and game server 1 and game server 2 included in game project B.

[0040] In the embodiments of this specification, the target sub-project to be processed is determined by responding to the task request for the target project, and the status monitoring, configuration change, server merging and other operations are performed on the target sub-project according to different task requests, thereby achieving unified management and efficient processing of different types of sub-projects, thereby improving the flexibility and accuracy of system management and operation.

[0041] Step 104: Determine target metadata of the target sub-project, wherein each metadata of the target sub-project is constructed based on the attribute fields in the project information table of the target sub-project.

[0042] The types of metadata of the target sub-project include multiple types, including but not limited to schema data structure, data dictionary, attribute list, etc. Each metadata is constructed according to the attribute field in the project information table of the sub-project. The constructed metadata includes the information table identifier, attribute field index, attribute field type, attribute field value annotation, etc. of the project information table of the sub-project. The information table identifier of the project information table indicates the project information table to be queried, the attribute field index indicates the attribute field to be queried, the attribute field type is the data type of the attribute field, and the attribute field value annotation is the annotation information corresponding to the value of the attribute field data. The target metadata refers to the metadata that needs to be processed in the target sub-project corresponding to the task request. The project information table of the target sub-project is a data table, which is used to store data information such as attribute fields and attribute field values ​​of specific information related to the project. These data information in the project information table are the basis for constructing metadata. Through the project information table, the system can dynamically query and process data of different sub-projects.

[0043] Exemplarily, in a game development scenario, the game server information table contains attribute fields of various configuration information of the game server and attribute values ​​corresponding to these attribute fields, including but not limited to attribute fields such as the status of the game server, channel list, and region ID. For example, the game server 1 information table corresponding to the game server 1 of game project A contains the status value of game server 1 as 1, the number of players as 5000, and the version information value as 1.2, etc., and the corresponding attribute fields are the status field, the number of players field, and the version information field. In the case where the task request is to query the status of the game server 1 of game project A, the target metadata of game server 1 is constructed based on these attribute fields, including the information table identifier of the project information table as the game server 1 project table, the attribute field index as the status field, the attribute field type as integer data, and the annotation of the attribute field value as "1" corresponding to "normal operation" and "0" corresponding to "maintenance".

[0044] In the embodiments of this specification, by constructing metadata containing sub-project attribute fields and their index, type and annotation information, the system can quickly locate and process specific data based on these metadata, realize unified management and dynamic query of different sub-project data, improve the flexibility and management efficiency of the system, simplify the operation process, and enhance the readability and comprehensibility of the data.

[0045] Step 106: Based on the target metadata of the target sub-project, query the project information table of the target sub-project to obtain the project information of the target sub-project.

[0046] After obtaining the target metadata of the target sub-project, the project information table of the target sub-project is queried according to the target metadata to obtain the project information of the target sub-project stored in the project information table. The project information includes data information such as various attribute fields and attribute field values. For example, following the above example, in the game development scenario, the game server 1 information table of game project A contains attribute fields: status field, number of players field, version information field, etc., and the corresponding attribute field values ​​are: "1", "5000", "1.2", etc. In the case where the task request is to query the status of game server 1 of game project A, the target metadata of game server 1 includes the information table identifier of the project information table as game server 1 project table, the attribute field index as status field, the attribute field type as integer data, and the annotation of the attribute field value as "1" corresponding to "normal operation" and "0" corresponding to "under maintenance". The game server information obtained by querying the game server 1 information table based on the target metadata of game server 1 is "status field" and "1". According to the annotation of the attribute field value, it can be obtained that "1" corresponds to the "normal operation" state.

[0047] In the embodiments of the present specification, by constructing target metadata including an information table identifier, attribute field index, attribute field type and annotation information of a project information table, accurate positioning and query of target sub-project data is achieved. After obtaining the target metadata of the target sub-project, the system can accurately extract the required project information from the project information table according to the information in the metadata, including each attribute field and its corresponding value. This not only improves the accuracy and efficiency of the query, but also enhances the readability and comprehensibility of the data through annotations, so that the system can quickly respond to and process task requests for different sub-projects, thereby significantly improving the flexibility of data management and overall management efficiency.

[0048] Step 108: Based on the project information of the target sub-project, execute the target task corresponding to the task request.

[0049] Based on the project information of the target sub-project obtained by the query, execute the target task corresponding to the task request, including but not limited to: when the target task is to monitor the status of the target sub-project, return the status information contained in the project information of the target sub-project; when the configuration information of the target sub-project is changed, change the project information of the target sub-project; when the target sub-project is added or deleted, add or delete the project information of the target sub-project.

[0050] For example, following the above example, when the game server information of game project A game server 1 is "status field" and "1", it can be obtained that "1" corresponds to the "normal operation" state according to the annotation of the attribute field value. The solution to the target task of "querying the status of the game server of the game project" is "returning status information", and the status of game project A game server 1 is returned as "normal operation".

[0051] In the embodiments of this specification, by executing the target task corresponding to the task request based on the project information of the target sub-project, automated processing of different task requests is achieved. The system processes the task request according to the corresponding processing method, which not only improves the accuracy and efficiency of task execution, but also reduces the need for manual intervention through automated processes, enhances the flexibility and reliability of the system, and significantly improves the overall management efficiency.

[0052] For example, Figure 2 A process flow chart of a task processing method provided by an embodiment of the present specification is shown as follows: Figure 2 As shown: When the external system needs to process a task, it generates a target task request through the operation and maintenance system interface and sends it to the dynamic query controller; the dynamic query controller determines the target project to be processed based on the target task request and queries the target metadata of the target project; based on the target metadata, it queries the sub-project information table and returns the corresponding project information to the external system. Among them, the sub-project table in the sub-environment records the information table name of each sub-project in the sub-environment, and querying the sub-project information table is to query the corresponding sub-project information table in the sub-project table in the sub-environment.

[0053] An embodiment of the present specification implements a task processing method, including determining a target project to be processed in response to a target task request; querying the project metadata of the target project, wherein the project metadata is constructed based on the attribute fields in the project information table of the target project; querying the project information table of the target project based on the project metadata of the target project to obtain the project information of the target project; and executing the target task corresponding to the target task request based on the project information of the target project. By querying and utilizing the metadata and information table specific to each sub-project in the project, sub-projects with different configurations can be flexibly responded to without affecting the normal operation of each sub-project in the project, and dynamic loading and unified processing of different sub-project configuration information are realized, ensuring that each task can be executed based on the correct project information, which not only improves the accuracy and efficiency of task processing, but also enhances the scalability and adaptability of the system, allowing the introduction of more diverse and complex projects without sacrificing management quality.

[0054] In an optional embodiment of the present specification, before determining the target metadata of the target sub-item, it is necessary to first construct the metadata of each sub-item; Correspondingly, before step 104, the following steps are also included: For each sub-project in the target project, a project information table corresponding to each sub-project is constructed based on the project information of each sub-project, wherein the data structure of the project information of each sub-project is different; Extract the information table identifier and attribute fields of the project information table corresponding to each sub-project; The metadata of each sub-project is constructed according to the information table identifier and attribute field of the project information table corresponding to each sub-project.

[0055] Since the metadata of each sub-project is constructed based on the project information table of each sub-project, it is necessary to construct the project information table of each sub-project first. The project information table is a data table that is used to store data information such as attribute fields and attribute field values ​​of specific information related to the sub-project. In addition, the project information table can also include the sub-environment identifier of the sub-project, the creation timestamp of the sub-project, the update log, and the notes information. These data information in the project information table are the basis for constructing metadata.

[0056] After the project information table is constructed, the information table identifier and attribute field are extracted from the project information table, and the attribute field index is established according to the attribute field; the metadata of each sub-project is constructed according to the information table identifier and attribute field index of the project information table corresponding to each sub-project, and further, the attribute field type and attribute field value annotation can be established according to the attribute field in the project information table, and the metadata of each sub-project is constructed in combination with the information table identifier and attribute field index. The constructed metadata includes the information table identifier, attribute field index, attribute field type, attribute field value annotation, etc. of the project information table of the sub-project. The information table identifier of the project information table indicates the project information table to be queried, such as the game project A game area 1 information table; the attribute field index indicates the attribute field to be queried, such as the status field; the attribute field type is the data type of the attribute field, such as integer data; the attribute field value annotation is the annotation information corresponding to the value of the attribute field data, such as "1" corresponds to "normal operation" and "0" corresponds to "maintenance".

[0057] In the embodiments of the present specification, by pre-constructing metadata for each sub-project, it is ensured that the system can efficiently query and process project information of different sub-projects based on these metadata. Before constructing the metadata, it is necessary to first construct a project information table, and by extracting the information table identifier and attribute fields in the project information table, establishing attribute field indexes, types and annotations, the constructed metadata provides a clear description and rapid positioning capability for the sub-project data, which not only improves the accuracy and efficiency of data acquisition and processing, but also enhances the readability and comprehensibility of the data, thereby significantly improving the flexibility and reliability of the system in managing information of multiple sub-projects with different configurations.

[0058] In an optional embodiment of the present specification, when constructing the project information table, it is necessary to consider the sub-environment node to which the sub-project belongs, and pre-process the environment topology architecture of the entire project; Correspondingly, based on the project information of each sub-project, a project information table corresponding to each sub-project is constructed, including the following steps: Identify an environment topology architecture of a target project, wherein the environment topology architecture represents an environment distribution of the target project; Preprocessing the environment topology of the target project according to the preset topology, wherein the preset topology is used to constrain the environment distribution level of the target project; Determine the sub-environment nodes corresponding to the target level of each sub-project in the pre-processed environment topology architecture; Based on the project information of each sub-project, a corresponding project information table is constructed in the sub-environment node corresponding to each sub-project.

[0059] The environmental topology architecture of a project is a structural design that describes the hierarchical relationship and connection between the group environment and its sub-environment in the project system. It is used to define the distribution and organizational form of different environmental levels to facilitate the management and resource allocation of the project system. The environmental topology architecture generally includes the project level, the group environment level, and the sub-environment level, among which: the project level is the overall project level, which usually represents the entire project, such as project A, project B, etc. Each project level includes one or more group environment levels; the group environment level is the environment level with similar characteristics in the project. This level is used to logically group sub-environments with different functions or different configurations, such as test environment, pre-production environment and production environment, etc. Each group environment level includes one or more sub-environment levels; the sub-environment level is the environment unit that actually carries specific functions or services. It is a concept at the physical level, usually the smallest unit in the environmental topology architecture, and is directly related to a specific server, database or other resource. The preset topology architecture is a preset environmental topology architecture standard, which defines the specific environmental distribution level in the environmental topology architecture. In the preprocessing of the environmental topology architecture of the target project, it is used to constrain the environmental distribution level of the entire target project.

[0060] After preprocessing the environmental topology architecture of the project according to the preset topology architecture, the project information table of the corresponding sub-project can be established in each sub-environment node included in the sub-environment hierarchy. For example, in a game development scenario, the sub-environment can correspond to a specific game server or test instance. For example, the sub-environment can be "XX province server", and the corresponding sub-projects under the sub-environment can be "XX1 server", "XX2 server", etc. The corresponding "XX1 server information table" and "XX2 server information table" are constructed in the "XX province server" sub-environment node, and the sub-environment in the table is marked as "XX province server".

[0061] In the embodiments of the present specification, the environmental topology architecture of the target project is preprocessed according to a preset topology architecture standard, the environmental distribution level of the project is constrained, and the position of each sub-project in its environmental topology architecture is clarified, thereby achieving precise management of sub-projects and effective allocation of resources, improving the organization and manageability of the system, simplifying the process of building and maintaining project information tables in different hierarchical environments, and enhancing the flexibility and scalability of the system.

[0062] In an optional embodiment of the present specification, preprocessing the environment topology of the target project according to the preset topology includes the following steps: When the number of environment distribution levels in the environment topology architecture is less than the number of environment distribution levels indicated by the preset topology architecture, a sub-environment layer is added to the environment topology architecture.

[0063] The environment distribution levels of different projects may also be different. For some projects, the sub-environment nodes in the sub-environment levels they contain do not need to be grouped according to the environment. In this case, the sub-environment node can be either a separate grouping environment level or a separate sub-environment level. At this time, for the preset topology architecture, the number of environment distribution levels for the project is insufficient, so preprocessing operations are required. By using the sub-environment node as the grouping environment level and adding the corresponding sub-environment level under it, the number of environment distribution levels indicated in the preset topology architecture can be aligned.

[0064] For example, Figure 3 A schematic diagram showing a task processing method provided by an embodiment of the present specification for preprocessing a game environment topology in a game development scenario is shown, such as Figure 3 As shown: In the game development scenario, game project A includes overseas servers and test servers, and the corresponding sub-environment nodes are overseas sub-environment nodes and test sub-environment nodes respectively. However, the overseas sub-environment nodes and test sub-environment nodes cannot be grouped by environment. At this time, for the overseas sub-environment nodes and test sub-environment nodes, when the preset topology architecture is "project-environment grouping-sub-environment node", they lack an environment distribution level. Therefore, the overseas sub-environment nodes and test sub-environment nodes can be separately grouped into overseas environment groups and test environment groups, and the same overseas sub-environment nodes and test sub-environment nodes can be added to the corresponding groups respectively, that is, the environment distribution level that meets the constraints of the preset topology architecture.

[0065] In the embodiments of the present specification, by adding sub-environment layers when the number of environment distribution levels in the environment topology architecture is insufficient, it is ensured that the environment topology architecture of all projects can be aligned with the standards of the preset topology architecture, thereby achieving consistent management of the project environment, improving the organization and scalability of the system, and simplifying the resource allocation and management process across environments.

[0066] In an optional embodiment of the present specification, a task processing method provided in the present specification further includes the following steps: In response to a request to create a new project, create an environment topology architecture of the new project according to a preset topology architecture; Determine the sub-environment nodes corresponding to the target level of each sub-project in the new project's environment topology architecture; Based on the project information of each sub-project in the newly added project, a corresponding project information table is constructed in the sub-environment node corresponding to each sub-project in the newly added project.

[0067] In addition to processing tasks for configured projects, if there are newly created projects, the newly created projects also need to be processed. When a new project is needed, a creation request for the new project will be generated. After the new project is added, the environment topology architecture of the new project needs to be preprocessed according to the preset topology architecture to align the number of distribution levels. Then, based on the environment topology architecture of the new project, the sub-environment nodes of the sub-environment level are determined, and then based on the project information of each sub-project in the new project, the corresponding project information table is constructed in the corresponding sub-environment node.

[0068] For example, Figure 4 A flowchart of a newly added item of a task processing method provided by an embodiment of this specification is shown, such as Figure 4 As shown: When adding a new project, the response component responds to the request for adding a new project, establishes a grouping environment for the new project, and determines whether a sub-environment exists. If not, a default default environment is established, that is, a sub-environment node that only has a sub-environment level but no grouping environment level is used as the grouping environment; the operation and maintenance system adds a new sub-environment node; then, in the storage medium, the GameSubEnv dynamic table of the sub-environment is configured and the environment properties are initialized, dynamic sub-projects are created, and sub-project metadata is configured to complete the creation of the new project.

[0069] Exemplarily, in a game development scenario, if a new game project B needs to be added, a corresponding creation request is generated, and the environmental topology architecture of game project B is created according to the preset topology architecture "project-environment grouping-sub-environment node"; it is determined that the "YY1 area server" and "YY2 area server" contained in game project B correspond to the "YY province area server" sub-environment node in the sub-environment hierarchy, and the corresponding "YY1 area server information table" and "YY2 area server information table" are constructed under the "YY province area server" sub-environment node, and the sub-environment in the table is identified as "YY province area server".

[0070] After the project information table is constructed, the metadata of each sub-item of the newly added project can be constructed according to the metadata construction steps recorded in the above-mentioned embodiment.

[0071] In the embodiments of the present specification, by responding to the creation request of a new project, the environmental topology architecture of the project is automatically created and configured according to the preset topology architecture, ensuring that the environmental distribution level of the new project is consistent with the standard of the preset topology architecture, determining the sub-environment node according to the structure of the new project, and constructing the corresponding project information table on this basis, thereby achieving efficient management of the new project and orderly organization of information, and improving the flexibility and management efficiency of the system when processing new projects.

[0072] In an optional embodiment of this specification, step 106 further includes the following steps: Determine a project information table of the target subproject based on an information table identifier included in the target metadata of the target subproject; Construct a query statement based on the attribute fields contained in the target metadata; According to the query statement, the project information of the target sub-project is queried from the project information table of the target sub-project.

[0073] The information table identifier indicates the project information table to be queried. A query statement is a command used to retrieve specific data from a database. It follows specific syntax and rules and is usually constructed based on the Structured Query Language (SQL). The query statement may include multiple operations such as selection, filtering, and sorting to accurately locate the required data records. In an embodiment of the present specification, the query statement is constructed based on the information table identifier and attribute field index in the target metadata, with the purpose of querying specific project information from the project information table of the target subproject. The construction of the query statement relies on the Object-Relational Mapping (ORM) technology, which allows the object model to be mapped to the relational database model, simplifying database operations.

[0074] Optionally, the query statement may include: project information table (target), filter parameters (req), query method and other information. The method of constructing a query statement based on the attribute field index contained in the target metadata includes: determining the project information table, that is, determining it based on the information table identifier of the project information table of the target sub-project in the metadata process; determining the filter parameters, which define the filter conditions, including the attribute field name corresponding to the attribute field index, as well as the attribute field operator, the attribute field value and the attribute field information to be returned; determining the query method, Instance Api. Instance FilteredObject Post is a method for querying a database, which performs a database query by receiving a client connection, a target table identifier and an object containing filter parameters as input. The method dynamically constructs a query statement based on the provided filter conditions, and then retrieves specific data records that meet the conditions from the database.

[0075] For example, in a game development scenario, when it is necessary to query the "server status of server XX1 in game project A", first determine that the project information table to be queried is the "server information table XX1"; then determine that the attribute field name in the filter parameter is the "server status" field, the attribute field operator is the "==" operator, the attribute field value is "1" or "0", and the attribute field information is "normal operation" or "under maintenance"; then determine that the query method is Instance Api. Instance FilteredObject Post; and the corresponding query statement can be constructed.

[0076] In the embodiments of the present specification, by constructing query statements based on information table identifiers and attribute field indexes in the target metadata, accurate queries on project information of target sub-projects are achieved, which not only improves the flexibility and accuracy of the queries, but also simplifies the query process, enabling the system to quickly respond to and process task requests for different sub-projects, thereby improving overall management efficiency and data processing capabilities.

[0077] In an optional embodiment of this specification, step 108 further includes the following steps: Based on the task request, search for the target processing strategy corresponding to the target task in the preset processing strategy library; Call the target processing strategy and execute the target task based on the project information of the target subproject.

[0078] When there are many tasks corresponding to the task request and the task processing method is complex, a preset processing strategy library containing the processing methods corresponding to each task can be built. The preset processing strategy library refers to a collection of a series of predefined processing strategies, which is used to automatically select the corresponding processing scheme according to different target tasks. After querying and obtaining the project information of the target sub-project, the system can automatically call the processing method of the corresponding target task in the preset processing strategy library according to the task request to execute the target task corresponding to the task request.

[0079] For example, in a game development scenario, the preset processing strategy library stores processing methods for different target tasks for different game servers, such as the target task is to query the status of the target game server, and return the status information contained in the game server information of the target game server; the target game server configuration information is changed, and the processing method is to change the target game server configuration information; the target task is to add or delete a target sub-project, and the processing method is to add or delete the project information of the target sub-project, etc. When the target task is received as "query the server status of the XX1 server in game project A", the corresponding target processing strategy is searched in the preset processing strategy library as "return the server status information contained in the XX1 server information table in game project A" and the corresponding processing operation is performed accordingly, that is, the corresponding server status information is returned to complete the target task.

[0080] In the embodiments of the present specification, by searching a preset processing strategy library for a processing strategy that matches a specific task request and automatically calling the strategy to execute the task, the processing flow of complex tasks is simplified, processing efficiency and accuracy are improved, and consistency and reliability of task processing are ensured.

[0081] In an optional embodiment of this specification, step 104 further includes the following steps: Rendering each metadata of the target sub-item to obtain an information page containing each metadata of the target sub-item; Display information page; In response to the metadata selection event, target metadata of the target sub-item is determined.

[0082] In order to determine the target metadata of the target sub-item, the metadata of the target sub-item can be rendered to obtain an information page containing the metadata of the target sub-item, and the information page is displayed. In response to the metadata selection event, the target metadata of the target sub-item is determined. The metadata selection event can be that the user selects the target metadata in the information page, or selects in the information page according to the default selection method, or can be a selection event in other ways, which is not specifically limited in this specification.

[0083] For example, in a game development scenario, in order to determine the target metadata of the XX1 server of the target sub-project game project A, the metadata of the XX1 server, such as the status attribute field, the number of players field, the version information field, etc., can be rendered to obtain an information page containing these fields and displayed. When the user needs to query the status of the XX1 server, he can determine the status attribute field as the target metadata by selecting the selection event of the status attribute field.

[0084] In the embodiments of the present specification, by rendering the metadata of each target sub-item into an information page and displaying it, and then responding to a selection event to determine the target metadata of the target sub-item, the required target metadata can be selected intuitively, which simplifies the target metadata determination process, improves the user experience and selection accuracy during task processing, and ensures that the required information can be obtained quickly and accurately.

[0085] For example, Figure 5 A schematic diagram of an operation and maintenance interface of a task processing method provided by an embodiment of this specification is shown. Figure 5 As shown: The operation and maintenance workbench provides a variety of interfaces for clients or users, and users can initiate task processing requests based on different interfaces; the presentation layer renders the UI interface according to the target sub-project and interacts with users through the API interface; the core business layer includes a dynamic query / change engine, which can complete the "status modification", "region and server dashboard", "region and server version information", and "Schema editing" task requests in the background management, as well as the "region and server status query" and "game status query" task requests in the external interface; the data layer contains environment metadata and a dynamic region and server table, and the dynamic region and server table contains a list of regions and servers in each environment of each game; the data layer stores data in a database, and the database can be an MS SQL database or a CMDB database, or other storage media, and this manual does not make specific restrictions on this.

[0086] The following combination Figure 6 , Attachment Figure 7 , taking the application of the task processing method provided in this specification in the game development scenario as an example, the task processing method is further explained. Figure 6 A processing flow chart of a task processing method provided by an embodiment of the present specification in a game development scenario is shown, which specifically includes the following steps: Step 602: accepting a target task request, and determining a target region and server of a target game according to the target task request; Step 604: pre-processing the environment topology architecture of the target game; Step 606: query the metadata of the target server to obtain the server information of the target server; Step 608: Based on the target task request, searching for a target processing strategy corresponding to the target task in a preset processing strategy library; Step 610: Call the target processing strategy and execute the target task for the target game based on the server information of the target server.

[0087] Figure 7 FIG. 1 shows a schematic diagram of a processing process of a task processing method provided by an embodiment of the present specification in a game development scenario, such as Figure 7As shown: After receiving the target task request, preprocessing operations need to be performed, where the preprocessing operations include aligning the environmental topology architecture of the target game and determining the target area and server of the game. After determining the target area and server, the metadata of the target area and server will be queried, where the metadata of the target area and server include Schema metadata and the corresponding game area and server information table; after querying the area and server information of the target area and server, the processing method of the target task will be queried in the preset processing strategy library, and the target game project (such as game B in the example in the figure) will be processed based on the processing method.

[0088] In the above step 606, the metadata of the target zone and server may be a Schema data structure table, which has a mapping relationship with the zone and server information table of the target zone and server. Figure 8 A schematic diagram of a query method of a task processing method provided by an embodiment of this specification in a game development scenario is shown, such as Figure 8 As shown: After the target server is determined, the operation and maintenance system interface queries the Schema metadata of the target server, and through the addressing module, in combination with the target server information table name obtained in the Schema metadata, queries the server information of the target server in the database, and returns the server information of the target server. The database can be a MS SQL database or a CMDB database, or other storage media, which is not specifically limited in this specification.

[0089] The following combination Fig. 9 Taking the application of the task processing method provided in this specification in the game development scenario as an example, a task processing product interface provided by the task processing method is further described. Fig. 9 A schematic diagram of a product interface of a task processing method provided by an embodiment of this specification in a game development scenario is shown, specifically: The upstream system is the upper-level management system of the entire game project. It can manage game projects and game servers in the game projects. For example, it can issue alarms based on the status of the server list, monitor game projects and servers, and maintain status changes of game environment information. The display layer displays the server status list and game environment information of the game project, and users can intuitively obtain various information about the game project from the display layer. The game environment contains game environment meta-information, which is the Schema data structure meta-information of each game project. The server list contains the server information of each game project.

[0090] Corresponding to the above-mentioned task processing method embodiment, this specification also provides a task processing device embodiment. Fig.10 FIG. 1 shows a schematic diagram of a task processing device provided by an embodiment of the present specification. Fig.10 As shown, the device comprises: The determination module 1002 is configured to determine a target item to be processed in response to a target task request; The metadata determination module 1004 is configured to determine target metadata of the target sub-project, wherein each metadata of the target sub-project is constructed based on the attribute fields in the project information table of the target sub-project; The target information query module 1006 is configured to query the project information table of the target sub-project based on the target metadata of the target sub-project to obtain the project information of the target sub-project; The execution module 1008 is configured to execute the target task corresponding to the target task request based on the project information of the target sub-project.

[0091] Optionally, the target metadata query module further includes: A construction module is configured to construct a project information table corresponding to each sub-project in the target project based on the project information of each sub-project, wherein the data structure of the project information of each sub-project is different; Extract the information table identifier and attribute fields of the project information table corresponding to each sub-project; The metadata of each sub-project is constructed according to the information table identifier and attribute field of the project information table corresponding to each sub-project.

[0092] Optionally, the building block is further configured to: Identify an environment topology architecture of a target project, wherein the environment topology architecture represents an environment distribution of the target project; Preprocessing the environment topology of the target project according to the preset topology, wherein the preset topology is used to constrain the environment distribution level of the target project; Determine the sub-environment nodes corresponding to the target level of each sub-project in the pre-processed environment topology architecture; Based on the project information of each sub-project, a corresponding project information table is constructed in the sub-environment node corresponding to each sub-project.

[0093] Optionally, the building block is further configured to: When the number of environment distribution levels in the environment topology architecture is less than the number of environment distribution levels indicated by the preset topology architecture, a sub-environment layer is added to the environment topology architecture.

[0094] Optionally, the building blocks also include: The project creation module is configured to respond to a creation request of a new project and create an environment topology architecture of the new project according to a preset topology architecture; Determine the sub-environment nodes corresponding to the target level of each sub-project in the new project's environment topology architecture; Based on the project information of each sub-project in the newly added project, a corresponding project information table is constructed in the sub-environment node corresponding to each sub-project in the newly added project.

[0095] Optionally, the target information query module is further configured to: Determine a project information table of the target subproject based on an information table identifier included in the target metadata of the target subproject; Construct a query statement based on the attribute field index contained in the target metadata; According to the query statement, the project information of the target sub-project is queried from the project information table of the target sub-project.

[0096] Optionally, the execution module is further configured to: Based on the task request, search for the target processing strategy corresponding to the target task in the preset processing strategy library; Call the target processing strategy and execute the target task based on the project information of the target subproject.

[0097] Optionally, the determination module is further configured such that the target item is a target game, and the target sub-item is a target zone and server of the target game.

[0098] Optionally, the metadata determination module is further configured to: Rendering each metadata of the target sub-item to obtain an information page containing each metadata of the target sub-item; Display information page; In response to the metadata selection event, target metadata of the target sub-item is determined.

[0099] In the embodiment of the present specification, in response to a target task request, a target project to be processed is determined; the project metadata of the target project is queried, wherein the project metadata is constructed based on the attribute fields in the project information table of the target project; based on the project metadata of the target project, the project information table of the target project is queried to obtain the project information of the target project; based on the project information of the target project, the target task corresponding to the target task request is executed. By querying and utilizing the metadata and information table specific to each sub-project in the project, sub-projects with different configurations can be flexibly responded to without affecting the normal operation of each sub-project in the project, and dynamic loading and unified processing of configuration information of different sub-projects are realized, ensuring that each task can be executed based on the correct project information, which not only improves the accuracy and efficiency of task processing, but also enhances the scalability and adaptability of the system, allowing the introduction of more diverse and complex projects without sacrificing management quality.

[0100] The above is a schematic scheme of a task processing device of this embodiment. It should be noted that the technical scheme of the task processing device and the technical scheme of the above task processing method belong to the same concept, and the details of the technical scheme of the task processing device that are not described in detail can all be referred to the description of the technical scheme of the above task processing method.

[0101] Fig.11 The structure block diagram of a computing device provided by an embodiment of the present specification is shown. The components of the computing device 1100 include but are not limited to a memory 1110 and a processor 1120. The processor 1120 is connected to the memory 1110 via a bus 1130, and the database 1150 is used to store data.

[0102] The computing device 1100 also includes an access device 1140, which enables the computing device 1100 to communicate via one or more networks 1160. Examples of these networks include a 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. The access device 1140 may include one or more of any type of network interface (e.g., a Network Interface Controller (NIC)) of wired or wireless, such as an IEEE 802.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, and a Near Field Communication (NFC).

[0103] In one embodiment of the present specification, the above components of the computing device 1100 and Fig.11 Other components not shown in the figure may also be connected to each other, for example, via a bus. It should be understood that Fig.11 The computing device structure block diagram shown is only for the purpose of illustration, and is not intended to limit the scope of this specification. Those skilled in the art can add or replace other components as needed.

[0104] The computing device 1100 may be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (e.g., a tablet computer, a personal digital assistant, a laptop computer, a notebook computer, a netbook, etc.), a mobile phone (e.g., a smart phone), a wearable computing device (e.g., a smart watch, smart glasses, etc.), or other types of mobile devices, or a stationary computing device such as a desktop computer or a personal computer (PC). The computing device 1100 may also be a mobile or stationary server.

[0105] The processor 1120 is used to execute the following computer program / instruction, which implements the steps of the above-mentioned task processing method when executed by the processor.

[0106] The above is a schematic scheme of a computing device of this embodiment. It should be noted that the technical scheme of the computing device and the technical scheme of the above-mentioned task processing method belong to the same concept, and the details not described in detail in the technical scheme of the computing device can be referred to the description of the technical scheme of the above-mentioned task processing method.

[0107] An embodiment of the present specification also provides a computer-readable storage medium storing a computer program / instruction, which implements the steps of the above-mentioned task processing method when executed by a processor.

[0108] The above is a schematic scheme of a computer-readable storage medium of this embodiment. It should be noted that the technical scheme of the storage medium and the technical scheme of the above-mentioned task processing method belong to the same concept, and the details not described in detail in the technical scheme of the storage medium can be referred to the description of the technical scheme of the above-mentioned task processing method.

[0109] An embodiment of the present specification also provides a computer program product, including a computer program / instruction, which implements the steps of the above-mentioned task processing method when executed by a processor.

[0110] The above is a schematic solution of a computer program product of this embodiment. It should be noted that the technical solution of the computer program product and the technical solution of the above-mentioned task processing method belong to the same concept, and the details not described in detail in the technical solution of the computer program product can be referred to the description of the technical solution of the above-mentioned task processing method.

[0111] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0112] The computer instructions include computer program codes, which may be in source code form, object code form, executable files or some intermediate forms, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, USB flash drive, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium, etc. It should be noted that the contents contained in the computer-readable medium may be appropriately increased or decreased according to the requirements of patent practice. For example, in some regions, according to patent practice, computer-readable media do not include electric carrier signals and telecommunication signals.

[0113] It should be noted that, for the above-mentioned method embodiments, for the sake of simplicity of description, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the embodiments of this specification are not limited by the order of the actions described, because according to the embodiments of this specification, some steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the embodiments of this specification.

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

[0115] The preferred embodiments of this specification disclosed above are only used to help explain this specification. The optional embodiments do not describe all the details in detail, nor do they limit the invention to only the specific implementation methods described. Obviously, many modifications and changes can be made according to the content of the embodiments of this specification. This specification selects and specifically describes these embodiments in order to better explain the principles and practical applications of the embodiments of this specification, so that technicians in the relevant technical field can well understand and use this specification. This specification is only limited by the claims and their full scope and equivalents.

Claims

1. A task processing method, characterized in that: include: In response to a task request for a target project, determining a target sub-project to be processed in the target project; Determining target metadata of the target sub-project, wherein each metadata of the target sub-project is constructed based on an attribute field in a project information table of the target sub-project; Based on the target metadata of the target sub-project, query the project information table of the target sub-project to obtain the project information of the target sub-project; Based on the project information of the target sub-project, the target task corresponding to the task request is executed.

2. The task processing method according to claim 1, characterized in that: Before determining the target metadata of the target sub-item, the method further includes: For each sub-project in the target project, constructing a project information table corresponding to each sub-project based on the project information of each sub-project, wherein the data structure of the project information of each sub-project is different; Extract the information table identifier and attribute fields of the project information table corresponding to each sub-project; The metadata of each sub-item is constructed according to the information table identifier and the attribute field of the project information table corresponding to each sub-item.

3. The task processing method according to claim 2, characterized in that: The step of constructing a project information table corresponding to each sub-project based on the project information of each sub-project includes: Identifying an environment topology architecture of the target project, wherein the environment topology architecture represents an environment distribution of the target project; Preprocessing the environment topology of the target project according to a preset topology, wherein the preset topology is used to constrain the environment distribution level of the target project; Determine the sub-environment nodes corresponding to the target levels of the preprocessed environment topology architecture for each of the sub-projects; Based on the project information of each sub-project, a corresponding project information table is constructed in the sub-environment node corresponding to each sub-project.

4. The task processing method according to claim 3, characterized in that: The preprocessing of the environment topology architecture of the target project according to the preset topology architecture includes: When the number of environment distribution levels in the environment topology architecture is less than the number of environment distribution levels indicated by the preset topology architecture, a sub-environment layer is added to the environment topology architecture.

5. The task processing method according to claim 3, characterized in that: Also includes: In response to a request to create a new project, creating an environment topology architecture of the new project according to the preset topology architecture; Determine the sub-environment node corresponding to the target level in the environment topology architecture of the newly added project for each sub-project in the newly added project; Based on the project information of each sub-project in the newly added project, a corresponding project information table is constructed in the sub-environment node corresponding to each sub-project in the newly added project.

6. The task processing method according to any one of claims 1 to 5, characterized in that: The querying of the project information table of the target sub-project based on the target metadata of the target sub-project to obtain the project information of the target sub-project includes: Determining a project information table of the target sub-project based on an information table identifier included in the target metadata of the target sub-project; Constructing a query statement according to the attribute fields contained in the target metadata; According to the query statement, the project information of the target sub-project is queried from the project information table of the target sub-project.

7. The task processing method according to any one of claims 1 to 5, characterized in that: The executing the target task corresponding to the task request based on the project information of the target sub-project includes: Based on the task request, searching for a target processing strategy corresponding to the target task in a preset processing strategy library; The target processing strategy is called to execute the target task based on the project information of the target sub-project.

8. The task processing method according to any one of claims 1 to 5, characterized in that: The target item is a target game, and the target sub-item is a target region and server of the target game.

9. The task processing method according to any one of claims 1 to 5, characterized in that: The step of determining target metadata of the target sub-item includes: Rendering each metadata of the target sub-item to obtain an information page containing each metadata of the target sub-item; Displaying the information page; In response to a metadata selection event, target metadata of the target sub-item is determined.

10. A task processing device, characterized in that: include: A determination module, configured to determine a target item to be processed in response to a target task request; A metadata determination module is configured to determine target metadata of the target sub-project, wherein each metadata of the target sub-project is constructed based on an attribute field in a project information table of the target sub-project; A target information query module is configured to query a project information table of the target sub-project based on the target metadata of the target sub-project to obtain the project information of the target sub-project; The execution module is configured to execute the target task corresponding to the target task request based on the project information of the target sub-project.

11. A computing device, characterized in that: include: Memory and processor; The memory is used to store computer programs / instructions, and the processor is used to execute the computer programs / instructions. When the computer programs / instructions are executed by the processor, the steps of the task processing method according to any one of claims 1 to 9 are implemented.

12. A computer-readable storage medium, characterized in that: It stores a computer program / instruction, which, when executed by a processor, implements the steps of the task processing method described in any one of claims 1 to 9.

13. A computer program product, characterized in that The method comprises a computer program / instruction, which, when executed by a processor, implements the steps of the task processing method according to any one of claims 1 to 9.

Images