Admission of QoS flows based on energy

Abstract

A network entity receives a request to admit a QoS flow. The network entity determines energy requirements for the QoS flow based on a criterion 501. The network entity admits or rejects the QoS flow

Description

BACKGROUND Field Certain examples of the present disclosure provide one or more techniques for admission of Quality of Service (QoS) flows based on energy, for example 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 TR 22.882 VO.2.0 (2022-11), 3rd Generation Partnership Project; Technical Specification Group TSG SA; Study on Energy Efficiency as service criteria (Release 19). [2] 3GPP TS 23.501 V18.0.0. [3] 3GPP TS 24.501 V18.1.0. [4] 3GPP TS 38.413 V17.5.0. Various acronyms, abbreviations and definitions used in the present disclosure are defined at the end of this description. Ongoing 3GPP study in SA1 on ‘Energy Efficiency as Service Criteria’ The 3GPP SA1 groups is currently studying how to introduce energy efficiency as a service and this is documented in 3GPP TR 22.882 V0.2.0 [1], The overview of the study as defined in [1] is provided below: “Climate change and globally energy shortage are issues that requires international cooperation and coordinated solutions at all levels, many regions and countries have published related policies and requirements to control carbon release and promote energy efficiency. These policies have made energy efficiency a strategic priority for many telecoms operators around the world. Energy efficiency has been considered in many standard groups and specifications. The existing studies concentrate more on how to satisfy user experience and try to achieve energy efficiency at the same time and achieve energy efficiency within the network, so the requirements, use cases and solutions are basically within the network itself. Verticals and customers have no approach for energy efficiency related information from network. Introducing energy efficiency as a service will allow users to have the choice to select proper energy efficiency criteria as well as other network performance parameters when they need it, which may include: 1. Define and support energy efficiency criteria as part of communication service to user and application services. 2. Provide information exposure on systematic energy consumption or level of energy efficiency to vertical customers. Such as in satellite and terrestrial convenience scenario, for some regions where both satellite and terrestrial coverage exist, energy saving could be taken as a dimension while providing the communication service, users or operators could have the choice to find out a best way in satisfying both user experience and energy efficiency. From another perspective, the network could also react to different energy consumption modes of application or adjust network resource. Both the two aspects above need more interaction between application and network on energy consumption status. It is worth considering how to deliver services with energy efficiency as service criteria, associated with verticals’ preferences, and how to support the policy of handling energy as part of a subscription.” The study also contains use cases for which potential requirement may be defined. One of the use cases focuses on using energy as a performance criteria (for best effort communication). The use case is provided in section 5.1 of [1] and is as follows: “A large scale logistics company L has deployed a large number of communicating components. These are integrated into vehicles, palettes, facilities, etc.. Essentially, loT terminals enable remote tracking and monitoring functions. The information gathered is relevant, but not constrained with respect to latency. In fact, eventual delivery (e.g. after hours or even a full day) of communication is entirely acceptable for L. The MNO M offers a 'green service' which limits the rate of energy utilized for communication over a particular time interval (e.g. per day) and this service is appropriate for L, whose overall corporate goals are also served by 'green service,' as they strive to operate with energy efficiency. ” Admitting QoS flows in the Next Generation (NG) - Radio Access Network (RAN) As part of the overall QoS framework, the 5G System (5GS) can provide so called Guaranteed Bit Rate (GBR) QoS flows which means that the characteristics of the QoS flow can be guaranteed in the NG-RAN (at least) and the network. The profile of a QoS is provided below from [2]: A QoS Flow may either be 'GBR' or 'Non-GBR' depending on its QoS profile. The QoS profile of a QoS Flow is sent to the (R)AN and it contains QoS parameters as described below (details of QoS parameters are described in clause 5.7.2): - For each QoS Flow, the QoS profile shall include the QoS parameters: - 5G QoS Identifier (5QI); and - Allocation and Retention Priority (ARP). - For each QoS Flow, the QoS profile may also include the QoS parameters: - PDU Set QoS Parameters (described in clause 5.7.7). - For each Non-GBR QoS Flow only, the QoS profile may also include the QoS parameter: - Reflective QoS Attribute (RQA). - For each GBR QoS Flow only, the QoS profile shall also include the QoS parameters: - Guaranteed Flow Bit Rate (GFBR) - UL and DL; and - Maximum Flow Bit Rate (MFBR) - UL and DL; and - In the case of a GBR QoS Flow only, the QoS profile may also include one or more of the QoS parameters: - Notification control; - Maximum Packet Loss Rate - UL and DL. The characteristics of QoS are determined by a set of parameters as shown in the table below from [2], The table shows the characteristics for GBR flows vs non-GBR flows, each of which is associated with a standardized 5QI. 5QI Value Resource Type Default Priority Level Packet Delay Budget (NOTE 3) Packet Error Rate Default Maximum Data Burst Volume (NOTE 2) Default Averaging Window Example Services 1 GBR (NOTE 1) 20 100 ms (NOTE 11, NOTE 13) 10’2 N / A 2000 ms Conversational Voice 2 40 150 ms (NOTE 11, NOTE 13) 103 N / A 2000 ms Conversational Video (Live Streaming) 3 30 50 ms (NOTE 11, NOTE 13) 10-3 N / A 2000 ms Real Time Gaming, V2X messages (see TS 23.287

[121] ). Electricity distribution -medium voltage, Process automation monitoring 4 50 300 ms (NOTE 11, NOTE 13) 10-6 N / A 2000 ms Non-Conversational Video (Buffered Streaming) 65 (NOTE 9, NOTE 12) 7 75 ms (NOTE 7, NOTE 8) 10-2 N / A 2000 ms Mission Critical user plane Push To Talk voice (e.g. MCPTT) 66 (NOTE 12) 20 100 ms (NOTE 10, NOTE 13) 10’2 N / A 2000 ms Non-Mission-Critical user plane Push To Talk voice 67 (NOTE 12) 15 100 ms (NOTE 10, NOTE 13) 10-3 N / A 2000 ms Mission Critical Video user plane 75 (NOTE 14) 25 50 ms (NOTE 13) 10-2 N / A 2000 ms V2X messages (see TS 23.287

[121] ). A2X messages (see TS 23.256

[136] ) 71 56 150 ms (NOTE 11, NOTE 13, NOTE 15) 10-6 N / A 2000 ms "Live" Uplink Streaming (e.g. TS 26.238

[76] ) 72 56 300 ms (NOTE 11, NOTE 13, NOTE 15) 10-4 N / A 2000 ms "Live" Uplink Streaming (e.g. TS 26.238

[76] ) 73 56 300 ms (NOTE 11, NOTE 13, NOTE 15) 10-8 N / A 2000 ms "Live" Uplink Streaming (e.g. TS 26.238

[76] ) 74 56 500 ms (NOTE 11, NOTE 15) 10-8 N / A 2000 ms "Live" Uplink Streaming (e.g. TS 26.238

[76] ) 76 56 500 ms (NOTE 11, NOTE 13, NOTE 15) 10-4 N / A 2000 ms "Live" Uplink Streaming (e.g. TS 26.238

[76] ) 5 Non-GBR (NOTE 1) 10 100 ms NOTE 10, NOTE 13) 10-6 N / A N / A IMS Signalling 6 60 300 ms (NOTE 10, NOTE 13) 10-6 N / A N / A Video (Buffered Streaming) TCP-based (e.g. www, e-mail, chat, ftp, p2p file sharing, progressive video, etc.), AI / ML model download for image recognition (e.g. for model topology) (see TS 22.261 [2]) 7 70 100 ms (NOTE 10, NOTE 13) 10‘3 N / A N / A Voice, Video (Live Streaming) Interactive Gaming, AI / ML model download for image recognition (e.g. for model weight factors) (see TS 22.261 [2]) 8 80 300 ms (NOTE 13) io-6 N / A N / A Video (Buffered Streaming) TCP-based (e.g. www, e-mail, chat, ftp, p2p file sharing, progressive video, etc.) 9 90 10 90 1100ms (NOTE 13) (NOTE 17) 10’6 N / A N / A Video (Buffered Streaming) TCP-based (e.g. www, e-mail, chat, ftp, p2p file sharing, progressive video, etc.) and any service that can be used over satellite access type with these characteristics 69 (NOTE 9, NOTE 12) 5 60 ms (NOTE 7, NOTE 8) 10’6 N / A N / A Mission Critical delay sensitive signalling (e.g. MC-PTT signalling) 70 (NOTE 12) 55 200 ms (NOTE 7, NOTE 10) 10-6 N / A N / A Mission Critical Data (e.g. example services are the same as 5QI 6 / 8 / 9) 79 65 50 ms (NOTE 10, NOTE 13) io-2 N / A N / A V2X messages (see TS 23.287

[121] ) 80 68 10 ms (NOTE 5, NOTE 10) io-6 N / A N / A Low Latency eMBB applications Augmented Reality 82 Delay-critical GBR 19 10 ms (NOTE 4) 10’4 255 bytes 2000 ms Discrete Automation (see TS 22.261 [2]) 83 22 10 ms (NOTE 4) 10’4 1354 bytes (NOTE 3) 2000 ms Discrete Automation (see TS 22.261 [2]); V2X messages (UE - RSU Platooning, Advanced Driving: Cooperative Lane Change with low LoA. See TS 22.186

[111] , TS 23.287

[121] ) 84 24 30 ms (NOTE 6) 10’5 1354 bytes (NOTE 3) 2000 ms Intelligent transport systems (see TS 22.261 [2]) 85 21 5 ms (NOTE 5) io-5 255 bytes 2000 ms Electricity Distribution- high voltage (see TS 22.261 [2]). V2X messages (Remote Driving. See TS 22.186

[111] , NOTE 16, see TS 23.287

[121] ). Split AI / ML inference - DL Split AI / ML image recognition, (see TS 22.261 [2]) 86 18 5 ms (NOTE 5) 10’4 1354 bytes 2000 ms V2X messages (Advanced Driving: Collision Avoidance, Platooning with high LoA. See TS 22.186

[111] , TS 23.287

[121] ) 87 25 5 ms (NOTE 4) 10’3 500 bytes 2000 ms Interactive Service - Motion tracking data, (see TS 22.261 [2]) 88 25 10 ms (NOTE 4) 10’3 1125 bytes 2000 ms Interactive Service - Motion tracking data, (see TS 22.261 [2]), split AI / ML inference - LJL Split AI / ML image recognition, (see TS 22.261 [2]) 89 25 15 ms (NOTE 4) 104 17000 bytes 2000 ms Visual content for cloud / edge / split rendering (see TS 22.261 [2]) 90 25 20 ms (NOTE 4) 10‘4 63000 bytes 2000 ms Visual content for cloud / edge / split rendering (see TS 22.261 [2]) NOTE 1: A packet which is delayed more than PDB is not counted as lost, thus not included in the PER. NOTE 2: It is required that default MDBV is supported by a PLMN supporting the related 5Qls. NOTE 3: The Maximum Transfer Unit (MTU) size considerations in clause 9.3 and Annex C of TS 23.060

[56] are also applicable. IP fragmentation may have impacts to CN PDB, and details are provided in clause 5.6.10. NOTE 4: A static value for the CN PDB of 1 ms for the delay between a UPF terminating N6 and a 5G-AN should be subtracted from a given PDB to derive the packet delay budget that applies to the radio interface. When a dynamic CN PDB is used, see clause 5.7.3.4. NOTE 5: A static value for the CN PDB of 2 ms for the delay between a UPF terminating N6 and a 5G-AN should be subtracted from a given PDB to derive the packet delay budget that applies to the radio interface. When a dynamic CN PDB is used, see clause 5.7.3.4. NOTE 6: A static value for the CN PDB of 5 ms for the delay between a UPF terminating N6 and a 5G-AN should be subtracted from a given PDB to derive the packet delay budget that applies to the radio interface. When a dynamic CN PDB is used, see clause 5.7.3.4. NOTE 7: For Mission Critical services, it may be assumed that the UPF terminating N6 is located "close" to the 5G_AN (roughly 10 ms) and is not normally used in a long distance, home routed roaming situation. Hence a static value for the CN PDB of 10 ms for the delay between a UPF terminating N6 and a 5G_AN should be subtracted from this PDB to derive the packet delay budget that applies to the radio interface. NOTE 8: In both RRC_IDLE and RRC_CONNECTED mode, the PDB requirement for these 5Qls can be relaxed (but not to a value greater than 320 ms) for the first packet(s) in a downlink data or signalling burst in order to permit reasonable battery saving (DRX) techniques. NOTE 9: It is expected that 5QI-65 and 5QI-69 are used together to provide Mission Critical Push to Talk service (e.g. 5QI-5 is not used for signalling). It is expected that the amount of traffic per UE will be similar or less compared to the IMS signalling. NOTE 10: In both RRC_IDLE and RRC_CONNECTED mode, the PDB requirement for these 5Qls can be relaxed for the first packet(s) in a downlink data or signalling burst in order to permit battery saving (DRX) techniques. NOTE 11: In RRC_IDLE mode, the PDB requirement for these 5Qls can be relaxed for the first packet(s) in a downlink data or signalling burst in order to permit battery saving (DRX) techniques. NOTE 12: This 5QI value can only be assigned upon request from the network side. The UE and any application running on the UE is not allowed to request this 5QI value. NOTE 13: A static value for the CN PDB of 20 ms for the delay between a UPF terminating N6 and a 5G-AN should be subtracted from a given PDB to derive the packet delay budget that applies to the radio interface. NOTE 14: This 5QI is only used for transmission of V2X messages as defined in TS 23.287

[121] and transmission of A2X messages as defined in TS 23.256

[136] , NOTE 15: For "live" uplink streaming (see TS 26.238

[76] ), guidelines for PDB values of the different 5Qls correspond to the latency configurations defined in TR 26.939

[77] , In order to support higher latency reliable streaming services (above 500ms PDB), if different PDB and PER combinations are needed these configurations will have to use non-standardised 5Qls. NOTE 16: These services are expected to need much larger MDBV values to be signalled to the RAN. Support for such larger MDBV values with low latency and high reliability is likely to require a suitable RAN configuration, for which, the simulation scenarios in TR 38.824

[112] may contain some guidance. NOTE 17: The worst case one way propagation delay for GEO satellite is expected to be ~270ms, ,~ 21 ms for LEO at 1200km, and 13 ms for LEO at 600km. The UL scheduling delay that needs to be added is also typically two way propagation delay e.g. ~540ms for GEO, ~42msfor LEO at 1200km, and ~26 ms for LEO at 600km. Based on that, the 5G-AN Packet delay budget is not applicable for 5Qls that require 5G-AN PDB lower than the sum of these values when the specific types of satellite access are used (see TS 38.300

[27] ). 5QI-10 can accommodate the worst case PDB for GEO satellite type. When the network attempts to establish a new QoS flow, either based on a request for a new Protocol Data Unit (PDU) session establishment or based on a modification of an existing PDU session, then the NG-RAN verifies if a new QoS flow can be admitted. This is especially crucial when the QoS requested is for a GBR QoS flow since admission of a guaranteed bit rate necessitates that the NG-RAN continuously provides the required treatment as long as there is associated data. One parameter which is associated with a QoS flow is referred to as Allocation and Retention Priority (ARP) which is described below from [2]: The QoS parameter ARP contains information about the priority level, the pre-emption capability and the pre-emption vulnerability. This allows deciding whether a QoS Flow establishment / modification / handover may be accepted or needs to be rejected in the case of resource limitations (typically used for admission control of GBR traffic). It may also be used to decide which existing QoS Flow to pre-empt during resource limitations, i.e. which QoS Flow to release to free up resources. The ARP priority level defines the relative importance of a QoS Flow. The range of the ARP priority level is 1 to 15 with 1 as the highest priority. The ARP priority levels 1-8 should only be assigned to QoS Flows for services that are authorized to receive prioritized treatment within an operator domain (i.e. that are authorized by the serving network). The ARP priority levels 9-15 may be assigned to QoS Flows for services that are authorized by the home network and thus applicable when a UE is roaming. NOTE: This ensures that future releases may use ARP priority level 1-8 to indicate e.g. emergency and other priority services within an operator domain in a backward compatible manner. This does not prevent the use of ARP priority level 1-8 in roaming situation in the case that appropriate roaming agreements exist that ensure a compatible use of these priority levels. The ARP pre-emption capability defines whether a QoS Flow may get resources that were already assigned to another QoS Flow with a lower priority. The ARP pre-emption vulnerability defines whether a QoS Flow may lose the resources assigned to it in order to admit a QoS Flow with higher priority. The ARP pre-emption capability and the ARP pre-emption vulnerability shall be either set to 'enabled' or 'disabled'. The ARP pre-emption vulnerability of the QoS Flow which the default QoS rule is associated with should be set appropriately to minimize the risk of a release of this QoS Flow. The details ofhowthe S MF sets the ARP for a QoS Flow are further described in clause 5.7.2.7 From the above, it can be seen that admission of a new GBR QoS flow requires the NG-RAN to verify if resources can be reserved and guaranteed for the flow and the NG-RAN considers the ARP of existing QoS flows to determine which QoS flow may be pre-empted when resources are scarce. 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. 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 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 example of a new Class 2 procedure for “Energy Criteria for Admission control Start”; Figure 2 illustrates an example of a new Class 2 procedure for “Energy Criteria for Admission control Failure Indication”; Figure 3 illustrates an example of a new Class 2 procedure for “Energy Criteria for Admission control stop (or deactivate)”; Figure 4 illustrates an example of a new Class 2 procedure for “Energy Criteria for Admission Control Notify”; Figure 5 illustrates an exemplary method for admission of a QoS flow based on energy; and Figure 6 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 admission of QoS flows based on energy, for example 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 an 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; and / or the functionality of an AMF entity in the examples below may be applied to any other suitable type of entity performing access and mobility management 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. According to various examples of the present disclosure, any suitable network entity may take into account the energy requirements of any QoS flow before admitting the QoS flow that is requested. Certain examples of the present disclosure provide a method for admission of a Quality of Service (QoS) flow based on energy, the method comprising: in response to receiving a request to admit a QoS flow, determining, by a first network entity, whether one or more criteria, based on one or more energy requirements dependent on the QoS flow, are satisfied; and admitting or rejecting, by the first network entity, the QoS flow based on the determination. In certain examples, the one or more criteria may be based on one or more of: a required energy level and / or rate for the QoS flow; a maximum allowed energy level and / or rate; an available energy level and / or rate; one or more energy constraints of the first network entity (e.g. a maximum energy quota); a priority associated with the QoS flow; a number of QoS flows already admitted; and one or more thresholds. In certain examples, the one or more energy requirements may be determined based on one or more of: a set of QoS parameters associated with the QoS flow; and one or more characteristics of the QoS flow. In certain examples, the one or more characteristics may comprise one or more of: a 5QI value; a resource type (e.g. GBR or non-GBR); a default priority level; a packet delay budget; a packet error rate; and a default averaging window. In certain examples, the one or more criteria may comprise one or more criteria based on a comparison of an energy requirement to an energy threshold. In certain examples, the energy requirement may comprise one or more of: an energy requirement associated with the QoS flow; and a total energy requirement comprising a current energy requirement and an energy requirement associated with the QoS flow. In certain examples, the one or more criteria may comprise one or more criteria based on a comparison of a priority of the QoS flow to a priority threshold. In certain examples, the method may further comprise, if the QoS flow is rejected, transmitting, to another network entity, an indication of the rejection including a cause of the rejection. In certain examples, the method may further comprise receiving, by the first network entity, configuration for applying or disapplying admission of a QoS flow based on energy. In certain examples, the method may further comprise receiving by the first network entity, from a second network entity (e.g. AMF), information (e.g. assistance information) for allowing the network entity to perform the determination. In certain examples, the configuration and / or information may comprise one or more of: information relating to energy consumption policy; one or more thresholds; and information based on UE subscription information. In certain examples, the configuration and / or information may relate and / or be applied (e.g. only) to one or more of: all UEs; one or more UEs on a certain network slice; one or more UEs in a certain location; one or more UEs at certain time; one or more UEs of a certain type; one or more UEs of a certain capability; one or more UEs with certain UE subscription information (e.g. information relating to energy requirements and / or energy information); and one or more cells associated with the first network entity. In certain examples, the method may further comprise storing (e.g. by the first network entity, a second network entity (e.g. AMF) and / or a UE) the configuration and / or information (e.g. in a UE context associated with the UE). In certain examples, the configuration and / or information may be received in response to a UE registration procedure. In certain examples, the method may further comprise receiving, from a UE, information indicating a capability of the UE to support admission of a QoS flow based on energy. In certain examples, the method may further comprise accepting or rejecting a UE based on the capability of the UE to support admission of a QoS flow based on energy. In certain examples, the method may further comprise performing, by the first network entity, an action relating to one or more existing QoS flows based on a change of and / or update to one or more energy requirements dependent on the QoS flows. In certain examples, the action may comprise one or more of: releasing a QoS flow; pausing a QoS flow; activate a QoS flow; deactivate a QoS flow; modify a QoS flow; replace a QoS flow; modify a mapping of a QoS flow to a DRB; and modify the ARP allocated to a QoS flow. In certain examples, the first network entity may comprise one or more of: an NG-RAN; a gNB; an SMF entity; and a UPF entity. In certain examples, the QoS flow may comprise one or more of: a GBR QoS flow or a non-GBR QoS flow; a delay-critical QoS flow; and a QoS flow in a certain PDU session or in a certain set of PDU sessions. Certain examples of the present disclosure provide a first network entity 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 a first network entity 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 will now be described in more detail. In certain examples, the NG-RAN is used as an example of a network entity. However, the skilled person will appreciate that the techniques described herein may be applied to any other suitable type of entity, for example gNB, Session Management Function (SMF), User Plane Function (UPF), and / or any other node. In certain examples, a GBR QoS flow is used as an example. However, the skilled person will appreciate that the techniques described herein may be applied to any other suitable type of flows, for example non-GBR QoS flows, delay-critical GBR flows, and / or any other type of QoS flows. The NG-RAN may be configured with information that indicates the estimated and / or precise energy use (or energy consumption) that is associated with a particular QoS flow, where the QoS flow is in turn associated with a particular set (one or more) of QoS parameters. For example, the NG-RAN may be configured with energy usage (or energy consumption) information for every 5QI, or for every entry in the existing QoS table that is shown earlier. The 5QI may be standardized or non-standardized. Moreover the QoS flow may be identified by the 5QI or a QFI. The skilled person will appreciate that the techniques described herein may use any suitable form of QoS flow identification, for example 5QI, QFI and / or other QoS flow identification methods. For example, a new column (or columns) can be defined to contain the energy usage unit (or energy consumption unit) and / or energy usage rate (or energy consumption rate) for each set of QoS parameters: 5QI Value Resource Type Default Priority Level Packet Delay Budget (NOTE 3) Packet Error Rate Default Maximum Data Burst Volume (NOTE 2) Default Averaging Window Energy usage rate 1 GBR (or non-GBR) 20 100 ms 10‘2 N / A 2000 ms N units or M units / time The table above shows one example of the proposal where the “Energy usage rate” column indicates how much energy is required to admit the particular QoS flow based on the characteristics shown above, such as, but not limited to, 5QI, resource type (GBR vs non-GBR), priority level, packet error rate, etc. Note that other methods to associate a QoS flow characteristics to the level of energy required for its admission may be defined using any other mechanism. However the main proposal is that the NG-RAN should be configured with information about the energy requirements (e.g. maximum and / or minimum energy consumption level(s), upper and / or lower bound, etc.) and / or usage with regards to a particular QoS flow (or QoS flows in a particular PDU session or in a set of PDU sessions, etc.). When the NG-RAN receives a request to admit a QoS flow, the NG-RAN should verify the required energy levels for the QoS flow in question, or the required energy usage rate / requirement for the QoS flow in question, optionally where this may be verified against existing information that the NG-RAN either has locally or may contact another network function to get such information. In this case, the NG-RAN entity may provide the necessary QoS information to the network function which then returns the required energy usage level for this QoS flow. Once the NG-RAN has determined the required energy usage for the QoS flow, the NG-RAN may verify any energy constraints that the NG-RAN may be configured to operate with. The verification may be based on any of the following: • The NG-RAN may be configured with a maximum energy operation quota (and / or an energy operation upper bound) which the NG-RAN should not exceed. The NG-RAN may verify the requirements, in terms of energy, for the given QoS flow (or QoS flows). The NG-RAN verifies if the total energy - e.g. current energy level in use plus the energy associated with the QoS flow - would exceed the NG-RAN’s energy quota. If yes, then the NG-RAN may reject the admission of the new QoS flow (or QoS flows). The NG-RAN may indicate to the requesting entity (e.g. SMF, AMF, UPF, and / or any other network node) the cause for rejecting the QoS flow admission is due to lack of sufficient energy or due to energy level exceeding the quota. • The NG-RAN may be configured to only admit certain QoS flow (or QoS flows) if its (or their) associated energy level (or energy requirement level) is less than (or equal to) a certain energy usage (or energy consumption) requirement. Note that this may be independent of the overall energy level being used in the NG-RAN (e.g. the overall energy consumption level in the NG-RAN at a given time, location and / or traffic status, etc.). As such, the NG-RAN verifies if the required energy level for the new QoS flow is below (or equal to) the allowed level: if it is then the NG-RAN may admit the QoS flow, otherwise if the required energy for the new QoS flow is above the allowable energy consumption level (or energy requirement level) then the NG-RAN may reject admission of this new QoS flow. In certain examples, at least one new set of indications may be defined in association with a new QoS flow (or QoS flows) such the set of indications informs the NG-RAN whether the QoS flow should be admitted even if its energy requirement is higher than the configured level that the NG-RAN can accept. This indication may be in the form of “energy priority” and may be composed of a single priority value which may be from a well-known range, or may be a categorical (or ordinal) value that reflects some level of energy such as “low energy priority”, “medium energy priority”, or “high energy priority”. Based on the priority level, the NG-RAN can determine if the QoS flow should be admitted even if its associated energy usage (or energy consumption) level is higher than the maximum value (or an upped bound). For example, if the energy priority level is deemed to be high, then the NG-RAN may admit the new QoS flow even if its energy requirement level is higher than the acceptable level. Note that the NG-RAN may be configured to permit a certain number of QoS flows for which the energy level may exceed the required (or expected) level. However the NG-RAN may stop admitting new QoS flows based on the NG-RAN determining that the exceptions or the higher priority QoS flows (with respect to energy) has also exceeded a certain maximum - where the maximum may be a maximum number of already admitted QoS flows, or the maximum may be the total energy (or total excess energy) that these admitted QoS flows would use or require. The NG-RAN may be configured with all these thresholds. In another example, the thresholds are provided to the NG-RAN from another network entity (and / or function), e.g. AMF, SMF, etc. Examples to start / stop the consideration of energy criteria for QoS admission Certain examples of the present disclosure may apply one or more of the following, in any suitable order or combination. For example, the NG-RAN may start the consideration of energy criteria - based on the techniques disclosed herein - when determining whether to admit a new QoS flow based on one or more of the following: • Based on the configuration in the NG-RAN e.g. to start considering energy as a criterion for QoS flow admission (or QoS flow modification). • For all UEs. • For all UEs on a particular slice, where the slice may be known to the NG-RAN. • For UEs in a certain location, at a certain time. • For all UEs (or a selected group of UEs) of a certain category (or type) and / or capability. • When the energy usage in the NG-RAN exceeds a certain threshold (or maximum value, or upped bound, etc.). • When the energy usage in the NG-RAN exceeds a certain value allowed (or permitted) according an energy policy (e.g. defined or pre-configured, etc.). • Based on assistance information at the NG-RAN obtained from at least another network entity (and / or function). For example, assistance information related to energy consumption policy or criteria (or thresholds or upped and / or lower bounds on energy consumption) that is provided by the AMF to the NG-RAN. In one example, the assistance information is based on the UE subscription information that the AMF retrieved from the UDM. In another example, AMF obtains this information from another network entity (and / or function), NWDAF, and / or from an Application function. • The AM F may include the information related to the energy consideration for admission of QoS flows, for the given UE, included in any of the existing (and / or newly defined) UE context management procedures. • The AMF and / or the NG-RAN may store the information related to the energy consideration for admission of QoS flows, for the UE, in the UE context. In another example, the UE also stores the energy consideration information. • When the NG-RAN is informed to start considering energy for admission control of QoS flows by any network function such as, but not limited to, an AMF. The “examples of specification changes” disclosed below provide examples on the new class 1 and / or class 2 for interaction between the NG-RAN node and the network (e.g. AMF, other network entities and / or functions). • The NG-RAN may apply the energy consideration, on admission of QoS flows, for a selected group of UEs, but not to other groups of UEs in the network. • The NG-RAN may apply the energy consideration, on admission of QoS flows, for a given period of time, and / or for a given location. While not apply NG-RAN may not apply the energy consideration the rest of the time and / or other locations. • The NG-RAN may switch on / off the energy consideration on all UE(s) (or some or a group of UEs or a particular UE) admission of QoS flows, based on, e.g. update of energy consumption policy (or criteria, upped and / or lower bounds, etc.) and / or based on indication from another network entity (and / or function). For example, based on an indication from the AMF to start or stop (or pause) the admission control based on energy consumption. • The NG-RAN may switch on / off the energy consideration of all UEs (e.g. served by the NG-RAN) considering the overall energy consumption of the NG-RAN, e.g. whether the NG-RAN energy consumption is going above / below a defined (or pre-configured) energy consumption values. • In another example, the NG-RAN may switch on / off the energy consideration admission of QoS flows in one (or more) of its cells. • The NG-RAN may provide an indication to all UE(s) (or some or a group of UEs or a particular UE) on NG-RAN behaviour to control admission of QoS flows, based on energy consideration (e.g. pre-defined, pre-configured in the NG-RAN, and / or obtained by the NG-RAN from one (or more) network entity(-ies) (and / or function(s)). • The network may provide assistance information to all UE(s) (or some or a group of UEs or a particular UE), on the network behaviour to control admission of QoS flows based on energy consumption criteria. • The network may provide the information to all UE(s) (or some or a group of UEs or a particular UE), using existing (and / or newly defined) dedicated signalling and / or messages (e.g. NAS and / or RRC signalling / messages). Additionally, the network may provide the information using system information broadcast (e.g. periodically and / or on-demand), e.g. using existing SIBs and / or newly defined SIBs. • The NG-RAN may provide an indication to all UE(s) (or some or a group of UEs), of the NG-RAN behaviour (or policy) for energy consideration on admission of QoS flows, by providing a 1 bit (flag) in the system information broadcast to indicate that admission control is enabled / not enabled (flag value is set to T or ’O’). In another example, the indication is provided to the UE using existing (and / or newly defined RRC signalling / messages). • In another example, the network may provide the information about the energy consideration on admission of QoS flows, as part of the UE registration procedure. For example, the AMF provides the information to the UE as part of the UE registration procedure. • The UE may provide (e.g. to the network) its capability to support the new network behaviour to control the admission of QoS flows based on energy consideration. • The network (e.g. NG-RAN and / or AMF) may verify the UE capability to support the new feature of admission control of QoS Flows based on energy consideration. • In one example, the network (e.g. NG-RAN and / or AMF) may accept or reject the UE if it cannot support (i.e. does not have the capability) to support the admission control of QoS Flows based on energy consideration. In certain example, when energy usage goes up, the NG-RAN can start releasing certain QoS flow. In certain examples, the NG-RAN may stop (fully or partially) the consideration of energy criteria (as described herein) to admit new QoS flow(s) based on any suitable condition, for example based on one or more of the following (e.g. in any order or combination): • Based on the configuration in the NG-RAN e.g. to stop considering energy as a criterion for QoS flow(s) admission. • For all UEs. • For all UEs on a particular slice, where the slice may be known to the NG-RAN. • For UEs in a certain location, at a certain time. • When the energy usage in the NG-RAN goes below a certain threshold. • When the NG-RAN is informed to stop considering energy for admission control of QoS flows by any network function such as, but not limited to, an AMF. • Other examples, similar to those disclosed herein for the case of start the consideration of energy criteria to admit new QoS flow(s). In certain examples, the NG-RAN may stop (fully or partially) the consideration of energy criteria (as disclosed herein) to admit new QoS flow(s), for example based on any of the examples disclosed herein: In certain examples, the NG-RAN may be configured to permit a certain number of QoS flows for which the energy level may exceed the required (or expected) level. However the NG-RAN may stop admitting new QoS flows based on the NG-RAN determining that the exceptions or the higher priority QoS flows (with respect to energy) has also exceed a certain maximum -where the maximum may be a maximum number of already admitted QoS flows, or the maximum may be the total energy (or total excess energy) that these admitted QoS flows would use or require. The NG-RAN may be configured with all these thresholds. Solutions to modify, release / pre-empt QoS Flows based on energy criteria for QoS Flows admission The techniques described herein, including the techniques described above, may be applied for any of the following, in any suitable order or combination. For example, in addition to start and / or stop of admission of QoS Flows based on energy consideration, the NG-RAN may also pause, activate, deactivate, admit (or modify) QoS flows. The various techniques disclosed herein may be applied to other QoS flow operations, e.g. to modify an existing QoS flow. The skilled person will appreciate that the techniques described herein are not restricted to admission of QoS flows. Moreover, in certain examples the NG-RAN may modify, replace, release or pre-empt existing QoS Flows taking into consideration of energy consumption criteria. In certain examples, the NG-RAN may decide to change the mapping of QoS Flows to DRBs based on energy consideration. In certain examples, the NG-RAN may prioritise the Allocation and Retention Priority (ARP) allocated to QoS Flows on the energy consideration for those QoS Flows. For example, in the case of traffic congestion and / or high priority UEs (and / or UEs services, e.g. URLLC, etc.). In another example, the energy consumption criteria (or policy or threshold or upper bound, etc.) is not violated. In another example, the NG-RAN may prioritise the energy consideration of the QoS Flows on their ARP, where optionally the ARP may include existing parameters or a new energy specific parameters. For example, in the case of increase in energy consumption, close to or higher than the allowed energy consumption criteria (or level or policy or threshold or upper bound, etc.). In certain examples, the NG-RAN may consider an version of ARP that is based on energy consumption criteria when admitting QoS Flows. The various techniques described herein based on interaction between the NG-RAN and core network (CN) may also be applied to other interfaces (i.e. not only to the NG or S1), including non-3GPP interfaces (e.g. via N3IWF support of connectivity). In certain examples, the NG-RAN may be configured, or may determine, to release at least one QoS flow due to energy constraints. For example, one or more of the following may be applied in any suitable order or combination: • The NG-RAN may be notified to release at least one QoS flow due to energy usage exceeding a certain threshold, or due to energy constraints. • The NG-RAN may be configured to release at least one QoS flow due to energy usage exceeding a certain threshold, or due to energy constraints. The NG-RAN may determine that the energy constraints is such that at least one QoS flow needs to be released, or the NG-RAN may determine that at least one QoS flow is using more energy than accepted e.g. based on a certain energy threshold or quota per QoS flow. • The NG-RAN may be configured to determine at least one QoS flow which need to be released (or modified, e.g. such that the QoS treatment may be downgraded) due to energy constraints. • The NG-RAN may be configured with methods to determine which QoS flow(s) need to be modified or released due to energy constraints. o For example, the NG-RAN may select a QoS flow based on its total energy usage, or its average energy usage, or the energy usage within a time window, or any combinations of these. The NG-RAN may be configured with a threshold against which such determination may be done. o For example, the NG-RAN may select a QoS based on a combination of energy usage and priority (e.g. any of the ARP parameters), where the determination of whether the QoS flow in question should be selected can be based on a weight value applied to these parameters and then a total score can be used to make the final determination. o For example, a QoS flow may be associated with a new energy priority parameters, or energy specific ARP parameters (or similar parameters) which can be used by the NG-RAN to select a QoS flow (for release or modification), where these parameters may be used when the reason for release or modification of the QoS flow is due to energy. As such, for example, the NG-RAN may use the existing ARP parameters to pre-empt a certain QoS flow if the reason is purely due to resources which are not energy related, otherwise if the constraints are energy related then the energy related APR parameters should be used. o For example, the NG-RAN may be configured to select QoS flows with certain QoS profiles or parameters, where it is known that these profiles or parameters are associated with a certain energy usage and the NG-RAN may be configured to relieve the energy usage of these associated energy costs. o For example, the NG-RAN may be configured to achieve a certain total reduction of energy level and as such the NG-RAN may select QoS flows that can help achieve such reduction e.g. the NG-RAN may select the QoS flow that is associated with a maximum energy usage, etc. For example, the NG-RAN may select at least one QoS flow such that the total energy used by the at least one QoS flow can achieve the desired reduction in energy. o The NG-RAN may consider the priority of the QoS flow or the priority of the user. For example, energy constraints or pre-emption of QoS flows due to energy constraints, or release of QoS flows due to energy constraints, or downgrading of QoS flows due to energy constraints should not be applied to QoS flows which are used for emergency services, or which are used for high priority services. o Any of the above may be applied in any suitable order or combination. o In certain examples, the selection of a QoS flow may be done for the purpose of applying certain actions - such as release of a QoS flow or downgrade of a QoS flow - due to energy constraints. The skilled person will appreciate that the various techniques described herein may be applied to 5GS and / or any other system, such as 3G, 4G, 6G, etc. Furthermore the various techniques described herein that require interactions between the core network and the RAN may be applied to all cases, i.e. for 3GPP RAN and non-3GPP RAN. Examples of specification changes (new text, procedures, messages and signalling) 3GPP TS 38.413 Energy Criteria for Admission Control of QoS Flows Procedures: Energy Criteria for Admission Control Start: The purpose of the Energy Criteria for Admission Control of QoS Flows procedure is to allow the AMF to request the NG-RAN node to initiate an admission control session of QoS Flows for a UE, based on (or considering a defined (or pre-configured) energy criteria. The procedure uses UE-associated signalling. If no UE-associated logical NG-connection exists, the UE-associated logical NG-connection shall be established as part of the procedure. Alternatively, this procedure may be a generic procedure which does not necessarily tied to a specific UE. [see Figure 1] The AMF initiates the procedure by sending an ENERGY CRITERIA FOR ADMISSION CONTROL START message (OR ENERGY CRITERIA FOR ADMISSION CONTROL OF QOS FLOWS START OR ENERGY BASED ADMISSION CONTROL START and / or any other naming example). The AMF may indicate the criteria for which the NG-RAN should verily before applying the energy control e.g. energy quota, Upon reception of the ENERGY CRITERIA FOR ADMISSION CONTROL START message, the NG-RAN node shall initiate the requested admission control session of QoS Flows for the UE, based on energy criteria. If the EnergyAdmissionControlActivation IE (or any other suitable example of IE naming) is included in the ENERGY CRITERIA FOR ADMISSION CONTROL START message, the NG-RAN node shall, if supported, initiate the requested session of admission control of QoS Flows based on energy criteria. Energy Criteria for Admission Control Failure Indication: The purpose of the ENERGY CRITERIA FOR ADMISSION CONTROL FAILURE INDICATION procedure is to allow the NG-RAN node to inform the AMF that an ENERGY CRITERIA FOR ADMISSION CONTROL START procedure or a Deactivate (or STOP) ENERGY CRITERIA FOR ADMISSION CONTROL procedure has failed. The procedure uses UE-associated signalling. [see Figure 2] The NG-RAN node initiates the procedure by sending an ENERGY CRITERIA FOR ADMISSION CONTROL FAILURE INDICATION message. The NG-RAN should include a cause value to indicate the reason for failure. Upon reception of the ENERGY CRITERIA FOR ADMISSION CONTROL INDICATION message, the AMF shall take appropriate actions based on the failure reason indicated by the Cause IE. Energy Criteria for Admission Control Deactivate (or Stop): The purpose of the ENERGY CRITERIA FOR ADMISSION CONTROL STOP (or DEACTIVATE) procedure is to allow the AMF to request the NG-RAN node to deactivate (or stop) the session of admission control of QoS Flows based on energy criteria. The procedure uses UE-associated signalling. [see Figure 3] The AMF initiates the procedure by sending a ENERGY CRITERIA FOR ADMISSION CONTROL STOP (or DEACTIVATE) message to the NG-RAN node. Upon reception of the ENERGY CRITERIA FOR ADMISSION CONTROL STOP (or DEACTIVATE) message, the NG-RAN node shall stop the admission control of QoS Flows based on energy criteria. Energy Criteria for Admission Control Notify: The purpose of the ENERGY CRITERIA FOR ADMISSION CONTROL NOTIFY procedure is to notify the AMF that the NG-RAN has started (or started or initiated or will start or initiate) QoS Flows admission control, modification and / or release, based on energy consideration or a defined (or pre-configured) energy criteria. The procedure uses UE-associated signalling. If no UE-associated logical NG-connection exists, the UE-associated logical NG-connection slial 1 be established as part of the procedure. Alternatively, this procedure may be a generic procedure which does not necessarily tied to a specific UE. In another example, the purpose of tire ENERGY CRITERIA FOR ADMISSION CONTROL NOTIFY procedure is to notify the AMF that the NG-RAN has stopped (or stopped or will stop) QoS Flows admission control, modification and / or release, based on energy consideration and / or a defined (or pre-configured) energy criteria. The procedure uses UE-associated signalling. If no UE-associated logical NG-connection exists, the UE-associated logical NG-connection shall be established as part of the procedure. Alternatively, this procedure may be a generic procedure which does not necessarily tied to a specific UE. In another example, the purpose of the ENERGY CRITERIA FOR ADMISSION CONTROL NOTIFY procedure is to notify the AMF of other changes, at the NG-RAN, related to QoS Flows admission, modification, and / or release based on energy consideration and / or a defined (or pre-configured) energy criteria. [see Figure 4] The NG-RAN node initiates tire procedure by sending, for example, an ENERGY CRITERIA FOR ADMISSION CONTROL NOTIFY message (other naming is also possible). The ENERGY CRITERIA FOR ADMISSION CONTROL NOTIFY message shall contain the information QoS flows which are (has been or will be) admitted, modified, and / or released, based on, for example, energy7 consideration and / or a defined (or pre-configured) energy criteria. - For each PDU session for which some QoS flows are admitted, modified, and / or released by the NG-RAN node, tire ENERGY CRITERIA FOR ADMISSION CONTROL NOTIFY message may include the following information (e.g. as part of the PDU Session Resource Notify Transfer IE and / or a newly defined IE): 1. The list of QoS flows which are admitted, modified, and / or released by the NG-RAN node by the NG-RAN node, based on energy consideration, if any, in, for example, any existing IE (e.g. QoS Flow Admitted, QoS Flow Modified, QoS Flow Released List IE) and / or newly defined IEs. 2. Information related to the energy consideration and / or defined (or pre-configured) energy criteria, used by the NG-RAN. Additionally, the NG-RAN node may include the QoS flow(s) release cause in the Cause IE (e.g. using existing and / or newly defined cause value). Upon reception of the ENERGY CRITERIA FOR ADMISSION CONTROL NOTIFY message, the AMF shall, for each PDU session (and / or QoS flow(s)), report this information to at least another network entity (and / or function), e.g. SMF, etc. For example, in the case of SMF receiving this information from the AMF, the SMF shall handle this information as specified in TS 23.502. In another example, the AMF, SMF, etc. may indicate a response to the NG-RAN. The skilled person will appreciate that any other suitable naming of the example messages and / or procedures disclosed herein are also possible, for example (and not limited to): - START (OR STOP OR DEACTIVATE) ENERGY CONSIDERATION, OR - START (OR STOP OR DEACTIVATE) ENERGY CONSIDERATION FOR ADMISSION OF QOS FLOWS. In other example, a new class 1 procedure may be used for the energy consideration for admission control for QoS flows for the UE (refer to the examples below). NGAP Procedures List of NGAP Elementary Procedures In the following tables, all EPs are divided into Class 1 and Class 2 EPs (see subclause 3.1 for explanation of the different classes): 5 Table 8.1-1: Example of update of Class 1 procedures Elementary Procedure Initiating Message Successful Outcome Unsuccessful Outcome Response message Response message Energy Consideration ENERGY CONSIDERATION REQUEST ENERGY CONSIDERATION RESPONSE ENERGY CONSIDERATION FAILURE Table 8.1-1: Example of update of Class 1 procedures Elementary Procedure Initiating Message Successful Outcome Unsuccessful Outcome Response message Response message Energy Consideration Session Activation ENERGY CONSIDERATION SESSION ACTIVATION REQUEST ENERGY CONSIDERATION SESSION ACTIVATION RESPONSE ENERGY CONSIDERATION SESSION ACTIVATION FAILURE Table 8.1-1: Example of updated Class 1 procedures Elementary Procedure Initiating Message Successful Outcome Unsuccessful Outcome Response message Response message Energy Consideration Session Deactivation ENERGY CONSIDERATION SESSION DEACTIVATION REQUEST ENERGY CONSIDERATION SESSION DEACTIVATION RESPONSE 10 Table 8.1-2: Example of update of Class 2 procedures Elementary Procedure Message Energy consideration for Admission Start ENERGY CONSIDERATION FOR ADMISSION START Energy consideration for Admission Failure Indication ENERGY CONSIDERATION FOR ADMISSION FAILURE INDICATION Deactivate Energy consideration for Admission DEACTIVATE ENERGY CONSIDERATION FOR ADMISSION Energy criteria for admission control notify (or Energy consideration for Admission control notify') ENERGY CRITERIA FOR ADMISSION CONTROL NOTIFY (or ENERGY CONSIDERATION FOR ADMISSION CONTROL NOTIFY) Figure 5 illustrates an exemplary method for admission of a QoS flow based on energy. Referring to Figure 5, a first operation 501 comprises, in response to receiving a request to admit a QoS flow, determining, by a first network entity, whether one or more criteria, based on one or more energy requirements dependent on the QoS flow, are satisfied. A second operation 502 comprises admitting or rejecting, by the first network entity, the QoS flow based on the determination. Figure 6 is a block diagram of an exemplary network entity (e.g. AMF entity, base station and / or any other network entity) that may be used in examples of the present disclosure. For example, the NG-RAN node and / or AMF of Figures 1-5 may be provided in the form of the network entity illustrated in Figure 6. 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 600 comprises a processor (or controller) 601, a transmitter 603 and a receiver 605. The receiver 605 is configured for receiving one or more messages from one or more other network entities, for example as described above. The transmitter 603 is configured for transmitting one or more messages to one or more other network entities, for example as described above. The processor 601 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 instructions that, when executed, implement certain examples of the present disclosure. Accordingly, certain examples provide a program comprising code for implementing a method, 5 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 signal carried over a wired or wireless connection. While the invention has been shown and described with reference to certain examples, it will 10 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 acronyms / definitions may be used. 3GPP 3G 3rd Generation Partnership Project 3rd Generation 5 4G 4th Generation 5G 5th Generation 6G 6th Generation 5GS 5G System 5QI 5G QoS Identifier 10 AI / ML Artificial Intelligence / Machine Learning AMF Access and Mobility Management Function ARP Allocation and Retention Priority ON Core Network DRB Data Radio Bearer 15 eNB Base Station FTP File Transfer Protocol GBR Guaranteed Bit Rate gNB 5G Base Station IE Information Element 20 MC-PTT Mission Critical Push To Talk ms milliseconds N3IWF non-3GPP Interworking Function NAS Non Access Stratum NG Next Generation 25 NG Interface between RAN and CN NR New Radio NWDAF Network Data Analytics Function P2P Peer-to-Peer PDU Protocol Data Unit 30 QFI QoS Flow Identifier QoS Quality of Service RAN Radio Access Network RRC Radio Resource Control RSU Roadside Unit 35 S1 Interface between RAN and CN SIB System Information Block SMF Session Management Function TCP Transmission Control Protocol TR Technical Report 40 TS Technical Specification UDM Unified Data Management UE User Equipment UPF User Plane Function URLLC Ultra-Reliable Low Latency Communications 45 V2X Vehicle to Everything

Claims

1. A method for admission of a Quality of Service (QoS) flow based on energy, the method comprising:in response to receiving a request to admit a QoS flow, determining, by a first network entity, whether one or more criteria, based on one or more energy requirements dependent on the QoS flow, are satisfied; andadmitting or rejecting, by the first network entity, the QoS flow based on the determination.

2. A method according to claim 1, wherein the one or more criteria are based on one or more of:a required energy level and / or rate for the QoS flow;a maximum allowed energy level and / or rate;an available energy level and / or rate;one or more energy constraints of the first network entity (e.g. a maximum energy quota);a priority associated with the QoS flow;a number of QoS flows already admitted; andone or more thresholds.

3. A method according to claim 1 or 2, wherein the one or more energy requirements are determined based on one or more of:a set of QoS parameters associated with the QoS flow; andone or more characteristics of the QoS flow.

4. A method according to claim 3, wherein the one or more characteristics comprise one or more of:a 5QI value;a resource type (e.g. GBR or non-GBR);a default priority level;a packet delay budget;a packet error rate; anda default averaging window.

5. A method according to any preceding claim, wherein the one or more criteria comprise one or more criteria based on a comparison of an energy requirement to an energy threshold.

6. A method according to claim 5, wherein the energy requirement comprises one or more of:an energy requirement associated with the QoS flow; anda total energy requirement comprising a current energy requirement and an energy requirement associated with the QoS flow.

7. A method according to any preceding claim, wherein the one or more criteria comprise one or more criteria based on a comparison of a priority of the QoS flow to a priority threshold.

8. A method according to any preceding claim, further comprising, if the QoS flow is rejected, transmitting, to another network entity, an indication of the rejection including a cause of the rejection.

9. A method according to any preceding claim, further comprising receiving, by the first network entity, configuration for applying or disapplying admission of a QoS flow based on energy.

10. A method according to any preceding claim, further comprising receiving by the first network entity, from a second network entity (e.g. AMF), information (e.g. assistance information) for allowing the network entity to perform the determination.

11. A method according to claim 9 or 10, wherein the configuration and / or information comprises one or more of:information relating to energy consumption policy;one or more thresholds; andinformation based on UE subscription information.

12. A method according to claim 9, 10 or 11, wherein the configuration and / or information relates and / or is applied (e.g. only) to one or more of:all UEs;one or more UEs on a certain network slice;one or more UEs in a certain location;one or more UEs at certain time;one or more UEs of a certain type;one or more UEs of a certain capability;one or more UEs with certain UE subscription information (e.g. information relating to energy requirements and / or energy information); andone or more cells associated with the first network entity.

13. A method according to any of claims 9 to 12, further comprising storing (e.g. by the first network entity, a second network entity (e.g. AMF) and / or a UE) the configuration and / or information (e.g. in a UE context associated with the UE).

14. A method according to any of claims 9 to 13, wherein the configuration and / or information is received in response to a UE registration procedure.

15. A method according to any preceding claim, further comprising receiving, from a UE, information indicating a capability of the UE to support admission of a QoS flow based on energy.

16. A method according to claim 15, further comprising accepting or rejecting a UE based on the capability of the UE to support admission of a QoS flow based on energy.

17. A method according to any preceding claim, further comprising performing, by the first network entity, an action relating to one or more existing QoS flows based on a change of and / or update to one or more energy requirements dependent on the QoS flows.

18. A method according to claim 17, wherein the action comprises one or more of: releasing a QoS flow;pausing a QoS flow;activate a QoS flow;deactivate a QoS flow;modify a QoS flow;replace a QoS flow;modify a mapping of a QoS flow to a DRB; and modify the ARP allocated to a QoS flow.

19. A method according to any preceding claim, wherein the first network entity comprises one or more of:an NG-RAN;a gNB;an SMF entity; anda UPF entity.

20. A method according to any preceding claim, wherein the QoS flow comprises one or more of:a GBR QoS flow or a non-GBR QoS flow;a delay-critical QoS flow; and5 a QoS flow in a certain PDU session or in a certain set of PDU sessions.

21. A first network entity configured to perform a method according to any preceding claim.

22. A network (or wireless communication system) comprising a UE and a first network10 entity according to claim 21.

23. 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 20.1524. A computer or processor-readable data carrier having stored thereon a computer program according to claim 23.31

Images