Network slice admission control based on energy consumption

Abstract

A method performed by an energy efficiency control function (EECF) of a 5G core network includes receiving a request from a session management function (SMF) for slice admission control based on energy efficiency, sending a request to obtain energy consumption analytics from a core network function, receiving energy consumption analytics from the core network function, determining that a protocol data unit (PDU) Session can be established; and / or that other PDU Session(s) can be released, and sending slice admission control results to the SMF from the determination of PDU session establishment.

Description

NETWORK SLICE ADMISSION CONTROL BASED ON ENERGY CONSUMPTIONRELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 574,500, filed April 4, 2024. and entitled NETWORK SLICE ADMISSION CONTROL BASED ON ENERGY CONSUMPTION, the contents of which are hereby incorporated herein by reference in their entirety.BACKGROUND

[0002] As stated in 3GPP TS 22.261 v 19.5.0 (2023-12) Service Requirements for the 5G System, Stage 1 (Release 19), energy efficiency is a critical issue in 5G. The potential to deploy systems in areas without a reliable energy source requires new methods of managing energy consumption not only in the UEs but throughout all components of the 5G system.

[0003] Climate change and the rising consumption of energy motivate increased energy efficiency. Energy efficiency is a strategic priority for telecom operators around the world.

[0004] Energy efficiency as a service criteria allows services to be delivered with diverse energy' efficiency and energy consumption policies. Energy consumption and efficiency information and network energy states can be exposed to third parties and energy consumption can be constrained.

[0005] For example, per individual UE or PDU session, the following are considerations: energy consumption in a network slice, energy' credit threshold, and maximum energy credit limit for a network slice.

[0006] Per network slice (overall), the following are considerations: energy consumption, maximum energy credit limit, and energy- credit threshold.

[0007] The overall energy consumption of a network slice shall not exceed the maximum energy credit limit.

[0008] The energy consumption of an individual UE or PDU session utilizing a network slice may exceed the per-UE or per-PDU session energy credit threshold of the network slice.

[0009] If threshold is reached, admission may be granted yvith a reduced QoS (e.g., lo ver bandyvidth, longer latency or degraded AQP level) or a higher charging rate.

[0010] The energy consumption of an individual UE or PDU session utilizing a network slice shall not exceed the per-UE or per-PDU session maximum energy credit limit of the network slice.Network Slice Admission Control (NSAC)

[0011] A conventional NSAC Function (NSACF) supports validation of the maximum number of UEs per slice, and the maximum number of PDU Sessions per slice.

[0012] An NSACF API, NumOfUEs / NumOfPDUs_Update_Request(), may be used by an Access and Mobility Function (AMF) and / or Session Management Function (SMF) to update the number of UEs / PDU Sessions.

[0013] Contributions

[0014] In accordance with a first contribution to the general knowledge (Contribution A), the NSACF may be enhanced to control the overall energy consumption per network slice. When receiving aNumOfUEs / NumOIPDUs_Update_Request(), theNSACF checks whether a maximum energy credit limit is exceeded for the network slice, and whether an energy credit threshold is reached. The energy credit threshold can be related to an admission with a reduced QoS (e.g., lower bandwidth, longer latency or degraded AQP level) or a higher charging rate. The SMF queries the NSACF during PDU Session establishment to check whether overall energy' consumption will exceed the maximum energy credit limit.

[0015] The NSACF performs the following based on operator policies: if the maximum energy credit limit is expected to be exceeded for the slice, notify the SMF (PDU Session establishment procedure fails); if the energy credit threshold is expected to be reached but below the maximum energy’ credit limit (PDU Session establishment procedure succeeds), update the number of PDU sessions, and notify the SMF and / or the Application Function (AF) charging function about the energy credit threshold being reached. Otherwise, update the number of PDU sessions.

[0016] In accordance yvith a second contribution to the general knowledge (Contribution B), an Energy Efficiency Control Function (EECF): collects energy information of the Single Net vork Slice Selection Assistance Information (S-NSSAI) from Operations, Administration, and Maintenance (0AM); determines the maximum number of UEs and the maximum number of PDU sessions for S-NSSAI(s) based on AF input, local operator policy or collected energy information; and sends the maximum number of UEs and the maximum number of PDU sessions to the NSACF.

[0017] The NSACF subscribes to network slice energy consumption analytics from the Network Data Analytics Function (NWDAF) / EECF of an S-NSSAI. When a UE attempts to register with the S-NSSAI or to establish a PDU session, the AMF / SMF updates the NSACF to increase the number of UEs or PDU sessions. The AMF checks the energy' state of the S-NSSAI (via the EECF or NSACF), to which the NSACF replies with a result, which may include yvhether an NSACenergy' threshold is exceeded, whether or not the S-NSSAI is included in the allowed NSSAI, and, as applicable, whether or not the PDU session has been established.

[0018] During PDU Session establishment, the NRF selects an SMF. The NRF may select an SMF based on whether or not the SMF supports energy7savings states or features. For example, the NRF may receive an indication that energy7savings is desired and, based on the indication determine to only select an SMF that supports energy' savings. The SMF checks admission control for the S-NSSAI with the EECF (or NSACF). The EECF replies whether the S-NSSAI can be provided. The SMF proceeds with the session establishment procedure and sends a response message (accept / reject) to the AMF / UE.BRIEF DESCRIPTION OF THE DRAWINGS

[0019] A more detailed understanding may be had from the detailed description below, given by way of example in conjunction with drawings appended hereto. Figures in such drawings, like the detailed description, are examples. As such, the Figures (FIGs.) and the detailed description are not to be considered limiting, and other equally effective examples are possible and likely. Furthermore, like reference numerals in the FIGs. indicate like elements, and wherein:

[0020] FIG. 1 A is a sy stem diagram illustrating an example communications system;

[0021] FIG. IB is a system diagram illustrating an example wireless transmit / receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1 A;

[0022] FIG. 1C is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communications system illustrated in FIG. 1A;

[0023] FIG. ID is a system diagram illustrating a further example RAN and a further example CN that may be used within the communications system illustrated in FIG. 1 A;

[0024] FIG. 2 illustrates an example NSAC procedure based on Energy' Category'; and

[0025] FIG. 3 illustrates an example NSAC procedure using Duplicated Slices Bundling.DETAILED DESCRIPTION|0026| In the following detailed description, numerous specific details are set forth to provide a thorough understanding of embodiments and / or examples disclosed herein. However, it will be understood that such embodiments and examples may be practiced without some or all of the specific details set forth herein. In other instances, well-known methods, procedures, components and circuits have not been described in detail, so as not to obscure the following description. Further, embodiments and examples not specifically described herein may be practiced in lieu of,or in combination with, the embodiments and other examples described, disclosed or otherwise provided explicitly, implicitly and / or inherently (collectively "provided") herein. Although various embodiments are described and / or claimed herein in which an apparatus, system, device, etc. and / or any element thereof carries out an operation, process, algorithm, function, etc. and / or any portion thereof, it is to be understood that any embodiments described and / or claimed herein assume that any apparatus, system, device, etc. and / or any element thereof is configured to carry out any operation, process, algorithm, function, etc. and / or any portion thereof.

[0027] Example Communications System

[0028] The methods, apparatuses and systems provided herein are well-suited for communications involving both wired and wireless networks. An overview of various types of wireless devices and infrastructure is provided with respect to FIGs. 1A-1D, where various elements of the network may utilize, perform, be arranged in accordance with and / or be adapted and / or configured for the methods, apparatuses and systems provided herein.

[0029] FIG. 1 A is a system diagram illustrating an example communications system 100 in which one or more disclosed embodiments may be implemented. The communications system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users. The communications system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, the communications systems 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC- FDMA), zero-tail (ZT) unique-word (UW) discreet Fourier transform (DFT) spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block-filtered OFDM, filter bank multicarrier (FBMC), and the like.

[0030] As shown in FIG. 1A. the communications system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104 / 113, a core network (CN) 106 / 115, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By7way of example, the WTRUs 102a, 102b, 102c, 102d, any7of which may be referred to as a "station" and / or a "STA", may be configured to transmit and / or receive wireless signals and may include (or be) a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant(PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi- Fi device, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and / or other wireless devices operating in an industrial and / or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and / or industrial wireless networks, and the like. Any of the WTRUs 102a, 102b, 102c and 102d may be interchangeably referred to as a UE.

[0031] The communications systems 100 may also include a base station 1 14a and / or a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d, e.g., to facilitate access to one or more communication networks, such as the CN 106 / 115, the Internet 110, and / or the networks 112. By way of example, the base stations 114a. 114b may be any of a base transceiver station (BTS), a Node-B (NB), an eNode-B (eNB), a Home Node-B (HNB), a Home eNode-B (HeNB), a gNode-B (gNB), a NR Node-B (NR NB), a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

[0032] The base station 114a may be part of the RAN 104 / 113, which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. The base station 114a and / or the base station 114b may be configured to transmit and / or receive wireless signals on one or more carrier frequencies, which may be referred to as a cell (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage for a wireless service to a specific geographical area that may be relatively fixed or that may change over time. The cell may further be divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in an embodiment, the base station 114a may include three transceivers, i.e., one for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each or any sector of the cell. For example, beamforming may be used to transmit and / or receive signals in desired spatial directions.

[0033] The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR),ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable radio access technology (RAT).

[0034] More specifically, as noted above, the communications system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. For example, the base station 114a in the RAN 104 / 113 and the WTRUs 102a, 102b, 102c may implement a radio technology7such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 116 using wideband CDMA (WCDMA). WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High-Speed Downlink Packet Access (HSDPA) and / or High-Speed Uplink Packet Access (HSUPA).

[0035] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and / or LTE- Advanced (LTE-A) and / or LTE- Advanced Pro (LTE-A Pro).

[0036] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR Radio Access, which may establish the air interface 116 using New Radio (NR).

[0037] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, for instance using dual connectivity7(DC) principles. Thus, the air interface utilized by WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions sent to / from multiple ty pes of base stations (e.g., an eNB and a gNB).

[0038] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (Wi-Fi), IEEE 802.16 (i.e.. Worldwide Interoperability7for Microwave Access (WiMAX)), CDMA2000, CDMA2000 IX, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.

[0039] The base station 114b in FIG. 1 A may7be a wireless router, Home Node-B, Home eNode- B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, and the like. In anembodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology7such as IEEE 802. 11 to establish a wireless local area network (WLAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802. 15 to establish a wireless personal area network (WPAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish any of a small cell, picocell or femtocell. As show n in FIG. 1 A. the base station 114b may have a direct connection to the Internet 110. Thus, the base station 114b may not be required to access the Internet 110 via the CN 106 / 1 15.

[0040] The RAN 104 / 1 13 may be in communication with the CN 106 / 115, which may be any ty pe of network configured to provide voice, data, applications, and / or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have varying quality of service (QoS) requirements, such as differing throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like. The CN 106 / 115 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions, such as user authentication. Although not shown in FIG. 1 A, it will be appreciated that the RAN 104 / 113 and / or the CN 106 / 1 15 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 / 113 or a different RAT. For example, in addition to being connected to the RAN 104 / 113, which may be utilizing an NR radio technology7, the CN 106 / 115 may also be in communication with another RAN (not shown) employing any of a GSM. UMTS, CDMA 2000. WiMAX. E-UTRA, or Wi-Fi radio technology.

[0041] The CN 106 / 115 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 may include circuit-switched telephone networks that provide plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP) and / or the internet protocol (IP) in the TCP / IP internet protocol suite. The networks 112 may include wired and / or wireless communications networks owned and / or operated by other service providers. For example, the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104 / 1 14 or a different RAT.

[0042] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities (e.g., the WTRUs 102a. 102b, 102c. 102d may include multiple transceivers for communicating with different wireless networks over different wirelesslinks). For example, the WTRU 102c shown in FIG. 1A may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.

[0043] FIG. 1 B is a system diagram illustrating an example WTRU 102. As shown in FIG. 1 B, the WTRU 102 may include a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and / or other elements / peripherals 138, among others. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.

[0044] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. While FIG. IB depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 118 and the transceiver 120 may be integrated together, e.g., in an electronic package or chip.

[0045] The transmit / receive element 122 may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 114a) over the air interface 116. For example, in an embodiment, the transmit / receive element 122 may be an antenna configured to transmit and / or receive RF signals. In an embodiment, the transmit / receive element 122 may be an emitter / detector configured to transmit and / or receive IR, UV, or visible light signals, for example. In an embodiment, the transmit / receive element 122 may be configured to transmit and / or receive both RF and light signals. It will be appreciated that the transmit / receive element 122 may be configured to transmit and / or receive any combination of wireless signals.

[0046] Although the transmit / receive element 122 is depicted in FIG. IB as a single element, the WTRU 102 may include any number of transmit / receive elements 122. For example, the WTRU 102 may employ MIMO technology7. Thus, in an embodiment, the WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.

[0047] The transceiver 120 may be configured to modulate the signals that are to be transmitted by the transmit / receive element 122 and to demodulate the signals that are received by the transmit / receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11, for example.

[0048] The processor 118 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. In addition, the processor 118 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and / or the removable memory 132. The non-removable memory 130 may include random-access memory (RAM), readonly memory (ROM), a hard disk, or any other type of memory storage device. The removable memory' 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor 118 may access information from, and store data in, memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).

[0049] The processor 118 may receive power from the power source 134, and may be configured to distribute and / or control the power to the other components in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may include one or more dry cell batteries (e.g.. nickel-cadmium (NiCd). nickel-zinc (NiZn). nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like.

[0050] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g.. longitude and latitude) regarding the current location of the WTRU 102. In addition to, or in lieu of, the information from the GPS chipset 136, the WTRU 102 may receive location information over the air interface 116 from a base station (e g., base stations 114a, 114b) and / or determine its location based on the timing of the signals being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by way of any suitable location-determination method while remaining consistent with an embodiment.

[0051] The processor 118 may further be coupled to other elements / peripherals 138, which may include one or more software and / or hardware modules / units that provide additional features, functionality and / or wired or wireless connectivity. For example, the elements / peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (e.g., forphotographs and / or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a virtual reality and / or augmented reality (VR / AR) device, an activity tracker, and the like. The elements / peripherals 138 may include one or more sensors, the sensors may be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and / or a humidity sensor.

[0052] The WTRU 102 may include a full duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for both the uplink (e.g., for transmission) and downlink (e.g., for reception) may be concurrent and / or simultaneous. The full duplex radio may include an interference management unit to reduce and or substantially eliminate self-interference via either hardware (e.g., a choke) or signal processing via a processor (e.g., a separate processor (not shown) or via processor 118). In an embodiment, the WTRU 102 may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the uplink (e.g., for transmission) or the downlink (e.g., for reception)).

[0053] FIG. 1C is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment. As noted above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a. 102b. and 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.

[0054] The RAN 104 may include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment. The eNode-Bs 160a. 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In an embodiment, the eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the eNode-B 160a, for example, may use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102a.

[0055] Each of the eNode-Bs 160a, 160b, and 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the uplink (UL) and / or downlink (DL), and the like. As shown in FIG. 1C, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.

[0056] The CN 106 show n in FIG. 1 C may include a mobility management entity7(MME) 162, a serving gateway (SGW) 164, and a packet data netw ork (PDN) gatew ay (PGW) 166. While each of the foregoing elements are depicted as part of the CN 106, it will be appreciated that any one of these elements may be owned and / or operated by an entity other than the CN operator.

[0057] The MME 162 may be connected to each of the eNode-Bs 160a, 160b, and 160c in the RAN 104 via an SI interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a. 102b, 102c, bearer activation / deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, and the like. The MME 162 may provide a control plane function for switching betw een the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA.

[0058] The SGW 164 may be connected to each of the eNode-Bs 160a. 160b, 160c in the RAN 104 via the S 1 interface. The SGW 164 may generally route and forward user data packets to / from the WTRUs 102a, 102b, 102c. The SGW 164 may perform other functions, such as anchoring user planes during inter-eNode-B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b. 102c, and the like.

[0059] The SGW 164 may be connected to the PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.

[0060] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the CN 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to the other netw orks 112, which may include other wired and / or wireless netw orks that are ow ned and / or operated by other service providers.

[0061] Although the WTRU is described in FIGs. 1 A-1D as a wireless terminal, it is contemplated that in certain representative embodiments that such a terminal may use (e.g., temporarily or permanently) wired communication interfaces with the communication network.

[0062] In representative embodiments, the other netw ork 112 may be a WLAN.

[0063] A WLAN in infrastructure basic service set (BSS) mode may have an access point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may have an accessor an interface to a distribution system (DS) or another type of wired / wireless network that carries traffic into and / or out of the BSS. Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs. Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations. Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA. The traffic between STAs within a BSS may be considered and / or referred to as peer-to-peer traffic. The peer-to-peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS). In certain representative embodiments, the DLS may use an 802. l ie DLS or an 802.1 Iz tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other. The IBSS mode of communication may sometimes be referred to herein as an "ad- hoc" mode of communication.

[0064] When using the 802. 11 ac infrastructure mode of operation or a similar mode of operations, the AP may transmit a beacon on a fixed channel, such as a primary channel. The primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set width via signaling. The primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with the AP. In certain representative embodiments, Carrier sense multiple access with collision avoidance (CSMA / CA) may be implemented, for example in in 802. 11 systems. For CSMA / CA, the STAs (e.g., every STA), including the AP, may sense the primary channel. If the primary channel is sensed / detected and / or determined to be busy by a particular STA, the particular STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS.

[0065] High throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadj acent 20 MHz channel to form a 40 MHz wide channel.

[0066] Very high throughput (VHT) STAs may support 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz wide channels. The 40 MHz, and / or 80 MHz, channels may be formed by combining contiguous 20 MHz channels. A 160 MHz channel may be formed by combining 8 contiguous 20 MHz channels, or by combining two non-contiguous 80 MHz channels, which may be referred to as an 80+80 configuration. For the 80+80 configuration, the data, after channel encoding, may be passed through a segment parser that may divide the data into two streams. Inverse fast fourier transform (IFFT) processing, and time domain processing, may be done on each stream separately. The streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by atransmitting STA. At the receiver of the receiving STA, the above-described operation for the 80+80 configuration may be reversed, and the combined data may be sent to a medium access control (MAC) layer, entity, etc.

[0067] Sub 1 GHz modes of operation are supported by 802.1 laf and 802.11ah. The channel operating bandwidths, and carriers, are reduced in 802.1 laf and 802. 11 ah relative to those used in 802.1 In, and 802. 1 lac. 802.1 laf supports 5 MHz, 10 MHz and 20 MHz bandwidths in the TV white space (TVWS) spectrum, and 802. 11 ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz. and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11 ah may support meter type control / machine-type communications (MTC), such as MTC devices in a macro coverage area. MTC devices may have certain capabilities, for example, limited capabilities including support for (e.g., only support for) certain and / or limited bandwidths. The MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).

[0068] WLAN systems, which may support multiple channels, and channel bandwidths, such as 802.1 In, 802.1 lac, 802.1 laf. and 802. 11 ah, include a channel which may be designated as the primary channel. The primary channel may have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and / or limited by a STA, from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode. In the example of 802.11 ah, the primary' channel may be 1 MHz wide for STAs (e.g., MTC type devices) that support (e.g., only support) a 1 MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz. 16 MHz. and / or other channel bandwidth operating modes. Carrier sensing and / or network allocation vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode), transmitting to the AP, the entire available frequency bands may be considered busy even though a majority of the frequency bands remains idle and may be available.

[0069] In the United States, the available frequency bands, which may be used by 802. 1 lah, are from 902 MHz to 928 MHz. In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidth available for 802. 1 lah is 6 MHz to 26 MHz depending on the country code.

[0070] FIG. ID is a system diagram illustrating the RAN 113 and the CN 115 according to an embodiment. As noted above, the RAN 113 may employ an NR radio technology7to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 113 may also be in communication with the CN 115.

[0071] The RAN 113 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 113 may include any number of gNBs while remaining consistent with an embodiment. The gNBs 180a. 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In an embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology7. For example, gNBs 180a, 180b may utilize beamforming to transmit signals to and / or receive signals from the WTRUs 102a. 102b, 102c. Thus, the gNB 180a, for example, may use multiple antennas to transmit wireless signals to, and / or receive wireless signals from, the WTRU 102a. In an embodiment, the gNBs 180a, 180b, 180c may implement carrier aggregation technology7. For example, the gNB 180a may transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum while the remaining component carriers may be on licensed spectrum. In an embodiment, the gNBs 180a. 180b, 180c may implement Coordinated Multi-Point (CoMP) technology. For example, WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and / or gNB 180c).

[0072] The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b. 180c using transmissions associated with a scalable numerology. For example, OFDM symbol spacing and / or OFDM subcarrier spacing may vary for different transmissions, different cells, and / or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using subframe or transmission time intervals (TTIs) of various or scalable lengths (e.g., including a varying number of OFDM symbols and / or lasting varying lengths of absolute time).

[0073] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c without also accessing other RANs (e.g., such as eNode-Bs 160a, 160b. 160c). In the standalone configuration, WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility7anchor point. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration WTRUs 102a, 102b, 102c may communicate with / connect to gNBs 180a, 180b, 180c while also communicating with / connecting to another RAN such as eNode-Bs 160a, 160b, 160c. For example, WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In the non-standalone configuration, eNode-Bs 160a. 160b, 160c may serve as amobility anchor for WTRUs 102a, 102b, 102c and gNBs 180a, 180b, 180c may provide additional coverage and / or throughput for servicing WTRUs 102a, 102b, 102c.

[0074] Each of the gNBs 180a, 180b. 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and / or DL, support of network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data towards user plane functions (UPFs) 184a, 184b, routing of control plane information towards access and mobility management functions (AMFs) 182a, 182b, and the like. As shown in FIG. ID, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.

[0075] The CN 115 shown in FIG. ID may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF) 183a, 183b, and at least one Data Network (DN) 185a, 185b. While each of the foregoing elements are depicted as part of the CN 1 15, it will be appreciated that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0076] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N2 interface and may serve as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different protocol data unit (PDU) sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of NAS signaling, mobility management, and the like. Network slicing may be used by the AMF 182a, 182b, e.g.. to customize CN support for WTRUs 102a, 102b. 102c based on the types of services being utilized WTRUs 102a, 102b, 102c. For example, different network slices may be established for different use cases such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, sendees for MTC access, and / or the like. The AMF 162 may provide a control plane function for switching between the RAN 1 13 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies such as Wi-Fi.

[0077] The SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 115 via an N11 interface. The SMF 183a. 183b may also be connected to a UPF 184a, 184b in the CN 115 via an N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b and configure the routing of traffic through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions, such as managing and allocating UE IP address, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notifications, and the like. A PDU session type may be IP-based, non-IP based. Ethernet-based, and the like.

[0078] The UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N3 interface, which may provide the WTRUs 102a, 102b. 102c with access to packet-switched networks, such as the Internet 110, e.g.. to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPF 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multihomed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, and the like.

[0079] The CN 115 may facilitate communications with other networks. For example, the CN 115 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) sen' er) that serves as an interface betw een the CN 115 and the PSTN 108. In addition, the CN 115 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and / or wireless networks that are owned and / or operated by other service providers. In an embodiment, the WTRUs 102a, 102b, 102c may be connected to a local Data Network (DN) 185a, 185b through the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.

[0080] In view of FIGs. 1A-1D. and the corresponding description of FIGs. 1A-1D, one or more, or all, of the functions described herein with regard to any of WTRUs 102a-d, base stations 114a- b, eNode-Bs 160a-c, MME 162, SGW 164, PGW 166, gNBs 180a-c, AMFs I82a-b, UPFs 184a-b, SMFs 183a-b, DNs 185a-b, and / or any other elements ) / device(s) described herein, may be performed by one or more emulation elements / devices (not shown). The emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described herein. For example, the emulation devices may be used to test other devices and / or to simulate network and / or WTRU functions.

[0081] The emulation devices may be designed to implement one or more tests of other devices in a lab environment and / or in an operator network environment. For example, the one or more emulation devices may perform the one or more, or all, functions while being fully or partially implemented and / or deployed as part of a wired and / or wireless communication netw ork in order to test other devices within the communication network. The one or more emulation devices may perform the one or more, or all, functions while being temporarily implemented / deployed as part of a wired and / or wireless communication netw ork. The emulation device may be directly coupled to another device for purposes of testing and / or may performing testing using over-the-air w ireless communications.

[0082] The one or more emulation devices may perform the one or more, including all, functions while not being implemented / deployed as part of a wired and / or wireless communication network.For example, the emulation devices may be utilized in a testing scenario in a testing laboratory7and / or a non-deployed (e.g., testing) wired and / or wireless communication network in order to implement testing of one or more components. The one or more emulation devices may be test equipment. Direct RF coupling and / or wireless communications via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation devices to transmit and / or receive data.

[0083] Examples provided herein do not limit applicability of the subject matter to other wireless technologies, e.g., using the same or different principles as may be applicable.

[0084] As explained herein, a wireless transmit / receive unit (WTRU) may be an example of a user equipment (UE). Hence the terms UE and WTRU may be used with equal scope herein.

[0085] Enhanced slice admission control for better energy efficiency and saving, and optimized usage of slices is described herein.

[0086] An R19 Energy Efficiency and Energy Saving study is ongoing. During this study, the two contributions described above have been proposed. According to said proposals, the SMF may reject a PDU Session establishment request based on the overall or UE-specific energy consumption for a slice. While higher cost and / or lower QoS may be allowed for a given PDU Session, other PDU Sessions associated with the same slice might not allow for energy consumption compromises.

[0087] A problem addressed in exemplary implementations described herein is how to optimize the usage of a network slice based on network slice and / or individual UE energy’ consumption related policies.

[0088] Solutions described herein are based on slice-specific energy- policies and analytics. The same logic / solutions apply to UE-specific energy policies and analytics.

[0089] For example, a UE may request a PDU Session Establishment. The EECF may detect that the UE-specific energy threshold is reached and may decide to accept this PDU Session establishment request (assuming its energy7category is ”1” or “2”, described beloyv) and release an existing PDU Session (which is associated with an energy category- “0”). Accordingly, the cost for the UE is increased or the QoS is lowered.

[0090] Similar to optional parameters such as UE-Slice-MBR which characterizes the per UE per Slice Maximum Bit Rate, there can be aUE-Slice-MET, to represent a per-UE, per-Slice Maximum Energy- Consumption / Credit threshold.NSAC based on Energy Category

[0091] An example NSAC procedure based on Energy Category is depicted in FIG. 2. This solution introduces the usage of a new Energy Category associated with a PDU Session.

[0092] In an initial step, during a Registration procedure (e.g., in a Registration Request), not shown in FIG. 2, a UE, UE1, may indicate that it supports the optimized energy usage feature and / or supported Energy Categories. The AMF checks that in the Allowed NSSAI for UE1, at least one slice can be subject to this optimized energy usage feature. Optionally, the list of slices supporting the feature can be provided by the AMF to UE1 (e.g., in a Registration Accept). Another possibility is for the AMF to specify the slice type (SST) which is adapted for energy optimization support (i.e., new types are defined related to energy optimization). The energy-aware UE1 may select a slice based on the energy category support.

[0093] The Energy Category may be specified during a PDU Session Establishment procedure, such as in a PDU Session Establishment request sent from UE1 to the SMF, as shown at step 1 in FIG. 2. The Energy Category' may be set, for example, to allow' higher cost and / or lower QoS (in preference order). Possible Energy Category values are: (0) no compromise. (1) allow higher cost, and / or (2) allow lower QoS (in preference order).

[0094] As an alternative to being included in the PDU Session Establishment request, the Energy Category may be stored in the UDM / UDR for the PDU Session, e.g., linked to the NSSAI and DNN in the UDM. In that case, the SMF retrieves the Energy Category from the UDM during the PDU Session Establishment.

[0095] The PDU Session Establishment Request from UE1 includes an S-NSSA1. After receiving the PDU Session Establishment Request from UE1 for a slice subject to energy consumption admission control, the SMF, at step 2 queries the EECF for slice admission control based on energy' efficiency and saving, such as by sending an Energy Info Req including the S-NSSAI and the Energy Category information to the EECF.

[0096] Optionally at step 3, the EECF may verify with the NSACF if anew PDU Session may be established based on regular admission control. Alternatively, step 3 may be skipped, in which case the EECF does not perform regular slice admission control but rather performs an energy consumption related admission control, with the procedure proceeding to step 4 directly from step 2.

[0097] In step 4, the EECF requests and obtains energy consumption analytics from the NWDAF and the EECF may use the energy' consumption analytics from the NWDAF to determine the current consumption of energy credits by the slice or to estimate or predict how many energy credits may be consumed by a slice if the PDU Session is established.

[0098] In step 5, the EECF determines, based on the current energy7consumption or estimate or predication that was made in step 5, if the overall (or UE) energy credit threshold for a slice may be reached or if the energy credit limit is exceeded and what should be done in this condition. For example, the EECF may determine, based on the Energy Category associated with the PDU Session, if establishment of the PDU Session should be accepted, rejected, and / or accepted on the condition that one or more other PDU Sessions be released or modified. More specifically: i) If the energy credit threshold for a slice is met and the PDU Session Establishment Request specifies Energy Category “0” (no compromise), then the EECF rejects the establishment of the PDU Session. ii) If the energy credit limit is exceeded, then the EECF rejects the establishment of the PDU Session. iii) If the energy credit threshold for a slice is met and the PDU Session Establishment Request specifies Energy Category "1" (allow higher cost) or "2" (allow lower QoS), then the EECF accepts the establishment of the PDU Session.

[0099] The EECF may also interact with the Application Function (AF) to obtain the AF requirements regarding energy usage. The AF may send the energy threshold or energy consumption information to the EECF. This information may be sent to the EECF for a particular UE, group of UEs, application ID, location, or any combination thereof. The EECF may also use the information received from the AF to make a determination whether a requested PDU session should be established or a different PDU session should be released / modified.

[0100] FIG. 2 illustrates two alternative sequence of steps. Alternative A and Alternative B, that the procedure can take after step 5. Alternative A occurs when the EECF rejects the request for PDU Session Establishment and Alternative B occurs when the EECF accepts the request for PDU Session Establishment.

[0101] In step 6a. the EECF replies to the SMF with a slice admission control response (e.g., Energy Info Rsp) that includes a result and an expected follow-up action with respect to the PDU Session Establishment request. The result may be, for example, an indication that the “threshold is met” or that the “limit is exceeded.” The follow-up action in this case may be “reject.” The EECF will reject establishment of the requested PDU Session when the Energy Category in the Energy Information Request (sent by the SMF to the EECF in step 2) is “0” (no compromise) and establishment of the PDU Session would cause the energy consumption threshold to be met, or the Energy Category7is any value and establishment of the PDU Session would cause the energy7consumption limit to be exceeded.

[0102] In step 7a, based on the results from the EECF, the SMF sends to the UE1 a PDU Session Establishment Reject, which includes an indication of cause having a value of “energy threshold met” or “energy credit limit exceeded for the UE / slice.” When the EECF indicates that the PDU session should be rejected, the SMF rejects it, and the EECF and / or the SMF can associate a backoff timer with the attempt to establish a PDU Session. The backoff timer represents how much time needs to pass before the UE can request a PDU session in this slice again, or after which the UE can request a PDU session with an Energy Category that is the same as the Energy Category that was indicated in step 6a. The backoff timer may be based on energy related information (perhaps using analytics), determined by the EECF and NWDAF. This timer may be different for each category’ (UE can have different timers for each category). This timer may also be different for each UE.

[0103] There can be, in addition to the total energy threshold, energy threshold for some energy category’ of the PDU sessions or maximum number of PDU session for some energy categories. For example, the network slice can have a limit of 50 PDU sessions of energy’ category’ "0", and a limit of 200 for the total number of PDU Sessions for all categories. In such an example, the 5GS needs to ensure that the number of PDU sessions of category “0” not exceed 50 in the slice, and that the total number of PDU sessions not exceed 200.

[0104] With respect to Alternative B, in step 6b, the EECF replies to the SMF with a slice admission control response (e.g., Energy Info Rsp) that includes a result and an expected followup action with respect to the PDU Session Establishment request. The result may be, for example, an indication that the “threshold is met.” The follow-up action in this case may be “accept.” The EECF will accept establishment of the requested PDU Session when the Energy Category’ in the Energy’ Information Request (sent by the SMF to the EECF in step 2) is “1” (higher cost) or “2” (lower QoS), and establishment of the PDU Session would cause the energy consumption threshold to be met.

[0105] In step 7b, based on the results from the EECF, the SMF sends to the UE1 a PDU Session Establishment Accept, which includes an indication “energy threshold met - higher cost” if the Energy' Category is “1” in the PDU Session Establishment Request sent from UE1 in step 1, or “energy threshold met - lower QoS.” if the Energy Category is “2” in said PDU Session Establishment Request.

[0106] In addition:

[0107] (1) in the case energy category = "0" (no compromise):The EECF specifies PDU Session IDs and associated action "release" in its reply at step 6b to indicate to the SMF that existing PDU Sessions should be released to allow theestablishment of the new PDU Session. In step 6b, the EECF includes PDU Sessions IDs associated with energy category "0", which do not allow any compromise, i.e., higher cost and / or lower QoS, in the message sent to the SMF.

[0108] (2) in the case energy category= " 1 " (higher cost) or “2” (lower QoS), if the EECF selects other PDU Session(s) to be released:The EECF may determine that one or more PDU Sessions can or need to be released, for energy related slice admission control based on different criteria. For example, if the PDU Session is inactive for a period of time and has the same energy category (" 1" or "2") as the requested PDU session, then it is eligible to be released. The EECF can compare the inactivity time of the eligible PDU sessions (those with a long enough inactivity time) and determine to select PDU sessions with the longest inactivity time, that have been inactive the longest. The EECF can use an average inactivity timer for each PDU session, and instead assess which PDU session to release, if they have a certain energy category (e.g., "1" or "2"), and they have the longest observed average inactivity’ time (where the EECF or another NF keeps track of the inactivity periods for the PDU session and derives an average value for the PDU session, so far). Also, the EECF may keep track for each UE, of the number of times it released a UE's PDU session of a certain category due to energy related slice admission control. In this case, each UE has a score of how- many times their PDU session(s) were released. The EECF can, for example to be fair across UEs, select to release PDU sessions for UEs with a low score at the time of the PDU session request (meaning they had fewer releases related to energy slice admission).

[0109] (3) in the case energy category= "1" or "2", if the EECF selects other PDU Session(s) to be modified:The EECF may determine that one or more PDU Sessions can or need to be modified. For example, the EECF can send a notification to the PCF that the energy that is consumed by a PDU Session needs to be lowered. The PCF may then change the PCC Rules of the PDU Session. The updated PCC Rules will trigger the SMF to generate new QoS Profiles, QoS Rules, and N4 Rules that result in low er energy consumption.

[0110] In step 8b, the SMF decides to trigger the release of existing PDU Session(s). as specified by the EECF and identified by their PDU Session IDs.

[0111] In step 9b, the SMF sends a PDU Session Release with cause value "energy threshold met for the UE / User".

[0112] In step 10b, the SMF decides to trigger the AMF to increase the cost or lower the QoS of a specific S-NSSAI.

[0113] In step l ib, the SMF sends a Slice Energy7Info indication to the AMF requesting to increase the cost or lower the QoS for the S-NSSAI.

[0114] In step 12b, the AMF interacts with the charging system to increase the cost for the S- NSSAI and / or interacts wi th the RAN to lower the QoS.

[0115] The mechanism to release the PDU Sessions may consider that other SMFs may serve the same S-NSSAI, so the SMF may not be able to release other UE PDU Sessions at least directly.

[0116] In this case, the SMF may use alternative A (i.e., reject PDU Session establishment) and at the same time trigger a release procedure to make room for more energy' efficient PDU Session. The cause and a backoff specified on the PDU Session Release may7instruct the UE that it can retry.

[0117] For example, the SMF may identify one or more PDU Sessions that are candidates for being released. The SMF may be configured such that it identifies candidate PDU Sessions for release based on how much time has passed since the PDU Session was last used to send data or the SMF may be configured to identify candidate PDU Sessions for release based on the energy7consumption of the PDU Sessions. The SMF may send the identities of the candidate PDU Sessions to the EECF / NSACF. The EECF / NSACF may receive, from multiple SMFs, identities of PDU Sessions that are candidates for release. The EECF / NSACF may determine which of the candidates should be released. The EECF / NSACF may use information about how much time has passed since the PDU Sessions were last used to send data and the information about the energy7consumption of the PDU Sessions to select which PDU Sessions should be released. The EECF / NSACF may send the identities of the selected PDU Sessions to the AMF so that the AMF can trigger a PDU Session Release procedure for the selected PDU Sessions. The AMF will trigger the PDU Session Release procedures by sending a request to each SMF that serves the selected PDU Session to release the PDU Session.

[0118] In one embodiment, aNSAC procedure based on an Energy Category from an EECF point of view may consider a higher cost or lower QoS with a consideration towards energy consumption as conditions for a solution to either accept or reject a PDU Session establishment request.

[0119] The steps from an EECF point of view include:

[0120] 1. The EECF receives an Energy Info Req including an S-NSSAI and an Energy Category, wherein the Energy Category may be expressed as Category7= ‘'higher cost” or “lower QoS” and energy7consumption = “threshold is met”.

[0121] 2. The EECF verifies with the NSACF if a new PDU Session may be established based on regular admission control.

[0122] 3. The EECF obtains energy consumption analytics from aNWDAF.

[0123] 4. The EECF determines the energy consumption status, i.e. if the energy' credit threshold for a slice is reached or if the energy credit limit is exceeded, and what should be done in this condition.

[0124] 5. The EECF, based on the "energy consumption status" and on the Energy’ Category associated with the PDU Session, accepts the PDU Session establishment on the condition that other PDU Sessions (one or many) are released or modified.

[0125] 6. The EECF replies to the SMF with slice admission control results (e.g. Energy Info Rsp) including a result and expected follow-up action with the PDU Session establishment request. For example, the result may be "threshold is met" and the follow-up action may be "accept".

[0126] In addition, the EECF specifies the PDU Session IDs and associated action "release" or "modify" in its reply to indicate to the SMF that existing PDU Sessions should be released to allow the establishment of the new PDU Session.NSAC Using Duplicated Slices Bundling

[0127] This solution introduces the usage of duplicated slices (i.e., creation of other identical slices) associated with different energy categories. The duplicated slices share common source of energy' credits. For example, whenever a new PDU Session is established or released in either slice, credits are deducted or added from the same source of energy7credits.

[0128] For example, a slice credit limit may be exceeded for a specific S-NSSAI. In this case, the SMF creates two duplicated slices. The first duplicated slice is associated with a higher cost and the second duplicated slice is associated with a lower QoS. PDU Sessions are moved to the appropriate duplicated slice, depending on their energy7category7. Note that both slices may be associated with the same S-NSSAI but they will each have a different Network Slice Instance Identifier (NSI ID).

[0129] The initial slice may not allow any compromise, i.e., PDU Sessions using this slice may be released in priority compared to other slices if the energy' credit threshold is reached or the energy7credit limit is exceeded.

[0130] FIG. 3 illustrates an example method of a NSAC using Duplicated Slices Bundling.

[0131] At step 0, Multiple PDU Sessions are created and associated to an S-NSSAI which is subject to energy efficiency and saving.

[0132] At step 1, UE1 initiates a PDU Session establishment procedure. The AMF sends the PDU Session establishment request to the SMF.

[0133] At step 2, the SMF queries the EECF for slice admission control and energy7efficiency and saving control.

[0134] At step 3, the SMF sends an EnergylnfoReq including S-NSSAI and the energy category for the new PDU Session.

[0135] At step 4, the EECF determines that the slice credit threshold is met:

[0136] a) If the slice is used by PDU sessions associated to different energy categories: i) The EECF duplicates the slice (obtains a new S-NSSAI or NSI ID) (i.e., creates another identical slice) and associates this new slice with another category7(i.e., based on the categories of the existing PDU Sessions); multiple new slices may be created (i.e., one per energy category ). The EECF may determine a new Maximum Slice Credit threshold (the new limit after adding the new slices). This new / updated limit may then be used for slice admission control for the bundled slices. ii) The EECF moves the PDU Sessions to the slice corresponding to the energy category7. Assigning an energy7category7to the original slice and to the new slices may be performed in a way that minimizes signaling for this operation. F or example, if there are 100 PDU sessions of category "0", and 10 PDU sessions of category " 1", 10 PDU sessions of category7"2", then the EECF may determine to keep the 100 PDU sessions with category7"0" in the current slice, and move the 20 other PDU sessions to the two newly created slices, as moving fewer PDU sessions may incur less signaling to the 5GS (PDU session establishment or modification procedures).

[0137] At step 5, the EECF bundles the slices together and informs the NSACF that the slices are bundled i.e., that the policies should be verified considenng the bundled slices as one entity / slice (i.e., the energy consumption limit should be checked against all bundled slices, as if they were a single slice). The EECF uses a message, e.g. a Slice Bundling message, to inform the NSACF and includes the S-NSSAI or NSI ID of the original slice, the new S-NSSAI or NSI ID of the bundled slice, and the associate energy category. This is done for all duplicated slices or the message includes such information for multiple duplicated slices.

[0138] For example, if 20 PDU Sessions are distributed among three bundled slices and the maximum number of PDU sessions for the slice is 20 then any new PDU Session establishment request, regardless of its energy category, should trigger the maximum number of PDU Session reached limit.

[0139] At step 6, the EECF sends a network slice duplication indication to the AMF, including the new S-NSSAI or NSI ID and associated energy7category7, to indicate that a new slice has been created and is bundled to an S-NSSAI or NSI ID for a specific energy category. The original S- NSSAI or NSI ID is still available.

[0140] Additionally (not shown in FIG. 3), the EECF may inform the SMF that slices have been moved to a duplicate slice. The SMF may inform the related UEs (e.g., using PDU Session Modification Req with previous S-NSSAI (or NSI ID), new S-NSSAI (or NSI ID), energy category).

[0141] At step 7, the EECF replies to the SMF using Energy InfoRsp including: the energy' result (e.g., threshold met. limit exceeded); the expected follow-up action (accept - higher cost, accept - lower QoS, reject) with respect to the PDU Session establishment request sent by the UE to the SMF in step 1; and the new S-NSSAI or NSI ID associated to the new duplicated slice.

[0142] At step 8, based on the results from the EECF and on the aforementioned expected followup action, the SMF accepts the PDU session (i.e., sends a PDU Session Establishment Accept to UE1) and includes a new indication e.g.. "threshold met - lower QoS" or "threshold met - higher cost".

[0143] At step 9, based on the results from the EECF (as received at step 7), the SMF triggers the AMF to increase the cost or lower the QoS of the duplicated slice.

[0144] At step 10, the AMF interacts with the charging system to increase the cost for the new S- NSSAI or NSI ID and interacts with the RAN to lower the QoS for the other new S-NSSAI or NSI ID

[0145] Once the duplicated slices are created and the PDU Sessions are associated to the slice corresponding to its energy category', if another PDU Session establishment request is received and the EECF detects that the slice credit limit is exceeded:1) The EECF determines that PDU Sessions from the slice associated with "no compromise" should be released first. If no such slice exists or no PDU Sessions are associated with this slice then no more PDU Session establishment requests are accepted or PDU Sessions from another slice are released (e.g., from lower QoS or from higher cost, depending on the preference specified in the policies).2) The SMF releases the PDU Sessions from the slice, as indicated by the EECF.

[0146] In one embodiment, an NSAC procedure based on the creation of bundles of duplicated slices may be as follows:

[0147] 1. The EECF receives an Energy’ Info Req (from the SMF) including an S-NSSAI or NSI ID and an energy category.

[0148] 2. The EECF determines that the slice credit threshold is met.

[0149] 3. The EECF duplicates the slice and associates this new slice with an energy category' which is different from the energy category specified in the PDU Session establishment request in step I. (i.e., based on the categories of the existing PDU Sessions).

[0150] 4. The EECF moves the existing PDU Sessions to the slice corresponding to their energy7category.

[0151] 5. The EECF bundles the slices together and informs the NSACF that the slices are bundled i.e., that the policies should be verified considering the bundled slices as one entity / slice.

[0152] 6. The EECF sends network slice duplication indication to the AMF, including the new S- NSSAI or NSI ID and associated energy7category7, to indicate that a new slice has been created and is bundled to an S-NSSAI or NSI ID for a specific energy category. The original S-NSSAI or NSI ID is still available.

[0153] 7. The EECF replies to the SMF request (received in step 1) using EnergylnfoRsp including the energy7result (e.g., threshold met, limit exceeded), the expected follow-up action with the PDU Session est. request (accept - higher cost, accept - lower QoS. reject) and the new S- NSSAI or NSI ID associated to the new duplicated slice.

[0154] Although features and elements are provided above in particular combinations, one of ordinary skill in the art will appreciate that each feature or element can be used alone or in any combination with the other features and elements. The present disclosure is not to be limited in terms of the particular embodiments described in this application, which are intended as illustrations of various aspects. Many modifications and variations may be made without departing from its spirit and scope, as will be apparent to those skilled in the art. No element, act, or instruction used in the description of the present application should be construed as critical or essential to the invention unless explicitly provided as such. Functionally equivalent methods and apparatuses within the scope of the disclosure, in addition to those enumerated herein, will be apparent to those skilled in the art from the foregoing descriptions. Such modifications and variations are intended to fall within the scope of the appended claims. The present disclosure is to be limited only by the terms of the appended claims, along with the full scope of equivalents to which such claims are entitled. It is to be understood that this disclosure is not limited to particular methods or systems.

[0155] The foregoing embodiments are discussed, for simplicity, with regard to the terminology and structure of infrared capable devices, i.e.. infrared emitters and receivers. However, the embodiments discussed are not limited to these systems but may be applied to other systems that use other forms of electromagnetic w aves or non-electromagnetic weaves such as acoustic w aves.

[0156] It is also to be understood that the terminology7used herein is for the purpose of describing particular embodiments only, and is not intended to be limiting. As used herein, the term "video" or the term "imagery" may mean any of a snapshot, single image and / or multiple images displayedover a time basis. As another example, when referred to herein, the terms "user equipment" and its abbreviation "UE", the term "remote" and / or the terms "head mounted display" or its abbreviation "HMD" may mean or include (i) a wireless transmit and / or receive unit (WTRU); (ii) any of a number of embodiments of a WTRU; (iii) a wireless-capable and / or wired-capable (e.g., tetherable) device configured with, inter alia, some or all structures and functionality of a WTRU; (iii) a wireless-capable and / or wired-capable device configured with less than all structures and functionality of a WTRU; or (iv) the like. Details of an example WTRU, which may be representative of any WTRU recited herein, are provided herein with respect to FIGs. 1A-1D. As another example, various disclosed embodiments herein supra and infra are described as utilizing a head mounted display. Those skilled in the art will recognize that a device other than the head mounted display may be utilized and some or all of the disclosure and various disclosed embodiments can be modified accordingly without undue experimentation. Examples of such other device may include a drone or other device configured to stream information for providing the adapted reality experience.

[0157] In addition, the methods provided herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted over wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, a read only memory (ROM), a random access memory' (RAM), a register, cache memory’, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD- ROM disks, and digital versatile disks (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer.

[0158] Variations of the method, apparatus and system provided above are possible without departing from the scope of the invention. In view of the wide variety of embodiments that can be applied, it should be understood that the illustrated embodiments are examples only, and should not be taken as limiting the scope of the following claims. For instance, the embodiments provided herein include handheld devices, which may include or be utilized with any appropriate voltage source, such as a battery and the like, providing any appropriate voltage.

[0159] Moreover, in the embodiments provided above, processing platforms, computing systems, controllers, and other devices that include processors are noted. These devices may include at least one Central Processing Unit ("CPU") and memory. In accordance with the practices of persons skilled in the art of computer programming, reference to acts and symbolic representations ofoperations or instructions may be performed by the various CPUs and memories. Such acts and operations or instructions may be referred to as being "executed," "computer executed" or "CPU executed."

[0160] One of ordinary skill in the art will appreciate that the acts and symbolically represented operations or instructions include the manipulation of electrical signals by the CPU. An electrical system represents data bits that can cause a resulting transformation or reduction of the electrical signals and the maintenance of data bits at memory locations in a memory system to thereby reconfigure or otherwise alter the CPU's operation, as well as other processing of signals. The memory locations where data bits are maintained are physical locations that have particular electrical, magnetic, optical, or organic properties corresponding to or representative of the data bits. It should be understood that the embodiments are not limited to the above-mentioned platforms or CPUs and that other platforms and CPUs may support the provided methods.

[0161] The data bits may also be maintained on a computer readable medium including magnetic disks, optical disks, and any other volatile (e.g., Random Access Memory (RAM)) or non-volatile (e.g., Read-Only Memory (ROM)) mass storage system readable by the CPU. The computer readable medium may include cooperating or interconnected computer readable medium, which exist exclusively on the processing system or are distributed among multiple interconnected processing systems that may be local or remote to the processing system. It should be understood that the embodiments are not limited to the above-mentioned memories and that other platforms and memories may support the provided methods.

[0162] In an illustrative embodiment, any of the operations, processes, etc. described herein may be implemented as computer-readable instructions stored on a computer-readable medium. The computer-readable instructions may be executed by a processor of a mobile unit, a network element, and / or any other computing device.

[0163] There is little distinction left between hardware and software implementations of aspects of systems. The use of hardware or software is generally (but not always, in that in certain contexts the choice between hardware and software may become significant) a design choice representing cost versus efficiency tradeoffs. There may be various vehicles by which processes and / or systems and / or other technologies described herein may be effected (e.g., hardware, software, and / or firmware), and the preferred vehicle may vary with the context in which the processes and / or systems and / or other technologies are deployed. For example, if an implementer determines that speed and accuracy are paramount, the implementer may opt for a mainly hardware and / or firmware vehicle. If flexibility is paramount, the implementer may opt for a mainly softwareimplementation. Alternatively, the implementer may opt for some combination of hardware, software, and / or firmware.

[0164] The foregoing detailed description has set forth various embodiments of the devices and / or processes via the use of block diagrams, flowcharts, and / or examples. Insofar as such block diagrams, flowcharts, and / or examples include one or more functions and / or operations, it will be understood by those within the art that each function and / or operation within such block diagrams, flowcharts, or examples may be implemented, individually and / or collectively, by a wide range of hardware, software, firmware, or virtually any combination thereof. In an embodiment, several portions of the subject matter described herein may be implemented via Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), digital signal processors (DSPs), and / or other integrated formats. However, those skilled in the art will recognize that some aspects of the embodiments disclosed herein, in whole or in part, may be equivalently implemented in integrated circuits, as one or more computer programs running on one or more computers (e.g., as one or more programs running on one or more computer systems), as one or more programs running on one or more processors (e.g., as one or more programs running on one or more microprocessors), as firmware, or as virtually any combination thereof, and that designing the circuitry' and / or writing the code for the software and or firmware would be well within the skill of one of skill in the art in light of this disclosure. In addition, those skilled in the art will appreciate that the mechanisms of the subject matter described herein may be distributed as a program product in a variety of forms, and that an illustrative embodiment of the subject matter described herein applies regardless of the particular type of signal bearing medium used to actually carry out the distribution. Examples of a signal bearing medium include, but are not limited to, the following: a recordable type medium such as a floppy disk, a hard disk drive, a CD, a DVD, a digital tape, a computer memory, etc., and a transmission type medium such as a digital and / or an analog communication medium (e.g., a fiber optic cable, a waveguide, a wired communications link, a wireless communication link, etc.).

[0165] Those skilled in the art will recognize that it is common within the art to describe devices and / or processes in the fashion set forth herein, and thereafter use engineering practices to integrate such described devices and / or processes into data processing systems. That is. at least a portion of the devices and / or processes described herein may be integrated into a data processing system via a reasonable amount of experimentation. Those having skill in the art will recognize that a typical data processing system may generally include one or more of a system unit housing, a video display device, a memory such as volatile and non-volatile memory, processors such as microprocessors and digital signal processors, computational entities such as operating systems, drivers, graphicaluser interfaces, and applications programs, one or more interaction devices, such as a touch pad or screen, and / or control systems including feedback loops and control motors (e.g., feedback for sensing position and / or velocity, control motors for moving and / or adjusting components and / or quantities). A typical data processing system may be implemented utilizing any suitable commercially available components, such as those typically found in data computing / communication and / or network computing / communi cation systems.

[0166] The herein described subject matter sometimes illustrates different components included within, or connected with, different other components. It is to be understood that such depicted architectures are merely examples, and that in fact many other architectures may be implemented which achieve the same functionality. In a conceptual sense, any arrangement of components to achieve the same functionality is effectively "associated" such that the desired functionality maybe achieved. Hence, any two components herein combined to achieve a particular functionality may be seen as "associated with" each other such that the desired functionality is achieved, irrespective of architectures or intermedia! components. Likewise, any two components so associated may also be viewed as being "operably connected", or "operably coupled", to each other to achieve the desired functionality, and any two components capable of being so associated may also be viewed as being "operably couplable" to each other to achieve the desired functionality. Specific examples of operably couplable include but are not limited to physically mateable and / or physically interacting components and / or wirelessly interactable and / or wirelessly interacting components and / or logically interacting and / or logically interactable components.

[0167] With respect to the use of substantially any plural and / or singular terms herein, those having skill in the art can translate from the plural to the singular and / or from the singular to the plural as is appropriate to the context and / or application. The various singular / plural permutations may be expressly set forth herein for sake of clarity.

[0168] It will be understood by those within the art that, in general, terms used herein, and especially in the appended claims (e.g., bodies of the appended claims) are generally intended as "open" terms (e.g., the term "including" should be interpreted as "including but not limited to," the term "having" should be interpreted as "having at least," the term "includes" should be interpreted as "includes but is not limited to," etc.). It will be further understood by those within the art that if a specific number of an introduced claim recitation is intended, such an intent will be explicitly recited in the claim, and in the absence of such recitation no such intent is present. For example, where only one item is intended, the term "single" or similar language may be used. As an aid to understanding, the following appended claims and / or the descriptions herein may include usage of the introductory phrases "at least one" and "one or more" to introduce claim recitations. However,the use of such phrases should not be construed to imply that the introduction of a claim recitation by the indefinite articles "a" or "an" limits any particular claim including such introduced claim recitation to embodiments including only one such recitation, even when the same claim includes the introductory phrases "one or more" or "at least one" and indefinite articles such as "a" or "an" (e.g., "a" and / or "an" should be interpreted to mean "at least one" or "one or more"). The same holds true for the use of definite articles used to introduce claim recitations. In addition, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the art will recognize that such recitation should be interpreted to mean at least the recited number (e.g., the bare recitation of "two recitations," without other modifiers, means at least two recitations, or two or more recitations). Furthermore, in those instances where a convention analogous to "at least one of A, B, and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B, and C" would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc.). In those instances where a convention analogous to "at least one of A. B, or C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g.. "a system having at least one of A, B, or C" would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc.). It will be further understood by those within the art that virtually any disjunctive word and / or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to contemplate the possibilities of including one of the terms, either of the terms, or both terms. For example, the phrase "A or B" will be understood to include the possibilities of "A" or "B" or "A and B." Further, the terms "any of' followed by a listing of a plurality of items and / or a plurality of categories of items, as used herein, are intended to include "any of." "any combination of." "any multiple of," and / or "any combination of multiples of' the items and / or the categories of items, individually or in conjunction with other items and / or other categories of items. Moreover, as used herein, the term "set" is intended to include any number of items, including zero. Additionally, as used herein, the term "number" is intended to include any number, including zero. And the term "multiple", as used herein, is intended to be synonymous with "a plurality".

[0169] In addition, where features or aspects of the disclosure are described in terms of Markush groups, those skilled in the art will recognize that the disclosure is also thereby described in terms of any individual member or subgroup of members of the Markush group.

[0170] As will be understood by one skilled in the art, for any and all purposes, such as in terms of providing a written description, all ranges disclosed herein also encompass any and all possible subranges and combinations of subranges thereof. Any listed range can be easily recognized as sufficiently describing and enabling the same range being broken down into at least equal halves, thirds, quarters, fifths, tenths, etc. As a non-limiting example, each range discussed herein may be readily broken down into a lower third, middle third and upper third, etc. As will also be understood by one skilled in the art all language such as "up to," "at least," "greater than," "less than," and the like includes the number recited and refers to ranges which can be subsequently broken down into subranges as discussed above. Finally, as will be understood by one skilled in the art, a range includes each individual member. Thus, for example, a group having 1-3 cells refers to groups having 1, 2, or 3 cells. Similarly, a group having 1-5 cells refers to groups having 1, 2, 3, 4, or 5 cells, and so forth.

[0171] Moreover, the claims should not be read as limited to the provided order or elements unless stated to that effect. In addition, use of the terms "means for" in any claim is intended to invoke 35 U.S.C. §112, * 6 or means-plus-function claim format, and any claim without the terms "means for" is not so intended.

Claims

CLAIMS:What is Claimed:

1. A method performed by an energy efficiency control function (EECF) of a communications network, the method comprising: receiving, from a session management function (SMF), a request for slice admission control based on energy consumption; sending a request to obtain energy consumption analytics from a core network function; receiving energy consumption analytics from the core network function; determining, based on the energy consumption analytics, that a protocol data unit (PDU) session associated with a wireless transmit / receive unit (WTRU) can be established; and sending slice admission control results to the SMF in accordance with determining that the PDU session can be established.

2. The method of claim 1, wherein receiving the request from the SMF for slice admission control includes receiving an energy information request including a single network slice selection assistance information (S-NSSAI).

3. The method of claim 1 or 2, wherein the core network function includes a network data analytics function (NWDAF).

4. The method of claim 1, 2, or 3, wherein determining that the PDU session can be established includes determining that a PDU session request is to be rejected if an energy credit in a network slice is exceeded and the request includes an energy category indication of no compromise.

5. The method of claim 1, 2, or 3, wherein determining that the PDU session can be established includes determining that a PDU session request is to be accepted if an energy credit limit in a network slice is met and the request includes an energy category indication of an allowance of higher energy costs or an allowance of a lower quality of service (QoS).

6. The method of claim 1 , 2, 3, 4, or 5, wherein determining that the PDU session can be established includes determining that at least one other PDU session can be released or modified.

7. The method of claim 6, wherein the slice admission control results include an indication of the at least one other PDU session.

8. The method of claim 1, 2, 3, 4, 5, 6, or 7, comprising: after receiving the request for slice admission control, determining with a network slice admission control function (NSACF) that a new PDU session may be established or not based on regular admission control; and receiving an indication that admission control is to be based on energy efficiency.

9. A non-transient computer-readable storage media having instructions therein, wherein when executed by a computer, cause the method of claim 1, 2, 3, 4, 5, 6, 7, or 8 to be performed.

10. An apparatus comprising circuitry, including a transmitter, a receiver, a processor, and memory', the apparatus configured to: receive, from a session management function (SMF), a request for slice admission control based on energy consumption; send a request to obtain energy consumption analytics from a core network function; receive energy' consumption analytics from the core network function; determine, based on the energy consumption analytics, that a protocol data unit (PDU) session associated with a wireless transmit / receive unit (WTRU) can be established; and send slice admission control results to the SMF in accordance with determining that the PDU session can be established.

11. The apparatus of claim 10, wherein receiving the request from the SMF for slice admission control includes receiving an energy information request including a single network slice selection assistance information (S-NSSAI).

12. The apparatus of claim 10 or 11, wherein the core netw ork function includes a network data analytics function (NWDAF).

13. The apparatus of claim 10, 11, or 12, wherein determining that a PDU session can be established includes determining that a PDU session request is to be rejected if an energy' credit in a network slice is exceeded and the request includes an energy category indication of no compromise.

14. The apparatus of claim 10, 11, or 12, wherein determining that a PDU session can be established includes determining that a PDU session request is to be accepted if an energy credit limit in a network slice is met and the request includes an energy category indication of an allowance of higher energy costs or an allowance of a lower quality of service (QoS).

15. The apparatus of claim 10.

11.

12. 13, or 14, wherein determining that a PDU session can be established includes determining that at least one other PDU session can be released or modified.

16. The apparatus of claim 15, wherein the slice admission control results include an indication of the at least one other PDU session.

17. The apparatus of claim 10, 1 1 , 12, 13, 14, 15, or 1 , wherein the circuitry is configured to: after receiving the request for slice admission control, determine with a network slice admission control function (NSACF) that a new PDU session may be established or not based on regular admission control; and receive an indication that admission control is to be based on energy efficiency.

18. A method performed by an energy efficiency control function (EECF) of a communications network, the method comprising: receiving, from a session management function (SMF). a request for slice admission control, the request for slice admission control relating to establishment of a protocol data unit (PDU) session and being based on an energy7category7; determining that a network slice energy credit threshold is met; duplicating a network slice thereby creating a new network slice; associating the new network slice with an energy category that is different from the energy category7of one or more existing PDU sessions using the netw ork slice; moving at least one of the one or more existing PDU sessions to the new network slice corresponding to the energy category of the new network slice; bundling network slices together and informing a network slice admission control function (NSACF) that the bundled network slices are considered as one slice having an associated energy category7; sending information of the new network slice and the associated energy category to an Access and Mobility Management Function (AMF); andsending a reply to the SMF, the reply including a first indication to accept the establishment of the PDU session or a second indication to reject the establishment of the PDU session.

19. The method of claim 18, wherein associating the new network slice with an energy category that is different from the request for anew PDU session includes associating the new network slice with an energy category7that is based on the energy category7of the one or more existing PDU sessions.

20. The method of claim 18 or 19, wherein the reply to the SMF includes a new single network slice selection assistance information (S-NSSAI) associated with the new network slice.

21. The method of claim 18, 19, or 20, wherein the first indication indicates to accept the establishment of the PDU session with a higher cost or with a lower quality of service (QoS).

22. A non-transient computer-readable storage media having instructions therein, wherein when executed by a computer, cause the method of claim 18, 19, 20. or 21 to be performed.

23. An apparatus comprising circuitry, including a transmitter, a receiver, a processor, and memory, the apparatus configured to: receive, from a session management function (SMF), a request for slice admission control, the request for slice admission control relating to establishment of a protocol data unit (PDU) session and being based on an energy category; determine that a network slice energy credit threshold is met; duplicate a network slice thereby creating a new network slice; associate the new network slice with an energy category that is different from the energy category of one or more existing PDU sessions using the network slice; move at least one of the one or more existing PDU sessions to the new network slice corresponding to the energy category7of the new network slice; bundle network slices together and informing a netw ork slice admission control function (NSACF) that the bundled network slices are considered as one slice having an associated energy category; send information of the new network slice and the associated energy category to an Access and Mobility7Management Function (AMF); andsend a reply to the SMF, the reply including a first indication to accept the establishment of the PDU session or a second indication to reject the establishment of the PDU session.

24. The apparatus of claim 23, wherein associating the new network slice with an energy category that is different from the request for anew PDU session includes associating the new network slice with an energy category7that is based on the energy category7of the one or more existing PDU sessions.

25. The apparatus of claim 23 or 24, wherein the reply to the request for slice admission control includes a new single network slice selection assistance information (S-NSSAI) associated with the new network slice.

26. The apparatus of claim 23, 24, or 25, wherein the first indication indicates to accept the establishment of the PDU session with a higher cost or with a lower quality7of service (QoS).

27. A method performed by a wireless transmit / receive unit (WTRU), the method comprising: sending to a session management function (SMF), a request to establish a protocol data unit(PDU) session, the request including energy7category7information, the energy category7information including an indication to allow the PDU session with a higher cost, or with a lower quality of service (QoS), or with no compromise; and receiving from the SMF a response that the request is rejected or a response that the request is accepted, wherein: the response that the request is rejected includes cause information including an indication that an energy threshold is met or an indication that an energy credit limit is exceeded, and the response that the request is accepted includes an indication that the energy threshold met is met with a higher cost, or an indication that the energy threshold is met with a lower QoS.

28. The method of claim 27, wherein the request includes Single Network Slice Selection Assistance Information (S-NSSAI) indicating at least one slice that can be subject to energy consumption admission control.

29. A wireless transmit / receive unit (WTRU) comprising a transceiver and one or more processors configured to: send to a session management function (SMF), a request to establish a protocol data unit (PDU) session, the request including energy category information, the energy category information including an indication to allow the PDU session with a higher cost, or with a lower quality of service (QoS), or with no compromise; and receive from the SMF a response that the request is rejected or a response that the request is accepted, wherein: the response that the request is rejected includes cause information including an indication that an energy7threshold is met or an indication that an energy7credit limit is exceeded, and the response that the request is accepted includes an indication that the energy threshold met is met with a higher cost, or an indication that the energy threshold is met with a lower QoS.

30. The WTRU of claim 29, wherein the request includes Single Network Slice Selection Assistance Information (S-NSSAI) indicating at least one slice that can be subject to energy consumption admission control.

Images