Energy consumption control

Abstract

A network entity or functionality determines an energy consumption value associated with a service for a UE and determines whether the energy consumption is acceptable based on a comparison with a max

Description

BACKGROUND Field Certain examples of the present disclosure provide one or more techniques for energy consumption control, for example in Dual Connectivity (DC) in a 3rd Generation Partnership Project (3GPP) 5th Generation (5G) New Radio (NR) network. Description of the Related Art Herein, the following document may be referenced: [1] 3GPP RP-231159 on AI / ML for NG-RAN. [2] 3GPP SP-220446 New SID: Study on Energy Efficiency as service criteria. [3] 3GPP TR 37.817 Study on enhancement for data collection for NR and ENDC. [4] 3GPP RAN3#121 chairman report. [5] 3GPP SP-230235 Revised SID on Energy Efficiency as service criteria (FS_EnergyServ). [6] 3GPP TS 37.340 (e.g. V17.5.0) NR; Multi-connectivity; Overall description; Stage-2. Various acronyms, abbreviations and definitions used in the present disclosure are defined at the end of this description. In 3GPP RAN#100, RAN approved the revised work item (Wl) on AI / ML for NG-RAN in [RP-231159]. The following are the objectives of this Wl: Normative work is based on the conclusions captured in TR37.817. The detailed objectives of the Wl are listed as follows: • Specify data collection enhancements and signaling support within existing NG-RAN interfaces and architecture (including non-split architecture and split architecture) for AI / ML-based Network Energy Saving, Load Balancing and Mobility Optimization. (RAN3) RAN3 has been discussing the use case on AI / ML-based Network Energy Saving (ES) and signaling over Xn [RAN3 chairman report [RAN3#121]]: ES and Xn procedures AI / ML based Energy Savinci: • Current Energy Efficiency metric can be exchanged between RAN nodes for the energy saving use case. • Energy Efficiency constitutes a metric that reflects the energy consumption of a cell or a node. It is FFS what the granularity and exact coding of this metric is. • The "Energy Efficiency" metric should be measurable, produced and interpretable by the RAN. • Start with per node granularity EE and Per cell granularity EE could be considered if it is feasible. • l / l / A Take the EE defined in SA5 as the baseline for the energy efficiency of a gNB. • Introduce the metric of Energy Cost (EC) as the AI / ML metric to be shared over the Xn interface among gNBs. • Adopt the below Option-3a and exchange Energy Cost (EC) upon request over the Xn interface. • The metric of Energy Cost (EC) exchanged between NG-RAN nodes can be an inferred energy consumption related to an additional load or an actual energy consumption value from a neighboring node for either additional load or current load (The details to be further discussed). EC is a value at gNB level. • WA: If the Energy Cost is encoded as an index (0, ..Max), representing energy consumption on a linear scale, it is agreed that the CAM configures rules to a NG-RAN node to determine how to normalize the values of the EC. The rules shall be the same at least for all neighboring NG-RAN nodes within the area where a request on EC reporting is triggered by a source NG-RAN node. • It is agreed that the Energy Cost is a node level parameter. Further EC granularities are out of scope of Rei 18. • 3GPP SA1 completed a Study item on Energy Efficiency as service criteria (FS_EnergyServ) [SP-230235], Energy consumption as a service criteria was agreed as part of the consolidated requirements in section 6.1 in the technical report TR 22.822. 6.1 Energy consumption as service criteria This subclause contains the requirements related to energy consumption as service criteria and supporting energy credit limit for specific service. Table 6.1-1 - Consolidated requirements on energy consumption as service criteria CPR# Consolidated Potential Requirement Original PR # Comment CPR 6.7-7 Subject to operator's policy, the 5G system shall support subscription policies and means to enforce the policy that define a maximum energy consumption rate for services without QoS criteria. NOTE x: The granularity of the subscription policies can either apply to the subscriber (all services), or to particular services. PR 5.1.6-1, PR 5.1.6-2 merge CPR 6.1-2 The 5G network shall support a means to define maximum energy consumption rate with specific granularities (which include subscriber granularity, network slice granularity). PR 5.1.6-3 CPR 6.1-3 Subject to operator’s policy, the 5G system shall support subscription policies that define a maximum energy credit limit for services. NOTE x: The definition of subscription is in TS 21.905. P.R 5.5.6-1 Definition of subscription is in TS 21905 maximum energy credit limit: a policy establishing an upper bound on the quantity of energy used by the 5G system to provide services provided to a specific subscriber.(clause 3.1) The above information is presented as background information only to assist with an understanding of the present disclosure. No determination has been made, and no assertion is made, as to whether any of the above might be applicable as prior art with regard to the present invention. 10 SUMMARY It is an aim of certain examples of the present disclosure to address, solve and / or mitigate, at least partly, at least one of the problems and / or disadvantages associated with the related art, for example at least one of the problems and / or disadvantages described herein. It is an aim of certain examples of the present disclosure to provide at least one advantage over the 15 related art, for example at least one of the advantages described herein. The present invention is defined in the independent claims. Advantageous features are defined in the dependent claims. Embodiments or examples disclosed in the description and / or figures falling outside the scope of the claims are to be understood as examples useful for understanding the present invention. Other aspects, advantages and salient features of the invention will become apparent to those skilled in the art from the following detailed description taken in conjunction with the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS Figure 1 illustrates an exemplary method for controlling energy consumption in a network; and Figure 2 is a block diagram of an exemplary network entity that may be used in certain examples of the present disclosure. DETAILED DESCRIPTION The following description of examples of the present disclosure, with reference to the accompanying drawings, is provided to assist in a comprehensive understanding of the present invention, as defined by the claims. The description includes various specific details to assist in that understanding but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the examples described herein can be made without departing from the scope of the invention. The same or similar components may be designated by the same or similar reference numerals, although they may be illustrated in different drawings. Detailed descriptions of techniques, structures, functions, operations or processes known in the art may be omitted for clarity and conciseness, and to avoid obscuring the subject matter of the present invention. The terms and words used herein are not limited to the bibliographical or standard meanings, but, are merely used to enable a clear and consistent understanding of the invention. Throughout the description and claims of this specification, the words “comprise”, “include” and “contain” and variations of the words, for example “comprising” and “comprises”, means “including but not limited to”, and is not intended to (and does not) exclude other features, elements, components, integers, steps, processes, operations, functions, characteristics, properties and / or groups thereof. Throughout the description and claims of this specification, the singular form, for example “a”, “an” and “the”, encompasses the plural unless the context otherwise requires. For example, reference to “an object” includes reference to one or more of such objects. Throughout the description and claims of this specification, language in the general form of “X for Y” (where Y is some action, process, operation, function, activity or step and X is some means for carrying out that action, process, operation, function, activity or step) encompasses means X adapted, configured or arranged specifically, but not necessarily exclusively, to do Y. Features, elements, components, integers, steps, processes, operations, functions, characteristics, properties and / or groups thereof described or disclosed in conjunction with a particular aspect, embodiment, example or claim are to be understood to be applicable to any other aspect, embodiment, example or claim described herein unless incompatible therewith. The skilled person will appreciate that the techniques described herein may be used in any suitable combination. Certain examples of the present disclosure provide one or more techniques for energy consumption control, for example in Dual Connectivity in a 3GPP 5G NR network. However, the skilled person will appreciate that the present invention is not limited to these examples, and may be applied in any suitable system or standard, for example one or more existing and / or future generation wireless communication systems or standards, including any existing or future releases of the same standards specification, for example 3GPP 5G. The functionality of the various network entities and other features disclosed herein may be applied to corresponding or equivalent entities or features in the same or any other suitable communication systems or standards. Corresponding or equivalent entities or features may be regarded as entities or features that perform the same or similar role, function or purpose within the network. For example, the functionality of a NG-RAN node (e.g. a base station, eNB or gNB) in the examples below may be applied to any other suitable type of entity performing RAN functions. A particular network entity may be implemented as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, and / or as a virtualised function instantiated on an appropriate platform, e.g. on a cloud infrastructure. The skilled person will appreciate that the present invention is not limited to the specific examples disclosed herein. For example: • The techniques disclosed herein are not limited to 3GPP 5G. For example, the techniques disclosed herein may be applied to 3GPP 5G-advanced or 6G, and / or any existing and / or future 3GPP Release (e.g. Rel-19, 20, etc.), and / or any suitable non-3GPP technology. • One or more entities in the examples disclosed herein may be replaced with one or more alternative entities performing equivalent or corresponding functions, processes or operations. • One or more of the messages in the examples disclosed herein may be replaced with one or more alternative messages, signals or other type of information carriers that communicate equivalent or corresponding information. • One or more further elements or entities may be added to the examples disclosed herein. • One or more non-essential elements or entities may be omitted in certain examples. • The functions, processes or operations of a particular entity in one example may be divided between two or more separate entities in an alternative example. • The functions, processes or operations of two or more separate entities in one example may be performed by a single entity in an alternative example. • Information carried by a particular message in one example may be carried by two or more separate messages in an alternative example. • Information carried by two or more separate messages in one example may be carried by a single message in an alternative example. • The order in which operations are performed and / or the order in which messages are transmitted may be modified, if possible, in alternative examples. Certain examples of the present disclosure may be provided in the form of an apparatus / device / network entity configured to perform one or more defined network functions and / or a method therefor. Certain examples of the present disclosure may be provided in the form of a system (e.g. network or wireless communication system) comprising one or more such apparatuses / devices / network entities, and / or a method therefor. As explained above, the network can define energy policies in order to enforce the maximum energy consumption rate and / or maximum energy credit limit for all services (or particular services), with or without QoS criteria, for a given subscriber. However, one problem is how the network performs enforcement of the maximum energy consumption rate and / or maximum energy credit limit for a subscriber (or a user equipment (UE)) that is in a dual connectivity scenario (e.g. EN-DC or MR-DC), in which the UE may be served by two RAN nodes, namely a Master node (MN) and Secondary Node (SN), e.g. a UE. Certain examples of the present disclosure provide one or more techniques to provide one or more energy enforcement policies that allow control of energy consumption, for example in a dual connectivity scenario. Certain examples address one or more of the following questions: 1. How to enforce the maximum energy consumption rate and / or maximum energy credit limit, for a given subscriber (or UE), in a dual connectivity scenario? 2. Whether the MN and / or SN perform(s) the maximum energy consumption rate and / or maximum energy credit limit? 3. How the MN and / or SN exchange assistance information related to the enforcement of the energy consumption? 4. How the MN, SN and / or the UE exchange assistance information related to the enforcement of the energy consumption? 5. How and what assistance information the UE may provide to the network in relation energy policy? 6. How the MN and / or SN decide(s) on moving QoS flows from the MN to SN and vice versa based on energy considerations? 7. How the MN and / or SN modifies the mapping of QoS flows to different bearers based on energy considerations? 8. How to network, MN, and / or SN changes the bearer type and / or bearer termination point based on energy considerations? Certain examples of the present disclosure address one or more problems related to energy consumption control in a dual connectivity scenario (e.g. EN-DC or MR-DC), in which the UE (or a group of UEs) may be served by two RAN nodes, for example a Master node (MN) and a Secondary Node (SN), and / or other network entities (and / or network functions). Certain examples provide interactions between the MN, SN, and / or other network entities (and / or functions) in order to control energy consumption for a given subscriber(s) (or UE(s)). Certain examples of the present disclosure provide a method for controlling energy consumption in a network, the method comprising: determining, by one or more network entities and / or functionalities, one or more energy consumption values associated with one or more services for one or more UEs; and determining, by the one or more network entities and / or functionalities, whether or not the one or more energy consumption values are acceptable based on a comparison between the one or more energy consumption values and one or more reference (e.g. maximum) energy consumption values for the one or more services for the one or more UEs. In certain examples, the maximum energy consumption values may be associated with one or more maximum energy consumption rates and / or one or more maximum energy credit limits for the one or more services for the one or more UEs. In certain examples, the method may further comprise setting and / or modifying one or more network parameters and / or configurations associated with the one or more services for the one or more UEs based on a result of the comparison. In certain examples, the setting and / or modifying may comprise setting and / or modifying, by a base station serving one or more of the UEs, mapping rules for QoS Flows to bearers based on the energy consumption values. In certain examples, the method may further comprise updating, by the one or more network entities and / or functionalities, the maximum energy consumption values. In certain examples, the one or more network entities and / or functionalities may comprise one or more RAN nodes (e.g. base station, eNB, gNB, NG-RAN) and / or one or more core network entities (e.g. AMF, SMF, MME, UPF). In certain examples, the one or more network entities and / or functions may comprise a first base station and a second base station capable of serving a UE in a dual connectivity scenario. In certain examples, the energy consumption values and / or maximum energy consumption values may comprise one or more combined values associated with the first and second base stations together, and / or one or more separate values associated with the first and second base stations individually. In certain examples, the method may further comprise determining, by the first and / or second base station, whether one or more maximum energy consumption values would be exceeded for one or more services for a certain UE if the UE participated in dual connectivity. In certain examples, the method may further comprise configuring a UE behaviour for a UE participating in dual connectivity based on energy consumption. In certain examples, the method may further comprise receiving, by one or more network entities, from a UE, an indication of capability to support network access based on energy consumption. In certain examples, the method may further comprise transmitting, by one or more network entities, to a UE, assistance information for controlling access to the network based on energy consumption. In certain examples, one or more of the energy consumption values and / or maximum energy consumption values may be associated with one or more of: one or more of traffic flows; one or more PDU sessions; one or more QoS flows; one or more Main Cell Group (MCG) bearers; one or more Secondary Cell Group (SCG) bearers; one or more Master Node (MN) terminated bearers; one or more Secondary Node (SN) terminated bearers; one or more split bearers; and one or more network slices. In certain examples, the method may further comprise transmitting, from a first one of the network entities (e.g. a MN or a core network entity) to a second one of the network entities (e.g. a SN or a NG-RAN node), information relating to the energy consumption values and / or the maximum energy consumption values. In certain examples, the information may be transmitted from the first network entity to the second network entity in a certain IE. In certain examples, the method may further comprise reconfiguring one or more traffic flows based on a comparison between the one or more energy consumption values and one or more minimum energy consumption values. In certain examples, one or more of the UEs may comprise a subscriber, and each subscriber may be associated with subscription information comprising energy related information. Certain examples of the present disclosure provide a network entity (e.g. AMF, SMF) and / or a base station (e.g. eNB, gNB) configured to perform a method according to any example, aspect, embodiment and / or claim disclosed herein. Certain examples of the present disclosure provide a network (or wireless communication system) comprising a UE and one or more network entities according to any examples, aspects, embodiments and / or claims disclosed herein. Certain examples of the present disclosure provide a computer program comprising instructions which, when the program is executed by a computer or processor, cause the computer or processor to carry out a method according to any example, aspect, embodiment and / or claim disclosed herein. Certain examples of the present disclosure provide a computer or processor-readable data carrier having stored thereon a computer program according to any example, aspect, embodiment and / or claim disclosed herein. Various examples and features will now be described. The skilled person will appreciate that these examples and features may be used individually or in any suitable combination. General examples The techniques described herein may apply for a particular subscriber, e.g. based on subscription information (that may be defined and optionally forwarded to other network nodes e.g. from the UDM), or for a group of subscribers, or for all subscribers. For example, a subscriber may refer to a UE. The techniques may apply at a certain time, or at all times, or for a certain location or regardless of the location. The techniques described herein may apply fora UE in any state such as RRC-CONNECTED, RRC-IDLE, RRC-CONNECTED with inactive indication, RRC-IDLE with suspend indication, RRC-INACTIVE, etc., or for any NAS mode, e.g. 5GMM-CONNECTED mode, 5GMM-IDLE mode, 5GMM-CONNECTED mode with RRC inactive indication, or any combination of RRC state and NAS mode. A set of (one or more) network entities (and / or functionalities) may define (or set) a certain level (threshold, upper bound, lower bound and / or granularity, etc.) of energy consumption value(s) associated with all services (or some services or a particular service) for a given subscriber (or UE) or groups of subscribers (or group of UEs) or for all UEs. These values maybe related to a given time and / or location. The set of (one or more) network entities (and / or functionalities) may update the certain level (and / or threshold or upper and / or lower bound or granularity, etc.) of energy consumption value(s) (or quantities) associated with all services (or some services or a particular service) for a given subscriber (or UE) or groups of subscribers (or group of UEs). These values maybe related to a given time and / or location. The set of network entities (and / or functionalities) may also calculate, measure, aggregate, estimate, predict, and / or obtain (from at least another network entity and / or function, application function, OAM, server, etc.) the values (or quantities) of (and / or information related to) the energy consumption associated to all services (or some services or a particulate service) for a given UE (or groups of UEs). A set of (one or more) network entities (and / or functionalities) may define (or set or determine) a certain level (threshold, upper bound, lower bound and / or granularity, etc.) of the maximum energy consumption rate and / or maximum energy credit limit for all services (or some services or a particular service) for a UE (or groups of UEs). These values maybe related to a given time and / or location. The set of (one or more) network entities (and / or functionalities) may calculate, measure, aggregate, estimate, predict, and / or obtain (from at least another network entity and / or function, application function, OAM, server, etc.) the values of (and / or information related to) the maximum energy consumption rate and / or maximum energy credit limit for all services (or some services or a particular service for a given UE (or groups of UEs). The set of (one or more) network entities (and / or functionalities) may define (or set or categorise or assign or classify, etc.) certain value(s) of energy consumption, for a given entity(-ies) (and / or network function(s)), in relation to providing services to a given subscriber(s) (or UE or a groups of UEs), as acceptable (or permitted or allowed or recommended) or not acceptable (or not permitted or allowed or recommended) or acceptable or recommended (or not acceptable or recommended) for a given period of time and / or a given location. The set of (one or more) network entities (and / or functionalities) may decide (or conclude or determine) that the value(s) (quantities, levels and / or rates) of energy consumption are acceptable or not acceptable by comparing those values to the maximum energy consumption rate and / or maximum energy credit limit, and / or any other variations (parts of, fractions and / or percentages) of maximum energy consumption rate and / or maximum energy credit limit that are specified for a given subscriber(s) (or UE or a group of UEs). For example, the network entities defined above, can be RAN nodes (or base stations eNBs, gNBs, NG-RANs) and / or Core network entities (e.g. AMF, SMF, MME, UPF, etc.). In certain examples, the UE may be served by one base station that performs (and / or is involved in) any of the above mentioned actions in relation to defining energy consumption and / or enforcement of the maximum energy consumption rate and / or maximum energy credit limit of the UE for all services (or some services or particular service). In certain examples, the base station may set (or decide) the mapping rules for the QoS Flows to bearers (e.g. DRBs) based on energy consumption levels. In certain examples, the base station may modify (or update) the mapping rules for the QoS Flows to bearers (e.g. DRBs) based on energy consumption levels. Examples relating to interactions between MN and SN based on energy In certain examples, the UE may be served by two base stations, namely, MN and SN, in a dual connectivity scenario. The MN and / or SN perform(s) (and / or are involved in) any of the above mentioned actions in relation to defining energy consumption and / or enforcement of the maximum energy consumption rate and / or maximum energy credit limit of the of the UE for all services (or some services or particular service). In certain examples, the MN and / or SN may define(s) (and / or any other actions mentioned above) combined (or aggregate or total) energy consumption values (or parameters or rates or energy cost) for all services (or some services or particular services) for the served UE (or subscriber) in a dual connectivity scenario. In certain examples, the MN and / or SN may define(s) (and / or any other actions mentioned above) separate (or individual or part of a total or aggregate) energy consumption values (or parameters or rates or energy cost) for all services (or some services or particular services) for the served UE (or subscriber) in a dual connectivity scenario. In certain examples, the MN and / or SN may define(s) (and / or any other action mentioned above) a combined (or aggregate or total) energy consumption values (or parameters or rates or energy cost) for all (or part of or a particular) traffic, PDUs sessions, MCG (Main Cell Group) bearers, SCG (Secondary Cell Group) bearers, and / or split bearers, and / or QoS flows, for the served UE (or subscriber) in a dual connectivity scenario. In certain examples, the MN and / or SN may define(s) (and / or any other actions mentioned above) separate (or individual or part of a total or aggregate) energy consumption values (or parameters or rates or energy cost) for all values (or parameters or rates or energy cost) for all (or part of or a particular) traffic, PDUs sessions, MCG bearers, SCG bearers, and / or split bearers, MN terminated and SN terminated bearers, and / or QoS flows, for the served UE (or subscriber) in a dual connectivity scenario. In certain examples, the MN and / or SN may define(s) (and / or any other action mentioned above) the maximum energy consumption rate and / or maximum energy credit limit of the UE for all services (or some services or particular service). In certain examples, the MN and / or SN may define(s) (and / or any other action mentioned above) the maximum energy consumption rate and / or maximum energy credit limit of, for example, all (or part of or a particular) traffic, PDUs sessions (or a PDU session, or a split PDU session), MCG bearers, SCG bearers, and / or split bearers, MN terminated andSN terminated bearers, and / or QoS flows, etc., for the served UE (or subscriber) in a dual connectivity scenario. In certain examples, the MN and SN may exchange information related to the energy consumption values (or parameters) and / or the maximum energy consumption rate and / or maximum energy credit limit for all (or some or part of) services, traffic, PDU sessions (or a PDU session, ora split PDU session), MCG bearers, SCG bearers, and / or split bearers, MN terminated and SN terminated bearers, and / or QoS flows, etc. In certain examples, the MN may decide the part (or fraction or percentage, or threshold, level, granularity, etc.) of the maximum energy consumption rate and / or maximum energy credit limit to be enforced by the MN and the part to be enforced by the SN. This information may be sent to the SN. In certain examples, upon receiving this information, the SN may perform one or more of the following actions: accept, reject, acknowledge, negotiate (or propose or recommend or request) different values, report to another network entity (and / or function), do nothing, ignore, report to the served UE (or groups of UEs), and / or any of the entities indicated in the previous examples. In certain examples, the MN may decide the part (or fraction or percentage, or threshold, level, granularity, etc.) of the maximum energy consumption rate and / or maximum energy credit limit to be enforced by the MN and that to be enforced by the MN. In certain examples, the part to be enforced by the SN may be decided by the SN. This information (about different parts values) may be exchanged between the MN and the SN. In certain examples, upon receiving this information, the MN and / or the SN may perform one or more of the following actions: accept, reject, acknowledge, negotiate (or propose or recommend or request) different values, do nothing, ignore, report to another network entity (and / or function), report to the served UE (or groups of UEs), and / or any of the entities indicated in the previous examples and embodiments. In certain examples, the energy consumption information on the values (e.g. total and / or parts) of energy consumption, maximum energy consumption rate and / or maximum energy credit limit, may be exchanged between the MN and SN, using, for example, existing lEs and Xn (or X2) signalling. In certain examples, the information may be provided using lEs, messages, and / or signalling Xn (or X2), for example newly defined, such as: new lEs for the MaximumEnergyConsumptionRate IE and / or MaximumEnergyCreditLimit IE, and / or any other suitable naming. In certain examples, the energy consumption information, for example as disclosed in the preceding bullet point, may be exchanged between the network and the UE, using any of the existing dedicated signalling, messages, and / or lEs, (and / or newly defined signalling, new messages and / or new lEs). In certain examples, the information may be exchanged via system information broadcast (e.g. periodically and / or on-demand) using existing SIBs (and / or newly defined SIBs). In certain examples, the MN may be configured to determine whether the UE will exceed (or expected to) exceed the maximum energy consumption rate and / or maximum energy credit limit if it participate in dual connectivity scenario (i.e. served by two nodes MN and SN). In certain examples, the MN may indicate to the UE that access to a secondary node (i.e. to be served by a SN in a dual connectivity scenario) is currently (e.g. at current time and / or location) not permitted, optionally due to energy consumption being at a certain level. In certain examples, the MN may indicate to the UE that access to a secondary node (SN) (i.e. to be served by a SN in a dual connectivity scenario) is currently (e.g. at current time and / or location) not permitted, optionally due to a predictable change in energy consumption, for example one or more of: • An increase in energy consumption above a given energy consumption level (or part or fraction or granularity or threshold or upper and / or lower bound, etc.). • An increase above the maximum energy consumption rate and / or maximum energy credit limit. • An increase above part of (or fraction or percentage or granularity or upped and / or lower bound) of the maximum energy consumption rate and / or maximum energy credit limit that is assigned to MN and / or SN. • Any other change in energy consumption that is not allowed (or permitted or recommended) or will not allow the UE access to a new SN (e.g. SN addition) or a modification to a different SN (e.g. SN modification). For example, all services, some service or a particular service for a given UE. In certain examples, the MN may indicate to the UE other assistance information in relation to the non-permitted access to a secondary node (i.e. to be served by a SN in a dual connectivity scenario), for example one or more of the following: • A cause value, recommendation on next available access time slots and / or location, e.g. cells. • A back-off timer so that the UE will not try to request access to a secondary node during the indicated timer (i.e. not before expiry of the timer). In certain examples, the MN and / or SN may trigger(s) the SN modification due to the energy consumption level (e.g. total or individual energy consumption at the MN and / or SN) reaching (or being at or measured or calculated at), or is expected to (or predicted to) exceed a given energy consumption level (or part or granularity or threshold or upper and / or lower bound, etc.). Other possible examples, related to change in energy consumption: • An increase above the maximum energy consumption rate and / or maximum energy credit limit. • An increase above part of (or fraction or percentage or granularity or upped and / or lower bound) of the maximum energy consumption rate and / or maximum energy credit limit that is assigned to MN and / or SN. • Any other change in energy consumption that is not allowed (or permitted or recommended) for the given UE (e.g. all services, some service ora particular service). In certain examples, the MN and / or SN may trigger(s) the SN release due to the energy consumption level (e.g. total or individual energy consumption at the MN and / or SN) reaching (or being or measured or calculated at) or is expected to (or predicted to) exceed a given energy consumption level (or part or granularity or threshold or upper and / or lower bound, etc.). Other possible examples, related to change in energy consumption: • An increase above the maximum energy consumption rate and / or maximum energy credit limit. • An increase above part of (or fraction or percentage or granularity or upped and / or lower bound) of the maximum energy consumption rate and / or maximum energy credit limit that is assigned to MN and / or SN. • Any other change in energy consumption that is not allowed (or permitted or recommended) for the given UE (e.g. all services, some service ora particular service). In certain examples, the network may configure a given UE behaviour for the case of controlled access to MN and / or SN in dual connectivity scenario based on energy consumption (and / or any other suitable information related to energy consumption, including any of the examples disclosed herein) in the network. In certain examples, the UE may provide to the network its capability to support network access (e.g. to MN and / or SN) based on energy consumption (and / or any other suitable information related to energy consumption, including any of the examples disclosed herein) in the network, the MN and / or the SN. Additionally, UE may indicate its capability to support dual connectivity under energy consideration. In certain examples, the network may provide assistance information to UE(s), on the new network behaviour to control UE access to the MN and / or SN based on energy consumption level(s) (and / or any other suitable information related to energy consumption, including any of the examples disclosed herein). In certain examples, the MN may configure the SN, or the SN may be configured via OAM to operate at a certain level of energy (or certain upper and / or lower bounds of energy, and / or maximum values, credits, quota, rate, etc.). When a fraction (or percentage or part of) or all of this quota is reached (or exceeded), the SN may report (or trigger a report or indicate) to the MN this energy event (e.g. energy exceeded a certain level). The MN may stop using this SN for a given UE. Additionally, the MN or the SN may initiates (or triggers) the secondary node release (SN release) procedure, for example one or more of the following: • The MN may initiate the SN release by triggering the SN Release procedure - MN initiated. In certain examples, the MN may use a newly defined procedure. Optionally, the MN may include a cause value for the SN release, e.g. Energyconsumption, or any other suitable cause naming. • The SN may initiate the SN release by triggering the SN Release procedure - SN initiated. In certain examples, the MN may use a newly defined procedure. Optionally, the SN may include a cause value for the SN release, e.g. Energyconsumption, or any other suitable cause naming. • In both cases, whether the SN release is initiated by MN or SN, the UE should be informed to switch to the MN. Optionally, the MN or SN may send a cause value for the SN release, e.g. Energyconsumption (or any other suitable cause naming) to the UE. In certain examples, the SN may report its energy consumption information (and / or other energy information mentioned in previous examples) to the MN. Additionally, upon receiving this information the MN may decide to initiate (or perform), e.g. SN addition, SN change and / or SN release. In certain examples, the SN may report its energy consumption information (and / or other energy information mentioned in previous examples) to the MN. Additionally, the SN may decide to initiate (or perform), e.g. SN addition, SN change, and / or SN release. In certain examples, the MN and / or SN may ensure that the combined (or aggregate or total, etc.) energy consumption of the MN and SN is kept to a certain total (or a certain ratio, or upper bound, a maximum, threshold, an energy criteria or energy policy, etc.). In certain examples, the MN and / or SN may calculate (or measure or estimate or predict, etc.) the combined (or aggregate or total, etc.) energy consumption in the MN and SN. In certain examples, the MN and / or SN may calculate (or measure estimate or predict, etc.) the individual energy consumption values in the MN and SN, respectively. The MN and SN may exchange their individual energy consumption values (and / or any other information related to energy consumption at the MN and SN). For example, the MN and / or SN measure(s) (estimate(s), and / or predict(s)) energy consumption in all MN terminated and / or SN terminated bearers, and / or energy consumption in MCG bearers, SCG bearers and split bearers. In certain examples, the energy consumption measurement (estimation, and / or prediction) can be at the granularity (or level) or a PDU session (or PDU sessions) or all traffic (or a some traffic or a particular traffic, a slice, etc.). In certain examples, all possible bearer type change options (or some of the options or a particular option) are (is) supported based on energy consumption (and / or any information related to energy consumption) in the MN and / or SN, for example, in MR-DC: • MCG bearer to / from split bearer; • MCG bearer to / from SCG bearer; • SCG bearer to / from split bearer. In certain examples, bearer termination point change may be supported for all bearer types (or a given bearer type) based on energy consumption (and / or any information related to energy consumption) in the MN and / or SN, and can be performed with or without bearer type change: • MN terminated bearer to / from SN terminated bearer. In certain examples, the network (e.g. CN) and / or NG-RAN (MN and / or SN) may decide to change a given bearer (or more than one bearer) type (and / or bearer termination point), for example based on one or more of the following: • an indication (or decision) by the network (e.g. CN); • the calculated (predicted and / or estimated) energy consumption values at the MN and / or SN, e.g. for all traffic / services (some of or a particular traffic / service); • the calculated (predicted and / or estimated) energy consumption values at the MN and / or SN per PDU session (or PDU session) or a split PDU session, or a particular PDU session; • the calculated (predicted and / or estimated) energy consumption values at the MN and / or SN per bearer (or bearers), or a given / particular bearer; In certain examples, the network (e.g. CN) and / or NG-RAN (MN and / or SN) may decide to change a given bearer (or more than one bearer) type (and / or bearer termination point), for example, the MN may decide to change a given MN terminated bearer type to a SN terminated bearer if the energy consumption at the MN has increased (or reached or expected to reach) the allowed (or maximum energy consumption value or credit, or part or fraction or percentage of maximum energy consumption value) at the MN. In certain examples, the network (e.g. CN) may send to the NG-RAN(s) (MN and / or SN) information related to the energy consumption information of the MN and / or SN, and / or energy consumption enforcement information (e.g. maximum energy consumption rate and / or maximum energy credit limit, and / or other energy related information, etc.). In certain examples, when the MN and / or SN want(s) to admit or modify a QoS flow, the MN and / or SN may verify the SN’s energy consumption and then determine whether to admit the flow and where to admit the flow i.e. in the MN or in the SN. In certain examples, the MN can only admit (or assign or allocated) certain QoS flows to SN based on energy configuration, even if the SN does not send any report (e.g. a report on the SN current and / or predicted energy consumption before and / or after admitting the QoS flows). Accordingly, certain QoS profile (and / or QoS flows) will use (or consume) X units of energy and the SN may be configured to only provide QoS flows with X unit of energy. The same can apply to the MN and so when a QoS flow arrives, then based on this configuration or policy (or criteria), the MN determines if the QoS flow has to be served by the MN or SN. In certain examples, the SN may decide to re-allocate (or re-assign) all (or some or a particular) QoS Flow(s) to the MN, (e.g. fora given PDU session (or PDU sessions), if the SN decides (or calculates or estimates or predicts) that the SN will be exceeding maximum energy consumption (or a pre-configured energy threshold, or a higher bound, or maximum energy consumption rate (or part of it), or maximum energy credit limit (or part of it), and / or other energy related information, etc.) that is allowed at the SN. This maximum energy consumption value at the SN, may be pre-configured by the MN, SN, and / or other network entity(-ies) and / or network functions, or via QAM, OTT server, or application server. Additionally, the SN may change this request upon any change in energy consumption at the MN and / or SN. This change may be reported (or indicated) to the MN. Optionally, for example, the change may be also reported to at least another network entity (and / or function). In certain examples, the SN may decide to request the MN to re-allocate (or re-assign) all (or some or a particular) QoS Flow(s) to the SN, (e.g. for a given PDU session (or PDU sessions), if the SN decides (or calculates or estimates or predicts) that the SN energy consumption will go below the minimum energy consumption (or a pre-configured energy threshold, a lower bound, or minimum energy consumption rate (or part of it), or minimum energy credit limit (or part of it), and / or other energy related information, etc.) that is allowed at the SN. This minimum energy consumption value at the SN, may be pre-configured by the MN, SN, and / or other network entity(-ies) and / or network functions, or via QAM, OTT server, or application server. Additionally, the SN may change this request upon any change in energy consumption at the MN and / or SN. This change is reported (or indicated) to the MN. Optionally, for example, the change may be also reported to at least another network entity (and / or function). In certain examples, the MN may decide to re-allocate (or re-assign) all (or some or a particular) QoS Flow(s) to the SN, (e.g. for a given PDU session (or PDU sessions), if the MN decides (or calculates or estimates or predicts) that the MN will be exceeding maximum energy consumption (or a pre-configured energy threshold, or a higher bound, or maximum energy consumption rate (or part of it), or maximum energy credit limit (or part of it), and / or other energy related information, etc.) that is allowed at the MN. This maximum energy consumption value at the MN, may be pre-configured by the MN, SN, and / or other network entity(-ies) and / or network functions, or via OAM, OTT server, or application server. Additionally, the MN may change this request upon any change in energy consumption at the MN and / or SN. This change may be reported (or indicated) to the SN. Optionally, for example, the change may be also reported to at least another network entity (and / or function). In certain examples, the MN may decide to request the SN to re-allocate (or re-assign) all (or some or a particular) QoS Flow(s) to the MN, or MN may retrieve those QoS Flows from the SN, (e.g. for a given PDU session (or PDU sessions), if the MN decides (or calculates or estimates or predicts) that the MN energy consumption will go below the minimum energy consumption (or a pre-configured energy threshold, a lower bound, or minimum energy consumption rate (or part of it), or minimum energy credit limit (or part of it), and / or other energy related information, etc.) that is allowed at the MN. This minimum energy consumption value at the MN, may be pre-configured by the MN, SN, and / or other network entity(-ies) and / or network functions, or via OAM, OTT server, or application server. Additionally, the MN may change this request upon any change in energy consumption at the MN and / or SN. This change may be reported (or indicated) to the SN. Optionally, for example, the change may be also reported to at least another network entity (and / or function). In certain examples, the MN may decide to request the SN to re-allocate (or re-assign) all (or some or a particular) QoS Flow(s) to the MN, or MN may retrieve those QoS Flow(s) from the SN, (e.g. for a given PDU session (or PDU sessions), if the MN decides (or calculates or estimates or predicts) that the SN energy consumption will go above (or exceed) the maximum energy consumption (or a pre-configured energy threshold, a upper bound, or maximum energy consumption rate (or part of it), or maximum energy credit limit (or part of it), and / or other energy related information, etc.) that is allowed at the SN. Additionally, the MN may change the request to SN to re-allocate QoS Flows (or change the allocated or assigned QoS Flows to the SN) following any change in the energy consumption at the MN and / or SN For example, the change in QoS Flows allocation (and / or energy consumption) may be also reported to at least another network entity (and / or function). In certain examples, the MN may decide to re-allocate (or re-assign) all (or some or a particular) QoS Flow(s) to the SN, (e.g. for a given PDU session (or PDU sessions), if the MN decides (or calculates or estimates or predicts) that the SN energy consumption will go below the minimum energy consumption (or a pre-configured energy threshold, a lower bound, or minimum energy consumption rate (or part of it), or minimum energy credit limit (or part of it), and / or other energy related information, etc.) that is allowed at the SN. Additionally, the MN may change the request to SN to re-allocate QoS Flows (or change the allocated or assigned QoS Flows to the SN) following any change in the energy consumption at the MN and / or SN. Optionally, for example, the change in QoS Flows allocation (and / or energy consumption) may be also reported to at least another network entity (and / or function). In certain examples, the UE may provide assistance information to the SN and / or MN to assist the MN and / or SN in energy enforcement that is related to all (or part of a particular service(s) of the UE in a dual connectivity scenario. The MN may decide to add an SN (SN addition) and / or modify an SN (SN modification) based on the energy consumption in the network, MN, and / or SN. For example, if the change of the MN energy consumption and / or total energy consumption (e.g. MN and / or SN) is predicted (or estimated or calculated or measured) to be (at a given time and / or location) for all services (or some services or a particular service), all PDU session (or some or a particular PDU session), bearers (MCG, SCG, split bear, MN terminated, SN terminated, etc.), and / or QoS Flows (some or a particular QoS Flow), to change to an allowed (permitted or acceptable) energy consumption level (and / or any other suitable energy consumption related information, including any of the examples disclosed herein (e.g. threshold, max, policy, etc.)). The skilled person will appreciate that, in the various examples described herein, it may be assumed that the MN and / or SN may exchange their energy consumption information (and / or any other energy information mentioned in previous examples) using any suitable new and / or existing multi-connectivity procedure(s) (e.g. EN-DC, MR-DC, etc.), for example Secondary Node Addition procedure (MN initiated), Conditional Secondary Node Addition procedure, Secondary Node Modification procedure (MN / SN initiated), SN Modification procedure - SN initiated with MN involvement, SN modification - SN initiated without MN involvement, SN initiated Conditional SN Modification without MN involvement, SN Release procedure - MN initiated I SN initiated, SN Change - MN initiated / SN initiated, Conditional SN Change - MN initiated, Conditional SN Change - SN initiated, etc. Additionally, any suitable new and / or existing procedure(s) may be used to carry the interactions between the MN and SN in relation to energy (or energy information). The skilled person will appreciate that the term “access control” herein is not to be restricted to control of access at the RAN level (e.g. MN and / or SN) only, but it can also mean control of general access or usage of the network and hence may include mechanisms similar to congestion control at any layer (e.g. RRC, NAS, etc.) or any back-off mechanism. Various examples disclosed herein refer to traffic in general. The skilled person will appreciate that various examples disclosed herein are applicable to various types of flows, for example GBR QoS flows, non-GBR QoS flows and / or Delay-critical GBR flows. The skilled person will appreciate that, in various examples, interactions (and actions) between / (by) the network, MN and / or SN may be based on change(s) in energy consumption (and / or any information disclosed herein) in the network, MN and / or SN. For example, changes in the total energy consumption (network, MN, and / or SN) and / or individual energy consumption (MN or SN) above (or below) a given energy consumption level (threshold, upper or lower bound, and / or any information disclosed herein). For example, one or more of the following actions (or interactions) between the network, MN, and / or SN: • An action (and / or interaction) of SN addition, SN modification, and / or SN release by the MN and / or SN (and / or the network), based on change in information of energy consumption (e.g. energy information disclosed herein). • An action (and / or interaction) of QoS re-mapping (or re-allocation) to bearers, based on change in information of energy consumption (e.g. energy information disclosed herein). • An action (and / or interaction) of PDU session split (and / or QoS Flow allocation) to MN and / or SN, based on change in information of energy consumption (e.g. energy information disclosed herein). • An action (and / or interaction) of bearer type change and / or bearer termination change, based on change in information of energy consumption (e.g. energy information disclosed herein). Examples of changes to 3GPP specifications TS 37.340: Inter-node Energy Coordination • For MR-DC operations, MN and SN may coordinate their energy consumption in a semi-static manner via UE associated signalling. Activation and Deactivation of SCG based on Energy • An activation and deactivation mechanism of SCG based on energy consumption is supported. • The MN can configure the SCG as activated or deactivated upon (or based on or following) changes in energy consumption of the MN and / or SN. • The SCG activation can be requested by the MN, by the SN and by the UE (e.g. based on changes in energy consumption levels, thresholds, parameters, etc.). Bearer handling aspects QoS aspects - QoS flows belonging to the same PDU session may be mapped to different bearer types considering the energy consumption levels, e.g. at the MN and / or SN. For example, • the MN decides the QoS flows that are assigned to the SN longer, the SN informs the MN and the MN cannot reject the request. • the SN may accept or reject the assigned QoS Flows (from the MN) based on energy consumption information at the SN. For example, whether the decision to assign the QoS Flows to the SN would increase energy consumption at the SN above than the maximum energy consumption allowed at the SN. • The SN would responds (or acknowledge) MN deciding (or request) to move QoS Flows (or assign Flows) to the SN. In the case of rejection of failure to accommodate the assigned QoS Flows, e.g. the SN may reject the MN decision (or request) and indicates a new cause value for the rejection, e.g. NotAllowedEnergylIncrease (and / or any other suitable naming). The MN or SN node decides how to map the QoS flow to DRBs based on expected (predicted or estimated or calculated) energy consumption at the MN or SN upon (or following) accommodating this QoS Flow at the MN or SN. For example, o The MN or SN may map a QoS Flow to a DRB based on energy consumption at the QoS Flow level. For example, prioritizing DRB energy over DRB QoS flow level QoS parameters. Figure 1 illustrates an exemplary method for controlling energy consumption in a network. Referring to Figure 1, in a first operation 101, one or more network entities and / or functionalities determine one or more energy consumption values associated with one or more services for one or more UEs. In a second operation 102, the one or more network entities and / or functionalities determine whether or not the one or more energy consumption values are acceptable based on a comparison between the one or more energy consumption values and one or more maximum energy consumption values for the one or more services for the one or more UEs. Figure 2 is a block diagram of an exemplary network entity (e.g. UE, base station and / or any other network entity) that may be used in examples of the present disclosure. The skilled person will appreciate that a network entity may be implemented, for example, as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, and / or as a virtualised function instantiated on an appropriate platform, e.g. on a cloud infrastructure. The entity 200 comprises a processor (or controller) 201, a transmitter 203 and a receiver 205. The receiver 205 is configured for receiving one or more messages from one or more other network entities, for example as described above. The transmitter 203 is configured for transmitting one or more messages to one or more other network entities, for example as described above. The processor 201 is configured for performing one or more operations, for example according to the operations as described above. The techniques described herein may be implemented using any suitably configured apparatus and / or system. Such an apparatus and / or system may be configured to perform a method according to any aspect, embodiment, example or claim disclosed herein. Such an apparatus may comprise one or more elements, for example one or more of receivers, transmitters, transceivers, processors, controllers, modules, units, and the like, each element configured to perform one or more corresponding processes, operations and / or method steps for implementing the techniques described herein. For example, an operation / function of X may be performed by a module configured to perform X (or an X-module). The one or more elements may be implemented in the form of hardware, software, or any combination of hardware and software. It will be appreciated that examples of the present disclosure may be implemented in the form of hardware, software or any combination of hardware and software. Any such software may be stored in the form of volatile or non-volatile storage, for example a storage device like a ROM, whether erasable or rewritable or not, or in the form of memory such as, for example, RAM, memory chips, device or integrated circuits or on an optically or magnetically readable medium such as, for example, a CD, DVD, magnetic disk or magnetic tape or the like. It will be appreciated that the storage devices and storage media are embodiments of machine-readable storage that are suitable for storing a program or programs comprising 5 instructions that, when executed, implement certain examples of the present disclosure. Accordingly, certain examples provide a program comprising code for implementing a method, apparatus or system according to any example, embodiment, aspect and / or claim disclosed herein, and / or a machine-readable storage storing such a program. Still further, such programs may be conveyed electronically via any medium, for example a communication 10 signal carried over a wired or wireless connection. While the invention has been shown and described with reference to certain examples, it will be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the scope of the invention, as defined by the appended claims. Definitions / Acronyms In the present disclosure, the following definitions / acronyms may be used (e.g. see 3GPP TS 37.340). En-gNB: node providing NR user plane and control plane protocol terminations towards the UE, and acting as Secondary Node in EN-DC. Master Cell Group: in MR-DC, a group of serving cells associated with the Master Node, comprising of the SpCell (PCell) and optionally one or more SCells. Master node: in MR-DC, the radio access node that provides the control plane connection to the core network. It may be a Master eNB (in EN-DC), a Master ng-eNB (in NGEN-DC) or a Master gNB (in NR-DC and NE-DC). MCG bearer: in MR-DC, a radio bearer with an RLC bearer (or two RLC bearers, in case of CA packet duplication in an E-UTRAN cell group, or up to four RLC bearers in case of CA packet duplication in a NR cell group) only in the MCG. MN terminated bearer: in MR-DC, a radio bearer for which PDCP is located in the MN. MCG SRB: in MR-DC, a direct SRB between the MN and the UE. Multi-Radio Dual Connectivity: Dual Connectivity between E-UTRA and NR nodes, or between two NR nodes. Ng-eNB: as defined in 3GPP TS 38.300. PCell: SpCell of a master cell group. PSCell: SpCell of a secondary cell group. RLC bearer: RLC and MAC logical channel configuration of a radio bearer in one cell group. Secondary Cell Group: in MR-DC, a group of serving cells associated with the Secondary Node, comprising of the SpCell (PSCell) and optionally one or more SCells. Secondary node: in MR-DC, the radio access node, with no control plane connection to the core network, providing additional resources to the UE. It may be an en-gNB (in EN-DC), a Secondary ng-eNB (in NE-DC) or a Secondary gNB (in NR-DC and NGEN-DC). SCG bearer: in MR-DC, a radio bearer with an RLC bearer (or two RLC bearers, in case of CA packet duplication in an E-UTRAN cell group, or up to four RLC bearers in case of CA packet duplication in a NR cell group) only in the SCG. SN terminated bearer: in MR-DC, a radio bearer for which PDCP is located in the SN. SpCell: primary cell of a master or secondary cell group. SRB3: in EN-DC, NGEN-DC and NR-DC, a direct SRB between the SN and the UE. Split bearer: in MR-DC, a radio bearer with RLC bearers both in MCG and SCG. Split PDU Session (or PDU Session split): a PDU Session whose QoS Flows are served by more than one SDAP entities in the NG-RAN. Split SRB: in MR-DC, a SRB between the MN and the UE with RLC bearers both in MCG and SCG. User plane resource configuration: in MR-DC with 5GC, encompasses radio network resources and radio access resources related to either one or more PDU sessions, one or more QoS flows, one or more DRBs, or any combination thereof. 3GPP 3rd Generation Partnership Project 5G 5th Generation eNB Base Station EN-DC E-UTRA-NR Dual Connectivity E-UTRA Evolved Universal Terrestrial Radio Access gNB ID 5G Base Station Identity / ldentifi cation IE Information Element MCG Master Cell Group MN Master Node MR-DC Multi-Radio Dual Connectivity NE-DC NR-E-UTRA Dual Connectivity NG Next Generation NGEN-DC NG-RAN E-UTRA-NR Dual Connectivity NG-RAN Next Generation Radio Access Network NR New Radio NR-DC NR-NR Dual Connectivity RAN Radio Access Network SCG Secondary Cell Group SN Secondary Node TS Technical Specification UE User Equipment

Claims

1. A method for controlling energy consumption in a network, the method comprising: determining, by one or more network entities and / or functionalities, one or more energy consumption values associated with one or more services for one or more UEs; anddetermining, by the one or more network entities and / or functionalities, whether or not the one or more energy consumption values are acceptable based on a comparison between the one or more energy consumption values and one or more maximum energy consumption values for the one or more services for the one or more UEs.

2. A method according to claim 1, wherein the maximum energy consumption values are associated with one or more maximum energy consumption rates and / or one or more maximum energy credit limits for the one or more services for the one or more UEs.

3. A method according to claim 1 or 2, further comprising setting and / or modifying one or more network parameters and / or configurations associated with the one or more services for the one or more UEs based on a result of the comparison.

4. A method according to claim 3, wherein the setting and / or modifying comprises setting and / or modifying, by a base station serving one or more of the UEs, mapping rules for QoS Flows to bearers based on the energy consumption values.

5. A method according to any preceding claim, further comprising updating, by the one or more network entities and / or functionalities, the maximum energy consumption values.

6. A method according to any preceding claim, wherein the one or more network entities and / or functionalities comprise one or more RAN nodes (e.g. base station, eNB, gNB, NG-RAN) and / or one or more core network entities (e.g. AMF, SMF, MME, UPF).

7. A method according to any preceding claim, wherein the one or more network entities and / or functions comprise a first base station and a second base station capable of serving a UE in a dual connectivity scenario.

8. A method according to claim 7, wherein the energy consumption values and / or maximum energy consumption values comprise one or more combined values associated with the first and second base stations together, and / or one or more separate values associated with the first and second base stations individually.

9. A method according to claim 7 or 8, further comprising determining, by the first and / or second base station, whether one or more maximum energy consumption values would be exceeded for one or more services for a certain UE if the UE participated in dual connectivity.

10. A method according to claim 7, 8 or 9, further comprising configuring a UE behaviour for a UE participating in dual connectivity based on energy consumption.

11. A method according to any preceding claim, further comprising receiving, by one or more network entities, from a UE, an indication of capability to support network access based on energy consumption.

12. A method according to any preceding claim, further comprising transmitting, by one or more network entities, to a UE, assistance information for controlling access to the network based on energy consumption.

13. A method according to any preceding claim, wherein one or more of the energy consumption values and / or maximum energy consumption values are associated with one or more of:one or more of traffic flows;one or more PDU sessions;one or more QoS flows;one or more Main Cell Group (MCG) bearers;one or more Secondary Cell Group (SCG) bearers;one or more Master Node (MN) terminated bearers;one or more Secondary Node (SN) terminated bearers;one or more split bearers; and one or more network slices.

14. A method according to any preceding claim, further comprising transmitting, from a first one of the network entities (e.g. a MN or a core network entity) to a second one of the network entities (e.g. a SN or a NG-RAN node), information relating to the energy consumption values and / or the maximum energy consumption values.

15. A method according to claim 14, wherein the information is transmitted from the first network entity to the second network entity in a certain IE.

16. A method according to any preceding claim, further comprising reconfiguring one or more traffic flows based on a comparison between the one or more energy consumption values and one or more minimum energy consumption values.

17. A method according to any preceding claim, wherein one or more of the UEs comprise a subscriber, and wherein each subscriber is associated with subscription information comprising energy related information.

18. A network entity (e.g. AMF, SMF) and / or a base station (e.g. eNB, gNB) configured to perform a method according to any preceding claim.

19. A network (or wireless communication system) comprising a UE and one or more network entities according to claim 18.

20. A computer program comprising instructions which, when the program is executed by a computer or processor, cause the computer or processor to carry out a method according to any of claims 1 to 17.

21. A computer or processor-readable data carrier having stored thereon a computer program according to claim 20.

Images