Computing power resource allocation method and device, electronic equipment and computer program product

Abstract

The invention relates to the technical field of wireless communication, and particularly provides a computing power resource allocation method and device, electronic equipment and a computer program product. The method comprises: sending a first message or a second message to a second device, the first message being used for indicating a service computing power demand, and the second message being used for indicating computing power resource allocation. According to the method and the device, the general calculation performance requirement of the service or the slice is decomposed into the calculation power requirement, so that the allocation or reservation of wireless calculation power related resources is enhanced, and the multi-dimensional resource guarantee of the specific service or the slice is realized.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to the technical field of wireless communication, and particularly relates to a computing resource configuration method and device, electronic equipment and computer program product. BACKGROUND

[0002] In the prior art, a service profile mainly faces the service demand related to a wireless communication connection, is decomposed into different slice communication connection service demands (such as a RAN Slice Profile), and the resources allocated for a base station or a slice based on the service demand only include physical resource blocks (PRBs), radio resource control (RRC) connection numbers and logical data links (DRBs).

[0003] When facing diversified services such as augmented reality (XR), artificial intelligence (AI), vehicle-to-everything (V2X) and the like, which have higher requirements for wireless communication and computing capabilities, it is necessary to utilize the remaining computing capabilities of the wireless network to realize common deployment of services. However, the existing technical solutions for resource reservation through slices do not consider the demand of other services for computing resources. Meanwhile, the service demand and the communication demand can change at any time, and the existing resource allocation mode cannot flexibly cope with such changes, and cannot effectively handle the competition of different services for computing resources. SUMMARY

[0004] The present disclosure is proposed in view of the above problems. The present disclosure provides a computing resource configuration method and device, electronic equipment and computer program product.

[0005] According to a first aspect of the present disclosure, a computing resource configuration method is provided, applied to a first device, and the method comprises: sending a first message or a second message to a second device, wherein the first message is used to indicate a service computing demand, and the second message is used to indicate a computing resource allocation.

[0006] In addition, according to the computing resource configuration method of one aspect of the present disclosure, the method further comprises: receiving a third message before sending the first message or the second message to the second device, wherein the third message is used to indicate a service demand.

[0007] In addition, according to the computing resource configuration method of one aspect of the present disclosure, the method further comprises: generating a service communication demand and / or a service computing demand based on the third message before sending the first message or the second message to the second device.

[0008] Further, the computing resource allocation method according to an aspect of the present disclosure, wherein the second message comprises computing resources, the computing resources being used for computing resource allocation, the computing resources comprising at least one of: computing resources, memory resources, storage resources, and network resources, wherein the computing resources are generated based on the service computing demand.

[0009] Further, the computing resource allocation method according to an aspect of the present disclosure, wherein the first message comprises at least one of: a service type, a computing data volume, a computing processing time, a computing service start time, a computing service end time, a computing service mode, a computing processing number, a computing time delay budget, a computing reliability, a scaling configuration, a backup configuration, a resource type, a resource description, and a computing priority.

[0010] Further, the computing resource allocation method according to an aspect of the present disclosure, wherein the third message comprises at least one of: a service type, a computing data volume, a computing processing time, a computing service start time, a computing service end time, a computing service mode, a computing processing number, a scaling function, a backup function, a resource type, a resource description, a computing priority, a service end-to-end time delay, and a service reliability.

[0011] According to a second aspect of the present disclosure, a computing resource allocation method is provided, applied to a second device, the method comprising: receiving a first message or a second message sent by a first device, wherein the first message is used to indicate a service computing demand, and the second message is used to indicate computing resource allocation.

[0012] Further, the computing resource allocation method according to an aspect of the present disclosure, wherein the method further comprises: after receiving the second message sent by the first device, performing computing resource allocation based on the second message, wherein the second message comprises computing resources, the computing resources comprising at least one of: computing resources, memory resources, storage resources, and network resources, wherein the computing resources are generated based on the service computing demand.

[0013] Further, the computing resource allocation method according to an aspect of the present disclosure, wherein the method further comprises: after receiving the first message sent by the first device, generating computing resources based on the first message; and performing computing resource allocation based on the computing resources.

[0014] Further, the computing resource allocation method according to an aspect of the present disclosure, wherein the first message comprises at least one of: a service type, a computing data volume, a computing processing time, a computing service start time, a computing service end time, a computing service mode, a computing processing number, a computing time delay budget, a computing reliability, a scaling configuration, a backup configuration, a resource type, a resource description, and a computing priority.

[0015] According to a third aspect of the present disclosure, there is provided a computing resource configuration apparatus applied to a first device, the apparatus comprising: a sending module configured to send a first message or a second message to a second device, wherein the first message is configured to indicate a service computing requirement, and the second message is configured to indicate a computing resource allocation.

[0016] According to a fourth aspect of the present disclosure, there is provided a computing resource configuration apparatus applied to a second device, the apparatus comprising: a receiving module configured to receive a first message or a second message sent by a first device, wherein the first message is configured to indicate a service computing requirement, and the second message is configured to indicate a computing resource allocation.

[0017] According to a fifth aspect of the present disclosure, there is provided an electronic device comprising: a memory configured to store computer readable instructions; and a processor configured to execute the computer readable instructions to cause the electronic device to perform the computing resource configuration method as described above.

[0018] According to a sixth aspect of the present disclosure, there is provided a computer program product comprising a computer program which, when executed by a processor, implements the computing resource configuration method as described above.

[0019] As will be described in detail below, according to the computing resource configuration method of the embodiments of the present disclosure, the present disclosure enhances the allocation or reservation of wireless computing related resources by decomposing the service or slice performance requirement into computing requirements, thereby achieving multi-dimensional resource guarantee for specific services or slices.

[0020] It is to be understood that both the foregoing general description and the following detailed description are exemplary and intended to provide further explanation of the subject technology. BRIEF DESCRIPTION OF DRAWINGS

[0021] The foregoing and other objects, features and advantages of the present disclosure will become more apparent from the following detailed description, which proceeds with reference to the accompanying drawings. The drawings are provided to illustrate embodiments of the present disclosure and, together with the detailed description, serve to explain the present disclosure and do not constitute a limitation thereof. In the drawings, like reference numerals refer to like elements or steps throughout.

[0022] Figure 1 is a scenario schematic diagram illustrating an application scenario of the computing resource configuration method according to an embodiment of the present disclosure.

[0023] Figure 2 is a method flowchart illustrating the computing resource configuration method according to an embodiment of the present disclosure.

[0024] Figure 3 is a method flowchart further illustrating the computing resource configuration method according to an embodiment of the present disclosure.

[0025] Figure 4 is a whole flow chart illustrating a computing resource allocation method according to an embodiment of the present disclosure.

[0026] Figure 5 is a method flow chart further illustrating the conversion of business demand into computing resource demand according to an embodiment of the present disclosure.

[0027] Figure 6 is a method flow chart further illustrating the conversion of computing resource demand into computing resource according to an embodiment of the present disclosure.

[0028] Figure 7 is a method flow chart further illustrating the conversion of computing resource demand into computing resource according to another embodiment of the present disclosure.

[0029] Figure 8 is a method flow chart further illustrating the conversion of computing resource demand into computing resource according to a third embodiment of the present disclosure.

[0030] Figure 9 is a method flow chart further illustrating the conversion of computing resource demand into computing resource according to a fourth embodiment of the present disclosure.

[0031] Figure 10 is a device schematic diagram illustrating a computing resource allocation apparatus according to an embodiment of the present disclosure.

[0032] Figure 11 is a device schematic diagram further illustrating a computing resource allocation apparatus according to an embodiment of the present disclosure.

[0033] Figure 12 is a hardware block diagram of an electronic device according to an embodiment of the present disclosure.

[0034] Figure 13 is a schematic diagram of a computer program product according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0035] In order to make the objectives, technical solutions and advantages of the present disclosure more obvious, the following will describe the example embodiments according to the present disclosure in detail with reference to the drawings. Obviously, the described embodiments are only part of the embodiments of the present disclosure, rather than all the embodiments of the present disclosure, and it should be understood that the present disclosure is not limited by the example embodiments described herein.

[0036] The techniques described in the embodiments of the present application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, and can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), and other systems. The terms "system" and "network" are often used interchangeably in the embodiments of the present application, and the described techniques can be used in the above-mentioned systems and radio technologies, as well as other systems and radio technologies. The following describes a New Radio (NR) system for example purposes, and NR terminology is used in most of the following description, and these techniques can also be applied to applications other than NR system applications, such as 6th Generation (6G) communication systems.

[0037] First, refer to Figure 1 The application scenario according to the embodiments of the present application is summarized.

[0038] Figure 1 is a scenario diagram illustrating an application scenario of the computing resource configuration method according to the embodiments of the present application. As Figure 1 shown, the application scenario can at least include: a terminal device 10 and a network device 20, wherein the network device 20 can be further subdivided into a first device 21 and a second device 22. That is, the first device 21 and the second device 22 can be independently deployed, or can be deployed on the same network device.

[0039] The terminal device 10 can also be referred to as a terminal or a user equipment (UE), and can be a terminal device such as a mobile phone, a tablet personal computer (PC), a laptop PC, a personal digital assistant (PDA), a palmtop PC, a netbook, an ultra-mobile personal computer (UMPC), a mobile Internet device (MID), a wearable device, or a vehicle-mounted device (VUE), a pedestrian terminal (PUE), etc. The wearable device can include a bracelet, an earphone, glasses, etc. It should be noted that the specific type of the terminal device 10 is not limited in the embodiments of the present disclosure.

[0040] The network device 20 (which can include the first device 21 and the second device 22) can be a cloud platform, a cluster, an infrastructure, a base station, or a core network. The base station can be referred to as a node B, an evolved node B, an access point, a base transceiver station (BTS), a radio base station, a radio transceiver, a basic service set (BSS), an extended service set (ESS), a node B, an evolved node B (eNB), a next generation node B (gNB), a home node B, a home evolved node B, a WLAN access point, a WiFi node, a transmitting receiving point (TRP), or some other appropriate terminology in the art. It should be noted that the specific type of the network device 20 is not limited in the embodiments of the present disclosure.

[0041] Specifically, as described above, the first device 21 and the second device 22 in the embodiments of the present disclosure can be independently deployed. The first device 21 can be a network device with communication, orchestration, management, control, etc. functions; and the second device 22 can be a network device with communication, resource allocation or reservation, etc. functions (as shown in (A) of FIG. 1). Figure 1

[0042] Further, the first device 21 and the second device 22 in the embodiments of the present disclosure can also be deployed on the same network device 20, and have communication, resource allocation or reservation, etc. functions, and can also implement orchestration, management, control, etc. functions (as shown in (B) of FIG. 1). Figure 1

[0043] ​​It should be noted that the embodiments of the present disclosure are only exemplarily illustrated by taking the independent deployment of the first device 21 and the second device 22 as an example, but this does not constitute a limitation.

[0044] Figure 2 is a method flowchart illustrating a computing resource configuration method according to an embodiment of the present disclosure. As shown in Figure 2 , the computing resource configuration method applied to the first device 21 can at least include the following steps.

[0045] In step S201, a first message or a second message is sent to the second device, wherein the first message is used to indicate service computing power demand, and the second message is used to indicate computing resource allocation. As described above, the present disclosure to be solved is that the service profile in the prior art is mainly a communication type service, and the problem of reserving computing resources for other services is not considered, so after receiving the service demand sent by the terminal device 10, the first device 21 will decompose it into service communication demand and / or service computing power demand, or further translate it into computing resource, and then send these demands or resources to the second device 22 for subsequent allocation or reservation of computing resources. Specifically, see Figures 4-9 for a more detailed description.

[0046] Figure 3 is a method flowchart further illustrating a computing resource configuration method according to an embodiment of the present disclosure. As shown in Figure 3 , the computing resource configuration method applied to the second device 22 can at least include the following steps.

[0047] In step S301, the first message or the second message sent by the first device is received, wherein the first message is used to indicate service computing power demand, and the second message is used to indicate computing resource allocation. As described above, this step can be understood as the opposite step of step S201, and see Figures 4-9 for a more detailed description.

[0048] Figure 4 is a whole flowchart illustrating a computing resource configuration method according to an embodiment of the present disclosure. As shown in Figure 4 , the execution subject of the computing resource configuration method can at least include: a terminal device 10, a first device 21, and a second device 22. The first device 21 can be an orchestrator, a manager, a controller, etc.; the second device 22 can be a cloud platform, a cluster, an infrastructure, a base station, etc. The computing resource configuration method can include the following steps.

[0049] 4.1: The terminal device 10 sends a third message to the first device 21, wherein the third message is used to indicate the service demand. As described above, in order to solve the problem that the service profile in the prior art is mainly a communication type service and does not consider reserving computing resources for other services, the present disclosure enhances the description of the demand of different slices for computing type services and considers the end-to-end service demand of computing and communication fusion on the basis of the original.

[0050] In an embodiment of the present disclosure, the parameters added in the service / slice demand can be as shown in Table 1.

[0051]

[0052]

[0053] Table 1

[0054] 4.2: The first device 21 converts the service demand into computing demand. As described above, the present disclosure reserves resources for both communication and computing, so when converting the service / slice demand, not only the communication demand needs to be considered, but also the computing demand. By dividing the service demand into at least communication demand and computing demand, the amount of demand of the service on communication and computing resources can be more accurately determined to facilitate subsequent corresponding resource allocation.

[0055] Among them, the communication demand can refer to the prior art (for example, RAN Slice Profile), and the present disclosure mainly introduces the computing demand.

[0056] In an embodiment of the present disclosure, the parameters (for example, Computing Service Profile) describing the computing demand can refer to Table 2.

[0057] It should be noted that the first device 21 can be further subdivided, and specific details will be described with reference to Figure 5 which will be further described.

[0058]

[0059]

[0060]

[0061] Table 2

[0062] 4.3a: The first device 21 converts the computing power requirement into computing power resources. As described above, the computing power resources have been obtained in 4.2, and this step converts them into computing power resources to facilitate subsequent resource allocation. The computing power resources can include computing resources, memory resources, storage resources, network resources, and the like.

[0063] In one embodiment of the present disclosure, specific parameters (e.g., computing resource configuration parameter Computing Resource Config) describing computing power resources can be seen from Table 3.

[0064] Parameter name Necessity Description Resource type M Used to identify the resource type to be allocated for the computing task / service >computing O Computing resource >>cpu >>>cpuNumber >>>coreNumber >>>vcpuNumber >>>acrossNode Used to indicate whether to allow across physical nodes >>>acrossNuma Used to indicate whether to allow across NUMA >>gpu >>fpga >>DSP >memory O Memory resource >storage O Storage resource >connectionPoint O Network resource >>cpNumber >>vcpNumber >>throughput

[0065] Table 3

[0066] Among them, for computing resources, the resource type includes central processing unit (CPU), graphics processing unit (GPU), field programmable gate array (FPGA), etc., and the description of the resource type, such as the description of the CPU architecture (x86 or ARM). Further, for detailed resource allocation, when the computing resource is CPU resource, it can be specified by CPU number, CPU core number or VCPU number; when the computing resource is GPU / neural network processing unit (NPU) / tensor processing unit (TPU) resource, it can be specified by floating point operation per second (Flops) / giga floating point operation per second (GFlops) / tera floating point operation per second (TFlops) and the like; when the computing resource is FPGA, it can be specified by logical resource number. For memory resources, it can be specified by memory resource number, such as MB and the like. For storage resources, it can be specified by storage size, such as GB and the like. For network resources, it can be specified by port number, virtual port number or bandwidth required for specific port, such as Mbps and the like.

[0067] Further, when the slice reserves wireless communication related resources, the first device 21, based on the communication demand in the service serviceProfile, according to the relationship between the communication task performance requirement and the corresponding computing demand, further enhances the resource allocation of computing power based on the communication resource allocation of the wireless resource management strategy, increases the type of resources to be allocated, and increases the resource allocation related to computing power in the resource type resourceType, thereby reserving computing power related resources for the base station task of the slice or service.

[0068] In one embodiment of the present disclosure, specific parameters describing the base station task reserving computing power related resources can be seen from Table 4.

[0069]

[0070] Table 4

[0071] In particular, the first device 21 can be composed of a single functional module or a plurality of functional or logical functions independently or jointly, details of which will be described with reference to Figures 6-7 Further description will be made.

[0072] 4.4a: The first device 21 sends a second message to the second device 22, wherein the second message is used to indicate the allocation of computing power resources. As described above, the relevant parameters of the computing power resources (such as Table 3 or Table 4) have been obtained in 4.3a, and this step aims to send the second message carrying these parameters to the second device 22 so that it performs 4.5.

[0073] 4.5: The second device 22 allocates computing power resources. As described above, after receiving the second message, the second device 22 performs resource reservation and allocation based on the relevant parameters of the computing power resources therein to meet the service requirements described in the service profile.

[0074] Optionally, the above step of converting the computing power requirement into computing power resources can also be performed by the second device 22, in particular:

[0075] 4.3b: The first device 21 sends the computing power requirement obtained in 4.2 to the second device 22 in the form of a first message, i.e., the first message is used to indicate the computing power requirement. As described above, in this optional step, the first device 21 does not convert the computing power requirement into computing power resources.

[0076] 4.4b: The second device 22 converts the computing power requirement into computing power resources. As described above, the second device 22 performs the conversion of the computing power requirement into computing power resources, and the relevant parameters of the computing power resources can refer to Tables 3 and 4 described above. In particular, details will be described with reference to Figures 8-9 Further description will be made.

[0077] The other steps are the same as described above and will not be described again.

[0078] The following will be described in combination with Figures 5-9 Further description will be made on 4.2, 4.3a, and 4.4b described above. Figures 5-9 Exemplary description will be made taking the Open Radio Access Network (O-RAN) architecture as an example. First, the main concepts in the O-RAN architecture will be briefly introduced.

[0079] O-RAN is committed to building an open, intelligent, virtualized, and fully interoperable wireless access network architecture. Among them:

[0080] Service Management and Orchestration (SMO): Mainly responsible for: RAN management, core network management, transmission management, end-to-end management.

[0081] E2 Node: A logical node connected by the E2 interface defined by O-RAN.

[0082] Near-RT RIC: Based on the data collected by E2 Node, it provides near real-time wireless resource control and optimization to the base station.

[0083] Non-RT RIC: A logical function of SMO, deployed in SMO.

[0084] A1, O1, O2, E2, Y1 refer to the interfaces in the O-RAN system, used to realize communication and data transmission between different network components.

[0085] Figure 5 is a further flow chart illustrating the method of converting service demand into computing power demand according to the embodiments of the present disclosure. As described in 4.2 above, the step of converting service demand into computing power demand is performed by the first device 21, so the present embodiment involves the execution subject can include: terminal device 10 and first device 21. The first device 21 can be further subdivided into SMO and / or Near-RT RIC, wherein both SMO and Near-RT RIC can perform the conversion of service demand into computing power demand, and the specific method can include the following steps.

[0086] 5.1a: The terminal device 10 sends a third message to the SMO, wherein the third message is used to indicate the service demand. Specifically, the third message can include at least one or more parameters in Table 1. The third message in the following 5.1b, 5.1c is the same, and will not be repeated here.

[0087] 5.2a: The SMO converts the service demand into computing power demand. Specifically, it can be completed by one or more functions in the SMO, including but not limited to Non-RT RIC, new function new Function, NFO, FOCOM, etc.

[0088] Optionally, the conversion of service demand into computing power demand can also be performed by the Near-RT RIC, specifically:

[0089] 5.1b: The terminal device 10 directly sends the third message to the Near-RT RIC. Specifically, the third message can be sent to the Near-RT RIC through the Y1 interface or a newly defined interface.

[0090] 5.2b: Near-RT RIC translates the service requirement into the computing requirement.

[0091] Alternatively,

[0092] 5.1c: The terminal device 10 sends a third message to the Near-RT RIC via the SMO. Specifically, the SMO can send the third message to the Near-RT RIC through the O1 interface; or the Non-RT RIC in the SMO sends the third message to the Near-RT RIC through the A1 interface.

[0093] 5.2c: Same as 5.2b, the Near-RT RIC translates the service requirement into the computing requirement.

[0094] Figure 6 is a further flow chart illustrating a method of translating the computing requirement into the computing resource according to the embodiment one of the present disclosure. The embodiment relates to the execution subject which can include the first device 21 and the second device 22. Wherein the first device 21 is the SMO, and the second device 22 is the O-Cloud or the gNB, the SMO translates the computing requirement into the computing resource. Specifically, the SMO can be further subdivided into the first function and the second function, and both the first function and the second function can perform the translation of the computing requirement into the computing resource. The specific method can include the following steps.

[0095] 6.1a: The Non-RT RIC / new Function (i.e. the first function) translates the computing requirement into the computing resource.

[0096] 6.2a: The Non-RT RIC / new Function sends a second message to the O-Cloud via the NFO / FOCOM (i.e. the second function), wherein the second message is used to indicate the computing resource allocation. Specifically, based on the service interface between the logical functions in the Decouple SMO architecture, the SMO needs to send the translated computing resource configuration parameters to the NFO / FOCOM, and send the computing resource configuration parameters (e.g. Table 3) to the O-Cloud through the enhanced O2 interface (e.g. sending the resource configuration parameters through the NFD, ASD configuration file, or through the configuration request), so as to be subsequently executed by the O-Cloud for the computing resource allocation.

[0097] Alternatively, the second device 22 can also be the gNB, specifically as follows:

[0098] 6.1b: Same as 6.1a, the Non-RT RIC / new Function translates the computing requirement into the computing resource.

[0099] 6.2b: Non-RT RIC / new Function sends a second message directly to gNB, wherein the second message is used to indicate the allocation of computing resource. Specifically, based on the service interface between the logical functions in the Decouple SMO architecture, the converted computing resource configuration parameters need to be sent to OAM, and the enhanced computing resource configuration parameters (e.g., Table 4) are sent to gNB through the enhanced O1 interface, and the gNB protocol stack enhances the allocation of computing resources in addition to the allocation of communication resources.

[0100] Optionally, the step of converting the computing demand into computing resource can also be performed by NFO / FOCOM, specifically:

[0101] 6.1c: NFO / FOCOM (i.e., the second function) converts the computing demand into computing resource.

[0102] 6.2c: NFO / FOCOM sends a second message to O-Cloud, wherein the second message is used to indicate the allocation of computing resource.

[0103] Figure 7 is a further flow chart illustrating the method of converting the computing demand into computing resource according to Embodiment Two of the present disclosure. The present embodiment relates to the execution subject, which can include a first device 21 and a second device 22. Wherein the first device 21 is SMO and Near-RT RIC, the Near-RT RIC performs the step of converting the computing demand into computing resource, and the second device 22 is O-Cloud or gNB. The specific method can include the following steps.

[0104] 7.1a: SMO sends a first message to Near-RT RIC, wherein the first message is used to indicate the computing demand. Specifically, the computing demand (e.g., Table 2) can be sent through the enhanced O1 interface, or based on the Non-RT RIC in SMO through the A1 interface.

[0105] 7.2a: O-Cloud sends the cluster computing capability to Near-RT RIC. Specifically, it can be subscribed by Near-RT RIC, for example, Near-RT RIC subscribes to the current cluster computing capability of O-Cloud through the Notification API interface, including but not limited to: CPU parameters, total number of resources such as CPU / memory / storage / bandwidth, occupied amount of resources, and number of allocatable resources, etc.

[0106] 7.3a: Near-RT RIC converts the computing demand into computing resource. Specifically, the configuration requirements of the computing resource can be, for example, Table 3.

[0107] 7.4a: Near-RT RIC sends a second message to O-Cloud, wherein the second message is used to indicate the computing resource allocation. Specifically, the Near-RT RIC sends the computing resource configuration to the O-Cloud through the Notification API interface according to the current cluster capability learned in 7.2a, so that the O-Cloud performs resource allocation.

[0108] Optionally, in the case of insufficient current O-Cloud resources, the Near-RT RIC can perform 7.5: Near-RT RIC sends computing resource configuration parameters to SMO to select appropriate locations to configure resources through SMO.

[0109] Optionally, the second device 22 can also be a gNB, specifically:

[0110] 7.1b: same as 7.1a, not repeated here.

[0111] 7.2b: gNB sends infrastructure computing power capability to Near-RT RIC. Specifically, the Near-RT RIC can subscribe to the gNB, for example, the Near-RT RIC subscribes to the computing power capability of the infrastructure where the current communication base station is located through the E2 interface, including but not limited to: CPU parameters, total number of resources such as CPU / memory / storage / bandwidth, occupied amount of resources, and number of allocatable resources.

[0112] 7.3b: Near-RT RIC converts computing power demand into computing power resources. Specifically, the communication and computing power demand can be converted into computing resource allocation strategy (e.g., Table 4) based on the service.

[0113] 7.4b: Near-RT RIC sends a second message to gNB, wherein the second message is used to indicate the computing resource allocation. Specifically, the Near-RT RIC can send the computing resource configuration to the gNB through the E2 interface for resource configuration.

[0114] Optionally, in the case of insufficient current gNB infrastructure resources, the Near-RT RIC can also perform 7.5: Near-RT RIC sends computing resource configuration parameters to SMO to select appropriate locations to configure resources through SMO.

[0115] Figure 8 is a further flow chart illustrating a method of converting computing power demand into computing power resources according to Embodiment Three of the present disclosure. The embodiment relates to the execution subject, which can include a first device 21 and a second device 22. Wherein the first device 21 is an SMO or a Near-RT RIC, and the second device 22 is an O-Cloud, which performs the conversion of computing power demand into computing power resources, and the specific method can include the following steps.

[0116] When the first device 21 is SMO, 8.1a-8.3a are performed; when the first device 21 is Near-RT RIC, 8.1b-8.3b or 8.1c-8.5c are performed. Details are as follows:

[0117] 8.1a: When the first device 21 is SMO, the SMO sends a first message to the O-Cloud, wherein the first message is used to indicate the computing power requirement. Specifically, the SMO can send the service computing power requirement (e.g., Table 2) to the O-Cloud through the enhanced O2 interface.

[0118] 8.2a: The O-Cloud converts the computing power requirement into computing power resources. Specifically, the conversion of the computing power requirement into the resource configuration parameter can be completed by the O-Cloud function (IMS / DMS).

[0119] 8.3a: The O-Cloud performs computing power resource allocation. Specifically, the resource allocation can be completed by the O-Cloud function (IMS / DMS).

[0120] Alternatively, the first device 21 can also be a Near-RT RIC, as follows:

[0121] 8.1b: When the first device 21 is a Near-RT RIC, the SMO sends a first message to the O-Cloud via the Near-RT RIC, wherein the first message is used to indicate the computing power requirement. Specifically, the SMO sends the communication service requirement to the Near-RT RIC through the enhanced O1 / A1 interface, and then the Near-RT RIC sends the service computing power requirement (e.g., Table 2) to the O-Cloud through the enhanced Notification API.

[0122] 8.2b: Same as 8.2a, which will not be repeated.

[0123] 8.3b: Same as 8.3a, which will not be repeated.

[0124] Alternatively,

[0125] 8.1c: When the first device 21 is a Near-RT RIC, the SMO sends a third message to the Near-RT RIC, wherein the third message is used to indicate the service requirement. Specifically, the SMO sends the end-to-end service requirement (e.g., Table 1) to the Near-RT RIC through the enhanced O1 / A1 interface.

[0126] 8.2c: The Near-RT RIC converts the service requirement into the computing power requirement.

[0127] 8.3c: Near-RT RIC sends a first message to O-Cloud, where the first message is used to indicate the computing power requirement. Specifically, the Near-RT RIC sends the service computing power requirement (e.g., Table 2) to the O-Cloud through an enhanced Notification API.

[0128] 8.4c: Same as 8.2a, which will not be repeated.

[0129] 8.5c: Same as 8.3a, which will not be repeated.

[0130] Figure 9 is a further flow chart illustrating a method of converting computing power requirement into computing power resource according to Embodiment Four of the present disclosure. The execution subject of the present embodiment can include: a first device 21 and a second device 22. Wherein the first device 21 is an SMO / network management / cloud management or a Near-RT RIC, and the second device 22 is a gNB, and the gNB performs the conversion of the computing power requirement into the computing power resource, and the specific method can include the following steps.

[0131] 9.1a: When the first device 21 is an SMO / network management / cloud management, the SMO / network management / cloud management sends a first message to the gNB, where the first message is used to indicate the computing power requirement. Wherein the network management can be, for example: Operation Administration and Maintenance (OAM), Operation and Maintenance Center (OMC), etc.; the cloud management can be, for example: Network Functions Virtualisation Orchestrator (NFVO), Multi-access Edge Orchestrator (MEO), NFO, FOCOM, etc. Specifically, the SMO can send the service computing power requirement (e.g., Table 2) to the gNB through an enhanced O1 interface.

[0132] 9.2a: The gNB converts the computing power requirement into the computing power resource.

[0133] 9.3a: The gNB performs computing power resource allocation. Specifically, the computing resource allocation can be achieved through protocol stack enhancement (e.g., enhanced control plane function).

[0134] Alternatively, the first device 21 can also be a Near-RT RIC, as follows:

[0135] 9.1b: When the first device 21 is a Near-RT RIC, the SMO / network management / cloud management sends a first message to the gNB via the Near-RT RIC, where the first message is used to indicate the computing power requirement. Specifically, the SMO / network management / cloud management sends the communication algorithm service requirement (e.g., Table 2) to the Near-RT RIC through the enhanced O1 / A1 interface.

[0136] 9.2b: Same as 9.2a, which will not be repeated.

[0137] 9.3b: Same as 9.3a, which will not be repeated.

[0138] Alternatively,

[0139] 9.1c: When the first device 21 is a Near-RT RIC, the SMO / network management / cloud management sends a third message to the Near-RT RIC, where the third message is used to indicate the service requirement. Specifically, the SMO / network management / cloud management sends the end-to-end service requirement (e.g., Table 1) to the Near-RT RIC through the enhanced O1 / A1 interface.

[0140] 9.2c: The Near-RT RIC converts the service requirement into the computing power requirement.

[0141] 9.3c: The Near-RT RIC sends a first message to the gNB, where the first message is used to indicate the computing power requirement. Specifically, the Near-RT RIC can send the service computing power requirement (e.g., Table 2) to the gNB through the enhanced E2 interface.

[0142] 9.4c: Same as 9.2a, which will not be repeated.

[0143] 9.5c: Same as 9.3a, which will not be repeated.

[0144] Figure 10 is a device schematic diagram illustrating a computing power resource configuration apparatus according to an embodiment of the present disclosure. As shown in Figure 10 , the computing power resource configuration apparatus 1000 applied to the first device 21 can at least include the following modules.

[0145] The sending module 1001 is configured to send a first message or a second message to the second device, where the first message is used to indicate the service computing power requirement, and the second message is used to indicate the computing power resource allocation.

[0146] In addition, the following modules can also be included:

[0147] The service receiving module 1002 is configured to receive a third message before sending the first message or the second message to the second device, where the third message is used to indicate the service requirement.

[0148] The demand conversion module 1003 is configured to generate a service communication demand and / or a service computing power demand based on the third message before the first message or the second message is sent to the second device.

[0149] The resource conversion module 1004 is configured to generate a computing power resource based on the service computing power demand before the second message is sent to the second device.

[0150] The first message includes at least one of the following: a service type, a computing data volume, a computing processing time, a computing service start time, a computing service end time, a computing service mode, a computing processing number, a computing time delay budget, a computing reliability, a scaling configuration, a backup configuration, a resource type, a resource description, and a computing power priority.

[0151] The second message includes at least one of the following: a computing resource, a memory resource, a storage resource, and a network resource.

[0152] The third message includes at least one of the following: a service type, a computing data volume, a computing processing time, a computing service start time, a computing service end time, a computing service mode, a computing processing number, a scaling function, a backup function, a resource type, a resource description, a computing power priority, a service end-to-end time delay, and a service reliability.

[0153] Figure 11 FIG. 11 is a device schematic diagram further illustrating a computing power resource configuration device according to an embodiment of the present disclosure. As shown in FIG. 11, the computing power resource configuration device 1100 applied to the second device 22 can at least include the following modules. Figure 11

[0154] The receiving module 1101 is configured to receive a first message or a second message sent by the first device, where the first message is used to indicate a service computing power demand, and the second message is used to indicate a computing power resource allocation.

[0155] In addition, the computing power resource configuration device 1100 applied to the second device 22 can further include the following modules.

[0156] The resource allocation module 1102 is configured to perform a computing power resource allocation based on the second message after receiving the second message sent by the first device.

[0157] The resource conversion allocation module 1103 is configured to generate a computing power resource based on the first message after receiving the first message sent by the first device, and perform a computing power resource allocation based on the computing power resource.

[0158] The first message includes at least one of the following: a service type, a computing data volume, a computing processing time, a computing service start time, a computing service end time, a computing service mode, a computing processing number, a computing time delay budget, a computing reliability, a scaling configuration, a backup configuration, a resource type, a resource description, and a computing power priority. ​

[0159] a second message comprising at least one of: a computing resource, a memory resource, a storage resource, a network resource.

[0160] Figure 12 is a hardware block diagram illustrating an electronic device according to an embodiment of the present disclosure. The electronic device according to an embodiment of the present disclosure at least includes a processor; and a memory for storing computer readable instructions. When the computer readable instructions are loaded and run by the processor, the processor performs the computing resource configuration method as described above.

[0161] Figure 12 The electronic device 1200 shown specifically includes a central processing unit (CPU) 1201, a graphics processing unit (GPU) 1202, and a memory 1203. These units are connected to each other through a bus 1204. The central processing unit (CPU) 1201 and / or the graphics processing unit (GPU) 1202 can be used as the processor described above, and the memory 1203 can be used as the memory for storing computer readable instructions described above. In addition, the electronic device 1200 can further include a communication unit 1205, a storage unit 1206, an output unit 1207, an input unit 1208, and an external device 1209, which are also connected to the bus 1204.

[0162] Figure 13 is a schematic diagram illustrating a computer program product according to an embodiment of the present disclosure. As shown in Figure 13 The computer program product 1300 according to an embodiment of the present disclosure has a computer program 1301 stored thereon. When the computer program 1301 is executed by a processor, the computing resource configuration method described with reference to the above figures is performed. The computer program product includes, but is not limited to, for example, volatile memory and / or non-volatile memory. The volatile memory may, for example, include random access memory (RAM) and / or cache memory, etc. The non-volatile memory may, for example, include read-only memory (ROM), hard disk, flash memory, optical disc, magnetic disc, etc.

[0163] In the above, the computing resource configuration method, device, electronic device, and computer program product according to an embodiment of the present disclosure are described with reference to the accompanying drawings. According to the computing resource configuration method of the present disclosure, for the case of co-deployment of services and wireless network functions, the present disclosure further enhances the slice or base station service to meet the general performance requirements. On the basis of the decomposition of traditional slice service requirements into communication requirements, the present disclosure enhances the decomposition of service or slice general performance requirements into computing power requirements, and enhances the allocation of wireless computing power related resources based on existing wireless resource allocation strategies, so as to reserve computing power and network resources according to service requirements, and guarantee multi-dimensional resources for specific services or slices.

[0164] Those skilled in the art can realize the units and algorithm steps of each example described in connection with the embodiments disclosed herein can be realized in electronic hardware, or a combination of computer software and electronic hardware. Whether the functions are performed in hardware or software depends on the specific application and design constraints. Those skilled in the art can realize the described functions by various methods, and the implementation should not be limited to a specific method. The above description is only a specific implementation of the present disclosure and not intended to limit the protection scope of the present disclosure.

[0165] The above describes the basic principles of the present disclosure in conjunction with specific embodiments, but it should be noted that the advantages, benefits, effects and the like mentioned in the present disclosure are only examples and not limitations, and these advantages, benefits, effects and the like cannot be considered as the various embodiments of the present disclosure must have. In addition, the above specific details of the disclosure are only for the purpose of example and for the purpose of understanding, and the above details do not limit the present disclosure to the above specific details.

[0166] The block diagrams of the devices, apparatuses, equipment, systems involved in the present disclosure are only illustrative examples and are not intended to require or imply the connection, arrangement, configuration shown in the block diagram. As those skilled in the art will recognize, these devices, apparatuses, equipment, systems can be connected, arranged, configured in any manner. Words such as "include", "contain", "have" and the like are open-ended words, which means "including but not limited to", and can be used interchangeably. The words "or" and "and" used herein mean the word "and / or", and can be used interchangeably unless the context clearly indicates otherwise. The word "such as" used herein means the phrase "such as but not limited to", and can be used interchangeably.

[0167] In addition, as used herein, "or" used in a list of items, starting with "at least one of the items, indicates a disjunctive list, so that, for example, "at least one of A, B, or C" means A or B or C, or AB or AC or BC, or ABC (i.e., A and B and C). In addition, the phrase "exemplary" does not mean that the described example is preferred or better than other examples.

[0168] It should also be noted that in the systems and methods of the present disclosure, the components or steps can be decomposed and / or recombined. These decompositions and / or recombination should be considered as equivalent solutions of the present disclosure.

[0169] Various changes, modifications, and alterations to the techniques described herein can be made without departing from the teachings of the attached claims. Moreover, the scope of the claims of the present disclosure is not limited to the particular aspects described herein. Rather, the scope of the claims of the present disclosure includes all alternatives, modifications, and alterations that can result from changing the components of the processes, machines, compositions of matter, means, methods, or steps described herein in their entirety to those which are different than the recited claims. Accordingly, the attached claims are not intended to be limited to the aspects described herein unless so limited by the term "means," which is expressly intended to be limiting only to the extent that it is intended to be limiting based on its legal definition.

[0170] The above description of the disclosed aspects is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein can be applied to other aspects without departing from the scope of the disclosure. Thus, the present disclosure is not intended to be limited to the aspects shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

[0171] The above description has been presented for the purpose of illustration and description. Furthermore, this description is not intended to limit the embodiments of the present disclosure to the forms disclosed herein. Although various example aspects and embodiments have been discussed above, those of ordinary skill in the art will appreciate a variety of modifications, alternatives, permutations, additions, and sub-combinations, which fall within the scope of the appended claims.

Claims

1. A computing resource allocation method, characterized in that, Applied to a first device, the method comprises: sending a first message or a second message to a second device, wherein the first message is used to indicate a service computing power requirement, and the second message is used to indicate a computing power resource allocation. 2.The computing resource allocation method of claim 1, wherein, The method further comprises: before the sending of the first message or the second message to the second device, receiving a third message, wherein the third message is used to indicate a service requirement. 3.The computing resource allocation method of claim 2, wherein, The method further comprises: before the sending of the first message or the second message to the second device, generating a service communication requirement and / or the service computing power requirement based on the third message.

4. The computing power resource configuration method of claim 1, wherein: the second message comprises a computing power resource, and the computing power resource is used for the computing power resource allocation, and the computing power resource comprises at least one of a computing resource, a memory resource, a storage resource, and a network resource, wherein the computing power resource is generated based on the service computing power requirement.

5. The computing resource allocation method of any one of claims 1 to 4, wherein, The first message comprises at least one of: a service type, a computing data volume, a computing processing time, a computing service start time, a computing service end time, a computing service mode, a computing processing number, a computing time delay budget, a computing reliability, a scaling configuration, a backup configuration, a resource type, a resource description, and a computing power priority.

6. The computing resource allocation method of claim 2 or 3, wherein, The third message comprises at least one of: a service type, a computing data volume, a computing processing time, a computing service start time, a computing service end time, a computing service mode, a computing processing number, a scaling function, a backup function, a resource type, a resource description, a computing power priority, a service end-to-end time delay, and a service reliability.

7. A computing resource allocation method, characterized in that, Applied to a second device, the method comprises: receiving a first message or a second message sent by a first device, wherein the first message is used to indicate a service computing power requirement, and the second message is used to indicate a computing power resource allocation. 8.The computing resource allocation method of claim 7, wherein, The method further comprises: after the receiving of the second message sent by the first device, performing the computing power resource allocation based on the second message, wherein the second message comprises a computing power resource, and the computing power resource comprises at least one of a computing resource, a memory resource, a storage resource, and a network resource, wherein the computing power resource is generated based on the service computing power requirement. 9.The computing resource allocation method of claim 7, wherein, The method further comprises: after the receiving of the first message sent by the first device, generating the computing power resource based on the first message; performing the computing power resource allocation based on the computing power resource.

10. The computing resource allocation method of any one of claims 7 to 9, wherein, The first message comprises at least one of: a service type, a computing data volume, a computing processing time, a computing service start time, a computing service end time, a computing service mode, a computing processing number, a computing time delay budget, a computing reliability, a scaling configuration, a backup configuration, a resource type, a resource description, and a computing power priority.

11. A computing resource allocation apparatus, characterized by comprising: Applied to a first device, the apparatus comprises: a sending module, configured to send a first message or a second message to a second device, wherein the first message is used to indicate a service computing power requirement, and the second message is used to indicate a computing power resource allocation.

12. A computing resource allocation apparatus, characterized by comprising: Applied to a second device, the apparatus comprises: A receiving module is configured to receive a first message or a second message sent by the first device, wherein the first message is used to indicate a service computing power requirement, and the second message is used to indicate a computing power resource allocation.

13. An electronic device, comprising: The computer program product comprises a computer readable storage medium, and the computer readable storage medium stores the computer program. The computer readable storage medium stores the computer program. The computer program is executed by a processor to implement the computing power resource allocation method in any one of claims 1 to 10. The computer program is executed by a processor to implement the computing power resource allocation method in any one of claims 1 to 10.

14. A computer program product comprising a computer program, characterized in that, ​

Images