Government affair resource management method and computer equipment

Abstract

The invention discloses a government affair resource management method and computer equipment, and relates to the technical field of resource management. The method comprises the following steps: acquiring a plurality of government affair resources, wherein the plurality of government affair resources comprise one or more of an application resource, a component resource, a data resource or a cloud resource; and based on a plurality of government affair resources, taking the government affair resources as nodes, and taking the incidence relation among the government affair resources as edges, constructing a resource map. Establishing one or more operation management relationships based on the resource map; and managing the plurality of government affair resources based on the operation management relationship. Through visual display of the resource map, a manager can quickly understand and master distribution and association conditions of multiple government affair resources, so that the management efficiency of the government affair resources is improved.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of resource management technology, and in particular to government resource management methods and computer equipment. Background Art

[0002] With the rapid development of informatization, the types and quantity of resources involved in informatization are constantly increasing. Taking government informatization as an example, the government resources involved in government informatization include all software and hardware facilities, data information, and related technical support and services used in the informatization process.

[0003] In related technologies, the management methods for various government resources often rely on offline management methods, such as submitting and managing them in the form of paper or electronic documents, or developing different software for different government resources.

[0004] However, whether it is offline management or the development of different software for management, due to the independence of different government resources, information transmission is not timely and difficult to share, it is easy for different government resources to form information islands, resulting in low management efficiency of government resources. Summary of the Invention

[0005] The embodiments of the present application provide a government resource management method and computer equipment, which improve the management efficiency of government resources.

[0006] To achieve the above objectives, the present invention adopts the following technical solutions:

[0007] In a first aspect, a method for managing government resources is provided. The method comprises: obtaining multiple government resources, wherein the multiple government resources include one or more of application resources, component resources, data resources, or cloud resources; constructing a resource graph based on the multiple government resources, using the government resources as nodes and relationships between the government resources as edges; establishing one or more operation and management relationships based on the resource graph; and managing the multiple government resources based on the operation and management relationships.

[0008] The solution provided in this application unifies the management of multiple government resources and displays them in an intuitive, graphical resource map. The intuitive display of the resource map enables managers to quickly understand and grasp the distribution and correlation of multiple government resources, thereby improving the management efficiency of government resources. In addition, the construction of a resource map containing multiple government resources also promotes information sharing among multiple government resources, breaks down information silos, and improves the transparency and utilization of government information.

[0009] A possible implementation method is to construct a resource map based on multiple government resources, with government resources as nodes and the association relationships between government resources as edges. The method can be specifically implemented as one or more of the following: establishing nodes for multiple government resources; calling component resources based on application resources, and establishing a component pointing relationship between application resources and component resources; calling data resources based on application resources, and establishing a data pointing relationship between application resources and data resources; calling cloud resources based on application resources, and establishing an application-cloud resource pointing relationship between application resources and cloud resources; establishing an application-association relationship between the first application resource and the second application resource based on the association relationship between the first application resource and the second application resource; calling cloud resources based on component resources, and establishing a component-cloud resource pointing relationship between component resources and cloud resources; using at least one of the component pointing relationship, data pointing relationship, cloud resource pointing relationship, application association relationship or component-cloud resource pointing relationship as an edge to obtain a resource map.

[0010] In another possible implementation, the component pointing relationship, data pointing relationship, cloud resource pointing relationship, application association relationship or component cloud resource pointing relationship is determined based on the entered association relationship information, or based on the dependency relationship between different resources.

[0011] In another possible implementation, the dependency relationship includes at least one of the following: a data flow relationship, a call relationship, a storage relationship, or a location deployment relationship.

[0012] In another possible implementation, the attribute information of the application resources includes: application name, application code, source, status, review status, application type, application field, core business, integrated construction status, integrated construction scope, application introduction, access address, construction area, construction plan, construction basis, responsible unit, collaborative unit, developer, security vendor, average daily visits or average daily active users, at least one of them.

[0013] In another possible implementation, the attribute information of the component resource includes at least one of: component code, component name, publisher, unit code, technical field, functional field, usage type, component type, number of applications, component health, number of component calls, service unit, service contact or release time.

[0014] In another possible implementation, the attribute information of data resources includes: data resource code, data directory name, collection table name, information resource summary, data source, field, data health, government data provider, government data summary, provision channel, data type, data source unit, number of visits, number of applications, source application code, source application name, administrative area code, source or at least one of data sensitivity level.

[0015] In another possible implementation, the operational management relationships include object management relationships. Establishing one or more operational management relationships based on a resource map can be specifically implemented by, in response to a configuration instruction for an object management relationship in the resource map, configuring attribute information for the object management relationship corresponding to the configuration instruction. The attribute information for the object management relationship includes dependency category and / or dependency strength. By configuring attribute information for the relationship, a deeper understanding of the interdependence and influence relationships between different government resources can be achieved, thereby enabling refined management of the relationships between government resources.

[0016] Another possible implementation method is that the operation management relationship includes: supplier management relationship; establishing one or more operation management relationships based on the resource map can be specifically implemented as follows: based on supplier resources, creating nodes corresponding to supplier resources in the resource map, and creating edges in the resource map corresponding to the association relationship between supplier resources and government resources.

[0017] Another possible implementation method is that the operation management relationship includes: risk management relationship; one or more operation management relationships are established based on the resource map, which can be specifically implemented as follows: setting a corresponding color for each government resource, and the color of the node corresponding to each government resource is related to the health of the government resource. Setting a corresponding color for each cloud resource, and the color of the node corresponding to each cloud resource is related to the health of the cloud resource. Setting a corresponding color for each component resource, and the color of the node corresponding to each component resource is related to the health of the component resource. Color coding can quickly identify which application resources, cloud resources, and component resources are in normal, warning, or fault status, so that action can be taken quickly. In addition, the intuitive display of health through color simplifies the monitoring process, and there is no need to go into the detailed logs or status reports of each government resource.

[0018] In another possible implementation, the health of cloud resources is negatively correlated with the utilization rate of cloud resources.

[0019] Another possible implementation method is to manage multiple government resources based on the operation and management relationship, which can be specifically implemented as any of the following:

[0020] The application digital twin view displays a topological view of application resources. This view includes the nodes corresponding to the application resources and other nodes with which the nodes have edges. The application digital twin is a digital model that digitally describes the nodes and edges corresponding to the application resources. The cloud digital twin view displays a topological view of cloud resources. This view includes the nodes corresponding to the cloud resources and other nodes with which the nodes have edges. The cloud digital twin is a digital model that digitally describes the nodes and edges corresponding to the cloud resources. The component digital twin view displays a topological view of component resources. This view includes the nodes corresponding to the component resources and other nodes with which the nodes have edges. The component digital twin is a digital model that digitally describes the nodes and edges corresponding to the component resources. The data digital twin view displays a topological view of data resources. This view includes the nodes corresponding to the data resources and other nodes with which the nodes have edges. The data digital twin is a digital model that digitally describes the nodes and edges corresponding to the data resources. Multiple display perspectives for the resource map are provided. The global perspective provides an overview of the entire government resource ecosystem, facilitating a macro-level understanding and analysis of government resource layout. The local perspective helps quickly locate government resources, enabling targeted review and optimization of these resources.

[0021] In a second aspect, a government resource management device is provided, which includes: an acquisition module, a construction module, and a management module.

[0022] The above-mentioned acquisition module is used to obtain multiple government resources, which include one or more of application resources, component resources, data resources or cloud resources.

[0023] The above-mentioned construction module is used to construct a resource map based on multiple government resources, using government resources as nodes and the relationships between government resources as edges. One or more operation and management relationships are established based on the resource map.

[0024] The above management module is used to manage multiple government resources based on operation and management relationships.

[0025] The government resource management device provided in the second aspect is used to execute the government resource management method provided by the first aspect or any possible implementation method of the first aspect. The technical effects corresponding to any implementation method in the second aspect can be referred to the technical effects corresponding to any implementation method in the first aspect, and will not be repeated here.

[0026] In a third aspect, a computer device is provided, comprising: a processor and a memory, wherein at least one computer program is stored in the memory, and the at least one computer program is loaded and executed by the processor to implement the government resource management method described in the first aspect or any possible implementation method of the first aspect.

[0027] In a fourth aspect, a computer-readable storage medium is provided, in which at least one computer program is stored. The at least one computer program is loaded and executed by a processor to implement the government resource management method as described in the first aspect or any one of the implementation methods of the first aspect.

[0028] In the fifth aspect, a computer program product is provided, which includes a computer program or instructions. When the computer program or instructions are executed by a processor, the government resource management method described in the first aspect or any one of the implementation methods in the first aspect is implemented.

[0029] In the sixth aspect, an embodiment of the present application provides a chip system comprising at least one processor and at least one interface circuit, wherein the at least one interface circuit is used to perform transceiver functions and send instructions to the at least one processor. When the at least one processor executes the instructions, the at least one processor executes to implement the government resource management method as described in the first aspect or any one of the implementation methods in the first aspect.

[0030] The solutions provided in aspects 3 to 6 above are used to implement the methods provided in aspect 1 above or any one of the implementations of aspect 1 above, and their specific implementations are not described in detail here. The technical effects corresponding to any one of the implementations of aspects 3 to 6 above can be found in the technical effects corresponding to aspect 1 above or any one of the implementations of aspect 1 above, and are not described in detail here.

[0031] It should be noted that various possible implementations of any of the above aspects can be combined under the premise that the solutions are not contradictory. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] Figure 1 A schematic diagram of the architecture of a computer system provided in an embodiment of the present application;

[0033] Figure 2 A flowchart of a method for managing government resources provided in an embodiment of the present application;

[0034] Figure 3 A schematic diagram of inputting attribute information of an application resource provided in an embodiment of the present application;

[0035] Figure 4A schematic diagram of inputting attribute information of a component resource provided in an embodiment of the present application;

[0036] Figure 5 A schematic diagram of inputting attribute information of a data resource provided in an embodiment of the present application;

[0037] Figure 6 A schematic diagram of entering attribute information of a cloud resource provided in an embodiment of the present application;

[0038] Figure 7 A schematic diagram of a configuration object management relationship provided in an embodiment of the present application;

[0039] Figure 8 A schematic diagram of creating a new node provided in an embodiment of the present application;

[0040] Figure 9 A schematic diagram of an early warning monitoring mechanism provided in an embodiment of the present application;

[0041] Figure 10 A schematic diagram of a resource map provided in an embodiment of the present application;

[0042] Figure 11 A schematic diagram of a topological view of application resources provided in an embodiment of the present application;

[0043] Figure 12 A schematic diagram of a topological view of cloud resources provided in an embodiment of the present application;

[0044] Figure 13 A schematic diagram of a topological view of component resources provided in an embodiment of the present application;

[0045] Figure 14 A schematic diagram of a topological view of a data resource provided in an embodiment of the present application;

[0046] Figure 15 A schematic diagram of the structure of a government resource management device provided in an embodiment of the present application;

[0047] Figure 16 A schematic diagram of the structure of a computer device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0048] In the embodiments of the present application, in order to clearly describe the technical solutions of the embodiments of the present application, words such as "first" and "second" are used to distinguish between identical or similar items with substantially the same functions and effects. Those skilled in the art will understand that words such as "first" and "second" do not limit the quantity or execution order, and words such as "first" and "second" do not necessarily mean different. There is no order of precedence or priority between the technical features described by "first" and "second".

[0049] In the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of this application should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner to facilitate understanding.

[0050] In the embodiments of the present application, at least one can also be described as one or more, and multiple can be two, three, four or more, which is not limited in this application.

[0051] In addition, the network architecture and scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field can know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0052] It should be noted that the information (including but not limited to device information, personal information of the subject, etc.), data (including but not limited to data used for analysis, stored data, displayed data, etc.), and signals involved in this application are all authorized by the subject 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. For example, the government resources involved in this application are all obtained with full authorization.

[0053] Figure 1 The schematic diagram of the computer system architecture provided by one embodiment of the present application is shown. The computer system may include: a terminal 100 and a server 200.

[0054] The terminal 100 can be an electronic device such as a mobile phone, a tablet computer, a vehicle-mounted terminal (car computer), a wearable device, a personal computer (PC), a vehicle-mounted terminal, an aircraft, an unmanned vending terminal, etc. The terminal 100 can be installed with a client that runs a target application. The target application can be an application that refers to government resource management, or it can be other applications that provide government resource management functions. This application does not limit this. For example, the resource map can be viewed / edited in the terminal 100. In addition, this application does not limit the form of the target application, including but not limited to applications (Application, App) installed in the terminal 100, applets, etc., and can also be in the form of a web page.

[0055] Server 200 can be a standalone physical server, a server cluster or distributed system consisting of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud computing services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial palm image recognition platforms. Server 200 can be the backend server of the target application described above, providing backend services to the client of the target application.

[0056] Cloud technology refers to a hosting technology that unifies hardware, software, and network resources within a wide area network (WAN) or local area network (LAN) to enable data computing, storage, processing, and sharing. Cloud technology is a general term for network technology, information technology, integration technology, management platform technology, and application technology, all based on the cloud computing business model. It can form a resource pool that can be used on demand with flexibility and convenience. Cloud computing technology will become a crucial support. Backend services for technical network systems, such as video websites, image websites, and more portals, require significant computing and storage resources. With the rapid development and application of the internet industry, every item will likely have its own unique identification mark and will need to be transmitted to backend systems for logical processing. Data of varying levels will be processed separately, and data from all industries will require a strong system backend, which can only be achieved through cloud computing.

[0057] In some embodiments, the aforementioned servers can also be implemented as nodes in a blockchain system. Blockchain is a novel application model for computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanisms, and encryption algorithms. Essentially, a blockchain is a decentralized database, a series of data blocks generated using cryptographic methods. Each block contains information about a batch of network transactions, used to verify the validity of the information (to prevent counterfeiting) and generate the next block. A blockchain can include an underlying blockchain platform, a platform product and service layer, and an application service layer.

[0058] The terminal 100 and the server 200 may communicate with each other via a network, such as a wired or wireless network.

[0059] The embodiment of the present application provides a method for managing government resources. The execution subject of each step can be a computer device, which refers to an electronic device with data calculation, processing and storage capabilities. Figure 1Taking the implementation environment of the solution shown as an example, the government resource management method can be executed by the terminal 100 (such as the client of the target application installed and running in the terminal 100 executes the government resource management method), or the government resource management method can be executed by the server 200, or the terminal 100 and the server 200 can interact and cooperate to execute it. This application does not limit this.

[0060] Figure 2 A flowchart of a government resource management method is provided for an embodiment of the present application. The government resource management method is executed by a computer device. The computer device can be Figure 1 The terminal 100 and the server 200 in the illustrated computer system.

[0061] like Figure 2 As shown, the government resource management method may include:

[0062] Step 202: The computer device obtains multiple government resources.

[0063] Among them, government resources refer to all software and hardware facilities, data information, and related technical support and services generated, managed or used in the process of government informatization.

[0064] Optionally, the multiple government resources include at least one of application resources, component resources, data resources or cloud resources, but are not limited to these. The embodiments of the present application do not make specific limitations on this.

[0065] Application resources refer to the various software applications used in the process of government informationization. These applications are used to process workflows, provide services, and manage information. Examples include e-government service platforms, online approval systems, and internal management systems.

[0066] Component resources refer to the component services relied upon in the process of government informationization. For example, identity authentication service components, payment components, and message queue service components. These components can exist independently of specific applications, facilitating maintenance and upgrades.

[0067] Data resources refer to various data collections or databases, such as basic data, business data, and statistical data.

[0068] Cloud resources refer to the basic services or infrastructure provided during the process of government informationization, such as cloud servers, cloud storage, cloud databases, and cloud application services.

[0069] Exemplarily, the attribute information of application resources includes: application name, application code, source, status (under planning, under application, under construction, in operation, in suspension), review status (to be improved, to be submitted, to be reviewed, passed the preliminary review, to be reviewed, passed the review, removed from the shelves), application type, application field, core business, whether to build a unified system, scope of unified construction, application introduction, access address, construction area, construction plan, construction basis, responsible unit, collaborative unit, developer, security vendor, average daily visits or average daily active users, at least one of the above, but not limited to these, and the embodiments of the present application do not make specific limitations on this.

[0070] The attribute information of the component resource includes at least one of: component code, component name, publisher, unit code, technical field, functional field, usage type, component type, number of applications, component health, number of component calls, service unit, service contact or release time, but is not limited to these. The embodiments of this application do not make specific limitations on this.

[0071] The attribute information of data resources includes: data resource code, data directory name, collection table name, information resource summary, data source, field, data health, government data provider, government data summary, provision channel, data type, data source unit, number of visits, number of applications, source application code, source application name, administrative area code, source (manual addition, template import, Excel import, data table generation, database import, interface push, exploration system) or at least one of the data sensitivity levels, but is not limited to this. The embodiments of the present application do not make specific limitations on this.

[0072] The attribute information of cloud resources includes at least one of: cloud instance code, cloud product type, region ID, cloud area name, cloud environment instance name, instance description, creator or creation time, but is not limited to these. The embodiments of this application do not make specific limitations on this.

[0073] In some embodiments, after the computer device acquires multiple government resources, it constructs a resource map based on the multiple government resources and simultaneously enters attribute information of the multiple government resources so that when the computer device subsequently views the government resources in the resource map, the attribute information corresponding to the government resources can be viewed.

[0074] Optionally, the method of entering attribute information of multiple government resources includes: a standard field input method, or a resource exploration method, but is not limited to this, and the embodiments of the present application do not make specific limitations on this.

[0075] The standard field input method refers to inputting corresponding attribute information according to the preset field requirements. The resource exploration method refers to automatically collecting and filling attribute information from multiple government resources.

[0076] For example, for the attribute information of application resources, the corresponding attribute information can be entered according to the preset field requirements of the application resources, or the relevant attribute information can be automatically collected and filled in through the resource exploration party.

[0077] For example, Figure 3 The diagram shows how to enter attribute information for an application resource. The diagram shows the catalog corresponding to the application resource, through which a computer device can enter the attribute information for the application resource. For example, based on the catalog corresponding to the application resource, the corresponding attribute information can be entered according to the preset field requirements of the catalog corresponding to the application resource, such as the region to which the application resource belongs, the application field, the publishing terminal, the application type, the construction level, and the application status. Alternatively, attribute information can be automatically collected and filled in the attribute information of the application resource according to the catalog corresponding to the application resource.

[0078] For the attribute information of component resources, you can enter the corresponding attribute information according to the preset field requirements of the component resources, or you can automatically collect and fill in the relevant attribute information through the resource explorer.

[0079] For example, Figure 4 The diagram shows how to enter component resource attribute information. The diagram shows the catalog corresponding to the component resource. A computer device can use the catalog corresponding to the component resource to enter the component resource attribute information. For example, based on the catalog corresponding to the component resource, the corresponding attribute information can be entered according to the preset field requirements of the catalog corresponding to the component resource. For example, the component name, publishing unit, version number, number of applications, number of calls, status, etc. can be entered. Alternatively, attribute information can be automatically collected and filled in the component resource attribute information according to the catalog corresponding to the component resource.

[0080] For the attribute information of data resources, you can enter the corresponding attribute information according to the preset field requirements of the data resources, or you can automatically collect and fill in the relevant attribute information through resource exploration.

[0081] For example, Figure 5 The diagram shows how to enter attribute information for a data resource. The diagram shows the catalog corresponding to the data resource, through which a computer device can enter the attribute information for the data resource. For example, based on the catalog corresponding to the data resource, the corresponding attribute information can be entered according to the preset field requirements of the catalog corresponding to the data resource, such as the sharing method, collection status, data return flow, sharing attributes, etc. Alternatively, attribute information can be automatically collected and filled in the attribute information of the data resource according to the catalog corresponding to the data resource.

[0082] For the attribute information of cloud resources, you can enter the corresponding attribute information according to the preset field requirements of the cloud resources, or you can automatically collect and fill in the relevant attribute information through the resource explorer.

[0083] For example, Figure 6 The diagram shows how to enter cloud resource attribute information. The diagram shows the cloud resource's corresponding catalog. A computer device can use the cloud resource's corresponding catalog to enter the cloud resource's attribute information. For example, based on the cloud resource's corresponding catalog, the computer can enter the corresponding attribute information according to the preset field requirements of the cloud resource's corresponding catalog. For example, the cloud resource's name, resource code, application, department, operating status, type, and so on can be entered. Alternatively, attribute information can be automatically collected and populated in the cloud resource's attribute information according to the cloud resource's corresponding catalog.

[0084] In some embodiments, after acquiring the attribute information of the plurality of government resources, the attribute information of the plurality of government resources is checked to ensure the accuracy and compliance of the attribute information of the plurality of government resources.

[0085] Optionally, the verification content includes at least one of: whether the format of the attribute information is correct, whether the attribute information is complete, and whether the format of the attribute information is the latest, but is not limited thereto. The embodiments of the present application do not make specific limitations on this.

[0086] Step 204: The computer device constructs a resource map based on multiple government resources, using the government resources as nodes and the relationships between the government resources as edges.

[0087] Exemplarily, multiple government resources are established as nodes. Based on application resources, component resources are called, and a component-pointing relationship is established between the application resources and the component resources. Based on application resources, the data resources are called, and a data-pointing relationship is established between the application resources and the data resources. Based on application resources, cloud resources are called, and an application-cloud-resource-pointing relationship is established between the application resources and the cloud resources. Based on the association relationship between a first application resource and a second application resource, an application-association relationship is established between the first application resource and the second application. Based on component resources, cloud resources are called, and a component-cloud-resource-pointing relationship is established between the component resource and the cloud resource. A resource graph is obtained by using at least one of the component-pointing relationship, the data-pointing relationship, the cloud-resource-pointing relationship, the application-association relationship, or the component-cloud-resource-pointing relationship as an edge.

[0088] Optionally, the association relationship between government resources includes at least one of the following, but is not limited thereto, and is not specifically limited in this embodiment of the present application:

[0089] (1) Component-pointing relationships between application resources and component resources. Component-pointing relationships between application resources and component resources are used to describe how application resources call component resources, that is, to describe how applications rely on various software components to perform specific functions. For example, an e-government service application may need to use an authentication component to verify user identity. An online tax filing system (application resource) may rely on a security authentication component (component resource) to ensure that only authorized users can access and submit tax information.

[0090] (2) Data-pointing relationships between application resources and data resources: This relationship is used to describe how application resources call data resources, that is, how applications use or access data resources to perform specific functions. For example, a public service query system (application resource) needs to access a database (data resource) containing all public service information to respond to user query requests.

[0091] (3) The application-cloud resource pointing relationship between application resources and cloud resources. The data pointing relationship between application resources and cloud resources is used to describe the application resources calling cloud resources, that is, to describe the application using cloud infrastructure and services (cloud resources) to run and expand its functions. For example, an online voting system (application resource) may run on a cloud server (cloud resource) to dynamically adjust resources to meet the high traffic during the voting peak.

[0092] (4) Application association relationships between application resources: Application association relationships between application resources are used to describe the association relationship between any two applications in the application resources, that is, to describe the interaction between different applications that may need to collaborate or share information with each other. For example, an urban planning application (application resource) may need to obtain real-time traffic data from a traffic management application (application resource) to optimize the city layout.

[0093] (5) Component-cloud resource pointing relationships between component resources and cloud resources. Component-cloud resource pointing relationships between component resources and cloud resources are used to describe how component resources call cloud resources, that is, to describe how software components are deployed and used in a cloud environment and how they depend on cloud resources. For example, a load balancing component (component resource) may be deployed on a cloud platform (cloud resource) to ensure even traffic distribution among multiple application servers and improve system stability.

[0094] For example, after determining the association relationships among multiple government resources, the government resources are used as nodes to connect the association relationships among the government resources to obtain a resource map.

[0095] Optionally, the component pointing relationship, data pointing relationship, cloud resource pointing relationship, application association relationship or component cloud resource pointing relationship is determined based on the entered association relationship information, or based on the dependency relationship between different resources.

[0096] Optionally, the dependency relationship includes at least one of the following: a data flow relationship, a call relationship, a storage relationship, or a location deployment relationship, but is not limited thereto and is not specifically limited in the embodiments of the present application.

[0097] Step 206: The computer device establishes one or more operation management relationships based on the resource map; and manages multiple government resources based on the operation management relationships.

[0098] The operation management relationship includes one or more of an object management relationship, a supplier management relationship, or a risk management relationship, but is not limited thereto. The embodiments of the present application do not make specific limitations on this.

[0099] For example, after constructing a resource graph, when a new relationship needs to be established in the resource graph, the computer device can create a new edge between the corresponding nodes according to the addition instruction. For example, suppose a new database (data resource) is added and needs to be associated with an existing online tax filing application (application resource). The user issues an instruction through the interface to add an association between the two resources to the resource graph. The computer device will respond to this instruction and create a new edge between the online tax filing application node and the new database node to represent the association between them.

[0100] After constructing the resource graph, when a certain relationship in the resource graph is no longer applicable or needs to be removed, the computer device can delete the corresponding edge according to the deletion instruction. For example, suppose a component resource (such as an authentication service) is no longer used by an application resource (such as an online government service application). The user issues an instruction through the interface to delete the relationship between the two resources in the resource graph. The computer device will respond to this instruction and delete the edge between the online government service application node and the authentication service node, indicating that the association between them has been released.

[0101] In some embodiments, the operation management relationship includes an object management relationship. In response to a configuration instruction for the object management relationship in the resource map, the computer device configures attribute information for the object management relationship corresponding to the configuration instruction.

[0102] Optionally, the attribute information of the object management relationship includes dependency category and / or dependency strength, but is not limited thereto, and the embodiments of the present application do not make specific limitations on this.

[0103] Optionally, the dependency category includes at least one of interface dependency, data dependency, or page dependency, but is not limited thereto and is not specifically limited in the embodiments of the present application.

[0104] Optionally, dependency strength is used to indicate the degree of mutual influence between government resources having an object management relationship.

[0105] An interface dependency is when one resource interacts with another resource through an API. For example, an online tax filing application (application resource) exchanges data with a tax database (data resource) through a REST API.

[0106] Data dependency occurs when one resource relies on data provided by another resource. For example, a report generation tool (application resource) relies on data from a statistical database (data resource).

[0107] Page dependency refers to the situation where one resource relies on the webpage content or services provided by another resource. For example, a portal website (application resource) relies on a backend content management system (component resource) to provide news pages.

[0108] For example, Figure 7 The schematic diagram of the configuration object management relationship shown is a diagram in which the corresponding dependency category and dependency strength can be entered in the dependency type and dependency strength corresponding to the corresponding application resource to complete the configuration of the association relationship.

[0109] When a user or computer device issues an instruction to configure a certain relationship in the resource graph, the computer device will perform the corresponding operation to update the detailed information of this relationship. For example, the resource graph currently shows that there is an edge between "application resource A" and "component resource B", indicating that there is a certain relationship between them. The user issues an instruction to configure the attribute information of this relationship, specifying the dependency category as interface dependency and setting the dependency strength to high. According to the instruction, the computer device updates the resource graph and adds attribute information for the relationship between "application resource A" and "component resource B", including the dependency category (interface dependency) and dependency strength (high). After that, the resource graph is updated. The edge between "application resource A" and "component resource B" in the latest resource graph now contains attribute information, indicating that this is a high-strength interface dependency relationship.

[0110] In some embodiments, the operation management relationship includes a supplier management relationship. The computer device obtains supplier resources. Based on the supplier resources, a node corresponding to the supplier resources is created in the resource graph, and an edge corresponding to the association relationship between the supplier resources and the government resources is created in the resource graph.

[0111] Among them, the attribute information of the supplier resource includes: at least one of the supplier's name, service type provided, contract information, service quality level or contact information, but is not limited to these, and the embodiments of the present application do not make specific limitations on this.

[0112] For example, the computer device uses the collected supplier information to create a new node in the resource map, which represents the supplier resource. At the same time, an association relationship is established between the supplier resource node and the existing government resource node in the resource map.

[0113] For example, suppose a government information system needs to use a cloud storage service provided by an external supplier. The information provided by the supplier includes the supplier name (for example, "Big A"), service type (cloud storage), service level agreement (level one), etc. Create a node corresponding to the supplier resource in the resource graph: the computer device creates a new node in the resource graph based on the information obtained, and names it "Big A (cloud storage supplier)". Create edges in the resource graph corresponding to the association relationship between the supplier resource and other government resources. Suppose that the "Electronic Document Management System" in the government information system needs to use the cloud storage service provided by Big A to store documents. The computer device will create an edge between the "Big A (cloud storage supplier)" node and the "Electronic Document Management System" node to represent the service dependency relationship between them.

[0114] For example, Figure 8 The diagram for creating a new node shows how to create a new node corresponding to a supplier resource in the resource graph. The first step is to obtain the supplier resource's attribute information. For example, the obtained supplier resource attribute information includes: supplier name, code, business scope, business address, legal person, and associated applications. The computer device enters the supplier resource's attribute information and generates a node corresponding to the supplier resource based on the supplier resource.

[0115] In some embodiments, the operation management relationship includes a risk management relationship. The computer device can also perform operation monitoring and management on the government resources in the resource map. Operation monitoring and management refers to monitoring the health of the operation of the government resources.

[0116] Optionally, a corresponding color is set for each government resource, and the color of the node corresponding to each government resource is related to the health of the government resource. Different colors can be used to display the health of the operation of the government resource.

[0117] For example, in the topology view of application resources, the color of the node corresponding to each application resource is related to the health of the application resource. This means that each application resource node in the topology view will display different colors according to its health (such as performance, stability, availability and other indicators). For example, the higher the health, the closer the color may be to green; the lower the health, the closer the color may be to red. For example, an application resource node that is running normally and has a fast response time may be displayed in green, while an application resource node that often crashes or responds slowly may be displayed in red.

[0118] In the topology view of cloud resources, the color of the node corresponding to each cloud resource is related to the health of the cloud resource. The health of a cloud resource is negatively correlated with its utilization. This means that the color of a cloud resource node reflects its health, which in turn is related to the utilization of the resource. The higher the utilization, the lower the health may be, so the color may be closer to red; the lower the utilization, the higher the health may be, and the color may be closer to green. For example, if the utilization of a cloud server (cloud resource) is very high and approaches or reaches the capacity limit, its node color may be red, indicating low health and may require resource expansion or optimization. Conversely, if the utilization is low, the node color may be green, indicating high health.

[0119] In the component resource topology view, the color of each component resource's corresponding node is related to the component resource's health. The component resource's health may be determined based on, but is not limited to, factors such as the component's operating status, error rate, and performance. For example, a certified component node that is operating stably and has no reported errors may appear green. On the other hand, a component node that frequently experiences failures or performance issues may appear yellow or red.

[0120] For example, Figure 9 The diagram of the early warning monitoring mechanism shown shows that by setting rules, the content of the set rules includes: rules, rule descriptions, alarm categories, upper thresholds, lower thresholds, applicable objects, etc. The set rules can monitor and manage the operation of government resources in the resource map. When the government resources in the resource map meet the set rules, an alarm is triggered and fault information is displayed. The fault information includes: fault name, fault level, duration, start time, person in charge, review, etc. By establishing an early warning monitoring mechanism, the health of the operation of government resources is monitored and fed back to the resource map. As the resource map continues to evolve, the relationship between resources will also change. The resource map can capture these changes in real time and automatically update the related information in the map, so as to make feedback adjustments, realize continuous operation management, and improve the efficiency and quality of resource management.

[0121] Exemplarily, managing multiple government resources includes any of the following, but is not limited thereto, and is not specifically limited in this embodiment of the present application:

[0122] 1. Display resource maps. After obtaining the resource map, the entire resource map can be displayed from a holistic perspective. That is, multiple government resources can be displayed in a graphical manner so that all government resources and their interrelationships can be intuitively seen.

[0123] For example, Figure 10 The schematic diagram of the resource map shown shows nodes corresponding to multiple government resources, as well as statistical data for the multiple government resources, including, but not limited to, the total number of applications, the total number of data, the total number of components, and the total number of cloud resources. Furthermore, the resource map can also be used to query and retrieve any of the multiple government resources.

[0124] 2. Based on the resource map, the topological view of the application resources is displayed in the application digital twin view. The topological view of the application resources includes the nodes corresponding to the application resources and other nodes with edges to the nodes corresponding to the application resources. In other words, the resource map is displayed from the perspective of the application resources, and the parts related to the application resources are extracted from the resource map to display the application resources and other directly associated resources (such as component resources, data resources, cloud resources, etc.). For example, the topological view of the online tax declaration system is displayed, which includes the tax declaration application node, the authentication component node directly connected to it, the database node, and the cloud server node hosting the application, etc.

[0125] An application digital twin is a digital model that digitally describes the nodes and edges corresponding to application resources. After obtaining a resource map, the computer device digitally represents the nodes and edges corresponding to the application resources, constructing the application digital twin. The computer device then renders the digitally constructed nodes and edges in the application digital twin to obtain a topological view of the application resources.

[0126] For example, Figure 11 The diagram below shows a topological view of application resources. The resource map, displayed from the application resource perspective, includes not only the nodes corresponding to the application resources but also other nodes with which they have edges. This topological view from different resource perspectives clearly shows the usage and load status of each resource, allowing for timely resource allocation adjustments to avoid overloading some resources while leaving others idle, and preventing duplicate construction.

[0127] 3. Based on the resource graph, the cloud digital twin displays a topological view of cloud resources. This topological view includes the nodes corresponding to the cloud resources and other nodes with which they have edges. Specifically, the resource graph is presented from the perspective of cloud resources, showing cloud resources and their directly associated resources, such as application resources, component resources, and data resources. For example, a topological view of a cloud server would include the cloud server nodes, the different application nodes deployed on the cloud server, and the component and data resource nodes on which these applications depend.

[0128] A cloud digital twin is a digital model that digitally describes the nodes and edges corresponding to cloud resources. After obtaining a resource map, a computer device digitally represents the nodes and edges corresponding to cloud resources, constructing a cloud digital twin. The computer device then renders the digitally constructed nodes and edges in the cloud digital twin to obtain a topological view of the cloud resources.

[0129] For example, Figure 12 The diagram below shows a topological view of cloud resources. This resource map, displayed from a cloud resource perspective, includes not only the nodes corresponding to the cloud resources but also other nodes with which they have edges. This topological view from different resource perspectives allows you to clearly see the usage and load status of each resource, allowing you to adjust resource allocation in a timely manner, avoiding overloading some resources while leaving others idle, and preventing duplicate construction.

[0130] 4. Based on the resource graph, a topological view of component resources is displayed in the component digital twin view. The topological view of component resources includes the node corresponding to the component resource and other nodes with which the node corresponding to the component resource has edges. In other words, the resource graph is displayed from the perspective of the component resource, showing specific component resources and other resources directly associated with them, such as application resources, data resources, or cloud resources. For example, a topological view of a security authentication component is displayed, including the authentication component node, the application nodes that use the component, and the data resource nodes that the component may access.

[0131] A component digital twin is a digital model that numerically describes the nodes and edges corresponding to component resources. After obtaining a resource map, a computer device digitally represents the nodes and edges corresponding to the component resources, constructing the component digital twin. The computer device then renders the digitally constructed nodes and edges in the component digital twin to obtain a topological view of the component resources.

[0132] For example, Figure 13The diagram below shows a topological view of component resources. The resource map displayed from the component resource perspective includes not only the nodes corresponding to the component resources but also other nodes with which they have edges. This topological view from different resource perspectives clearly shows the usage and load status of each resource, allowing for timely resource allocation adjustments to avoid overloading some resources while leaving others idle, and preventing duplicate construction.

[0133] 5. Based on the resource graph, the topological view of the data resource is displayed in the data digital twin view. The topological view of the data resource includes the node corresponding to the data resource and other nodes with which the node corresponding to the data resource has edges. In other words, the resource graph is displayed from the perspective of the data resource, showing the data resource and other resources directly associated with it, such as application resources, component resources, or cloud resources. For example, the topological view of a citizen information database is displayed, including the database node, the various application nodes that access the database, and the cloud resource nodes responsible for storing the database.

[0134] A data digital twin is a digital model that numerically describes the nodes and edges corresponding to a data resource. After obtaining a resource map, a computer device digitally represents the nodes and edges corresponding to the data resource, constructing a data digital twin. The computer device then renders the digitally constructed nodes and edges in the data digital twin to create a topological view of the data resource.

[0135] For example, Figure 14 The diagram below shows a topological view of data resources. This resource map, displayed from a data resource perspective, includes not only the nodes corresponding to the data resource but also other nodes with which the data resource node has edges. This topological view from different resource perspectives clearly shows the usage and load status of each resource, allowing for timely resource allocation adjustments to avoid overloading some resources while leaving others idle, and preventing duplicate construction.

[0136] It should be noted that resource maps displayed based on different resource perspectives can be switched between each other; resource maps displayed based on at least two resource perspectives can also be displayed on the same screen for easy comparison and viewing.

[0137] In some embodiments, the computer device may further split or classify the same application resources in the resource map that have an association relationship with the cloud resources.

[0138] For example, based on the resource map, multiple identical application resources deployed on the same cloud resource are identified; these identical application resources are then deployed on different cloud resources. This means that through the resource map, we can identify identical application resources deployed on the same cloud server. For example, suppose the resource map shows three identical tax filing application resources, all deployed on cloud server X. To improve system reliability and load capacity, the identical application resources are deployed on different cloud servers. For example, the three tax filing application resources are deployed on cloud server X, cloud server Y, and cloud server Z, respectively.

[0139] Exemplarily, based on the resource map, multiple identical application resources deployed on different cloud resources are determined; and multiple identical application resources are deployed on one cloud resource. The resource map is used to identify identical application resources that have been dispersedly deployed on different cloud servers. For example, the resource map shows five tax declaration applications, which are deployed on cloud servers A, B, C, D, and E respectively. In order to simplify management and maintenance, or to utilize the characteristics of specific cloud resources (such as higher performance or specific services), the originally dispersed application resources are concentrated on the same cloud server or cloud service. For example, the tax declaration application resources originally deployed on five different cloud servers are centrally migrated to cloud server F because cloud server F provides higher performance and better support services.

[0140] In some embodiments, the computer device may further split or classify the same component resources in the resource map that have an association relationship with the cloud resources.

[0141] Exemplarily, based on the resource map, multiple identical component resources deployed on the same cloud resource are determined; and the multiple identical component resources are deployed on different cloud resources respectively. Through the resource map, the identical component resources deployed on the same cloud server are identified. For example, the resource map shows that there is a load balancer component (component resource), which is deployed three times on cloud server X. These load balancer components all handle the same work. In order to improve the reliability and fault tolerance of the system, the resources of the same component are dispersed and deployed on different cloud servers. For example, three load balancer components are deployed on cloud server X, cloud server Y and cloud server Z respectively. In this way, even if one cloud server fails, the load balancer components on other servers can still process requests.

[0142] Exemplarily, based on the resource map, multiple identical component resources deployed on different cloud resources are determined; and multiple identical component resources are deployed on one cloud resource respectively. The resource map is used to identify identical component resources that have been dispersedly deployed on different cloud servers. For example, the resource map shows that there is a database cache component, and five database cache components are deployed on cloud servers A, B, C, D, and E respectively. In order to simplify management and maintenance, or to take advantage of the characteristics of specific cloud resources (such as higher performance or specific services), the originally dispersed component resources are concentrated on the same cloud server. For example, the database cache component instances originally deployed on five different cloud servers are centrally migrated to cloud server F, because cloud server F provides higher memory and faster processing speed, which is suitable for running cache services.

[0143] In summary, the solution provided by this application unifies the management of multiple government resources and displays them in an intuitive, graphical resource map. The intuitive display of the resource map enables managers to quickly understand and grasp the distribution and correlation of multiple government resources, thereby improving the management efficiency of government resources. In addition, the construction of a resource map containing multiple government resources also promotes information sharing among multiple government resources, breaks down information silos, and improves the transparency and utilization of government information.

[0144] The above mainly introduces the solution provided by this application. Correspondingly, this application also provides a government resource management device, which is used to implement the above method embodiment.

[0145] In some embodiments, in order to realize the above functions, the government resource management device includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware 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 to be beyond the scope of this application.

[0146] The embodiment of the present application can divide the functional modules of the government resource management device according to the above-mentioned method embodiment. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above-mentioned integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical functional division. There may be other division methods in actual implementation.

[0147] Figure 15 This is a schematic diagram of the structure of a government resource management device provided in an embodiment of the present application. Figure 15 The government resource management device includes an acquisition module 1501, a construction module 1502, and a management module 1503.

[0148] The acquisition module 1501 is used to acquire multiple government resources, which include one or more of application resources, component resources, data resources or cloud resources.

[0149] The construction module 1502 is used to construct a resource map based on multiple government resources, with the government resources as nodes and the association relationships between the government resources as edges.

[0150] The management module 1503 is used to establish one or more operation management relationships based on the resource map; and manage multiple government resources based on the operation management relationships.

[0151] A possible implementation method is that the construction module 1502 is also used to construct a resource map based on multiple government resources, with government resources as nodes and the association relationships between government resources as edges. It can be specifically implemented as one or more of the following: establishing nodes for multiple government resources; calling component resources based on application resources, and establishing a component pointing relationship between the application resources and the component resources; calling the data resources based on application resources, and establishing a data pointing relationship between the application resources and the data resources; calling cloud resources based on application resources, and establishing an application-cloud resource pointing relationship between the application resources and the cloud resources; establishing an application association relationship between the first application resource and the second application resource based on the association relationship between the first application resource and the second application resource; calling cloud resources based on component resources, and establishing a component-cloud resource pointing relationship between the component resource and the cloud resource; using at least one of the component pointing relationship, data pointing relationship, cloud resource pointing relationship, application association relationship or component-cloud resource pointing relationship as an edge to obtain a resource map.

[0152] In another possible implementation, the component pointing relationship, data pointing relationship, cloud resource pointing relationship, application association relationship or component cloud resource pointing relationship is determined based on the entered association relationship information, or based on the dependency relationship between different resources.

[0153] In another possible implementation, the dependency relationship includes at least one of the following: a data flow relationship, a call relationship, a storage relationship, or a location deployment relationship.

[0154] In another possible implementation, the attribute information of the application resources includes: application name, application code, source, status, review status, application type, application field, core business, integrated construction status, integrated construction scope, application introduction, access address, construction area, construction plan, construction basis, responsible unit, collaborative unit, developer, security vendor, average daily visits or average daily active users, at least one of them.

[0155] In another possible implementation, the attribute information of the component resource includes at least one of: component code, component name, publisher, unit code, technical field, functional field, usage type, component type, number of applications, component health, number of component calls, service unit, service contact or release time.

[0156] In another possible implementation, the attribute information of data resources includes: data resource code, data directory name, collection table name, information resource summary, data source, field, data health, government data provider, government data summary, provision channel, data type, data source unit, number of visits, number of applications, source application code, source application name, administrative area code, source or at least one of data sensitivity level.

[0157] In another possible implementation, the operation management relationship includes: an object management relationship; the construction module 1502 is also used to respond to the configuration instruction of the object management relationship in the resource map, and configure attribute information for the object management relationship corresponding to the configuration instruction, and the attribute information of the object management relationship includes dependency category and / or dependency strength.

[0158] In another possible implementation, the operation management relationship includes: supplier management relationship; construction module 1502 is also used to create nodes corresponding to supplier resources in the resource map based on supplier resources, and to create edges corresponding to the association relationship between supplier resources and government resources in the resource map.

[0159] In another possible implementation, the operation management relationship includes: a risk management relationship; the construction module 1502 is further used to set a corresponding color for each government resource, and the color of the node corresponding to each government resource is related to the health of the government resource.

[0160] In another possible implementation, the health of cloud resources is negatively correlated with the utilization rate of cloud resources.

[0161] In another possible implementation, the management module 1503 is further configured to implement any of the following:

[0162] Based on the operational management relationship in the resource map, the topological view of the application resources is displayed in the view of the application digital twin. The topological view of the application resources includes the nodes corresponding to the application resources and other nodes that have edges with the nodes corresponding to the application resources. The application digital twin refers to a digital model that describes the nodes and edges corresponding to the application resources through numbers.

[0163] Based on the operational management relationship in the resource map, the topological view of cloud resources is displayed in the cloud digital twin view. The topological view of cloud resources includes the nodes corresponding to the cloud resources and other nodes that have edges with the nodes corresponding to the cloud resources. The cloud digital twin refers to a digital model that describes the nodes and edges corresponding to the cloud resources through numbers.

[0164] Based on the operational management relationship in the resource map, the topological view of the component resources is displayed in the view of the component digital twin. The topological view of the component resources includes the nodes corresponding to the component resources and other nodes with edges corresponding to the nodes of the component resources. The component digital twin refers to a digital model that describes the nodes and edges corresponding to the component resources through numbers.

[0165] Based on the operational management relationship in the resource map, the topological view of the data resources is displayed in the view of the data digital twin. The topological view of the data resources includes the nodes corresponding to the data resources and other nodes that have edges with the nodes corresponding to the data resources. The data digital twin refers to a digital model that describes the nodes and edges corresponding to the data resources through numbers.

[0166] like Figure 16 As shown, the computer device provided in the embodiment of the present application may include a processor 1601, a bus 1602, a communication interface 1603, and a memory 1604. The processor 1601, the memory 1604, and the communication interface 1603 communicate with each other via the bus 1602. It should be understood that the present application does not limit the number of processors and memories in the computer device.

[0167] The bus 1602 may be a PCI bus or an extended industry standard architecture (EISA) bus, or a USB bus. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 16 The bus 1602 may include a path for transmitting information between various components of a computer device (eg, memory 1604, processor 1601, and communication interface 1603).

[0168] The processor 1601 may include any one or more processors such as a CPU, a graphics processing unit (GPU), a microprocessor (MP), or a digital signal processor (DSP).

[0169] The memory 1604 may include volatile memory, such as random access memory (RAM). The processor 1601 may also include non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD), or solid state drive (SSD).

[0170] The communication interface 1603 uses a transceiver module such as, but not limited to, a network interface card or a transceiver to implement communication between the computer device and other devices or a communication network.

[0171] The memory 1604 stores executable program code, and the processor 1601 executes the executable program code to respectively implement the functions of the government resource management device or the CPU core in the above-mentioned method embodiment. That is, the memory 1604 stores the program code for executing the above-mentioned government resource management method.

[0172] On the other hand, a computer-readable storage medium is provided, in which at least one computer program is stored. The at least one computer program is loaded and executed by a processor to implement the government resource management method provided in the above-mentioned method embodiments.

[0173] On the other hand, a computer program product is provided, which includes a computer program or instructions. When the computer program or instructions are executed by a processor, the government resource management method described above is implemented.

[0174] On the other hand, a chip system is provided, comprising at least one processor and at least one interface circuit, wherein the at least one interface circuit is used to perform transceiver functions and send instructions to the at least one processor. When the at least one processor executes the instructions, the at least one processor executes to implement the government resource management method as described above.

[0175] The computer device, computer-readable storage medium, or computer program product provided in the embodiments of the present application are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods provided above, and will not be repeated here.

[0176] Through the description of the above embodiments, those skilled in the art can clearly understand that for the convenience and brevity of description, only the division of the above functional modules is used as an example. In actual application, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device (such as a computer device) is divided into different functional modules to complete all or part of the functions described above. The specific working process of the system, device (such as a computer device) and unit described above can refer to the corresponding process in the aforementioned method embodiment and will not be repeated here.

[0177] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices (such as computer devices) and methods can be implemented in other ways. For example, the device (such as computer device) embodiments described above are merely schematic. For example, the division of the modules or units is only a logical function division. There may be other division methods in actual implementation, 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 an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0178] 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.

[0179] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0180] If the above-mentioned 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 technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) or a processor to execute all or part of the steps of the method of each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as flash memory, mobile hard disk, read-only memory, random access memory, magnetic disk or optical disk.

[0181] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A government resource management method, characterized in that: The method comprises: Acquire a plurality of government resources, wherein the plurality of government resources include one or more of application resources, component resources, data resources, or cloud resources; Based on the multiple government resources, a resource map is constructed with the government resources as nodes and the associations between the government resources as edges; Establishing one or more operation management relationships based on the resource map; The plurality of government resources are managed based on the operation and management relationship.

2. The method according to claim 1, characterized in that The constructing of a resource map based on the plurality of government resources, with the government resources as nodes and the relationships between the government resources as edges, includes one or more of the following: Establish nodes for multiple government resources; Calling the component resource based on the application resource, and establishing a component pointing relationship between the application resource and the component resource; Calling the data resource based on the application resource, and establishing a data pointing relationship between the application resource and the data resource; Calling the cloud resource based on the application resource, and establishing an application-cloud resource pointing relationship between the application resource and the cloud resource; Based on the association relationship between the first application resource and the second application resource, establishing an application association relationship between the first application resource and the second application; Calling the cloud resource based on the component resource, and establishing a component-cloud resource pointing relationship between the component resource and the cloud resource; The resource graph is obtained by using at least one of the component pointing relationship, the data pointing relationship, the cloud resource pointing relationship, the application association relationship or the component cloud resource pointing relationship as an edge.

3. The method according to claim 2, characterized in that The component pointing relationship, the data pointing relationship, the cloud resource pointing relationship, the application association relationship or the component cloud resource pointing relationship is determined based on the entered association relationship information, or based on the dependency relationship between different resources.

4. The method according to claim 3, characterized in that The dependency relationship includes at least one of the following: a data flow relationship, a call relationship, a storage relationship, or a location deployment relationship.

5. The method according to any one of claims 1 to 4, characterized in that The operation management relationship includes: object management relationship; The establishing of one or more operation management relationships based on the resource map includes: In response to a configuration instruction for the object management relationship in the resource map, attribute information is configured for the object management relationship corresponding to the configuration instruction, where the attribute information of the object management relationship includes dependency category and / or dependency strength.

6. The method according to any one of claims 1 to 4, characterized in that The operational management relationship includes: supplier management relationship; The establishing of one or more operation management relationships based on the resource map includes: Based on the supplier resources, a node corresponding to the supplier resources is created in the resource map, and an edge corresponding to the association relationship between the supplier resources and the government resources is created in the resource map.

7. The method according to any one of claims 1 to 4, characterized in that The operational management relationship includes: risk management relationship; The establishing of one or more operation management relationships based on the resource map includes: A corresponding color is set for each government resource, and the color of the node corresponding to each government resource is related to the health of the government resource.

8. The method according to claim 7, characterized in that The health of the cloud resources is negatively correlated with the utilization rate of the cloud resources.

9. The method according to any one of claims 1 to 6, characterized in that The managing of the plurality of government resources based on the operation and management relationship includes any one of the following: Displaying a topological view of an application resource in a view of an application digital twin, wherein the topological view of the application resource includes a node corresponding to the application resource and other nodes having edges with the node corresponding to the application resource. The application digital twin is a digital model that digitally describes the nodes and edges corresponding to the application resource. Displaying a topological view of cloud resources in a cloud digital twin view, wherein the topological view of cloud resources includes nodes corresponding to the cloud resources and other nodes having edges with the nodes corresponding to the cloud resources. The cloud digital twin is a digital model that digitally describes the nodes and edges corresponding to the cloud resources. Displaying a topological view of a component resource in a component digital twin view, wherein the topological view of the component resource includes a node corresponding to the component resource and other nodes having edges with the node corresponding to the component resource. The component digital twin is a digital model that digitally describes the nodes and edges corresponding to the component resource. The topological view of the data resource is displayed in the view of the data digital twin. The topological view of the data resource includes the nodes corresponding to the data resource and other nodes with edges existing with the nodes corresponding to the data resource. The data digital twin refers to a digital model that describes the nodes and edges corresponding to the data resource by numbers.

10. A computer device, characterized in that: The computer device includes a processor and a memory; the processor and the memory are coupled; The memory is used to store computer program instructions; The processor is configured to call the computer program instructions in the memory to execute the method according to any one of claims 1 to 9.

Images