Method for sharing computing-power resource, method for deploying service, and electronic device

Abstract

Provided in the present application are a method for sharing a computing-power resource, a method for deploying a service, and an electronic device. The method for sharing a computing-power resource comprises: a first network node receiving a computing-power resource acquisition request which is sent by a second network node (S110), wherein the computing-power resource acquisition request carries computing-power demand information; then, the first network node determining, from a computing-power pool which includes a plurality of network nodes, a shared network node which meets the computing-power demand information (S120); and sending identification information of the shared network node to the second network node, such that the second network node deploys a target service on the shared network node on the basis of the identification information (S130).

Description

Computing power resource sharing method, service deployment method and electronic device

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application is based on the Chinese patent application with application number 202311291721.8 and application date September 28, 2023, and claims the priority of the Chinese patent application. The entire content of the Chinese patent application is hereby introduced into this application as a reference. Technical Field

[0003] The present application relates to the field of communication technology, and in particular to a computing resource sharing method, a service deployment method, and an electronic device. Background Art

[0004] With the rapid development of cloud computing and big data, the computing power demand of network nodes such as base stations and servers is becoming increasingly higher, and many resource scheduling methods for network nodes have emerged.

[0005] However, related resource scheduling methods only allocate computing power within network nodes. For network nodes with increased load, capacity expansion often requires hardware resource planning and other methods. This has drawbacks such as slow response, high workload, and the need for manual intervention. Therefore, the problems of traditional resource scheduling methods make it difficult to meet the needs of today's rapidly growing business.

[0006] Summary of the Invention

[0007] Embodiments of the present application provide a computing resource sharing method, a service deployment method, and an electronic device.

[0008] In a first aspect, an embodiment of the present application provides a computing power resource sharing method, which is applied to a first network node, and the method includes: receiving a computing power resource acquisition request sent by a second network node, the computing power resource acquisition request carrying computing power demand information; determining a shared network node that meets the computing power demand information from a computing power pool comprising multiple network nodes; and sending identification information of the shared network node to the second network node, so that the second network node deploys a target service on the shared network node according to the identification information.

[0009] In the second aspect, an embodiment of the present application provides a service deployment method, which is applied to a second network node, and the method includes: sending a computing power resource acquisition request carrying computing power requirement information to the first network node, so that the first network node determines a shared network node that meets the computing power requirement information from a computing power pool containing multiple network nodes; receiving identification information of the shared network node sent by the first network node; and deploying a target service on the shared network node according to the identification information.

[0010] In a third aspect, an embodiment of the present application provides a computing power resource sharing system, the system comprising a first network node and multiple second network nodes, the first network node and multiple second network nodes forming a computing power pool, wherein the first network node is configured to receive a computing power resource acquisition request sent by the second network node, the computing power resource acquisition request carries computing power demand information, determines a shared network node that meets the computing power demand information from the computing power pool, and sends the identification information of the shared network node to the second network node, so that the second network node deploys a target service on the shared network node according to the identification information; the second network node is configured to send a computing power resource acquisition request carrying computing power demand information to the first network node, so that the first network node determines a shared network node that meets the computing power demand information from the computing power pool, receives the identification information of the shared network node sent by the first network node, and deploys the target service on the shared network node according to the identification information.

[0011] In a fourth aspect, an embodiment of the present application provides an electronic device comprising: one or more processors; a memory on which one or more programs are stored, and when the one or more programs are executed by the one or more processors, the one or more processors implement the computing power resource sharing method described in the first aspect above; or, implement the service deployment method described in the second aspect above.

[0012] In a fifth aspect, an embodiment of the present application provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, it implements the computing power resource sharing method described in the first aspect above; or, it implements the service deployment method described in the second aspect above. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] The accompanying drawings are used to provide an understanding of the technical solution of the present application and constitute a part of the specification. Together with the embodiments of the present application, they are used to explain the technical solution of the present application and do not constitute a limitation on the technical solution of the present application.

[0014] FIG1 is a schematic diagram of a network architecture provided in an embodiment of the present application;

[0015] FIG2 is a flow chart of a computing resource sharing method provided by one embodiment of the present application;

[0016] FIG3 is a flow chart of a computing resource sharing method provided by another embodiment of the present application;

[0017] FIG4 is a flow chart of a computing resource sharing method provided by another embodiment of the present application;

[0018] FIG5 is a flow chart of a service deployment method provided by an embodiment of the present application;

[0019] FIG6 is a flow chart of a service deployment method provided in another embodiment of the present application;

[0020] FIG7 is a schematic diagram of an implementation of a service deployment method provided in another embodiment of the present application;

[0021] FIG8 is a schematic structural diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0022] In order to enable technical personnel in this field to better understand the technical solution of this application, the computing power resource sharing method, service deployment method, computing power resource sharing system, electronic device, and computer-readable storage medium provided by this application are described in detail below in conjunction with the accompanying drawings.

[0023] Example embodiments will be described more fully hereinafter with reference to the accompanying drawings, but the described example embodiments may be embodied in different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this application will be thorough and complete and will fully convey the scope of this application to those skilled in the art.

[0024] As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed items.

[0025] The terms used herein are used only to describe specific embodiments and are not intended to limit this application. As used herein, the singular forms "a," "an," and "the" are intended to include the plural forms, unless the context clearly indicates otherwise. It will also be understood that when the terms "comprising" and / or "made of" are used in this specification, they specify the presence of features, wholes, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, wholes, steps, operations, elements, components, and / or groups thereof.

[0026] In the following description, reference is made to “some embodiments”, which describes a subset of all possible embodiments, but it will be understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0027] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by those of ordinary skill in the art. It will also be understood that terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant art and the present application, and will not be interpreted as having an idealized or overly formal meaning, unless clearly defined in the examples of the present application.

[0028] With the rapid development of cloud computing and big data, the computing power demand of network nodes such as base stations and servers is becoming increasingly higher, and many resource scheduling methods for network nodes have emerged.

[0029] However, related resource scheduling methods only allocate computing power within network nodes. For network nodes with increased load, capacity expansion often requires hardware resource planning and other methods. This has drawbacks such as slow response, high workload, and the need for manual intervention. Therefore, the problems of traditional resource scheduling methods make it difficult to meet the needs of today's rapidly growing business.

[0030] Based on this, the embodiments of the present application propose a computing power resource sharing method, a service deployment method and an electronic device, which can realize resource sharing between network nodes and improve the resource utilization of network nodes.

[0031] Before introducing the technical solution of the embodiment of the present application, the network architecture of the embodiment of the present application is first exemplified. The network architecture of the embodiment of the present application includes multiple network nodes, and each network node can communicate with each other to exchange data and perceive status. Please refer to Figure 1, which is a schematic diagram of a network architecture provided by the embodiment of the present application. As shown in Figure 1, the network architecture includes a first network node 101, a second network node 201, a second network node 202, a second network node 203, a second network node 204, etc. The above-mentioned multiple network nodes constitute a computing power pool, and each network node in the computing power pool can communicate with each other, wherein the first network node serves as the master station in the computing power pool, and the second network nodes other than the first network node in the computing power pool serve as slave stations. The slave stations report heartbeats, their own resources, applications and other data to the master station. The master station is responsible for monitoring the heartbeats of the slave stations and receiving and storing the data reported by the slave stations. The network nodes can be physical nodes that can provide computing power resources, such as base stations and general x86 servers.

[0032] The embodiment of the present application first proposes a computing power resource sharing method, which is applied to a first network node. Please refer to Figure 2. Figure 2 shows a computing power resource sharing method provided by an embodiment of the present application. As shown in Figure 2, the method includes but is not limited to steps S110 to S130.

[0033] Step S110: Receive a computing power resource acquisition request sent by the second network node, where the computing power resource acquisition request carries computing power demand information.

[0034] It can be understood that the first network node and the second network node are members of the computing power pool, the first network node is the master station in the computing power pool, and the second network node is the slave station in the computing power pool. When the second network node itself has insufficient resources, the second network node sends a computing power resource acquisition request carrying computing power demand information to the first network node, and the first network node selects and allocates shared network nodes based on the computing power demand information.

[0035] It should be understood that the computing power requirement information can be the requirement information of at least one of the resources such as CPU, GPU, memory, storage, etc.

[0036] Step S120: Determine a shared network node that meets the computing power requirement information from a computing power pool including multiple network nodes.

[0037] It should be noted that network nodes in different regions can be included in the computing power pool as resource nodes, and the included network nodes can be continuously managed and monitored through the main station of the computing power pool, continuously expanding the computing power pool and increasing shared computing power resources. Through subsequent cross-site deployment of services, the idle resources of network nodes can be utilized across regions, which not only reduces manual intervention and improves operation and maintenance efficiency, but also cuts costs and improves resource utilization and energy efficiency.

[0038] Step S130: Send the identification information of the shared network node to the second network node, so that the second network node deploys the target service on the shared network node according to the identification information.

[0039] It should be understood that after the first network node determines the shared network node from the computing power pool, the first network node sends the identification information of the shared network node, such as the IP address, MAC address, host number or port number of the shared network node, to the second network node. The second network node establishes a communication connection with the shared network node based on the identification information, so that the second network node can complete the deployment of the target service on the shared network node.

[0040] Through the computing power resource sharing method provided by the embodiment of the present application, the services on the network nodes can be deployed across stations to any network node in the computing power pool, realizing computing power resource sharing of multiple network nodes in the computing power pool. Network nodes in different regions can complement each other in terms of busy and idle resources in terms of software and hardware resources, solving a series of computing power shortage problems caused by tidal effects, regional business differences, high computing power requirements, etc., while also maximizing the use of idle resources of each network node. Compared with the traditional resource sharing method that is limited to the internal resource allocation of the base station, the embodiment of the present application breaks through the spatial limitations of computing power resource sharing, and can achieve nearly unlimited resource sharing capabilities by continuously accessing more network nodes and utilizing the multi-node computing power sharing capability.

[0041] In some embodiments, the computing power resource sharing method provided in the embodiments of the present application also includes step S210.

[0042] Step S210: Receive reporting information sent by the target network node in the computing power pool.

[0043] It can be understood that each target network node in the computing power pool can periodically send reporting information to the first network node serving as the master station of the computing power pool. For example, each target network node sends reporting information to the first network node every 30 seconds, and the first network node continuously receives reporting information sent by each target network node, thereby realizing monitoring of each network node in the computing power pool; each target network node in the computing power pool can also send reporting information to the first network node serving as the master station of the computing power pool based on conditional triggering or user triggering, or the above methods can exist at the same time (such as sending reporting information based on user triggering while periodically sending reporting information). This application does not limit this.

[0044] In some embodiments, the computing power resource sharing method provided in the embodiments of the present application also includes step S310.

[0045] Step S310: Mark the target network node as being in an abnormal state or a normal state according to the reported information.

[0046] Please refer to Figure 3, which is a computing power resource sharing method provided by an embodiment of the present application. As shown in Figure 3, after the master station and slave station in the computing power pool are configured, the first network node serving as the master station begins to monitor the status of the second network node serving as the slave station in the computing power pool, and the second network node sends reporting information to the first network node, and the first network node receives and stores the reporting information of each second network node, wherein the first network node marks the network node as an abnormal state or a normal state according to the reporting information. Specifically, when the first network node receives the reporting information sent by the target network node within a first preset time interval, the first network node considers that the target network node is operating normally and marks the target network node as a normal state. When the first network node does not receive the reporting information sent by the target network node within the first preset time interval, the first network node considers that the target network node is abnormal and marks the target network node as an abnormal state. In some embodiments, when the first network node does not receive the reporting information sent by the target network node within a second preset time interval, the first network node considers that the target network node is out of connection and marks the target network node as a lost state in an abnormal state, wherein the second preset time interval is greater than the first preset time interval, that is, compared to marking the target network node as an abnormal state, the first network node will mark the target network node as a lost state only if it does not receive the reporting information within a longer time interval.

[0047] For example, as shown in FIG3 , the first preset time interval may be referred to as the abnormal time, and the second preset time interval may be referred to as the loss of connection time. For the second network node A in the computing power pool, if the first network node does not receive the reporting information sent by it within the abnormal time, the second network node A will be marked as an abnormal state by the first network node serving as the master station. If, after the loss of connection time, the first network node still does not receive the reporting information sent by the second network node A, the second network node A will be marked as a loss of connection state by the first network node serving as the master station.

[0048] It can be understood that when the target network node is marked as abnormal (or disconnected) by the first network node, the target network node will not be used as a shared network node. That is, the first network node only determines the shared network node that meets the computing power requirement information from the network nodes in normal state.

[0049] The first network node monitors the status of each network node in the computing power pool, realizing automatic management of the computing power pool, reducing the cost of manual intervention and improving operation and maintenance efficiency.

[0050] It should be understood that the target network node may fail to send reporting information to the first network node due to its own equipment failure or busy business, or the first network node may fail to receive the reporting information sent by the target network node due to a communication link failure between the target network node and the first network node, thereby causing the target network node to be marked as abnormal (or disconnected) by the first network node. When the problem that caused the first network node to fail to receive the reporting information sent by the second network node is eliminated, as shown in Figure 3, the first network node receives the reporting information sent by the target network node marked as abnormal (or disconnected), and re-marks the target network node as normal, indicating that the target network node can continue to participate in computing resource sharing.

[0051] In some embodiments, the reported information includes resource usage information of the target network node, and determining a shared network node that meets the computing power requirement information from a computing power pool including multiple network nodes includes:

[0052] Based on the resource usage information, a shared network node that meets the computing power demand information is determined from the computing power pool containing multiple network nodes.

[0053] It is understood that each target network node in the computing power pool sends resource usage information to the first network node, and the resource usage information includes the resource usage of each target network node. Thus, the first network node can determine from the computing power pool a shared network node with more computing power resources that can meet the computing power requirements of the second network node based on the resource usage information of each network node, so that the second network node can deploy the target service on the shared network node and operate normally.

[0054] In some embodiments, the resource usage information may include at least one of a CPU real-time utilization rate, a GPU real-time utilization rate, a memory real-time occupancy rate, or a hard disk real-time occupancy rate.

[0055] In some embodiments, the reported information includes operating status information of the target network node, and determining a shared network node that meets the computing power requirement information from a computing power pool including multiple network nodes includes:

[0056] According to the operating status information, a shared network node that meets the computing power requirement information is determined from the computing power pool containing multiple network nodes.

[0057] It is understood that each target network node in the computing power pool sends operating status information to the first network node, and the operating status information includes the operating status of each target network node. Thus, the first network node can determine from the computing power pool a shared network node that can meet the computing power requirements of the second network node and is in good operating condition based on the operating status information of each network node, thereby improving the service quality of the target service deployed by the second network node on the shared network node.

[0058] In some embodiments, the operating status information may include: base station connection status information, including whether the base station is online, the connection status with the core network, and whether there is a disconnection; base station signal quality information, including quality indicator information of received and transmitted signals, such as signal strength, signal-to-noise ratio, bit error rate, etc.; power and power supply status information, including the status of the main power supply and backup power supply, power consumption and other information; user connection and traffic statistics information, including the number of users currently connected to the base station, the number of active users, data traffic, call volume and other statistical data; and at least one of delay information, service software version, etc.

[0059] Exemplarily, the first network node selects multiple network nodes with short bandwidth latency and high service software compatibility from the computing power pool according to the latency information or service software version in the running status information as the service deployment circle of the second network node, and the first network node determines the shared network node in the service deployment circle of the second network node.

[0060] In some embodiments, determining a shared network node that meets the computing power requirement information from a computing power pool comprising multiple network nodes includes steps S410 and S420.

[0061] Step S410: Obtain historical service deployment records.

[0062] Step S420: Determine a shared network node that meets the computing power requirement information from a computing power pool including multiple network nodes based on historical service deployment records.

[0063] It can be understood that when the first network node allocates shared network nodes, it obtains historical service deployment records and uses the historical service deployment records to perform KPI modeling, and screens the network nodes in the computing power pool from the perspective of improving service deployment efficiency, so that the first network node can allocate shared network nodes that significantly improve service deployment efficiency to the second network node.

[0064] In some embodiments, the historical service deployment record may include at least one of a deployed service type, service business data, etc. The service deployment record may be formed by the second network node during the process of deploying the target service on the shared network node.

[0065] It should be understood that the first network node can determine a shared network node that meets the computing power requirement information from a computing power pool comprising multiple network nodes based on at least one of resource usage information, operating status information, and historical service deployment records. In other words, the first network node can select any one, any two, or all three of the resource usage information, operating status information, and historical service deployment records as the basis for selecting a shared network node. For example, when allocating a shared network node, the first network node can determine a shared network node that meets the computing power requirement information from a computing power pool comprising multiple network nodes based on the resource usage information, operating status, and historical service deployment records. On the one hand, resource usage information can be used to identify network nodes in the computing power pool that not only meet the computing power requirement information but also have more computing power resources. On the other hand, operating status information can be used to screen a high-quality service deployment circle for the second network node in the computing power pool. On the other hand, the first network node can use historical service deployment records to perform KPI modeling, screening network nodes in the computing power pool from the perspective of improving service deployment efficiency, and assigning a shared network node that significantly improves service deployment efficiency to the second network node. Therefore, the first network node can select a shared network node with more shared resources and better service deployment effects within the service deployment circle of the second network node based on resource usage information, operation status information and historical service deployment records.

[0066] For example, please refer to Figure 4, which shows a flow chart of a computing power resource sharing method provided in an embodiment of the present application. As shown in Figure 4, the first network node uses a preset orchestration model to perform orchestration calculations to obtain a shared network node that can meet the computing power demand information, wherein the orchestration model involves three parameter dimensions: resource supply capability, service deployment efficiency improvement capability, and service deployment circle. The orchestration calculation is performed through the resource usage information, operating status information, and historical service deployment records of the network node. That is to say, in some embodiments, the first network node determines the shared network node that meets the computing power demand information from a computing power pool containing multiple network nodes based on the resource usage information, operating status information, and historical service deployment records, and is used to score and rank the network nodes in the computing power pool in terms of resource supply capability, service deployment circle, and service deployment efficiency improvement capability, so as to select network nodes with more shared resources and better service deployment effects from the service deployment circle of the second network node as much as possible to maximize the efficiency of service deployment.

[0067] In some embodiments, the computing power resource sharing method provided in the embodiments of the present application also includes steps S510 to S530.

[0068] Step S510: Obtain the service deployment record.

[0069] Step S520: Obtain the operation information of the target service based on the current service deployment record.

[0070] Step S530: Determine the next shared network node selection strategy for the computing power pool based on the operation information.

[0071] It can be understood that after the second network node deploys the target service on the shared network node, it records the service deployment information, and the first network node obtains the service deployment record. The first network node analyzes the service deployment record and determines the next shared network node selection strategy for the computing power pool from the perspective of service deployment effect based on the operation information.

[0072] In some embodiments, operational information may include performance indicators of the service, including response time, throughput, number of concurrent connections, and other indicators; availability and reliability indicators, including uptime, mean time to repair (MTTR), mean time between failures (MTBF), and other indicators; user behavior and experience data, including at least one of user visits, user activity, user retention rate, and other indicators.

[0073] In some embodiments, determining the next shared network node selection strategy of the computing power pool based on the operation information includes step S610 or step S620.

[0074] Step S610: When the operation information meets the preset conditions, the next shared network node selection strategy of the computing power pool is maintained.

[0075] Step S620: If the operation information does not meet the preset conditions, adjust the next shared network node selection strategy of the computing power pool.

[0076] It should be understood that judging whether the operation information of the target service meets the preset conditions, for example, in the performance indicators, judging whether the response time of the target service meets the expected requirements, in the reliability indicators, judging whether the average failure interval time of the target service meets the expected requirements, and in the user behavior indicators, judging whether the user visits of the target service meet the expected requirements, thereby determining the next shared network node selection strategy of the computing power pool based on the operation information. In some embodiments, if it is judged that the operation data meets the expected requirements, the current shared network node selection strategy is maintained. If it is judged that the operation data does not meet the expected requirements, the next shared network node selection strategy of the computing power pool is adjusted according to the built-in configuration or adjustment rules to improve the quality of subsequent cross-site deployment of services. Exemplarily, when the target service does not meet the expected requirements in terms of response time and average failure interval time, the next shared network node selection strategy of the computing power pool is adjusted to reduce the response time after the service cross-site deployment and reduce the occurrence of abnormalities and failures in the cross-site deployment of the service.

[0077] For example, a first network node assigns shared network node B to second network node A. Second network node A records the service deployment information. Subsequently, after analyzing the service deployment record, the first network node learns that shared network node B is not suitable for cross-site service deployment as a shared node for second network node A. The first network node can then adjust the computing power pool's next shared network node selection strategy, such as lowering the priority of shared network node B in the next shared network node selection. The unsuitability of shared network node B for cross-site service deployment can be manifested by the target service's response time and mean time between failures on shared network node B failing to meet expected requirements.

[0078] An embodiment of the present application also proposes a service deployment method, which is applied to the second network node. Please refer to Figure 5. Figure 5 shows a service deployment method provided by an embodiment of the present application. As shown in Figure 5, the service deployment method includes but is not limited to steps S710 to S730.

[0079] Step S710: Send a computing power resource acquisition request carrying computing power requirement information to the first network node, so that the first network node determines a shared network node that meets the computing power requirement information from a computing power pool including multiple network nodes.

[0080] Step S720: Receive identification information of the shared network node sent by the first network node.

[0081] Step S730: deploy the target service on the shared network node according to the identification information.

[0082] It can be understood that the second network node acts as a slave station of the computing power pool. When the second network node itself has insufficient resources, the second network node sends a computing power resource acquisition request carrying computing power demand information to the first network node acting as the master station of the computing power pool. The first network node selects and allocates shared network nodes based on the computing power demand information.

[0083] Through the service deployment method of the embodiment of the present application, the services on the network nodes can be deployed across sites to any network node in the computing power pool, realizing the sharing of computing power resources of multiple network nodes in the computing power pool. Network nodes in different regions can complement each other in terms of busy and idle software and hardware resources, solving a series of computing power shortage problems caused by tidal effects, regional business differences, high computing power requirements, etc., and at the same time maximizing the utilization of idle resources of each network node.

[0084] In the embodiment of the present application, compared with cloud services, the shared network node as a resource sharing party will not affect its own business when sharing resources, and the second network node as a resource demander can choose to deploy communication business services with high requirements for response speed and link quality at the local site, and deploy services that do not have high requirements for response speed and link quality, or have high computing power requirements across sites, so that efficient businesses use local site resources and general businesses use cross-site resources, which can achieve more scientific and reasonable resource sharing, can not only meet the resource needs of the second network node, but also improve the resource utilization of each network node in the computing power pool.

[0085] It should be noted that the specific implementation and beneficial effects of the service deployment method applied to the second network node in the above embodiment can be found in the relevant description of the computing resource sharing method applied to the first network node, and will not be repeated here.

[0086] In some embodiments, in an embodiment of the present application, a computing power resource acquisition request carrying computing power requirement information is sent to the first network node, including but not limited to step S810 and step S820.

[0087] Step S810: When the local idle resources cannot meet the needs of the target service, determine the computing power requirement information of the target service.

[0088] Step S810: Send a computing power resource acquisition request carrying computing power requirement information to the first network node.

[0089] It should be understood that as a slave station in the computing power pool, the second network node monitors the status of its own service. When the local idle resources cannot meet the target service, the second network node first determines the specific computing power demand information of the target service. Then, the second network node sends a computing power resource acquisition request carrying computing power demand information to the first network node as the resource demand direction, and performs cross-site deployment of services based on the identification information of the shared network node returned by the first network node, thereby realizing service self-management. Please refer to Figure 6, which shows a flow diagram of a service deployment method provided by an embodiment of the present application. As shown in Figure 6, when the second network node is short of resources, it selects to pop up service instance S1. After receiving the identification information of the shared network node sent by the first network node, the second network node establishes a communication connection with the shared network node based on the identification information. Then, the second network node creates a corresponding service instance S1 and deploys the service instance S1 on the shared network node.

[0090] In some embodiments, after the target service is deployed on the shared network node according to the identification information, the embodiment of the present application further includes step S910.

[0091] Step S910: obtaining the local real-time service load, and when the real-time service load is lower than a preset threshold, recovering the target service from the shared network node, and switching the target service to the local node.

[0092] In an embodiment of the present application, the service refers to a Kubernetes service, i.e., a container, which can be deployed across sites in the form of a process instance. When the real-time business load of the second network node is reduced and is lower than a preset threshold, the second network node can choose to redeploy the target service deployed across sites locally. That is, when the real-time business load of the second network node is lower than the preset threshold, the local idle resources representing the second network node can meet the target service deployed across sites. As shown in Figure 6, the second network node creates a service instance S1 of the target service and deploys the service instance S1 on a shared network node. The second network node reclaims the service instance S1 popped up by the target service from the shared network node and switches the target service to use a local instance. The second network node reclaims the service instance S1 popped up by the target service from the shared network node, and switches the target service to use a local instance. The second network node reclaims the service instance S1 popped up by the target service from the shared network node, including the second network node instructing the shared network node to delete the service instance S1 and migrate the cached data and persistent storage data of the service instance S1 to the second network node, cleans up the cached data and persistent storage data, and releases the hardware resources occupied by the second network node.

[0093] In some embodiments, after the target service is deployed on the shared network node according to the identification information, the embodiment of the present application further includes step S1010 and step S1020.

[0094] Step S1010: When a deployment exception occurs in the target service on the shared network node, the target service is recovered from the shared network node.

[0095] Step S1020: resend a computing power resource acquisition request carrying computing power requirement information to the first network node, so that the first network node re-determines a new shared network node that meets the computing power requirement information from the computing power pool containing multiple network nodes.

[0096] It is understandable that after the second network node deploys its own service across sites, it monitors the deployed shared network node and the target service.

[0097] In some embodiments, the second network node may periodically or regularly send a status query request for the target service to the shared network node, so that the shared network node returns the status information of the target service to the second network node based on the status query request. For example, for an interactive target service, the status information may include whether the service is operating normally, the response time and throughput of the service during operation, and other information. If the second network node learns from the status information returned by the shared network node that the target service has a deployment anomaly on the shared network node, such as a response time delay, a decrease in throughput, or an abnormal termination of the service due to an operation error, the second network node may choose to reclaim the service instance popped up by the target service from the shared network node and re-deploy the target service across sites, thereby achieving self-repair of the service. In some embodiments, the second network node re-sends a computing resource acquisition request carrying computing power requirement information to the first network node, so that the first network node re-determines a new shared network node that meets the computing power requirement information from a computing power pool containing multiple network nodes. The second network node then re-deploys the target service across sites on the new shared network node, thereby achieving self-repair of the service and seamlessly switching the service when a service deployment anomaly occurs, so that users are unaware of or only experience a very brief interruption when using the service.

[0098] In some embodiments, the service deployment method provided in the embodiments of the present application also includes step S1110.

[0099] Step S1110: Continue to send reporting information to the first network node.

[0100] It can be understood that the second network node, as a slave station in the computing power pool, continuously (periodically, regularly, conditionally triggered or user-triggered, or several methods exist simultaneously) sends reporting information to the first network node, so that the first network node can monitor the status and allocate resources of each network node in the computing power pool according to the reporting information, realize the automatic management of the computing power pool, reduce the cost of manual intervention and improve the efficiency of operation and maintenance.

[0101] The following describes the computing resource sharing method and service deployment method provided in the embodiments of the present application through examples.

[0102] Please refer to Figure 7, which shows a schematic diagram of an implementation of a service deployment method provided by an embodiment of the present application. As shown in Figure 7, the computing power pool includes base station A, base station B, base station C..., wherein base station C is the master station in the computing power pool, and base station A, base station B and other base stations are slave stations in the computing power pool. The slave stations periodically send reporting information to the master station, and the master station receives the reporting information sent by the slave stations and uses it to monitor the status of the slave stations. During this period, base station A has insufficient resources and is unable to deploy target services SA4 and SA5 at this station. Then, base station A, as the resource demand direction, sends computing power resource request information carrying computing power demand information of target services SA4 and SA5 to base station C. After base station C receives the computing power demand information sent by base station A, it determines from each base station in the computing power pool that base station B can meet the computing power demand. Therefore, the master station sends the identification information of base station B to base station A, so that base station A can deploy target services SA4 and SA5 across base stations at base station B.

[0103] The embodiment of the present application further provides a computing power resource sharing system, which includes a first network node and multiple second network nodes, wherein the first network node and the multiple second network nodes form a computing power pool, wherein:

[0104] The first network node is configured to receive a computing power resource acquisition request sent by the second network node, the computing power resource acquisition request carrying computing power requirement information, determine a shared network node that meets the computing power requirement information from the computing power pool, and send identification information of the shared network node to the second network node, so that the second network node deploys a target service on the shared network node based on the identification information;

[0105] The second network node is configured to send a computing power resource acquisition request carrying computing power requirement information to the first network node, so that the first network node determines a shared network node that meets the computing power requirement information from a computing power pool containing multiple network nodes, receives the identification information of the shared network node sent by the first network node, and deploys the target service on the shared network node according to the identification information.

[0106] It should be noted that the above embodiment describes a computing power resource sharing system. For the first network node and the second network node in the computing power resource sharing system, the specific implementation of the execution steps and the beneficial effects can be found in the relevant descriptions in the computing power resource sharing method and the service deployment method, which will not be repeated here.

[0107] Referring to FIG. 8 , an embodiment of the present application further provides an electronic device, which includes but is not limited to:

[0108] at least one processor 2001;

[0109] At least one memory 2002, configured to store at least one program;

[0110] When at least one program is executed by at least one processor 2001, the computing resource sharing method applied to the first network node as described in any of the above embodiments is executed; or, the service deployment method applied to the second network node as described in any of the above embodiments is executed.

[0111] It should be understood that the processor 2001 and the memory 2002 may be connected via a bus or other means.

[0112] It should be understood that the processor 2001 can be a central processing unit (CPU). The processor can also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. Alternatively, the processor 2001 uses one or more integrated circuits to execute relevant programs to implement the technical solutions provided in the embodiments of the present application.

[0113] Memory 2002, as a non-transitory computer-readable storage medium, can be used to store non-transitory software programs and non-transitory computer executable programs, such as the collaborative perception method performed on the electronic device side described in any embodiment of this application. Processor 2001 executes the non-transitory software program and instructions stored in memory 2002 to implement the computing resource sharing method applied to the first network node as described in any of the above embodiments; or implement the service deployment method applied to the second network node as described in any of the above embodiments.

[0114] Memory 2002 may include a program storage area and a data storage area. The program storage area may store an operating system and at least one application required for a function; the data storage area may store and execute the collaborative perception method described above. Furthermore, memory 2002 may include high-speed random access memory and non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state storage device.

[0115] In some embodiments, the memory 2002 includes a memory remotely located relative to the processor 2001, and these remote memories may be connected to the processor 2001 via a network. Examples of the aforementioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0116] The non-transient software programs and instructions required to implement the above-mentioned computing power resource sharing method or service deployment method are stored in the memory 2002. When executed by one or more processors 2001, the computing power resource sharing method or service deployment method provided by any embodiment of the present application is executed.

[0117] An embodiment of the present application also provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, it implements the computing power resource sharing method applied to the first network node as described in any of the above embodiments; or implements the service deployment method applied to the second network node as described in any of the above embodiments.

[0118] In an embodiment of the present application, a first network node receives a computing power resource acquisition request sent by a second network node, where the computing power resource acquisition request carries computing power demand information. The first network node then determines a shared network node that meets the computing power demand information from a computing power pool containing multiple network nodes, and sends the identification information of the shared network node to the second network node, so that the second network node deploys a target service on the shared network node according to the identification information. In an embodiment of the present application, the first network node determines a corresponding shared network node from a computing power pool containing multiple network nodes for the second network node, so that the second network node can deploy its own service on the shared network node, thereby realizing resource sharing between network nodes, improving the resource utilization of network nodes, reducing the operating costs of operators, and meeting the current high-speed business requirements.

[0119] The computer storage medium of the embodiment of the present application can adopt any combination of one or more computer-readable media.Computer-readable media can be computer-readable signal media or computer-readable storage media.Computer-readable storage media can be, for example, but not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or devices, or any combination thereof.Examples (non-exhaustive) of computer-readable storage media include: electrical connections with one or more wires, portable computer disks, hard disks, random access memories (RAM), read-only memories (ROM), erasable programmable read-only memories (EPROM or flash memory), optical fibers, portable compact disk read-only memories (CD-ROMs), optical storage devices, magnetic storage devices, or any suitable combination thereof.In this document, computer-readable storage media can be any tangible medium containing or storing a program, which can be used by an instruction execution system, device or device or used in combination with it.

[0120] A computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, which carries computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or transport a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0121] Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

[0122] The computer program code for performing the operations of the present application can be written in one or more programming languages, or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computer (such as through the Internet using an Internet service provider).

[0123] An embodiment of the present application also provides a computer program product, which stores program instructions. When the program instructions are executed on a computer device, the computer device implements the computing power resource sharing method applied to the first network node as described in any of the above embodiments; or implements the service deployment method applied to the second network node as described in any of the above embodiments.

[0124] The above is an explanation of the implementation of this application, but this application is not limited to the above implementation. Those skilled in the art can make various equivalent modifications or substitutions without violating the spirit of this application. These equivalent modifications or substitutions are all included in the scope defined by this application.

Claims

1. A computing resource sharing method, applied to a first network node, the method comprising: Receive a computing power resource acquisition request sent by the second network node, where the computing power resource acquisition request carries computing power demand information; Determine a shared network node that meets the computing power requirement information from a computing power pool including multiple network nodes; The identification information of the shared network node is sent to the second network node, so that the second network node deploys the target service on the shared network node according to the identification information.

2. The computing resource sharing method according to claim 1, further comprising: Receive reporting information sent by the target network node in the computing power pool.

3. The computing resource sharing method according to claim 2, further comprising: The target network node is marked as being in an abnormal state or a normal state according to the reported information.

4. The computing resource sharing method according to claim 2, wherein: The reported information includes resource usage information of the target network node; The determining a shared network node that meets the computing power requirement information from a computing power pool including multiple network nodes includes: Determine a shared network node that meets the computing power requirement information from a computing power pool including multiple network nodes according to the resource usage information.

5. The computing resource sharing method according to claim 2, wherein: The reported information includes the operating status information of the target network node; The determining a shared network node that meets the computing power requirement information from a computing power pool including multiple network nodes includes: Determine a shared network node that meets the computing power requirement information from a computing power pool comprising multiple network nodes according to the operating status information.

6. The computing resource sharing method according to claim 1, wherein: The determining a shared network node that meets the computing power requirement information from a computing power pool including multiple network nodes includes: Get historical service deployment records; According to the historical service deployment record, a shared network node that meets the computing power demand information is determined from a computing power pool including multiple network nodes.

7. The computing resource sharing method according to claim 1, further comprising: Get the service deployment record. Obtaining the operation information of the target service according to the service deployment record; The next shared network node selection strategy of the computing power pool is determined according to the operation information.

8. A service deployment method, applied to a second network node, the method comprising: Sending a computing power resource acquisition request carrying computing power demand information to the first network node, so that the first network node determines a shared network node that meets the computing power demand information from a computing power pool including multiple network nodes; receiving identification information of the shared network node sent by the first network node; A target service is deployed on the shared network node according to the identification information.

9. The service deployment method according to claim 8, wherein: The sending a computing power resource acquisition request carrying computing power requirement information to the first network node includes: When the local idle resources cannot meet the needs of the target service, determine the computing power requirement information of the target service; Send a computing power resource acquisition request carrying the computing power requirement information to the first network node.

10. The service deployment method according to claim 8, wherein: After deploying the target service on the shared network node according to the identification information, the method further includes: A local real-time service load is obtained, and when the real-time service load is lower than a preset threshold, the target service is recovered from the shared network node, and the target service is switched to the local node.

11. The service deployment method according to claim 8, wherein: After deploying the target service on the shared network node according to the identification information, the method further includes: When there is a deployment exception of the target service on the shared network node, reclaiming the target service from the shared network node; Resend a computing power resource acquisition request carrying computing power demand information to the first network node, so that the first network node re-determines a new shared network node that meets the computing power demand information from a computing power pool including multiple network nodes.

12. The service deployment method according to claim 8, further comprising: Continue to send reporting information to the first network node.

13. A computing resource sharing system, the system comprising a first network node and a plurality of second network nodes, the first network node and the plurality of second network nodes forming a computing power pool, wherein: The first network node is configured to receive a computing power resource acquisition request sent by the second network node, the computing power resource acquisition request carries computing power demand information, determines a shared network node that meets the computing power demand information from the computing power pool, and sends identification information of the shared network node to the second network node, so that the second network node deploys a target service on the shared network node according to the identification information; The second network node is configured to send a computing power resource acquisition request carrying computing power demand information to the first network node, so that the first network node determines a shared network node that meets the computing power demand information from a computing power pool comprising multiple network nodes, receives identification information of the shared network node sent by the first network node, and deploys a target service on the shared network node according to the identification information.

14. An electronic device comprising: one or more processors; A memory having one or more programs stored thereon, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the computing resource sharing method as described in any one of claims 1 to 7; or, implement the service deployment method as described in any one of claims 8 to 12.

15. A computer-readable storage medium having a computer program stored thereon, wherein when the program is executed by a processor, the computing resource sharing method as described in any one of claims 1 to 7 is implemented; or, the service deployment method as described in any one of claims 8 to 12 is implemented.

Images