Enabling energy efficiency and energy saving based on data traffic type in wireless communication networks
By differentiating between FDT and BDT and configuring QoS rules, wireless communication systems optimize energy usage and reduce power consumption, addressing the challenges of high-density user support and flexible scheduling.
Patent Information
- Application Number
- PCT/US2026/025224
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-09
- Filing Date
- 2026-04-24
- Publication Date
- 2026-11-12
AI Technical Summary
Existing wireless communication systems face challenges in achieving energy efficiency and energy saving, particularly in supporting high-density mobile broadband users with lower latency and battery consumption, as well as flexible UE scheduling.
Implementing apparatuses and methods that enable devices to differentiate between Foreground Data Traffic (FDT) and Background Data Traffic (BDT), allowing networks to support energy efficiency and energy saving features by configuring Quality of Service (QoS) rules for data transfers.
Enhances energy efficiency and savings by optimizing network resources based on data traffic type, reducing power consumption and latency, and supporting higher user densities in wireless communication networks.
Smart Images

Figure US2026025224_12112026_PF_FP_ABST
Abstract
Description
ENABLING ENERGY EFFICIENCY AND ENERGY SAVING BASED ON DATA TRAFFIC TYPE IN WIRELESS COMMUNICATION NETWORKSFIELD
[0001] The invention relates to wireless communications, and more particularly to apparatuses, systems, and methods for enabling energy efficiency and energy saving.DESCRIPTION OF THE RELATED ART
[0002] Wireless communication systems are rapidly growing in usage. In recent years, wireless devices such as smart phones and tablet computers have become increasingly sophisticated. In addition to supporting telephone calls, many mobile devices now provide access to the internet, email, text messaging, and navigation using the global positioning system (GPS), and are capable of operating sophisticated applications that utilize these functionalities. Additionally, there exist numerous different wireless communication technologies and standards.
[0003] Long Term Evolution (LTE), also referred to as the Evolved Universal Terrestrial Radio Access Network (E-UTRAN, has been the technology of choice for the majority of wireless network operators worldwide, providing mobile broadband data and high-speed Internet access to their subscriber base. LTE was first proposed in 2004 and was first standardized in 2008. Since then, as usage of wireless communication systems has expanded exponentially, demand has risen for wireless network operators to support a higher capacity for a higher density of mobile broadband users. Thus, in 2015 study of a new radio access technology began and, in 2017, a first release of the Third Generation Partnership Project (3GPP) Fifth Generation New Radio (5G NR) was standardized. 5th generation mobile networks or 5th generation wireless systems, referred to as 3GPP NR (otherwise known as 5G-NR or NR-5G for 5G New Radio, also simply referred to as NR). NR proposes a higher capacity for a higher density of mobile broadband users, also supporting device-to-device, ultra-reliable, and massive machine communications, as well as lower latency and lower battery consumption, than LTE standards.
[0004] 5G-NR provides, as compared to LTE, a higher capacity for a higher density of mobile broadband users, while also supporting device-to-device, ultra-reliable, and massivemachine type communications with lower latency and / or lower battery consumption. Further, NR may allow for more flexible UE scheduling as compared to current LTE. Consequently, efforts are being made in ongoing developments of 5G-NR to take advantage of higher throughputs possible at higher frequencies.
[0005] One aspect of wireless communication systems, e.g., systems for NR cellular wireless communications, is energy efficiency and energy saving.SUMMARY
[0006] Embodiments relate to wireless communications, and more particularly to apparatuses, systems, and methods to enable energy efficiency and energy saving.
[0007] Embodiments relate to wireless communications, and more particularly to apparatuses, systems, and methods for a device configured for communicating in a wireless communication network, comprising: one or more processors, coupled to a memory, configured to: receive a request indicating whether a data request type is a Foreground Data Traffic (FDT) or a Background Data Traffic (BDT); send an accept message indicating that the network supports energy efficiency and energy saving features; receive a packet data unit (PDU) session establishment request message; and send a packet data unit (PDU) session establishment accept message including Quality of Service (QoS) rules for a data transfer.
[0008] Other embodiments relate to a user equipment comprising: one or more processors, coupled to a memory, configured to: send a request indicating whether a data request type is a Foreground Data Traffic (FDT) or a Background Data Traffic (BDT); receive an accept message indicating that the network supports energy efficiency and energy saving features; send a packet data unit (PDU) session establishment request message; and receive a packet data unit (PDU) session establishment accept message including Quality of Service (QoS) rules for a data transfer.
[0009] The techniques described herein may be implemented in and / or used with a number of different types of devices, including but not limited to base stations, access points, cellular phones, tablet computers, wearable computing devices, portable media players, vehicles, and any of various other computing devices.
[0010] This Summary is intended to provide a brief overview of some of the subjectmatter described in this document. Accordingly, it will be appreciated that the abovedescribed features are merely examples and should not be construed to narrow the scope or spirit of the subject matter described herein in any way. Other features, aspects, and advantages of the subject matter described herein will become apparent from the following Detailed Description, Figures, and Claims.BRIEF DESCRIPTION OF THE DRAWINGS
[0011] A better understanding of the present subject matter can be obtained when the following detailed description of various embodiments is considered in conjunction with the following drawings, in which:
[0012] Figure 1A illustrates an example wireless communication system according to some embodiments.
[0013] Figure IB illustrates an example of a base station and an access point in communication with a user equipment (UE) device, according to some embodiments.
[0014] Figure 2 illustrates an example block diagram of a base station, according to some embodiments.
[0015] Figure 3 illustrates an example block diagram of a server according to some embodiments.
[0016] Figure 4 illustrates an example block diagram of a UE according to some embodiments.
[0017] Figure 5 illustrates an example block diagram of cellular communication circuitry, according to some embodiments.
[0018] Figure 6A illustrates an example of a 5G network architecture that incorporates both 3GPP (e.g., cellular) and non-3GPP (e.g., non-cellular) access to the 5G CN, according to some embodiments.
[0019] Figure 6B illustrates an example of a 5G network architecture that incorporates both dual 3GPP (e.g., LTE and 5G NR) access and non-3GPP access to the 5G CN, according to some embodiments.
[0020] Figure 7 illustrates an example of a baseband processor architecture for a UE, according to some embodiments.
[0021] Figure 8 illustrates an example of a device in accordance with some embodiments.
[0022] Figure 9 illustrates an example baseband circuitry in accordance with some embodiments.
[0023] Figure 10 illustrates an example of a control plane protocol stack in accordance with some embodiments.
[0024] Figures 11A-11B illustrate an example of a system including an Energy Information Function (EIF) in accordance with some embodiments.
[0025] Figure 12 illustrates an example of Energy Efficiency and Energy Saving (EEES) policy selection and data transfer according to some embodiments.
[0026] Figures 13A-13B illustrate an example of Energy Efficiency and Energy Saving (EEES) data transfer according to some embodiments.
[0027] Figures 14A-14B illustrate an example of Energy Efficiency and Energy Saving (EEES) for roaming cases according to some embodiments.
[0028] Figure 15 illustrates a block diagram of an example of a method for enabling energy efficiency and energy saving.
[0029] Figure 16 illustrates a block diagram of an example of a method for enabling energy efficiency and energy saving.
[0030] While the features described herein may be susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and are herein described in detail. It should be understood, however, that the drawings and detailed description thereto are not intended to be limiting to the particular form disclosed, but on the contrary, the intention is to cover all modifications, equivalents and alternatives falling within the spirit and scope of the subject matter as defined by the appended claims.DETAILED DESCRIPTION
[0031] The following is a glossary of terms used in this disclosure:
[0032] Memory Medium - Any of various types of non-transitory memory devices orstorage devices. The term “memory medium” is intended to include an installation medium, e.g., a CD- ROM, floppy disks, or tape device; a computer system memory or randomaccess memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; a non-volatile memory such as a Flash, magnetic media, e.g., a hard drive, or optical storage; registers, or other similar types of memory elements, etc. The memory medium may include other types of non-transitory memory as well or combinations thereof. In addition, the memory medium may be located in a first computer system in which the programs are executed, or may be located in a second different computer system which connects to the first computer system over a network, such as the Internet. In the latter instance, the second computer system may provide program instructions to the first computer for execution. The term “memory medium” may include two or more memory mediums which may reside in different locations, e.g., in different computer systems that are connected over a network. The memory medium may store program instructions (e.g., embodied as computer programs) that may be executed by one or more processors.
[0033] Carrier Medium - a memory medium as described above, as well as a physical transmission medium, such as a bus, network, and / or other physical transmission medium that conveys signals such as electrical, electromagnetic, or digital signals.
[0034] Programmable Hardware Element - includes various hardware devices comprising multiple programmable function blocks connected via a programmable interconnect. Examples include FPGAs (Field Programmable Gate Arrays), PLDs (Programmable Logic Devices), FPOAs (Field Programmable Object Arrays), and CPLDs (Complex PLDs). The programmable function blocks may range from fine grained (combinatorial logic or look up tables) to coarse grained (arithmetic logic units or processor cores). A programmable hardware element may also be referred to as "reconfigurable logic”.
[0035] Computer System (or Computer) - any of various types of computing or processing systems, including a personal computer system (PC), mainframe computer system, workstation, network appliance, Internet appliance, personal digital assistant (PDA), television system, grid computing system, or other device or combinations of devices. In general, the term "computer system" can be broadly defined to encompass any device (or combination of devices) having at least one processor that executes instructions from a memory medium.
[0036] User Equipment (UE) (or “UE Device”) - any of various types of computer systems devices which are mobile or portable and which performs wireless communications. Examples of UE devices include mobile telephones or smart phones (e.g., iPhone™, Android™-based phones), portable gaming devices (e.g., Nintendo DS™, PlayStation Portable™, Gameboy Advance™, iPhone™), laptops, wearable devices (e.g., smart watch, smart glasses), PDAs, portable Internet devices, music players, data storage devices, other handheld devices, unmanned aerial vehicles (UAVs) (e.g., drones), UAV controllers (UACs), and so forth. In general, the term “UE” or “UE device” can be broadly defined to encompass any electronic, computing, and / or telecommunications device (or combination of devices) which is easily transported by a user and capable of wireless communication.
[0037] Base Station - The temr "Base Station" has the full breadth of its ordinary meaning, and at least includes a wireless communication station installed at a fixed location and used to communicate as part of a wireless telephone system or radio system.
[0038] Processing Element (or Processor) - refers to various elements or combinations of elements that are capable of performing a function in a device, such as a user equipment or a cellular network device. Processing elements may include, for example: processors and associated memory, portions or circuits of individual processor cores, entire processor cores, processor arrays, circuits such as an ASIC (Application Specific Integrated Circuit), programmable hardware elements such as a field programmable gate array (FPGA), as well any of various combinations of the above.
[0039] Channel - a medium used to convey information from a sender (transmitter) to a receiver. It should be noted that since characteristics of the term “channel” may differ according to different wireless protocols, the term “channel” as used herein may be considered as being used in a manner that is consistent with the standard of the type of device with reference to which the term is used. In some standards, channel widths may be variable (e.g., depending on device capability, band conditions, etc.). For example, LTE may support scalable channel bandwidths from 1.4 MHz to 20MHz. In contrast, WLAN channels may be 22MHz wide while Bluetooth channels may be IMhz wide. Other protocols and standards may include different definitions of channels. Furthermore, some standards may define and use multiple types of channels, e.g., different channels for uplink or downlink and / or different channels for different uses such as data, control information,etc.
[0040] Band - The term "band" has the full breadth of its ordinary meaning, and at least includes a section of spectrum (e.g., radio frequency spectrum) in which channels are used or set aside for the same purpose.
[0041] Wi-Fi - The term "Wi-Fi" (or WiFi) has the full breadth of its ordinary meaning, and at least includes a wireless communication network or RAT that is serviced by wireless LAN (WLAN) access points and which provides connectivity through these access points to the Internet. Most modern Wi-Fi networks (or WLAN networks) are based on IEEE 802.11 standards and are marketed under the name “Wi-Fi”. A Wi-Fi (WLAN) network is different from a cellular network.
[0042] 3GPP Access - refers to accesses (e.g., radio access technologies) that are specified by the Third Generation Partnership Project (3GPP) standards. These accesses include, but are not limited to, GSM / GPRS, LTE, LTE-A, and / or 5G NR. In general, 3GPP access refers to various types of cellular access technologies.
[0043] Non-3GPP Access - refers any accesses (e.g., radio access technologies) that are not specified by 3GPP standards. These accesses include, but are not limited to, WiMAX, CDMA2000, Wi-Fi, WLAN, and / or fixed networks. Non-3GPP accesses may be split into two categories, "trusted" and "untrusted" : Trusted non-3GPP accesses can interact directly with an evolved packet core (EPC) and / or a 5G core (5GC) whereas untrusted non-3GPP accesses interwork with the EPC / 5GC via a network entity, such as an Evolved Packet Data Gateway and / or a 5G NR gateway. In general, non-3GPP access refers to various types on non-cellular access technologies.
[0044] Automatically - refers to an action or operation performed by a computer system (e.g., software executed by the computer system) or device (e.g., circuitry, programmable hardware elements, ASICs, etc.), without user input directly specifying or performing the action or operation. Thus, the term "automatically" is in contrast to an operation being manually performed or specified by the user, where the user provides input to directly perform the operation. An automatic procedure may be initiated by input provided by the user, but the subsequent actions that are performed “automatically” are not specified by the user, i.e., are not performed “manually”, where the user specifies each action to perform. For example, a user filling out an electronic form by selecting each field and providing input specifying information (e.g., by typing information, selecting checkboxes, radio selections, etc.) is filling out the form manually, even though the computer system can update the form in response to the user actions. The form may be automatically filled out by the computer system where the computer system (e.g., software executing on the computer system) analyzes the fields of the form and fills in the form without any user input specifying the answers to the fields. As indicated above, the user may invoke the automatic filling of the form, but is not involved in the actual filling of the form (e.g., the user is not manually specifying answers to fields but rather they are being automatically completed). The present specification provides various examples of operations being automatically performed in response to actions the user has taken.
[0045] Approximately - refers to a value that is almost correct or exact. For example, approximately may refer to a value that is within 1 to 10 percent of the exact (or desired) value. It should be noted, however, that the actual threshold value (or tolerance) may be application dependent. For example, in some embodiments, “approximately” may mean within 0.1% of some specified or desired value, while in various other embodiments, the threshold may be, for example, 2%, 3%, 5%, and so forth, as desired or as used by the particular application.
[0046] Concurrent - refers to parallel execution or performance, where tasks, processes, or programs are performed in an at least partially overlapping manner. For example, concurrency may be implemented using “strong” or strict parallelism, where tasks are performed (at least partially) in parallel on respective computational elements, or using “weak parallelism”, where the tasks are performed in an interleaved manner, e.g., by time multiplexing of execution threads.
[0047] Various components may be described as “configured to” perform a task or tasks. In such contexts, “configured to” is a broad recitation generally meaning “having structure that” performs the task or tasks during operation. As such, the component can be configured to perform the task even when the component is not currently performing that task (e.g., a set of electrical conductors may be configured to electrically connect a module to another module, even when the two modules are not connected). In some contexts, “configured to” may be a broad recitation of structure generally meaning “having circuitry that” performs the task or tasks during operation. As such, the component can be configured to perform the task even when the component is not currently on. In general, the circuitry that forms the structure corresponding to “configured to” may include hardware circuits.
[0048] Various components may be described as performing a task or tasks, for convenience in the description. Such descriptions should be interpreted as including the phrase “configured to.” Reciting a component that is configured to perform one or more tasks is expressly intended not to invoke 35 U.S.C. § 112(f) interpretation for that component.Figures 1A and IB: Communication Systems
[0049] Figure 1A illustrates a simplified example wireless communication system, according to some embodiments. It is noted that the system of Figure 1 A is merely one example of a possible system, and that features of this disclosure may be implemented in any of various systems, as desired.
[0050] As shown, the example wireless communication system includes a base station 102 A which communicates over a transmission medium with one or more user equipment 106A, 106B, etc., through 106N. Each of the user equipment devices may be referred to herein as a “user equipment” (UE). Thus, the user equipment 106 devices are referred to as UEs or UE devices.
[0051] The base station (BS) 102A may be a base transceiver station (BTS) or cell site (a “cellular base station”) and may include hardware that enables wireless communication with the UEs 106A through 106N.
[0052] The communication area (or coverage area) of the base station may be referred to as a “cell.” The base station 102A and the UEs 106 may be configured to communicate over the transmission medium using any of various radio access technologies (RATs), also referred to as wireless communication technologies, or telecommunication standards, such as GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, LTE-Advanced (LTE-A), 5G new radio (5G NR), HSPA, 3GPP2 CDMA2000 (e.g., IxRTT, IxEV-DO, HRPD, eHRPD), etc. Note that if the base station 102A is implemented in the context of LTE (E-UTRAN), it may alternately be referred to as an 'eNodeB' or ‘eNB’. Note that if the base station 102A is implemented in the context of 5G NR, it may alternately be referred to as ‘gNodeB’ or ‘gNB’.
[0053] As shown, the base station 102A may also be equipped to communicate with a network (NW) 100 (e.g., a core network of a cellular service provider, a telecommunicationnetwork such as a public switched telephone network (PSTN), and / or the Internet, among various possibilities). Thus, the base station 102A may facilitate communication between the user devices and / or between the user devices and the network 100. In particular, the cellular base station 102 A may provide UEs 106 with various telecommunication capabilities, such as voice, SMS and / or data services.
[0054] Base station 102A and other similar base stations (such as base stations 102B...102N) operating according to the same or a different cellular communication standard may thus be provided as a network of cells, which may provide continuous or nearly continuous overlapping service to UEs 106A-N and similar devices over a geographic area via one or more cellular communication standards.
[0055] Thus, while base station 102A may act as a “serving cell” for UEs 106A-N as illustrated in Figure 1A, each UE 106 may also be capable of receiving signals from (and possibly within communication range of) one or more other cells (which might be provided by base stations 102B-N and / or any other base stations), which may be referred to as “neighboring cells”. Such cells may also be capable of facilitating communication between user devices and / or between user devices and the network 100. Such cells may include “macro” cells, “micro” cells, “pico” cells, and / or cells which provide any of various other granularities of service area size. For example, base stations 102A-B illustrated in Figure 1A might be macro cells, while base station 102N might be a micro cell. Other configurations are also possible.
[0056] In some embodiments, base station 102A may be a next generation base station, e.g., a 5G New Radio (5G NR) base station, or “gNB”. In some embodiments, a gNB may be connected to a legacy evolved packet core (EPC) network and / or to a NR core (NRC) network. In addition, a gNB cell may include one or more transmission and reception points (TRPs). In addition, a UE capable of operating according to 5G NR may be connected to one or more TRPs within one or more gNBs.
[0057] Note that a UE 106 may be capable of communicating using multiple wireless communication standards. For example, the UE 106 may be configured to communicate using a wireless networking (e.g., Wi-Fi) and / or peer-to-peer wireless communication protocol (e.g., Bluetooth, Wi-Fi peer-to-peer, etc.) in addition to at least one cellular communication protocol (e.g., GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, LTE-A, 5G NR, HSPA, 3GPP2 CDMA2000 (e.g.,IxRTT, IxEV-DO, HRPD, eHRPD), etc.). The UE 106 may also or alternatively be configured to communicate using one or more global navigational satellite systems (GNSS, e.g., GPS or GLONASS), one or more mobile television broadcasting standards (e.g., ATSC-M / H or DVB-H), and / or any other wireless communication protocol, if desired. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible.
[0058] Figure IB illustrates user equipment 106 (e.g., one of the devices 106A through 106N) in communication with a base station 102 and an access point 112, according to some embodiments. The UE 106 may be a device with both cellular communication capability and non-cellular communication capability (e.g., Bluetooth, Wi-Fi, and so forth) such as a mobile phone, a hand- held device, a computer or a tablet, or virtually any type of wireless device.
[0059] The UE 106 may include a processor that is configured to execute program instructions stored in memory. The UE 106 may perform any of the method embodiments described herein by executing such stored instructions. Alternatively, or in addition, the UE 106 may include a programmable hardware element such as an FPGA (field -programmable gate array) that is configured to perform any of the method embodiments described herein, or any portion of any of the method embodiments described herein.
[0060] The UE 106 may include one or more antennas for communicating using one or more wireless communication protocols or technologies. In some embodiments, the UE 106 may be configured to communicate using, for example, CDMA2000 (IxRTT I I EV-DO I HRPD / eHRPD), LTE / LTE- Advanced, or 5G NR using a single shared radio and / or GSM, LTE, LTE- Advanced, or 5G NR using the single shared radio. The shared radio may couple to a single antenna, or may couple to multiple antennas (e.g., for MIMO) for performing wireless communications. In general, a radio may include any combination of a baseband processor, analog RF signal processing circuitry (e.g., including filters, mixers, oscillators, amplifiers, etc.), or digital processing circuitry (e.g., for digital modulation as well as other digital processing). Similarly, the radio may implement one or more receive and transmit chains using the aforementioned hardware. For example, the UE 106 may share one or more parts of a receive and / or transmit chain between multiple wireless communication technologies, such as those discussed above.
[0061] In some embodiments, the UE 106 may include separate transmit and / or receivechains (e.g., including separate antennas and other radio components) for each wireless communication protocol with which it is configured to communicate. As a further possibility, the UE 106 may include one or more radios which are shared between multiple wireless communication protocols, and one or more radios which are used exclusively by a single wireless communication protocol. For example, the UE 106 might include a shared radio for communicating using either of LTE (E-UTRAN) or 5G NR (or LTE or I RTTor LTE or GSM), and separate radios for communicating using each of Wi-Fi and Bluetooth. Other configurations are also possible.2: Block Diagram of a Base Station
[0062] Figure 2 illustrates an example block diagram of a base station 102, according to some embodiments. It is noted that the base station of Figure 2 is merely one example of a possible base station. As shown, the base station 102 may include processor(s) 204 which may execute program instructions for the base station 102. The processor(s) 204 may also be coupled to memory management unit (MMU) 240, which may be configured to receive addresses from the processor(s) 204 and translate those addresses to locations in memory (e.g., memory 260 and read only memory (ROM) 250) or to other circuits or devices.
[0063] The base station 102 may include at least one network port 270. The network port 270 may be configured to couple to a telephone network and provide a plurality of devices, such as 106, access to the telephone network as described above in Figures 1A-1B.
[0064] The network port 270 (or an additional network port) may also or alternatively be configured to couple to a cellular network, e.g., a core network of a cellular service provider. The core network may provide mobility related services and / or other services to a plurality of devices, such as UE 106. In some cases, the network port 270 may couple to a telephone network via the core network, and / or the core network may provide a telephone network (e.g., among other UE devices serviced by the cellular service provider).
[0065] In some embodiments, base station 102 may be a next generation base station, e.g., a 5G New Radio (5G NR) base station, or “gNB". In such embodiments, base station 102 may be connected to a legacy evolved packet core (EPC) network and / or to a NR core (NRG) network. In addition, base station 102 may be considered a 5G NR cell and mayinclude one or more transmission and reception points (TRPs). In addition, a UE capable of operating according to 5G NR may be connected to one or more TRPs within one or more gNBs.
[0066] The base station 102 may include at least one antenna 234, and possibly multiple antennas. The at least one antenna 234 may be configured to operate as a wireless transceiver and may be further configured to communicate with UE 106 via radio 230. The antenna 234 communicates with the radio 230 via communication chain 232. Communication chain 232 may be a receive chain, a transmit chain or both. The radio 230 may be configured to communicate via various wireless communication standards, including, but not limited to, 5G NR, LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, etc.
[0067] The base station 102 may be configured to communicate wirelessly using multiple wireless communication standards. In some instances, the base station 102 may include multiple radios, which may enable the base station 102 to communicate according to multiple wireless communication technologies. For example, as one possibility, the base station 102 may include an LTE radio for performing communication according to LTE as well as a 5G NR radio for performing communication according to 5G NR. In such a case, the base station 102 may be capable of operating as both an LTE base station and a 5G NR base station. As another possibility, the base station 102 may include a multi-mode radio which is capable of performing communications according to any of multiple wireless communication technologies (e.g., 5G NR and Wi-Fi, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc.).
[0068] As described further subsequently herein, the BS 102 may include hardware and software components for implementing or supporting implementation of features described herein. The processor 204 of the base station 102 may be configured to implement or support implementation of part or all of the methods described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, the processor 204 may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit), or a combination thereof. Alternatively (or in addition) the processor 204 of the BS 102, in conjunction with one or more of the other components 230, 232, 234, 240, 250, 260, 270 may be configured to implement or support implementation of part or all of the features described herein.
[0069] In addition, as described herein, processor(s) 204 may be comprised of one or more processing elements. In other words, one or more processing elements may be included in processor(s) 204. Thus, processor(s) 204 may include one or more integrated circuits (ICs) that are configured to perform the functions of processor(s) 204. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processor(s) 204.
[0070] Further, as described herein, radio 230 may be comprised of one or more processing elements. In other words, one or more processing elements may be included in radio 230. Thus, radio 230 may include one or more integrated circuits (ICs) that are configured to perform the functions of radio 230. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of radio 230.Figure 3: Block Diagram of a Server
[0071] Figure 3 illustrates an example block diagram of a server 104, according to some embodiments. It is noted that the server of Figure 3 is merely one example of a possible server. As shown, the server 104 may include processor(s) 344 which may execute program instructions for the server 104. The processor(s) 344 may also be coupled to memory management unit (MMU) 374, which may be configured to receive addresses from the processor(s) 344 and translate those addresses to locations in memory (e.g., memory 364 and read only memory (ROM) 354) or to other circuits or devices.
[0072] The server 104 may be configured to provide a plurality of devices, such as base station 102 and UE 106 access to network functions, e.g., as further described herein.
[0073] In some embodiments, the server 104 may be part of a radio access network, such as a 5G New Radio (5G NR) radio access network. In some embodiments, the server 104 may be connected to a legacy evolved packet core (EPC) network and / or to a NR core (NRC) network.
[0074] As described further subsequently herein, the server 104 may include hardware and software components for implementing or supporting implementation of features described herein. The processor 344 of the server 104 may be configured to implement or support implementation of part or all of the methods described herein, e.g., by executingprogram instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, the processor 344 may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit), or a combination thereof. Alternatively (or in addition) the processor 344 of the server 104, in conjunction with one or more of the other components 354, 364, and / or 374 may be configured to implement or support implementation of part or all of the features described herein.
[0075] In addition, as described herein, processor(s) 344 may be comprised of one or more processing elements. In other words, one or more processing elements may be included in processor(s) 344. Thus, processor(s) 344 may include one or more integrated circuits (ICs) that are configured to perform the functions of processor(s) 344. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processor(s) 344.Figure 4: Block Diagram of a UE
[0076] Figure 4 illustrates an example simplified block diagram of a communication device 405, according to some embodiments. It is noted that the block diagram of the communication device of Figure 4 is only one example of a possible communication device. According to embodiments, communication device 405 may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet, an unmanned aerial vehicle (UAV), a UAV controller (UAC) and / or a combination of devices, among other devices. As shown, the communication device 405 may include a set of components (SOC) 400 configured to perform core functions. For example, this set of components may be implemented as a system on chip (also referred to as a SOC), which may include portions for various purposes. Alternatively, this set of components 400 may be implemented as separate components or groups of components for the various purposes. The set of components 400 may be coupled (e.g., communicatively; directly or indirectly) to various other circuits of the communication device 405.
[0077] For example, the communication device 405 may include various types of memory (e.g., including NAND flash memory 410), an input / output interface such asconnector I / F 420 (e.g., for connecting to a computer system; dock; charging station; input devices, such as a microphone, camera, keyboard; output devices, such as speakers; etc.), the display 460, which may be integrated with or external to the communication device 405, and cellular communication circuitry 430 such as for 5G NR, LTE, GSM, etc., and short to medium range wireless communication circuitry 429 (e.g., Bluetooth™ and WLAN circuitry). In some embodiments, communication device 405 may include wired communication circuitry (not shown), such as a network interface card, e.g., for Ethernet.
[0078] The cellular communication circuitry 430 may couple (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas 435 and 436 as shown. The short to medium range wireless communication circuitry 429 may also couple (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas 437 and 438 as shown. Alternatively, the short to medium range wireless communication circuitry 429 may couple (e.g., communicatively; directly or indirectly) to the antennas 435 and 436 in addition to, or instead of, coupling (e.g., communicatively; directly or indirectly) to the antennas 437 and 438. The short to medium range wireless communication circuitry 429 and / or cellular communication circuitry 430 may include multiple receive chains and / or multiple transmit chains for receiving and / or transmitting multiple spatial streams, such as in a multiple-input multiple output (MIMO) configuration.
[0079] In some embodiments, as further described below, cellular communication circuitry 430 may include dedicated receive chains (including and / or coupled to, e.g., communicatively; directly or indirectly, dedicated processors and / or radios) for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G NR). In addition, in some embodiments, cellular communication circuitry 430 may include a single transmit chain that may be switched between radios dedicated to specific RATs. For example, a first radio may be dedicated to a first RAT, e.g., LTE, and may be in communication with a dedicated receive chain and a transmit chain shared with an additional radio, e.g., a second radio that may be dedicated to a second RAT, e.g., 5G NR, and may be in communication with a dedicated receive chain and the shared transmit chain.
[0080] The communication device 405 may also include and / or be configured for use with one or more user interface elements. The user interface elements may include any of various elements, such as display 460 (which may be a touchscreen display), a keyboard (which may be a discrete keyboard or may be implemented as part of a touchscreen display),a mouse, a microphone and / or speakers, one or more cameras, one or more buttons, and / or any of various other elements capable of providing information to a user and / or receiving or interpreting user input.
[0081] The communication device 405 may further include one or more smart cards 445 that include SIM (Subscriber Identity Module) functionality, such as one or more UICC(s) (Universal Integrated Circuit Card(s)) cards 445. Note that the term “SIM” or “SIM entity” is intended to include any of various types of SIM implementations or SIM functionality, such as the one or more UICC(s) cards 445, one or more eUICCs, one or more eSIMs, either removable or embedded, etc. In some embodiments, the communication device 405 may include at least two SIMs. Each SIM may execute one or more SIM applications and / or otherwise implement SIM functionality. Thus, each SIM may be a single smart card that may be embedded, e.g., may be soldered onto a circuit board in the communication device 405, or each SIM may be implemented as a removable smart card. Thus, the SIM(s) may be one or more removable smart cards (such as UICC cards, which are sometimes referred to as “SIM cards”), and / or the SIMs may be one or more embedded cards (such as embedded UICCs (eUICCs), which are sometimes referred to as “eSIMs” or “eSIM cards”). In some embodiments (such as when the SIM(s) include an eUICC), one or more of the SIM(s) may implement embedded SIM (eSIM) functionality; in such an embodiment, a single one of the SIM(s) may execute multiple SIM applications. Each of the SIMs may include components such as a processor and / or a memory; instructions for performing SIM / eSIM functionality may be stored in the memory and executed by the processor. In some embodiments, the communication device 405 may include a combination of removable smart cards and fixed / non-removable smart cards (such as one or more eUICC cards that implement eSIM functionality), as desired. For example, the communication device 405 may comprise two embedded SIMs, two removable SIMs, or a combination of one embedded SIMs and one removable SIMs. Various other SIM configurations are also contemplated.
[0082] As noted above, in some embodiments, the communication device 405 may include two or more SIMs. The inclusion of two or more SIMs in the communication device 405 may allow the communication device 405 to support two different telephone numbers and may allow the communication device 405 to communicate on corresponding two or more respective networks. For example, a first SIM may support a first RAT such as LTE, and a second SIM support a second RAT such as 5G NR. Other implementations andRATs are of course possible. In some embodiments, when the communication device 405 comprises two SIMs, the communication device 405 may support Dual SIM Dual Active (DSDA) functionality. The DSDA functionality may allow the communication device 405 to be simultaneously connected to two networks (and use two different RATs) at the same time, or to simultaneously maintain two connections supported by two different SIMs using the same or different RATs on the same or different networks. The DSDA functionality may also allow the communication device 405 to simultaneously receive voice calls or data traffic on either phone number. In certain embodiments the voice call may be a packet switched communication. In other words, the voice call may be received using voice over LTE (VoLTE) technology and / or voice over NR (VoNR) technology. In some embodiments, the UE 106 may support Dual SIM Dual Standby (DSDS) functionality. The DSDS functionality may allow either of the two SIMs in the communication device 405 to be on standby waiting for a voice call and / or data connection. In DSDS, when a call / data is established on one SIM, the other SIM is no longer active. In some embodiments, DSDx functionality (either DSDA or DSDS functionality) may be implemented with a single SIM (e.g., a eUICC) that executes multiple SIM applications for different carriers and / or RATs.
[0083] As shown, the SOC 400 may include processor(s) 402, which may execute program instructions for the communication device 405 and display circuitry 404, which may perform graphics processing and provide display signals to the display 460. The processor(s) 402 may also be coupled to memory management unit (MMU) 440, which may be configured to receive addresses from the processor(s) 402 and translate those addresses to locations in memory (e.g., memory 406, read only memory (ROM) 450, NAND flash memory 410) and / or to other circuits or devices, such as the display circuitry 404, short to medium range wireless communication circuitry 429, cellular communication circuitry 430, connector I / F 420, and / or display 460. The MMU 440 may be configured to perform memory protection and page table translation or set up. In some embodiments, the MMU 440 may be included as a portion of the processor(s) 402.
[0084] As noted above, the communication device 405 may be configured to communicate using wireless and / or wired communication circuitry. The communication device 405 may be configured to perform methods for enabling energy efficiency and energy saving, as further described herein.
[0085] As described herein, the communication device 405 may include hardware andsoftware components for implementing the above features for a communication device 405to communicate a scheduling profile for power savings to a network. The processor 402 of the communication device 405 may be configured to implement part or all of the features described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer- readable memory medium). Alternatively (or in addition), processor 402 may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit). Alternatively (or in addition) the processor 402 of the communication device 405, in conjunction with one or more of the other components 400, 404, 406, 410, 420, 429, 430, 440, 445, 450, 460 may be configured to implement part or all of the features described herein.
[0086] In addition, as described herein, processor 402 may include one or more processing elements. Thus, processor 402 may include one or more integrated circuits (ICs) that are configured to perform the functions of processor 402. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processor(s) 402.
[0087] Further, as described herein, cellular communication circuitry 430 and short to medium range wireless communication circuitry 429 may each include one or more processing elements. In other words, one or more processing elements may be included in cellular communication circuitry 430 and, similarly, one or more processing elements may be included in short to medium range wireless communication circuitry 429. Thus, cellular communication circuitry 430 may include one or more integrated circuits (ICs) that are configured to perform the functions of cellular communication circuitry 430. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of cellular communication circuitry 430. Similarly, the short to medium range wireless communication circuitry 429 may include one or more ICs that are configured to perform the functions of short to medium range wireless communication circuitry 429. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of short to medium range wireless communication circuitry 429.of Cellular Communication Circuitry
[0088] Figure 5 illustrates an example simplified block diagram of cellular communication circuitry, according to some embodiments. It is noted that the block diagram of the cellular communication circuitry of Figure 5 is only one example of a possible cellular communication circuit. According to embodiments, cellular communication circuitry 535, which may be cellular communication circuitry 430, may be included in a communication device, such as communication device 405 described above. As noted above, communication device 405 may be a user equipment (UE) 106 device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet and / or a combination of devices, among other devices.
[0089] The cellular communication circuitry 535 may couple (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas 435a-b and 436 as shown (in Figure 4). In some embodiments, cellular communication circuitry 535 may include dedicated receive chains (including and / or coupled to, e.g., communicatively; directly or indirectly, dedicated processors and / or radios) for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G NR). For example, as shown in Figure 5, cellular communication circuitry 535 may include a modem 510 and a modem 520. Modem 510 may be configured for communications according to a first RAT, e.g., such as LTE or LTE-A, and modem 520 may be configured for communications according to a second RAT, e.g., such as 5G NR.
[0090] As shown, modem 510 may include one or more processors 512 and a memory 516 in communication with processors 512. Modem 510 may be in communication with a radio frequency (RF) front end 530. RF front end 530 may include circuitry for transmitting and receiving radio signals. For example, RF front end 530 may include receive circuitry (RX) 532 and transmit circuitry (TX) 534. In some embodiments, receive circuitry 532 may be in communication with downlink (DL) front end 550, which may include circuitry for receiving radio signals via antenna 335a.
[0091] Similarly, modem 520 may include one or more processors 522 and a memory 526 in communication with processors 522. Modem 520 may be in communication with an RF front end 540. RF front end 540 may include circuitry for transmitting and receiving radio signals. For example, RF front end 540 may include receive circuitry 542 and transmit circuitry 544. In some embodiments, receive circuitry 542 may be in communication withDL front end 560, which may include circuitry for receiving radio signals via antenna 335b.
[0092] In some embodiments, a switch 570 may couple transmit circuitry 534 to uplink (UL) front end 572. In addition, switch 570 may couple transmit circuitry 544 to UL front end 572. UL front end 572 may include circuitry for transmitting radio signals via antenna 336. Thus, when cellular communication circuitry 535 receives instructions to transmit according to the first RAT (e.g., as supported via modem 510), switch 570 may be switched to a first state that allows modem 510 to transmit signals according to the first RAT (e.g., via a transmit chain that includes transmit circuitry 534 and UL front end 572). Similarly, when cellular communication circuitry 535 receives instructions to transmit according to the second RAT (e.g., as supported via modem 520), switch 570 may be switched to a second state that allows modem 520 to transmit signals according to the second RAT (e.g., via a transmit chain that includes transmit circuitry 544 and UL front end 572).
[0093] In some embodiments, the cellular communication circuitry 535 may be configured to perform methods for enabling energy efficiency and energy saving, as further described herein.
[0094] As described herein, the modem 510 may include hardware and software components for implementing the above features or for time division multiplexing UL data for NSA NR operations, as well as the various other techniques described herein. The processors 512 may be configured to implement part or all of the features described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), processor 512 may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit). Alternatively (or in addition) the processor 512, in conjunction with one or more of the other components 530, 532, 534, 550, 570, 572, 335 and 336 may be configured to implement part or all of the features described herein.
[0095] In addition, as described herein, processors 512 may include one or more processing elements. Thus, processors 512 may include one or more integrated circuits (ICs) that are configured to perform the functions of processors 512. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processors 512.
[0096] As described herein, the modem 520 may include hardware and softwarecomponents for implementing the above features for performing methods for enabling energy efficiency and energy saving, as further described herein, as well as the various other techniques described herein. The processors 522 may be configured to implement part or all of the features described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer- readable memory medium). Alternatively (or in addition), processor 522 may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit). Alternatively (or in addition) the processor 522, in conjunction with one or more of the other components 540, 542, 544, 550, 570, 572, 335 and 336 may be configured to implement part or all of the features described herein.
[0097] In addition, as described herein, processors 522 may include one or more processing elements. Thus, processors 522 may include one or more integrated circuits (ICs) that are configured to perform the functions of processors 522. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processors 522.Figures 6A, 6B, and 7: 5G Core Network Architecture - Interworking with Wi-Fi
[0098] In some embodiments, the 5G core network (CN) may be accessed via (or through) a cellular connection / interface (e.g., via a 3GPP communication architecture / protocol) and a non- cellular connection / interface (e.g., a non-3GPP access architecture / protocol such as Wi-Fi connection). Figure 6 A illustrates an example of a 5G network architecture that incorporates both 3GPP (e.g., cellular) and non-3GPP (e.g., non-cellular) access to the 5G CN, according to some embodiments. As shown, a user equipment device (e.g., such as UE 106) may access the 5G CN through both a radio access network (RAN, e.g., such as gNB 604, which may be a base station 102) and an access point, such as AP 612. The AP 612 may include a connection to the Internet 600 as well as a connection to a non-3GPP inter-working funchon (N3IWF) 603 network entity. The N3IWF may include a connection to a core access and mobility management function (AMF) 605 of the 5G CN. The AMF 605 may include an instance of a 5G mobility management (5G MM) function associated with the UE 106. In addition, the RAN (e.g., gNB 604) may also have a connection to the AMF 605. Thus, the 5G CN may support unified authentication over both connections as well as allow simultaneous registration forUE 106 access via both gNB 604 and AP 612. As shown, the AMF 605 may include one or more functional entities associated with the 5G CN (e.g., network slice selection function (NSSF) 620, short message service function (SMSF) 622, application function (AF) 624, unified data management (UDM) 626, policy control function (PCF) 628, and / or authentication server function (AUSF) 630). Note that these functional entities may also be supported by a session management function (SMF) 606a and an SMF 606b of the 5G CN. The AMF 605 may be connected to (or in communication with) the SMF 606a. Further, the gNB 604 may in communication with (or connected to) a user plane function (UPF) 608a that may also be communication with the SMF 606a. Similarly, the N3IWF 603 may be communicating with a UPF 608b that may also be communicating with the SMF 606b. Both UPFs may be communicating with the data network (e.g., DN 610a and 610b) and / or the Internet 600 and Internet Protocol (IP) Multimedia Subsystem / IP Multimedia Core Network Subsystem (IMS) core network 610.
[0099] Figure 6B illustrates an example of a 5G network architecture that incorporates both dual 3GPP (e.g., LTE and 5G NR) access and non-3GPP access to the 5G CN, according to some embodiments. As shown, a user equipment device (e.g., such as UE 106) may access the 5G CN through both a radio access network (RAN, e.g., such as gNB 604 or eNB 602, which may be a base station 102) and an access point, such as AP 612. The AP 612 may include a connection to the Internet 600 as well as a connection to the N3IWF 603 network entity. The N3IWF may include a connection to the AMF 605 of the 5G CN. The AMF 605 may include an instance of the 5G MM function associated with the UE 106. In addition, the RAN (e.g., gNB 604) may also have a connection to the AMF 605. Thus, the 5G CN may support unified authentication over both connections as well as allow simultaneous registration for UE 106 access via both gNB 604 and AP 612. In addition, the 5G CN may support dual-registration of the UE on both a legacy network (e.g., LTE via eNB 602) and a 5G network (e.g., via gNB 604). As shown, the eNB 602 may have connections to a mobility management entity (MME) 642 and a serving gateway (SGW) 644. The MME 642 may have connections to both the SGW 644 and the AMF 605. In addition, the SGW 644 may have connections to both the SMF 606a and the UPF 608a. As shown, the AMF 605 may include one or more functional entities associated with the 5G CN (e.g., NSSF 620, SMSF 622, AF 624, UDM 626, PCF 628, and / or AUSF 630). Note that UDM 626 may also include a home subscriber server (HSS) function and the PCF may also include a policy and charging rules function (PCRF). Note further that these functionalentities may also be supported by the SMF 606a and the SMF 606b of the 5G CN. The AMF 605 may be connected to (or in communication with) the SMF 606a. Further, the gNB 604 may in communication with (or connected to) the UPF 608a that may also be communication with the SMF 606a. Similarly, the N3IWF 603 may be communicating with a UPF 608b that may also be communicating with the SMF 606b. Both UPFs may be communicating with the data network (e.g., DN 610a and 610b) and / or the Internet 600 and IMS core network 610.
[0100] Note that in various embodiments, one or more of the above-described network entities may be configured to perform methods for enabling energy efficiency and energy saving, as further described herein.
[0101] Figure 7 illustrates an example of a baseband processor architecture for a UE (e.g., such as UE 106), according to some embodiments. The baseband processor architecture 700 described in Figure 7 may be implemented on one or more radios (e.g., radios 429 and / or 430 described above) or modems (e.g., modems 510 and / or 520) as described above. As shown, the non-access stratum (NAS) 710 may include a 5G NAS 720 and a legacy NAS 750. The legacy NAS 750 may include a communication connection with a legacy access stratum (AS) 770. The 5G NAS 720 may include communication connections with both a 5G AS 740 and a non-3GPP AS 730 and Wi-Fi AS 732. The 5G NAS 720 may include functional entities associated with both access stratums. Thus, the 5G NAS 720 may include multiple 5G MM entities 726 and 728 and 5G session management (SM) entities 722 and 724. The legacy NAS 750 may include functional entities such as short message service (SMS) entity 752, evolved packet system (EPS) session management (ESM) entity 754, session management (SM) entity 756, EPS mobility management (EMM) entity 758, and mobility management (MM) / GPRS mobility management (GMM) entity 760. In addition, the legacy AS 770 may include functional entities such as LTE AS 772, UMTS AS 774, and / or GSM / GPRS AS 776.
[0102] Thus, the baseband processor architecture 700 allows for a common 5G-NAS for both 5G cellular and non-cellular (e.g., non-3GPP access). The baseband processor architecture 700 can be in communication with one or more UICC(s) 745. Note that as shown, the 5G MM may maintain individual connection management and registration management state machines for each connection. Additionally, a device (e.g., UE 106) may register to a single PLMN (e.g., 5G CN) using 5G cellular access as well as non-cellularaccess. Further, it may be possible for the device to be in a connected state in one access and an idle state in another access and vice versa. Finally, there may be common 5G-MM procedures (e.g., registration, de -registration, identification, authentication, as so forth) for both accesses.
[0103] Note that in various embodiments, one or more of the above-described functional entities of the 5G NAS and / or 5G AS may be configured to perform methods for enabling energy efficiency and energy saving, as further described herein.8 and 9: Device
[0104] Figure 8 illustrates example components of a device 800 in accordance with some embodiments. In some embodiments, the device 800 may include application circuitry 802, baseband circuitry 804, Radio Frequency (RF) circuitry 806, front-end module (FEM) circuitry 808, one or more antennas 810, and power management circuitry (PMC) 812 coupled together at least as shown. The components of the illustrated device 800 may be included in a UE or a RAN node. In some embodiments, the device 800 may include less elements (e.g., a RAN node may not utilize application circuitry 802, and instead include a processor / controller to process IP data received from an EPC). In some embodiments, the device 800 may include additional elements such as, for example, memory / storage, display, camera, sensor, or input / output (RO) interface. In other embodiments, the components described below may be included in more than one device (e.g., said circuitries may be separately included in more than one device for Cloud-RAN (C-RAN) implementations).
[0105] The application circuitry 802 may include one or more application processors. For example, the application circuitry 802 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor(s) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processors may be coupled with or may include memory / storage and may be configured to execute instructions stored in the memory / storage to enable various applications or operating systems to run on the device 800. In some embodiments, processors of application circuitry 802 may process IP data packets received from an EPC.
[0106] The baseband circuitry 804 may include circuitry such as, but not limited to, one or more single-core or multi -core processors. The baseband circuitry 804 may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 806 and to generate baseband signals for a transmit signal path of the RF circuitry 806. Baseband processing circuity 804 may interface with the application circuitry 802 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 806. For example, in some embodiments, the baseband circuitry 804 may include a third generation (3G) baseband processor 804A, a fourth generation (4G) baseband processor 804B, a fifth generation (5G) baseband processor 804C, or other baseband processor(s) 804D for other existing generations, generations in development or to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.). The baseband circuitry 804 (e.g., one or more of baseband processors 804A-D) may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 806. In other embodiments, some or all of the functionality of baseband processors 804A-D may be included in modules stored in the memory 804G and executed via a Central Processing Unit (CPU) 804E. The radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some embodiments, modulation / demodulation circuitry of the baseband circuitry 804 may include Fast-Fourier Transfomr (FFT), precoding, or constellation mapping / demapping functionality. In some embodiments, encoding / decoding circuitry of the baseband circuitry 804 may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder / decoder functionality. Embodiments of modulation / demodulation and encoder / decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.
[0107] In some embodiments, the baseband circuitry 804 may include one or more audio digital signal processor(s) (DSP) 804F. The audio DSP(s) 804F may be include elements for compression / decompression and echo cancellation and may include other suitable processing elements in other embodiments. Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments. In some embodiments, some or all of the constituent components of the baseband circuitry 804 and the application circuitry 802 may be implemented together such as, for example, on a system on a chip (SOC).
[0108] In some embodiments, the baseband circuitry 804 may provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry 804 may support communication with an evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN). Embodiments in which the baseband circuitry 804 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.
[0109] RF circuitry 806 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry 806 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. RF circuitry 806 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 808 and provide baseband signals to the baseband circuitry 804. RF circuitry 806 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 804 and provide RF output signals to the FEM circuitry 808 for transmission.
[0110] In some embodiments, the receive signal path of the RF circuitry 806 may include mixer circuitry 806a, amplifier circuitry 806b and filter circuitry 806c. In some embodiments, the transmit signal path of the RF circuitry 806 may include filter circuitry 806c and mixer circuitry 806a. RF circuitry 806 may also include synthesizer circuitry 806d for synthesizing a frequency for use by the mixer circuitry 806a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry 806a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 808 based on the synthesized frequency provided by synthesizer circuitry 806d. The amplifier circuitry 806b may be configured to amplify the down-converted signals and the filter circuitry 806c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals may be provided to the baseband circuitry 804 for further processing. In some embodiments, the output baseband signals may be zero-frequency baseband signals, although this is not a requirement. In some embodiments, mixer circuitry 806a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
[0111] In some embodiments, the mixer circuitry 806a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 806d to generate RF output signals for the FEM circuitry 808. The baseband signals may be provided by the baseband circuitry 804 and may be filtered by filter circuitry 806c.
[0112] In some embodiments, the mixer circuitry 806a of the receive signal path and the mixer circuitry 806a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upcon version, respectively. In some embodiments, the mixer circuitry 806a of the receive signal path and the mixer circuitry 806a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry 806a of the receive signal path and the mixer circuitry 806a may be arranged for direct downconversion and direct upconversion, respectively. In some embodiments, the mixer circuitry 806a of the receive signal path and the mixer circuitry 806a of the transmit signal path may be configured for super-heterodyne operation.
[0113] In some embodiments, the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternate embodiments, the output baseband signals and the input baseband signals may be digital baseband signals. In these alternate embodiments, the RF circuitry 806 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 804 may include a digital baseband interface to communicate with the RF circuitry 806.
[0114] In some dual-mode embodiments, a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.
[0115] In some embodiments, the synthesizer circuitry 806d may be a fractional-N synthesizer or a fractional N / N+l synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable. For example, synthesizer circuitry 806d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
[0116] The synthesizer circuitry 806d may be configured to synthesize an output frequency for use by the mixer circuitry 806a of the RF circuitry 806 based on a frequencyinput and a divider control input. In some embodiments, the synthesizer circuitry 806d may be a fractional N / N+l synthesizer.
[0117] In some embodiments, frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement. Divider control input may be provided by either the baseband circuitry 804 or the applications processor 802 depending on the desired output frequency. In some embodiments, a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the applications processor 802.
[0118] Synthesizer circuitry 806d of the RF circuitry 806 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator. In some embodiments, the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by either N or N+l (e.g., based on a carry out) to provide a fractional division ratio. In some example embodiments, the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop. In these embodiments, the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.
[0119] In some embodiments, synthesizer circuitry 806d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other. In some embodiments, the output frequency may be a LO frequency (fLO). In some embodiments, the RF circuitry 806 may include an IQ / polar converter.
[0120] FEM circuitry 808 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 810, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 806 for further processing. FEM circuitry 808 may also include a transmit signal path which may include circuitry configured to amplify signals for transmissionprovided by the RF circuitry 806 for transmission by one or more of the one or more antennas 810. In various embodiments, the amplification through the transmit or receive signal paths may be done solely in the RF circuitry 806, solely in the FEM 808, or in both the RF circuitry 806 and the FEM 808.
[0121] In some embodiments, the FEM circuitry 808 may include a TX / RX switch to switch between transmit mode and receive mode operation. The FEM circuitry may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry may include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 806). The transmit signal path of the FEM circuitry 808 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 806), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 810).
[0122] In some embodiments, the PMC 812 may manage power provided to the baseband circuitry 804. In particular, the PMC 812 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion. The PMC 812 may often be included when the device 800 is capable of being powered by a battery, for example, when the device is included in a UE. The PMC 812 may increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics.
[0123] While Figure 8 shows the PMC 812 coupled only with the baseband circuitry 804. However, in other embodiments, the PMC 8 12 may be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, application circuitry 802, RF circuitry 806, or FEM 808.
[0124] In some embodiments, the PMC 812 may control, or otherwise be part of, various power saving mechanisms of the device 800. For example, if the device 800 is in an RRC_Connected state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the device 800 may power down for brief intervals of time and thus save power.
[0125] If there is no data traffic activity for an extended period of time, then the device 800 may transition off to an RRC_Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The device 800 goes into a very low power state and it performs paging where again it periodicallywakes up to listen to the network and then powers down again. The device 800 may not receive data in this state, in order to receive data, it can transition back to RRC_Connected state.
[0126] An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.
[0127] Processors of the application circuitry 802 and processors of the baseband circuitry 804 may be used to execute elements of one or more instances of a protocol stack. For example, processors of the baseband circuitry 804, alone or in combination, may be used to execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry 804 may utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers). As referred to herein, Layer 3 may comprise a radio resource control (RRC) layer, described in further detail below. As referred to herein, Layer 2 may comprise a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, described in further detail below. As referred to herein, Layer 1 may comprise a physical (PHY) layer of a UE / RAN node, described in further detail below.
[0128] Figure 9 illustrates example interfaces of baseband circuitry in accordance with some embodiments. As discussed above, the baseband circuitry 804 of Figure 8 may comprise processors 804A-804E and a memory 804G utilized by said processors. Each of the processors 804A-804E may include a memory interface, 904A-904E, respectively, to send / receive data to / from the memory 804G.
[0129] The baseband circuitry 804 may further include one or more interfaces to communicatively couple to other circuitries / devices, such as a memory interface 912 (e.g., an interface to send / receive data to / from memory external to the baseband circuitry 804), an application circuitry interface 914 (e.g., an interface to send / receive data to / from the application circuitry 802 of Figure 8), an RF circuitry interface 916 (e.g., an interface to send / receive data to / from RF circuitry 806 of Figure 8), a wireless hardware connectivity interface 918 (e.g., an interface to send / receive data to / from Near Field Communication(NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components), and a power management interface 920 (e.g., an interface to send / receive power or control signals to / from the PMC 812.10: Control Plane Protocol Stack
[0130] Figure 10 is an illustration of a control plane protocol stack in accordance with some embodiments. In one embodiment, a control plane 1000 may be a communications protocol stack between one or more UEs such as, for example, UE 801 (or alternatively, the UE 802), and / or one or more RAN nodes 811 (or alternatively, the RAN node 812), and a mobility management entity (MME) 821.
[0131] The PHY layer 1001 may transmit or receive information used by the MAC layer 1002 over one or more air interfaces. The PHY layer 1001 may further perform link adaptation or adaptive modulation and coding (AMC), power control, cell search (e.g., for initial synchronization and handover purposes), and other measurements used by higher layers, such as the RRC layer 1005. The PHY layer 1001 may still further perform error detection on the transport channels, forward error correction (FEC) coding / decoding of the transport channels, modulation / demodulation of physical channels, interleaving, rate matching, mapping onto physical channels, and Multiple Input Multiple Output (MIMO) antenna processing.
[0132] The MAC layer 1002 may perform mapping between logical channels and transport channels, multiplexing of MAC service data units (SDUs) from one or more logical channels onto transport blocks (TB) to be delivered to PHY via transport channels, de-multiplexing MAC SDUs to one or more logical channels from transport blocks (TB) delivered from the PHY via transport channels, multiplexing MAC SDUs onto TBs, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ), and logical channel prioritization.
[0133] The RLC layer 1003 may operate in a plurality of modes of operation, including: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). The RLC layer 1003 may execute transfer of upper layer protocol data units (PDUs), error correction through automatic repeat request (ARQ) for AM data transfers, and concatenation, segmentation and reassembly of RLC SDUs for UM and AM data transfers.The RLC layer 1003 may also execute re-segmentation of RLC data PDUs for AM data transfers, reorder RLC data PDUs for UM and AM data transfers, detect duplicate data for UM and AM data transfers, discard RLC SDUs for UM and AM data transfers, detect protocol errors for AM data transfers, and perform RLC re-establishment.
[0134] The PDCP layer 1004 may execute header compression and decompression of IP data, maintain PDCP Sequence Numbers (SNs), perform in-sequence delivery of upper layer PDUs at re-establishment of lower layers, eliminate duplicates of lower layer SDUs at re-establishment of lower layers for radio bearers mapped on RLC AM, cipher and decipher control plane data, perform integrity protection and integrity verification of control plane data, control timer-based discard of data, and perform security operations (e.g., ciphering, deciphering, integrity protection, integrity verification, etc.).
[0135] The main services and functions of the RRC layer 1005 may include broadcast of system information (e.g., included in Master Information Blocks (MIBs) or System Information Blocks (SIBs) related to the non-access stratum (NAS)), broadcast of system information related to the access stratum (AS), paging, establishment, maintenance and release of an RRC connection between the UE and E-UTRAN (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), establishment, configuration, maintenance and release of point to point Radio Bearers, security functions including key management, inter radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting. Said MIBs and SIBs may comprise one or more information elements (IES), which may each comprise individual data fields or data structures.
[0136] In one example, a UE (e.g., UE 106A-N) and a RAN node (e.g., base station 102) 811 may utilize a Uu interface (e.g., an LTE-Uu interface) to exchange control plane data via a protocol stack comprising the PHY layer 1001, the MAC layer 1002, the RLC layer 1003, the PDCP layer 1004, and the RRC layer 1005.
[0137] The non-access stratum (NAS) protocols 1006 form the highest stratum of the control plane between the UE (e.g., UE 106A-N) 801 and an MME 821. The NAS protocols 1006 support the mobility of the UE (e.g., UE 106A-N) 801and the session management procedures to establish and maintain IP connectivity between the UE (e.g., UE 106A-N) 80 land a P-GW.
[0138] The SI Application Protocol (Sl-AP) layer 1015 may support the functions ofthe SI interface and comprise Elementary Procedures (EPs). An EP is a unit of interaction between a RAN node (e.g., base station 102)81 land the CN. The Sl-AP layer 1015 services may comprise two groups: UE-associated services and non UE-associated services. These services perform functions including, but not limited to: E-UTRAN Radio Access Bearer (E-RAB) management, UE capability indication, mobility, NAS signaling transport, RAN Information Management (RIM), and configuration transfer.
[0139] The Stream Control Transmission Protocol (SCTP) layer (alternatively referred to as the SCTP / IP layer) 1014 may ensure reliable delivery of signaling messages between the RAN node (e.g., base station 102) 8 Hand aMME821 based, in part, on the IP protocol, supported by the IP layer 1013. The L2 layer 1012 and the LI layer 1011 may refer to communication links (e.g., wired or wireless) used by the RAN node (e.g., base station 102) and the MME to exchange information.
[0140] The RAN node (e.g., base station 102) 81 land the MME 821may utilize an Sl-MME interface to exchange control plane data via a protocol stack comprising the LI layer 1011, theL2 layer 1012, the IP layer 1013, the SCTP layer 1014, and the Sl-AP layer 1015.11A-11B: Architecture of a an Energy Information Function
[0141] Figures 11 A-l IB illustrates an example architecture of a system 1100 including an Energy Information Function (EIF) in accordance with various embodiments. Figure 11A illustrates an architecture of system 1100 using service-based interfaces. Figure 1 IB illustrates an architecture of system 1100 using reference point representation. Components in system 1100 may form a core network for a 5G System (which may be referred to as a 5GC). The system 1100 is shown to include a UE 1101, which may be the same or similar to the UEs 106A, 106B, or 106N discussed previously; a (R)AN 1110, which may be the same or similar to the BSs 102A or 102N discussed previously; and a data network (DN) 1103, which may be, for example, operator services, Internet access, or 3rd party services. Further, system 1100 may include a number of network functions (NFs) including an Authentication Server Function (AUSF) 1122; Access and Mobility Management Function (AMF) 1121; a Session Management Function (SMF) 1124; a Network Exposure Function (NEF) 1123; a Policy Control Function (PCF) 1126; a Network Repository Function (NRF) 1125; a Unified Data Management (UDM) 1127; anApplication Function (AF) 1128; a User Plane Function (UPF) 1102; a Network Slice Selection Function (NSSF) 1129; and an Energy Information Function (EIF) 1130. These network functions may be implemented, in some cases, as virtualized software based functions / services. It should be noted that NFs may include additional functions not explicitly illustrated in Figures 11A-1 IB. Figure 11 A includes examples of NFs enhanced to support Energy Efficiency and Energy Saving functionality and Figure 11B illustrates an example direct interface of the Energy Information Function (EIF) with other NFs.
[0142] The UPF 1102 may act as an anchor point for intra-RAT and inter-RAT mobility, an external packet data unit (PDU) session point of interconnect to DN 1103, and a branching point to support multi-homed PDU session. A PDU session is a logical connection between the UE 1101 and the DN 1103. The UPF 1102 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rules, lawfully intercept packets (user plane (UP) collection), perform traffic usage reporting, perform quality of service (QoS) handling for a user plane (e.g., packet filtering, gating, UL / DE rate enforcement), perform Uplink Traffic verification (e.g., Service Data Flows (SDF) to QoS flow mapping), transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. UPF 1102 may include an uplink classifier to support routing traffic flows to a data network, The DN 1103 may represent various network operator services, Internet access, or third party services. DN 1103 may include, or be similar to, application server 104 discussed previously. The UPF 1102 may interact with the SMF 1124 via an N4 reference point between the SMF 1124 and the UPF 1102.
[0143] The AUSF 1122 may store data for authentication of UE 1101 and handle authentication-related functionality. The AUSF 1122 may facilitate a common authentication frame work for various access types. The AUSF 1122 may communicate with the AMF 1121 via an N12 reference point between the AMF 1121 and the AUSF 1122 (not shown by Figure 11A); and may communicate with the UDM 1127 via an N13 reference point between the UDM 1127 and the AUSF 1122 (not shown by Figure 11A). Additionally, the AUSF 1122 may exhibit an Nausf service -based interface.
[0144] The AMF 1121 may be responsible for registration management (e.g., for registering UE 1101, etc.), connection management, reachability management, mobility management, and lawful interception of AMF-related events, and access authentication andauthorization. The AMF 1121 may be a termination point for the Nil reference point between the AMF 1121 and the SMF 1124. The AMF 1121 may provide transport for SM messages between the UE 1101 and the SMF 1124, and act as a transparent proxy for routing SM messages. AMF 1121 may also provide transport for Short Message Service (SMS) messages between UE 1101 and an SMSF (not shown by Figure 11 A). AMF 1121 may act as a security anchor function (SEAF), which may include interaction with AUSF 1122 and the UE 1101, receipt of an intermediate key that was established as a result of the UE 1101 authentication process. Where Universal Subscriber Identity Module (US1M) based authentication is used, the AMF 1121 may retrieve the security material from AUSF 1122. AMF 1121 may also include a Security Context Management (SCM) function, which receives a key from the SEAF that it uses to derive access-network specific keys. Furthermore, AMF 1121 may be a termination point of a RAN control plane (CP) interface, which may include or be an N2 reference point between the (R)AN 1110 and the AMF 1121; and the AMF 1121 may be a termination point of NAS (Nl) signaling, and perform NAS ciphering and integrity protection.
[0145] AMF 1121 may also support NAS signaling with a UE 1101 over a non-3GPP Inter-Working Function (N3IWF) interface. The N3IWF may be used to provide access to untrusted entities. N3IWF may be a termination point for the N2 interface between the (R)AN 1110 and the AMF 1121 for the control plane, and may be a termination point for the N3 reference point between the (R)AN 1110 and the UPF 1102 for the user plane. As such, the AMF 1121 may handle N2 signaling from the SMF 1124 and the AMF 1121 for PDU sessions and encapsulate / decapsulate packets for IPSec and N3 tunneling, mark N3 user-plane packets in the uplink, and enforce QoS corresponding to N3 packet marking while considering QoS requirements associated with such marking received over N2. N3IWF may also relay uplink and downlink control plane non-access stratum (NAS) signaling between the UE 1101 and AMF 1121 via an Nl reference point between the UE 1101 and the AMF 1121, and relay uplink and downlink user-plane packets between the UE 1101 and UPF 1102. The N3IWF also provides mechanisms for internet protocol security (IPsec) tunnel establishment with the UE 1101. The AMF 1121 may exhibit an Namf service based interface, and may be a termination point for an N14 reference point between two AMFs 1121 and an N17 reference point between the AMF 1121 and a 5G Equipment Identity Register (5G-EIR) (not shown by Figure HA).
[0146] The UE 1101 may need to register with the AMF 1121 in order to receivenetwork services. Registration Management (RM) is used to register or deregister the UE 1101 with the network (e.g., AMF 1121), and establish a UE context in the network (e.g., AMF 1121). The UE 1101 may operate in an RM-REGISTERED state or an RM-DEREGISTERED state. In the RM -DEREGISTERED state, the UE 1101 is not registered with the network, and the UE context in AMF 1121 holds no valid location or routing information for the UE 1101, so the UE 1101 is not reachable by the AMF 1121. In the RM REGISTERED state, the UE 1101 is registered with the network, and the UE context in AMF 1121 may hold a valid location or routing information for the UE 1101 so the UE 1101 is reachable by the AMF 1121. In the RM-REGISTERED state, the UE 1101 may perform mobility registration update procedures, perform periodic registration update procedures triggered by expiration of the periodic update timer (e.g., to notify the network that the UE 1101 is still active), and perform a Registration Update procedure to update UE capability information or to re-negotiate protocol parameters with the network, among others.
[0147] The AMF 1121 may store one or more RM contexts for the UE 1101, where each RM context is associated with a specific access to the network. The RM context may be a data structure, database object, etc. that indicates or stores, inter glia, a registration state per access type and the periodic update timer. The AMF 1121 may also store a 5GC mobility management (MM) context that may be the same or similar to the evolved packet services (EPS) Mobility Management (E)MM context discussed previously. In various embodiments, the AMF 1121 may store a CE mode B Restriction parameter of the UE 1101 in an associated MM context or registration management (RM) context. The AMF 1121 may also derive the value, when needed, from the UE's usage setting parameter already stored in the UE context (and / or MM / RM context).
[0148] Connection Management (CM) may be used to establish and release a signaling connection between the UE 1101 and the AMF 1121 over the N1 interface. The signaling connection is used to enable NAS signaling exchange between the UE 1101 and a core network, and comprises both the signaling connection between the UE and the AN (e.g., RRC connection or UE-N3IWF connection for non-3GPP access) and the N2 connection for the UE 1101 between the AN (e.g., AN 1110) and the AMF 1121. The UE 1101 may operate in one of two CM states, CM-IDLE mode or CM-CONNECTED mode. When the UE 1101 is operating in the CM-IDLE state / mode, the UE 1101 may have no NAS signaling connection established with the AMF 1121 over the N1 interface, and there maybe (R)AN 1110 signaling connection (e.g., N2 and / or N3 connections) for the UE 1101. When the UE 1101 is operating in the CM-CONNECTED state / mode, the UE 1101 may have an established NAS signaling connection with the AMF 1121 over the N1 interface, and there may be a (R)AN 1110 signaling connection (e.g., N2 and / or N3 connections) for the UE 1101. Establishment of an N2 connection between the (R)AN 1110 and the AMF 1121 may cause the UE 1101 to transition from CM-IDLE mode to CM-CONNECTED mode, and the UE 1101 may transition from the CM-CONNECTED mode to the CM-IDEE mode when N2 signaling between the (R)AN 1110 and the AMF 1121 is released.
[0149] The SMF 1124 may be responsible for session management (SM) session establishment, modify and release, including tunnel maintain between UPF and AN node); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement and QoS; lawful intercept (for SM events and interface to LI system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF over N2 to AN; and determining SSC mode of a session. SM may refer to management of a PDU session, and a PDU session or "session" may refer to a PDU connectivity service that provides or enables the exchange of PDUs between a UE 1101 and a data network (DN) 1103 identified by a Data Network Name (DNN). PDU sessions may be established upon UE 1101 request, modified upon UE 1101 and a core network request, and released upon UE 1101 and a core network request using NAS SM signaling exchanged over the N1 reference point between the UE 1101 and the SMF 1124. Upon request from an application server, a core network may trigger a specific application inthe UE 1101. In response to receipt of the trigger message, the UE 1101 may pass the trigger message (or relevant parts / information of the trigger message) to one or more identified applications in the UE 1101. The identified application(s) in the UE 1101 may establish a PDU session to a specific data network name (DNN). The SMF 1124 may check whether the UE 1101 requests are compliant with user subscription information associated with the UE 1101. In this regard, the SMF 1124 may retrieve and / or request to receive update notifications on SMF 1124 level subscription data from the UDM 1127.
[0150] The SMF 1124 may include the following roaming functionality: handling local enforcement to apply QoS SLAB virtual Public Land Mobile Network (VPLMN); charging data collection and charging interface (VPLMN); lawful intercept (in VPLMN for SMevents and interface to LI system); and support for interaction with external DN 1103 for transport of signaling for PDU session authorization / authentication by external DN 1103. An N16 reference point between two SMFs 1124 may be included in the system 1100 (not shown by Figure 11 A), which may be between another SMF 1124 in a visited network and the SMF 1124 in the home network in roaming scenarios. Additionally, the SMF 1124 may exhibit the Nsmf service -based interface.
[0151] The NEF 1123 may provide means for securely exposing the services and capabilities provided by 3 GPP network functions for third party, internal exposure / re-exposure, Application Functions (e.g., AF 1128), edge computing or fog computing systems, etc. In such embodiments, the NEF 1123 may authenticate, authorize, and / or throttle the AFS. NEF 1123 may also translate information exchanged with the AF 1128 and information exchanged with internal network functions. For example, the NEF 1123 may translate between an AF-Service-Identifier and an internal SCC information. NEF 1123 may also receive information from other network functions (NFs) based on exposed capabilities of other network functions. This information may be stored at the NEF 1123 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 1123 to other NFs and AFs, and / or used for other purposes such as analytics. Additionally, the NEF 1123 may exhibit an Nnef service -based interface.
[0152] The NRF 1125 may support service discovery functions, receive NF discovery requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF 1125 also maintains information of available NF instances and their supported services. As used herein, the terms "instantiate," "instantiation," and the like may refer to the creation of an instance, and an "instance" may refer to a concrete occurrence of an object, which may occur, for example, during execution of program code. Additionally, the NRF 1125 may exhibit the Nnrf service based interface.
[0153] The PCF 1126 may provide policy rules to control plane function(s) to enforce them, and may also support unified policy framework to govern network behavior, The PCF 1126 may also implement a front end (FE) to access subscription information relevant for policy decisions in a Unified Data Repository (UDR) of the UDM 1127. The PCF 1126 may communicate with the AMF 1121 via an N15 reference point between the PCF 1126 and the AMF 1121 (note shown by Figure 11 A), which may include a PCF 1126 in a visitednetwork and the AMF 1121 in case of roaming scenarios. The PCF 1126 may communicate with the AF 1128 via an N5 reference point between the PCF 1126 and the AF 1128 (not shown by Figure 11A); and with the SMF 1124 via an N7 reference point between the PCF 1126 and the SMF 1124 (not shown by Figure 11A). The system 1100 may also include an N24 reference point between the PCF 1126 (in the home network) and a PCF 1126 in a visited network (not shown by Figure 11 A). Additionally, the PCF 1126 may exhibit an Npcf service-based interface.
[0154] The UDM 1127 may handle subscription-related information to support the network entities' handling of communication sessions, and may store subscription data of UE 1101. For example, subscription data may be communicated between the UDM 1127 and the AMF 1121 via an N5 reference point between the UDM 1127 and the AMF 1121 (not shown by Figure 11A). The UDM 1127 may include two parts, an application FE and a UDR (the FE and UDR are not shown by Figure 11 A). The UDR may store subscription data and policy data for the UDM 1127 and the PCF 1126, and / or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 1101) for the NEF 1123. The Nadr service-based interface may be exhibited by the UDR to allow the UDM 1127, PCF 1126, and NEF 1123 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notification of relevant data changes in the UDR. The UDM 1127 may include a UDM-FE, which is in charge of processing credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration / mobility management, and subscription management. The UDR may interact with the SMF 1124 via an N10 reference point between the UDM 1127 and the SMF 1124 (not shown by Figure 11 A). UDM 1127 may also support SMS management, wherein an SMS-FE implements the similar application logic as discussed previously. Additionally, the UDM 1127 may exhibit the Nudm service based interface.
[0155] The AF 1128 may provide application influence on traffic routing, provide access to the NCE, and interact with the policy framework for policy control. The NCE may be a mechanism that allows a core network and AF 1128 to provide information to each other via NEF 1123, which may be used for edge computing implementations. In suchimplementations, the network operator and third party services may be hosted close to the UE 1101 access point of attachment to achieve an efficient service delivery through the reduced end-to-end latency and load on the transport network. For edge computing implementations, the 5GC may select a UPF 1102 close to the UE 1101 and execute traffic steering from the UPF 1102 to DN 1103 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 1128. In this way, the AF 1128 may influence UPF (re)selection and traffic routing. Based on operator deployment, when AF 1128 is considered to be a trusted entity, the network operator may permit AF 1128 to interact directly with relevant NFs. Additionally, the AF 1128 may exhibit an Naf service -based interface.
[0156] The NSSF 1129 may select a set of network slice instances serving the UE 1101. The NSSF 1129 may also determine allowed Network Slice Selection .Assistance Information (NSSAI) and the mapping to the subscribed single NSSAI (S-NSSAI) is, if needed. The NSSF 1129 may also determine the AMF set to be used to serve the UE 1101, or a list of candidate AMF(s) 1121 based on a suitable configuration and possibly by querying the NRF 1125. The selection of a set of network slice instances for the UE 1101 may be triggered by the AMF 1121 with which the UE 1101 is registered by interacting with the NSSF 1129, which may lead to a change of AMF 1121. The NSSF 1129 may interact with the AMF 1121 via an N22 reference point between AMF 1121 and NSSF 1129 (not shown by Figure 11); and may communicate with another NSSF 1129 in a visited network via an N31 reference point (not shown by Figure 11). Additionally, the NSSF 1129 may exhibit an Nnssf service-based interface.
[0157] As discussed previously, a core network may include a short message service function (SMSF), which may be responsible for SMS subscription checking and verification, and relaying SM messages to / from the UE 1101 to / from other entities, such as an SMS-GMSC / IWMSC / SMS-router. The SMS may also interact with AMF 1121 and UDM 1127 for a notification procedure that the UE 1101 is available for SMS transfer (e.g., set a UE not reachable flag, and notifying UDM 1127 when UE 1101 is available for SMS).
[0158] A core network may also include other elements that are not shown by Figure 11 A, such as a Data Storage system / architecture, a 5G-E1R, a Security Edge Protection Proxy (SEPP), and the like. The Data Storage system may include a Structured Data Storage Network Function (SDSF), air Unstructured Data Storage Function (UDSF),and / or the like. Any network function (NF) may store and retrieve unstructured data into / from the UDSF (e.g., UE contexts), via N18 reference point between any NF and the UDSF (not shown by Figure HA), Individual NFs may share a UDSF for storing their respective unstructured data or individual NFs may each have their own UDSF located at or near the individual NFs. Additionally, the UDSF may exhibit an Nudsf service-based interface (not shown by Figure 11 A). The 5G-EIR may be an NF that checks the status of permanent equipment identifier (PEI) for determining whether particular equipment / entities are blacklisted from the network; and the SEPP may be a nontransparent proxy that performs topology hiding, message filtering, and policing on inter-PLMN control plane interfaces.
[0159] Additionally, there may be many more reference points and / or service -based interfaces between the NF services in the NFs; however, these interfaces and reference points have been omitted from Figures 11 A- 11 B for clarity. In one example, a core network may include an Nx interface, which is an inter-CN interface between a mobility management entity (MME) and the AMF 1121 in order to enable interworking between a core network and a core network in a 4G system. Other example interfaces / reference points may include an N5G-EIR service-based interface exhibited by a 5G-EIR, an N27 reference point between the NRF in the visited network and the NRF in the home network; and an N31 reference point between the NSSF in the visited network and the NSSF in the home network.
[0160] The EIF 1130 may support the following functionality; collection of the UE related Energy Consumption information; calculation of the Energy Consumption information at UE, S-NSSAI, PDU Session and Service Data Flow (e.g., per UE per application) granularity; and exposure of the Energy Consumption information to the authorized consumer NF(s) (AF 1128 / NEF 1123 or 5GC NF). As illustrated in Figure 1 IB, the EIF 1130 may communicate with the AF 1128 via an N110 reference point between the EIF 1130 and the AF 1128; the EIF 1130 may communicate with the NEF 1123 via an Nl ll reference point between the EIF 1130 and the NEF 1123; the EIF 1130 may communicate with the UDM 1127 via an N112 reference point between the EIF 1130 and the UDM 1127; the EIF 1130 may communicate with the PCF 1126 via an N 113 reference point between the EIF 1130 and the PCF 1126; and the EIF 1130 may communicate with the SMF 1124 via an N114 reference point between the EIF 1130 and the SMF 1124.
[0161] The EIF 1130 may collect the UE related Energy Consumption information including Node-level energy consumption information, Node-level data volume from operation and management (0AM) and data volume of the required granularities (i.e. S-NSSAI, PDU Session and / or Service Data Flow) from UPF 1102 (via SMF 1124). It should be noted that in Figures 11A-11B, the interface between EIF 1130 and an 0AM are not shown. The serving SMFs 1124 may be retrieved by the EIF 1130 from the UDM 1127 of the UE 1101 based on the provided input parameters including the UE ID and (S-NSSAI, DNN). The EIF 1130 may request the energy consumption and data volume information per NF level from the 0AM by providing the serving gNB ID(s) and (I-)UPF ID(s) received from SMFs. The EIF 1130 may request energy-related information from 0AM by creating management objects. The EIF 1130 may calculate the Energy Consumption information of the required granularities (UE, S-NSSAI, PDU Session and / or Service Data Flow), based on input parameters from and get the results. AF 1128 / NEF 1123 or 5GC NF may subscribe to the EIF 1130 for Energy Consumption information of required granularities (UE, S-NSSAI, PDU session and / or Service Data Flow). The consumer NF(s) may also subscribe to the Energy Consumption information exposure. If the consumer NF is AF 1128 / NEF 1123, it may subscribe the Energy Consumption information exposure of required granularity and may provide reporting threshold for the required granularity and the reporting time period.
[0162] Thus, the EIF 1130 provides functionality for supporting energy efficiency and energy saving in a network. 3 GPP plans to continue to provide enhancements from a system perspective for further improvement of network energy efficiency and energy saving. That is, 3GPP is investigating ways where networks can run more on sustainable sources of power (including, for example, green / renewable energy sources) and is studying ways a UE can access a network when green power is available (e.g., when solar power is available). 3GPP studies aim to focus on bringing efficiencies in User Plane signaling and selection of cells and NFs that run on green power. The 3 GPP studies also plan to address aspects of handling congestion in network, as congestion results in higher power consumption for both the UE and the network. For example, congestion in a network causes more battery drain with less than ideal service for UEs.
[0163] One 3GPP study plans to focus on following objectives: (i) How to enhance the collection, determination and exposure of energy related information in the 5GS: (ii) How to support service adjustments for the UE to enable energy saving. This may include howto support taking the energy attributes (e.g., renewable energy information) into account to determine UE traffic handling (e.g., QoS adjustment) and / or how to support policy control based on interaction with EIF and identify charging impacts caused by service adjustment; and (iii) How to support NF (re)selection and / or UP path adjustment based on energy related information.
[0164] With respect to enhancing the collection, determination and exposure of energy related information in the 5GS, aspects which may be considered include, for example: enhancing architecture, functionality and procedures along with accuracy, robustness; enhancing collection and exposure of newly identified energy related information for carbon emissions, renewable energy and expected energy related characteristics; and determining what information shall (or should) be provided to UEs related to the current energy-related characteristics of the serving network.
[0165] With respect to supporting service adjustments for the UE to enable energy saving, aspects which may be considered include, for example: how to support taking the energy attributes (e.g., Energy Consumption information which is existing attribute, and / or the new attributes such as renewable energy information if required) into account to determine UE traffic handling (e.g., for QoS adjustment); how to support SM policy control based on interaction with EIF for the service adjustments; how to identify charging impacts caused by service adjustment; and how to assist an authorized 3rd party to identify the set of UEs for whom to adjust the provided application service considering criteria such as the current and future (e.g. predicted) energy-related characteristics of their serving network.
[0166] With respect to supporting NF (re)selection and / or UP path adjustment based on energy related information, aspects which may be considered include, for example: how to optimize energy perspective (e.g., energy consumption or carbon footprint) in 5GC; determining what energy related information can be considered for making the decisions on NF (re)selection and / or UP path adjustment; how to extend NF profile (e.g., include energy related information) to support NF (re)selection for energy efficiency; and how to trigger UP path adjustment.
[0167] This disclosure describes example techniques for enabling energy efficiency and energy saving. According to the technique described herein, energy consumed by both a UE and a network may be reduced. Further, the techniques described herein, may also help 3GPP systems use more green power when it is available.
[0168] Renewable energy may include energy which is produced from resources that rely on fuel sources that restore themselves over short periods of time and do not diminish, such as, fuel sources including the sun, wind, moving water, organic plant and waste material (eligible biomass), and the earth’s heat (geothermal). Green energy power may refer to a subset of renewable energy technologies providing a specified environment benefit. Carbon based energy or power may refer to energy with is produced using the combustion of fossil fuels.Figures 12-13B Energy Efficiency and Energy Saving (EEES) Policy Selection and Data Transfer
[0169] Figure 12 illustrates an example of Energy Efficiency and Energy Saving (EEES) policy selection and data transfer according to some embodiments. In EEES policy selection and data transfer 1200, at 1202, AF 1128 indicates EEES driven Planned Data Transfer with QoS (PDTAQ). That is, as described in further detail below, QoS profiles may be configured based on data traffic type such that EEES may be enabled. At 1204, NEF 1123 authenticates AF 1128. At 1206, NEF 1123 invokes PCT 1126 to create an appropriate policy, i.e., based on the EEES driven PDTQ requirements. At 1208, PCF 1126 queries UDR of UDM 1127 and retrieves stored policy information. At 1210, PCF 1126 requests the collection of network status and energy related information in the network. At 1212, PCF 1126 generates appropriate policies and QoS profiles. At 1214, PCF 1126 sends the policies to the NEF 1123. At 1216, NEF 1123 forwards the policies to AF 1128. At 1218, AF 1128 selects a policy. At 1220, AF 1128 notifies NEF 1123 and PCF 1126 of the selected policy. At 1222, PCF 1126 informs UPF 1102 and SMF 1124 of the selected policy. In this manner, a EEES policy is selected. Examples of EEES policies are described in further detail below.
[0170] At 1224, UE 1101 indicates a type of data transfer and appropriate policies are applied in the network. As described in further detail below, a type of data transfer may include a Background Data Traffic (BDT) data transfer and a Foreground Data Traffic (FDT) data transfer. At 1226, an end-to-tend device traffic transfer is performed with appropriate QoS for EEES. In this manner, according to the techniques herein, a UE and a network may be configured to perform techniques for enabling EEES.
[0171] Figures 13A-13B illustrate an example of Energy Efficiency and Energy Saving(EEES) data transfer according to some embodiments. Referring to Figure 13 A, in EEES data transfer 1300, at 1302, UE 1101 sends a Service Request or Registration Request to (R)AN 1110, which may be a gNB. At 1304, (R)AN forwards the request to AMF 1121. The request includes a data request type and an indication that UE 1101 supports EEES. In one example, UE 1101 may indicate to the network if it supports EEES feature(s) in the 5GMM (mobility management) capability IE (Information Element). In one example, UE 1101 classifies the request to establish DRBs (Data Radio Bearers) due to Background Data Traffic (BDT) or Foreground Data Traffic (FDT). In one example, FDT may be any data directly transferred by UE 1101 because of user interactions which happens synchronously in foreground of a User Interface (UI). For example, FDT data may include video data being transferred using a streaming application. In one example, BDT traffic may be any data transferred by UE 1101 which may not be requested directly by a user which happens asynchronously in background of UI. For example, BDT data may include locally stored data which is asynchronously backed-up to a server. Thus, according to the techniques here, UE 1101 may indicate, using, e.g., a data traffic type IE in a Registration Request, Service Request, and other NAS messages whether the UE 1101 requests to perform a FDT or BDT data transfer.
[0172] As described above, according to the techniques herein, a network can create and select a policy based on EEES driven PDTQ requirements. In one example, a network can configure two types of QoS profiles for a PDU session for supporting FDT and BDT. In one example, a FDT QoS profile may have QoS rules that are configured such that the QoS parameters (Packet Delay, Round Trip Time (RTT), Allocation and Retention Priority (ARP), Maximum Flow Bit Rate (MFBR), etc.) have values for optimum user experience. In one example, a BDT QoS profile may have QoS rules that are configured such that the QoS parameters are relaxed and have less stringent values. In some examples, this can be configured for any DNN / APN (but preferable for internet DNN), and may not be applicable for some slices, such as, Ultra-Reliable Low Latency Communication (URLLC) which require stringent QoS parameters. In general, more energy may be consumed for FDT and less energy may be consumed for BDT.
[0173] At 1306, AMF 1121 stores an indication that UE 1101 supports EEES. At 1308, SMF 1124 sends a Registration Accept / Service Accept message to UE 1101. That is, if the network supports the EEES feature(s) and network maintained UE 1101 context contains Energy Saving Indicator as supported for the UE 1101, then the network indicates EnergySaving Indicator in Registration Accept / Service Accept messages. In one example, when both UE 1101 and network support the EEES feature, that network configures the two types of QoS profiles to be configured for data transfer, i.e., FDT and BDT.
[0174] At 1310, UE 1101 sends a PDU session establishment request with a DNN to SMF 1124. At 1312, AMF 1121 performs SMF selection for PDU session activation based on the information indicating if UE 1 101 supports EEES. At 1314, SMF selects UPF(s) 1102 based on EEES policies. For example, SMF 1124 may select a UPF 1102 based on whether it is running on green power. At 1316, SMF 1124 provide QoS rules for UE 1101 in a PDU Session Establishment Accept message. In one example, two QoS flows are supported, i.e., one for BDT and one for FDT. In this manner, a network receiving an NAS message with data traffic type IE indication (e.g., BDT or FDT) may acts as follows: for a BDT data transfer, a UPF running on green power may be preferred for BDT type of traffic. Further, if the network is experiencing high load scenarios, then gNB can reject the RRC connection request from UE with a backoff timer for BDT traffic. In some examples, UE 1101 may include a RRC connection establishment cause to differentiate FDT and BDT traffic. In some cases, this may help a network to identify the request from UE 1101 and, in some examples, the network may decide to reject the RRC connection setup request by UE 1101. For a FDT data transfer, in one example, UE 1101 may be able to override the provided backoff timer, if FDT UL traffic is now pending at UE 1101. The network can accept the request from UE 1101 for establishing DRBs for FDT traffic type. If UE 1101 has requested FDT type of traffic, then the network can consider this request on priority and look to establish the DRBs with the normal QoS rules setup for the PDU session. Thus, in one example, the network configures both QoS profiles (for FDT and BDT) when the PDU session is established. Based on data traffic type information in the NAS messages and the network activates the specific QoS Flow using the same DRB. As such, based on the data traffic type information, the data packets will be sent / received using the specific QoS Flow as indicated by the UE 1101.
[0175] Referring to Figure 13B, Figure 13B further illustrate EEES data transfer 1300 for a case where UE 1101 and the network enter IDLE mode and UE 1101 has UL data pending and a case where a path switch from BDT to FDT is handled. At 1318, UE 1101 and the network enter IDLE mode with UE 1101 having UL data pending. At 1320, UE 1101 sends a Service Request or Registration Request to AMF 1121 indicating a requested data type. At 1322, DRBs are established for both QoS rule (i.e., FDT and BDT). At 1324,AMF 1121 sends a Registration Accept / Service Accept message to UE 1101.
[0176] That is, in one example, the network may configure both QoS profiles when the PDU session is established. In one example, based on the data traffic type information in the NAS messages, network activates the specific QoS Flow using the same DRB and the data packets may be sent / received using the specific QoS Flow as indicated by the UE 1101. In one example, a secondary cell may be added can carry a specific QoS Flow for FDT or BDT. For example, at a given time, a primary cell SCELL-1 may cany FDT packets and secondary cell SCELL-2 may carry BDT. In this case, in one example, when a BDT data transfer is ongoing, the S-CELL and the respective UPF configured for a BDT data transfer is selected such that it is powered by a higher mix of green energy. Further, it should be noted that in this example, the QoS Flow for BDT is supported on one cell which has relaxed QoS parameters and hence can serve more users and a UPF powered by green energy can be selected at a more distant location.
[0177] At 1326, UE 1101 changes from a BDT data transfer to a FDT data transfer. At 1328, UE 1101 sends a Service Request or Registration Request to AMF 1121 indicating a requested data type is FDT. That is, UE 1101 initiates a SERVICE REQ indicating the updated data traffic type to FDT. This indicates to the network that UE is now requesting FDT traffic and corresponding QoS Flow and S-CELL needs to be added. At 1330, AMF changes traffic to FDT. That is, for example, UPF prioritizes traffic on a QoS FDT flow. At 1332, AMF sends a Registration Accept / Service Accept message to UE 1101. Thus, according to the techniques herein, if there is a switch in traffic request from BDT to FDT, then SCELL-1 may carry the data traffic for the specific PDU session / DNN and active SCELL-2 can be dropped. In one example, in order to prevent frequent BDT to FDT, switches hysteresis timers may be added at the UE 1101 or network side and / or in one example, switches may not be allowed until the DRBs are released or UE enters RRC-inactive mode, and in this case the network will not look to add BDT QoS flow again. Thus, in one example, only BDT to FDT switches are allowed and an FDT to BDT QoS flow change is allowed after DRBs are suspended (UE 1101 enters RRC-inactive) or DRBs are released. That is, in some examples, an FDT to BDT switch is not allowed for the ongoing active PDU session with active data traffic, unless UE 1101 enters RRC-inactive or IDLE mode.
[0178] In some examples, SMF 1124 may initiate a PDU session modificationprocedure to configure, modify, and / or remove QoS rules for BDT or FDT as needed. In some examples, UE Route Selection Policy (URSP) rules can initiate a request to configure DRBs for BDT or FDT traffic. For example, URSP rules can be provisioned to differentiate BDT traffic from other data traffic and when a URSP rule for BDT traffic is matched, then UE 1101 may initiate a Service Request procedure with data traffic type set to BDT type. In one example, the network may configure two PDU Sessions one for BDT-DNN and other for FDT-DNN and URSP rules may initiate a request to configure DRBs for BDT or FDT traffic. For example, URSP rules may be provisioned to differentiate BDT traffic from other data traffic and when a URSP rule for BDT traffic is matched, then UE 1101 activates PDU session for BDT-DNN. In one example, if traffic is not BDT, then a normal QoS rule profile may be configured. In one example, instead of frequently performing PDU session modification, UE 1101 and the network can configure two PDU session profiles one for BDT and for normal (e.g., FDT) data transfer. In one example, if there is a change from BDT to FDT, then UE 1101 can indicate the change in a UE 1101 requested PDU Session Modification to activate a FDT QoS profile to be used instead of BDT QoS Profile and vice versa, for example, as described above.
[0179] With respect to UE traffic handling using Access Management (AM) Policy, according to the techniques herein, energy attributes and renewable energy information may be taken into account to determine UE traffic handling. In one example, based on the UE 1101 indicated data traffic type in NAS messages, the network can consider the information in AM policy and route traffic to UPFs / gNB that are being served by green energy or where BDT traffic characteristics can be met, i.e., longer packet delays can be tolerated. Further, the UE 1101 subscription information for EIF 1130 includes Energy Saving Indicator. This indicator may enable the network to determine an AM policy of the UE 1101 based on mobility and determine if path switch is needed or not. In one example, based on the UE 1101 indication of whether a request is a FDT or BDT data transfer, the network can perform a path switch to NFs which are served by renewable power sources, provided the QoS requirements for respective traffic mode is acceptable. For example, if BDT traffic is active, then longer packet delays may be acceptable and if FDT is active, then switches to NFs served by renewable power sources may not be performed.
[0180] Further, in some examples, according to the techniques herein, authorized 3rd party servers may be assisted to identify a set of UEs 1101 in order to adjust the provided application service to consider criteria such as, the current and future (e.g., predicted)energy-related characteristics of their serving network. In one example, data traffic usage from UE 1101 may be used to assist an external application server to perform data traffic usage specific adjustments when green power is available. In one example, threshold based indications may be provided to a 3rd party service. For example, if a user data quota threshold is exceeded, then a 3rd party service can be notified about the data limits being applied for carbon powered NFs for BDT traffic. In such cases, BDT traffic may be considered as normal traffic (if there is no advantage for network in charging aspects). For example, in a case where BDT traffic is initiated by UE 1101 and the network load is low, (hence the network can handle BDT traffic and if there is no green powered gNB or NF available to serve UE traffic) in one example, a normal data charge may apply at PCRF. In one example, UEs can also be separated based on NFs / gNBs using carbon based or green energy. This information can help external 3rd party application servers to prioritize or provide better data plans or extra credits for use of its application (application level control tracking may be needed at the network and 3rd party application side). For example, a streaming service may provide such information and the network may apply appropriate controls if a user is accessing content from the streaming service.
[0181] In one example, according to the techniques herein, NF profile extension may be used to support EEES. In one example, a NF profile may be extended (e.g., extended to include energy related information) to support NF (re)selection for energy efficiency. In one example, 0AM 1132 or NRF 1125 may maintain information of UPFs and gNBs that are powered by green power, including during which periods, and what is the mix of green and carbon power used in the network. As provide above, because the SMF 1124 queries the NRF 1125 forthe best UPF 1102 selection, if the NRF 1125 maintains this information, then the NRF 1125 may assist in the SMF 1124 selection process. In one example, this information may additionally or alternatively be stored at EIF 1130, which may provide for better accessibility by 3rd party servers and SMF 1124. In one example, according to the techniques herein, the EIF 1130 may be extended to maintain information of gNB and other NFs which are being served by green power and for what duration (e.g., store information for both location and time for different NFs). In this case, SMF 1124 may query EIF 1130 (e.g., using UE location) to find out which gNBs and NFs are powered by green power and for what duration. Similarly, AMF 1121 can help in a SMF 1124 selection process based on UE 1101 location. In one example, using above information from either 0AM 1132 or EIF 1130, SMF 1124 can select those UPFs 1102 which are powered by green energy.
[0182] Further, in one example, AMF 1121 may use the information UEs supporting EEES to select those gNBs that are running on green power. AM policy may further help in selecting those cells supporting green power during mobility. This information can further help in determining how many more UEs the UPF 1102 or gNB can support at any given time. This may help in AM decisions for path switching. In one example, gNB can broadcast (SI: System Information) indicating a mix of green and carbon based electricity driving the cell(s). This may help in cell selection and cell re-selection. gNB can take into account the mix of green based and carbon based powered energy generation aspect during Handover / redirection to different NR cells. It should be noted that Annex T of 3GPP TS 23.501 V19.3.0 (2025-03), “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 19)” describes how to calculate energy consumed by a UE, gNB & UPF for PDU Session I QoS Flow I S-NSSAI. According to the techniques herein, these formulas may be extended to include energy consumed during BDT and FDT (normal) data traffic at gNB and UPF and at UE. Determining energy usage for FDT, BDT traffic, network may be used to decide if the network needs to backoff BDT traffic based on energy consumed.
[0183] In one example, data traffic type identification and tracking can be determined by network (based on packet headers, transport protocols used, IP addresses, etc.) In one example, the network can monitor specific PDU session data activity and classify the data traffic as BDT. For example, based on DNN used traffic for certain applications can always be categorized as BDT traffic and network can configure the appropriate QoS flows for the UE. It should be noted in some examples according to the techniques herein, application traffic categorization may be performed exclusively for cases which do not result in violations of user privacy.
[0184] In one example, the network may deploy a specific slice for different traffic types. In one example, this may be also updated by the network in the URSP rules. That is, URSP rules may need to be updated for the UE 1101 to request specific S-NSSAI activation, when certain applications are sending data in BDT mode. In one example, when there is user interaction, then the normal S-NSSAI with Internet DNN can be initiated. The QoS rules used for BDT Slice and Internet DNN may have relaxed QoS parameters. In one example, the network may provide a green slice. That is, during PDU session activation UE 1101 may request a green slice (and Internet DNN) for BDT traffic or FDT (normal) traffic. In this case, if UE 1101 is located in an area where green power is available, itstraffic may be handled on the green slice when green energy is available. In one example, to support green slices, SMF 1124 may selects UPF 1102 and gNB powered by green energy. In one example, UEs that are not located in the area where green energy is available will not be configured with a green slice. In one example, a green slice can be configured in the configured NSSAI provided by AMF 1121 in Configuration Update Command (CUC) or Registration Accept NAS messages. In one example, corresponding URSP rules may be updated using POLICY COMMAND by the PCF 1126 to update the matching filter for internet traffic to use a green slice. In one example, Area of Service availability of a slice can be configured for Green slice, i.e., indicating the availability of the green slice for a certain duration. Further, in one example, NS-AoS concept of slice availability in a certain location can also be used to inform the availability of green slice in certain locations which are using green energy.Figures 14A-14B: Energy Efficiency and Energy Saving (EEES) for Roaming Cases
[0185] In NR, roaming refers to a UE that moves from its Home Public Land Mobile Network (HPLMN) to a Visited Public Land Mobile Network (VPLMN) and continues accessing 5G services through the VPLMN. According to the techniques described herein, UE 1101 and the network may support EEES for roaming cases. In particular, for example, charging, tracking of green energy in a VPLMN, and handling of home routed and local break out scenarios for EEES are supported. Figures 14A-14B illustrate an example of Energy Efficiency and Energy Saving (EEES) for roaming cases according to some embodiments. It should be noted that in Figures 14A-14B, V-NF indicates a NF corresponding to a VPLMN and H-NF indicates a NF corresponding to a HPLMN. Further, a I-UPF corresponds to an Intermediate UPF and a PSA-UDF corresponds to a PDU Session Anchor-UDF.
[0186] Referring to Figure 14A, in EEES data transfer 1400, at 1402, UE 1101 sends a Service Request or Registration Request to V-AMF 1121a (e.g., via a gNB). The request includes a data request type and an indication that UE 1101 supports EEES, which may be as described above. At 1404, V-SMF 1124a sends a Registration Accept / Service Accept message to UE 1101. At 1406, UE 1101 sends a PDU session establishment request with a DNN to V-SMF 1124a. At 1408, V-SMF 1124a indicates to H-SMF 1124b that UE 1101 supports EEES. It should be noted, as described in further detail below, that this examplecorresponds to a home routed case. At 1410, H-SMF 1124b determines the QoS rules for BDT and FDT traffic. At 1412, H-SMF 1124b selects a PSA-UPF 1102a. For example, H-SMF 1124b selects a PSA-UPF that is running on green power. At 1414, V-SMF 1124a selects a I-UPF 1102b to satisfy the QoS rules provided by H-SMF 1124b. At 1416, H-SMF 1124b provides the QoS rule for BDT and FDT traffic in a PDU SESSION ESTABLISHMENT ACCEPT.
[0187] Referring to Figure 14B, Figure 14B further illustrate EEES data transfer 1400 for a case where UE 1101 and the network enter IDLE mode and UE 1101 has UL data pending. At 1418, UE 1101 and the network enter IDLE mode with UE 1101 having UL data pending. At 1420, UE 1101 sends a Service Request or Registration Request to V-AMF 1121a indicating a requested data type. It should be noted that in some examples, based on the type of data traffic and prevailing network load, BDT traffic can be backed-off. At 1422, V-AMF 1121a sends a Registration Accept / Service Accept message to UE 1101. At 1424, DRBs are established for both QoS rule (i.e., FDT and BDT). Thus, in this case, as described above, when a QoS Flow for BDT is supported on one cell which has relaxed QoS parameters, more users can be served and also UPFs powered by green energy can be selected (e.g., at a relative far off location).
[0188] As described above, the example in Figures 14A-14B corresponds to a home routed case. Thus, according to the techniques herein, when both the VPLMN and the HPLMN support EEES, for the home routed case, V-AMF 1121a selects the H-SMF 1124b and EEES and type of traffic is indicated to H-SMF 1124b to support of different type of traffic for creation of the PDU session. H-SMF 1124b selects PSA-UPF 1102a and V-SMF 1124a selects I-UPF 1102b such that both run on green power. Further, UPF selection by a SMF may consider information from NRF / EIF / OAM (not shown by Figures 14A-14B). Further, QoS rales defined for BDT and FDT traffic may be provided by H-SMF 1124b based on inputs from a H-PCF (not shown by Figures 14A-14B). These may be used to configure I-UPF 1102b and PSA-UPF 1102a. Charging function (CHF) may use information from UPFs (e.g., I-UPF 1102b and PSA-UPF 1102a) to track charging based on type of traffic (e.g., BDT or FDT QoS rales and data volume used). In one example, the VPLMN handles the RRC connection and congestion (or high network load) case for BDT type traffic. In one example, a respective EIF 1130 (not shown by Figures 14A-14B) on both VPLMN and HPLMN may track UE usage and UPF and gNB network usage of data and provides inputs to a 3rd party application server.
[0189] When both the VPLMN and the HPLMN support EEES, for the local breakout case, in one example, V-SMF, V-UPF and V-CHF may track energy usage locally in the network. This case may be similar to a case where UE 1101 served by HPLMN, except H-CHF will be indicated about the charging done by V-CHF.
[0190] According to the techniques herein, when the VPLMN, but not the HPLMN supports EEES, for the home routed case, V-AMF 1121a selects the H-SMF 1124b for creation of the PDU session. H-SMF 1124b selects any UPF as PSA-UPF 1102a, since it does not support the EEES feature and V-SMF 1121a selects I-UPF such that it runs on green power. UPF selection done by V-SMF 1121a may be done considering information from NRF / EIF / OAM. In one example, one set of QoS rules will be defined for traffic, which may be used to configure I-UPF 1102b and PSA-UPF 1102a. Charging function (CHF) may use information from UPFs (e.g., I-UPF 1102b and PSA-UPF 1102a) to track charging based on type of traffic (BDT or FDT), QoS rules, and data volume used and this information is indicated to H-CHF. In this case, the visited network handles the RRC connection and congestion (or high network load) case for BDT type traffic. Since the VPLMN supports EEES, it can help in reducing carbon footprint and saving power consumption when available. Saving of power consumption can be done in high network load scenarios by backing off BDT traffic data
[0191] When the VPLMN, but not the HPLMN supports EEES, for the local breakout case, in one example, V-SMF, V-UPF and V-CHF may track energy usage locally in the network. This case may be similar to a case where UE 1101 served by HPLMN, except H-CHF will be indicated about the charging done by V-CHF.
[0192] According to the techniques herein, when the HPLMN, but not the VPLMN supports EEES, for the home routed case, V-AMF 1124a selects the H-SMF 1124b for creation of the PDU session. H-SMF 1124b selects PSA-UPF 1102a based on the consideration that it runs on green power since and V-SMF 1124a selects any I-UPF 1102b. PSA-UPF 1102a selection done by H-SMF 1124b is done considering information from NRF / EIF / OAM. In this case, both sets of QoS rules may be defined for BDT and FDT traffic and used to configure I-UPF 1102b and PSA-UPF 1102a. In this case, CHF will use information from UPFs (LUPF 1102b and PSA-UPF 1102a) to track charging based on type of traffic (BDT or FDT), QoS rules, and data volume used, and this information is indicated to H-CHF. In this case, since HPLMN supports EEES, it can help in reducingcarbon footprint for home network by selecting UPFs that are powered by green power.
[0193] When the HPLMN, but not the VPLMN supports EEES, for the home routed case, no EEES will be applicable in this case. That is, V-SMF, V-UPF and V-CHF will track energy usage locally in the network without any specific benefit to UE 1101 or network.
[0194] In this manner, according to the techniques herein, a UE and a network may be configured to perform techniques for enabling EEES.Figures 15 and 16: Methods for enabling Energy Efficiency and Energy Saving (EEES) in a wireless communications network
[0195] Figure 15 illustrates a block diagram of an example of a method 1500 for enabling energy efficiency and energy saving at a network (NW) entity in a wireless communications network, according to some embodiments. The method shown in Figure 15 may be used in conjunction with any of the systems, methods, or devices shown in the Figures, among other devices. In various embodiments, some of the method elements shown may be performed concurrently, in a different order than shown, or may be omitted. Additional method elements may also be performed as desired. As shown, this method may operate as follows.
[0196] At 1510, a device in a wireless communications network, for example, a base station (BS), such as BS 102, receives a request indicate foreground data traffic (FDT) or background data traffic (BDT). For example, a network entity providing a NF may receive a Registration Request, Service Request, and other NAS messages including a data traffic type IE, as described above.
[0197] At 1520, the device may send an accept message indicating the network supports energy efficiency and energy saving features. For example, a network entity providing a NF may receive a Registration Accept or a Service Accept, as described above.
[0198] At 1530, the device may receive a packet data unit (PDU) session establishment request message. For example, a network entity providing a NF may receive a PDU session establishment request message, as described above.
[0199] At 1540, the device may send a packet data unit (PDU) session establishment accept message including QoS rules. For example, a network entity providing a NF mayreceive a PDU session establishment accept message, including QoS rules for FDT and BDT. as described above.
[0200] In some examples, FDT includes data transferred due to interactions by a user of the UE.
[0201] In some examples, BDT includes data which is not directly requested by the user of UE.
[0202] In some examples, Quality of Service (QoS) rules for a data transfer include rules of a FDT data transfer and a BDT data transfer.
[0203] In some examples, Quality of Service (QoS) rules for a BDT data transfer are configured such that QoS parameters have values which are less stringent compared to values for a FDT data transfer.
[0204] In some examples, the network comprises an access and mobility management function (AMF) that is configured to perform session management function (SMF) selection for a packet data unit (PDU) session activation based on the UE supporting Energy Efficiency and Saving.
[0205] In some examples, method 1500 further comprises establishing separate data radio bearers (DRBs) for the BDT data transfer and the FDT data transfer, with separate QoS rales for each data radio bearer based on the data request type.
[0206] In some examples, the network includes a session management function (SMF) that selects a user plane function (UPF) for the BDT data transfer based on whether the UPF is running on green power.
[0207] In some examples, the SMF provides QoS rales one for the FDT and other QoS rales for the BDT to the UE.
[0208] In some examples, method 1500 further comprises receiving a change of traffic from BDT to the FDT from the UE and sending instructions to the UPF to prioritize data traffic the data radio bearer for the FDT data transfer.
[0209] In some examples, a change of traffic from FDT to BDT is not allowed for an ongoing active PDU session with active data traffic unless the UE enters a radio resource control inactive (RRC-Inactive) or IDLE mode.
[0210] In some examples, receiving a request includes receiving a registration request,a service request, or a non-access stratum (NAS) message.
[0211] In some examples, a request includes a data traffic type information element (IE) indicating a FDT or BDT data request type.
[0212] In some examples, a request further includes an indication that the UE supports energy efficiency and energy saving features.
[0213] In some examples, and indication that the UE supports energy efficiency and energy saving features is provided in a 5GMM (mobility management) capability IE.
[0214] In some examples, an accept message includes a registration accept message or a service accept message.
[0215] Figure 16 illustrates a block diagram of an example of a method 1600 for enabling energy efficiency and energy saving at a User Equipment (UE) in a wireless communications network, according to some embodiments. The method shown in Figure 16 may be used in conjunction with any of the systems, methods, or devices shown in the Figures, among other devices. In various embodiments, some of the method elements shown may be performed concurrently, in a different order than shown, or may be omitted. Additional method elements may also be performed as desired. As shown, this method may operate as follows.
[0216] At 1610, a device in a wireless communications network, for example, a User Equipment (UE), such as UE 1101, sends a request indicate foreground data traffic (FDT) or background data traffic (BDT). For example, a UE may send a Registration Request, Service Request, and other NAS messages including a data traffic type IE, as described above.
[0217] At 1620, the device may receive an accept message indicating the network supports energy efficiency and energy saving features. For example, a UE may receive a Registration Accept or a Service Accept, as described above.
[0218] At 1630, the device may send a packet data unit (PDU) session establishment request message. For example, a UE may send a PDU session establishment request message, as described above.
[0219] At 1640, the device may receive a packet data unit (PDU) session establishment accept message including QoS rules. For example, a UE may receive a PDU session establishment accept message, including QoS rules for FDT and BDT, as described above.
[0220] In some examples, FDT includes data transferred due to interactions by a user of the UE when a user application requesting data transfer is in the foreground.
[0221] In some examples, BDT includes data which is not directly requested by the user of UE and occurs when a user application requesting data transfer is in the background.
[0222] In some examples, Quality of Service (QoS) rules and QoS flow descriptions for a data transfer include rules and flows of a FDT data transfer and a BDT data transfer.
[0223] In some examples, Quality of Service (QoS) rules for a BDT data transfer are configured such that QoS parameters have values which are less stringent compared to values for a FDT data transfer.
[0224] In some examples, sending a request includes sending a registration request, a service request, or a non-access stratum (NAS) message.
[0225] In some examples, a request includes a data traffic type information element (IE) indicating a FDT or BDT data request type.
[0226] In some examples, a request further includes an indication that the UE supports energy efficiency and energy saving features.
[0227] In some examples, and indication that the UE supports energy efficiency and energy saving features is provided in a 5GMM (mobility management) capability IE.
[0228] In some examples, an accept message includes a registration accept message or a service accept message.
[0229] In some examples, a User Equipment (UE) includes a radio resource control (RRC) connection establishment cause to differentiate between FDT and BDT traffic.
[0230] In some examples, a network comprises an operation and management (0AM) that is configured to store information regarding green power usage by network entities.
[0231] In some examples, a network comprises a Network Repository (NRF) function that is configured to store information regarding green power usage by network entities.
[0232] In some examples, a network comprises an Energy Information Function (EIF) that is configured to store information regarding green power usage by network entities.
[0233] In some examples, a network includes a session management function (SMF) that selects a user plane function (UPF) and a base station (gNB) powered by green energybased on a request to use a green slice from a User Equipment (UE)
[0234] In some examples, a network includes a Home Public Land Mobile Network (HPLMN) and a Visited Public Land Mobile Network (VPLMN).
[0235] In some examples, a VPLMN supports energy efficiency and energy saving features.
[0236] In some examples, both of the HPLMN and the VPLMN support energy efficiency and energy saving features.
[0237] In some examples, for a home routed case, the VPLMN handles a radio resource control (RRC) connection for BDT type traffic.
[0238] In some examples, network functions in the VPLMN track energy usage locally in the VPLMN.
[0239] It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.
[0240] Embodiments of the present disclosure may be realized in any of various forms. For example, some embodiments may be realized as a computer-implemented method, a computer- readable memory medium, or a computer system. Other embodiments may be realized using one or more custom-designed hardware devices such as ASICs. Still other embodiments may be realized using one or more programmable hardware elements such as FPGAs.
[0241] In some embodiments, a non-transitory computer-readable memory medium may be configured so that it stores program instructions and / or data, where the program instructions, if executed by a computer system, cause the computer system to perform a method, e.g., any of the method embodiments described herein, or, any combination of the method embodiments described herein, or, any subset of any of the method embodiments described herein, or, any combination of such subsets.
[0242] In some embodiments, a device (e.g., a UE 106) may be configured to include a processor (or a set of processors) including one or more baseband processors and one ormore application processors and a memory medium, where the memory medium stores program instructions, where the processor is configured to read and execute the program instructions from the memory medium, where the program instructions are executable to implement any of the various method embodiments described herein (or, any combination of the method embodiments described herein, or, any subset of any of the method embodiments described herein, or, any combination of such subsets). The device may be realized in any of various forms.
[0243] Any of the methods described herein for operating a user equipment (UE) may be the basis of a corresponding method for operating a base station, by interpreting each message / signal X received by the UE in the downlink as message / signal X transmitted by the base station, and each message / signal Y transmitted in the uplink by the UE as a message / signal Y received by the base station.
[0244] Although the embodiments above have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to embrace all such variations and modifications.
Claims
CLAIMSWhat is claimed is:
1. A method for enabling energy efficiency and energy saving in a wireless communications network, the method comprising:sending, to a network, a request indicating whether a data request type is a Foreground Data Traffic (FDT) or a Background Data Traffic (BDT);receiving, from the network, an accept message indicating that the network supports energy efficiency and energy saving features;sending, to the network, a packet data unit (PDU) session establishment request message; andreceiving, from the network, a packet data unit (PDU) session establishment accept message including authorized Quality of Service (QoS) rules and authorized QoS flow descriptions for a data transfer based on the data request type.
2. The method of claim 1 , wherein FDT includes data transferred due to interactions by a user of a User Equipment (UE) when a user application requesting data transfer is in the foreground.
3. The method of any of claims 1-2, wherein BDT includes data which is not directly requested by a user of a User Equipment (UE) and occurs when a user application requesting data transfer is in the background.
4. The method of any of claims 1-3, wherein Quality of Service (QoS) rules and QoS flow descriptions for a data transfer based on the data request type include rules of a FDT data transfer and a BDT data transfer.
5. The method of claim 4, wherein Quality of Service (QoS) rules and QoS flow descriptions for a BDT data transfer are configured such that QoS parameters have values which are less stringent compared to values for a FDT data transfer.
6. The method of claim 1, wherein sending the request includes sending a registration request, a service request, or a non-access stratum (NAS) message.
7. The method of any of claims 1-6, wherein the request includes a data traffic type information element (IE) indicating a FDT or BDT data request type.
8. The method of any of claim 1-7, wherein the request further includes an indication that the UE supports energy efficiency and energy saving features.
9. The method of claim 8, wherein the indication that the UE supports energy efficiency and energy saving features is provided in a 5GMM (mobility management) capability IE.
10. The method of any of claims 1-9, wherein the accept message includes a registration accept message or a service accept message.
11. A method for enabling energy efficiency and energy saving at a Network (NW) entity in a wireless communications network, the method comprising:receiving, from a User Equipment (UE), a request indicating whether a data request type is a Foreground Data Traffic (FDT) or a Background Data Traffic (BDT);sending, to the UE, an accept message indicating that the network supports energy efficiency and energy saving features;receiving, from the UE, a packet data unit (PDU) session establishment request message; andsending, to the UE, a packet data unit (PDU) session establishment accept message including Quality of Service (QoS) rules for a data transfer based on the data request type.
12. The method of claim 11, wherein FDT includes data transferred due to interactions by a user of the UE when a user application requesting data transfer is in the foreground.
13. The method of any of claims 11-12, wherein BDT includes data which is not directly requested by the user of UE and occurs when a user application requesting data transfer is in the background.
14. The method of any of claims 11-13, wherein Quality of Service (QoS) rules and QOS flow descriptions for a data transfer based on the data request type include rules of a FDT data transfer and a BDT data transfer.
15. The method of claim 14, wherein Quality of Service (QoS) rales and QoS flow descriptions for a BDT data transfer are configured such that QoS parameters have values which are less stringent compared to values for a FDT data transfer.
16. The method of claim 11, wherein the network comprises an access and mobility management function (AMF) that is configured to perform session management function (SMF) selection for a packet data unit (PDU) session activation based on the UE and network supporting Energy Efficiency and Saving.
17. The method of claim 14, further comprising establishing separate data radio bearers (DRBs) for the BDT data transfer and the FDT data transfer, with separate QoS rales and QoS flow descriptions for each data radio bearer based on the data request type.
18. The method of claim 16, wherein the network includes a session management function (SMF) that selects a user plane function (UPF) for the BDT data transfer based on whether the UPF is running on green power.
19. The method of claim 18, wherein the SMF provides one set of QoS rales and QoS flow descriptions for the FDT and another set of QoS rales and QoS flow descriptions for the BDT to the UE.
20. The method of claim 14, further comprising receiving a change of traffic from BDT to the FDT from the UE and sending instructions to the UPF to prioritize data traffic the data radio bearer for the FDT data transfer.
21. The method of claim 20, wherein a change of traffic from FDT to BDT is not allowed for an ongoing active PDU session with active data traffic unless the UE enters a radio resource control inactive (RRC-Inactive) mode or IDLE mode.
22. The method of claim 11, wherein receiving the request includes receiving a registration request, a service request, or a non-access stratum (NAS) message.
23. The method of any of claims 11-22, wherein the request includes a data traffic type information element (IE) indicating a FDT or BDT data request type.
24. The method of any of claims 11-23, wherein the request further includes an indication that the UE supports energy efficiency and energy saving features.
25. The method of claim 24, wherein the indication that the UE supports energy efficiency and energy saving features is provided in a 5GMM (mobility management) capability IE.
26. The method of any of claims 11-25, wherein the accept message includes a registration accept message or a service accept message.
27. The method of any of claims 1-26, wherein a User Equipment (UE) includes a radio resource control (RRC) connection establishment cause to differentiate between FDT and BDT traffic.
28. The method of claim 11, wherein the network comprises an operation and management (OAM) function that is configured to store information regarding green power usage by network entities.
29. The method of claim 11, wherein the network comprises a Network Repository (NRF) function that is configured to store information regarding green power usage by network entities.
30. The method of claim 11, wherein the network comprises an Energy Information Function (EIF) that is configured to store information regarding green power usage by network entities.
31. The method of claim 11 , wherein the network includes a session management function (SMF) that selects a user plane function (UPF) and a base station (gNB) powered by green energy based on a request to use a green slice from a User Equipment (UE).
32. The method of claim 11, wherein the network includes a Home Public Land Mobile Network (HPLMN) and a Visited Public Land Mobile Network (VPLMN).
33. The method of claim 32, wherein the VPLMN supports energy efficiency and energy saving features.
34. The method of claim 32, wherein both of the HPLMN and the VPLMN support energy efficiency and energy saving features.
35. The method of any of claims 32-34, wherein for a home routed case, the VPLMN handles a radio resource control (RRC) connection for BDT type traffic.
36. The method of any of claims 32-34, wherein network functions in the VPLMN track energy usage locally in the VPLMN.
37. A device configured for communicating in a wireless communication network, comprising:one or more processors, coupled to a memory, configured to perform any of the methods of claims 1-36.
38. The device of claim 37, wherein the device includes a user equipment (UE).
39. The device of claim 37, wherein the device includes a base station (BS).
40. The device of claim 37, wherein the device includes a network entity.
41. A non-transitory computer program product, comprising computer instructions which, when executed by one or more processors, perform any of the methods of claims 1-36.
42. A baseband processor configured to cause a user equipment (UE) to perform any of the methods of claims 1-36.
43. A baseband processor configured to cause a base station to perform one or more of the methods of claims 1-36.
