Energy-saving affiliation and placement of clouded network functions
By defining policy features in the open cloud domain and mapping them to the operating mode of open cloud resources, the energy consumption problem of cloud network functions in the open cloud is solved, and energy-saving classification and efficient attribution and placement decisions for O-Cloud resources are realized.
Patent Information
- Application Number
- CN202411454786.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-10-17
- Filing Date
- 2024-10-17
- Publication Date
- 2025-04-18
AI Technical Summary
The prior art is difficult to effectively reduce the energy consumption of cloud network functions (NF) in open cloud (O-Cloud), especially when making home and placement decisions, it is difficult to accurately identify O-Cloud resource capabilities that meet cloud NF deployment resource requirements and energy-saving strategies.
By defining policy characteristics in the open cloud domain, defining policy standards and policies associated with policy characteristics, mapping policies to the operating mode of open cloud resources, and classifying open cloud resources in cluster templates, we can realize the transformation and mode implementation of energy-saving attributes.
The energy-saving strategies in the O-Cloud and Service Management and Orchestrator (SMO) domains are transformed into clear energy consumption level ranges, thereby classifying O-Cloud resources energy savings, improving the energy efficiency of cloud-based NF homes and placement decisions.
Smart Images

Figure CN119854916A_ABST
Abstract
Description
Technical Field
[0001] Some example embodiments generally relate to mobile or wireless telecommunication systems, such as Long Term Evolution (LTE) or fifth generation (5G) New Radio (NR) access technology, or above 5G, or sixth generation (6G) access technology, or other communication systems. For example, certain example embodiments may relate to apparatus, systems and / or methods for energy-efficient home and placement of cloudified network functions (NFs). Background Art
[0002] Examples of mobile or wireless telecommunication systems may include Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), Long Term Evolution (LTE) Evolved UTRAN (E-UTRAN), LTE-Advanced (LTE-A), MulteFire, LTE-A Pro, fifth generation (5G) radio access technology or new radio (NR) access technology and / or sixth generation (6G) radio access technology. Fifth generation (5G) and sixth generation (6G) wireless systems refer to next generation (NG) radio systems and network architectures. 5G and 6G network technologies are primarily based on new radio (NR) technology, but 5G / 6G (or NG) networks may also be built on E-UTRAN radio. It is estimated that NR can provide bit rates at or above the level of 10-20Gbit / s and can support at least enhanced mobile broadband (eMBB) and ultra-reliable low latency communications (URLLC) and massive machine type communications (mMTC). NR is expected to provide extremely high bandwidth and ultra-robust, low latency connectivity as well as massive networking to support the Internet of Things (IoT). Summary of the invention
[0003] Some example embodiments may be directed to a method. The method may include defining a feature of a policy in an open cloud domain. The method may also include defining a policy standard and a policy associated with the feature of the policy. The method may also include mapping the policy to at least one operation mode of an open cloud resource. Additionally, the method may include classifying the open cloud resources in a cluster template. Furthermore, the method may include sending a mapping of the feature, the policy, the policy standard, and the policy to a service management and orchestrator or an open cloud.
[0004] Other example embodiments may be directed to an apparatus. The apparatus may include at least one processor and at least one memory storing instructions. The instructions, when executed by the at least one processor, cause the apparatus to at least define characteristics of a policy in an open cloud domain. The apparatus is also caused to define policy standards and policies associated with the characteristics of the policy. The apparatus is also caused to map the policy to at least one operating mode of an open cloud resource. In addition, the apparatus may be caused to classify the open cloud resources in a cluster template. In addition, the apparatus may be caused to send a mapping of characteristics, policies, policy standards, and policies to a service management and orchestrator or an open cloud.
[0005] Other example embodiments may be directed to an apparatus. The apparatus may include components for defining features of a policy in an open cloud domain. The apparatus may also include components for defining policy criteria and policies associated with the features of the policy. The apparatus may also include components for mapping the policy to at least one operating mode of the open cloud resources. Additionally, the apparatus may include components for classifying the open cloud resources in a cluster template. Additionally, the apparatus may include components for sending features, policies, policy criteria, and mappings of the policies to a service management and orchestrator or an open cloud.
[0006] According to other example embodiments, a non-transitory computer readable medium may be encoded with instructions that, when executed in hardware, may perform a method. The method may include defining features of a policy in an open cloud domain. The method may also include defining policy standards and policies associated with the features of the policy. The method may also include mapping the policy to at least one operating mode of an open cloud resource. Additionally, the method may include classifying the open cloud resources in a cluster template. Furthermore, the method may include sending a mapping of features, policies, policy standards, and policies to a service management and orchestrator or an open cloud.
[0007] Other example embodiments may be directed to a computer program product for performing a method. The method may include defining features of a policy in an open cloud domain. The method may also include defining policy criteria and policies associated with the features of the policy. The method may also include mapping the policy to at least one operating mode of an open cloud resource. Additionally, the method may include classifying the open cloud resources in a cluster template. Furthermore, the method may include sending a mapping of the features, policies, policy criteria, and policies to a service management and orchestrator or an open cloud.
[0008] Other example embodiments may be directed to an apparatus that may include circuitry configured to define features of a policy in an open cloud domain. The apparatus may also include circuitry configured to define policy criteria and policies associated with the features of the policy. The apparatus may also include circuitry configured to map the policy to at least one operating mode of the open cloud resources. Additionally, the apparatus may include circuitry configured to classify the open cloud resources in a cluster template. Additionally, the apparatus may include circuitry for sending features, policies, policy criteria, and mappings of policies to a service management and orchestrator or an open cloud.
[0009] Some example embodiments may be directed to a method. The method may include receiving energy-saving attributes including a mapping of features, policies, policy criteria, and policies at a service management and orchestration or an open cloud. The method may also include performing a home decision and placing a network function deployment on an open cloud node cluster based on the energy-saving attributes.
[0010] Other example embodiments may be directed to an apparatus. The apparatus may include at least one processor and at least one memory storing instructions. The instructions, when executed by the at least one processor, cause the apparatus to receive energy-saving attributes including mappings of features, policies, policy criteria, and policies at least at a service management and orchestration device or an open cloud. The apparatus is also caused to perform a home decision based on the energy-saving attributes and place a network function deployment on an open cloud node cluster.
[0011] Other example embodiments may be directed to an apparatus. The apparatus may include components for receiving energy-saving attributes including features, policies, policy criteria, and mappings of policies at a service management and orchestration or an open cloud. The apparatus may also include components for performing a home decision based on the energy-saving attributes and placing a network function deployment on an open cloud node cluster.
[0012] According to other example embodiments, a non-transitory computer readable medium may be encoded with instructions that, when executed in hardware, may perform a method. The method may include receiving energy-saving attributes including a mapping of features, policies, policy criteria, and policies at a service management and orchestration device or an open cloud. The method may also include performing a home decision based on the energy-saving attributes and placing a network function deployment on an open cloud node cluster.
[0013] Other example embodiments may be directed to a computer program product for performing a method. The method may include receiving, at a service management and orchestrator or an open cloud, energy conservation attributes including a mapping of features, policies, policy criteria, and policies. The method may also include performing a home decision based on the energy conservation attributes and placing a network function deployment on an open cloud node cluster.
[0014] Other example embodiments may be directed to an apparatus that may include a circuit system configured to receive energy-saving attributes including features, policies, policy criteria, and mappings of policies at a service management and orchestration device or an open cloud. The apparatus may also include a circuit system configured to perform a home decision based on the energy-saving attributes and place a network function deployment on an open cloud node cluster. BRIEF DESCRIPTION OF THE DRAWINGS
[0015] For a proper understanding of the example embodiments, reference should be made to the accompanying drawings, in which:
[0016] Figure 1 Examples of Service Management and Orchestration (SMO) and Open Cloud (O-Cloud) relationships and responsibilities are shown in accordance with certain example embodiments.
[0017] Figure 2 A summary of example energy conservation problems and solutions according to certain example embodiments is presented.
[0018] Figure 3 An example table of high-level policies with characteristics and criteria is shown, according to certain example embodiments.
[0019] Figure 4 Examples of policies defining policy criteria in accordance with certain example embodiments are shown.
[0020] Figure 5 An example of a cluster is shown in accordance with certain example embodiments.
[0021] Figure 6 An example schema implementation output based on a cluster example is shown according to some example embodiments.
[0022] Figure 7 Examples of energy saving attributes in a cluster template are shown in accordance with certain example embodiments.
[0023] FIG. 8( a ) shows an example of cluster provisioning, according to certain example embodiments.
[0024] FIG. 8( b ) shows another example of cluster provisioning, in accordance with certain example embodiments.
[0025] Fig. 9 Example deployment descriptors and artifacts with ES support are shown according to certain example embodiments.
[0026] Fig.10 Examples of input of data types to a cluster template are shown, according to certain example embodiments.
[0027] Fig.11 An example cluster template for cluster provisioning shown in FIG. 8( a ) is shown, in accordance with certain example embodiments.
[0028] Fig.12 An example cluster template for cluster provisioning shown in FIG. 8( b ) is shown, in accordance with certain example embodiments.
[0029] Fig.13 An example O-Cloud cluster configuration for the cluster provisioning shown in FIG. 8( a ) is shown in accordance with certain example embodiments.
[0030] Fig.14 An example flow chart of a method according to certain example embodiments is shown.
[0031] Fig.15 An example flow chart of another method according to certain example embodiments is shown.
[0032] Fig.16 A collection of apparatuses according to certain example embodiments is shown. DETAILED DESCRIPTION
[0033] It will be readily appreciated that the components of certain example embodiments as generally described and illustrated herein may be arranged and designed in a variety of different configurations. The following is a detailed description of some example embodiments of systems, methods, apparatuses, and computer program products for energy-efficient home and placement of cloudified network functions (NFs).
[0034] The features, structures, or characteristics of the example embodiments described in this specification may be combined in any suitable manner in one or more example embodiments. For example, the use of the phrases "certain embodiments," "example embodiments," "some embodiments," or other similar language in this specification means that specific features, structures, or characteristics described in connection with the embodiments may be included in at least one embodiment. Therefore, the appearance of the phrases "in certain embodiments," "example embodiments," "in some embodiments," "in other embodiments," or other similar language in this specification does not necessarily refer to the same set of embodiments, and the features, structures, or characteristics may be combined in any suitable manner in one or more example embodiments. In addition, the terms "base station," "cell," "node," "gNB," "network," or other similar language in this specification may be used interchangeably.
[0035] As used herein, “at least one of the following elements: ” and “at least one of ” and similar expressions, where a list of two or more elements is connected by “and” or “or”, mean at least any one element, or at least two or more elements, or at least all the elements.
[0036] The Open Radio Access Network (O-RAN) provides various energy-saving examples and potential solutions for carriers and cells with off / on and radio frequency (RF) channel off / on. These examples focus on the network side by proposing solutions to reduce energy consumption. Another area of energy saving is within the open cloud (O-Cloud) where the cloudified NF is deployed. For example, the O-Cloud can be a cloud computing platform that includes a set of physical infrastructure nodes that meet the requirements of the O-RAN to carry related O-RAN functions (e.g., near real-time RAN intelligent controller (near-RT RIC), O-RAN central unit control plane (O-CU-CP) and O-RAN central unit user plane (O-CU-UP) and O-RAN distributed unit (O-DU)), supporting software components (e.g., operating system, virtual machine monitor, container runtime, etc.) and appropriate management and orchestration functions. In addition, the cloudified NF can correspond to RAN NF software that can be deployed in the O-Cloud via one or more NF deployments, and the NF deployment can correspond to the software deployment on the O-Cloud resources that implement all or part of the cloudified NF. Resources are defined in the O-Cloud infrastructure as resources that can be provisioned and managed through abstraction. The O-Cloud infrastructure can have multiple types of resources, including, for example, physical resources and logical resources. A physical resource is defined as a resource that has a representation in the real world. A logical resource is defined as a resource that uses multiple physical resources, or parts of physical resources, or multiple software entities. Resources can be assigned to an orchestrator that will deploy workloads for resource consumption.
[0037] Since data centers may consume about 9% of the energy consumption in mobile networks, it may be beneficial to make effective decisions on the home and placement of cloudified NFs to reduce O-Cloud energy consumption. Figure 1 An example of the Service Management and Orchestration (SMO) and O-Cloud (i.e., O-Cloud Infrastructure Management Service (IMS) and O-Cloud Deployment Management Service (DMS)) relationships and responsibilities for the ownership and placement of cloudified NFs according to certain example embodiments is shown. In certain example embodiments, DMS may refer to a logical service provided by O-Cloud for managing the lifecycle of deployments using cloud resources, and SMO may refer to a component that oversees handling all orchestration, management, and automation processes to monitor and control RAN components. Additionally, IMS may include a logical service provided by O-Cloud that provides an interface to orchestrate the O-Cloud lifecycle processes and other operational processes with the NFs it may host.
[0038] like Figure 1As shown, the SMO may be responsible for making affiliation decisions, which may cause the SMO to select an appropriate O-Cloud node cluster that matches the capabilities requested for a particular NF deployment. The SMO may also determine a specific DMS that the SMO deems suitable for NF deployment. In addition, the O-Cloud may include multiple DMSs. In some example embodiments, there may be a single IMS for the O-Cloud that manages all resources of the DMS and resources that are not allocated to any DMS in the O-Cloud. (Multiple) O-Cloud DMSs may be responsible for deciding the placement of workloads for NF deployments. This decision may be based on the SMO's affiliation decision within the (multiple) O-Cloud node cluster and other NF deployment requirements received by the SMO through the O2dms. The O2 interface may refer to an interface associated with a set of O-Cloud services provided by the O-Cloud platform to the SMO.
[0039] The O-Cloud node cluster can be composed of a collection of mutually cooperating O-Cloud nodes, interconnected by a collection of interconnected O-Cloud node cluster networks. The O-Cloud node may also include a network connection (physical and / or logical) computer or a network connection termination function. The O-Cloud node may be supplied to the O-Cloud node cluster by the IMS, and the O-Cloud node may be an abstract resource open to the O2ims based computing node inside the cloud infrastructure. The O-Cloud node may also be a basic computing resource identifier used to execute a workload, and may be a rented physical or logical server connected to the O-Cloud network. The O-Cloud node may be supplied (e.g., rented) from an O-Cloud resource pool with an assigned operating system and cluster software to a managed O-Cloud node cluster.
[0040] As described herein, certain example embodiments may provide a collaborative solution to make the attribution and placement of cloudified NF decisions more efficient with respect to O-Cloud energy consumption. To achieve such a solution, certain example embodiments may identify various parts that may have an impact on the energy efficiency of the attribution and placement decisions of cloudified NFs. For example, some of these parts may include energy-saving policy conversion, energy-saving-based resource classification (e.g., node groups), and / or NF deployment lifecycle management (e.g., attribution). According to certain example embodiments, an O-Cloud node group may include a set of O-Cloud nodes within an O-Cloud node cluster that may be considered equal by certain parties (such as, for example, an O-Cloud node cluster scheduler). These O-Cloud nodes may be interconnected by a set of O-Cloud node cluster networks and an optional set of O-Cloud node group networks. O-Cloud nodes may generally have similar capabilities and features exposed from the computing, storage, and network resources they use. In addition, node clusters may be deployed locally at a cloud site or distributed across multiple cloud sites; but they may generally be located within an O-Cloud. Furthermore, attribution may include a process for selecting an appropriate DMS, and there may be a function within the SMO to select an appropriate cluster of O-Cloud nodes that matches the capabilities requested for the NF(s) deployment, and to identify a specific DMS that the SMO deems appropriate for the NF deployment.
[0041] Figure 2 A summary of example energy saving problems and solutions according to certain example embodiments is shown. Figure 2 As shown, an energy saving problem may involve energy saving policies and requirements that can be expressed in different layers at SMO and O-Cloud. These policies may be generated from different sources, and the policies of each layer may be expressed in different contexts and semantics. Therefore, it may be difficult to achieve autonomous and consistent conversion of each layer policy and identify where the enforcement function can be applied. Another problem may involve the classification of O-Cloud resources within the cluster for energy-saving attribution and placement of cloudified NF deployment. For example, for cluster provisioning in O-Cloud, a set of specific requirements may be provided by a containerized network function (CNF) provider to the O-Cloud operator to host cloudified NFs. Cluster templates can be used to specify these requirements for O-Cloud cluster provisioning. However, there is currently no method to classify O-Cloud resources within a cluster and detect which O-Cloud node group (NG) within the cluster is the best candidate for hosting cloudified NF deployment in terms of energy consumption.
[0042] like Figure 2As shown, another issue may involve making a home decision for a cloudified NF. In this regard, the SMO may select an appropriate DMS in the O-Cloud and an O-Cloud node cluster that matches the requested capabilities for that cloudified NF deployment. The DMS may be responsible for the placement of the NF deployment. If the requested capabilities for the cloudified NF deployment require energy conservation, it may be necessary to efficiently and accurately identify the O-Cloud resource capabilities that meet the cloudified NF deployment resource requirements and energy conservation policies.
[0043] In view of the various problems described above, certain example embodiments may provide methods for converting energy-saving policies in O-Cloud and SMO domains into explicit ranges (e.g., mode implementations) of different energy consumption levels to classify O-Cloud resources (e.g., node groups) for energy saving. Certain example embodiments may also introduce specific energy-saving (ES) attributes (such as, for example, ES cluster tags, (multiple) ES modes, time, location, etc.) into cluster templates to classify node groups. In other example embodiments, SMO or network function orchestration (NFO) may use cluster tags and (multiple) ES mode attributes to effectively and accurately make attribution and placement decisions. In some example embodiments, NFO may include a logical service of SMO that coordinates between O-Clouds to manage deployment lifecycle events, open-loop and closed-loop operation processes.
[0044] As an example solution to the above problem, certain example embodiments may provide energy policy conversion and pattern implementation. For example, by defining features of low-level policies (e.g., O-Cloud policies related to specific methods and details for achieving high-level goals (SMO policies)) in the O-Cloud domain, defining pattern standards, and mapping low-level policies into patterns, example solutions for energy-saving policy conversion and pattern implementation between O-Cloud and SMO can be implemented. The methods described herein may, for example, refer to techniques for implementing energy-saving features in O-Cloud. The feature may include a data tag on which criteria for a policy may be built, and a policy may include a collection of rules or criteria to achieve energy saving for O-Cloud resources using energy-saving features. In addition, a pattern may refer to a comprehensive range of different energy consumption levels achieved by (multiple) different sets of policies applied together.
[0045] In energy policy transitions and mode implementations, characteristics for a policy may be defined. For example, in certain example embodiments, characteristics may include a power savings rate corresponding to the amount of power saved by the policy during a specific (e.g., predefined) time period. In other example embodiments, characteristics may include resource availability, which defines the availability of O-Cloud resources (e.g., central processing unit (CPU), memory, hardware (HW), accelerators, etc.) when the policy is applied. In further example embodiments, characteristics may include time windows during which a policy or mode may be activated, and may include the location of cloud sites supporting virtual RAN functions (e.g., cloudified NFs). In other example embodiments, other reasonable characteristics for energy policy transitions and mode implementations may be added and considered.
[0046] In energy policy conversion and mode implementation, policies and policy criteria may also be defined. For example, high-level policies may be defined based on the value of certain features based on certain thresholds or ranges (eg, criteria). Figure 3 An example table of high-level policies (e.g., SMO policies related to comprehensive goal(s) that focus on the "what" without detailed implementation details at a higher level of abstraction) with features and criteria according to certain example embodiments is shown. Figure 3 As shown, three strategies may be considered, including strategies a, b, and c, for example. However, in other example embodiments, more or fewer strategies than the three strategies shown may be applicable. In addition, Figure 3 An example standard with thresholds / ranges for each of policies a, b, and c is shown, and each policy is associated with certain characteristics related to O-Cloud resources, including, for example, power saving rate (%), CPU availability (%), memory availability (%), hardware accelerator (HW acc) availability (%), time window, and location. In addition, Figure 4A method is shown showing on / enabled / allowed / active, off / disabled / not allowed / inactive, and any / don't care / emoji / neutral policies according to policy criteria defined in certain embodiments. This unique option provides specific criteria for policy transitions between high-level and low-level policies. When the energy saving policy is set to "on / enabled / allowed / active", it converts to a low-level policy where O-Cloud resources are configured to achieve the greatest possible energy savings and use the least possible O-Cloud and data center resources, with a time window that depends on the business load pattern at a specific site. When the energy saving policy is set to "off / disabled / not allowed / inactive", it converts to a low-level policy where O-Cloud resources are configured to achieve no energy savings, and O-Cloud and data center resource energy savings are disabled or turned off at any time during a 24-hour time window at a specific site. When the energy saving policy is set to "any / don't care / emoji / neutral", it converts to a low-level policy where O-Cloud resources are configured to the O-Cloud policy best effort energy saving capability, with a time window that depends on the business load pattern at a specific site.
[0047] Figure 5 shows an example of a cluster according to certain example embodiments, and Figure 6 An example mode implementation output based on a cluster example is shown according to some example embodiments. Figure 6 As shown, the mode implementation outputs may include performance mode, balance mode, and energy saving mode. A mode may refer to a comprehensive energy consumption range achieved by different sets of policies applied together. In addition, a mode may correspond to a range of energy consumption defined by a cloud operator or network service provider. The operator may define a greater or lesser number of modes, with optional names. In energy policy conversion and mode implementation, mode implementation may be performed. To implement these modes, Figure 5 The low-level policies shown in can be mapped to Figure 3 For example, a mode can be implemented by mapping low-level policies to high-level policies. In some example embodiments, when there are a large number of low-level policies, the low-level policies may be preferably grouped (e.g., based on similarities or conditions satisfied in the criteria) and then mapped to the appropriate high-level policies. By performing this grouping, complexity can be reduced. For example, Figure 5 and Figure 6 As shown in , low-level strategies 1, 3 and 10 have power saving rates, resource availability and time windows according to thresholds defined for performance mode. In addition, strategies 4, 6, 7 and 9 can be defined for balanced mode, and strategies 2, 5 and 8 can be defined for energy-saving mode.
[0048] As another example solution to the above problem, certain example embodiments may provide for the implementation of ES attributes into cluster templates. In order to classify O-Cloud resources (e.g., node groups) in cluster templates, certain attributes may be defined, including, for example, patterns and cluster labels. The patterns may be derived as described above, and the cluster labels may represent attributes defined in the deployment descriptor of the NF deployment. The deployment descriptor may describe deployment options that have been verified by the solution provider of the application. The deployment descriptor may include design-time information and data describing the application, and is used by the SMO as input for the deployment of the application workload.
[0049] Figure 7 An example of ES attributes in a cluster template according to some example embodiments is shown. Figure 7 As shown, according to the cluster template, cluster X supports all three modes. In some example embodiments, there may be various options on how the cluster can be provisioned. For example, FIG. 8( a) shows that the cluster can be provisioned as part of a static mode NG, which can be created as NG-1, NG-2, and NG-3 in cluster X and assigned each of their corresponding modes. Alternatively, FIG. 8( b) shows that the cluster can be provisioned as part of a dynamic mode NG, where the mode of the NG can be changed to Perf / Eco / Bal as needed.
[0050] As additional example solutions to the above problems, certain example embodiments may provide cluster tag(s) and ES mode attributes for attribution. As part of the SMO NF deployment process, the SMO may use the ES attributes from the above example solutions, as well as cluster templates or ES attributes available to the SMO. For example, the SMO may use such attributes to efficiently perform and accurately place NF deployments on specific O-Cloud node clusters that support a wide range of energy-saving features.
[0051] In certain example embodiments, the NF deployment may be deployed on an O-Cloud process where the SMO receives an instantiation request. The instantiation request may be received by the SMO from a network function installation project manager. The network function installation project manager may correspond to an operator that designs each NF instance. In addition, the instantiation request may include attribution requirements regarding the location where the NF deployment needs to be instantiated (e.g., the instantiation request may identify a target O-Cloud node cluster) and / or relative constraints on the instantiation of the NF deployment. However, in other example embodiments, the instantiation request may not contain attribution location information (e.g., target O-Cloud). In such a case, the SMO may use the deployment descriptor and NF deployment artifacts to determine on which O-Cloud node cluster to instantiate the NF deployment. For example, Fig. 9 Example deployment descriptors and artifacts with ES support according to certain example embodiments are shown. In addition, NF deployment artifacts can be described as cloud native descriptors and cluster templates. In certain example embodiments, NF deployment descriptors can include design-time information and data that describe applications and are used by SMO as input for deployment of application workloads. In addition, cloud native deployment files can correspond to artifacts that describe O-Cloud resources. In addition, Fig.10 An example of inputting a data type into a cluster template according to certain example embodiments is shown. Fig.10 As shown, the input data type can be NF deployment descriptor, cloud native descriptor file, and deployment strategy.
[0052] Fig.11 shows an example cluster template for cluster provisioning shown in FIG. 8( a ) according to certain example embodiments, and Fig.12 An example cluster template for cluster provisioning shown in FIG. 8( b ) is shown, in accordance with certain example embodiments.
[0053] also, Fig.13 An example O-Cloud cluster configuration for cluster provisioning shown in FIG. 8( a) is shown in accordance with certain example embodiments. Fig.13 As shown, a cluster template or descriptor may include information of an O-Cloud node cluster as a declarative target configuration of the node cluster. A cluster template may include an O-Cloud internal configuration for how the node cluster is built and configured based on O-Cloud internal resources and software. A cluster template may also include the above-mentioned set of energy-saving attributes as part of the ES attributes in the cluster template.
[0054] In certain example embodiments, ES attributes may be configured within a node cluster and exposed to the SMO via an O2ims interface (e.g., an O2 interface). The O2 interface may be an open logical interface within the O-RAN architecture that provides secure communication between the SMO and the O-Cloud. The O2 interface may enable management of the O-Cloud infrastructure and deployment lifecycle management of the O-RAN cloudified NFs running on the O-Cloud. In other words, the O2 interface may provide a platform for resource and workload management. In addition, the O2 interface may consist of services provided by the SMO and services provided by the O-Cloud.
[0055] According to certain example embodiments, the creation of cluster templates can be accomplished by a technical team with knowledge of O-Cloud available resources and application providers (e.g., NF deployment providers). In addition, in some example embodiments, cluster templates can be tested through validation and added to O-Cloud and SMO repositories.
[0056] Fig.14 An example flow chart of a method according to certain example embodiments is shown. In an example embodiment, Fig.14 The method may be performed by a network entity or a plurality of network element groups in a 3GPP system (such as LTE or 5G-NR). For example, in an example embodiment, Fig.14 The method can be performed by an O-Cloud service (e.g., IMS) or a microservice in O-Cloud or SMO, similar to Fig.16 One of the devices 10 or 20 shown in .
[0057] like Fig.14 As shown, the method may include defining characteristics of a policy in an open cloud domain at 1400. The method may also include defining policy standards and policies associated with the characteristics of the policy at 1405. The method may also include mapping the policy to at least one operation mode of the open cloud resources at 1410. In addition, the method may also include classifying the open cloud resources into cluster templates at 1415. In addition, the method may also include sending the mapping of the characteristics, policies, policy standards, and policies to a service management and orchestrator or an open cloud at 1420.
[0058] According to some example embodiments, the characteristics may include a power saving rate of power saved by the policy during a predetermined time period, resource availability of open cloud resources, a time window during which the policy or at least one operating mode may be activated, or a location of a cloud site supporting a virtual radio access network function. In other example embodiments, any other reasonable characteristics may be included and considered. According to some example embodiments, the policies and policy criteria may be defined based on values, thresholds, or ranges. According to other example embodiments, the policy criteria are defined by at least one of on / off, any / don't care, emoji, and neutral.
[0059] In certain example embodiments, at least one operating mode may be a combined range of energy consumption achieved by different policies applied together. In some example embodiments, at least one operating mode may include performance, balance, or energy saving. In other example embodiments, the method may further include grouping policies and additional policies based on similarities or conditions that meet policy criteria. In other example embodiments, the classification of open cloud resources or cluster nodes is based on at least one of an operating mode or a cluster tag, where a cluster tag is an attribute defined in a deployment descriptor for a network function deployment. In some example embodiments, a cluster template may identify a group of open cloud resources or cluster nodes provisioned in a static mode node group or a dynamic mode node group.
[0060] Fig.15 An example flow chart of a method according to certain example embodiments is shown. In an example embodiment, Fig.15 The method may be performed by a network entity or a plurality of network element groups in a 3GPP system (such as LTE or 5G-NR). For example, in an example embodiment, Fig.15 The method can be similar to Fig.16 An SMO is performed in one of the devices 10 or 20 shown in FIG.
[0061] like Fig.15 As shown, the method may include receiving energy-saving attributes including features, policies, policy criteria, and policy mappings at a service management and orchestrator or an open cloud at 1500. The method may also include, at 1505, performing a home decision based on the energy-saving attributes and placing a network function deployment on an open cloud node cluster.
[0062] According to certain example embodiments, a portion of the network function deployment may include receiving an instantiation request. According to some example embodiments, the instantiation request may include an attribution requirement as to where the network function deployment needs to be instantiated, or a relative constraint on the instantiation of the network function deployment. According to other example embodiments, the method may also include determining on which open cloud node cluster to instantiate the network function deployment based on the deployment descriptor and the network function deployment artifact. In some example embodiments, the network function deployment artifact may include a cloud native descriptor and a cluster template.
[0063] In certain example embodiments, a cluster template or cloud native descriptor may include information of an open cloud node cluster as a declarative target configuration for the node cluster. In other example embodiments, a cluster template may include an open cloud internal configuration for how the node cluster will be built and configured. In further example embodiments, a cluster template may include a collection of energy-saving attributes. According to certain example embodiments, the energy-saving attributes may be configured within the node cluster and exposed to the open cloud through the O2 interface.
[0064] Fig.16 A collection of apparatuses 10 and 20 according to certain example embodiments is shown. In certain example embodiments, apparatuses 10 and 20 may be elements in a communication network or associated with such a network. For example, apparatus 10 may be an O-Cloud service (e.g., IMS), or a microservice in an O-Cloud or SMO, or other similar radio communication computer equipment, and apparatus 20 may be an SMO, or other similar computing device.
[0065] In some example embodiments, the apparatuses 10 and 20 may include one or more processors, one or more computer-readable storage media (e.g., memory, storage, etc.), one or more radio access components (e.g., modems, transceivers, etc.), and / or user interfaces. In some example embodiments, the apparatuses 10 and 20 may be configured to operate using one or more radio access technologies, such as GSM, LTE, LTE-A, NR, 5G, 6G, WLAN, WiFi, NB-IoT, Bluetooth, NFC, MulteFire, and / or any other radio access technology. It should be noted that a person of ordinary skill in the art will understand that the apparatuses 10 and 20 may include Fig.16 Components or features not shown.
[0066] like Fig.16As shown in the example of , the devices 10 and 20 may include or be coupled to processors 12 and 22 for processing information and executing instructions or operations. The processors 12 and 22 may be any type of general or special purpose processor. In fact, the processors 12 and 22 may include one or more of the following: a general purpose computer, a special purpose computer, a microprocessor, a DSP, a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), and a processor based on a multi-core processor architecture, as examples. Although a single processor 12 and 22 is Fig.16 1 and 2, but according to other example embodiments, multiple processors may be utilized. For example, it should be understood that in some example embodiments, devices 10 and 20 may include two or more processors that may form a multiprocessor system that may support multiprocessing (e.g., in this case, processor 12 may represent a multiprocessor). According to some example embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., forming a computer cluster).
[0067] Processors 12 and 22 may perform functions associated with the operation of devices 10 and 20, including, as some examples, precoding of antenna gain / phase parameters, encoding and decoding of individual bits forming communication messages, formatting of information, and overall control of devices 10 and 20, including Figures 1 to 15 The process and examples shown in .
[0068] The devices 10 and 20 may also include or be coupled to memory 14 and 24 (internal or external), which may be coupled to the processors 12 and 24, respectively, for storing information and instructions that can be executed by the processors 12 and 24. The memory 14 and 24 may be one or more memories and may be of any type suitable for the local application environment and may be implemented using any suitable volatile or non-volatile data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and / or removable memory. For example, the memory 14 and 24 may include any combination of random access memory (RAM), read-only memory (ROM), static storage (such as a magnetic disk or optical disk), hard disk drive (HDD), or any other type of non-transitory machine or computer readable medium. The instructions stored in the memory 14 and 24 may include program instructions or computer program code that, when executed by the processors 12 and 22, enables the devices 10 and 20 to perform the tasks described herein.
[0069] In certain example embodiments, the devices 10 and 20 may also include or be coupled to a (internal or external) drive or port configured to accept and read an external computer-readable storage medium, such as an optical disk, a USB drive, a flash drive, or any other storage medium. For example, the external computer-readable storage medium may store a computer program or software for execution by the processors 12 and 22 and / or the devices 10 and 20 to perform Figures 1 to 15 Any of the methods and examples shown in .
[0070] In some example embodiments, the apparatuses 10 and 20 may also include or be coupled to one or more antennas 15 and 25 for receiving downlink signals and transmitting from the apparatuses 10 and 20 via the UL. The apparatuses 10 and 20 may also include transceivers 18 and 28 configured to send and receive information. The transceivers 18 and 28 may also include a radio interface (e.g., a modem) coupled to the antennas 15 and 25. The radio interface may correspond to a variety of radio access technologies, including one or more of GSM, LTE, LTE-A, 5G, NR, 6G, WLAN, NB-IoT, Bluetooth, BT-LE, NFC, RFID, UWB, etc. The radio interface may include other components, such as filters, converters (e.g., digital-to-analog converters, etc.), symbol demappers, signal shaping components, inverse fast Fourier transform (IFFT) modules, etc., to process symbols carried by the downlink or UL, such as OFDMA symbols.
[0071] For example, transceivers 18 and 28 may be configured to modulate information onto a carrier waveform for transmission by antennas 15 and 25, and demodulate information received via antennas 15 and 25 for further processing by other elements of devices 10 and 20. In other example embodiments, transceivers 18 and 28 may be capable of directly sending and receiving signals or data. Additionally or alternatively, in some example embodiments, device 10 may include input and / or output devices (I / O devices). In certain example embodiments, devices 10 and 20 may also include a user interface, such as a graphical user interface or a touch screen.
[0072] In certain example embodiments, the memory 14 and 34 store software modules that provide functionality when executed by the processors 12 and 22. These modules may include, for example, an operating system that provides operating system functionality for the devices 10 and 20. The memory may also store one or more functional modules, such as applications or programs, to provide additional functionality for the devices 10 and 20. The components of the devices 10 and 20 may be implemented in hardware form, or as any suitable combination of hardware and software. According to certain example embodiments, the devices 10 and 20 may optionally be configured to communicate with each other (in any combination) via a wireless or wired communication link 70 according to any radio access technology (such as NR).
[0073] According to some example embodiments, processors 12 and 22 and memories 14 and 24 may be included in or may form part of a processing circuit system or a control circuit system. In addition, in some example embodiments, transceivers 18 and 28 may be included in or may form part of a transceiver circuit system.
[0074] For example, in certain example embodiments, the apparatus 10 may be controlled by the memory 14 and the processor 12 to define characteristics of a policy in an open cloud domain. The apparatus 10 may also be controlled by the memory 14 and the processor 12 to define policy criteria and policies associated with the characteristics of the policy. The apparatus 10 may also be controlled by the memory 14 and the processor 12 to map the policy to at least one operating mode of the open cloud resources. In addition, the apparatus 10 may be controlled by the memory 14 and the processor 12 to classify the open cloud resources into cluster templates. Furthermore, the apparatus 10 may be controlled by the memory 14 and the processor 12 to send a mapping of the characteristics, policies, policy criteria, and policies to a service management and orchestrator or an open cloud.
[0075] In other example embodiments, the device 20 may be controlled by the memory 24 and the processor 22 to receive energy-saving attributes including mappings of features, policies, policy criteria, and policies at a service management and orchestration device or an open cloud. The device 20 may also be controlled by the memory 24 and the processor 22 to perform a home decision based on the energy-saving attributes and place the network function deployment on the open cloud node cluster.
[0076] In some example embodiments, an apparatus (e.g., apparatus 10 and / or apparatus 20) may include components for performing the methods, processes, or any variants discussed herein. Examples of components may include one or more processors, memories, controllers, transmitters, receivers, and / or computer program code for causing the execution of operations.
[0077] Certain example embodiments may be directed to an apparatus including means for performing any of the methods described herein, including, for example, means for defining features of a policy in an open cloud domain. The apparatus may also include means for defining a policy and a policy standard associated with the features of the policy. The apparatus may also include means for mapping the policy to at least one operating mode of an open cloud resource. Additionally, the apparatus may include means for classifying the open cloud resources in a cluster template. Furthermore, the apparatus may include means for sending features, policies, policy standards, and mappings of policies to a service management and orchestrator or an open cloud.
[0078] Other example embodiments may be directed to an apparatus including means for performing any of the methods described herein, including means for receiving energy-saving attributes including a mapping of features, policies, policy criteria, and policies at a service management and orchestrator or an open cloud. The apparatus may also include means for performing a home decision and placing a network function deployment on an open cloud node cluster based on the energy-saving attributes.
[0079] Certain example embodiments described herein provide several technical improvements, enhancements and / or advantages with respect to the attribution and placement of cloudified NFs. For example, in some example embodiments, a collaborative solution may be provided to make the attribution and placement of cloudified NF decisions more efficient with respect to O-Cloud energy consumption. In other example embodiments, the SMO and attribution functions may not need to know and understand the detailed O-Cloud CPU resource configuration (e.g., p / c states, etc.) and energy-saving capabilities. In further example embodiments, the SMO and attribution functions may not need to know and understand the energy-saving policies of the O-Cloud node cluster. Additionally, in some example embodiments, NF deployments may be attributable to a cluster that supports energy saving based on a time of day. In other example embodiments, NF deployments may be attributable to a cluster with a wide range of support for (multiple) different energy-saving modes, as described herein with respect to classifying ES attributes into cluster templates. According to further example embodiments, SMO-level ES policies may be written in a more declarative (e.g., output-oriented, rather than "how") manner.
[0080] The computer program product may include one or more computer executable components that are configured to perform some example embodiments when the program is run. The one or more computer executable components may be at least one software code or part thereof. Modifications and configurations required to implement the functionality of some example embodiments may be performed as (multiple) routines, which may be implemented as added or updated (multiple) software routines. (Multiple) software routines may be downloaded into the device.
[0081] As an example, software or computer program code or parts thereof may be in source code form, object code form or some intermediate form and may be stored in some carrier, distribution medium or computer readable medium, which may be any entity or device capable of carrying the program. For example, such carriers may include recording media, computer memory, read-only memory, optoelectronic and / or electrical carrier signals, telecommunication signals and software distribution packages. Depending on the processing power required, the computer program may be executed in a single electronic digital computer or distributed among multiple computers. The computer readable medium or computer readable storage medium may be a non-transitory medium.
[0082] In other example embodiments, the function may be performed by hardware or circuitry included in a device (e.g., device 10 or device 20), such as by using an application specific integrated circuit (ASIC), a programmable gate array (PGA), a field programmable gate array (FPGA), or any other hardware and software combination. In yet another example embodiment, the function may be implemented as a signal, i.e., a non-tangible means that may be carried by an electromagnetic signal downloaded from the Internet or other network.
[0083] According to certain example embodiments, an apparatus (such as a node, device or corresponding component) may be configured as a circuit system, a computer or a microprocessor (such as a single-chip computer element) or a chipset, including a memory for providing storage capacity used for arithmetic operations and an operation processor for performing arithmetic operations.
[0084] A person of ordinary skill in the art will readily appreciate that the disclosure described above may be practiced using processes in a different order and / or hardware elements in a configuration different from that disclosed. Therefore, although the present disclosure has been described based on these example embodiments, certain modifications, variations, and alternative constructions will be apparent to those skilled in the art while remaining within the spirit and scope of the example embodiments. Although the above embodiments relate to 5G NR and LTE technologies, the above embodiments may also be applicable to any other existing or future 3GPP technologies, such as LTE-advanced and / or fourth generation (4G) technologies.
[0085] Partial glossary:
[0086] 3GPP Third Generation Partnership Project
[0087] 5G Fifth Generation
[0088] 5GCN 5G Core Network
[0089] 5GS 5G System
[0090] BS Base Station
[0091] CNF containerized network functions
[0092] DL Downlink
[0093] DMS O-Cloud Deployment Management Service
[0094] eNB Enhanced Node B
[0095] E-UTRAN Evolved UTRAN
[0096] FOCOM and O-Cloud orchestration and management
[0097] gNB 5G or Next Generation NodeB
[0098] IM Information Model
[0099] IMS O-Cloud Infrastructure Management Services
[0100] LCM Lifecycle Management
[0101] LTE Long Term Evolution
[0102] NF Network Function
[0103] NFO Network Function Orchestration
[0104] NFVI Network Function Virtualization Infrastructure
[0105] NR New Radio
[0106] O-CU O-RAN Central Unit
[0107] O-CU-CP O-CU control plane
[0108] O-CU-UP O-CU User Plane
[0109] O-DU O-RAN Distributed Unit
[0110] O-RU O-RAN Radio Unit
[0111] PNF Physical Network Function
[0112] RAN Radio Access Network
[0113] SMO Service Management and Orchestration Framework
[0114] UE User Equipment
[0115] UL Uplink
[0116] VIM Virtual Infrastructure Manager
[0117] VNF Virtual Network Function
Claims
1. A method comprising: Define the characteristics of policies in an open cloud domain; defining policy criteria and policies associated with said characteristics of said policy; mapping the policy to at least one operation mode of the open cloud resource; Classifying the open cloud resources in a cluster template; as well as The characteristics, the policies, the policy criteria, and the mapping of the policies are sent to a service management and orchestration or an open cloud.
2. The method of claim 1, wherein the features include: a power saving rate of power saved by the strategy during a predetermined time period, Resource availability of open cloud resources, a time window during which the strategy or the at least one operating mode can be activated, or The location of the cloud site that supports the virtual radio access network function.
3. The method according to any one of claims 1 or 2, wherein the at least one operating mode is a comprehensive energy consumption range achieved by different strategies applied together, and Wherein the at least one operating mode comprises performance, balanced, or power saving.
4. The method according to any one of claims 1 to 3, further comprising: The policy is grouped with additional policies based on similarities or conditions that satisfy the policy criteria.
5. The method according to any one of claims 1 to 4, wherein the classification of the open cloud resources or cluster nodes is based on at least one of the following: the operating mode, or A cluster tag, wherein the cluster tag is a property defined in a deployment descriptor of a network function deployment. 6 . The method according to claim 1 , wherein the cluster template identifies: a group of open cloud resources or a group of cluster nodes provisioned in a static mode node group or a dynamic mode node group.
7. A device comprising: at least one processor; as well as at least one memory storing instructions, wherein the instructions, when executed by the at least one processor, cause the apparatus to at least: Define the characteristics of policies in an open cloud domain; defining policy criteria and policies associated with said characteristics of said policy; mapping the policy to at least one operation mode of the open cloud resource; Classifying the open cloud resources in a cluster template; as well as The characteristics, the policies, the policy criteria, and the mapping of the policies are sent to a service management and orchestration or an open cloud.
8. The apparatus of claim 7, wherein the features include: a power saving rate of power saved by the strategy during a predetermined time period, Resource availability of open cloud resources, a time window during which the strategy or the at least one operating mode can be activated, or The location of the cloud site that supports the virtual radio access network function.
9. The apparatus of claim 7 or 8, wherein the policy and the policy criteria are defined based on a value, a threshold, or a range.
10. The apparatus of any one of claims 7 to 9, wherein the policy criteria is defined by at least one of the following: On / Off, Any / nothing to do with, or Emoji and neutral.
11. The device according to any one of claims 7 to 10, wherein the at least one operating mode is a comprehensive energy consumption range achieved by different strategies applied together, and Wherein the at least one operating mode comprises performance, balanced, or power saving.
12. The apparatus according to any one of claims 7 to 11, wherein the instructions, when executed by the at least one processor, further cause the apparatus to at least: The policy is grouped with additional policies based on similarities or conditions that satisfy the policy criteria.
13. The apparatus according to any one of claims 7 to 12, wherein the classification of the open cloud resources or cluster nodes is based on at least one of the following: the operating mode, or A cluster tag, wherein the cluster tag is a property defined in a deployment descriptor of a network function deployment.
14. The apparatus according to any one of claims 7 to 13, wherein the cluster template identifies: an open cloud resource group or a cluster node group provisioned in a static mode node group or a dynamic mode node group.
15. An apparatus comprising: at least one processor; as well as at least one memory storing instructions, wherein the instructions, when executed by the at least one processor, cause the apparatus to at least: receiving, at a service management and orchestrator or an open cloud, energy conservation attributes, the energy conservation attributes comprising characteristics, policies, policy criteria, and a mapping of the policies; as well as Based on the energy-saving attributes, a home decision is performed and the network function deployment is placed on an open cloud node cluster.