Control of energy and / or power consumption for a communication network

Abstract

A method is disclosed for controlling energy and / or power consumption of a communication network associated with a plurality of network function features. The method comprises acquiring (110, 120) an indication of usage for each network function feature, and a plurality of consumption profiles, wherein each consumption profile corresponds to a specific one of the network function features. The method also comprises determining (130) a potential consumption reduction which is achievable by deactivation of a selected one of the network function features, based on the usage of the selected network function feature and the corresponding consumption profile, and causing (140) deactivation of the selected network function feature responsive to a deactivation decision, which is based on the potential consumption reduction. Corresponding consumption profile, apparatus, network consumption orchestration node, license server, consumption server node, system, computer program product, and non-transitory computer readable medium are also disclosed.

Description

[0001] CONTROL OF ENERGY AND / OR POWER CONSUMPTION FOR A COMMUNICATION NETWORK

[0002] TECHNICAL FIELD

[0003] The present disclosure relates generally to the field of consumption of energy and / or power. More particularly, it relates to control of energy and / or power consumption of a communication network (e.g., a wireless communication network). In various aspects, there are provided a method for controlling energy and / or power consumption of a communication network, as well as corresponding consumption profile, apparatus, network consumption orchestration node, license server, consumption server node, system, computer program product, and non-transitory computer readable medium.

[0004] BACKGROUND

[0005] In the following disclosure, energy consumption will be used as an example. Meanwhile, it should be understood that "energy" can be replaced and / or complemented by "power", as suitable.

[0006] It is well known that communication networks consume energy. It should be noted that the energy consumption of a communication network may be caused by any one or more function related to the communication network (e.g., signal transfer, data processing, information storing, etc.).

[0007] Generally, controlling energy consumption is one approach for reducing carbon emissions and / or preserving available energy for other purposes. To this end, reduction of energy consumption may be advantageous in the context of communication networks. Alternatively, or additionally, reduction of energy consumption can entail one or more other advantages in the context of communication networks. For example, lower cost of operation, increased battery time, etc.

[0008] With the expected increase of service demands (capacity, quality, speed, etc.) for communication networks, control of energy consumption may become even more interesting to avoid that the energy consumption increases unacceptably as a consequence of increasing service demands.

[0009] Some efforts have been made with the aim to reduce energy consumption of communication networks. For example, when a communication network operates within two or more frequency bands, some of those frequency bands may be switched off during less busy time intervals. However, such approaches may not provide sufficient reduction in energy consumption. Furthermore, they are not applicable for all communication network scenarios. For example, switching off frequency band(s) is not applicable for communication networks that operate within a single frequency band, and may not be suitable where operation within two or more frequency bands is required for some reason (e.g., reliability). Therefore, there is a need for alternative approaches for control of energy consumption of communication networks.

[0010] SUMMARY

[0011] It should be emphasized that the term "comprises / comprising" (replaceable by "includes / including") when used in this specification is taken to specify the presence of stated features, integers, steps, or components, but does not preclude the presence or addition of one or more other features, integers, steps, components, or groups thereof. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.

[0012] Generally, when an arrangement is referred to herein, it is to be understood as a physical product; e.g., an apparatus. The physical product may comprise one or more parts, such as controlling circuitry in the form of one or more controllers, one or more processors, or the like.

[0013] It is an object of the invention to facilitate efficiency of a communication network.

[0014] It is an object of some embodiments to solve or mitigate, alleviate, or eliminate at least some of the above or other disadvantages.

[0015] Particularly, it is an object of some embodiments to provide flexible approaches for controlling energy consumption of communication networks (e.g., to reduce carbon emissions, and / or preserve available energy for other purposes than operation of the communication network, and / or lower the cost of operation of the communication network). Preferably, such approaches should enable energy reduction without switching off frequency band(s).

[0016] A first aspect is a computer-implemented method for controlling energy consumption and / or power consumption of a communication network associated with a plurality of network function features. The method comprises acquiring an indication of usage for each network function feature from a license server of the communication network, and acquiring a plurality of consumption profiles from a consumption server node of the communication network, wherein each consumption profile corresponds to a specific one of the network function features. The method also comprises determining a potential consumption reduction which is achievable by deactivation of a selected one of the network function features, wherein the potential consumption reduction is based on the usage of the selected network function feature and the corresponding consumption profile. Furthermore, the method comprises causing deactivation of the selected network function feature by providing a deactivation command to the license server responsive to a deactivation decision for the selected network function feature, wherein the deactivation decision is based on the potential consumption reduction. In some embodiments, the consumption profile comprises a consumption profile identity specifying the correspondence between the consumption profile and network function feature.

[0017] In some embodiments, the consumption profile comprises an indication of consumption associated with use of the corresponding network function feature.

[0018] In some embodiments, the potential consumption reduction for the selected network function feature is based on the acquired usage for the network function feature and the consumption indicated by the corresponding consumption profile.

[0019] In some embodiments, the consumption profile comprises an indication of importance of the corresponding network function feature, wherein the indication of importance is selected from a group of importance values comprising at least a first importance value and a second importance value, wherein the first importance value indicates higher importance than the second importance value.

[0020] In some embodiments, network function features with corresponding consumption profiles indicating the first importance value are excluded from being selected network function features.

[0021] In some embodiments, the method further comprises performing network function feature selection.

[0022] In some embodiments, the method further comprises evaluating the potential consumption reduction which is achievable by deactivation of the selected network function feature(s) in relation to a consumption reduction criterion, selecting an additional network function feature responsive to non-fulfillment of the consumption reduction criterion, and taking the deactivation decision for the selected network function feature(s) responsive to fulfillment of the consumption reduction criterion.

[0023] In some embodiments, the consumption reduction criterion comprises one or more of: the potential consumption reduction which is achievable by deactivation of the selected network function feature(s) equals, or exceeds, a reduction threshold, the potential consumption reduction which is achievable by deactivation of the selected network function feature(s) yields a remaining consumption which is lowerthan a remainder threshold, and the numberof selected network function features reaching a maximum number of deactivated network function features.

[0024] In some embodiments, the method further comprises receiving an indication of the consumption reduction criterion via an operator interface for control of the communication network.

[0025] In some embodiments, the method further comprises providing the indication of usage and corresponding consumption profile via an operator interface for control of the communication network, and receiving an indication of the selected network function feature via the operator interface.

[0026] In some embodiments, the method further comprises providing an indication of the determined potential consumption reduction via the operator interface.

[0027] In some embodiments, the method further comprises receiving the deactivation decision via the operator interface.

[0028] A second aspect is a computer program product comprising a non-transitory computer readable medium, having thereon a computer program comprising program instructions. The computer program is loadable into a data processing unit and configured to cause execution of the method according to the first aspect when the computer program is run by the data processing unit.

[0029] A third aspect is a computer program comprising program instructions. The computer program is loadable into a data processing unit and configured to cause execution of the method according the first aspect when the computer program is run by the data processing unit.

[0030] A fourth aspect is an apparatus for controlling energy consumption and / or power consumption of a communication network associated with a plurality of network function features. The apparatus comprises controlling circuitry configured to cause acquisition of an indication of usage for each network function feature from a license server of the communication network, and acquisition of a plurality of consumption profiles from a consumption server node of the communication network, wherein each consumption profile corresponds to a specific one of the network function features. The controlling circuitry is also configured to cause determination of a potential consumption reduction which is achievable by deactivation of a selected one of the network function features, wherein the potential consumption reduction is based on the usage of the selected network function feature and the corresponding consumption profile, and deactivation of the selected network function feature by provision of a deactivation command to the license server responsive to a deactivation decision for the selected network function feature, wherein the deactivation decision is based on the potential consumption reduction.

[0031] A fifth aspect is a network consumption orchestration node comprising the apparatus of the fourth aspect.

[0032] A sixth aspect is a license server for a communication network, for managing network licenses in relation to a plurality of network function features. The license server is configured to provide an indication of usage for each network function feature to a network consumption orchestration node for control of energy consumption and / or power consumption of the communication network by determination of a potential consumption reduction which is achievable by deactivation of a selected one of the network function features. The indication of usage is associated with a consumption profile identity specifying correspondence between a consumption profile and the network function feature, and the potential consumption reduction is based on the usage of the selected network function feature and the corresponding consumption profile. The license server is also configured to deactivate the selected network function feature responsive to receiving a deactivation command from the network consumption orchestration node, wherein the deactivation command corresponds to a deactivation decision based on the potential consumption reduction.

[0033] A seventh aspect is a consumption profile corresponding to a network function feature for control of energy consumption and / or power consumption of a communication network associated with the network feature. The consumption profile comprises a consumption profile identity specifying the correspondence between the consumption profile and network function feature.

[0034] An eighth aspect is a consumption server node configured to store one or more consumption profiles according to the seventh aspect. The consumption server node is also configured to provide one or more of the stored consumption profiles to a network consumption orchestration node forcontrol of energy consumption and / or powerconsumption of a communication network associated with a plurality of network function features by determination of a potential consumption reduction which is achievable by deactivation of a selected network function feature, wherein the potential consumption reduction is based on a usage of the selected network function feature and the corresponding consumption profile.

[0035] A ninth aspect is a non-transitory computer readable medium, having thereon one or more consumption profiles according to the seventh aspect, the consumption profiles being loadable into a data storing unit of the consumption server node of the eighth aspect.

[0036] A tenth aspect is a system for controlling energy consumption and / or power consumption of a communication network associated with a plurality of network function features, the system comprising the network consumption orchestration node of the fifth aspect, the license server of the sixth aspect, and the consumption server node of the eighth aspect.

[0037] In some embodiments, any of the above aspects may additionally have features identical with or corresponding to any of the various features as explained above for any of the other aspects.

[0038] An advantage of some embodiments is that approaches are provided forcontrol (e.g., monitoring and / or reduction) of energy consumption of communication networks.

[0039] An advantage of some embodiments is that energy reduction may be achieved without switching off frequency band(s), or further energy reduction may be achieved in addition to that entailing from switching off frequency band(s). An advantage of some embodiments is that carbon emissions caused by a communication network may be reduced and / or available energy may be preserved for other purposes than operation of the communication network.

[0040] An advantage of some embodiments is that the cost of operation of the communication network may be lowered.

[0041] An advantage of some embodiments is that a flexible approach to energy consumption management is provided, since network function features can be switched off individually. Thereby, it is possible to dynamically vary which network function features are allowed to be active; e.g., depending on varying energy availability and / or varying communication needs.

[0042] An advantage of some embodiments is that energy consumption management may be centralized for the communication network.

[0043] An advantage of some embodiments is that energy consumption management may be automated.

[0044] An advantage of some embodiments is that energy consumption management may be controlled by an operator of the communication network.

[0045] BRIEF DESCRIPTION OF THE DRAWINGS

[0046] Further objects, features and advantages will appear from the following detailed description of embodiments, with reference being made to the accompanying drawings. The drawings are not necessarily to scale, emphasis instead being placed upon illustrating the example embodiments.

[0047] Figure 1 is a flowchart illustrating example method steps according to some embodiments;

[0048] Figure 2 is a schematic drawing illustrating an example network license according to some embodiments;

[0049] Figure 3 is a schematic drawing illustrating an example consumption profile according to some embodiments;

[0050] Figure 4 is a combined flowchart and signaling diagram illustrating example method steps and signaling according to some embodiments;

[0051] Figure 5 is a combined flowchart and signaling diagram illustrating example method steps and signaling according to some embodiments;

[0052] Figure 6 is a signaling diagram illustrating example signaling according to some embodiments;

[0053] Figure 7 is a signaling diagram illustrating example signaling according to some embodiments; Figure 8 is a flowchart illustrating example method steps according to some embodiments;

[0054] Figure 9 is a schematic block diagram illustrating an example apparatus according to some embodiments;

[0055] Figure 10 is a schematic drawing illustrating an example system according to some embodiments;

[0056] Figure 11 is a schematic drawing illustrating an example computer readable medium according to some embodiments;

[0057] Figure 12 is a schematic drawing illustrating an example communication system according to some embodiments;

[0058] Figure 13 is a schematic block diagram illustrating an example network node according to some embodiments; and

[0059] Figure 14 is a schematic block diagram illustrating an example virtualization environment in which functions implemented by some embodiments may be virtualized.

[0060] DETAILED DESCRIPTION

[0061] As already mentioned above, it should be emphasized that the term "comprises / comprising" (replaceable by "includes / including") when used in this specification is taken to specify the presence of stated features, integers, steps, or components, but does not preclude the presence or addition of one or more other features, integers, steps, components, or groups thereof. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.

[0062] Embodiments of the present disclosure will be described and exemplified more fully hereinafter with reference to the accompanying drawings. The solutions disclosed herein can, however, be realized in many different forms and should not be construed as being limited to the embodiments set forth herein.

[0063] In the following, approaches will be presented and exemplified, which enable control (management) of energy consumption and / or power consumption of communication networks.

[0064] Generally, control of energy (or power) consumption is meant to encompass monitoring of the consumption and / or reduction of the consumption, and controlling energy (or power) consumption is meant to encompass monitoring the consumption and / or reducing the consumption.

[0065] The approaches are to be understood as applicable to any suitable communication network. Example suitable communication networks include - but are not limited to - wireless communication networks specified by the Third Generation Partnership Project (3GPP), e.g., under the fifth generation (5G).

[0066] Energy consumption will be used as an example, while it should be understood that embodiments are generally applicable for both energy consumption and power consumption.

[0067] As already mentioned, some operators take initiatives to switch off some radio frequencies during nightly hours to cope with the increasing demands regarding energy saving. Such approaches may be useful in relation to energy consumption associated with radio access and antenna operation. However, it is not useful for application to network functions.

[0068] A functionality provided to end users is usually accomplished by interaction of several network functions, and additional complexity may entail in the context of cloud native networks composed by a large plurality of micro-services (which may be regarded as a form of network functions).

[0069] A pure resource limitation for a specific network function (as would be the case if some radio frequencies were switched off) would indiscriminately slow down the entire network function without considering the entailing impact, and might cause performance degradation or service interruption for end users.

[0070] The approaches presented herein may be beneficial to overcome such problems and may be used instead of, or in addition to, other approaches for control of energy consumption of communication networks.

[0071] Figure 1 illustrates an example computer-implemented method 100 according to some embodiments. The method is for controlling energy consumption (and / or power consumption) of a communication network associated with a plurality of network function features.

[0072] Generally, the terms "network function" (NF) and "network function feature" should be understood to encompass - respectively - any suitable function of a communication network and any suitable feature of a function of a communication network. Particularly, the terms "network function" and "network function feature" should be understood to include - but not be limited to - the meaning of these terms as understood by the skilled person in view of the prior art.

[0073] For example, the method 100 may be performed by a network consumption orchestration node, which may be comprised in the communication network, or may be external to the communication network. In some embodiments, the method 100 is performed by distributed processing (e.g., cloud computing).

[0074] In step 110, an indication of usage is acquired for each network function feature from a license server of the communication network. For example, the acquisition may comprise sending a request to the license server and receiving the indication of usage in response thereto. Alternatively, or additionally, the license server may be configured to provide the indication of usage without being triggered by a request (e.g., at some specified point(s) in time, or responsive to some specified event(s)).

[0075] The license server may be comprised in the communication network, or may be external to the communication network. In some embodiments, the license server is implemented as a distributed server (e.g., within a cloud solution).

[0076] The usage of a network function feature may be based on information that the license server collects regarding when and / or how much the network function feature is in use.

[0077] For example, the indication of usage of a network function feature may indicate whether or not the network function feature is / was active at a particular instant in time (e.g., whether or not the network function feature is currently active).

[0078] Alternatively, or additionally, the indication of usage of a network function feature may indicate (e.g., based on statistics) a usage value based on how often (and / or for how long time) the network function feature is used in relation to each network license. For example, the usage value may comprise a cumulative or average value over all network licenses per some time unit. Exemplifying with four network licenses, where a network function feature is used 50% of the time by each of two of the network licenses, 20% of the time by one of the network licenses, and not at all by one of the network licenses, the usage value could be set to 1.2 (cumulative) or to 0.3 (average).

[0079] The usage value for a network function feature may be a single usage value applicable regardless of time, or it may be two or more usage values which are time-dependently applicable (e.g., one usage value for nighttime and one usage value for daytime). The usage values may be static / fixed values, or may be dynamically updated as the license server collects new information regarding when and / or how much the network function feature is in use.

[0080] In step 120, a plurality of consumption profiles (e.g., energy profiles) is acquired from a consumption server node (e.g., an energy server node) of the communication network. For example, the acquisition may comprise sending a request to the consumption server node and receiving the plurality of consumption profiles in response thereto. Alternatively, or additionally, the consumption server node may be configured to provide the plurality of consumption profiles without being triggered by a request (e.g., at some specified point(s) in time, or responsive to some specified event(s)).

[0081] The consumption server node may be comprised in the communication network, or may be external to the communication network. In some embodiments, the consumption server node is implemented as a distributed server (e.g., within a cloud solution). Each consumption profile corresponds to one of the network function features. For example, a consumption profile may comprise a consumption profile identity specifying the correspondence between the consumption profile and network function feature. Typically, the consumption profile identity may be indicated also in the license server (associated with the corresponding network function feature), and the indication of usage acquired in step 110 for a network function feature may further indicate the consumption profile identity. It should be noted that the consumption profile identity is meant to include any suitable approaches (e.g., links, pointers, etc.) for specifying correspondence between consumption profile and network function feature.

[0082] It should be noted that - generally - steps 110 and 120 may be performed in any order, or in parallel.

[0083] In a typical example, step 110 comprises acquiring network license information from the license server, wherein the network license information indicates active network function features, and acquiring the usage value for the indicated active network function features, while step 120 comprises acquiring the consumption profiles for the indicated active network function features.

[0084] In step 130, a potential consumption reduction (e.g., a potential energy reduction) is determined, which is achievable by deactivation of a selected one of the network function features. The potential consumption reduction is based on the usage of the selected network function feature (as acquired in step 110) and the corresponding consumption profile (as acquired in step 120).

[0085] In some embodiments, the consumption profile may comprise an indication of consumption (e.g., energy consumption) associated with use of the corresponding network function feature, and the potential consumption reduction for the selected network function feature may be based on the acquired usage for the network function feature and the consumption indicated by the corresponding consumption profile.

[0086] Typically, the consumption associated with use of a network function feature may comprise a consumption value indicating how much energy is consumed (e.g., on average) each time the network function feature is used by a network license, and / or how much power is consumed when the network function feature is used.

[0087] The consumption value may be determined in any suitable way. For example, the consumption value for a network function feature may be determined by simulations and / or measurement tests conducted for the network function feature (e.g., in connection with deployment of the network function feature). Alternatively, or additionally, the consumption value may be determined / updated based on measurements during operation. Generally, the consumption value for a network function feature may be a static / fixed value, or may be dynamically updated as new measurements are collected. Application of the principles disclosed in US10,936,473B2 provides one example of how the consumption associated with use of a network function feature may be determined, although other ways to determine the consumption value are also possible. According to US10,936,473B2, there is presented an approach to generate a power consumption profile for a software application. A network function feature as referred to herein may be seen as an example of a software application in the context of US10,936,473B2. The approach comprises performing performance tests of the software application, measuring power consumption of one or more hardware components in response to execution of the software application during the one or more performance tests, and generating the power consumption profile for the software application based on the measured power consumption.

[0088] For example, the consumption of a network function feature may be estimated by multiplying the consumption value with the usage value, and the potential consumption reduction achievable by deactivation of the network function feature may correspond to the estimated consumption.

[0089] According to some embodiments, a network function feature which is not currently active may be excluded from selection and / or may have a potential consumption reduction equal to zero.

[0090] In step 140, deactivation of the selected network function feature is caused responsive to a deactivation decision for the selected network function feature. For example the deactivation may be caused by providing a deactivation command to the license server.

[0091] The deactivation decision is based on the potential consumption reduction determined in step 130. For example, the deactivation decision may relate to one or more selected network function feature(s) for which the potential consumption reduction fulfills some suitable consumption reduction criterion.

[0092] The deactivation decision may be taken successively (e.g., for one selected network function feature at a time), or may be taken collectively (e.g., simultaneously for two or more selected network function features). Similarly, the deactivation may be caused successively (e.g., for one selected network function feature at a time), or may be caused collectively (e.g., simultaneously for two or more selected network function features).

[0093] The consumption profile may further comprise an indication of importance of the corresponding network function feature. The indication of importance is selected from a group of importance values comprising at least a first importance value and a second importance value, wherein the first importance value indicates higher importance than the second importance value. In some embodiments, network function features with corresponding consumption profiles indicating the first importance value are excluded from being selected network function features. For example, the consumption profile may indicate whether or not the corresponding network function feature is critical for operation of the communication network via a Boolean parameter which is set (e.g., "ON" or "1" or other suitable Boolean value, indicating relatively high importance, for example as the first importance value) when critical and not set (e.g., "OFF" or "0" or other suitable Boolean value, indicating relatively low importance, for example as the second importance value) when non-critical, and any network function feature indicated as critical is excluded from being selected (i.e., will not be deactivated).

[0094] In some embodiments, more than two importance values may be applied, each indicating a specific level of importance. The importance values may be used in any suitable way. For example, network function features may be selected in a reverse order of importance; starting with the relatively lowest importance.

[0095] Generally, the importance may refer to any suitable measure for the priority / essentiality / necessity / criticality of a network function feature; with metric values indicating how prioritized / essential / necessary / critical a network function feature is for network operation.

[0096] Any suitable values may be used to represent the importance. For example, relatively high values may represent relatively high importance and relatively low values may represent relatively low importance, or vice versa.

[0097] For example, some features may be mandatory (e.g., according to the service vendor specifications) and may be classified as having relatively high (e.g., highest) importance; i.e., being critical for network operation. Other examples of possibly critical network function features include those needed according to laws or regulations, to make voice calls, to make emergency calls, to convey messages of the short message service (SMS), and similar. Some examples of typical non-critical network function features include those used for quality improvement and / or throughput increase (e.g., payload filtering, multiple-input multiple-output

[0098] - MIMO - operation, and similar).

[0099] The selection of network function feature(s) - for determination of potential consumption reduction, evaluation in relation to a consumption reduction criterion, and deactivation decision

[0100] - may be performed in any suitable way.

[0101] For example, the selection may be randomly performed. Alternatively, the selection may be based on one or more of: consumption value, usage value, and importance (e.g., starting with highest consumption value, and / or highest usage value, and / or lowest importance). In some embodiments, the potential consumption reduction is determined for a plurality (e.g., all) of the network function features before section, and the selection is based on the potential consumption reduction and - possibly - importance (starting with the highest potential consumption reduction).

[0102] Figure 2 illustrates an example network license (Network License Y) 200 according to some embodiments. For example, the network license 200 may be managed - together with other network licenses - by a license server of a communication network.

[0103] The network license 200 is associated with a plurality of network function features (Feature A, Feature B, Feature C) 210, 220, 230. The association may, for example, imply that a holder / user of the network license 200 has access to (i.e., is authorized to use) the network function features 210, 220, 230.

[0104] Each of the network function features 210, 220, 230 is associated with a respective indication of usage (Usage A, Usage B, Usage C) 214, 224, 234 and a respective consumption profile identity (P ID A, P ID B, P ID C) 215, 225, 235. As explained in connection with Figure 1, the consumption profile identities 215, 225, 235 specify a correspondence between the relevant network function feature and a consumption profile, and the indications of usage 214, 224, 234 are based on information regarding when and / or how much the relevant network function feature is in use.

[0105] For example, the indications of usage 214, 224, 234 and corresponding consumption profile identities 215, 225, 235 may be provided by the license server to a network consumption orchestration node for control of energy consumption of the communication network (compare with step 110 of Figure 1).

[0106] The consumption profile identities 215, 225, 235 may be stored together with the corresponding network function features, as illustrated in Figure 2. Alternatively, the consumption profile identities 215, 225, 235 may be stored separately from the corresponding network function features; and even external to the license server. For example, a mapping function, a look-up- table, or the like may specify a correspondence between network function features and consumption profiles.

[0107] Alternatively, or additionally, the indications of usage 214, 224, 234 may be derived and / or stored separately from the corresponding network function features; and even external to the license server. For example, the license server may provide more general statistics (e.g., historical data) regarding the use of the network function features to the network consumption orchestration node, which may determine the indications of usage 214, 224, 234 based on the general statistics.

[0108] It should be noted that, generally, there may be network function feature(s) without corresponding consumption profile(s) (e.g., not associated with any consumption profile identity). Such network function feature(s) may be excluded from being selected for an attempt to reduce consumption according to the approaches described herein. For example, such network function feature(s) may be completely excluded from deactivation, or may be deactivated blindly in case an attempt to reduce consumption according to the approaches described herein is not successful (e.g., if the consumption is not sufficiently reduced by such an attempt).

[0109] It should be recognized that the network license 200 and / or the features 210, 220, 230 typically comprise further information in addition to that illustrated in Figure 2 (e.g., similar information as comprised in network licenses and features according to the prior art).

[0110] Generally, the management of network licenses (e.g., software licenses) represents a way to communicate, to a network function, a list of network function features that a specific license holder is entitled to use, possibly supplemented by a capacity quantity for the licensed feature. Information related to active features and their usage may be used to provide a holistic view of the network status (e.g., in terms of attached users, active sessions, etc.). Compared to using traditional metrics (e.g., CPU usage, memory usage, etc.), the holistic view may enable improved energy saving. This is because the energy consumption for a communication network typically depends on end user behavior. For example, increased energy consumption may be driven by more subscriptions, higher traffic demands, increased number of services, etc. The holistic view offers a possibility to reduce energy consumption without impacting end user experience (or at least while being able to control the impact on end user experience).

[0111] According to some embodiments, the license server is configured to act in the context of energy management by collecting statistical data for the network in terms of feature usage, providing a correlation between the statistical data consumption profiles, enabling centralized configuration of network features (by well-considered deactivation of network function features), and providing flexibility in terms energy consumption adjustments.

[0112] Figure 3 illustrates an example consumption profile (Consumption Profile X) 300 according to some embodiments. For example, the consumption profile 300 may be managed - together with other consumption profiles - by a consumption server node of a communication network.

[0113] The consumption profiles may be seen as a set of policies for managing energy consumption of the communication network. For example, each network function could have a consumption profile associated to each single feature.

[0114] The consumption profile 300 is associated with - e.g., comprises - a consumption profile identity (P ID X) 305, which specifies a correspondence between the consumption profile 300 and a network function feature (compare with network function features 210, 220, 230 of Figure 2, and their respective consumption profile identities 215, 225, 235).

[0115] The consumption profile 300 comprises an indication of consumption 306 for the corresponding network function feature. As explained in connection with Figure 1, the indication of consumption 306 may specify a consumption value indicating how much energy is consumed each time the corresponding network function feature is used.

[0116] In some embodiments, the consumption profile 300 also comprises an indication of importance 307 of the corresponding network function feature. As explained in connection with Figure 1, the indication of importance 307 may be selected from a group of importance values comprising at least a first importance value and a second importance value, wherein the first importance value indicates higher importance than the second importance value.

[0117] For example, the consumption profile 300 (or - more generally - an indication of its content) may be provided by the consumption server node to a network consumption orchestration node for control of energy consumption of the communication network (compare with step 120 of Figure 1).

[0118] Generally, the consumption profile for a network function feature may be defined in connection with deployment of a network function, or a network function feature. Alternatively, or additionally, the consumption profile may be defined / edited during operation.

[0119] Figure 4 illustrates example method steps which may be performed by a network consumption orchestration node (CO) 492, and corresponding signaling among the network consumption orchestration node 492, a license server (LS) 493, a consumption server node (CS) 494, and - optionally - a network operator (OP) 491. For example, the network operator 491 may be represented by a human, or machine, which is enabled to interact with the network consumption orchestration node 492 via an operator interface (e.g., a user interface) for control of the communication network. The example of Figure 4 represent an automated, or semi-automated, approach for consumption management.

[0120] In optional step 405, the CO 492 receives an indication 401 of a consumption reduction criterion from the OP 491. For example, the indication 401 may comprise a threshold value (e.g., a reduction threshold value, a remainder threshold value, a maximum number of deactivated network function features, or similar). It should be noted that the consumption reduction criterion may be acquired by the CO 492 in other ways. For example, the CO 492 may determine the consumption reduction criterion autonomously, the CO 492 may receive an indication of the consumption reduction criterion from some other suitable source, or the consumption reduction criterion may be hardcoded into the CO 492.

[0121] In step 410, the CO 492 acquires an indication 402 of usage for each network function feature from the LS 493 (compare with step 110 of Figure 1, and with 214, 224, 234 of Figure 2).

[0122] In step 420, the CO 492 acquires a plurality 403 of consumption profiles from the CS 494 (compare with step 120 of Figure 1, and with 300 of Figure 3). Each consumption profile acquired in step 420 corresponds to one of the network function features for which an indication of usage was acquired in step 410. For example, the correspondence may be implemented by a consumption profile identity (compare with 215, 225, 235 of Figure 2 and 305 of Figure 3).

[0123] In step 425, the CO 492 selects one or more network function feature(s). As mentioned in connections with Figure 1, the selection of network function feature(s) may be performed in any suitable way (e.g., randomly, or based on one or more of: consumption value, usage value, and importance).

[0124] In step 430, the CO 492 determines a potential consumption reduction, which is achievable by deactivation of the selected network function feature(s) (compare with step 130 of Figure 1). As mentioned in connections with Figure 1, the potential consumption reduction is based on the usage of the selected network function feature (as acquired in step 410) and the corresponding consumption profile (as acquired in step 420).

[0125] In step 435, the CO 492 evaluates the potential consumption reduction determined in step 430 in relation to a consumption reduction criterion.

[0126] The consumption reduction criterion may be any suitable criterion (or suitable combination of criteria).

[0127] For example, the consumption reduction criterion may be considered as fulfilled when the potential consumption reduction which is achievable by deactivation of the selected network function feature(s) equals, or exceeds, a reduction threshold (and not fulfilled otherwise). The reduction threshold value may, for example, be an expressed in relative terms as a portion of the current (or maximum) overall consumption of the communication network, or in absolute terms as a consumption reduction value.

[0128] Alternatively, or additionally, the consumption reduction criterion may be considered as fulfilled when the potential consumption reduction which is achievable by deactivation of the selected network function feature(s) yields a remaining consumption which is lower than a remainder threshold (and not fulfilled otherwise). The remainder threshold value may, for example, be an expressed in relative terms as a portion of the current (or maximum) overall consumption of the communication network, or in absolute terms as a consumption remainder value.

[0129] Yet alternatively, or additionally, the consumption reduction criterion may be considered as fulfilled when the number of selected network function features reaches a maximum number of deactivated network function features.

[0130] When the consumption reduction criterion is not fulfilled (N-path out or step 435), the CO 492 returns to step 425 for selection of one or more additional network function feature(s). This loop- back may be iterated until the consumption reduction criterion is fulfilled, or until all selectable network function feature have been selected.

[0131] In some embodiments, an execution of step 425 may comprise - in addition to selecting additional network function feature(s) - removing one or more network function feature(s) from the group of selected network function features. For example, if network function features are selected randomly and the potential consumption reduction determined in step 430 is relatively low for a selected network function feature, that network function feature may be removed from the group of selected network function features. Alternatively, if network function features are selected based on usage (e.g., in decreasing order of usage value) and the potential consumption reduction determined in step 430 is relatively low for a selected network function feature (e.g., due to a relatively low consumption value), that network function feature may be removed from the group of selected network function features. Yet alternatively, if network function features are selected based on consumption (e.g., in decreasing order of consumption value) and the potential consumption reduction determined in step 430 is relatively low for a selected network function feature (e.g., due to a relatively low usage value), that network function feature may be removed from the group of selected network function features.

[0132] When the consumption reduction criterion is fulfilled (Y-path out or step 435) and / or all selectable network function feature have been selected, the CO 492 takes a decision to deactivate the selected network function feature(s) and proceeds to step 440.

[0133] In step 440, the CO 492 causes deactivation of the selected network function feature(s) by providing a deactivation command 409 to the LS 493 (compare with step 140 of Figure 1).

[0134] Figure 5 illustrates example method steps which may be performed by a network consumption orchestration node (CO) 592, and corresponding signaling among the network consumption orchestration node 592, a license server (LS) 593, a consumption server node (CS) 594, and a network operator (OP) 591. For example, the network operator 591 may be represented by a human, or machine, which is enabled to interact with the network consumption orchestration node 592 via an operator interface (e.g., a user interface) for control of the communication network. The example of Figure 5 represents an approach for consumption management with manual, or at least external, control.

[0135] In step 510, the CO 592 acquires an indication 502 of usage for each network function feature from the LS 593 (compare with step 110 of Figure 1, and with 214, 224, 234 of Figure 2).

[0136] In step 520, the CO 592 acquires a plurality 503 of consumption profiles from the CS 594 (compare with step 120 of Figure 1, and with 300 of Figure 3).

[0137] Each consumption profile acquired in step 520 corresponds to one of the network function features for which an indication of usage was acquired in step 510. For example, the correspondence may be implemented by a consumption profile identity (compare with 215, 225, 235 of Figure 2 and 305 of Figure 3).

[0138] In optional step 527, the CO 592 provides the indications of usage and / or corresponding consumption profiles to the OP 591, as illustrated by 504. The information regarding usage and / or corresponding consumption profiles may, for example, be suitably visualized via a rendering device to serve as a basis for selection of one or more network function feature(s).

[0139] The OP 591 selects one or more network function feature(s). The selection of network function feature(s) may be performed in any suitable way (e.g., randomly - in which case step 527 may be omitted, or based on one or more of: consumption value, usage value, and importance).

[0140] In step 528, the CO 592 receives an indication 505 of the selected network function feature(s) from the OP 591.

[0141] In step 530, the CO 592 determines a potential consumption reduction, which is achievable by deactivation of the selected network function feature(s) (compare with step 130 of Figure 1). As mentioned in connections with Figure 1, the potential consumption reduction is based on the usage of the selected network function feature (as acquired in step 510) and the corresponding consumption profile (as acquired in step 520).

[0142] In step 537, the CO 592 provides an indication 506 of the determined potential consumption reduction to the OP 591. The information regarding potential consumption reduction may, for example, be suitably visualized via a rendering device to serve as a basis for a decision to deactivate one or more network function feature(s).

[0143] After execution of step 537, the CO 592 may receive a further indication 505 of the selected network function feature(s) from the OP 591, as illustrated by the optional loopback to step 528, or the CO 592 may proceed to step 538.

[0144] The indication 506 of the determined potential consumption reduction may take any suitable form (e.g., remaining consumption or consumption reduction, expressed in relative or absolute terms, specified per selected network function feature or cumulatively - for all network function features indicated by the latest selection indication 505 or for all network function features indicated by all selection indications 505 thus far in the session of loopbacks to step 528).

[0145] In step 538, the CO 592 receives a deactivation decision 507 from the OP 591. The deactivation decision 507 may be an (implicit or explicit) instruction that all network function features indicated by the latest selection indication 505 are to be deactivated, or that all network function features indicated by all selection indications 505 in the session of loopbacks to step 528 are to be deactivated. Alternatively, the deactivation decision 507 may be an instruction that only some, specific one(s), of the network function features indicated by the selection indication(s) 505 is / are to be deactivated.

[0146] In step 540, the CO 592 causes deactivation of the selected network function feature(s) indicated by the deactivation decision 507, by providing a deactivation command 509 to the LS 593 (compare with step 140 of Figure 1).

[0147] The approaches of Figures 4 and 5 may be seen as exemplifying two different use cases, which are enabled by the proposed system architecture.

[0148] According to the first use case (compare with Figure 4), an operator may provide a desired consumption value (e.g., in terms of a desired consumption reduction or a desired remaining consumption) to the network consumption orchestration node, which collects information from the license server and the consumption server node to determine which network function feature(s) should be deactivated (e.g., based on importance, usage, and consumption) to reach the desired consumption value. The first use case may be seen as a reduction-driven approach.

[0149] According to the second use case (compare with Figure 5), an operator may be more active and determine which network function feature(s) should be evaluated and which network function feature(s) should be deactivated. The second use case may be seen as a feature-driven approach.

[0150] Figure 6 illustrates example signaling among a network consumption orchestration node (CO) 692, a license server (LS) 693, a network function (NF) 695, a consumption server node (CS) 694, and a network operator (OP) 691. For example, the signaling of Figure 6 may be seen as further exemplifying the signaling of Figure 4 and / or the first use case.

[0151] The CO 692 receives an indication 601 of a consumption reduction criterion from the OP 691 (compare with 401 of Figure 4).

[0152] Independently of timing of the indication 601, the LS 693 activates features of the NF 695 via the licensing mechanism (illustrated by 602), the NF 695 reports the usage per feature to the LS 693 (illustrated by 603), and the LS 693 keeps updated usage statistics for the features of the NF 695 (illustrated by 604).

[0153] The CO 692 sends (e.g., responsive to reception of the indication 601) a request to the LS 693, and acquires an indication of usage from the LS 693 (compare with 402 of Figure 4). In the example of Figure 6, this procedure comprises the following protocol: "get network license" 605, "return network license" 606, "get historical license data" 607, and "return historical license data" 608.

[0154] The CO 692 also sends a request 609 to the CS 694, and acquires a plurality 610 of consumption profiles from the CS 694 (compare with 403 of Figure 4). Typically, the request 609 may indicate which consumption profiles should be included in the plurality of consumption profiles (e.g., those corresponding to network function features indicates as active in the signaling 606, 608).

[0155] As illustrated by 611, the CO 692 selects one or more network function feature(s), determines potential consumption reduction, evaluates the potential consumption reduction in relation to a consumption reduction criterion, and takes a decision to deactivate selected network function feature(s). For example, the CO 692 may build an ordered list of consumption profiles and take the decision based on the ordered list (e.g., iteratively selecting more and more network function feature(s) from the ordered list until the consumption reduction criterion is fulfilled).

[0156] The CO 692 causes deactivation of the selected network function feature(s) by providing a deactivation command 617 to the LS 693 (compare with 409 of Figure 4), and the LS 693 deactivates the selected network function feature(s) via the licensing mechanism (illustrated by 618).

[0157] The CO 692 also reports the updated consumption for the communication network to the OP 691 (illustrated by 619).

[0158] Figure 7 illustrates example signaling among a network consumption orchestration node (CO) 792, a license server (LS) 793, a network function (NF) 795, a consumption server node (CS) 794, and a network operator (OP) 791. For example, the signaling of Figure 7 may be seen as further exemplifying the signaling of Figure 5 and / or the second use case.

[0159] The CO 792 receives request 701 for running (active) network function features and corresponding consumption profiles from the OP 791.

[0160] Independently of timing of the request 701, the LS 793 activates features of the NF 795 via the licensing mechanism (illustrated by 702), the NF 795 reports the usage per feature to the LS 793 (illustrated by 703), and the LS 793 keeps updated usage statistics for the features of the NF 795 (illustrated by 704).

[0161] The CO 792 sends (e.g., responsive to reception of the request 701) a request to the LS 793, and acquires an indication of usage from the LS 793 (compare with 502 of Figure 5). In the example of Figure 7, this procedure comprises the following protocol: "get network license" 705, "return network license" 706, "get historical license data" 707, and "return historical license data" 708.

[0162] The CO 792 also sends a request 709 to the CS 794, and acquires a plurality 710 of consumption profiles from the CS 794 (compare with 503 of Figure 5). Typically, the request 709 may indicate which consumption profiles should be included in the plurality of consumption profiles (e.g., those corresponding to network function features indicates as active in the signaling 706, 708).

[0163] The CO 792 provides the indications of usage and corresponding consumption profiles to the OP 791, as illustrated by 713 (compare with 504 of Figure 5). The CO 792 receives an indication 714 of the selected network function feature(s) from the OP 791 (compare with 505 of Figure 5).

[0164] The CO 792 determines a potential consumption reduction, which is achievable by deactivation of the selected network function feature(s) and provides an indication 715 of the determined potential consumption reduction to the OP 791 (compare with 506 of Figure 5).

[0165] As mentioned in connection with Figure 5, the signaling 714, 715 may be repeated for different selections of network function feature(s).

[0166] Then, the CO 792 receives a deactivation decision 716 from the OP 791 (compare with 507 of Figure 5).

[0167] The CO 792 causes deactivation of the selected network function feature(s) by providing a deactivation command 717 to the LS 793 (compare with 509 of Figure 5), and the LS 793 deactivates the selected network function feature(s) via the licensing mechanism (illustrated by 718).

[0168] Figure 8 illustrates an example method 800 according to some embodiments. For example, the method 100 may be performed by a network consumption orchestration node. Alternatively, or additionally, the method 800 may be seen as an example, or variant, of any of the principles described in connection to Figures 1, 4, and 6.

[0169] In step 805, a criterion input - e.g., a remaining consumption threshold value - is received (compare with 401, 405 of Figure 4 and 601 of Figure 6).

[0170] In step 810, usage information is gotten from the license server (compare with 110 of Figure 1, 402, 410 of Figure 4 and 605, 606, 607, 608 of Figure 6).

[0171] In step 815, consumption profile information is gotten from the consumption server node (compare with 120 of Figure 1, 403, 420 of Figure 4 and 609, 610 of Figure 6).

[0172] In step 820, an ordered list is built of consumption profiles for the active network function features. The list may be ordered based on any relevant combination of usage and consumption. For example, the list may be ordered by decreasing product between usage and consumption. Building the ordered list may be seen as a determination of potential consumption reduction for each of the active network function features (compare with 130 of Figure 1, 430 of Figure 4 and 611 of Figure 6).

[0173] In step 825, the total consumption is determined for the active network function features, and in step 830, it is determined whether the criterion specified by the criterion input of step 805 is fulfilled (i.e., whether the total consumption is below the remaining consumption threshold value). When the criterion is fulfilled (Y-path out of step 830), the determined total consumption is provided as an output in step 835, and the process is ended in step 840.

[0174] When the criterion is fulfilled (N-path out of step 830), the method proceeds to step 845, where it is determined whether the list has been completely scanned for potential network function features to deactivate.

[0175] When the list has been completely scanned (Y-path out of step 845), the determined total consumption is provided as an output in step 835, and the process is ended in step 840. The output of step 835 may also comprise an indication that the list has been completely scanned.

[0176] When the list has not been completely scanned (N-path out of step 845), the method proceeds to step 850, where the next item in the ordered list is selected.

[0177] In step 855 it is determined whether the newly selected item is associated with a critical network function feature.

[0178] When critical (Y-path out of step 855), the newly selected item is dismissed as a network function feature that should not be deactivated, and the process returns to step 845.

[0179] When non-critical (N-path out of step 855), the newly selected item is deactivated in step 860 (compare with 140 of Figure 1, 409, 440 of Figure 4 and 617 of Figure 6), and the process returns to step 825.

[0180] Figure 9 schematically illustrates an example apparatus 900 for controlling energy consumption and / or power consumption of a communication network associated with a plurality of network function features. For example, the apparatus 900 may be comprised, or comprisable, in a network consumption orchestration node (CO) 910. Alternatively, or additionally, the apparatus 900 may be configured to cause execution of one or more method steps as described herein (e.g., in connection to any of the Figures 1, 4, 5, 6, 7, and 8).

[0181] The apparatus 900 comprises a controller (CNTR; e.g., controlling circuitry or a control module) 920.

[0182] The controller 920 is configured to cause acquisition of an indication of usage for each network function feature from a license server of the communication network (compare, e.g., with step 110 of Figure 1) and acquisition of a plurality of consumption profiles from a consumption server node of the communication network (compare, e.g., with step 120 of Figure 1).

[0183] The acquisitions may be achieved via one or more interfaces (I / O; e.g., interfacing circuitry) 930 towards the license server and the consumption server node. The controller 920 is also configured to cause determination of a potential consumption reduction which is achievable by deactivation of a selected one of the network function features, wherein the potential consumption reduction is based on the usage of the selected network function feature and corresponding consumption profile (compare, e.g., with step 130 of Figure 1).

[0184] To this end, the controller 920 may comprise, or be otherwise associated with (e.g., connected, or connectable, to) a determiner (DET; e.g., determining circuitry or a determination module) 921. The determiner 921 may be configured to determine the potential consumption reduction.

[0185] Furthermore, the controller 920 is configured to cause deactivation of the selected network function feature by provision of a deactivation command to the license server (compare, e.g., with step 140 of Figure 1).

[0186] The deactivation command may be provided via an interface 930 towards the license server.

[0187] In some embodiments, the controller 920 is configured to cause selection of network function feature(s) (compare, e.g., with step 425 of Figure 4).

[0188] To this end, the controller 920 may comprise, or be otherwise associated with (e.g., connected, or connectable, to) a selector (SEL; e.g., selecting circuitry or a selection module) 922. The selector 922 may be configured to select network function feature(s).

[0189] In some embodiments, the controller 920 is configured to cause evaluation of the potential consumption reduction in relation to a consumption reduction criterion (compare, e.g., with step 435 of Figure 4), and selection of an additional network function feature or taking of a deactivation decision depending on the outcome of the evaluation.

[0190] To this end, the controller 920 may comprise, or be otherwise associated with (e.g., connected, or connectable, to) an evaluator (EV; e.g., evaluating circuitry or an evaluation module) 923. The evaluator 923 may be configured to evaluate the potential consumption reduction in relation to the consumption reduction criterion.

[0191] In some embodiments, the controller 920 is configured to cause reception of an indication of the consumption reduction criterion (compare, e.g., with step 405 of Figure 4), e.g., via an operator interface (OP IF; e.g., interfacing circuitry) 940 for control of the communication network.

[0192] In some embodiments, the controller 920 is configured to cause provision of the indication of usage and corresponding consumption profile via an operator interface 940 for control of the communication network (compare, e.g., with step 527 of Figure 5). In some embodiments, the controller 920 is configured to cause reception of an indication of the selected network function feature via the operator interface 940 (compare, e.g., with step 528 of Figure 5).

[0193] In some embodiments, the controller 920 is configured to cause provision of an indication of the determined potential consumption reduction via the operator interface 940 (compare, e.g., with step 537 of Figure 5).

[0194] In some embodiments, the controller 920 is configured to cause reception of the deactivation decision via the operator interface 940 (compare, e.g., with step 538 of Figure 5).

[0195] Figure 10 schematically illustrates an example system for controlling energy consumption and / or power consumption of a communication network 1000 associated with a plurality of network function features.

[0196] The system comprises a network consumption orchestration node (CO) 1020; e.g., the CO 910 of Figure 9. For example, the CO 1020 may be configured to cause execution of one or more method steps as described herein (e.g., in connection to any of the Figures 1, 4, 5, 6, 7, and 8). To this end, the CO 1020 is connected to a license server (LS) 1010 and a consumption server node (CS) 1030. For example, the CO 1020 may be an energy orchestrator (EO) and the CS 1030 may be an energy server (ES).

[0197] Typically, the CO 1020 is a new network element that is configured to communicate with the LS 1010 and the CS 1030, determine consumption reduction, and cause deactivation of one or more network function feature(s).

[0198] The LS 1010 is configured to manage network licenses in relation to the plurality of network function features associated with the communication network 1000, to provide an indication of usage for each network function feature to the CO 1020 for control of energy consumption of the communication network 1000, and to deactivate a selected network function feature responsive to receiving a deactivation command from the CO 1020.

[0199] Typically, the LS 1010 is a network element responsible for managing network licenses in the communication network 1000. It may be implemented based on a license server according to the prior art, extended by introduction of an interface towards the CO 1020 and by introduction of the consumption profile identity specifying correspondence between a network function feature and a consumption profile.

[0200] The CS 1030 is configured to store consumption profiles corresponding to the plurality of network function features associated with the communication network 1000, and to provide one or more of the stored consumption profiles to the CO 1020 for control of energy consumption of the communication network 1000. Typically, the CS 1030 is a new network element that is configured to communicate with the CO 1020 to provide consumption profile information.

[0201] One or more of the LS 1010, the CO 1020, and the CS 1030 may be comprised in the communication network 1000 (e.g., in a central domain of the communication network 1000). In some embodiments, one or more of the LS 1010, the CO 1020, and the CS 1030 may be implemented in the context of an open radio access network (O-RAN) structure. In some embodiments, the LS 1010 is part of the operations support system (OSS) domain of the communication network.

[0202] Alternatively, one or more of the LS 1010, the CO 1020, and the CS 1030 may be external to the communication network 1000.

[0203] One or more of the LS 1010, the CO 1020, and the CS 1030 may be implemented by cloud technology. For example, some or all steps taken by the CO 1020 may be performed by distributed processing according to principles of cloud computing, as illustrated by 1050. Alternatively, or additionally, the LS 1010 and / or the CS 1030 may be implemented as a distributed server within a cloud solution.

[0204] One or more of the LS 1010, the CO 1020, and the CS 1030 may be implemented as standalone physical nodes, or may be incorporated in existing node(s) (e.g., existing network node(s) or existing cloud solution node(s)). For example, one or more of the LS 1010, the CO 1020, and the CS 1030 may be implemented as logical / virtualized entities within a physical system architecture.

[0205] Generally, it should be noted that features and advantages described in connection with one Figure or embodiment is equally applicable - as suitable and mutatis mutandis - in the context of other Figure(s) and embodiment(s), even if not explicitly mentioned in connection thereto.

[0206] The described embodiments and their equivalents may be realized in software or hardware or a combination thereof. The embodiments may be performed by general purpose circuitry. Examples of general purpose circuitry include digital signal processors (DSP), central processing units (CPU), co-processor units, field programmable gate arrays (FPGA) and other programmable hardware. Alternatively, or additionally, the embodiments may be performed by specialized circuitry, such as application specific integrated circuits (ASIC). The general purpose circuitry and / or the specialized circuitry may, for example, be associated with or comprised in an apparatus such as a network consumption orchestration node, a license server, or a consumption server node.

[0207] Embodiments may appear within an electronic apparatus (such as a network consumption orchestration node, a license server, or a consumption server node) comprising arrangements, circuitry, and / or logic according to any of the embodiments described herein. Alternatively, or additionally, an electronic apparatus (such as a network consumption orchestration node, a license server, or a consumption server node) may be configured to perform methods according to any of the embodiments described herein.

[0208] Figure 11 illustrates an example non-transitory computer readable medium 1100 in the form of a compact disc (CD) read-only memory (ROM).

[0209] According to some embodiments, a computer program product 1102 comprises a non-transitory computer readable medium such as, for example, a universal serial bus (USB) memory, a plug-in card, an embedded drive, or a read-only memory. Exemplifying a computer program product by the non-transitory computer readable medium 1100 of Figure 11, the computer readable medium has stored thereon a computer program 1101 comprising program instructions. The computer program is loadable into a data processor (PROC; e.g., a data processing unit) 1120, which may, for example, be comprised in a network consumption orchestration node 1110. When loaded into the data processor, the computer program may be stored in a memory (MEM) 1130 associated with, or comprised in, the data processor. According to some embodiments, the computer program may, when loaded into, and run by, the data processor, cause execution of method steps according to, for example, any of the methods illustrated in Figures 1, 4, 5, and 8; or otherwise described herein.

[0210] Alternatively, or additionally, a non-transitory computer readable medium (such as the non- transitory computer readable medium 1100 of Figure 11) may have stored thereon one or more consumption profiles. The consumption profiles are loadable into a data storing unit (DSU) 1150, which may, for example, be comprised in a consumption server node 1140.

[0211] Figure 12 shows an example of a communication system 1200 in accordance with some embodiments.

[0212] In the example, the communication system 1200 includes a telecommunication network 1202 (compare with 1000 of Figure 10) that includes an access network 1204, such as a radio access network (RAN), and a core network 1206, which includes one or more core network nodes 1208. The access network 1204 includes one or more access network nodes, such as network nodes 1210a and 1210b (one or more of which may be generally referred to as network nodes 1210), or any other similar 3rd Generation Partnership Project (3GPP) access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network 1202 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 1202 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network 1202, including one or more network nodes 1210 and / or core network nodes 1208.

[0213] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective "open" designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes 1210 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 1212a, 1212b, 1212c, and 1212d (one or more of which may be generally referred to as UEs 1212) to the core network 1206 over one or more wireless connections.

[0214] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 1200 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 1200 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0215] The UEs 1212 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 1210 and other communication devices. Similarly, the network nodes 1210 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 1212 and / or with other network nodes or equipment in the telecommunication network 1202 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 1202. In the depicted example, the core network 1206 connects the network nodes 1210 to one or more hosts, such as host 1216. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 1206 includes one or more core network nodes (e.g., core network node 1208) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 1208. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0216] The host 1216 may be under the ownership or control of a service provider other than an operator or provider of the access network 1204 and / or the telecommunication network 1202, and may be operated by the service provider or on behalf of the service provider. The host 1216 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0217] As a whole, the communication system 1200 of Figure 12 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0218] In some examples, the telecommunication network 1202 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 1202 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1202. For example, the telecommunications network 1202 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.

[0219] In some examples, the UEs 1212 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 1204 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1204. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0220] In the example, the hub 1214 communicates with the access network 1204 to facilitate indirect communication between one or more UEs (e.g., UE 1212c and / or 1212d) and network nodes (e.g., network node 1210b). In some examples, the hub 1214 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 1214 may be a broadband router enabling access to the core network 1206 for the UEs. As another example, the hub 1214 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 1210, or by executable code, script, process, or other instructions in the hub 1214. As another example, the hub 1214 may be a data collectorthat acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 1214 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 1214 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1214 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 1214 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0221] The hub 1214 may have a constant / persistent or intermittent connection to the network node 1210b. The hub 1214 may also allow for a different communication scheme and / or schedule between the hub 1214 and UEs (e.g., UE 1212c and / or 1212d), and between the hub 1214 and the core network 1206. In other examples, the hub 1214 is connected to the core network 1206 and / or one or more UEs via a wired connection. Moreover, the hub 1214 may be configured to connect to an M2M service provider over the access network 1204 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 1210 while still connected via the hub 1214 via a wired or wireless connection. In some embodiments, the hub 1214 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 1210b. In other embodiments, the hub 1214 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 1210b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0222] Figure 13 shows a network node 1300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0223] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0224] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, SelfOrganizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0225] The network node 1300 includes a processing circuitry 1302, a memory 1304, a communication interface 1306, and a power source 1308. The network node 1300 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 1300 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 1300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 1304 for different RATs) and some components may be reused (e.g., a same antenna 1310 may be shared by different RATs). The network node 1300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1300.

[0226] The processing circuitry 1302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node 1300 components, such as the memory 1304, to provide network node 1300 functionality.

[0227] In some embodiments, the processing circuitry 1302 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1302 includes one or more of radio frequency (RF) transceiver circuitry 1312 and baseband processing circuitry 1314. In some embodiments, the radio frequency (RF) transceiver circuitry 1312 and the baseband processing circuitry 1314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 1312 and baseband processing circuitry 1314 may be on the same chip or set of chips, boards, or units.

[0228] The memory 1304 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or nonvolatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 1302. The memory 1304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 1302 and utilized by the network node 1300. The memory 1304 may be used to store any calculations made by the processing circuitry 1302 and / or any data received via the communication interface 1306. In some embodiments, the processing circuitry 1302 and memory 1304 is integrated. The communication interface 1306 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 1306 comprises port(s) / terminal(s) 1316 to send and receive data, for example to and from a network over a wired connection. The communication interface 1306 also includes radio front-end circuitry 1318 that may be coupled to, or in certain embodiments a part of, the antenna 1310. Radio front-end circuitry 1318 comprises filters 1320 and amplifiers 1322. The radio front-end circuitry 1318 may be connected to an antenna 1310 and processing circuitry 1302. The radio front-end circuitry may be configured to condition signals communicated between antenna 1310 and processing circuitry 1302. The radio front-end circuitry 1318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 1318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1320 and / or amplifiers 1322. The radio signal may then be transmitted via the antenna 1310. Similarly, when receiving data, the antenna 1310 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1318. The digital data may be passed to the processing circuitry 1302. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0229] In certain alternative embodiments, the network node 1300 does not include separate radio front-end circuitry 1318, instead, the processing circuitry 1302 includes radio front-end circuitry and is connected to the antenna 1310. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1312 is part of the communication interface 1306. In still other embodiments, the communication interface 1306 includes one or more ports or terminals 1316, the radio front-end circuitry 1318, and the RF transceiver circuitry 1312, as part of a radio unit (not shown), and the communication interface 1306 communicates with the baseband processing circuitry 1314, which is part of a digital unit (not shown).

[0230] The antenna 1310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 1310 may be coupled to the radio front-end circuitry 1318 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 1310 is separate from the network node 1300 and connectable to the network node 1300 through an interface or port.

[0231] The antenna 1310, communication interface 1306, and / or the processing circuitry 1302 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 1310, the communication interface 1306, and / or the processing circuitry 1302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0232] The power source 1308 provides power to the various components of network node 1300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 1308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1300 with power for performing the functionality described herein. For example, the network node 1300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies powerto power circuitry of the power source 1308. As a further example, the power source 1308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0233] Embodiments of the network node 1300 may include additional components beyond those shown in Figure 13 for providing certain aspects of the network node's functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 1300 may include user interface equipment to allow input of information into the network node 1300 and to allow output of information from the network node 1300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1300.

[0234] Figure 14 is a block diagram illustrating a virtualization environment 1400 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1400 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 1400 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface. Applications 1402 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0235] Hardware 1404 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1406 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1408a and 1408b (one or more of which may be generally referred to as VMs 1408), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 1406 may present a virtual operating platform that appears like networking hardware to the VMs 1408.

[0236] The VMs 1408 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1406. Different embodiments of the instance of a virtual appliance 1402 may be implemented on one or more of VMs 1408, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0237] In the context of NFV, a VM 1408 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 1408, and that part of hardware 1404 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 1408 on top of the hardware 1404 and corresponds to the application 1402.

[0238] Hardware 1404 may be implemented in a standalone network node with generic or specific components. Hardware 1404 may implement some functions via virtualization. Alternatively, hardware 1404 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 1410, which, among others, oversees lifecycle management of applications 1402. In some embodiments, hardware 1404 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 1412 which may alternatively be used for communication between hardware nodes and radio units.

[0239] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0240] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device- readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

[0241] Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and / or is implied from the context in which it is used. Reference has been made herein to various embodiments. However, a person skilled in the art would recognize numerous variations to the described embodiments that would still fall within the scope of the claims.

[0242] For example, the method embodiments described herein discloses example methods through steps being performed in a certain order. However, it is recognized that these sequences of events may take place in another order without departing from the scope of the claims. Furthermore, some method steps may be performed in parallel even though they have been described as being performed in sequence. Thus, the steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and / or where it is implicit that a step must follow or precede another step.

[0243] In the same manner, it should be noted that in the description of embodiments, the partition of functional blocks into particular units is by no means intended as limiting. Contrarily, these partitions are merely examples. Functional blocks described herein as one unit may be split into two or more units. Furthermore, functional blocks described herein as being implemented as two or more units may be merged into fewer (e.g. a single) unit.

[0244] Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever suitable. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa.

[0245] Hence, it should be understood that the details of the described embodiments are merely examples brought forward for illustrative purposes, and that all variations that fall within the scope of the claims are intended to be embraced therein.

Claims

CLAIMS1. A computer-implemented method (100) for controlling energy consumption and / or power consumption of a communication network associated with a plurality of network function features, the method comprising: acquiring (110, 410, 510) an indication (402, 502) of usage for each network function feature from a license server of the communication network; acquiring (120, 420, 520) a plurality of consumption profiles (300, 403, 503) from a consumption server node of the communication network, wherein each consumption profile corresponds to a specific one of the network function features; determining (130, 430, 530) a potential consumption reduction which is achievable by deactivation of a selected one of the network function features, wherein the potential consumption reduction is based on the usage of the selected network function feature and the corresponding consumption profile; and causing (140, 440, 540) deactivation of the selected network function feature by providing a deactivation command (409, 509) to the license server responsive to a deactivation decision for the selected network function feature, wherein the deactivation decision is based on the potential consumption reduction.

2. The method of claim 1, wherein each consumption profile (300) comprises a consumption profile identity (305) specifying the correspondence between consumption profile and network function feature.

3. The method of any of claims 1 through 2, wherein the consumption profile (300) comprises an indication (306) of consumption associated with use of the corresponding network function feature.

4. The method of claim 3, wherein the potential consumption reduction for the selected network function feature is based on the acquired usage for the network function feature and the consumption indicated by the corresponding consumption profile.

5. The method of any of claims 1 through 4, wherein the consumption profile (300) comprises an indication (307) of importance of the corresponding network function feature, wherein the indication of importance is selected from a group of importance values comprising at least a first importance value and a second importance value, wherein the first importance value indicates higher importance than the second importance value.

6. The method of claim 5, wherein network function features with corresponding consumption profiles indicating the first importance value are excluded from being selected network function features.

7. The method of any of claims 1 through 6, further comprising performing network function feature selection (425).

8. The method of claim 7, further comprising: evaluating (435) the potential consumption reduction which is achievable by deactivation of the selected network function feature(s) in relation to a consumption reduction criterion; selecting (425) an additional network function feature responsive to non-fulfillment of the consumption reduction criterion; and taking the deactivation decision for the selected network function feature(s) responsive to fulfillment of the consumption reduction criterion.

9. The method of claim 8, wherein the consumption reduction criterion comprises one or more of: the potential consumption reduction which is achievable by deactivation of the selected network function feature(s) equals, or exceeds, a reduction threshold; the potential consumption reduction which is achievable by deactivation of the selected network function feature(s) yields a remaining consumption which is lower than a remainder threshold; and the number of selected network function features reaching a maximum number of deactivated network function features.

10. The method of any of claims 8 through 9, further comprising receiving (405) an indication(401) of the consumption reduction criterion via an operator interface for control of the communication network.

11. The method of any of claims 1 through 6, further comprising: providing (527) the indication of usage and corresponding consumption profile (504) via an operator interface for control of the communication network; and receiving (528) an indication (505) of the selected network function feature via the operator interface.

12. The method of claim 11, further comprising providing (537) an indication (506) of the determined potential consumption reduction via the operator interface.

13. The method of any of claims 11 through 12, further comprising receiving (538) the deactivation decision (507) via the operator interface.

14. A computer program product (1102) comprising a non-transitory computer readable medium(1100), having thereon a computer program (1101) comprising program instructions, the computer program being loadable into a data processing unit and configured to cause execution of the method according to any of claims 1 through 13 when the computer program is run by the data processing unit.

15. A computer program (1101) comprising program instructions, the computer program being loadable into a data processing unit and configured to cause execution of the method according to any of claims 1 through 13 when the computer program is run by the data processing unit.

16. An apparatus (900) for controlling energy consumption and / or power consumption of a communication network associated with a plurality of network function features, the apparatus comprising controlling circuitry (920) configured to cause: acquisition of an indication (402, 502) of usage for each network function feature from a license server of the communication network; acquisition of a plurality of consumption profiles (300, 403, 503) from a consumption server node of the communication network, wherein each consumption profile corresponds to a specific one of the network function features; determination of a potential consumption reduction which is achievable by deactivation of a selected one of the network function features, wherein the potential consumption reduction is based on the usage of the selected network function feature and the corresponding consumption profile; and deactivation of the selected network function feature by provision of a deactivation command (409, 509) to the license server responsive to a deactivation decision for the selected network function feature, wherein the deactivation decision is based on the potential consumption reduction.

17. The apparatus of claim 16, wherein each consumption profile (300) comprises a consumption profile identity (305) specifying the correspondence between consumption profile and network function feature.

18. The apparatus of any of claims 16 through 17, wherein the consumption profile (300) comprises an indication (306) of consumption associated with use of the corresponding network function feature.

19. The apparatus of claim 18, wherein the potential consumption reduction for the selected network function feature is based on the acquired usage for the network function feature and the consumption indicated by the corresponding consumption profile.

20. The apparatus of any of claims 16 through 19, wherein the consumption profile (300) comprises an indication (307) of importance of the corresponding network function feature, wherein the indication of importance is selected from a group of importance values comprising at least a first importance value and a second importance value, wherein the first importance value indicates higher importance than the second importance value.

21. The apparatus of claim 20, wherein network function features with corresponding consumption profiles indicating the first importance value are excluded from being selected network function features.

22. The apparatus of any of claims 16 through 21, wherein the controlling circuitry (920) is further configured to cause performance of network function feature selection.

23. The apparatus of claim 22, wherein the controlling circuitry (920) is further configured to cause: evaluation of the potential consumption reduction which is achievable by deactivation of the selected network function feature(s) in relation to a consumption reduction criterion; selection of an additional network function feature responsive to non-fulfillment of the consumption reduction criterion; and the deactivation decision to be taken for the selected network function feature(s) responsive to fulfillment of the consumption reduction criterion.

24. The apparatus of claim 23, wherein the consumption reduction criterion comprises one or more of: the potential consumption reduction which is achievable by deactivation of the selected network function feature(s) equals, or exceeds, a reduction threshold; the potential consumption reduction which is achievable by deactivation of the selected network function feature(s) yields a remaining consumption which is lower than a remainder threshold; andthe number of selected network function features reaching a maximum number of deactivated network function features.

25. The apparatus of any of claims 23 through 24, wherein the controlling circuitry (920) is further configured to cause reception of an indication (401) of the consumption reduction criterion via an operator interface for control of the communication network.

26. The apparatus of any of claims 16 through 21, wherein the controlling circuitry (920) is further configured to cause: provision of the indication of usage and corresponding consumption profile (504) via an operator interface for control of the communication network; and reception of an indication (505) of the selected network function feature via the operator interface.

27. The apparatus of claim 26, wherein the controlling circuitry (920) is further configured to cause provision of an indication (506) of the determined potential consumption reduction via the operator interface.

28. The apparatus of any of claims 26 through T1 , wherein the controlling circuitry (920) is further configured to cause reception of the deactivation decision (507) via the operator interface.

29. A network consumption orchestration node (492, 592, 692, 792, 910, 1020) comprising the apparatus of any of claims 16 through 28.

30. A license server (493, 593, 693, 793, 1010) for a communication network, for managing network licenses (200) in relation to a plurality of network function features, wherein the license server is configured to: provide an indication of usage for each network function feature to a network consumption orchestration node for control of energy consumption and / or power consumption of the communication network by determination of a potential consumption reduction which is achievable by deactivation of a selected one of the network function features, wherein the indication of usage is associated with a consumption profile identity specifying correspondence between a consumption profile and the network function feature, and wherein the potential consumption reduction is based on the usage of the selected network function feature and the corresponding consumption profile; and deactivate the selected network function feature responsive to receiving a deactivation command from the network consumption orchestration node, wherein the deactivation command corresponds to a deactivation decision based on the potential consumption reduction.

31. A consumption profile (300) corresponding to a network function feature for control of energy consumption and / or power consumption of a communication network associated with the network feature, wherein the consumption profile comprises a consumption profile identity (305) specifying the correspondence between the consumption profile and the network function feature.

32. The consumption profile of claim 31, further comprising an indication (306) of consumption associated with use of the corresponding network function feature.

33. The consumption profile of any of claims 31 through 32, further comprising an indication(307) of importance of the corresponding network function feature, wherein the indication of importance is selected from a group of importance values comprising at least a first importance value and a second importance value, wherein the first importance value indicates higher importance than the second importance value.

34. A consumption server node (494, 594, 694, 794, 1030) configured to store one or more consumption profiles according to any of claims 31 through 33, and to provide one or more of the stored consumption profiles to a network consumption orchestration node for control of energy consumption and / or power consumption of a communication network associated with a plurality of network function features by determination of a potential consumption reduction which is achievable by deactivation of a selected network function feature, wherein the potential consumption reduction is based on a usage of the selected network function feature and the corresponding consumption profile.

35. A non-transitory computer readable medium (1100), having thereon one or more consumption profiles according to any of claims 31 through 33, the consumption profiles being loadable into a data storing unit of the consumption server node of claim 34.

36. A system for controlling energy consumption and / or power consumption of a communication network associated with a plurality of network function features, the system comprising the network consumption orchestration node of claim 29, the license server of claim 30, and the consumption server node of claim 34.

Images