Computing power resource scheduling method, network element, storage medium and program product

Abstract

Disclosed are a computing power resource scheduling method, a network element, a storage medium and a program product, the method being applied to a first network, the method comprising: receiving a first computing power resource request, the first computing power resource request comprising an identifier of a computing power resource node cluster where a computing power resource requester is located, the computing power resource node cluster comprises computing power resource nodes of industry customers and operators; according to a preset computing power resource scheduling strategy, determining a target computing power resource node providing computing power resources for the computing power resource requester in the computing power resource node cluster; and sending the second computing power resource request to the target computing power resource node, so that the target computing power resource node allocates the corresponding computing power resource.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of communication, and in particular to a computing power resource scheduling method, a network element, a storage medium and a program product. BACKGROUND

[0002] In the medical industry, a medical association (referred to as a medical association) is a joint body composed of medical institutions of different levels and different categories, aiming to realize resource sharing, complementary advantages and collaborative services. Computing power can help hospitals to process and analyze large-scale medical data more quickly. In the field of intelligent medical care, a large amount of computing power resources are needed to provide computing power. For a medical association, computing power resources play a key role in data processing, analysis, storage and transmission.

[0003] In a medical association, large-scale first-class hospitals have more abundant computing power resources, while primary medical institutions or small and medium-sized hospitals have relatively insufficient computing power resources, resulting in limited medical services. In addition, operators deploy a large number of edge computing nodes at the edge of their networks, and medical institutions can access computing nodes nearby to obtain computing power resources. However, some sensitive data cannot be deployed on external computing nodes, and there is currently a lack of unified management and scheduling mechanism for computing power resources of a medical association. SUMMARY

[0004] Therefore, the embodiments of the present application provide a computing power resource scheduling method, a network element, a storage medium and a program product.

[0005] The technical scheme of the embodiments of the present application is as follows:

[0006] On the one hand, the embodiments of the present application provide a computing power resource scheduling method applied to a first network element, and the method comprises:

[0007] receiving a first computing power resource request, wherein the first computing power resource request comprises an identifier of a computing power resource node cluster where a computing power resource requester is located; the computing power resource node cluster comprises computing power resource nodes of industry customers and operators;

[0008] determining a target computing power resource node in the computing power resource node cluster for providing computing power resources for the computing power resource requester according to a preset computing power resource scheduling strategy;

[0009] sending a second computing power resource request to the target computing power resource node, so that the target computing power resource node allocates corresponding computing power resources.

[0010] In the above scheme, before receiving the first computing power resource request, the method further comprises:

[0011] A registration request is sent to the second network element, the registration request including the identifier of the first network element, the address of the first network element, and the identifier of the computing power resource node cluster.

[0012] In the above scheme, the method further includes:

[0013] The third network element receives the computing resource scheduling strategy sent by the third network element; the third network element queries the address of the first network element from the second network element based on the identifier of the computing resource node cluster.

[0014] In the above scheme, before receiving the first computing resource request, the method further includes:

[0015] Receive a computing power service registration request from a computing power resource node. The computing power service registration request includes the identifier of the computing power resource node cluster to which the computing power resource node belongs and the type of the computing power resource node.

[0016] In the above scheme, after receiving the computing power service registration request from the computing power resource node, the method further includes:

[0017] Receive computing resource information reported by the computing resource nodes.

[0018] In the above scheme, when the type of computing power resource node is an operator's computing power resource node, receiving the computing power service registration request from the computing power resource node includes:

[0019] The fourth network element receives a computing power service registration request from the computing power resource node sent by the fourth network element. The fourth network element then queries the address of the first network element from the second network element based on the identifier of the computing power resource node cluster.

[0020] In the above scheme, when the type of computing resource node is an industry customer's computing resource node, receiving the computing service registration request from the computing resource node includes:

[0021] The system receives a computing power service registration request from the computing power resource node sent by the fifth network element. The computing power resource node sends the computing power service registration request through the fifth network element, which is a control plane network element. The fifth network element queries the address of the first network element from the second network element based on the identifier of the computing power resource node cluster.

[0022] In the above scheme, when the type of computing resource node is an industry customer's computing resource node, receiving the computing service registration request from the computing resource node includes:

[0023] The system receives a computing power service registration request from a third network element, which is a network capability open network element. The third network element queries the second network element to obtain the address of the first network element based on the identifier of the computing power resource node cluster.

[0024] In the above scheme, receiving the first computing resource request includes:

[0025] The system receives a first computing resource request sent by a fifth network element, which is a control plane network element. The fifth network element obtains the address of the first network element from the second network element based on the identifier of the computing resource node cluster.

[0026] In the above scheme, receiving the first computing resource request includes:

[0027] The system receives a first computing resource request sent by a third network element, which is a network capability open network element. The third network element obtains the address of the first network element from the second network element based on the identifier of the computing resource node cluster.

[0028] In the above scheme, the first computing resource request includes an application security level, the preset computing resource scheduling strategy includes the correspondence between the application security level and the computing resource node type, and the step of determining the target computing resource node in the computing resource node cluster that provides computing resources to the computing resource requester according to the preset computing resource scheduling strategy includes:

[0029] Based on the application security level, the type of the target computing resource node is determined.

[0030] In the above scheme, after sending the second computing resource request to the target computing resource node, the method further includes:

[0031] Receive a response message sent by the target computing resource node, the response message including the computing resource access address;

[0032] The response message is sent to the requester of the computing resources.

[0033] This application embodiment also provides a network element, including: a processor and a memory for storing a computer program that can run on the processor, wherein the processor, when running the computer program, executes the steps in the above-described computing resource scheduling method.

[0034] This application embodiment also provides a computer storage medium storing a computer program, which, when executed by a processor, implements the steps in the above-described computing resource scheduling method.

[0035] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps in the above-described computing resource scheduling method.

[0036] This embodiment of the application receives a first computing resource request, which includes the identifier of the computing resource node cluster where the requester resides. The computing resource node cluster includes computing resource nodes from operators and industry customers. Based on a preset computing resource scheduling strategy, a target computing resource node within the computing resource node cluster is determined to provide computing resources to the requester. A second computing resource request is then sent to the target computing resource node, enabling it to allocate the corresponding computing resources. In this embodiment, when an industry customer needs to schedule computing resources, the first network element can schedule computing resources provided by other industry customers or operators within the computing resource node cluster according to the scheduling strategy. This allows for more efficient and rational use of the computing resources in the computing resource node cluster, improving the service response speed for industry customers. Attached Figure Description

[0037] Figure 1 This is a schematic diagram of a fixed-mobile converged network architecture provided in an embodiment of the present invention;

[0038] Figure 2 A schematic diagram of a lightweight core network system architecture provided for an embodiment of this application;

[0039] Figure 3 A schematic diagram of a medical consortium networking architecture provided in this application embodiment;

[0040] Figure 4 A schematic diagram of another medical consortium networking architecture provided in this application embodiment;

[0041] Figure 5 A flowchart illustrating a computing resource scheduling method provided in an embodiment of this application;

[0042] Figure 6 A flowchart illustrating the configuration of a computing resource scheduling strategy provided in an embodiment of the present invention;

[0043] Figure 7 A schematic diagram illustrating a computing power service registration process provided in an embodiment of the present invention;

[0044] Figure 8 This is a schematic diagram of another computing power service registration process provided in an embodiment of the present invention;

[0045] Figure 9 This is a schematic diagram of another computing power service registration process provided in an embodiment of the present invention;

[0046] Figure 10 This is a schematic diagram of a computing power service request process provided in an embodiment of the present invention;

[0047] Figure 11 A schematic diagram illustrating a process for determining a computing resource provider, provided as an embodiment of this application;

[0048] Figure 12 A schematic diagram of another computing power service request process provided for an embodiment of this application;

[0049] Figure 13 This is a schematic diagram of the hardware composition structure of a network element provided in an embodiment of this application. Detailed Implementation

[0050] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0051] Fixed-mobile convergence, also known as wireless-wired convergence, is the integration and cooperation between fixed and mobile networks to enable the operation of full-service and converged services, providing users with diverse, high-quality communication, information, and entertainment services, independent of their terminals, networks, applications, and locations. To achieve 5G fixed-mobile convergence, the 3rd Generation Partnership Project (3GPP) defines two types of gateways: Residential Gateway (RG) and Wireline Access Gateway Function (W-AGF), deployed on the user side and network side respectively, to address convergence issues in the following two locations:

[0052] The RG (Regulator) sits between the terminal and the access network, and is further divided into 5G-RG and Fixed Network Residential Gateway (FN-RG). 5G-RG has 5G communication capabilities and can interface with Next Generation Radio Access Network (NG-RAN) as well as wired access networks; while FN-RG can only interface with wired access networks.

[0053] W-AGF is positioned between the wired access network and 5GC, and together with the wired access network, it forms W-5GAN (wired 5G access network). It connects with 5GC through the standard 3GPP N2 and N3 interfaces.

[0054] "RG+W-AGF" is the foundation for realizing 5G fixed-mobile convergence. The fixed-mobile convergence network architecture based on 5G-RG+W-AGF is as follows: Figure 1 As shown in the diagram. N1-N15 are network interfaces in the network architecture. Based on the above 5G fixed-mobile converged architecture, the terminal first accesses the 5G-RG through a non-3GPP network (WLAN, wired, Bluetooth, etc.), and then indirectly accesses the 5G core network through the 5G-RG.

[0055] The Service-Based Architecture (SBA) design concept defined by 3GPP provides system architecture guarantees for lightweight core network deployment. By decomposing 5GC network element functions into several fine-grained, reusable network services, the decoupled network elements are connected via a unified message bus, enabling plug-and-play operation. Network services can be deployed uniformly or in a distributed manner, providing agile system architecture support for lightweight 5GC. Based on the service-based architecture, unnecessary network elements can be removed from the 5G core network, creating a lightweight core network product where network element function services can be combined on demand. Addressing the common and specific network needs of vertical industry users, lightweight 5GC possesses typical characteristics such as low cost, easy customization, high security, self-service, and interoperability with the public network. The system architecture is as follows: Figure 2 As shown.

[0056] A medical consortium (or medical alliance) is a consortium composed of medical institutions of different levels and categories, aiming to achieve resource sharing, complementary advantages, and collaborative services. Computing power enables hospitals to process and analyze large-scale medical data more quickly. In smart healthcare scenarios, such as intelligent consultation and AI-assisted image diagnosis, substantial computing resources are required. For medical consortia, computing resources play a crucial role in data processing, analysis, storage, and transmission. Within a medical consortium, different medical institutions need to exchange and share a large amount of data, including patient information, medical records, and diagnostic results, to achieve optimized resource allocation and service synergy.

[0057] However, the use of computing resources within medical consortia faces the following problems:

[0058] 1. Uneven distribution of computing resources: Generally, large tertiary hospitals have abundant computing resources, including more hardware such as servers and storage devices, as well as more advanced software technologies and algorithm models, enabling them to provide more efficient and accurate medical services. In contrast, primary healthcare institutions or small and medium-sized hospitals have relatively scarce computing resources, resulting in limited medical services.

[0059] 2. Lack of unified management of computing resources: Due to the lack of a unified management and scheduling mechanism, computing resources within the medical consortium often cannot be shared and coordinated efficiently, resulting in waste and duplication of resources, and may also reduce the response speed and accuracy of medical services.

[0060] 3. Lack of unified scheduling of internal and external computing resources: Operators have deployed a large number of edge clouds at the edge of their networks to support industry applications. Medical institutions can access computing resources from nearby computing nodes. However, due to the extremely high requirements of the medical industry for privacy data protection, some core applications and sensitive data cannot be deployed on external computing nodes. Therefore, a mechanism for unified scheduling of internal and external computing resources is needed to meet the needs of applications with different security levels.

[0061] In layman's terms, computing power refers to the ability to compute data. It can be defined as the ability of a node in a network with computing power to process data and output specific results. Computing power resources specifically include resources such as central processing units (CPUs), graphics processing units (GPUs), memory, and storage.

[0062] The metrics used to measure CPU and GPU are shown in Table 1 below:

[0063]

[0064] Table 1

[0065] The metrics used to measure memory and storage are shown in Table 2 below:

[0066]

[0067] Table 2

[0068] To address the shortcomings of the aforementioned related technologies, this invention provides a method for scheduling computing resources. Specific embodiments are described below to illustrate the technical solution described in this invention.

[0069] In one embodiment, the technical solution of this application relies on the following: Figure 3 The medical consortium network architecture shown in the diagram has a medical edge cloud within the hospitals of the medical consortium that is connected to a 5GC based on a 5G fixed-mobile converged architecture (which can be a lightweight 5GC customized for the medical consortium). The medical edge clouds of different hospitals can be directly interconnected through the 5G Local Area Network (LAN) function.

[0070] based on Figure 3In this application embodiment, a new Computing Resource Scheduling Function (CRSF) network element is added to the 5GC to uniformly manage and schedule the computing resources provided by the edge computing nodes deployed by the operator and the medical edge cloud of the member hospitals of the medical consortium. The network architecture is as follows: Figure 4 As shown.

[0071] The hospital's edge cloud connects to the hospital's 5G-RG, which in turn connects to the core network's W-AGF. The hospital's 5G-RG also connects to the core network's AMF via a base station. Operators deploy edge computing nodes (MECs) for the medical consortium. These deployments can be either a combined UPF and MEC setup or a MEC-only setup.

[0072] The process begins with the deployment of a new CRSF within the medical consortium. This CRSF can be newly created or selected from existing ones. The new CRSF must register with the 5GC's Network Repository Function (NRF) network element so that other network elements can discover it. The medical consortium management platform then issues computing resource scheduling policies to the CRSF through the Network Exposure Function (NEF) network element. The operator registers the edge computing nodes deployed within the medical consortium with the CRSF for computing services. Hospitals within the medical consortium that can provide computing resource services also register their computing service with the CRSF and report their computing resource status in real time. Hospitals within the medical consortium that require computing resources submit computing resource requests to the CRSF. Based on the computing resource scheduling policy and considering the computing resource status of edge computing nodes and medical edge clouds, the CRSF determines the computing resource provider and provides feedback to the computing resource requesting party. The requesting party then connects to the computing resource provider to utilize the computing resources.

[0073] Figure 5 This is a schematic diagram illustrating the implementation process of a computing resource scheduling method provided in an embodiment of the present invention. The method is applied to a first network element, which can be... Figure 4 CRSF network elements in the reference Figure 5 The computing resource scheduling methods include:

[0074] S501, Receive a first computing power resource request, the first computing power resource request including the identifier of the computing power resource node cluster where the computing power resource requester is located; the computing power resource node cluster includes computing power resource nodes of operators and industry customers.

[0075] Among them, the computing power resource nodes of industry customers are connected to the core network (AMF or W-AGF) through gateways, while the computing power resource nodes of operators are connected to the core network's UPF (or co-located with the UPF).

[0076] Here, the computing resource node cluster consists of computing resource nodes from operators and industry customers, aiming to achieve resource sharing, complementary advantages, and collaborative services. For example, one type of computing resource node cluster is a medical consortium. Industry customers refer to hospitals or medical institutions within the medical consortium. The medical consortium includes the hospital's own computing resource nodes (medical edge cloud) and computing resource nodes deployed by operators for the medical consortium.

[0077] The requester of computing resources is also a computing resource node in the computing resource node cluster. When the requester's own computing resources are insufficient, it can submit a computing resource application to the first network element, which will then allocate computing resources from other computing resource nodes (industry customers or operators) in the computing resource node cluster for its use. This can be achieved through two implementation methods: application via the control plane and application via network capability opening (detailed explanations will follow).

[0078] The first computing resource request should at least include the identifier of the computing resource node cluster (e.g., medical consortium ID), and may also include information such as the quantity of computing resources requested, the type of computing resources requested, and the ID and address of the computing resource requester.

[0079] S502, according to the preset computing power resource scheduling strategy, determine the target computing power resource node in the computing power resource node cluster that provides computing power resources to the computing power resource requester.

[0080] The first network element stores preset computing resource scheduling strategies. Taking a medical consortium as an example, the medical consortium management platform can issue computing resource scheduling strategies to the first network element based on the needs of medical industry customers.

[0081] The computing power resource scheduling strategy includes, but is not limited to: the correspondence between application security level and computing power node type (different types of computing power nodes are suitable for deploying applications with different security levels. For example, applications with high security level can only apply for and be deployed on the medical edge cloud, while applications with ordinary security level have no such restriction); the preferred computing power node type (e.g., applications with ordinary security level can be deployed on two types of computing power nodes, and the system should prioritize which type); and the computing power node selection strategy corresponding to the computing power node type (e.g., priority given to proximity or priority given to low resource utilization).

[0082] Based on a preset computing resource scheduling strategy, the target computing resource nodes in the computing resource node cluster that will provide computing resources to the requester are determined. For example, the target computing resource nodes that are closest to the requester are selected first.

[0083] S503, send a second computing power resource request to the target computing power resource node so that the target computing power resource node can allocate the corresponding computing power resources.

[0084] A second computing resource request is sent to the target computing resource node, requesting the allocation of corresponding computing resources. After the target computing resource node allocates the computing resources, it sends a computing resource response message to the first network element, including computing resource access address information, and may also include information such as computing resource type and quantity. Then, the first network element sends a response message to the computing resource requester, who then accesses the computing resource access address to use the computing resources.

[0085] This embodiment of the application receives a first computing resource request, which includes the identifier of the computing resource node cluster where the requester resides. The computing resource node cluster includes computing resource nodes from operators and industry customers. Based on a preset computing resource scheduling strategy, a target computing resource node within the computing resource node cluster is determined to provide computing resources to the requester. A second computing resource request is then sent to the target computing resource node, enabling it to allocate the corresponding computing resources. In this embodiment, when an industry customer needs to schedule computing resources, the first network element can schedule computing resources provided by other industry customers or operators within the computing resource node cluster according to the scheduling strategy. This allows for more efficient and rational use of the computing resources in the computing resource node cluster, improving the service response speed for industry customers.

[0086] In one embodiment, before receiving the first computing resource request, the method further includes:

[0087] A registration request is sent to the second network element, the registration request including the identifier of the first network element, the address of the first network element, and the identifier of the computing power resource node cluster.

[0088] The first network element can be a CRSF network element, and the second network element can be an NRF network element. The CRSF initiates a registration request to the NRF, and the registration information includes, but is not limited to: CRSF ID, CRSF IP address, CRSF domain name, and computing power resource node cluster ID.

[0089] In one embodiment, the method further includes:

[0090] The third network element receives the computing resource scheduling strategy sent by the third network element; the third network element queries the address of the first network element from the second network element based on the identifier of the computing resource node cluster.

[0091] Here, the third network element can be a Network Exposure Function (NEF) network element, such as... Figure 6 As shown, Figure 6This is a flowchart illustrating the configuration of a computing resource scheduling strategy according to an embodiment of the present invention. Taking a medical consortium as an example, the computing resource node cluster, based on the needs of medical industry customers, sends a computing resource scheduling strategy to CRSF, as shown in the flowchart:

[0092] 1. The medical consortium management platform sends a computing resource scheduling strategy to NEF, carrying at least the following information: medical consortium ID and computing resource scheduling strategy. The strategy includes, but is not limited to: the correspondence between application security level and computing node type (different types of computing nodes are suitable for deploying applications with different security levels. For example, high-security level applications can only apply for and be deployed on the medical edge cloud, while applications with ordinary security level have no such restriction), the preferred computing node type (e.g., applications with ordinary security level can be deployed on two types of computing nodes, and the system should prioritize which type), and the computing node selection strategy corresponding to the computing node type (e.g., proximity priority or low resource utilization priority).

[0093] 2. NEF queries NRF for the CRSF corresponding to the medical consortium, carrying information including at least the medical consortium ID.

[0094] 3. Based on the CRSF's registration information, NRF queries the CRSF corresponding to the medical consortium that meets the requirements, and sends the CRSF's identifier and address information to NEF.

[0095] 4. NEF sends the computing resource scheduling policy to CRSF.

[0096] 5. After CRSF is configured, it sends a response message to NEF, which then forwards it to the medical consortium management platform.

[0097] In one embodiment, before receiving the first computing resource request, the method further includes:

[0098] Receive a computing power service registration request from a computing power resource node. The computing power service registration request includes the identifier of the computing power resource node cluster to which the computing power resource node belongs and the type of the computing power resource node.

[0099] In one embodiment, after receiving a computing power service registration request from a computing power resource node, the method further includes:

[0100] Receive computing resource information reported by the computing resource nodes.

[0101] After registering computing power services with CRSF, the computing power resource nodes will report their computing power resource information to CRSF in real time. The information carried includes, but is not limited to, the ID of the computing power resource node, the total amount and utilization rate of each type of computing power resources provided by the computing power resource node, and the cluster ID of the computing power resource node. The reporting methods include, but are not limited to, scheduled reporting and reporting when the total amount of resources or the utilization rate changes when a certain threshold is exceeded.

[0102] The registration methods differ for different types of computing resource nodes. In one embodiment, when the type of computing resource node is an operator's computing resource node, receiving the computing service registration request from the computing resource node includes:

[0103] The fourth network element receives a computing power service registration request from the computing power resource node sent by the fourth network element. The fourth network element then queries the address of the first network element from the second network element based on the identifier of the computing power resource node cluster.

[0104] The fourth network element can be a Session Management Function (SMF) network element. When operators deploy Multi-access Edge Computing (MEC) nodes for industry customers, the node deployment method can be a combination of User Plane Function (UPF) network elements and MEC, or it can be MEC only. Taking a medical consortium as an example, the process for the operator's edge computing resource nodes to register computing services with the CRSF is as follows: Figure 7 As shown, the process is explained below:

[0105] 1. Edge computing resource nodes send computing service registration requests to UPF network elements, carrying information including but not limited to: computing node type (identified as operator edge computing node), MEC ID, MEC location information, medical consortium ID, computing service duration, and computing resource type (such as GPU, CPU, storage, etc.).

[0106] 2. UPF forwards the computing power service registration request to SMF.

[0107] 3. The SMF queries the NRF for the CRSF corresponding to the medical consortium, carrying information including at least the medical consortium ID.

[0108] 4. Based on the CRSF's registration information, NRF queries the CRSF corresponding to the medical consortium that meets the requirements, and sends the CRSF's identifier and address information to SMF.

[0109] 5. SMF sends a MEC computing power service registration request to CRSF.

[0110] 6. After completing the MEC computing power service registration, CRSF sends a response message to SMF, and then SMF forwards the computing power service registration response message to UPF, and UPF forwards it to MEC.

[0111] After registering its computing power service with CRSF, MEC will report its computing power resource information to CRSF in real time:

[0112] Information carried includes, but is not limited to, MEC ID, the total amount and utilization rate of various types of computing resources provided by MEC, and medical consortium ID;

[0113] Reporting path: MEC->UPF->SMF->CRSF;

[0114] Reporting methods include, but are not limited to, scheduled reporting and reporting when the total amount of resources or the utilization rate changes beyond a certain threshold.

[0115] Within a medical consortium, some or all hospitals can choose to share the computing resources of the medical edge cloud, depending on the industry's customer strategies. The medical edge cloud providing shared computing resources needs to register its computing service with CRSF. Registration can be done through two methods: control plane registration and network capability open registration.

[0116] In the control plane registration embodiment, when the type of the computing resource node is an industry customer (such as a hospital) computing resource node, receiving the computing service registration request from the computing resource node includes:

[0117] The system receives a computing power service registration request from the computing power resource node sent by the fifth network element. The computing power resource node sends the computing power service registration request through the fifth network element, which is a control plane network element. The fifth network element queries the address of the first network element from the second network element based on the identifier of the computing power resource node cluster.

[0118] The fifth network element is the Access and Mobility Management Function (AMF) network element. Taking a medical consortium as an example, the registration process for computing power services of computing power resource nodes is as follows: Figure 8 As shown, the process is explained below:

[0119] 1. The medical edge cloud sends a computing power service registration request to 5G-RG, carrying information including but not limited to: computing power node type (identified as medical edge cloud), medical edge cloud ID, medical consortium ID, medical edge cloud location information, computing power service duration, and computing power resource type (such as GPU, CPU, storage, etc.).

[0120] 2. 5G-RG forwards computing power registration requests to AMF via W-AGF or RAN.

[0121] 3. The AMF queries the NRF for the CRSF corresponding to the medical consortium, carrying information including at least the medical consortium ID; the NRF queries the CRSF corresponding to the medical consortium that meets the requirements based on the CRSF's registration information, and sends the CRSF's identifier and address information to the AMF.

[0122] 4. AMF sends a request to CRSF to register for computing power services for the medical edge cloud.

[0123] 5. After completing the registration of the medical edge cloud computing power service, CRSF sends a response message to AMF. Then, AMF forwards the computing power service registration response message to 5G-RG and 5G-RG to the medical edge cloud.

[0124] This embodiment is recommended for scenarios where operators do not support network capability openness. Since some operators have not opened their network capabilities, this embodiment is independent of the operator's network capability openness policy. In this embodiment, the medical edge cloud only needs local access to 5G-RG and does not need to connect to the network capability openness platform via the external network, thus ensuring high security.

[0125] In the embodiment of registration via network capability openness, where the type of computing resource node is a computing resource node of an industry customer (such as a hospital), receiving the computing service registration request from the computing resource node includes:

[0126] The system receives a computing power service registration request from a third network element, which is a network capability open network element. The third network element queries the second network element to obtain the address of the first network element based on the identifier of the computing power resource node cluster.

[0127] like Figure 9 As shown, Figure 9 This is a schematic diagram of a computing power service registration process provided by an embodiment of the present invention. The process is described as follows:

[0128] 1. The medical edge cloud sends a computing power service registration request to NEF, carrying information including but not limited to: computing power node type (identified as medical edge cloud), medical edge cloud ID, medical edge cloud location information, medical consortium ID, computing power service duration, and computing power resource type (such as GPU, CPU, storage, etc.).

[0129] 2. The NEF queries the NRF for the CRSF corresponding to the medical consortium, carrying information including at least the medical consortium ID; the NRF queries the CRSF corresponding to the medical consortium that meets the requirements based on the CRSF's registration information, and sends the CRSF's identifier and address information to the NEF.

[0130] 3. NEF sends a request to CRSF to register for computing power services for the medical edge cloud.

[0131] 4. After completing the registration of the medical edge cloud computing service, CRSF sends a response message to NEF.

[0132] 5. NEF forwards the computing power service registration response information to the medical edge cloud.

[0133] In scenarios where operators open up network capabilities, this embodiment is recommended. For 5GC, the technical solution in this embodiment only has functional requirements for NEF, and NEF upgrades do not affect existing network services; therefore, the impact on 5GC is minimal. The technical solution in this embodiment has no functional requirements for 5G-RG and will not affect the scope of 5G-RG procurement by customers.

[0134] After registering its computing power service with CRSF, the Medical Edge Cloud will report its computing power resource information to CRSF in real time. The information carried includes, but is not limited to, the Medical Edge Cloud ID, the total amount and utilization rate of various types of computing power resources provided by the Medical Edge Cloud, and the Medical Consortium ID.

[0135] Reporting paths: The reporting path via the control plane is Medical Edge Cloud -> 5G-RG -> W-AGF / RAN -> AMF -> CRSF; the reporting path via network capability opening is Medical Edge Cloud -> NEF -> CRSF.

[0136] Reporting methods include, but are not limited to, scheduled reporting and reporting when the total amount of resources or the utilization rate changes beyond a certain threshold.

[0137] When a hospital or medical institution within a medical consortium lacks sufficient computing resources, it can submit a computing resource request to the CRSF (Comprehensive Response System), which will then allocate the corresponding computing resources for its use. This can be achieved through two implementation methods: requesting through the control plane and requesting through network capability openness.

[0138] In the embodiment where the request is made via the control plane, receiving the first computing resource request includes:

[0139] The system receives a first computing resource request sent by a fifth network element, which is a control plane network element. The fifth network element obtains the address of the first network element from the second network element based on the identifier of the computing resource node cluster.

[0140] The fifth network element is the AMF network element. Figure 10 This is a schematic diagram of a computing power service request process provided by an embodiment of the present invention. The process is described as follows:

[0141] 1. The computing power demander (the medical edge cloud of a hospital or medical institution) sends a computing power resource application request to 5G-RG, carrying information including but not limited to: application security level, medical edge cloud ID, medical alliance ID, medical edge cloud location information, type of computing power resource requested (such as GPU, CPU, storage, etc.), and quantity of computing power resource requested.

[0142] 2. 5G-RG forwards computing resource application requests to AMF via W-AGF or RAN.

[0143] 3. The AMF queries the NRF for the CRSF corresponding to the medical consortium, carrying information including at least the medical consortium ID.

[0144] 4. Based on the CRSF's registration information, NRF queries the CRSF corresponding to the medical consortium that meets the requirements, and sends the CRSF's identifier and address information to AMF.

[0145] 5. AMF sends a request for computing resources for the medical edge cloud to CRSF.

[0146] 6. CRSF determines the computing power resource provider in the following way: Based on the application security level reported by the computing power requester, and according to the correspondence between the computing power node type and the application security level in the computing power resource scheduling strategy, and the preferred computing power node type, the type of computing power resource provider (edge ​​computing power node or medical edge cloud) is determined; the computing power resource provider is determined according to the computing power node selection strategy corresponding to the computing power node type in the computing power resource scheduling strategy; for example: the application security level reported by the computing power requester is "normal", while the computing power node type corresponding to the application security level of "normal" in the computing power resource scheduling strategy configured locally by CRSF is "edge computing power node", and the computing power node selection strategy corresponding to the edge computing power node is "distance priority".

[0147] 7. CRSF sends a computing resource application request to the selected computing resource provider, requesting the allocation of the corresponding computing resources.

[0148] 8. After allocating computing resources, the computing resource provider sends a computing resource request response message to CRSF, carrying information including but not limited to: computing resource access address information, computing resource type and quantity.

[0149] 9. The CRSF sends a response message to the AMF, carrying information including but not limited to: computing power provider ID, computing power provider type, computing power resource access address information, and computing power resource type and quantity. Then, the AMF forwards the computing power resource request response message to 5G-RG, and 5G-RG forwards it to the medical edge cloud.

[0150] The process by which CRSF determines the computing resource provider is as follows: Figure 11 As shown, it includes:

[0151] 1. The application security level reported by the demand side is "low".

[0152] 2. Based on the strategy, the type of computing power provider is the operator's edge computing power node.

[0153] 3. The selection strategy for edge computing node types is "distance priority".

[0154] 4. Obtain the location information of the medical edge cloud provided by the computing power demander.

[0155] 5. From the registered MECs that provide computing power services, select the MEC with available computing power resources that is closest to the medical edge cloud and use it as the computing power provider.

[0156] In the embodiment of applying for network capability access, receiving the first computing resource request includes:

[0157] The system receives a first computing resource request from a third network element, which is a network capability open network element. The third network element obtains the address of the first network element from the second network element based on the identifier of the medical consortium.

[0158] The third network element is the NEF network element. Figure 12 This is a schematic diagram of another computing power service request process provided by an embodiment of the present invention. The process is described as follows:

[0159] 1. The computing power requester (the medical edge cloud of a hospital or medical institution) sends a computing power resource application request to NEF, carrying information including but not limited to: application security level, medical edge cloud ID, medical alliance ID, medical edge cloud location information, type of computing power resource requested (such as GPU, CPU, storage, etc.), and quantity of computing power resource requested.

[0160] 2. NEF queries NRF for the CRSF corresponding to the medical consortium, carrying information including at least the medical consortium ID.

[0161] 3. Based on the CRSF's registration information, NRF queries the CRSF corresponding to the medical consortium that meets the requirements, and sends the CRSF's identifier and address information to NEF.

[0162] 4. NEF sends a request for computing resources for the medical edge cloud to CRSF.

[0163] 5. CRSF determines the computing power resource provider; the determination method is as follows: Figure 11 As described in the examples.

[0164] 6. CRSF sends a computing resource application request to the selected computing resource provider, requesting the allocation of the corresponding computing resources.

[0165] 7. After allocating computing resources, the computing resource provider sends a computing resource request response message to CRSF, carrying information including but not limited to: computing resource access address information, computing resource type and quantity.

[0166] 8. CRSF sends a response message to NEF, carrying information including but not limited to: computing power provider ID, computing power provider type, computing power resource access address information, computing power resource type and quantity; then NEF forwards the computing power resource application response message to the medical edge cloud.

[0167] Specifically, if the medical edge cloud registers computing power services with CRSF through control, it is also recommended that computing power demanders apply for computing power resources with CRSF through control; if the medical edge cloud registers computing power services with CRSF through network capability openness, it is also recommended that computing power demanders apply for computing power resources with CRSF through network capability openness.

[0168] In one embodiment, the first computing resource request includes an application security level, the preset computing resource scheduling strategy includes a correspondence between the application security level and the computing resource node type, and the step of determining the target computing resource node in the computing resource node cluster that provides computing resources to the computing resource requester according to the preset computing resource scheduling strategy includes:

[0169] Based on the application security level, the type of the target computing resource node is determined.

[0170] For example, in the healthcare industry, due to extremely high requirements for privacy data protection, some core applications and sensitive data cannot be deployed on external computing nodes. Therefore, a mechanism for unified scheduling of internal and external computing resources is needed to meet the needs of applications with different security levels. This embodiment determines the type of computing power provider based on the application security level reported by the computing power requester, according to the correspondence between computing node types and application security levels in the computing power resource scheduling strategy. For example, for a low security level, the corresponding computing power provider type is a hospital or medical institution's medical edge cloud; for a high security level, the corresponding computing power provider type is an operator's edge computing node.

[0171] In one embodiment, after sending the second computing resource request to the target computing resource node, the method further includes:

[0172] Receive a response message sent by the target computing resource node, the response message including the computing resource access address;

[0173] The response message is sent to the requester of the computing resources.

[0174] After requesting computing resources, the requester sends a message to the 5G-RG with the destination address being the access address of the requested computing resources, triggering the 5G-RG to create a corresponding PDU session.

[0175] If the computing power provider type is MEC, then create a 5G-RG to MEC corresponding UPF PDU session;

[0176] If the computing power provider type is medical edge cloud, then create a 5G LAN type PDU session to the corresponding medical edge cloud;

[0177] If the corresponding PDU session already exists, there is no need to create it again; the existing PDU session can be used.

[0178] This application embodiment leverages a 5G network to create a medical consortium. It adds network elements within the 5GC (5G Global Center) to uniformly schedule computing resources from operators and healthcare clients, providing flexible computing power to consortium members on demand. This embodiment achieves unified scheduling of computing resources from operators and clients through the 5G system. Furthermore, based on policies, it ensures that computing resources are scheduled considering factors such as resource utilization, application security, and the distance between computing nodes, resulting in more efficient, secure, and rational use of computing resources within the medical consortium.

[0179] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0180] It should be understood that, when used in this specification and the appended claims, the terms "comprising" and "including" indicate the presence of the described features, integrals, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or collections thereof.

[0181] It should be noted that the technical solutions described in the embodiments of the present invention can be combined arbitrarily without conflict.

[0182] In addition, in the embodiments of the present invention, "first," "second," etc. are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0183] This invention provides a computing resource scheduling device, which includes:

[0184] The receiving module is used to receive a first computing resource request, wherein the first computing resource request includes the identifier of the computing resource node cluster to which the computing resource requester is located; the computing resource node cluster includes computing resource nodes of industry customers and operators;

[0185] The determination module is used to determine the target computing resource node in the computing resource node cluster that provides computing resources to the computing resource requester, according to a preset computing resource scheduling strategy.

[0186] The sending module is used to send a second computing resource request to the target computing resource node so that the target computing resource node can allocate corresponding computing resources.

[0187] In one embodiment, the device further includes:

[0188] The registration module is used to send a registration request to the second network element. The registration request includes the identifier of the first network element, the address of the first network element, and the identifier of the computing power resource node cluster.

[0189] In one embodiment, the receiving module is further configured to:

[0190] The third network element receives the computing resource scheduling strategy sent by the third network element; the third network element queries the address of the first network element from the second network element based on the identifier of the computing resource node cluster.

[0191] In one embodiment, the receiving module is further configured to:

[0192] Receive a computing power service registration request from a computing power resource node. The computing power service registration request includes the identifier of the computing power resource node cluster to which the computing power resource node belongs and the type of the computing power resource node.

[0193] In one embodiment, the receiving module is further configured to:

[0194] Receive computing resource information reported by the computing resource nodes.

[0195] In one embodiment, when the type of the computing power resource node is an operator's computing power resource node, the receiving module is specifically used for:

[0196] The fourth network element receives a computing power service registration request from the computing power resource node sent by the fourth network element. The fourth network element then queries the address of the first network element from the second network element based on the identifier of the computing power resource node cluster.

[0197] In one embodiment, when the type of the computing power resource node is an industry customer's computing power resource node, the receiving module is specifically used for:

[0198] The system receives a computing power service registration request from the computing power resource node sent by the fifth network element. The computing power resource node sends the computing power service registration request through the fifth network element, which is a control plane network element. The fifth network element queries the address of the first network element from the second network element based on the identifier of the computing power resource node cluster.

[0199] In one embodiment, when the type of the computing power resource node is an industry customer's computing power resource node, the receiving module is specifically used for:

[0200] The system receives a computing power service registration request from a third network element, which is a network capability open network element. The third network element queries the second network element to obtain the address of the first network element based on the identifier of the computing power resource node cluster.

[0201] In one embodiment, the receiving module is specifically used to: receive a first computing resource request sent by a fifth network element, wherein the fifth network element is a control plane network element, and the fifth network element obtains the address of the first network element from the second network element based on the identifier of the computing resource node cluster.

[0202] In one embodiment, the receiving module is specifically used to: receive a first computing resource request sent by a third network element, wherein the third network element is a network capability open network element, and the third network element obtains the address of the first network element from the second network element according to the identifier of the computing resource node cluster.

[0203] In one embodiment, the first computing resource request includes an application security level, the preset computing resource scheduling strategy includes a correspondence between the application security level and the computing resource node type, and the determining module is specifically used for:

[0204] Based on the application security level, the type of the target computing resource node is determined.

[0205] In one embodiment, the device further includes:

[0206] A response message receiving module is used to receive a response message sent by the target computing power resource node, the response message including the computing power resource access address;

[0207] The response message sending module is used to send the response message to the computing resource requester.

[0208] In practical applications, the receiving module, determining module, and transmitting module can be implemented by processors in the network element, such as central processing unit (CPU), digital signal processor (DSP), microcontroller unit (MCU), or field-programmable gate array (FPGA).

[0209] It should be noted that the computing resource scheduling device provided in the above embodiments is only illustrated by the division of the above modules when performing computing resource scheduling. In actual applications, the above processing can be assigned to different modules as needed, that is, the internal structure of the device can be divided into different modules to complete all or part of the processing described above. In addition, the computing resource scheduling device and the computing resource scheduling method embodiments provided in the above embodiments belong to the same concept, and the specific implementation process can be found in the method embodiments, which will not be repeated here.

[0210] The aforementioned computing resource scheduling device can be in the form of an image file. After execution, the image file can run as a container or virtual machine to implement the computing resource scheduling method described in this application. However, it is not limited to the image file format; any software implementation capable of the computing resource scheduling method described in this application is within the scope of protection of this application.

[0211] Based on the hardware implementation of the above program modules, and in order to implement the method of the embodiments of this application, the embodiments of this application also provide a network element, wherein the above computing resource scheduling method is implemented by the processor of the network element.

[0212] Figure 13 This is a schematic diagram of the hardware composition structure of the network element in an embodiment of this application, as shown below. Figure 13 As shown, the network elements include:

[0213] The communication interface 1301 enables information exchange with other devices, such as network devices.

[0214] The processor 1302 is connected to the communication interface 1301 to enable information interaction with other devices and, when running a computer program, executes the methods provided by one or more of the aforementioned network element-side technical solutions. The computer program is stored in the memory 1303.

[0215] Of course, in practical applications, the various components in the network element are coupled together through the bus system 1304. It can be understood that the bus system 1304 is used to realize the connection and communication between these components. In addition to the data bus, the bus system also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, in... Figure 13 The general designated all buses as Bus System 1304.

[0216] The memory 1303 in this embodiment is used to store various types of data to support the operation of the network element. Examples of such data include any computer program used to operate on the network element.

[0217] In this application, a network element can be a single hardware device or a cluster of multiple hardware devices, such as a cloud computing platform. A cloud computing platform is a cluster device that organizes multiple independent network element physical hardware resources into a pooled resource, providing the necessary virtual resources and services to the outside world.

[0218] The memory 1303 in this embodiment is used to store various types of data to support the operation of the network element. Examples of such data include any computer program used to operate on the network element.

[0219] It is understood that memory 1303 can be volatile memory or non-volatile memory, or both. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), ferromagnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disc, or compact disc read-only memory (CD-ROM); magnetic surface memory can be disk storage or magnetic tape storage. Volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), SyncLink Dynamic Random Access Memory (SLDRAM), and Direct Rambus Random Access Memory (DRRAM).The memories described in the embodiments of this application are intended to include, but are not limited to, these and any other suitable types of memories.

[0220] The methods disclosed in the embodiments of this application can be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor may be a general-purpose processor, a DSP, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The processor can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. A general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of this application can be directly manifested as execution by a hardware decoding processor, or execution by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium, which is located in memory. The processor reads the program from the memory and, in conjunction with its hardware, completes the steps of the aforementioned method.

[0221] In an exemplary embodiment, this application also provides a computer program product, including a computer program that can be executed by the processor 1302 of a network element to complete the steps of the computing resource scheduling method described in this application embodiment.

[0222] Optionally, when the processor executes the program, it implements the corresponding processes implemented by the network element in the various methods of the embodiments of this application. For the sake of brevity, these will not be described in detail here.

[0223] In an exemplary embodiment, this application also provides a storage medium, namely a computer storage medium, specifically a computer-readable storage medium, such as a first memory storing a computer program, which can be executed by a processor of a network element to complete the steps described in the aforementioned method. The computer-readable storage medium may be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface memory, optical disc, or CD-ROM.

[0224] In the several embodiments provided in this application, it should be understood that the disclosed devices, network elements, and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods, such as: multiple units or components can be combined, or integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the various components shown or discussed can be through some interfaces, and the indirect coupling or communication connection between devices or units can be electrical, mechanical, or other forms.

[0225] The units described above as separate components may or may not be physically separate. 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 the units may be selected to achieve the purpose of this embodiment according to actual needs.

[0226] In addition, each functional unit in the various embodiments of this application can be integrated into one processing unit, or each unit can be a separate unit, or two or more units can be integrated into one unit; the integrated unit can be implemented in hardware or in the form of hardware plus software functional units.

[0227] Those skilled in the art will understand that all or part of the steps of the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it performs the steps of the above method embodiments. The aforementioned storage medium includes various media that can store program code, such as mobile storage devices, ROM, RAM, magnetic disks, or optical disks.

[0228] Alternatively, if the integrated units described above are implemented as software functional modules and sold or used as independent products, they can also be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, or the parts that contribute to related technologies, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, network element, or network device, etc.) to execute all or part of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as mobile storage devices, ROM, RAM, magnetic disks, or optical disks.

[0229] It should be noted that the technical solutions described in the embodiments of this application can be combined arbitrarily without conflict.

[0230] In addition, in this application example, terms such as "first" and "second" are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0231] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A computing resource scheduling method, applied to a first network element, and having the characteristics that, The method comprises: receiving a first computing power resource request, the first computing power resource request comprising an identifier of a computing power resource node cluster to which a computing power resource requester belongs; the computing power resource node cluster comprising computing power resource nodes of industry customers and operators; determining, according to a preset computing power resource scheduling strategy, a target computing power resource node in the computing power resource node cluster for providing computing power resources for the computing power resource requester; sending a second computing power resource request to the target computing power resource node, so that the target computing power resource node allocates corresponding computing power resources.

2. The method of claim 1, wherein, Before receiving the first computing power resource request, the method further comprises: sending a registration request to a second network element, the registration request comprising an identifier of the first network element, an address of the first network element, and an identifier of the computing power resource node cluster.

3. The method of claim 2, wherein, The method further comprises: receiving the computing power resource scheduling strategy sent by a third network element; the third network element obtains the address of the first network element from the second network element according to the identifier of the computing power resource node cluster.

4. The method of claim 2, wherein, Before receiving the first computing power resource request, the method further comprises: receiving a computing power service registration request of a computing power resource node, the computing power service registration request comprising an identifier of a computing power resource node cluster to which the computing power resource node belongs and a type of the computing power resource node.

5. The method of claim 4, wherein, After receiving the computing power service registration request of the computing power resource node, the method further comprises: receiving computing power resource information reported by the computing power resource node.

6. The method of claim 4, wherein, In the case that the type of the computing power resource node is an operator's computing power resource node, the receiving of the computing power service registration request of the computing power resource node comprises: receiving the computing power service registration request of the computing power resource node sent by a fourth network element, the fourth network element obtaining the address of the first network element from the second network element according to the identifier of the computing power resource node cluster.

7. The method of claim 4 wherein, In the case that the type of the computing power resource node is an industry customer's computing power resource node, the receiving of the computing power service registration request of the computing power resource node comprises: receiving the computing power service registration request of the computing power resource node sent by a fifth network element, the computing power resource node sending the computing power service registration request through the fifth network element, the fifth network element being a control plane network element, and the fifth network element obtaining the address of the first network element from the second network element according to the identifier of the computing power resource node cluster.

8. The method of claim 7, wherein, In the case that the type of the computing power resource node is an industry customer's computing power resource node, the receiving of the computing power service registration request of the computing power resource node comprises: receiving the computing power service registration request of the computing power resource node sent by a third network element, the computing power resource node sending the computing power service registration request through the third network element, the third network element being a network capability exposure network element, and the third network element obtaining the address of the first network element from the second network element according to the identifier of the computing power resource node cluster.

9. The method of claim 2, wherein, The receiving of the first computing power resource request comprises: receive a first computing resource request sent by a fifth network element, the fifth network element being a control plane network element, and the fifth network element obtaining the address of the first network element from the second network element according to the identifier of the computing resource node cluster.

10. The method of claim 2, wherein, The receiving the first computing resource request comprises: receive a first computing resource request sent by a third network element, the third network element being a network capability exposure network element, and the third network element obtaining the address of the first network element from the second network element according to the identifier of the computing resource node cluster.

11. The method of claim 1, wherein, The first computing resource request comprises an application security level, the preset computing resource scheduling strategy comprises a corresponding relationship between an application security level and a computing resource node type, and the determining, according to the preset computing resource scheduling strategy, of a target computing resource node in the computing resource node cluster for providing computing resource for the computing resource request party comprises: determining the type of the target computing resource node based on the application security level.

12. The method of claim 1, wherein, After the sending of the second computing resource request to the target computing resource node, the method further comprises: receiving a response message sent by the target computing resource node, the response message comprising a computing resource access address; sending the response message to the computing resource request party.

13. A network element, characterized by comprise: a processor and a memory for storing a computer program capable of running on the processor, wherein the processor is configured to execute the steps of the computing resource scheduling method according to any one of claims 1 to 11 when running the computer program.

14. A computer storage medium having stored thereon a computer program, characterized in that The computer program is executed by the processor to implement the steps of the computing resource scheduling method according to any one of claims 1 to 12.

15. A computer program product comprising a computer program, characterized in that, The computer program is executed by the processor to implement the steps of the computing resource scheduling method according to any one of claims 1 to 12. The computer program is executed by the processor to implement the steps of the computing resource scheduling method according to any one of claims 1 to 12.

Images