Computing power resource scheduling method and apparatus for open radio access network, and storage medium

Abstract

The present application relates to a computing power resource scheduling method and apparatus for an open radio access network, and a storage medium. The method comprises: receiving a first subscription request sent by a computing power scheduler, wherein the first subscription request is used for subscribing to functional unit performance information; in response to the first subscription request, acquiring performance information of functional units managed by means of an open cloud; and sending the performance information to the computing power scheduler, wherein the performance information is used for computing power resource scheduling.

Description

Method, device and storage medium for scheduling computing power resources of open radio access network

[0001] The present application claims priority to the Chinese patent application No. 2024105364807, filed on April 30, 2024, and entitled "Method, device and storage medium for scheduling computing power resources of open radio access network", the contents of which are hereby incorporated by reference in their entirety. TECHNICAL FIELD

[0002] The present application relates to the field of communication technology, in particular to a method, device and storage medium for scheduling computing power resources of open radio access network. BACKGROUND

[0003] With the rapid growth of mobile communication traffic, mobile networks and the devices and maintenance operations thereof need to reduce costs and improve efficiency, which urgently requires the virtualization of devices, resource sharing, flexibility, intelligence and energy saving. In particular, the access network part, the new generation of network needs to be more open and intelligent than the previous generations, and the open radio access network (ORAN) emerges as the times require. ORAN has the characteristics of software, virtualization, flexibility, and intelligence. ORAN adopts open and standardized interfaces, virtualized network elements, open source software, and a unified hardware reference framework.

[0004] In the traditional technology, the open cloud platform (O-Cloud) is a set of hardware and software components that provide cloud computing capabilities and services to execute network functions of ORAN to meet the computing power requirements of ORAN. However, the O-Cloud cannot meet the computing power requirements of the computing power scheduling party outside the ORAN. SUMMARY

[0005] According to various embodiments of the present application, a method, device and storage medium for scheduling computing power resources of open radio access network are provided.

[0006] In a first aspect, the present application provides a method for scheduling computing power resources of open radio access network, comprising:

[0007] receiving a first subscription request sent by a computing power scheduling party, the first subscription request being used to subscribe to function unit performance information;

[0008] in response to the first subscription request, obtaining performance information of a function unit managed by an open cloud platform;

[0009] sending the performance information to the computing power scheduling party, the performance information being used for computing power resource scheduling.

[0010] In one embodiment, in response to the first subscription request, the performance information of the function unit managed by the open cloud platform comprises:

[0011] In response to the first subscription request, a second subscription request is sent to a management service unit of the open cloud platform, the second subscription request being used to request the management service unit to report performance information;

[0012] The performance information sent by the management service unit in response to the second subscription request is received.

[0013] In one embodiment, the performance information is reported through an O1 interface or an O2 interface.

[0014] In one embodiment, the performance information is reported periodically or in the case where a preset triggering condition is met.

[0015] In one embodiment, the method further comprises:

[0016] A first resource scheduling request sent by a computing power scheduling party is received, the first resource scheduling request being used to adjust a first functional unit of the open cloud platform from being deployed on a first node of the open cloud platform to being deployed on a second node of the open cloud platform;

[0017] In response to the first resource scheduling request, the service data routing of the first functional unit is transferred from the first node to the second node;

[0018] A notification of successful node change is sent to the computing power scheduling party.

[0019] In one embodiment, the method further comprises:

[0020] In the case where the service data routing of the first functional unit is completed, a management service unit of the open cloud platform is notified to release the computing power resources occupied by the first functional unit on the first node.

[0021] In one embodiment, the method further comprises:

[0022] A second resource scheduling request sent by the computing power scheduling party is received, the second resource scheduling request being used to adjust the scale of a second functional unit of the open cloud platform;

[0023] In response to the second resource scheduling request, the scale of the second functional unit is reduced or expanded;

[0024] A notification of successful scale adjustment is sent to the computing power scheduling party.

[0025] In one embodiment, the functional units managed by the open cloud platform are deployed on K8s type nodes and / or ETSI type nodes.

[0026] In one embodiment, the method further comprises:

[0027] In a case where the second subscription confirmation message sent by the management service unit is received, a first subscription confirmation message is sent to the computing power scheduler, and the second subscription confirmation message indicates that the management service unit has received the second subscription request.

[0028] In one embodiment, the computing power scheduler comprises:

[0029] a non-proximal wireless intelligent controller application (rAPP) or an external computing power scheduling client.

[0030] In a second aspect, the present application provides a computing power resource scheduling device of an open wireless access network, comprising a memory, a transceiver, and a processor:

[0031] The memory is configured to store a computer program; the transceiver is configured to transceive data under the control of the processor; and the processor is configured to read the computer program in the memory and perform the following operations:

[0032] receiving a first subscription request sent by a computing power scheduler, the first subscription request being used to subscribe to performance information of a functional unit;

[0033] in response to the first subscription request, obtaining performance information of a functional unit managed by an open cloud platform;

[0034] sending the performance information to the computing power scheduler, the performance information being used for computing power resource scheduling.

[0035] In one embodiment, in response to the first subscription request, the performance information of the functional unit managed by the open cloud platform is obtained, comprising:

[0036] in response to the first subscription request, sending a second subscription request to a management service unit of the open cloud platform, the second subscription request being used to request the management service unit to report the performance information;

[0037] receiving the performance information sent by the management service unit in response to the second subscription request.

[0038] In one embodiment, the performance information is reported through an O1 interface or an O2 interface.

[0039] In one embodiment, the performance information is reported periodically or in a case where a preset triggering condition is met.

[0040] In one embodiment, the processor is further configured to perform the following operations:

[0041] receiving a first resource scheduling request sent by a computing power scheduler, the first resource scheduling request being used to adjust a first functional unit of the open cloud platform from being deployed on a first node of the open cloud platform to being deployed on a second node of the open cloud platform;

[0042] In response to the first resource scheduling request, the service data of the first function unit is transferred from the first node to the second node;

[0043] A notification of successful node change is sent to the computing power scheduling party.

[0044] In one embodiment, the processor is further configured to perform the following operations:

[0045] In the case where the service data routing of the first function unit is completed, the management service unit of the open cloud platform is notified to release the computing power resources occupied by the first function unit on the first node.

[0046] In one embodiment, the processor is further configured to perform the following operations:

[0047] A second resource scheduling request sent by the computing power scheduling party is received, and the second resource scheduling request is used to adjust the scale of the second function unit of the open cloud platform;

[0048] In response to the second resource scheduling request, the scale of the second function unit is reduced or expanded;

[0049] A notification of successful scale adjustment is sent to the computing power scheduling party.

[0050] In one embodiment, the function units managed by the open cloud platform are deployed on K8s type nodes and / or ETSI type nodes.

[0051] In one embodiment, the processor is further configured to perform the following operations:

[0052] In the case where the second subscription confirmation message sent by the management service unit is received, a first subscription confirmation message is sent to the computing power scheduling party, and the second subscription confirmation message indicates that the management service unit has received the second subscription request.

[0053] In one embodiment, the computing power scheduling party includes:

[0054] A non-close-end wireless intelligent controller application rAPP or an external computing power scheduling client.

[0055] In a third aspect, the present application provides a computing power resource scheduling device of an open wireless access network, comprising:

[0056] A first receiving unit is configured to receive a first subscription request sent by a computing power scheduling party, and the first subscription request is used to subscribe to function unit performance information;

[0057] A first response unit is configured to acquire performance information of function units managed by an open cloud platform in response to the first subscription request;

[0058] A first sending unit is configured to send the performance information to the computing power scheduling party, and the performance information is used for computing power resource scheduling.

[0059] In one embodiment, the first response unit is configured to:

[0060] In response to the first subscription request, send a second subscription request to a management service unit of the open cloud platform, the second subscription request being configured to request the management service unit to report performance information;

[0061] Receive the performance information sent by the management service unit in response to the second subscription request.

[0062] In one embodiment, the performance information is reported through an O1 interface or an O2 interface.

[0063] In one embodiment, the performance information is reported periodically or when a preset triggering condition is met.

[0064] In one embodiment, the apparatus further comprises:

[0065] The second receiving unit is configured to receive a first resource scheduling request sent by a computing power scheduler, the first resource scheduling request being configured to adjust a first function unit of the open cloud platform from being deployed on a first node of the open cloud platform to being deployed on a second node of the open cloud platform;

[0066] The second response unit is configured to, in response to the first resource scheduling request, route service data of the first function unit from the first node to the second node;

[0067] The second sending unit is configured to send a notification of successful node change to the computing power scheduler.

[0068] In one embodiment, the apparatus further comprises:

[0069] The first notification unit is configured to, in a case where the routing of the service data of the first function unit is completed, notify a management service unit of the open cloud platform to release computing power resources occupied by the first function unit on the first node.

[0070] In one embodiment, the apparatus further comprises:

[0071] The third receiving unit is configured to receive a second resource scheduling request sent by the computing power scheduler, the second resource scheduling request being configured to adjust a scale of a second function unit of the open cloud platform;

[0072] The third response unit is configured to, in response to the second resource scheduling request, reduce or expand the scale of the second function unit;

[0073] The second notification unit is configured to send a notification of successful scale adjustment to the computing power scheduler.

[0074] In an embodiment, the function unit managed by the open cloud platform is deployed on a K8s type node and / or an ETSI type node.

[0075] In an embodiment, the apparatus further comprises:

[0076] The third sending unit is configured to send, to the computing power scheduler, the first subscription confirmation message in a case where the second subscription confirmation message sent by the management service unit is received, the second subscription confirmation message indicating that the management service unit has received the second subscription request.

[0077] In an embodiment, the computing power scheduler comprises:

[0078] A non-proximal wireless intelligent controller application (rAPP) or an external computing power scheduling client.

[0079] In a fourth aspect, the present application further provides a computer device comprising a memory and a processor, the memory storing a computer program, and the processor implementing the open radio access network computing power resource scheduling method of the first aspect or any one of the embodiments of the first aspect when executing the computer program.

[0080] In a fifth aspect, the present application further provides a computer readable storage medium having a computer program stored thereon, the computer program being executed by a processor to implement the open radio access network computing power resource scheduling method of the first aspect or any one of the embodiments of the first aspect.

[0081] In a sixth aspect, the present application further provides a computer program product comprising a computer program, the computer program being executed by a processor to implement the open radio access network computing power resource scheduling method of the first aspect or any one of the embodiments of the first aspect.

[0082] The details of one or more embodiments of the present application are set forth in the accompanying drawings and the description below. Other features, objects, and advantages of the present application will be apparent from the description and drawings, and from the claims. BRIEF DESCRIPTION OF DRAWINGS

[0083] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related art, the drawings needed to be used in the embodiments or the related art description will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without any creative effort on the basis of these drawings.

[0084] FIG. 1 is an application environment diagram of the open radio access network computing power resource scheduling method in one or more embodiments;

[0085] FIG. 2 shows an ORAN architecture diagram;

[0086] FIG. 3 is a flow diagram of a method of scheduling computing resources of an open radio access network, according to one or more embodiments;

[0087] FIG. 4 is an interaction flow diagram of a method of scheduling computing resources of an open radio access network, according to one or more embodiments;

[0088] FIG. 5 illustrates an exemplary coverage diagram of an open radio access network;

[0089] FIG. 6 is an interaction flow diagram of a method of scheduling computing resources of an open radio access network, according to one or more embodiments;

[0090] FIG. 7 is an interaction flow diagram of a method of scheduling computing resources of an open radio access network, according to one or more embodiments;

[0091] FIG. 8 is a block diagram of a device for scheduling computing resources of an open radio access network, according to one or more embodiments;

[0092] FIG. 9 is a block diagram of a device for scheduling computing resources of an open radio access network, according to one or more embodiments. DETAILED DESCRIPTION

[0093] The term “and / or” in the embodiments of the present application describes the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B can represent the following three cases: A exists alone, A and B exist together, and B exists alone. The character “ / ” generally represents that the associated objects before and after it are in an “or” relationship.

[0094] The term “multiple” in the embodiments of the present application means two or more, and the meaning of the quantifier connected after “multiple” is similar.

[0095] The technical solutions in the embodiments of the present application will be described clearly and completely below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, not all. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative labor are within the scope of protection of the present application.

[0096] In the related work of open radio access network (ORAN) edge computing, an application programming interface (API) is defined for service management and orchestration (SMO) to orchestrate and manage an open cloud (O-Cloud). However, the traditional technology does not involve the scheduling of computing resources of the O-Cloud by the computing resource scheduling party outside the ORAN, so that the O-Cloud cannot meet the computing resource demand of the computing resource scheduling party outside the ORAN.

[0097] The embodiments of the present application provide an open radio access network computing resource scheduling method and device, which provide the performance information of each functional unit managed by the open cloud platform for the computing resource scheduling party outside the ORAN, so that the computing resource scheduling party outside the ORAN can use the performance information of each functional unit managed by the open cloud platform to schedule the computing resource, thereby meeting the computing resource demand of the computing resource scheduling party outside the ORAN. Further, the open radio access network computing resource scheduling method and device provided by the embodiments of the present application can provide the performance information of each functional unit managed by the open cloud platform for the computing resource scheduling party outside the ORAN through the SMO of the RAN, thereby assisting the computing resource scheduling party outside the ORAN to schedule the computing resource, meeting the computing resource demand, fully utilizing the edge computing resource of the open cloud platform, and better providing edge computing service for edge computing service.

[0098] The method and the device are based on the same application concept. Since the principles of the method and the device for solving problems are similar, the implementation of the device and the method can be mutually referred to, and the repeated parts will not be described again.

[0099] The open radio access network computing resource scheduling method provided by the embodiments of the present application can be applied in an application environment as shown in FIG. 1. As shown in FIG. 1, the application environment includes a computing resource scheduling party, an SMO, and an O-Cloud. The computing resource scheduling party can be a non-near RIC application (rAPP) or an external computing resource scheduling client. The computing resource scheduling party and the SMO communicate data through a wireless system, and the SMO and the O-Cloud can communicate data through the interface (such as O1 interface and O2 interface) of the ORAN. The O-Cloud can include a management service unit and multiple nodes (such as node 1 to node n, n represents the number of nodes). The O-Cloud will be described in detail below, and will not be described again here.

[0100] The technical solutions provided by the embodiments of the present application can be applied to various systems. For example, the applicable systems can be a long term evolution (LTE) system, an LTE frequency division duplex (FDD) system, an LTE time division duplex (TDD) system, a long term evolution advanced (LTE-A) system, a universal mobile system (UMTS), a worldwide interoperability for microwave access (WiMAX) system, a 5G new radio (NR) system, and an evolved communication system thereof. The various systems can include terminal devices and network devices. The system can also include a core network part, such as an evolved packet system (EPS), a 5G system (5GS), and the like.

[0101] The terminal device involved in the embodiments of the present application can refer to a device providing voice and / or data connectivity for a user, a handheld device with wireless connection function, or other processing devices connected to a wireless modem, etc. In different systems, the name of the terminal device can also be different, for example, in the 5G system, the terminal device can be called user equipment (UE). The wireless terminal device can be a USB storage device, other personal computer memory devices and a dongle, and can also communicate with one or more core networks (CN) through a radio access network (RAN). The wireless terminal device can be a mobile terminal device, such as a mobile phone (or called "cellular" phone) and a computer with a mobile terminal device, for example, it can be a portable, pocket-sized, handheld, computer-built-in or vehicle-mounted mobile device, which exchanges language and / or data with the radio access network. For example, personal communication service (PCS) phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), personal computers, tablet computers, machine-type communication (MTC) terminal devices, etc. The wireless terminal device can also be called a system, a subscriber unit, a subscriber station, a mobile station, a mobile, a remote station, an access point, a remote terminal, an access terminal, a user terminal, a user agent, a user device, and a wireless access device and a router / modem that meet the definition limit, etc. The embodiments of the present application are not limited.

[0102] The network device involved in the embodiments of the present application can be a base station, which can include multiple cells serving terminals. According to different application scenarios, the base station can also be referred to as an access point, or can be a device in an access network that communicates with wireless terminal devices through one or more sectors over an air interface, or other names. The network device can be used to exchange received air frames and Internet Protocol (IP) packets as a router between wireless terminal devices and the rest of the access network, which can include an Internet Protocol (IP) communication network. The network device can also coordinate the management of the properties of the air interface. For example, the network device involved in the embodiments of the present application can be an evolved network device (eNB or e-NodeB) in a long term evolution (LTE) system, a 5G base station (gNB) in a next generation system (5G network architecture), etc., and can also be a home evolved base station (HeNB), a relay node, a femto, a pico, a network test device, etc., which is not limited in the embodiments of the present application. In some network structures, the network device can include a centralized unit (CU) node and a distributed unit (DU) node, and the centralized unit and the distributed unit can also be arranged geographically apart.

[0103] The terminal device sends relevant information or the like to the network device in the embodiments of the present application, which only indicates that the terminal device sends relevant information in a wireless signal manner, and the intended recipient is the network device. The network device can obtain the relevant information by receiving the wireless signal.

[0104] ORAN adopts a three-layer architecture, from bottom to top, which is an operating platform, a network function and a management platform. FIG. 2 shows an ORAN architecture diagram.

[0105] As shown in FIG. 2, O-Cloud is used as a running platform in ORAN. O-Cloud is a cloud computing platform for deploying wireless network functions after general physical resources are clouded or virtualized by cloud technology. The underlying layer is composed of three parts, i.e., physical infrastructure nodes (such as general-purpose computers or special hardware platforms) meeting the requirements of O-RAN, cloud platform software, and O-RAN related management and orchestration functions. O-Cloud includes management service units such as infrastructure management services (IMS) and deployment management services (DMS), and also includes virtualized network functions (VNF) that can be dynamically deployed on O-Cloud nodes and applications (APP) that can be dynamically deployed on O-Cloud.

[0106] As shown in FIG. 2, SMO is used as a management platform in ORAN. O-Cloud can be connected to SMO through O2 interface (including O2ims interface and O2dms interface), so as to realize management of O-Cloud infrastructure, virtual network function (VNF) and other resources by SMO. Among them, SMO can set up and manage cloud platform deployment and resources through O2ims interface, and SMO can deploy and manage VNF through O2dms interface.

[0107] As shown in FIG. 2, the network functions of ORAN include near real-time (RT) RAN intelligent controller (RIC), O-RAN central unit controller plane (O-CU-CP), O-RAN central unit user plane (O-CU-UP), O-RAN distributed unit (O-DU) and O-RAN radio unit (O-RU) and other functions.

[0108] As shown in FIG. 2, O1 interface connects O-eNB to SMO and connects O-RU to SMO. That is, O-Cloud can be connected to SMO through O1 interface, so as to realize data transmission between SMO and O-Cloud.

[0109] It should be noted that other parts in the ORAN, such as the E1 interface, the E2 interface, and the Open Fronthaul M-Plane (OFH M-Plane) interface, the Open Fronthaul CUS-Plane (OFH CUS-Plane) interface, and the like shown in FIG. 2, and parts not shown in FIG. 2, can refer to related technologies, and will not be described herein.

[0110] In an exemplary embodiment, as shown in FIG. 3, a method for scheduling computing resources of an open radio access network is provided. The method is applied to the SMO in FIG. 1 or FIG. 2 as an example. As shown in FIG. 3, the method can include:

[0111] In step S301, a first subscription request sent by a computing resource scheduler is received.

[0112] The computing resource scheduler represents an object outside the ORAN that needs to be scheduled for computing resources. In an example, the computing resource scheduler can include a non-near radio intelligent controller application (Non-Near RIC APP, rAPP) or an external computing resource scheduling client. The rAPP is a modular application program that provides value-added services related to RAN control using the non-real-time RAN intelligent controller function of the SMO (see FIG. 2). The external computing resource scheduling client can be any client, terminal, or user equipment that needs to be scheduled for computing resources. The embodiments of the present application do not limit the computing resource scheduler.

[0113] In this step, the first subscription request can be used to subscribe to function unit performance information. The function unit can represent a unit for implementing network functions deployed in an open cloud platform. In an example, the function unit can include a VNF and / or an APP. The function unit performance information represents the performance information of the function unit. Accordingly, the performance information of the function unit can include the performance information of the VNF and / or the performance information of the APP. The open cloud platform in the ORAN can include multiple nodes, and one or more function units can be deployed on each node. That is, the open cloud platform in the ORAN can manage multiple function units, which can be VNFs or APPs. The computing resource scheduler can subscribe to the performance information of these function units, so as to schedule computing resource based on the subscribed performance information.

[0114] The types of the nodes included in the open cloud platform can be the same or different. For example, the nodes included in the open cloud management platform can be K8S (kubernetes) type nodes and / or European Telecommunications Standards Institute (ETSI) type nodes.

[0115] K8S is a distributed system platform with perfect cluster management capability and management tools. K8S is divided into a control node (Master) and a group of work nodes (Node). Among them, a group of processes related to cluster management run on the Master, responsible for the management and control of the entire cluster, realizing the management surface of the container. The real application runs on the Node, and the minimum unit of running is the container group (POD). POD is the smallest unit that can be created, scheduled, managed and deployed. Node can be a physical host or a virtual machine.

[0116] If the function unit is deployed on a K8S type node, the performance information of the function unit can at least include one or more of node information, node POD usage and node container usage.

[0117] Among them, the node information can at least include one or more of node state (NetworkUnavailable, MemoryPressure, DiskPressure, PIDPressure and Ready), node allocatable CPU core number, node allocatable memory total amount (unit: byte), node taint condition, node memory total amount (unit: byte), node CPU core number and node runnable POD total number.

[0118] The node POD usage can at least include one or more of RAM and CPU number.

[0119] The node container usage can at least include one or more of CPU index (percentage of container CPU usage to its application, number of container CPU usage to machine core, percentage of container CPU execution cycle limited), MEM index (container memory usage rate, current container memory usage byte number), network index (container network receiving byte number, container network sending byte number) and file system index (total amount of file system that container can use).

[0120] If the function unit is deployed on an ETSI type node, the performance information of the function unit can at least include one or both of node condition and function unit performance condition. Among them, the node condition can at least include one or more of node allocatable CPU core number, node allocatable memory total amount (unit: byte), node memory total amount (unit: byte) and node CPU core number. The function unit performance condition can at least include one or more of average virtual CPU usage, average virtual memory usage, average virtual disk usage, input data amount (unit: byte), output data amount (unit: byte), input data packet number and output data packet number.

[0121] It should be noted that the above is only an exemplary description of the node type and performance information, and is not intended to limit the node type and performance information. The open cloud platform can also include other types of nodes, and the functional unit can also include other performance information.

[0122] At step S302, in response to the first subscription request, the performance information of the functional unit managed by the open cloud platform is obtained.

[0123] After receiving the first subscription request, the SMO can obtain the performance information of the functional unit managed by the open cloud platform from the open cloud platform.

[0124] In a possible implementation, step S302 can include: in response to the first subscription request, sending a second subscription request to a management service unit of the open cloud platform; and receiving the performance information sent by the management service unit in response to the second subscription request.

[0125] The second subscription request can be used to request the management service unit of the open cloud platform to report the performance information of each functional unit managed by the open cloud platform. The management service unit of the open cloud platform can be an IMS and / or a DMS of the open cloud platform.

[0126] After receiving the first subscription request, the SMO can send a second subscription request to the management service unit. After receiving the second subscription request, the management service unit can collect the performance information of each functional unit managed by the open cloud platform from each node. Then, the management service unit can send the collected performance information to the SMO, and then the SMO provides the performance information to the computing power scheduler.

[0127] In a possible implementation, the performance information is reported through the O1 interface or the O2 interface. That is, the management service unit can send the performance information of each functional unit managed by the open cloud platform to the SMO through the O1 interface or the O2 interface.

[0128] In a possible implementation, the performance information can be reported periodically or reported when a preset condition is met. That is, the management service unit can periodically send the performance information of each functional unit managed by the open cloud platform to the SMO, or the management service unit can send the performance information of each functional unit managed by the open cloud platform to the SMO when a preset condition is met.

[0129] The preset condition can be set as needed. For example, the preset condition can be that the memory usage of the node container is greater than a certain value, or the average virtual memory usage is greater than a certain value, or the state information of the node does not match the preset node state information, or the state information of the POD does not match the preset POD state information, or the state information of the POD or the node matches the preset information, and the like. In the embodiment of the application, the preset condition is not limited.

[0130] The performance information is periodically reported or reported when the preset condition is met. The power scheduling party can specify in the first subscription request, or the SMO or the service management unit can pre-configure. The embodiment of the application does not limit this.

[0131] In a possible implementation, the method can further include: in a case where the second subscription confirmation message sent by the service management unit is received, sending the first subscription confirmation message to the power scheduling party.

[0132] The second subscription confirmation message can indicate that the service management unit has received the second subscription request. The first subscription confirmation message can indicate that the SMO has received the first subscription request.

[0133] The power scheduling party sends the first subscription request to the SMO; the SMO sends the second subscription request to the service management unit in response to the first subscription request. The service management unit sends the second subscription confirmation message to the SMO in response to the second subscription request, to notify the SMO that the service management unit has received the second subscription request and will subsequently report the performance information to the SMO. The SMO sends the first subscription confirmation message to the power scheduling party in response to the second subscription confirmation message, to notify the power scheduling party that the SMO has received the first subscription request and will subsequently report the performance information to the power scheduling party. After receiving the first subscription confirmation message, the power scheduling party can confirm that the SMO has prepared to provide the performance information.

[0134] Step S303: sending the performance information to the power scheduling party.

[0135] The performance information can be used for power resource scheduling. That is, the power provider can obtain the performance information of each functional unit managed by the open cloud platform, and then perform power resource scheduling according to the obtained performance information.

[0136] It should be noted that the process of the power scheduling party performing power resource scheduling according to the performance information can refer to related technologies, and the embodiment of the application does not limit this.

[0137] The method for scheduling computing power resources of the open wireless access network receives a first subscription request for subscribing to performance information of a functional unit sent by a computing power scheduler, obtains performance information of each functional unit managed by the open cloud platform, and then sends the performance information to the computing power scheduler, so that the computing power scheduler can use the performance information of each functional unit managed by the open cloud platform to schedule computing power resources, thereby meeting the computing power demand of the computing power scheduler outside the open wireless access network.

[0138] The above describes that the ORAN provides performance information to the external computing power scheduler, so that the external computing power scheduler can use the performance information to schedule computing power resources. The process of scheduling computing power resources is exemplarily described below.

[0139] In an exemplary embodiment, the method can further include receiving a first resource scheduling request sent by the computing power scheduler, in response to the first resource scheduling request, routing service data of the first functional unit from the first node to the second node, and sending a notification of successful node change to the computing power scheduler.

[0140] The first resource scheduling request is used to adjust the first functional unit of the open cloud platform from being deployed on the first node of the open cloud platform to being deployed on the second node of the open cloud platform.

[0141] The first node can represent any one node of the open cloud platform, and the second node can represent any one node of the open cloud platform except the first node. The first functional unit can represent any one functional unit deployed on the first node.

[0142] If the computing power scheduler determines that the first node cannot meet or may not meet the demand of the first functional unit for computing power resources in a short period of time after analyzing the received performance information, the computing power scheduler can send a first resource scheduling request to the SMO. After receiving the first resource scheduling request, the SMO can route the service data of the first functional unit from the first node to the second node. In this way, the service data of the first functional unit is calculated by the second node, reducing the consumption of computing power of the first node. After completing the change of the service data routing, the SMO can determine that the node where the first functional unit is deployed has been successfully changed, and can send a notification of successful node change to the computing power scheduler. After receiving the notification of node change, the computing power scheduler can confirm that the node where the first functional unit is deployed has been changed from the first node to the second node, and the problem or hidden danger of insufficient computing power resources has been solved.

[0143] In an example, a node closer to the first node can be determined as the second node, thereby reducing the change of routing information.

[0144] In an example embodiment, the method can further include: releasing, by the management service unit of the open cloud platform, the computing resource occupied by the first functional unit on the first node in a case where the service data routing transfer of the first functional unit is completed. In this way, the computing resource originally used by the first functional unit on the first node can be vacated to process other services, saving computing resources and facilitating improvement of the utilization rate of computing resources.

[0145] In an example embodiment, the method can further include: receiving a second resource scheduling request sent by the computing resource scheduler; in response to the second resource scheduling request, reducing or expanding the scale of the second functional unit; and sending a notification of successful scale adjustment to the computing resource scheduler.

[0146] The second resource scheduling request can be used to adjust the scale of the second functional unit of the open cloud platform.

[0147] The second functional unit can represent any functional unit deployed on any node of the open cloud platform.

[0148] If the computing resource scheduler determines, after analyzing the received performance information, that the actual computing resource occupied by the second functional unit is greater than or less than the required computing resource, the computing resource scheduler can send a second resource scheduling request to the SMO to request to expand the scale of the second functional unit (Scale-Out) or reduce the scale of the second functional unit (Scale-In). The SMO, in response to the second resource adjustment request, reduces the scale of the second functional unit (the actual computing resource occupied by the second functional unit is greater than the required computing resource) or expands the scale of the second functional unit (the actual computing resource occupied by the second functional unit is less than the required computing resource). After the scale of the second functional unit is adjusted, the SMO can send a notification of successful scale adjustment to the computing resource scheduler. After receiving the notification of successful scale adjustment, the computing resource scheduler can confirm that the scale of the second functional unit is appropriate. In this way, the waste of computing resources is reduced, thereby improving the utilization rate of computing resources.

[0149] In an example embodiment, as shown in FIG. 4, a computing resource scheduling method for an open wireless access network is provided. The method is applied to the application environment of FIG. 1 as an example for illustration. As shown in FIG. 4, the method can include:

[0150] Step S401, the computing resource scheduler sends a first subscription request to the SMO.

[0151] The first subscription request is used to subscribe to functional unit performance information.

[0152] Step S402, the SMO, in response to the first subscription request, sends a second subscription request to the management service unit of the open cloud platform.

[0153] The second subscription request can be used to request the management service unit to report performance information of the functional unit managed by the open cloud platform.

[0154] In step S403, the management service unit sends a second subscription confirmation message to the SMO.

[0155] The second subscription confirmation message can indicate that the management service unit has received the second subscription request.

[0156] In step S404, the SMO sends a first subscription confirmation message to the computing power scheduler in a case where the second subscription confirmation message is received.

[0157] The first subscription confirmation message can indicate that the SMO has received the first subscription request.

[0158] Steps S401 to S404 can refer to steps S301 and S302, which will not be described here.

[0159] After steps S401 to S404 complete the subscription of the performance information, the management service unit can report the performance information to the SMO, and the SMO can report the performance information to the computing power scheduler. The process of reporting the performance information can be periodic or conditionally triggered. The periodic reporting process is described below through steps S405 to S407, and the conditionally triggered reporting process is described below through steps S408 to S410.

[0160] In step S405, the node of the open cloud platform periodically sends performance information of a functional unit deployed on the node to the management service unit through the O2 interface.

[0161] In step S406, the management service unit periodically sends the received performance information to the SMO through the O1 interface or the O2 interface.

[0162] In step S407, the SMO periodically sends the received performance information to the computing power scheduler.

[0163] Steps S405 to S407 can refer to step S302, which will not be described here.

[0164] It should be noted that the periods of steps S405 to S407 can be the same or different. In the case where the periods of steps S405 to S407 are different, the lengths of the periods in the three steps can increase in turn.

[0165] In step S408, the node of the open cloud platform periodically sends performance information of a functional unit deployed on the node to the management service unit through the O2 interface.

[0166] Step S409, the management service unit periodically sends performance information to the SMO through the O1 interface or the O2 interface.

[0167] Step S410, the SMO sends the received performance information to the computing power scheduling provider in the case of meeting the preset triggering condition.

[0168] Steps S405 to S407 can refer to step S302, which will not be described here.

[0169] When the functional unit is successfully deployed, the SMO collects the performance information of the nodes distributed in each geographical location on the O-Cloud through the O1 or O2 interface. If the current nodes of the O-Cloud do not meet the computing power requirement, the SMO can redeploy or adjust the functional units deployed on the nodes through the O2 interface.

[0170] In this embodiment, the computing power scheduling direction SMO sends a first subscription request for subscribing to functional unit performance information, the SMO obtains the performance information of each functional unit managed by the open cloud platform from the open cloud platform, and then sends the performance information to the computing power scheduling party, so that the computing power scheduling party can use the performance information of each functional unit managed by the open cloud platform to schedule computing power resources, thereby meeting the computing power requirement of the computing power scheduling party outside the open wireless access network.

[0171] FIG. 5 shows an exemplary coverage schematic diagram of the open wireless access network. As shown in FIG. 5, node 1 and node 2 of the open cloud platform can cover area 1, and node 3 can cover area 2. For a user terminal (UE) in area 1, it can be provided with edge computing power service by node 1 or node 2. It is assumed that node 1 provides edge computing power service for the UE at the beginning. When the client finds that node 1 cannot meet the requirement of the UE, the client can send a request to the SMO to make the SMO configure node 2 to provide edge computing power service for the UE.

[0172] In an exemplary embodiment, as shown in FIG. 6, a computing power resource scheduling method of an open wireless access network is provided, which is applied to the application environment of FIG. 1 as an example for illustration. As shown in FIG. 6, the method can include:

[0173] Step S601, the computing power scheduling direction SMO sends a first subscription request.

[0174] The first subscription request is used to subscribe to functional unit performance information.

[0175] Step S602, the SMO sends a second subscription request to the management service unit of the open cloud platform in response to the first subscription request.

[0176] The second subscription request can be used to request the management service unit to report performance information of the functional unit managed by the open cloud platform.

[0177] In step S603, the management service unit sends a second subscription confirmation message to the SMO.

[0178] The second subscription confirmation message can indicate that the management service unit has received the second subscription request.

[0179] In step S604, the SMO sends a first subscription confirmation message to the computing power scheduler in the case of receiving the second subscription confirmation message.

[0180] The first subscription confirmation message can indicate that the SMO has received the first subscription request.

[0181] The above steps S601 to S604 can refer to steps S401 to S404, which will not be described here.

[0182] In step S605, the node 1 of the open cloud platform periodically sends performance information of the functional unit deployed on the node to the management service unit through the O2 interface.

[0183] It should be noted that in FIG. 6, node 1 is taken as an example, and nodes 2 to n will also periodically send performance information of the functional unit deployed on the node to the management service unit through the O2 interface, but the performance reporting process of nodes 2 to n is not shown in FIG. 6.

[0184] In step S606, the management service unit periodically sends the received performance information to the SMO through the O1 interface or the O2 interface.

[0185] In step S607, the SMO periodically or in the case of meeting a preset triggering condition, provides performance information for the computing power scheduler.

[0186] In step S608, when the computing power scheduler determines that the node 1 cannot meet the demand of the first functional unit, the computing power scheduler sends a first resource scheduling request to the SMO according to the current performance information.

[0187] The first functional unit is a functional unit deployed on the node 1, and here the node 1 is equivalent to the first node in the foregoing. For example, when the data volume processing capability of the node 1 cannot meet the data volume processing demand of the first functional unit, the computing power scheduler can determine that the node 1 cannot meet the demand of the first functional unit. Of course, the computing power scheduler can also determine that the node 1 cannot meet the demand of the first functional unit in other ways, which is not limited by the embodiments of the present application.

[0188] The first resource scheduling request can be used to adjust the first functional unit of the open cloud platform from being deployed on the node 1 to being deployed on the node 2.

[0189] Step S609, the SMO transfers the service data routing of the first function unit from the node 1 to the node 2 in response to the first resource scheduling request.

[0190] Step S610, the SMO informs the management service unit to release the computing power resources occupied by the first function unit on the node 1 in the case that the service data routing of the first function unit is transferred.

[0191] Step S611, the management service unit releases the computing power resources occupied by the first function unit on the node 1.

[0192] Step S612, the management service unit sends a notification of the first function unit resource release completion to the SMO.

[0193] Step S613, the SMO sends a notification of the node change success to the computing power scheduler.

[0194] In a possible implementation, by reporting the performance information, the computing power scheduler can also trigger the scale-in and scale-out to make more full use of the computing power resources.

[0195] In an exemplary embodiment, as shown in FIG. 7, a computing power resource scheduling method of an open wireless access network is provided, which is applied to the application environment of FIG. 1 for example. As shown in FIG. 7, the method can include:

[0196] Step S701, the computing power scheduler sends a first subscription request to the SMO.

[0197] The first subscription request is used to subscribe to the function unit performance information.

[0198] Step S702, the SMO sends a second subscription request to the management service unit of the open cloud platform in response to the first subscription request.

[0199] The second subscription request can be used to request the management service unit to report the performance information of the function unit managed by the open cloud platform.

[0200] Step S703, the management service unit sends a second subscription confirmation message to the SMO.

[0201] The second subscription confirmation message can indicate that the management service unit has received the second subscription request.

[0202] Step S704, the SMO sends a first subscription confirmation message to the computing power scheduler in the case that the second subscription confirmation message is received.

[0203] The first subscription confirmation message can indicate that the SMO has received the first subscription request.

[0204] The above steps S701 to S704 can refer to steps S401 to S404, which will not be described again here.

[0205] In step S705, the node of the open cloud platform periodically sends performance information of the function unit deployed on the node to the management service unit through the O2 interface.

[0206] In step S706, the management service unit periodically sends the received performance information to the SMO through the O1 interface or the O2 interface.

[0207] In step S707, the SMO periodically or in the case of meeting a preset triggering condition, provides performance information for the computing power scheduling party.

[0208] In step S708, the computing power scheduling party discovers that the resource configuration of the second function unit does not match the actual demand according to the reported performance information, and sends a second resource scheduling request to the SMO.

[0209] The second resource scheduling request is used to adjust the scale of the second function unit of the open cloud platform.

[0210] In step S709, the SMO sends a request to adjust the scale of the second function unit to the management service module in response to the second resource scheduling request.

[0211] In step S710, the management service module sends a notification of completion of scale adjustment to the SMO.

[0212] In step S711, the SMO sends a notification of completion of scale adjustment to the computing power scheduling party.

[0213] In the embodiments of the present application, the O-RAN SMO collects and reports O-Cloud performance information (including K8s node, POD, container performance; ETSI node and function unit performance) through the O1 or O2 interface, thereby assisting the rApp and external client in computing power task scheduling deployment and adjustment.

[0214] In the embodiments of the present application, performance information is provided for the rApp and external client that need to perform computing power scheduling, which assists the rApp and external client in computing power task scheduling deployment and adjustment, more fully and accurately schedules the edge computing power resources of the O-Cloud, and better provides computing power services for edge computing power businesses (for example: XR, AI / ML, V2X, vertical industry).

[0215] It should be understood that although each step in the flowchart involved in each embodiment as described above is shown in sequence according to the direction of the arrow, these steps are not necessarily executed in the order indicated by the arrow. Unless explicitly stated herein, there is no strict order limitation for the execution of these steps, and these steps can be executed in other orders. Moreover, at least part of the steps in the flowchart involved in each embodiment as described above can include multiple steps or multiple stages, which are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily sequential, but can be alternately or alternately executed with at least part of other steps or steps or stages in other steps.

[0216] Based on the same inventive concept, the embodiments of the present application also provide an open radio access network computing resource scheduling device for implementing the open radio access network computing resource scheduling method described above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme described in the above method, so the specific limitations in one or more open radio access network computing resource scheduling device embodiments provided below can refer to the limitations of the open radio access network computing resource scheduling method described above, which will not be repeated here.

[0217] In one exemplary embodiment, as shown in FIG. 8, an open radio access network computing resource scheduling device is provided, which device 800 can include a first receiving unit 801, a first response unit 802, and a first sending unit 803, wherein:

[0218] The first receiving unit 801 is configured to receive a first subscription request sent by a computing resource scheduler, and the first subscription request is used to subscribe to function unit performance information.

[0219] The first response unit 802 is configured to, in response to the first subscription request, obtain performance information of a function unit managed by an open cloud platform.

[0220] The first sending unit 803 is configured to send the performance information to the computing resource scheduler, and the performance information is used for computing resource scheduling.

[0221] In one embodiment, the first response unit is configured to:

[0222] In response to the first subscription request, send a second subscription request to a management service unit of the open cloud platform, and the second subscription request is used to request the management service unit to report the performance information.

[0223] Receive the performance information sent by the management service unit in response to the second subscription request.

[0224] In one embodiment, the performance information is reported through an O1 interface or an O2 interface.

[0225] In an embodiment, the performance information is reported periodically or upon satisfaction of a preset triggering condition.

[0226] In an embodiment, the apparatus further comprises:

[0227] a second receiving unit, configured to receive a first resource scheduling request sent by the computing power scheduler, the first resource scheduling request being used to adjust a first function unit of the open cloud platform from being deployed on a first node of the open cloud platform to being deployed on a second node of the open cloud platform;

[0228] a second responding unit, configured to, in response to the first resource scheduling request, route service data of the first function unit from the first node to the second node;

[0229] a second sending unit, configured to send a notification of success of the node change to the computing power scheduler.

[0230] In an embodiment, the apparatus further comprises:

[0231] a first notifying unit, configured to, in a case where the routing of the service data of the first function unit is completed, notify a management service unit of the open cloud platform to release computing power resources occupied by the first function unit on the first node.

[0232] In an embodiment, the apparatus further comprises:

[0233] a third receiving unit, configured to receive a second resource scheduling request sent by the computing power scheduler, the second resource scheduling request being used to adjust a scale of a second function unit of the open cloud platform;

[0234] a third responding unit, configured to, in response to the second resource scheduling request, reduce or expand the scale of the second function unit;

[0235] a second notifying unit, configured to send a notification of success of the scale adjustment to the computing power scheduler.

[0236] In an embodiment, the function units managed by the open cloud platform are deployed on K8s type nodes and / or ETSI type nodes.

[0237] In an embodiment, the apparatus further comprises:

[0238] a third sending unit, configured to, in a case where a second subscription confirmation message sent by the management service unit is received, send a first subscription confirmation message to the computing power scheduler, the second subscription confirmation message indicating that the management service unit has received a second subscription request.

[0239] In an embodiment, the computing power scheduler comprises:

[0240] The non-proximal wireless intelligent controllerapplicationrAPP or an external computing power scheduling client.

[0241] It should be noted that the division of the units in the embodiments of the present application is illustrative, and is only a logical function division. In actual implementation, another division manner can be used. In addition, each functional unit in each embodiment of the present application can be integrated in one processing unit, or each unit can be physically present separately, or two or more units can be integrated in one unit. The integrated unit can be realized in the form of hardware or in the form of a software functional unit.

[0242] When the integrated unit is realized in the form of a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solutions of the present application can be embodied in the form of a software product, the computer software product is stored in a storage medium, and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to execute all or part of the steps of the methods described in the various embodiments of the present application.

[0243] It should be noted that the above-described device provided by the embodiments of the present application can realize all the method steps achieved by the method embodiments, and can achieve the same technical effects. Here, the same parts and beneficial effects of the method embodiments in this embodiment will not be described in detail.

[0244] If "component", "module" and "system" and the like are used in the present application, they are intended to represent network device related entities, which can be hardware, a combination of hardware and software, software, or software in execution. For example, a component can be, but is not limited to, a process running on a processor, a processor, an object, executable code, an executing thread, a program, and / or a computer. As an illustration, an application running on a server and the server can both be components. One or more components can reside in a process and / or an executing thread, and a component can be located in one computer kernel or distributed between two or more computers.

[0245] In one exemplary embodiment, an open radio access network computing resource scheduling device is provided, and the structure of the open radio access network computing resource scheduling device can be as shown in FIG. 9. The resource allocation device includes a memory 1120, a transceiver 1110, and a processor 1100.

[0246] The transceiver is configured to receive and send data under the control of the processor.

[0247] In FIG. 9, the bus architecture can include any number of interconnected buses and bridges, which are used to link various circuits together, including the processors represented by one or more processors and the memory represented by the memory. The bus architecture can also link various other circuits, such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and thus, will not be further described herein. The bus interface provides an interface. The transceiver can be a plurality of elements, including a transmitter and a receiver, which provides a means for communicating with various other apparatus over a transmission medium, including a wireless channel, a wired channel, optical cable, and the like. The processor is responsible for managing the bus architecture and general processing, and the memory can store data used by the processor in executing operations.

[0248] The processor can be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or a complex programmable logic device (CPLD), and the processor can also adopt a multi-core architecture.

[0249] The processor is configured to execute any of the methods provided by the embodiments of the present application by invoking the program stored in the memory. The processor and the memory can also be physically arranged separately.

[0250] It should be noted that the above-described apparatus provided by the embodiments of the present application can implement all the method steps achieved by the above-described method embodiments and achieve the same technical effects. Therefore, the same parts and beneficial effects of the method embodiments will not be described in detail herein.

[0251] In one exemplary embodiment, an open radio access network computing resource scheduling apparatus is provided, which can be a network device, including a memory and a processor, the memory storing a computer program, and the processor implementing the steps in the above-described method embodiments when executing the computer program.

[0252] In one exemplary embodiment, a processor-readable storage medium is provided, which stores a computer program, and the computer program implements the steps in the above-described method embodiments when executed by a processor.

[0253] In one exemplary embodiment, a computer program product is provided, which includes a computer program, and the computer program implements the steps in the above-described method embodiments when executed by a processor.

[0254] The processor-readable storage media can be any available media or memory element to be accessed by a processor including both volatile and nonvolatile media, and removable and non-removable media. By way of example, and not limitation, such computer-readable media can comprise a RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired computer program code in the form of computer- executable instructions or data structures and that can be accessed by a computer. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or any other medium for transmitting computer-readable instructions, then the coaxial cable, fiber optic cable, twisted pair, DSL, or any other medium should be included in the definition of medium. Computer-readable storage media

[0255] Those skilled in the art will appreciate that embodiments of the present application can be devised for a method, a system, or a computer program product. Accordingly, the present application can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application can take the form of a computer program product on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, and other optical storage devices, and the like) embodying computer-readable program code.

[0256] The present application is described in the context of the methods, apparatuses (systems), and computer program products according to the embodiments of the present application by referring to the flowcharts and / or block diagrams. It is understood that each flow and / or block in the flowcharts and / or block diagrams, and combinations of flows and / or blocks in the flowcharts and / or block diagrams can be implemented by processor-executable instructions. These processor-executable instructions can be provided to a processor of a general purpose computer, a special purpose computer, an embedded processor or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart or flows and / or block or blocks in the block diagrams.

[0257] These processor-executable instructions can also be stored in a processor-readable storage medium that can direct the computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the processor-readable storage medium produce an article of manufacture including instruction means that implement the function specified in the flowchart or flows and / or block or blocks in the block diagrams.

[0258] It will be apparent to those skilled in the art that various modifications and variations can be made to the present application without departing from the spirit or scope of the application. Thus, it is intended that the present application cover the modifications and variations of this application provided they come within the scope of the appended claims and their equivalents.

Claims

1. A method for scheduling computing resources of an open radio access network, comprising: receiving a first subscription request sent by a computing resource scheduler, the first subscription request being used to subscribe to function unit performance information; in response to the first subscription request, obtaining performance information of a function unit managed by an open cloud platform; sending the performance information to the computing resource scheduler, the performance information being used for computing resource scheduling.

2. The method of claim 1, wherein, The performance information of the function unit managed by the open cloud platform is obtained in response to the first subscription request, comprising: in response to the first subscription request, sending a second subscription request to a management service unit of the open cloud platform, the second subscription request being used to request the management service unit to report the performance information; receiving the performance information sent by the management service unit in response to the second subscription request.

3. The method of claim 2, wherein, The performance information is reported through an O1 interface or an O2 interface.

4. The method of claim 2, wherein, The performance information is reported periodically or under the condition that a preset trigger condition is met.

5. The method of claim 1, wherein, The method further comprises: receiving a first resource scheduling request sent by the computing resource scheduler, the first resource scheduling request being used to adjust a first function unit of the open cloud platform from being deployed on a first node of the open cloud platform to being deployed on a second node of the open cloud platform; in response to the first resource scheduling request, routing service data of the first function unit from the first node to the second node; sending a notification of successful node change to the computing resource scheduler.

6. The method of claim 5, wherein, The method further comprises: in the case where the routing of the service data of the first function unit is completed, notifying a management service unit of the open cloud platform to release computing resources occupied by the first function unit on the first node.

7. The method of claim 1, wherein, The method further comprises: receiving a second resource scheduling request sent by the computing resource scheduler, the second resource scheduling request being used to adjust the scale of a second function unit of the open cloud platform; in response to the second resource scheduling request, reducing or expanding the scale of the second function unit; sending a notification of successful scale adjustment to the computing resource scheduler.

8. The method of claim 1, wherein, The function unit managed by the open cloud platform is deployed on a K8s type node and / or an ETSI type node.

9. The method of claim 2, wherein, The method further comprises: in the case where a second subscription confirmation message sent by the management service unit is received, sending a first subscription confirmation message to the computing resource scheduler, the second subscription confirmation message indicating that the management service unit has received the second subscription request.

10. The method of any one of claims 1 to 9, wherein, The computing resource scheduler comprises: a non-proximal wireless intelligent controller application (rAPP) or an external computing resource scheduling client.

11. An apparatus for scheduling computing resources of an open radio access network, comprising a memory, a transceiver, and a processor: a memory for storing the computer program; The transceiver is used to transceive data under the control of the processor. The processor is used to read a computer program in the memory and perform the following operations: receiving a first subscription request sent by a computing resource scheduler, the first subscription request being used to subscribe to function unit performance information; in response to the first subscription request, obtaining performance information of a function unit managed by an open cloud platform; The performance information is sent to the computing power scheduling party, and the performance information is used for computing power resource scheduling.

12. The apparatus of claim 11, wherein, The performance information of the functional unit managed by the open cloud platform is acquired in response to the first subscription request, including: In response to the first subscription request, a second subscription request is sent to a management service unit of the open cloud platform, and the second subscription request is used to request the management service unit to report the performance information. The performance information reported by the management service unit in response to the second subscription request is received.

13. The apparatus of claim 12, wherein, The performance information is reported through an O1 interface or an O2 interface.

14. The apparatus of claim 12, wherein, The performance information is reported periodically or under the condition that a preset trigger condition is met.

15. The apparatus of claim 11, wherein, The processor is further configured to perform the following operations: A first resource scheduling request is received from the computing power scheduling party, and the first resource scheduling request is used to adjust a first functional unit of the open cloud platform from being deployed on a first node of the open cloud platform to being deployed on a second node of the open cloud platform. In response to the first resource scheduling request, the service data of the first functional unit is routed from the first node to the second node. A notification of successful node change is sent to the computing power scheduling party.

16. The apparatus of claim 15, wherein, The processor is further configured to perform the following operations: In a case where the routing of the service data of the first functional unit is completed, the management service unit of the open cloud platform is notified to release the computing power resources occupied by the first functional unit on the first node.

17. The apparatus of claim 11, wherein, The processor is further configured to perform the following operations: A second resource scheduling request is received from the computing power scheduling party, and the second resource scheduling request is used to adjust the scale of a second functional unit of the open cloud platform. In response to the second resource scheduling request, the scale of the second functional unit is reduced or expanded. A notification of successful scale adjustment is sent to the computing power scheduling party.

18. The apparatus of claim 11, wherein, The functional units managed by the open cloud platform are deployed on K8s type nodes and / or ETSI type nodes.

19. The apparatus of claim 12, wherein, The processor is further configured to perform the following operations: In a case where a second subscription confirmation message sent by the management service unit is received, a first subscription confirmation message is sent to the computing power scheduling party, and the second subscription confirmation message indicates that the second subscription request has been received by the management service unit.

20. The apparatus of any of claims 11 to 19, wherein, The computing power scheduling party includes: A non-close wireless intelligent controller application (rAPP) or an external computing power scheduling client.

21. An open wireless access network computing power resource scheduling device, comprising: A first receiving unit configured to receive a first subscription request sent by a computing power scheduling party, and the first subscription request is used to subscribe to functional unit performance information. A first response unit configured to acquire performance information of a functional unit managed by an open cloud platform in response to the first subscription request. A first sending unit configured to send the performance information to the computing power scheduling party, and the performance information is used for computing power resource scheduling.

22. A processor-readable storage medium, wherein, The processor readable storage medium stores a program, and the program is used to make the processor perform the method in any one of claims 1 to 10.

Images