Supporting Energy Efficient Operation

Abstract

A wireless device sends, to a session management function (SMF), a first message, for a protocol data unit (PDU) session, indicating that the wireless device supports a reporting of an energy level. The wireless device receives, from the SMF and based on the sending, a second message, for the PDU session, comprising a condition for triggering the reporting of the energy level of the wireless device. The wireless device sends, based on the condition being met, a third message, for the PDU session, reporting a first energy level of the wireless device.

Description

Docket No.: 25-1028PCTTITLESupporting Energy Efficient OperationCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 754,298, filed February 5, 2025, all of which are hereby incorporated by reference in their entireties.BRIEF DESCRIPTION OF THE DRAWINGS

[0002] Examples of several of the various embodiments of the present disclosure are described herein with reference to the drawings.

[0003] FIG. 1A and FIG. 1B illustrate example mobile communication networks in which embodiments of the present disclosure may be implemented.

[0004] FIG. 2A and FIG. 2B respectively illustrate a New Radio (NR) user plane and control plane protocol stack.

[0005] FIG. 3 illustrates an example of services provided between protocol layers of the NR user plane protocol stack of FIG. 2A.

[0006] FIG. 4A illustrates an example downlink data flow through the NR user plane protocol stack of FIG.2A.

[0007] FIG. 4B illustrates an example format of a MAC subheader in a MAC PDU.

[0008] FIG. 5A and FIG. 5B respectively illustrate a mapping between logical channels, transport channels, and physical channels for the downlink and uplink.

[0009] FIG. 6 is an example diagram showing RRC state transitions of a UE.

[0010] FIG. 7 illustrates an example configuration of an NR frame into which OFDM symbols are grouped.

[0011] FIG. 8 illustrates an example configuration of a slot in the time and frequency domain for an NR carrier.

[0012] FIG. 9 illustrates an example of bandwidth adaptation using three configured BWPs for an NR carrier.

[0013] FIG. 10A illustrates three carrier aggregation configurations with two component carriers.

[0014] FIG. 10B illustrates an example of how aggregated cells may be configured into one or more PUCCH groups.

[0015] FIG. 11A illustrates an example of an SS / PBCH block structure and location.

[0016] FIG. 11B illustrates an example of CSI-RSs that are mapped in the time and frequency domains.

[0017] FIG. 12A and FIG. 12B respectively illustrate examples of three downlink and uplink beam management procedures.Docket No.: 25-1028PCT

[0018] FIG. 13A, FIG. 13B, and FIG. 13C respectively illustrate a four-step contention-based random access procedure, a two-step contention-free random access procedure, and another two-step random access procedure.

[0019] FIG. 14A illustrates an example of CORESET configurations for a bandwidth part.

[0020] FIG. 14B illustrates an example of a CCE-to-REG mapping for DCI transmission on a CORESET and PDCCH processing.

[0021] FIG. 15 illustrates an example of a wireless device in communication with a base station.

[0022] FIG. 16A, FIG. 16B, FIG. 16C, and FIG. 16D illustrate example structures for uplink and downlink transmission.

[0023] FIG. 17 illustrates an aspect of an example embodiment according to the present disclosure

[0024] FIG. 18 illustrates an aspect of an example embodiment according to the present disclosure.

[0025] FIG. 19 illustrates an aspect of an example embodiment according to the present disclosure.

[0026] FIG. 20 illustrates an aspect of an example embodiment according to the present disclosure.

[0027] FIG. 21 A illustrates an aspect of an example embodiment according to the present disclosure.

[0028] FIG. 21 B illustrates an aspect of an example embodiment according to the present disclosure.

[0029] FIG. 21 C illustrates an aspect of an example embodiment according to the present disclosure.

[0030] FIG. 21 D illustrates an aspect of an example embodiment according to the present disclosure.

[0031] FIG. 22 illustrates an aspect of an example embodiment according to the present disclosure.

[0032] FIG. 23 illustrates an aspect of an example embodiment according to the present disclosure

[0033] FIG. 24 illustrates an aspect of an example embodiment according to the present disclosure.

[0034] FIG. 25 illustrates an aspect of an example embodiment according to the present disclosure.

[0035] FIG. 26 illustrates an aspect of an example embodiment according to the present disclosure.

[0036] FIG. 27 illustrates an aspect of an example embodiment according to the present disclosure.

[0037] FIG. 28 illustrates an aspect of an example embodiment according to the present disclosure

[0038] FIG. 29 illustrates an aspect of an example embodiment according to the present disclosure.

[0039] FIG. 30 illustrates an aspect of an example embodiment according to the present disclosure.

[0040] FIG. 31 illustrates an aspect of an example embodiment according to the present disclosure.

[0041] FIG. 32 illustrates an aspect of an example embodiment according to the present disclosure

[0042] FIG. 33 illustrates an aspect of an example embodiment according to the present disclosure.

[0043] FIG. 34 illustrates an aspect of an example embodiment according to the present disclosure.

[0044] FIG. 35 illustrates an aspect of an example embodiment according to the present disclosure.

[0045] FIG. 36 illustrates an aspect of an example embodiment according to the present disclosure.

[0046] FIG. 37 illustrates an aspect of an example embodiment according to the present disclosure

[0047] FIG. 38 illustrates an aspect of an example embodiment according to the present disclosure.Docket No.: 25-1028PCTDETAILED DESCRIPTION

[0048] In the present disclosure, various embodiments are presented as examples of how the disclosed techniques may be implemented and / or how the disclosed techniques may be practiced in environments and scenarios. It will be apparent to persons skilled in the relevant art that various changes in form and detail can be made therein without departing from the scope. In fact, after reading the description, it will be apparent to one skilled in the relevant art how to implement alternative embodiments. The present embodiments should not be limited by any of the described exemplary embodiments. The embodiments of the present disclosure will be described with reference to the accompanying drawings. Limitations, features, and / or elements from the disclosed example embodiments may be combined to create further embodiments within the scope of the disclosure. Any figures which highlight the functionality and advantages, are presented for example purposes only. The disclosed architecture is sufficiently flexible and configurable, such that it may be utilized in ways other than that shown. For example, the actions listed in any flowchart may be re-ordered or only optionally used in some embodiments.

[0049] Embodiments may be configured to operate as needed. The disclosed mechanism may be performed when certain criteria are met, for example, in a wireless device, a base station, a radio environment, a network, a combination of the above, and / or the like. Example criteria may be based, at least in part, on for example, wireless device or network node configurations, traffic load, initial system set up, packet sizes, traffic characteristics, a combination of the above, and / or the like. When the one or more criteria are met, various example embodiments may be applied. Therefore, it may be possible to implement example embodiments that selectively implement disclosed protocols.

[0050] A base station may communicate with a mix of wireless devices. Wireless devices and / or base stations may support multiple technologies, and / or multiple releases of the same technology. Wireless devices may have some specific capability(ies) depending on wireless device category and / or capability(ies). When this disclosure refers to a base station communicating with a plurality of wireless devices, this disclosure may refer to a subset of the total wireless devices in a coverage area. This disclosure may refer to, for example, a plurality of wireless devices of a given LTE or 5G release with a given capability and in a given sector of the base station. The plurality of wireless devices in this disclosure may refer to a selected plurality of wireless devices, and / or a subset of total wireless devices in a coverage area which perform according to disclosed methods, and / or the like. There may be a plurality of base stations or a plurality of wireless devices in a coverage area that may not comply with the disclosed methods, for example, those wireless devices or base stations may perform based on older releases of LTE or 5G technology.

[0051] In this disclosure, "a” and “an” and similar phrases are to be interpreted as “at least one” and “one or more.” Similarly, any term that ends with the suffix “(s)” is to be interpreted as “at least one” and “one orDocket No.: 25-1028PCTmore.” In this disclosure, the term “may” is to be interpreted as “may, for example.” In other words, the term “may” is indicative that the phrase following the term “may” is an example of one of a multitude of suitable possibilities that may, or may not, be employed by one or more of the various embodiments. The terms “comprises” and “consists of’, as used herein, enumerate one or more components of the element being described. The term “comprises” is interchangeable with “includes” and does not exclude unenumerated components from being included in the element being described. By contrast, “consists of’ provides a complete enumeration of the one or more components of the element being described. The term “based on”, as used herein, should be interpreted as “based at least in part on” rather than, for example, “based solely on”. The term “and / or” as used herein represents any possible combination of enumerated elements. For example, “A, B, and / or C” may represent A; B; C; A and B; A and C; B and C; or A, B, and C.

[0052] If A and B are sets and every element of A is an element of B, A is called a subset of B. In this specification, only non-empty sets and subsets are considered. For example, possible subsets of B = {cell 1 , cell2} are: {celH }, {cell2}, and {celH , cell2}. The phrase “based on" (or equally “based at least on”) is indicative that the phrase following the term “based on” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “in response to” (or equally “in response at least to”) is indicative that the phrase following the phrase “in response to” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “depending on” (or equally “depending at least to”) is indicative that the phrase following the phrase “depending on” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “employing / using” (or equally “employing / using at least”) is indicative that the phrase following the phrase “employing / using” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments.

[0053] The term configured may relate to the capacity of a device whether the device is in an operational or non-operational state. Configured may refer to specific settings in a device that affect or implement the operational characteristics of the device whether the device is in an operational or non-operational state. In other words, the hardware, software, firmware, registers, memory values, and / or the like may be “configured” within a device, whether the device is in an operational or nonoperational state, to provide the device with specific characteristics. Terms such as “a control message to cause in a device” may mean that a control message has parameters that may be used to configure specific characteristics or may be used to implement certain actions in the device, whether the device is in an operational or non-operational state.

[0054] In this disclosure, parameters (or equally called, fields, or Information elements: IBs) may comprise one or more information objects, and an information object may comprise one or more other objects. For example, if parameter (IE) N comprises parameter (IE) M, and parameter (IE) M comprises parameter (IE)Docket No.: 25-1028PCTK, and parameter (IE) K comprises parameter (information element) J. Then, for example, N comprises K, and N comprises J. In an example embodiment, when one or more messages comprise a plurality of parameters, it implies that a parameter in the plurality of parameters is in at least one of the one or more messages, but does not have to be in each of the one or more messages.

[0055] Many features presented are described as being optional through the use of “may” or the use of parentheses. For the sake of brevity and legibility, the present disclosure does not explicitly recite each and every permutation that may be obtained by choosing from the set of optional features. The present disclosure is to be interpreted as explicitly disclosing all such permutations. For example, a system described as having three optional features may be embodied in seven ways, namely with just one of the three possible features, with any two of the three possible features or with three of the three possible features.

[0056] Many of the elements described in the disclosed embodiments may be implemented as modules. A module is defined here as an element that performs a defined function and has a defined interface to other elements. The modules described in this disclosure may be implemented in hardware, software in combination with hardware, firmware, wetware (e.g. hardware with a biological element) or a combination thereof, which may be behaviorally equivalent. For example, modules may be implemented as a software routine written in a computer language configured to be executed by a hardware machine (such as C, C++, Fortran, Java, Basic, MATLAB or the like) or a modeling / simulation program such as Simulink, Stateflow, GNU Octave, or LabVIEWMathScript. It may be possible to implement modules using physical hardware that incorporates discrete or programmable analog, digital and / or quantum hardware. Examples of programmable hardware comprise: computers, microcontrollers, microprocessors, application-specific integrated circuits (ASICs); field programmable gate arrays (FPGAs); and complex programmable logic devices (CPLDs). Computers, microcontrollers and microprocessors are programmed using languages such as assembly, C, C++ or the like. FPGAs, ASICs and CPLDs are often programmed using hardware description languages (HDL) such as VHSIC hardware description language (VHDL) or Verilog that configure connections between internal hardware modules with lesser functionality on a programmable device. The mentioned technologies are often used in combination to achieve the result of a functional module.

[0057] FIG. 1 A illustrates an example of a mobile communication network 100 in which embodiments of the present disclosure may be implemented. The mobile communication network 100 may be, for example, a public land mobile network (PLMN) run by a network operator. As illustrated in FIG. 1A, the mobile communication network 100 includes a core network (CN) 102, a radio access network (RAN) 104, and a wireless device 106.Docket No.: 25-1028PCT

[0058] The CN 102 may provide the wireless device 106 with an interface to one or more data networks (DNs), such as public DNs (e.g., the Internet), private DNs, and / or intra-operator DNs. As part of the interface functionality, the CN 102 may set up end-to-end connections between the wireless device 106 and the one or more DNs, authenticate the wireless device 106, and provide charging functionality.

[0059] The RAN 104 may connect the CN 102 to the wireless device 106 through radio communications over an air interface. As part of the radio communications, the RAN 104 may provide scheduling, radio resource management, and retransmission protocols. The communication direction from the RAN 104 to the wireless device 106 over the air interface is known as the downlink and the communication direction from the wireless device 106 to the RAN 104 over the air interface is known as the uplink. Downlink transmissions may be separated from uplink transmissions using frequency division duplexing (FDD), timedivision duplexing (TDD), and / or some combination of the two duplexing techniques.

[0060] The term wireless device may be used throughout this disclosure to refer to and encompass any mobile device or fixed (non-mobile) device for which wireless communication is needed or usable. For example, a wireless device may be a telephone, smart phone, tablet, computer, laptop, sensor, meter, wearable device, Internet of Things (loT) device, vehicle roadside unit (RSU), relay node, automobile, and / or any combination thereof. The term wireless device encompasses other terminology, including user equipment (UE), user terminal (UT), access terminal (AT), mobile station, handset, wireless transmit and receive unit (WTRU), and / or wireless communication device.

[0061] The RAN 104 may include one or more base stations (not shown). The term base station may be used throughout this disclosure to refer to and encompass a Node B (associated with UMTS and / or 3G standards), an Evolved Node B (eNB, associated with E-UTRA and / or 4G standards), a remote radio head (RRH), a baseband processing unit coupled to one or more RRHs, a repeater node or relay node used to extend the coverage area of a donor node, a Next Generation Evolved Node B (ng-eNB), a Generation Node B (gNB, associated with NR and / or 5G standards), an access point (AP, associated with, for example, Wi-Fi or any other suitable wireless communication standard), and / or any combination thereof. A base station may comprise at least one gNB Central Unit (gNB-CU) and at least one a gNB Distributed Unit (gNB-DU).

[0062] A base station included in the RAN 104 may include one or more sets of antennas for communicating with the wireless device 106 over the air interface. For example, one or more of the base stations may include three sets of antennas to respectively control three cells (or sectors). The size of a cell may be determined by a range at which a receiver (e.g., a base station receiver) can successfully receive the transmissions from a transmitter (e.g., a wireless device transmitter) operating in the cell. Together, the cells of the base stations may provide radio coverage to the wireless device 106 over a wide geographic area to support wireless device mobility.Docket No.: 25-1028PCT

[0063] In addition to three-sector sites, other implementations of base stations are possible. For example, one or more of the base stations in the RAN 104 may be implemented as a sectored site with more or less than three sectors. One or more of the base stations in the RAN 104 may be implemented as an access point, as a baseband processing unit coupled to several remote radio heads (RRHs), and / or as a repeater or relay node used to extend the coverage area of a donor node. A baseband processing unit coupled to RRHs may be part of a centralized or cloud RAN architecture, where the baseband processing unit may be either centralized in a pool of baseband processing units or virtualized. A repeater node may amplify and rebroadcast a radio signal received from a donor node. A relay node may perform the same / similar functions as a repeater node but may decode the radio signal received from the donor node to remove noise before amplifying and rebroadcasting the radio signal.

[0064] The RAN 104 may be deployed as a homogenous network of macrocell base stations that have similar antenna patterns and similar high-level transmit powers. The RAN 104 may be deployed as a heterogeneous network. In heterogeneous networks, small cell base stations may be used to provide small coverage areas, for example, coverage areas that overlap with the comparatively larger coverage areas provided by macrocell base stations The small coverage areas may be provided in areas with high data traffic (or so-called “hotspots”) or in areas with weak macrocell coverage. Examples of small cell base stations include, in order of decreasing coverage area, microcell base stations, picocell base stations, and femtocell base stations or home base stations.

[0065] The Third-Generation Partnership Project (3GPP) was formed in 1998 to provide global standardization of specifications for mobile communication networks similar to the mobile communication network 100 in FIG. 1A. To date, 3GPP has produced specifications for three generations of mobile networks: a third generation (3G) network known as Universal Mobile Telecommunications System (UMTS), a fourth generation (4G) network known as Long-Term Evolution (LTE), and a fifth generation (5G) network known as 5G System (5GS). Embodiments of the present disclosure are described with reference to the RAN of a 3GPP 5G network, referred to as next-generation RAN (NG-RAN). Embodiments may be applicable to RANs of other mobile communication networks, such as the RAN 104 in FIG. 1A, the RANs of earlier 3G and 4G networks, and those of future networks yet to be specified (e.g., a 3GPP 6G network). NG-RAN implements 5G radio access technology known as New Radio (NR) and may be provisioned to implement 4G radio access technology or other radio access technologies, including non-3GPP radio access technologies.

[0066] FIG. 1 B illustrates another example mobile communication network 150 in which embodiments of the present disclosure may be implemented. Mobile communication network 150 may be, for example, a PLMN run by a network operator. As illustrated in FIG. 1B, mobile communication network 150 includes a 5G core network (5G-CN) 152, an NG-RAN 154, and UEs 156A and 156B (collectively UEs 156). TheseDocket No.: 25-1028PCTcomponents may be implemented and operate in the same or similar manner as corresponding components described with respect to FIG. 1 A.

[0067] The 5G-CN 152 provides the UEs 156 with an interface to one or more DNs, such as public DNs (e.g., the Internet), private DNs, and / or intra-operator DNs. As part of the interface functionality, the 5G-CN 152 may set up end-to-end connections between the UEs 156 and the one or more DNs, authenticate the UEs 156, and provide charging functionality. Compared to the CN of a 3GPP4G network, the basis of the 5G-CN 152 may be a service-based architecture. This means that the architecture of the nodes making up the 5G-CN 152 may be defined as network functions that offer services via interfaces to other network functions. The network functions of the 5G-CN 152 may be implemented in several ways, including as network elements on dedicated or shared hardware, as software instances running on dedicated or shared hardware, or as virtualized functions instantiated on a platform (e.g., a cloud-based platform).

[0068] As illustrated in FIG. 1B, the 5G-CN 152 includes an Access and Mobility Management Function (AMF) 158A and a User Plane Function (UPF) 158B, which are shown as one component AMF / UPF 158 in FIG. 1 B for ease of illustration. The UPF 158B may serve as a gateway between the NG-RAN 154 and the one or more DNs. The UPF 158B may perform functions such as packet routing and forwarding, packet inspection and user plane policy rule enforcement, traffic usage reporting, uplink classification to support routing of traffic flows to the one or more DNs, quality of service (QoS) handling for the user plane (e.g., packet filtering, gating, uplink / downlink rate enforcement, and uplink traffic verification), downlink packet buffering, and downlink data notification triggering. The UPF 158B may serve as an anchor point for intra- / inter-Radio Access Technology (RAT) mobility, an external protocol (or packet) data unit (PDU) session point of interconnect to the one or more DNs, and / or a branching point to support a multi-homed PDU session. The UEs 156 may be configured to receive services through a PDU session, which is a logical connection between a UE and a DN.

[0069] The AMF 158A may perform functions such as Non-Access Stratum (NAS) signaling termination, NAS signaling security, Access Stratum (AS) security control, inter-CN node signaling for mobility between 3GPP access networks, idle mode UE reachability (e.g., control and execution of paging retransmission), registration area management, intra-system and inter-system mobility support, access authentication, access authorization including checking of roaming rights, mobility management control (subscription and policies), network slicing support, and / or session management function (SMF) selection. NAS may refer to the functionality operating between a CN and a UE, and AS may refer to the functionality operating between the UE and a RAN.

[0070] The 5G-CN 152 may include one or more additional network functions that are not shown in FIG.1 B for the sake of clarity. For example, the 5G-CN 152 may include one or more of a Session Management Function (SMF), an NR Repository Function (NRF), a Policy Control Function (PCF), a Network ExposureDocket No.: 25-1028PCTFunction (NEF), a Unified Data Management (UDM), an Application Function (AF), and / or an Authentication Server Function (AUSF).

[0071] The NG-RAN 154 may connect the 5G-CN 152 to the UEs 156 through radio communications over the air interface. The NG-RAN 154 may include one or more gNBs, illustrated as gNB 160A and gNB 160B (collectively gNBs 160) and / or one or more ng-eNBs, illustrated as ng-eNB 162A and ng-eNB 162B (collectively ng-eNBs 162). The gNBs 160 and ng-eNBs 162 may be more generically referred to as base stations. The gNBs 160 and ng-eNBs 162 may include one or more sets of antennas for communicating with the UEs 156 over an air interface. For example, one or more of the gNBs 160 and / or one or more of the ng-eNBs 162 may include three sets of antennas to respectively control three cells (or sectors).Together, the cells of the gNBs 160 and the ng-eNBs 162 may provide radio coverage to the UEs 156 over a wide geographic area to support UE mobility.

[0072] As shown in FIG. 1B, the gNBs 160 and / or the ng-eNBs 162 may be connected to the 5G-CN 152 by means of an NG interface and to other base stations by an Xn interface. The NG and Xn interfaces may be established using direct physical connections and / or indirect connections over an underlying transport network, such as an internet protocol (IP) transport network. The gNBs 160 and / or the ng-eNBs 162 may be connected to the UEs 156 by means of a Uu interface. For example, as illustrated in FIG. 1B, gNB 160A may be connected to the UE 156A by means of a Uu interface. The NG, Xn, and Uu interfaces are associated with a protocol stack. The protocol stacks associated with the interfaces may be used by the network elements in FIG. 1B to exchange data and signaling messages and may include two planes: a user plane and a control plane. The user plane may handle data of interest to a user. The control plane may handle signaling messages of interest to the network elements.

[0073] The gNBs 160 and / or the ng-eNBs 162 may be connected to one or more AMF / UPF functions of the 5G-CN 152, such as the AMF / UPF 158, by means of one or more NG interfaces. For example, the gNB 160A may be connected to the UPF 158B of the AMF / UPF 158 by means of an NG-User plane (NG-U) interface. The NG-U interface may provide delivery (e.g., non-guaranteed delivery) of user plane PDUs between the gNB 160A and the UPF 158B. The gNB 160A may be connected to the AMF 158A by means of an NG-Control plane (NG-C) interface. The NG-C interface may provide, for example, NG interface management, UE context management, UE mobility management, transport of NAS messages, paging, PDU session management, and configuration transfer and / or warning message transmission.

[0074] The gNBs 160 may provide NR user plane and control plane protocol terminations towards the UEs 156 over the Uu interface. For example, the gNB 160A may provide NR user plane and control plane protocol terminations toward the UE 156A over a Uu interface associated with a first protocol stack. The ng-eNBs 162 may provide Evolved UMTS Terrestrial Radio Access (E-UTRA) user plane and control plane protocol terminations towards the UEs 156 over a Uu interface, where E-UTRA refers to the 3GPP 4GDocket No.: 25-1028PCTradio-access technology. For example, the ng-eNB 162B may provide E-UTRA user plane and control plane protocol terminations towards the UE 156B over a Uu interface associated with a second protocol stack.

[0075] The 5G-CN 152 was described as being configured to handle NR and 4G radio accesses. It will be appreciated by one of ordinary skill in the art that it may be possible for NR to connect to a 4G core network in a mode known as “non-standalone operation.” In non-standalone operation, a 4G core network is used to provide (or at least support) control-plane functionality (e.g., initial access, mobility, and paging). Although only one AMF / UPF 158 is shown in FIG. 1B, one gNB or ng-eNB may be connected to multiple AMF / UPF nodes to provide redundancy and / or to load share across the multiple AMF / UPF nodes.

[0076] As discussed, an interface (e.g., Uu, Xn, and NG interfaces) between the network elements in FIG.1 B may be associated with a protocol stack that the network elements use to exchange data and signaling messages. A protocol stack may include two planes: a user plane and a control plane. The user plane may handle data of interest to a user, and the control plane may handle signaling messages of interest to the network elements.

[0077] FIG. 2A and FIG. 2B respectively illustrate examples of NR user plane and NR control plane protocol stacks for the Uu interface that lies between a UE 210 and a gNB 220. The protocol stacks illustrated in FIG. 2A and FIG. 2B may be the same or similar to those used for the Uu interface between, for example, the UE 156A and the gNB 160A shown in FIG. 1 B.

[0078] FIG. 2A illustrates a NR user plane protocol stack comprising five layers implemented in the UE 210 and the gNB 220. At the bottom of the protocol stack, physical layers (PHYs) 211 and 221 may provide transport services to the higher layers of the protocol stack and may correspond to layer 1 of the Open Systems Interconnection (OSI) model. The next four protocols above PHYs 211 and 221 comprise media access control layers (MACs) 212 and 222, radio link control layers (RLCs) 213 and 223, packet data convergence protocol layers (PDCPs) 214 and 224, and service data application protocol layers (SDAPs) 215 and 225. Together, these four protocols may make up layer 2, or the data link layer, of the OSI model.

[0079] FIG. 3 illustrates an example of services provided between protocol layers of the NR user plane protocol stack. Starting from the top of FIG. 2A and FIG. 3, the SDAPs 215 and 225 may perform QoS flow handling. The UE 210 may receive services through a PDU session, which may be a logical connection between the UE 210 and a DN. The PDU session may have one or more QoS flows. A UPF of a CN (e.g., the UPF 158B) may map IP packets to the one or more QoS flows of the PDU session based on QoS requirements (e.g., in terms of delay, data rate, and / or error rate). The SDAPs 215 and 225 may perform mapping / de-mapping between the one or more QoS flows and one or more data radio bearers. The mapping / de-mapping between the QoS flows and the data radio bearers may be determined by the SDAP 225 at the gNB 220. The SDAP 215 at the UE 210 may be informed of the mapping between the QoS flowsDocket No.: 25-1028PCTand the data radio bearers through reflective mapping or control signaling received from the gNB 220. For reflective mapping, the SDAP 225 at the gNB 220 may mark the downlink packets with a QoS flow indicator (QFI), which may be observed by the SDAP 215 at the UE 210 to determine the mapping / de-mapping between the QoS flows and the data radio bearers.

[0080] The PDCPs 214 and 224 may perform header compression / decompression to reduce the amount of data that needs to be transmitted over the air interface, ciphering / deciphering to prevent unauthorized decoding of data transmitted over the air interface, and integrity protection (to ensure control messages originate from intended sources. The PDCPs 214 and 224 may perform retransmissions of undelivered packets, in-sequence delivery and reordering of packets, and removal of packets received in duplicate due to, for example, an intra-g NB handover. The PDCPs 214 and 224 may perform packet duplication to improve the likelihood of the packet being received and, at the receiver, remove any duplicate packets. Packet duplication may be useful for services that require high reliability.

[0081] Although not shown in FIG. 3, PDCPs 214 and 224 may perform mapping / de-mapping between a split radio bearer and RLC channels in a dual connectivity scenario. Dual connectivity is a technique that allows a UE to connect to two cells or, more generally, two cell groups: a master cell group (MCG) and a secondary cell group (SCG). A split bearer is when a single radio bearer, such as one of the radio bearers provided by the PDCPs 214 and 224 as a service to the SDAPs 215 and 225, is handled by cell groups in dual connectivity. The PDCPs 214 and 224 may map / de-map the split radio bearer between RLC channels belonging to cell groups.

[0082] The RLCs 213 and 223 may perform segmentation, retransmission through Automatic Repeat Request (ARQ), and removal of duplicate data units received from MACs 212 and 222, respectively. The RLCs 213 and 223 may support three transmission modes: transparent mode (TM); unacknowledged mode (UM); and acknowledged mode (AM). Based on the transmission mode an RLC is operating, the RLC may perform one or more of the noted functions. The RLC configuration may be per logical channel with no dependency on numerologies and / or Transmission Time Interval (TTI) durations. As shown in FIG. 3, the RLCs 213 and 223 may provide RLC channels as a service to PDCPs 214 and 224, respectively.

[0083] The MACs 212 and 222 may perform multiplexing / demultiplexing of logical channels and / or mapping between logical channels and transport channels. The multiplexing / demultiplexing may include multiplexing / demultiplexing of data units, belonging to the one or more logical channels, into / from Transport Blocks (TBs) delivered to / from the PHYs 211 and 221. The MAC 222 may be configured to perform scheduling, scheduling information reporting, and priority handling between UEs by means of dynamic scheduling. Scheduling may be performed in the gNB 220 (at the MAC 222) for downlink and uplink. The MACs 212 and 222 may be configured to perform error correction through Hybrid Automatic Repeat Request (HARQ) (e.g., one HARQ entity per carrier in case of Carrier Aggregation (CA)), priority handlingDocket No.: 25-1028PCTbetween logical channels of the UE 210 by means of logical channel prioritization, and / or padding. The MACs 212 and 222 may support one or more numerologies and / or transmission timings. In an example, mapping restrictions in a logical channel prioritization may control which numerology and / or transmission timing a logical channel may use. As shown in FIG. 3, the MACs 212 and 222 may provide logical channels as a service to the RLCs 213 and 223.

[0084] The PHYs 211 and 221 may perform mapping of transport channels to physical channels and digital and analog signal processing functions for sending and receiving information over the air interface. These digital and analog signal processing functions may include, for example, coding / decoding and modulation / demodulation. The PHYs 211 and 221 may perform multi-antenna mapping. As shown in FIG.3, the PHYs 211 and 221 may provide one or more transport channels as a service to the MACs 212 and 222.

[0085] FIG. 4A illustrates an example downlink data flow through the NR user plane protocol stack. FIG.4A illustrates a downlink data flow of three IP packets (n, n+1, and m) through the NR user plane protocol stack to generate two TBs at the gNB 220. An uplink data flow through the NR user plane protocol stack may be similar to the downlink data flow depicted in FIG. 4A.

[0086] The downlink data flow of FIG. 4A begins when SDAP 225 receives the three IP packets from one or more QoS flows and maps the three packets to radio bearers. In FIG. 4A, the SDAP 225 maps IP packets n and n+1 to a first radio bearer 402 and maps IP packet m to a second radio bearer 404. An SDAP header (labeled with an "H” in FIG. 4A) is added to an IP packet. The data unit from / to a higher protocol layer is referred to as a service data unit (SDU) of the lower protocol layer and the data unit to / from a lower protocol layer is referred to as a protocol data unit (PDU) of the higher protocol layer. As shown in FIG. 4A, the data unit from the SDAP 225 is an SDU of lower protocol layer PDCP 224 and is a PDU of the SDAP 225.

[0087] The remaining protocol layers in FIG. 4A may perform their associated functionality (e.g , with respect to FIG. 3), add corresponding headers, and forward their respective outputs to the next lower layer. For example, the PDCP 224 may perform IP-header compression and ciphering and forward its output to the RLC 223. The RLC 223 may optionally perform segmentation (e.g., as shown for IP packet m in FIG.4A) and forward its output to the MAC 222 The MAC 222 may multiplex a number of RLC PDUs and may attach a MAC subheader to an RLC PDU to form a transport block. In NR, the MAC subheaders may be distributed across the MAC PDU, as illustrated in FIG. 4A. In LTE, the MAC subheaders may be entirely located at the beginning of the MAC PDU. The NR MAC PDU structure may reduce processing time and associated latency because the MAC PDU subheaders may be computed before the full MAC PDU is assembled.Docket No.: 25-1028PCT

[0088] FIG. 4B illustrates an example format of a MAC subheader in a MAC PDU . The MAC subheader includes: an SDU length field for indicating the length (e.g., in bytes) of the MAC SDU to which the MAC subheader corresponds; a logical channel identifier (LCID) field for identifying the logical channel from which the MAC SDU originated to aid in the demultiplexing process; a flag (F) for indicating the size of the SDU length field; and a reserved bit (R) field for future use.

[0089] FIG. 4B further illustrates MAC control elements (CEs) inserted into the MAC PDU by a MAC, such as MAC 223 or MAC 222. For example, FIG. 4B illustrates two MAC CEs inserted into the MAC PDU. MAC CEs may be inserted at the beginning of a MAC PDU for downlink transmissions (as shown in FIG. 4B) and at the end of a MAC PDU for uplink transmissions. MAC CEs may be used for in-band control signaling. Example MAC CEs include: scheduling-related MAC CEs, such as buffer status reports and power headroom reports; activation / deactivation MAC CEs, such as those for activation / deactivation of PDCP duplication detection, channel state information (CSI) reporting, sounding reference signal (SRS) transmission, and prior configured components; discontinuous reception (DRX) related MAC CEs; timing advance MAC CEs; and random access related MAC CEs. A MAC CE may be preceded by a MAC subheader with a similar format as described for MAC SDUs and may be identified with a reserved value in the LCID field that indicates the type of control information included in the MAC CE.

[0090] Before describing the NR control plane protocol stack, logical channels, transport channels, and physical channels are first described as well as a mapping between the channel types. One or more of the channels may be used to carry out functions associated with the NR control plane protocol stack described later below.

[0091] FIG. 5A and FIG. 5B illustrate, for downlink and uplink respectively, a mapping between logical channels, transport channels, and physical channels. Information is passed through channels between the RLC, the MAC, and the PHY of the NR protocol stack. A logical channel may be used between the RLC and the MAC and may be classified as a control channel that carries control and configuration information in the NR control plane or as a traffic channel that carries data in the NR user plane. A logical channel may be classified as a dedicated logical channel that is dedicated to a specific UE or as a common logical channel that may be used by more than one UE. A logical channel may also be defined by the type of information it carries. The set of logical channels defined by NR include, for example:

[0092] - a paging control channel (PCCH) for carrying paging messages used to page a UE whose location is not known to the network on a cell level;

[0093] - a broadcast control channel (BCCH) for carrying system information messages in the form of a master information block (MIB) and several system information blocks (SIBs), wherein the system information messages may be used by the UEs to obtain information about how a cell is configured and how to operate within the cell;Docket No.: 25-1028PCT

[0094] - a common control channel (CCCH) for carrying control messages together with random access;

[0095] - a dedicated control channel (DCCH) for carrying control messages to / from a specific the UE to configure the UE; and

[0096] - a dedicated traffic channel (DTCH) for carrying user data to / from a specific the UE.

[0097] Transport channels are used between the MAC and PHY layers and may be defined by how the information they carry is transmitted over the air interface. The set of transport channels defined by NR include, for example:

[0098] -- a paging channel (PCH) for carrying paging messages that originated from the PCCH;

[0099] - a broadcast channel (BCH) for carrying the MIB from the BCCH;

[0100] - a downlink shared channel (DL-SCH) for carrying downlink data and signaling messages, including the SIBs from the BCCH;

[0101] - an uplink shared channel (UL-SCH) for carrying uplink data and signaling messages; and

[0102] - a random access channel (RACH) for allowing a UE to contact the network without any prior scheduling.

[0103] The PHY may use physical channels to pass information between processing levels of the PHY. A physical channel may have an associated set of time-frequency resources for carrying the information of one or more transport channels. The PHY may generate control information to support the low-level operation of the PHY and provide the control information to the lower levels of the PHY via physical control channels, known as L1 / L2 control channels. The set of physical channels and physical control channels defined by NR include, for example:

[0104] -- a physical broadcast channel (PBCH) for carrying the MIB from the BCH;

[0105] - a physical downlink shared channel (PDSCH) for carrying downlink data and signaling messages from the DL-SCH, as well as paging messages from the PCH;

[0106] - a physical downlink control channel (PDCCH) for carrying downlink control information (DCI), which may include downlink scheduling commands, uplink scheduling grants, and uplink power control commands;

[0107] - a physical uplink shared channel (PUSCH) for carrying uplink data and signaling messages from the UL-SCH and in some instances uplink control information (UCI) as described below;

[0108] - a physical uplink control channel (PUCCH) for carrying UCI, which may include HARQ acknowledgments, channel quality indicators (CQI), pre-coding matrix indicators (PM I), rank indicators (Rl), and scheduling requests (SR); and

[0109] - a physical random access channel (PRACH) for random access.

[0110] Similar to the physical control channels, the physical layer generates physical signals to support the low-level operation of the physical layer. As shown in FIG. 5A and FIG. 5B, the physical layer signalsDocket No.: 25-1028PCTdefined by NR include: primary synchronization signals (PSS), secondary synchronization signals (SSS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), sounding reference signals (SRS), and phase-tracking reference signals (PT-RS). These physical layer signals will be described in greater detail below.

[0111] FIG. 2B illustrates an example NR control plane protocol stack. As shown in FIG. 2B, the NR control plane protocol stack may use the same / similar first four protocol layers as the example NR user plane protocol stack. These four protocol layers include the PHYs 211 and 221 , the MACs 212 and 222, the RLCs 213 and 223, and the PDCPs 214 and 224. Instead of having the SDAPs 215 and 225 at the top of the stack as in the NR user plane protocol stack, the NR control plane stack has radio resource controls (RRCs) 216 and 226 and NAS protocols 217 and 237 at the top of the NR control plane protocol stack.

[0112] The NAS protocols 217 and 237 may provide control plane functionality between the UE 210 and the AMF 230 (e.g., the AMF 158A) or, more generally, between the UE 210 and the CN. The NAS protocols 217 and 237 may provide control plane functionality between the UE 210 and the AMF 230 via signaling messages, referred to as NAS messages. There is no direct path between the UE 210 and the AMF 230 through which the NAS messages can be transported. The NAS messages may be transported using the AS of the Uu and NG interfaces. NAS protocols 217 and 237 may provide control plane functionality such as authentication, security, connection setup, mobility management, and session management.

[0113] The RRCs 216 and 226 may provide control plane functionality between the UE 210 and the gNB 220 or, more generally, between the UE 210 and the RAN. The RRCs 216 and 226 may provide control plane functionality between the UE 210 and the gNB 220 via signaling messages, referred to as RRC messages. RRC messages may be transmitted between the UE 210 and the RAN using signaling radio bearers and the same / similar PDCP, RLC, MAC, and PHY protocol layers. The MAC may multiplex controlplane and user-plane data into the same transport block (TB). The RRCs 216 and 226 may provide control plane functionality such as: broadcast of system information related to AS and NAS; paging initiated by the CN or the RAN; establishment, maintenance and release of an RRC connection between the UE 210 and the RAN; security functions including key management; establishment, configuration, maintenance and release of signaling radio bearers and data radio bearers; mobility functions; QoS management functions; the UE measurement reporting and control of the reporting; detection of and recovery from radio link failure (RLF); and / or NAS message transfer. As part of establishing an RRC connection, RRCs 216 and 226 may establish an RRC context, which may involve configuring parameters for communication between the UE 210 and the RAN.

[0114] FIG. 6 is an example diagram showing RRC state transitions of a UE. The UE may be the same or similar to the wireless device 106 depicted in FIG. 1A, the UE 210 depicted in FIG. 2A and FIG. 2B, or any other wireless device described in the present disclosure. As illustrated in FIG. 6, a UE may be in at leastDocket No.: 25-1028PCTone of three RRC states: RRC connected 602 (e.g., RRC_CONNECTED), RRC idle 604 (e.g., RRC_I DLE), and RRC inactive 606 (e.g., RRCJNACTIVE).

[0115] In RRC connected 602, the UE has an established RRC context and may have at least one RRC connection with a base station. The base station may be similar to one of the one or more base stations included in the RAN 104 depicted in FIG. 1A, one of the gNBs 160 or ng-eNBs 162 depicted in FIG. 1B, the gNB 220 depicted in FIG. 2A and FIG. 2B, or any other base station described in the present disclosure. The base station with which the UE is connected may have the RRC context for the UE. The RRC context, referred to as the UE context, may comprise parameters for communication between the UE and the base station. These parameters may include, for example: one or more AS contexts; one or more radio link configuration parameters; bearer configuration information (e.g., relating to a data radio bearer, signaling radio bearer, logical channel, QoS flow, and / or PDU session); security information; and / or PHY, MAC, RLC, PDCP, and / or SDAP layer configuration information. While in RRC connected 602, mobility of the UE may be managed by the RAN (e.g., the RAN 104 or the NG-RAN 154). The UE may measure the signal levels (e.g., reference signal levels) from a serving cell and neighboring cells and report these measurements to the base station currently serving the UE. The UE's serving base station may request a handover to a cell of one of the neighboring base stations based on the reported measurements. The RRC state may transition from RRC connected 602 to RRC idle 604 through a connection release procedure 608 or to RRC inactive 606 through a connection inactivation procedure 610.

[0116] In RRC idle 604, an RRC context may not be established for the UE. In RRC idle 604, the UE may not have an RRC connection with the base station. While in RRC idle 604, the UE may be in a sleep state for the majority of the time (e.g., to conserve battery power). The UE may wake up periodically (e.g., once in every discontinuous reception cycle) to monitor for paging messages from the RAN. Mobility of the UE may be managed by the UE through a procedure known as cell reselection. The RRC state may transition from RRC idle 604 to RRC connected 602 through a connection establishment procedure 612, which may involve a random access procedure as discussed in greater detail below.

[0117] In RRC inactive 606, the RRC context previously established is maintained in the UE and the base station. This allows for a fast transition to RRC connected 602 with reduced signaling overhead as compared to the transition from RRC idle 604 to RRC connected 602. While in RRC inactive 606, the UE may be in a sleep state and mobility of the UE may be managed by the UE through cell reselection. The RRC state may transition from RRC inactive 606 to RRC connected 602 through a connection resume procedure 614 or to RRC idle 604 though a connection release procedure 616 that may be the same as or similar to connection release procedure 608.

[0118] An RRC state may be associated with a mobility management mechanism. In RRC idle 604 and RRC inactive 606, mobility is managed by the UE through cell reselection. The purpose of mobilityDocket No.: 25-1028PCTmanagement in RRC idle 604 and RRC inactive 606 is to allow the network to be able to notify the UE of an event via a paging message without having to broadcast the paging message over the entire mobile communications network. The mobility management mechanism used in RRC idle 604 and RRC inactive 606 may allow the network to track the UE on a cell-group level so that the paging message may be broadcast over the cells of the cell group that the UE currently resides within instead of the entire mobile communication network. The mobility management mechanisms for RRC idle 604 and RRC inactive 606 track the UE on a cell-group level. They may do so using different granularities of grouping. For example, there may be three levels of cell-grouping granularity: individual cells; cells within a RAN area identified by a RAN area identifier (RAI); and cells within a group of RAN areas, referred to as a tracking area and identified by a tracking area identifier (TAI).

[0119] Tracking areas may be used to track the UE at the CN level. The CN (e.g., the CN 102 or the 5G-CN 152) may provide the UE with a list of TAIs associated with a UE registration area. If the UE moves, through cell reselection, to a cell associated with a TAI not included in the list of TAIs associated with the UE registration area, the UE may perform a registration update with the CN to allow the CN to update the UE's location and provide the UE with a new the UE registration area.

[0120] RAN areas may be used to track the UE at the RAN level. For a UE in RRC inactive 606 state, the UE may be assigned a RAN notification area. A RAN notification area may comprise one or more cell identities, a list of RAIs, or a list of TAIs. In an example, a base station may belong to one or more RAN notification areas. In an example, a cell may belong to one or more RAN notification areas. If the UE moves, through cell reselection, to a cell not included in the RAN notification area assigned to the UE, the UE may perform a notification area update with the RAN to update the UE's RAN notification area.

[0121] A base station storing an RRC context for a UE or a last serving base station of the UE may be referred to as an anchor base station. An anchor base station may maintain an RRC context for the UE at least during a period of time that the UE stays in a RAN notification area of the anchor base station and / or during a period of time that the UE stays in RRC inactive 606.

[0122] A g N B, such as gNBs 160 in FIG. 1 B, may be split into two parts: a central unit (gNB-CU), and one or more distributed units (gNB-DU). A gNB-CU may be coupled to one or more gNB-DUs using an F1 interface. The gNB-CU may comprise the RRC, the PDCP, and the SDAP. A gNB-DU may comprise the RLC, the MAC, and the PHY.

[0123] In NR, the physical signals and physical channels (discussed with respect to FIG. 5A and FIG. 5B) may be mapped onto orthogonal frequency divisional multiplexing (OFDM) symbols. OFDM is a multicarrier communication scheme that transmits data over F orthogonal subcarriers (or tones). Before transmission, the data may be mapped to a series of complex symbols (e.g., M-quadrature amplitude modulation (M-QAM) or M-phase shift keying (M-PSK) symbols), referred to as source symbols, and divided into F parallelDocket No.: 25-1028PCTsymbol streams. The F parallel symbol streams may be treated as though they are in the frequency domain and used as inputs to an Inverse Fast Fourier Transform (IFFT) block that transforms them into the time domain. The IFFT block may take in F source symbols at a time, one from each of the F parallel symbol streams, and use each source symbol to modulate the amplitude and phase of one of F sinusoidal basis functions that correspond to the F orthogonal subcarriers. The output of the IFFT block may be F timedomain samples that represent the summation of the F orthogonal subcarriers. The F time-domain samples may form a single OFDM symbol. After some processing (e.g., addition of a cyclic prefix) and up-conversion, an OFDM symbol provided by the IFFT block may be transmitted over the air interface on a carrier frequency. The F parallel symbol streams may be mixed using an FFT block before being processed by the IFFT block. This operation produces Discrete Fourier Transform (DFT)-precoded OFDM symbols and may be used by UEs in the uplink to reduce the peak to average power ratio (PAPR). Inverse processing may be performed on the OFDM symbol at a receiver using an FFT block to recover the data mapped to the source symbols.

[0124] FIG. 7 illustrates an example configuration of an NR frame into which OFDM symbols are grouped. An NR frame may be identified by a system frame number (SFN). The SFN may repeat with a period of 1024 frames. As illustrated, one NR frame may be 10 milliseconds (ms) in duration and may include 10 subframes that are 1 ms in duration. A subframe may be divided into slots that include, for example, 14 OFDM symbols per slot.

[0125] The duration of a slot may depend on the numerology used for the OFDM symbols of the slot. In NR, a flexible numerology is supported to accommodate different cell deployments (e.g., cells with carrier frequencies below 1 GHz up to cells with carrier frequencies in the mm-wave range). A numerology may be defined in terms of subcarrier spacing and cyclic prefix duration. For a numerology in NR, subcarrier spacings may be scaled up by powers of two from a baseline subcarrier spacing of 15 kHz, and cyclic prefix durations may be scaled down by powers of two from a baseline cyclic prefix duration of 4.7 ps. For example, NR defines numerologies with the following subcarrier spacing / cyclic prefix duration combinations: 15 kHz / 4.7 ps; 30 kHz / 2.3 ps; 60 kHz / 1.2 ps; 120 kHz / 0.59 ps; and 240 kHz / 0.29 ps.

[0126] A slot may have a fixed number of OFDM symbols (e.g., 14 OFDM symbols). A numerology with a higher subcarrier spacing has a shorter slot duration and, correspondingly, more slots per subframe. FIG. 7 illustrates this numerology-dependent slot duration and slots-per-subframe transmission structure (the numerology with a subcarrier spacing of 240 kHz is not shown in FIG. 7 for ease of illustration). A subframe in NR may be used as a numerology-independent time reference, while a slot may be used as the unit upon which uplink and downlink transmissions are scheduled. To support low latency, scheduling in NR may be decoupled from the slot duration and start at any OFDM symbol and last for as many symbols asDocket No.: 25-1028PCTneeded for a transmission. These partial slot transmissions may be referred to as mini-slot or subslot transmissions.

[0127] FIG. 8 illustrates an example configuration of a slot in the time and frequency domain for an NR carrier. The slot includes resource elements (REs) and resource blocks (RBs). An RE is the smallest physical resource in NR. An RE spans one OFDM symbol in the time domain by one subcarrier in the frequency domain as shown in FIG. 8. An RB spans twelve consecutive REs in the frequency domain as shown in FIG. 8. An NR carrier may be limited to a width of 275 RBs or 275x12 = 3300 subcarriers. Such a limitation, if used, may limit the NR carrier to 50, 100, 200, and 400 MHz for subcarrier spacings of 15, 30, 60, and 120 kHz, respectively, where the 400 MHz bandwidth may be set based on a 400 MHz per carrier bandwidth limit.

[0128] FIG. 8 illustrates a single numerology being used across the entire bandwidth of the NR carrier. In other example configurations, multiple numerologies may be supported on the same carrier.

[0129] NR may support wide carrier bandwidths (e.g., up to 400 MHz for a subcarrier spacing of 120 kHz). Not all UEs may be able to receive the full carrier bandwidth (e.g., due to hardware limitations). Also, receiving the full carrier bandwidth may be prohibitive in terms of UE power consumption. In an example, to reduce power consumption and / or for other purposes, a UE may adapt the size of the UE's receive bandwidth based on the amount of traffic the UE is scheduled to receive. This is referred to as bandwidth adaptation.

[0130] NR defines bandwidth parts (BWPs) to support UEs not capable of receiving the full carrier bandwidth and to support bandwidth adaptation. In an example, a BWP may be defined by a subset of contiguous RBs on a carrier. A UE may be configured (e.g., via RRC layer) with one or more downlink BWPs and one or more uplink BWPs per serving cell (e.g., up to four downlink BWPs and up to four uplink BWPs per serving cell). At a given time, one or more of the configured BWPs for a serving cell may be active These one or more BWPs may be referred to as active BWPs of the serving cell. When a serving cell is configured with a secondary uplink carrier, the serving cell may have one or more first active BWPs in the uplink carrier and one or more second active BWPs in the secondary uplink carrier.

[0131] For unpaired spectra, a downlink BWP from a set of configured downlink BWPs may be linked with an uplink BWP from a set of configured uplink BWPs if a downlink BWP index of the downlink BWP and an uplink BWP index of the uplink BWP are the same. For unpaired spectra, a UE may expect that a center frequency for a downlink BWP is the same as a center frequency for an uplink BWP.

[0132] For a downlink BWP in a set of configured downlink BWPs on a primary cell (PCell), a base station may configure a UE with one or more control resource sets (CORESETs) for at least one search space. A search space is a set of locations in the time and frequency domains where the UE may find control information. The search space may be a UE-specific search space or a common search space (potentiallyDocket No.: 25-1028PCTusable by a plurality of UEs). For example, a base station may configure a UE with a common search space, on a PCell or on a primary secondary cell (PSCell), in an active downlink BWP.

[0133] For an uplink BWP in a set of configured uplink BWPs, a BS may configure a UE with one or more resource sets for one or more PUCCH transmissions. A UE may receive downlink receptions (e.g., PDCCH or PDSCH) in a downlink BWP according to a configured numerology (e.g., subcarrier spacing and cyclic prefix duration) for the downlink BWP. The UE may transmit uplink transmissions (e.g., PUCCH or PUSCH) in an uplink BWP according to a configured numerology (e.g., subcarrier spacing and cyclic prefix length for the uplink BWP).

[0134] One or more BWP indicator fields may be provided in Downlink Control Information (DCI). A value of a BWP indicator field may indicate which BWP in a set of configured BWPs is an active downlink BWP for one or more downlink receptions. The value of the one or more BWP indicator fields may indicate an active uplink BWP for one or more uplink transmissions.

[0135] A base station may semi-statically configure a UE with a default downlink BWP within a set of configured downlink BWPs associated with a PCell. If the base station does not provide the default downlink BWP to the UE, the default downlink BWP may be an initial active downlink BWP. The UE may determine which BWP is the initial active downlink BWP based on a CORESET configuration obtained using the PBCH.

[0136] A base station may configure a UE with a BWP inactivity timer value for a PCell. The UE may start or restart a BWP inactivity timer at any appropriate time. For example, the UE may start or restart the BWP inactivity timer (a) when the UE detects a DCI indicating an active downlink BWP other than a default downlink BWP for a paired spectra operation; or (b) when a UE detects a DCI indicating an active downlink BWP or active uplink BWP other than a default downlink BWP or uplink BWP for an unpaired spectra operation. If the UE does not detect DCI during an interval of time (e.g., 1 ms or 0.5 ms), the UE may run the BWP inactivity timer toward expiration (for example, increment from zero to the BWP inactivity timer value, or decrement from the BWP inactivity timer value to zero). When the BWP inactivity timer expires, the UE may switch from the active downlink BWP to the default downlink BWP.

[0137] In an example, a base station may semi-statically configure a UE with one or more BWPs. A UE may switch an active BWP from a first BWP to a second BWP in response to receiving a DCI indicating the second BWP as an active BWP and / or in response to an expiry of the BWP inactivity timer (e.g., if the second BWP is the default BWP).

[0138] Downlink and uplink BWP switching (where BWP switching refers to switching from a currently active BWP to a not currently active BWP) may be performed independently in paired spectra. In unpaired spectra, downlink and uplink BWP switching may be performed simultaneously Switching betweenDocket No.: 25-1028PCTconfigured BWPs may occur based on RRC signaling, DCI, expiration of a BWP inactivity timer, and / or an initiation of random access.

[0139] FIG. 9 illustrates an example of bandwidth adaptation using three configured BWPs for an NR carrier. A UE configured with the three BWPs may switch from one BWP to another BWP at a switching point. In the example illustrated in FIG. 9, the BWPs include: a BWP 902 with a bandwidth of 40 MHz and a subcarrier spacing of 15 kHz; a BWP 904 with a bandwidth of 10 MHz and a subcarrier spacing of 15 kHz; and a BWP 906 with a bandwidth of 20 MHz and a subcarrier spacing of 60 kHz. The BWP 902 may be an initial active BWP, and the BWP 904 may be a default BWP. The UE may switch between BWPs at switching points. In the example of FIG. 9, the UE may switch from the BWP 902 to the BWP 904 at a switching point 908. The switching at the switching point 908 may occur for any suitable reason, for example, in response to an expiry of a BWP inactivity timer (indicating switching to the default BWP) and / or in response to receiving a DCI indicating BWP 904 as the active BWP. The UE may switch at a switching point 910 from active BWP 904 to BWP 906 in response to receiving a DCI indicating BWP 906 as the active BWP. The UE may switch at a switching point 912 from active BWP 906 to BWP 904 in response to an expiry of a BWP inactivity timer and / or in response to receiving a DCI indicating BWP 904 as the active BWP. The UE may switch at a switching point 914 from active BWP 904 to BWP 902 in response to receiving a DCI indicating BWP 902 as the active BWP.

[0140] If a UE is configured for a secondary cell with a default downlink BWP in a set of configured downlink BWPs and a timer value, UE procedures for switching BWPs on a secondary cell may be the same / similar as those on a primary cell. For example, the UE may use the timer value and the default downlink BWP for the secondary cell in the same / similar manner as the UE would use these values for a primary cell.

[0141] To provide for greater data rates, two or more carriers can be aggregated and simultaneously transmitted to / from the same UE using carrier aggregation (CA). The aggregated carriers in CA may be referred to as component carriers (CCs). When CA is used, there are a number of serving cells for the UE, one for a CC. The CCs may have three configurations in the frequency domain.

[0142] FIG. 10A illustrates the three CA configurations with two CCs. In the intraband, contiguous configuration 1002, the two CCs are aggregated in the same frequency band (frequency band A) and are located directly adjacent to each other within the frequency band. In the intraband, non-contiguous configuration 1004, the two CCs are aggregated in the same frequency band (frequency band A) and are separated in the frequency band by a gap. In the interband configuration 1006, the two CCs are located in frequency bands (frequency band A and frequency band B).

[0143] In an example, up to 32 CCs may be aggregated. The aggregated CCs may have the same or different bandwidths, subcarrier spacing, and / or duplexing schemes (TDD or FDD). A serving cell for a UEDocket No.: 25-1028PCTusing CA may have a downlink CC. For FDD, one or more uplink CCs may be optionally configured for a serving cell. The ability to aggregate more downlink carriers than uplink carriers may be useful, for example, when the UE has more data traffic in the downlink than in the uplink.

[0144] When CA is used, one of the aggregated cells for a UE may be referred to as a primary cell (PCell). The PCell may be the serving cell that the UE initially connects to at RRC connection establishment, reestablishment, and / or handover. The PCell may provide the UE with NAS mobility information and the security input. UEs may have different PCells. In the downlink, the carrier corresponding to the PCell may be referred to as the downlink primary CC (DL PCC). In the uplink, the carrier corresponding to the PCell may be referred to as the uplink primary CC (UL PCC). The other aggregated cells for the UE may be referred to as secondary cells (SCells). In an example, the SCells may be configured after the PCell is configured for the UE. For example, an SCell may be configured through an RRC Connection Reconfiguration procedure. In the downlink, the carrier corresponding to an SCell may be referred to as a downlink secondary CC (DL SCC). In the uplink, the carrier corresponding to the SCell may be referred to as the uplink secondary CC (UL SCC).

[0145] Configured SCells for a UE may be activated and deactivated based on, for example, traffic and channel conditions. Deactivation of an SCell may mean that PDCCH and PDSCH reception on the SCell is stopped and PUSCH, SRS, and CQI transmissions on the SCell are stopped. Configured SCells may be activated and deactivated using a MAC CE with respect to FIG. 4B. For example, a MAC CE may use a bitmap (e.g., one bit per SCell) to indicate which SCells (e.g., in a subset of configured SCells) for the UE are activated or deactivated. Configured SCells may be deactivated in response to an expiration of an SCell deactivation timer (e.g., one SCell deactivation timer per SCell).

[0146] Downlink control information, such as scheduling assignments and scheduling grants, for a cell may be transmitted on the cell corresponding to the assignments and grants, which is known as selfscheduling. The DCI for the cell may be transmitted on another cell, which is known as cross-carrier scheduling. Uplink control information (e.g., HARQ acknowledgments and channel state feedback, such as CQI, PMI, and / or Rl) for aggregated cells may be transmitted on the PUCCH of the PCell. For a larger number of aggregated downlink CCs, the PUCCH of the PCell may become overloaded. Cells may be divided into multiple PUCCH groups.

[0147] FIG. 10B illustrates an example of how aggregated cells may be configured into one or more PUCCH groups. A PUCCH group 1010 and a PUCCH group 1050 may include one or more downlink CCs, respectively. In the example of FIG. 10B, the PUCCH group 1010 includes three downlink CCs: a PCell 1011, an SCell 1012, and an SCell 1013. The PUCCH group 1050 includes three downlink CCs in the present example: a PCell 1051 , an SCell 1052, and an SCell 1053. One or more uplink CCs may be configured as a PCell 1021, an SCell 1022, and an SCell 1023. One or more other uplink CCs may beDocket No.: 25-1028PCTconfigured as a primary SCell (PSCell) 1061, an SCell 1062, and an SCell 1063. Uplink control information (UCI) related to the downlink CCs of the PUCCH group 1010, shown as UC1 1031, UC1 1032, and UCI 1033, may be transmitted in the uplink of the PCell 1021. Uplink control information (UCI) related to the downlink CCs of the PUCCH group 1050, shown as UC1 1071, UC1 1072, and UC1 1073, may be transmitted in the uplink of the PSCell 1061. In an example, if the aggregated cells depicted in FIG. 10B were not divided into the PUCCH group 1010 and the PUCCH group 1050, a single uplink PCell to transmit UCI relating to the downlink CCs, and the PCell may become overloaded. By dividing transmissions of UCI between the PCell 1021 and the PSCell 1061, overloading may be prevented.

[0148] A cell, comprising a downlink carrier and optionally an uplink carrier, may be assigned with a physical cell ID and a cell index. The physical cell ID or the cell index may identify a downlink carrier and / or an uplink carrier of the cell, for example, depending on the context in which the physical cell ID is used. A physical cell ID may be determined using a synchronization signal transmitted on a downlink component carrier. A cell index may be determined using RRC messages. In the disclosure, a physical cell ID may be referred to as a carrier ID, and a cell index may be referred to as a carrier index. For example, when the disclosure refers to a first physical cell ID for a first downlink carrier, the disclosure may mean the first physical cell ID is for a cell comprising the first downlink carrier. The same / similar concept may apply to, for example, a carrier activation. When the disclosure indicates that a first carrier is activated, the specification may mean that a cell comprising the first carrier is activated.

[0149] In CA, a multi-carrier nature of a PHY may be exposed to a MAC. In an example, a HARQ entity may operate on a serving cell. A transport block may be generated per assignment / grant per serving cell. A transport block and potential HARQ retransmissions of the transport block may be mapped to a serving cell.

[0150] In the downlink, a base station may transmit (e.g., unicast, multicast, and / or broadcast) one or more Reference Signals (RSs) to a UE (e.g., PSS, SSS, CSI-RS, DMRS, and / or PT-RS, as shown in FIG.5A). In the uplink, the UE may transmit one or more RSs to the base station (e.g., DMRS, PT-RS, and / or SRS, as shown in FIG. 5B). The PSS and the SSS may be transmitted by the base station and used by the UE to synchronize the UE to the base station. The PSS and the SSS may be provided in a synchronization signal (SS) / physical broadcast channel (PBCH) block that includes the PSS, the SSS, and the PBCH. The base station may periodically transmit a burst of SS / PBCH blocks.

[0151] FIG. 11A illustrates an example of an SS / PBCH block's structure and location. A burst of SS / PBCH blocks may include one or more SS / PBCH blocks (e.g., 4 SS / PBCH blocks, as shown in FIG. 11A). Bursts may be transmitted periodically (e.g., every 2 frames or 20 ms). A burst may be restricted to a half-frame (e.g , a first half-frame having a duration of 5 ms). It will be understood that FIG. 11A is an example, and that these parameters (number of SS / PBCH blocks per burst, periodicity of bursts, position of burst withinDocket No.: 25-1028PCTthe frame) may be configured based on, for example: a carrier frequency of a cell in which the SS / PBCH block is transmitted; a numerology or subcarrier spacing of the cell; a configuration by the network (e.g., using RRC signaling); or any other suitable factor. In an example, the UE may assume a subcarrier spacing for the SS / PBCH block based on the carrier frequency being monitored, unless the radio network configured the UE to assume a different subcarrier spacing.

[0152] The SS / PBCH block may span one or more OFDM symbols in the time domain (e.g., 4 OFDM symbols, as shown in the example of FIG. 11 A) and may span one or more subcarriers in the frequency domain (e.g., 240 contiguous subcarriers). The PSS, the SSS, and the PBCH may have a common center frequency. The PSS may be transmitted first and may span, for example, 1 OFDM symbol and 127 subcarriers. The SSS may be transmitted after the PSS (e.g., two symbols later) and may span 1 OFDM symbol and 127 subcarriers. The PBCH may be transmitted after the PSS (e.g., across the next 3 OFDM symbols) and may span 240 subcarriers.

[0153] The location of the SS / PBCH block in the time and frequency domains may not be known to the UE (e.g., if the UE is searching for the cell). To find and select the cell, the UE may monitor a carrier for the PSS. For example, the UE may monitor a frequency location within the carrier. If the PSS is not found after a certain duration (e.g., 20 ms), the UE may search for the PSS at a different frequency location within the carrier, as indicated by a synchronization raster. If the PSS is found at a location in the time and frequency domains, the UE may determine, based on a known structure of the SS / PBCH block, the locations of the SSS and the PBCH, respectively. The SS / PBCH block may be a cell-defining SS block (CD-SSB). In an example, a primary cell may be associated with a CD-SSB. The CD-SSB may be located on a synchronization raster. In an example, a cell selection / search and / or reselection may be based on the CD-SSB.

[0154] The SS / PBCH block may be used by the UE to determine one or more parameters of the cell. For example, the UE may determine a physical cell identifier (PCI) of the cell based on the sequences of the PSS and the SSS, respectively. The UE may determine a location of a frame boundary of the cell based on the location of the SS / PBCH block. For example, the SS / PBCH block may indicate that it has been transmitted in accordance with a transmission pattern, wherein a SS / PBCH block in the transmission pattern is a known distance from the frame boundary.

[0155] The PBCH may use a QPSK modulation and may use forward error correction (FEC). The FEC may use polar coding. One or more symbols spanned by the PBCH may carry one or more DMRSs for demodulation of the PBCH. The PBCH may include an indication of a current system frame number (SFN) of the cell and / or a SS / PBCH block timing index. These parameters may facilitate time synchronization of the UE to the base station. The PBCH may include a master information block (MIB) used to provide the UE with one or more parameters. The MIB may be used by the UE to locate remaining minimum systemDocket No.: 25-1028PCTinformation (RMSI) associated with the cell. The RMS I may include a System Information Block Type 1 (SIB1 ). The SIB1 may contain information needed by the UE to access the cell. The UE may use one or more parameters of the MIB to monitor PDCCH, which may be used to schedule PDSCH. The PDSCH may include the SIB1. The SIB1 may be decoded using parameters provided in the MIB. The PBCH may indicate an absence of SIB1. Based on the PBCH indicating the absence of SIB1 , the UE may be pointed to a frequency. The UE may search for an SS / PBCH block at the frequency to which the UE is pointed.

[0156] The UE may assume that one or more SS / PBCH blocks transmitted with a same SS / PBCH block index are quasi co-located (QCLed) (e.g., having the same / similar Doppler spread, Doppler shift, average gain, average delay, and / or spatial Rx parameters). The UE may not assume QCL for SS / PBCH block transmissions having different SS / PBCH block indices.

[0157] SS / PBCH blocks (e.g., those within a half-frame) may be transmitted in spatial directions (e.g., using different beams that span a coverage area of the cell). In an example, a first SS / PBCH block may be transmitted in a first spatial direction using a first beam, and a second SS / PBCH block may be transmitted in a second spatial direction using a second beam.

[0158] In an example, within a frequency span of a carrier, a base station may transmit a plurality of SS / PBCH blocks. In an example, a first PCI of a first SS / PBCH block of the plurality of SS / PBCH blocks may be different from a second PCI of a second SS / PBCH block of the plurality of SS / PBCH blocks. The PCIs of SS / PBCH blocks transmitted in different frequency locations may be different or the same.

[0159] The CSI-RS may be transmitted by the base station and used by the UE to acquire channel state information (CSI). The base station may configure the UE with one or more CSI-RSs for channel estimation or any other suitable purpose. The base station may configure a UE with one or more of the same / similar CSI-RSs. The UE may measure the one or more CSI-RSs. The UE may estimate a downlink channel state and / or generate a CSI report based on the measuring of the one or more downlink CSI-RSs. The UE may provide the CSI report to the base station. The base station may use feedback provided by the UE (e.g., the estimated downlink channel state) to perform link adaptation.

[0160] The base station may semi-statically configure the UE with one or more CSI-RS resource sets. A CSI-RS resource may be associated with a location in the time and frequency domains and a periodicity. The base station may selectively activate and / or deactivate a CSI-RS resource The base station may indicate to the UE that a CSI-RS resource in the CSI-RS resource set is activated and / or deactivated.

[0161] The base station may configure the UE to report CSI measurements. The base station may configure the UE to provide CSI reports periodically, aperiodically, or semi-persistently. For periodic CSI reporting, the UE may be configured with a timing and / or periodicity of a plurality of CSI reports. For aperiodic CSI reporting, the base station may request a CSI report. For example, the base station may command the UE to measure a configured CSI-RS resource and provide a CSI report relating to theDocket No.: 25-1028PCTmeasurements. For semi-persistent CSI reporting, the base station may configure the UE to transmit periodically, and selectively activate or deactivate the periodic reporting. The base station may configure the UE with a CSI-RS resource set and CSI reports using RRC signaling.

[0162] The CSI-RS configuration may comprise one or more parameters indicating, for example, up to 32 antenna ports. The UE may be configured to employ the same OFDM symbols for a downlink CSI-RS and a control resource set (CORESET) when the downlink CSI-RS and CORESET are spatially QCLed and resource elements associated with the downlink CSI-RS are outside of the physical resource blocks (PRBs) configured for the CORESET. The UE may be configured to employ the same OFDM symbols for downlink CSI-RS and SS / PBCH blocks when the downlink CSI-RS and SS / PBCH blocks are spatially QCLed and resource elements associated with the downlink CSI-RS are outside of PRBs configured for the SS / PBCH blocks.

[0163] Downlink DMRSs may be transmitted by a base station and used by a UE for channel estimation. For example, the downlink DMRS may be used for coherent demodulation of one or more downlink physical channels (e.g. , PDSCH). An NR network may support one or more variable and / or configurable DMRS patterns for data demodulation At least one downlink DMRS configuration may support a front-loaded DMRS pattern. A front-loaded DMRS may be mapped over one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). A base station may semi-statically configure the UE with a number (e.g. a maximum number) of front-loaded DMRS symbols for PDSCH. A DMRS configuration may support one or more DMRS ports. For example, for single user-MIMO, a DMRS configuration may support up to eight orthogonal downlink DMRS ports per UE. For multiuser-MIMO, a DMRS configuration may support up to 4 orthogonal downlink DMRS ports per UE. A radio network may support (e.g., at least for CP-OFDM) a common DMRS structure for downlink and uplink, wherein a DMRS location, a DMRS pattern, and / or a scrambling sequence may be the same or different. The base station may transmit a downlink DMRS and a corresponding PDSCH using the same precoding matrix. The UE may use the one or more downlink DMRSs for coherent demodulation / channel estimation of the PDSCH.

[0164] In an example, a transmitter (e.g., a base station) may use a precoder matrices for a part of a transmission bandwidth. For example, the transmitter may use a first precoder matrix for a first bandwidth and a second precoder matrix for a second bandwidth. The first precoder matrix and the second precoder matrix may be different based on the first bandwidth being different from the second bandwidth. The UE may assume that a same precoding matrix is used across a set of PRBs. The set of PRBs may be denoted as a precoding resource block group (PRG).

[0165] A PDSCH may comprise one or more layers. The UE may assume that at least one symbol with DMRS is present on a layer of the one or more layers of the PDSCH. A higher layer may configure up to 3 DMRSs for the PDSCH.Docket No.: 25-1028PCT

[0166] Downlink PT-RS may be transmitted by a base station and used by a UE for phase-noise compensation. Whether a downlink PT-RS is present or not may depend on an RRC configuration. The presence and / or pattern of the downlink PT-RS may be configured on a UE-specific basis using a combination of RRC signaling and / or an association with one or more parameters employed for other purposes (e.g., modulation and coding scheme (MCS)), which may be indicated by DCI. When configured, a dynamic presence of a downlink PT-RS may be associated with one or more DCI parameters comprising at least MCS. An NR network may support a plurality of PT-RS densities defined in the time and / or frequency domains. When present, a frequency domain density may be associated with at least one configuration of a scheduled bandwidth. The UE may assume a same precoding for a DMRS port and a PT-RS port. A number of PT-RS ports may be fewer than a number of DMRS ports in a scheduled resource. Downlink PT-RS may be confined in the scheduled time / frequency duration for the UE. Downlink PT-RS may be transmitted on symbols to facilitate phase tracking at the receiver.

[0167] The UE may transmit an uplink DMRS to a base station for channel estimation. For example, the base station may use the uplink DMRS for coherent demodulation of one or more uplink physical channels. For example, the UE may transmit an uplink DMRS with a PUSCH and / or a PUCCH. The uplink DM-RS may span a range of frequencies that is similar to a range of frequencies associated with the corresponding physical channel. The base station may configure the UE with one or more uplink DMRS configurations. At least one DMRS configuration may support a front-loaded DMRS pattern. The front-loaded DMRS may be mapped over one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more uplink DMRSs may be configured to transmit at one or more symbols of a PUSCH and / or a PUCCH. The base station may semi-statically configure the UE with a number (e.g. maximum number) of front-loaded DMRS symbols for the PUSCH and / or the PUCCH, which the UE may use to schedule a single-symbol DMRS and / or a double-symbol DMRS. An NR network may support (e.g., for cyclic prefix orthogonal frequency division multiplexing (CP-OFDM)) a common DMRS structure for downlink and uplink, wherein a DMRS location, a DMRS pattern, and / or a scrambling sequence for the DMRS may be the same or different.

[0168] A PUSCH may comprise one or more layers, and the UE may transmit at least one symbol with DMRS present on a layer of the one or more layers of the PUSCH. In an example, a higher layer may configure up to three DMRSs for the PUSCH.

[0169] Uplink PT-RS (which may be used by a base station for phase tracking and / or phase-noise compensation) may or may not be present depending on an RRC configuration of the UE. The presence and / or pattern of uplink PT-RS may be configured on a UE-specific basis by a combination of RRC signaling and / or one or more parameters employed for other purposes (e.g., Modulation and Coding Scheme (MCS)), which may be indicated by DCI. When configured, a dynamic presence of uplink PT-RS may be associated with one or more DCI parameters comprising at least MCS. A radio network mayDocket No.: 25-1028PCTsupport a plurality of uplink PT-RS densities defined in time / frequency domain. When present, a frequency domain density may be associated with at least one configuration of a scheduled bandwidth. The UE may assume a same precoding for a DMRS port and a PT-RS port. A number of PT-RS ports may be fewer than a number of DMRS ports in a scheduled resource. For example, uplink PT-RS may be confined in the scheduled time / frequency duration for the UE.

[0170] SRS may be transmitted by a UE to a base station for channel state estimation to support uplink channel dependent scheduling and / or link adaptation. SRS transmitted by the UE may allow a base station to estimate an uplink channel state at one or more frequencies. A scheduler at the base station may employ the estimated uplink channel state to assign one or more resource blocks for an uplink PUSCH transmission from the UE. The base station may semi-statically configure the UE with one or more SRS resource sets. For an SRS resource set, the base station may configure the UE with one or more SRS resources. An SRS resource set applicability may be configured by a higher layer (e.g., RRC) parameter. For example, when a higher layer parameter indicates beam management, an SRS resource in an SRS resource set of the one or more SRS resource sets (e.g., with the same / similar time domain behavior, periodic, aperiodic, and / or the like) may be transmitted at a time instant (e.g., simultaneously). The UE may transmit one or more SRS resources in SRS resource sets. An NR network may support aperiodic, periodic and / or semi-persistent SRS transmissions. The UE may transmit SRS resources based on one or more trigger types, wherein the one or more trigger types may comprise higher layer signaling (e.g., RRC) and / or one or more DCI formats. In an example, at least one DCI format may be employed for the UE to select at least one of one or more configured SRS resource sets. An SRS trigger type 0 may refer to an SRS triggered based on a higher layer signaling. An SRS trigger type 1 may refer to an SRS triggered based on one or more DCI formats. In an example, when PUSCH and SRS are transmitted in a same slot, the UE may be configured to transmit SRS after a transmission of a PUSCH and a corresponding uplink DMRS.

[0171] The base station may semi-statically configure the UE with one or more SRS configuration parameters indicating at least one of following: a SRS resource configuration identifier; a number of SRS ports; time domain behavior of an SRS resource configuration (e.g., an indication of periodic, semi-persistent, or aperiodic SRS); slot, mini-slot, and / or subframe level periodicity; offset for a periodic and / or an aperiodic SRS resource; a number of OFDM symbols in an SRS resource; a starting OFDM symbol of an SRS resource; an SRS bandwidth; a frequency hopping bandwidth; a cyclic shift; and / or an SRS sequence ID.

[0172] An antenna port is defined such that the channel over which a symbol on the antenna port is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed. If a first symbol and a second symbol are transmitted on the same antenna port, the receiver may infer the channel (e.g., fading gain, multipath delay, and / or the like) for conveying the second symbolDocket No.: 25-1028PCTon the antenna port, from the channel for conveying the first symbol on the antenna port. A first antenna port and a second antenna port may be referred to as quasi co-located (QCLed) if one or more large-scale properties of the channel over which a first symbol on the first antenna port is conveyed may be inferred from the channel over which a second symbol on a second antenna port is conveyed. The one or more large-scale properties may comprise at least one of: a delay spread; a Doppler spread; a Doppler shift; an average gain; an average delay; and / or spatial Receiving (Rx) parameters.

[0173] Channels that use beamforming require beam management. Beam management may comprise beam measurement, beam selection, and beam indication. A beam may be associated with one or more reference signals. For example, a beam may be identified by one or more beamformed reference signals. The UE may perform downlink beam measurement based on downlink reference signals (e.g., a channel state information reference signal (CSI-RS)) and generate a beam measurement report. The UE may perform the downlink beam measurement procedure after an RRC connection is set up with a base station.

[0174] FIG. 11B illustrates an example of channel state information reference signals (CSI-RSs) that are mapped in the time and frequency domains. A square shown in FIG. 11B may span a resource block (RB) within a bandwidth of a cell. A base station may transmit one or more RRC messages comprising CSI-RS resource configuration parameters indicating one or more CSI-RSs. One or more of the following parameters may be configured by higher layer signaling (e.g., RRC and / or MAC signaling) for a CSI-RS resource configuration: a CSI-RS resource configuration identity, a number of CSI-RS ports, a CSI-RS configuration (e.g., symbol and resource element (RE) locations in a subframe), a CSI-RS subframe configuration (e.g., subframe location, offset, and periodicity in a radio frame), a CSI-RS power parameter, a CSI-RS sequence parameter, a code division multiplexing (CDM) type parameter, a frequency density, a transmission comb, quasi co-location (QCL) parameters (e.g., QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid), and / or other radio resource parameters.

[0175] The three beams illustrated in FIG. 11 B may be configured for a UE in a UE-specific configuration. Three beams are illustrated in FIG. 11 B (beam #1 , beam #2, and beam #3), more or fewer beams may be configured. Beam #1 may be allocated with CSI-RS 1101 that may be transmitted in one or more subcarriers in an RB of a first symbol. Beam #2 may be allocated with CSI-RS 1102 that may be transmitted in one or more subcarriers in an RB of a second symbol. Beam #3 may be allocated with CSI-RS 1103 that may be transmitted in one or more subcarriers in an RB of a third symbol. By using frequency division multiplexing (EDM), a base station may use other subcarriers in a same RB (for example, those that are not used to transmit CSI-RS 1101) to transmit another CSI-RS associated with a beam for another UE. By using time domain multiplexing (TDM), beams used for the UE may be configured such that beams for the UE use symbols from beams of other UEs.Docket No.: 25-1028PCT

[0176] CSI-RSs such as those illustrated in FIG 11 B (e.g., CSI-RS 1101, 1102, 1103) may be transmitted by the base station and used by the UE for one or more measurements. For example, the UE may measure a reference signal received power (RSRP) of configured CSI-RS resources. The base station may configure the UE with a reporting configuration and the UE may report the RSRP measurements to a network (for example, via one or more base stations) based on the reporting configuration. In an example, the base station may determine, based on the reported measurement results, one or more transmission configuration indication (TCI) states comprising a number of reference signals. In an example, the base station may indicate one or more TCI states to the UE (e.g., via RRC signaling, a MAC CE, and / or a DCI). The UE may receive a downlink transmission with a receive (Rx) beam determined based on the one or more TCI states. In an example, the UE mayor may not have a capability of beam correspondence. If the UE has the capability of beam correspondence, the UE may determine a spatial domain filter of a transmit (Tx) beam based on a spatial domain filter of the corresponding Rx beam. If the UE does not have the capability of beam correspondence, the UE may perform an uplink beam selection procedure to determine the spatial domain filter of the Tx beam. The UE may perform the uplink beam selection procedure based on one or more sounding reference signal (SRS) resources configured to the UE by the base station The base station may select and indicate uplink beams for the UE based on measurements of the one or more SRS resources transmitted by the UE.

[0177] In a beam management procedure, a UE may assess (e.g., measure) a channel quality of one or more beam pair links, a beam pair link comprising a transmitting beam transmitted by a base station and a receiving beam received by the UE. Based on the assessment, the UE may transmit a beam measurement report indicating one or more beam pair quality parameters comprising, e.g., one or more beam identifications (e.g., a beam index, a reference signal index, or the like), RSRP, a precoding matrix indicator (PMI), a channel quality indicator (CQI), and / or a rank indicator (Rl).

[0178] FIG. 12A illustrates examples of three downlink beam management procedures: P1 , P2, and P3. Procedure P1 may enable a UE measurement on transmit (Tx) beams of a transmission reception point (TRP) (or multiple TRPs), e.g., to support a selection of one or more base station Tx beams and / or UE Rx beams (shown as ovals in the top row and bottom row, respectively, of P1). Beamforming at a TRP may comprise a Tx beam sweep for a set of beams (shown, in the top rows of P1 and P2, as ovals rotated in a counterclockwise direction indicated by the dashed arrow). Beamforming at a UE may comprise an Rx beam sweep for a set of beams (shown, in the bottom rows of P1 and P3, as ovals rotated in a clockwise direction indicated by the dashed arrow). Procedure P2 may be used to enable a UE measurement on Tx beams of a TRP (shown, in the top row of P2, as ovals rotated in a counterclockwise direction indicated by the dashed arrow). The UE and / or the base station may perform procedure P2 using a smaller set of beams than is used in procedure P1, or using narrower beams than the beams used in procedure P1. ThisDocket No.: 25-1028PCTmay be referred to as beam refinement. The UE may perform procedure P3 for Rx beam determination by using the same Tx beam at the base station and sweeping an Rx beam at the UE.

[0179] FIG. 12B illustrates examples of three uplink beam management procedures: U1, U2, and U3. Procedure U1 may be used to enable a base station to perform a measurement on Tx beams of a UE, e.g., to support a selection of one or more UE Tx beams and / or base station Rx beams (shown as ovals in the top row and bottom row, respectively, of U1). Beamforming at the UE may include, e.g., a Tx beam sweep from a set of beams (shown in the bottom rows of U1 and U3 as ovals rotated in a clockwise direction indicated by the dashed arrow). Beamforming at the base station may include, e.g., an Rx beam sweep from a set of beams (shown, in the top rows of U1 and U2, as ovals rotated in a counterclockwise direction indicated by the dashed arrow). Procedure U2 may be used to enable the base station to adjust its Rx beam when the UE uses a fixed Tx beam. The UE and / or the base station may perform procedure U2 using a smaller set of beams than is used in procedure P1 , or using narrower beams than the beams used in procedure P1. This may be referred to as beam refinement The UE may perform procedure U3 to adjust its Tx beam when the base station uses a fixed Rx beam.

[0180] A UE may initiate a beam failure recovery (BFR) procedure based on detecting a beam failure. The UE may transmit a BFR request (e.g., a preamble, a UCI, an SR, a MAC CE, and / or the like) based on the initiating of the BFR procedure. The UE may detect the beam failure based on a determination that a quality of beam pair link(s) of an associated control channel is unsatisfactory (e.g., having an error rate higher than an error rate threshold, a received signal power lower than a received signal power threshold, an expiration of a timer, and / or the like).

[0181] The UE may measure a quality of a beam pair link using one or more reference signals (RSs) comprising one or more SS / PBCH blocks, one or more CSI-RS resources, and / or one or more demodulation reference signals (DMRSs). A quality of the beam pair link may be based on one or more of a block error rate (BLER), an RSRP value, a signal to interference plus noise ratio (SINR) value, a reference signal received quality (RSRQ) value, and / or a CSI value measured on RS resources. The base station may indicate that an RS resource is quasi co-located (QCLed) with one or more DM-RSs of a channel (e.g., a control channel, a shared data channel, and / or the like). The RS resource and the one or more DMRSs of the channel may be QCLed when the channel characteristics (e.g., Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameter, fading, and / or the like) from a transmission via the RS resource to the UE are similar or the same as the channel characteristics from a transmission via the channel to the UE.

[0182] A network (e.g., a gNB and / or an ng-eNB of a network) and / or the UE may initiate a random access procedure. A UE in an RRCJDLE state and / or an RRCJNACTIVE state may initiate the random access procedure to request a connection setup to a network. The UE may initiate the random accessDocket No.: 25-1028PCTprocedure from an RRC_CONNECTED state. The UE may initiate the random access procedure to request uplink resources (e.g ., for uplink transmission of an SR when there is no PUCCH resource available) and / or acquire uplink timing (e.g., when uplink synchronization status is non-synchronized). The UE may initiate the random access procedure to request one or more system information blocks (SIBs) (e.g., other system information such as SIB2, SIB3, and / or the like). The UE may initiate the random access procedure for a beam failure recovery request. A network may initiate a random access procedure for a handover and / or for establishing time alignment for an SCell addition.

[0183] FIG. 13A illustrates a four-step contention-based random access procedure. Prior to initiation of the procedure, a base station may transmit a configuration message 1310 to the UE. The procedure illustrated in FIG. 13A comprises transmission of four messages: a Msg 1 1311, a Msg 2 1312, a Msg 3 1313, and a Msg 4 1314. The Msg 1 1311 may include and / or be referred to as a preamble (or a random access preamble). The Msg 2 1312 may include and / or be referred to as a random access response (RAR).

[0184] The configuration message 1310 may be transmitted, for example, using one or more RRC messages. The one or more RRC messages may indicate one or more random access channel (RACH) parameters to the UE. The one or more RACH parameters may comprise at least one of following: general parameters for one or more random access procedures (e.g., RACH-configGeneral)', cell-specific parameters (e.g., RACH-ConfigCommon) and / or dedicated parameters (e.g., RACH-configDedicated). The base station may broadcast or multicast the one or more RRC messages to one or more UEs. The one or more RRC messages may be UE-specific (e.g., dedicated RRC messages transmitted to a UE in an RRC_CONNECTED state and / or in an RRCJNACTIVE state). The UE may determine, based on the one or more RACH parameters, a time-frequency resource and / or an uplink transmit power for transmission of the Msg 1 1311 and / or the Msg 3 1313. Based on the one or more RACH parameters, the UE may determine a reception timing and a downlink channel for receiving the Msg 2 1312 and the Msg 4 1314.

[0185] The one or more RACH parameters provided in the configuration message 1310 may indicate one or more Physical RACH (PRACH) occasions available for transmission of the Msg 1 1311. The one or more PRACH occasions may be predefined. The one or more RACH parameters may indicate one or more available sets of one or more PRACH occasions (e.g., prach-Configlndex). The one or more RACH parameters may indicate an association between (a) one or more PRACH occasions and (b) one or more reference signals. The one or more RACH parameters may indicate an association between (a) one or more preambles and (b) one or more reference signals. The one or more reference signals may be SS / PBCH blocks and / or CSI-RSs. For example, the one or more RACH parameters may indicate a number of SS / PBCH blocks mapped to a PRACH occasion and / or a number of preambles mapped to a SS / PBCH blocks.Docket No.: 25-1028PCT

[0186] The one or more RACH parameters provided in the configuration message 1310 may be used to determine an uplink transmit power of Msg 1 1311 and / or Msg 3 1313. For example, the one or more RACH parameters may indicate a reference power for a preamble transmission (e.g., a received target power and / or an initial power of the preamble transmission). There may be one or more power offsets indicated by the one or more RACH parameters. For example, the one or more RACH parameters may indicate: a power ramping step; a power offset between SSB and CSI-RS; a power offset between transmissions of the Msg 1 1311 and the Msg 3 1313; and / or a power offset value between preamble groups. The one or more RACH parameters may indicate one or more thresholds based on which the UE may determine at least one reference signal (e.g., an SSB and / or CSI-RS) and / or an uplink carrier (e.g., a normal uplink (NUL) carrier and / or a supplemental uplink (SUL) carrier).

[0187] The Msg 1 1311 may include one or more preamble transmissions (e.g., a preamble transmission and one or more preamble retransmissions). An RRC message may be used to configure one or more preamble groups (e.g., group A and / or group B). A preamble group may comprise one or more preambles. The UE may determine the preamble group based on a pathloss measurement and / or a size of the Msg 3 1313. The UE may measure an RSRP of one or more reference signals (e.g., SSBs and / or CSI-RSs) and determine at least one reference signal having an RSRP above an RSRP threshold (e.g., rsrp-ThresholdSSB and / or rsrp-ThresholdCSI-RS). The UE may select at least one preamble associated with the one or more reference signals and / or a selected preamble group, for example, if the association between the one or more preambles and the at least one reference signal is configured by an RRC message.

[0188] The UE may determine the preamble based on the one or more RACH parameters provided in the configuration message 1310. For example, the UE may determine the preamble based on a pathloss measurement, an RSRP measurement, and / or a size of the Msg 3 1313. As another example, the one or more RACH parameters may indicate: a preamble format; a maximum number of preamble transmissions; and / or one or more thresholds for determining one or more preamble groups (e.g., group A and group B). A base station may use the one or more RACH parameters to configure the UE with an association between one or more preambles and one or more reference signals (e.g., SSBs and / or CSI-RSs). If the association is configured, the UE may determine the preamble to include in Msg 1 1311 based on the association. The Msg 1 1311 may be transmitted to the base station via one or more PRACH occasions. The UE may use one or more reference signals (e.g., SSBs and / or CSI-RSs) for selection of the preamble and for determining of the PRACH occasion. One or more RACH parameters (e.g., ra-ssb-OccasionMsklndex and / or ra-OccasionList) may indicate an association between the PRACH occasions and the one or more reference signals.Docket No.: 25-1028PCT

[0189] The UE may perform a preamble retransmission if no response is received following a preamble transmission. The UE may increase an uplink transmit power for the preamble retransmission. The UE may select an initial preamble transmit power based on a pathloss measurement and / or a target received preamble power configured by the network. The UE may determine to retransmit a preamble and may ramp up the uplink transmit power. The UE may receive one or more RACH parameters (e.g., PREAMBLE_POWER_RAMPING_STEP) indicating a ramping step for the preamble retransmission. The ramping step may be an amount of incremental increase in uplink transmit power for a retransmission. The UE may ramp up the uplink transmit power if the UE determines a reference signal (e.g., SSB and / or CSI-RS) that is the same as a previous preamble transmission. The UE may count a number of preamble transmissions and / or retransmissions (e.g., PREAMBLE_TRANSMISSION_COUNTER). The UE may determine that a random access procedure completed unsuccessfully, for example, if the number of preamble transmissions exceeds a threshold configured by the one or more RACH parameters (e.g., preambleTransMax) .

[0190] The Msg 2 1312 received by the UE may include an RAR. In some scenarios, the Msg 2 1312 may include multiple RARs corresponding to multiple UEs The Msg 2 1312 may be received after or in response to the transmitting of the Msg 1 1311. The Msg 2 1312 may be scheduled on the DL-SCH and indicated on a PDCCH using a random access RNTI (RA-RNTI). The Msg 2 1312 may indicate that the Msg 1 1311 was received by the base station. The Msg 2 1312 may include a time-alignment command that may be used by the UE to adjust the UE’s transmission timing, a scheduling grant for transmission of the Msg 3 1313, and / or a Temporary Cell RNTI (TC-RNTI). After transmitting a preamble, the UE may start a time window (e.g., ra-ResponseWindow) to monitor a PDCCH for the Msg 2 1312. The UE may determine when to start the time window based on a PRACH occasion that the UE uses to transmit the preamble. For example, the UE may start the time window one or more symbols after a last symbol of the preamble (e.g., at a first PDCCH occasion from an end of a preamble transmission). The one or more symbols may be determined based on a numerology. The PDCCH may be in a common search space (e.g., a Typel-PDCCH common search space) configured by an RRC message. The UE may identify the RAR based on a Radio Network Temporary Identifier (RNTI). RNTIs may be used depending on one or more events initiating the random access procedure. The UE may use random access RNTI (RA-RNTI). The RA-RNTI may be associated with PRACH occasions in which the UE transmits a preamble. For example, the UE may determine the RA-RNTI based on: an OFDM symbol index; a slot index; a frequency domain index; and / or a UL carrier indicator of the PRACH occasions. An example of RA-RNTI may be as follows:

[0191] RA-RNTI= 1 + s_id + 14 x t_id + 14 x 80 x fjd + 14 x 80 x 8 x ul_carrier_id , where s_id may be an index of a first OFDM symbol of the PRACH occasion (e.g., 0 sjd < 14), t_id may be an index of aDocket No.: 25-1028PCTfirst slot of the PRACH occasion in a system frame (e.g., 0 < t_id < 80), f_id may be an index of the PRACH occasion in the frequency domain (e.g., 0 f_id < 8), and ul_carrier_id may be a UL carrier used for a preamble transmission (e.g., 0 for an NUL carrier, and 1 for an SUL carrier).

[0192] The UE may transmit the Msg 3 1313 in response to a successful reception of the Msg 2 1312 (e.g., using resources identified in the Msg 2 1312). The Msg 3 1313 may be used for contention resolution in, for example, the contention-based random access procedure illustrated in FIG. 13A. In some scenarios, a plurality of UEs may transmit a same preamble to a base station and the base station may provide an RAR that corresponds to a UE. Collisions may occur if the plurality of UEs interpret the RAR as corresponding to themselves. Contention resolution (e.g., using the Msg 3 1313 and the Msg 4 1314) may be used to increase the likelihood that the UE does not incorrectly use an identity of another the UE. To perform contention resolution, the UE may include a device identifier in the Msg 3 1313 (e.g., a C-RNTI if assigned, a TC-RNTI included in the Msg 2 1312, and / or any other suitable identifier).

[0193] The Msg 4 1314 may be received after or in response to the transmitting of the Msg 3 1313. If a C-RNTI was included in the Msg 3 1313, the base station will address the UE on the PDCCH using the C-RNTI. If the UE's unique C-RNTI is detected on the PDCCH, the random access procedure is determined to be successfully completed. If a TC-RNTI is included in the Msg 3 1313 (e.g., if the UE is in an RRCJDLE state or not otherwise connected to the base station), Msg 4 1314 will be received using a DL-SCH associated with the TC-RNTI. If a MAC PDU is successfully decoded and a MAC PDU comprises the UE contention resolution identity MAC CE that matches or otherwise corresponds with the CCCH SDU sent (e.g., transmitted) in Msg 3 1313, the UE may determine that the contention resolution is successful and / or the UE may determine that the random access procedure is successfully completed.

[0194] The UE may be configured with a supplementary uplink (SUL) carrier and a normal uplink (NUL) carrier. An initial access (e.g., random access procedure) may be supported in an uplink carrier. For example, a base station may configure the UE with two separate RACH configurations: one for an SUL carrier and the other for an NUL carrier. For random access in a cell configured with an SUL carrier, the network may indicate which carrier to use (NUL or SUL). The UE may determine the SUL carrier, for example, if a measured quality of one or more reference signals is lower than a broadcast threshold. Uplink transmissions of the random access procedure (e.g., the Msg 1 1311 and / or the Msg 3 1313) may remain on the selected carrier. The UE may switch an uplink carrier during the random access procedure (e.g., between the Msg 1 1311 and the Msg 3 1313) in one or more cases. For example, the UE may determine and / or switch an uplink carrier for the Msg 1 1311 and / or the Msg 3 1313 based on a channel clear assessment (e.g., a listen-before-talk).

[0195] FIG. 13B illustrates a two-step contention-free random access procedure. Similar to the four-step contention-based random access procedure illustrated in FIG. 13A, a base station may, prior to initiation ofDocket No.: 25-1028PCTthe procedure, transmit a configuration message 1320 to the UE. The configuration message 1320 may be analogous in some respects to the configuration message 1310. The procedure illustrated in FIG. 13B comprises transmission of two messages: a Msg 1 1321 and a Msg 2 1322. The Msg 1 1321 and the Msg 2 1322 may be analogous in some respects to the Msg 1 1311 and a Msg 2 1312 illustrated in FIG. 13A, respectively. As will be understood from FIGS. 13A and 13B, the contention-free random access procedure may not include messages analogous to the Msg 3 1313 and / or the Msg 4 1314.

[0196] The contention-free random access procedure illustrated in FIG. 13B may be initiated for a beam failure recovery, other SI request, SCell addition, and / or handover. For example, a base station may indicate or assign to the UE the preamble to be used for the Msg 1 1321 . The UE may receive, from the base station via PDCCH and / or RRC, an indication of a preamble (e g., ra-Preamblelndex).

[0197] After transmitting a preamble, the UE may start a time window (e.g., ra-ResponseWindow) to monitor a PDCCH for the RAR. In the event of a beam failure recovery request, the base station may configure the UE with a separate time window and / or a separate PDCCH in a search space indicated by an RRC message (e.g., recovery SearchSpaceld). The UE may monitor for a PDCCH transmission addressed to a Cell RNTI (C-RNTI) on the search space. In the con tent! on -free random access procedure illustrated in FIG. 13B, the UE may determine that a random access procedure successfully completes after or in response to transmission of Msg 1 1321 and reception of a corresponding Msg 2 1322. The UE may determine that a random access procedure successfully completes, for example, if a PDCCH transmission is addressed to a C-RNTI. The UE may determine that a random access procedure successfully completes, for example, if the UE receives an RAR comprising a preamble identifier corresponding to a preamble transmitted by the UE and / or the RAR comprises a MAC sub-PDU with the preamble identifier. The UE may determine the response as an indication of an acknowledgement for an SI request.

[0198] FIG. 13C illustrates another two-step random access procedure. Similar to the random access procedures illustrated in FIGS. 13A and 13B, a base station may, prior to initiation of the procedure, transmit a configuration message 1330 to the UE. The configuration message 1330 may be analogous in some respects to the configuration message 1310 and / or the configuration message 1320. The procedure illustrated in FIG. 13C comprises transmission of two messages: a Msg A 1331 and a Msg B 1332.

[0199] Msg A 1331 may be transmitted in an uplink transmission by the UE. Msg A 1331 may comprise one or more transmissions of a preamble 1341 and / or one or more transmissions of a transport block 1342. The transport block 1342 may comprise contents that are similar and / or equivalent to the contents of the Msg 3 1313 illustrated in FIG. 13A. The transport block 1342 may comprise UCI (e.g., an SR, a HARQ ACK / NACK, and / or the like). The UE may receive the Msg B 1332 after or in response to transmitting the Msg A 1331. The Msg B 1332 may comprise contents that are similar and / or equivalent to the contents ofDocket No.: 25-1028PCTthe Msg 2 1312 (e.g., an RAR) illustrated in FIGS. 13A and 13B and / or the Msg 4 1314 illustrated in FIG.13A.

[0200] The UE may initiate the two-step random access procedure in FIG. 13C for licensed spectrum and / or unlicensed spectrum. The UE may determine, based on one or more factors, whether to initiate the two-step random access procedure. The one or more factors may be: a radio access technology in use (e.g., LTE, NR, and / or the like); whether the UE has valid TA or not; a cell size; the UE's RRC state; a type of spectrum (e.g., licensed vs. unlicensed); and / or any other suitable factors.

[0201] The UE may determine, based on two-step RACH parameters included in the configuration message 1330, a radio resource and / or an uplink transmit power for the preamble 1341 and / or the transport block 1342 included in the Msg A 1331. The RACH parameters may indicate a modulation and coding schemes (MCS), a time-frequency resource, and / or a power control for the preamble 1341 and / or the transport block 1342. A time-frequency resource for transmission of the preamble 1341 (e.g., a PRACH) and a time-frequency resource for transmission of the transport block 1342 (e.g., a PUSCH) may be multiplexed using FDM, TDM, and / or CDM. The RACH parameters may enable the UE to determine a reception timing and a downlink channel for monitoring for and / or receiving Msg B 1332.

[0202] The transport block 1342 may comprise data (e.g., delay-sensitive data), an identifier of the UE, security information, and / or device information (e.g., an International Mobile Subscriber Identity (IMSI)). The base station may transmit the Msg B 1332 as a response to the Msg A 1331. The Msg B 1332 may comprise at least one of following: a preamble identifier; a timing advance command; a power control command; an uplink grant (e.g., a radio resource assignment and / or an MCS); a UE identifier for contention resolution; and / or an RNTI (e.g., a C-RNTI or a TC-RNTI). The UE may determine that the two-step random access procedure is successfully completed if: a preamble identifier in the Msg B 1332 is matched to a preamble transmitted by the UE; and / or the identifier of the UE in Msg B 1332 is matched to the identifier of the UE in the Msg A 1331 (e.g., the transport block 1342).

[0203] A UE and a base station may exchange control signaling. The control signaling may be referred to as L1 / L2 control signaling and may originate from the PHY layer (e.g., layer 1) and / or the MAC layer (e.g., layer 2). The control signaling may comprise downlink control signaling transmitted from the base station to the UE and / or uplink control signaling transmitted from the UE to the base station.

[0204] The downlink control signaling may comprise: a downlink scheduling assignment; an uplink scheduling grant indicating uplink radio resources and / or a transport format; a slot format information; a preemption indication; a power control command; and / or any other suitable signaling. The UE may receive the downlink control signaling in a payload transmitted by the base station on a physical downlink control channel (PDCCH). The payload transmitted on the PDCCH may be referred to as downlink controlDocket No.: 25-1028PCTinformation (DCI). In some scenarios, the PDCCH may be a group common PDCCH (GC-PDCCH) that is common to a group of UEs.

[0205] A base station may attach one or more cyclic redundancy check (CRC) parity bits to a DCI in order to facilitate detection of transmission errors. When the DCI is intended for a UE (or a group of the UEs), the base station may scramble the CRC parity bits with an identifier of the UE (or an identifier of the group of the UEs). Scrambling the CRC parity bits with the identifier may comprise Modulo-2 addition (or an exclusive OR operation) of the identifier value and the CRC parity bits. The identifier may comprise a 16-bit value of a radio network temporary identifier (RNTI).

[0206] DCIs may be used for different purposes. A purpose may be indicated by the type of RNTI used to scramble the CRC parity bits. For example, a DCI having CRC parity bits scrambled with a paging RNTI (P-RNTI) may indicate paging information and / or a system information change notification. The P-RNTI may be predefined as “FFFE” in hexadecimal. A DCI having CRC parity bits scrambled with a system information RNTI (SI-RNTI) may indicate a broadcast transmission of the system information. The SI-RNTI may be predefined as "FFFF” in hexadecimal. A DCI having CRC parity bits scrambled with a random access RNTI (RA-RNTI) may indicate a random access response (RAR) A DCI having CRC parity bits scrambled with a cell RNTI (C-RNTI) may indicate a dynamically scheduled unicast transmission and / or a triggering of PDCCH-ordered random access. A DCI having CRC parity bits scrambled with a temporary cell RNTI (TC-RNTI) may indicate a contention resolution (e.g. , a Msg 3 analogous to the Msg 3 1313 illustrated in FIG. 13A). Other RNTIs configured to the UE by a base station may comprise a Configured Scheduling RNTI (CS-RNTI), a Transmit Power Control-PUCCH RNTI (TPC-PUCCH-RNTI), a Transmit Power Control-PUSCH RNTI (TPC-PUSCH-RNTI), a Transmit Power Control-SRS RNTI (TPC-SRS-RNTI), an Interruption RNTI (INT-RNTI), a Slot Format Indication RNTI (SFI-RNTI), a Semi-Persistent CSI RNTI (SP-CSI-RNTI), a Modulation and Coding Scheme Cell RNTI (MCS-C-RNTI), and / or the like.

[0207] Depending on the purpose and / or content of a DCI, the base station may transmit the DCIs with one or more DCI formats. For example, DCI format 0_0 may be used for scheduling of PUSCH in a cell. DCI format 0_0 may be a fallback DCI format (e.g., with compact DCI payloads). DCI format 0_1 may be used for scheduling of PUSCH in a cell (e.g., with more DCI payloads than DCI format 0_0). DCI format 1_0 may be used for scheduling of PDSCH in a cell. DCI format 1_0 may be a fallback DCI format (e.g., with compact DCI payloads). DCI format 1_1 may be used for scheduling of PDSCH in a cell (e.g., with more DCI payloads than DCI format 1 _0) . DCI format 2_0 may be used for providing a slot format indication to a group of UEs. DCI format 2_1 may be used for notifying a group of UEs of a physical resource block and / or OFDM symbol where the UE may assume no transmission is intended to the UE. DCI format 2_2 may be used for transmission of a transmit power control (TPC) command for PUCCH or PUSCH. DCI format 2_3 may be used for transmission of a group of TPC commands for SRSDocket No.: 25-1028PCTtransmissions by one or more UEs. DCI format(s) for new functions may be defined in future releases. DCI formats may have different DCI sizes, or may share the same DCI size.

[0208] After scrambling a DCI with a RNTI, the base station may process the DCI with channel coding (e.g . , polar coding), rate matching, scrambling and / or QPSK modulation. A base station may map the coded and modulated DCI on resource elements used and / or configured for a PDCCH. Based on a payload size of the DCI and / or a coverage of the base station, the base station may transmit the DCI via a PDCCH occupying a number of contiguous control channel elements (CCEs). The number of the contiguous CCEs (referred to as aggregation level) may be 1 , 2, 4, 8, 16, and / or any other suitable number. A CCE may comprise a number (e.g., 6) of resource-element groups (REGs). A REG may comprise a resource block in an OFDM symbol. The mapping of the coded and modulated DCI on the resource elements may be based on mapping of CCEs and REGs (e.g., CCE-to-REG mapping).

[0209] FIG. 14A illustrates an example of CORESET configurations for a bandwidth part. The base station may transmit a DCI via a PDCCH on one or more control resource sets (CORESETs). A CORESET may comprise a time-frequency resource in which the UE tries to decode a DCI using one or more search spaces. The base station may configure a CORESET in the time-frequency domain. In the example of FIG.14A, a first CORESET 1401 and a second CORESET 1402 occur at the first symbol in a slot. The first CORESET 1401 overlaps with the second CORESET 1402 in the frequency domain. A third CORESET 1403 occurs at a third symbol in the slot. A fourth CORESET 1404 occurs at the seventh symbol in the slot. CORESETs may have a different number of resource blocks in frequency domain.

[0210] FIG. 14B illustrates an example of a CCE-to-REG mapping for DCI transmission on a CORESET and PDCCH processing. The CCE-to-REG mapping may be an interleaved mapping (e.g., for the purpose of providing frequency diversity) or a non-interleaved mapping (e.g., for the purposes of facilitating interference coordination and / or frequency-selective transmission of control channels). The base station may perform different or same CCE-to-REG mapping on different CORESETs. A CORESET may be associated with a CCE-to-REG mapping by RRC configuration. A CORESET may be configured with an antenna port quasi co-location (QCL) parameter. The antenna port QCL parameter may indicate QCL information of a demodulation reference signal (DMRS) for PDCCH reception in the CORESET.

[0211] The base station may transmit, to the UE, RRC messages comprising configuration parameters of one or more CORESETs and one or more search space sets. The configuration parameters may indicate an association between a search space set and a CORESET. A search space set may comprise a set of PDCCH candidates formed by CCEs at a given aggregation level. The configuration parameters may indicate: a number of PDCCH candidates to be monitored per aggregation level; a PDCCH monitoring periodicity and a PDCCH monitoring pattern; one or more DCI formats to be monitored by the UE; and / or whether a search space set is a common search space set or a UE-specific search space set. A set ofDocket No.: 25-1028PCTCCEs in the common search space set may be predefined and known to the UE. A set of CCEs in the UE-specific search space set may be configured based on the UE's identity (e.g C-RNTI).

[0212] As shown in FIG. 14B, the UE may determine a time-frequency resource for a CORESET based on RRC messages. The UE may determine a CCE-to-REG mapping (e.g., interleaved or non-interleaved, and / or mapping parameters) for the CORESET based on configuration parameters of the CORESET. The UE may determine a number (e.g., at most 10) of search space sets configured on the CORESET based on the RRC messages. The UE may monitor a set of PDCCH candidates according to configuration parameters of a search space set. The UE may monitor a set of PDCCH candidates in one or more CORESETs for detecting one or more DCIs. Monitoring may comprise decoding one or more PDCCH candidates of the set of the PDCCH candidates according to the monitored DCI formats. Monitoring may comprise decoding a DCI content of one or more PDCCH candidates with possible (or configured) PDCCH locations, possible (or configured) PDCCH formats (e.g., number of CCEs, number of PDCCH candidates in common search spaces, and / or number of PDCCH candidates in the UE-specific search spaces) and possible (or configured) DCI formats. The decoding may be referred to as blind decoding. The UE may determine a DCI as valid for the UE, in response to CRC checking (e.g., scrambled bits for CRC parity bits of the DCI matching a RNTI value). The UE may process information contained in the DCI (e.g., a scheduling assignment, an uplink grant, power control, a slot format indication, a downlink preemption, and / or the like).

[0213] The UE may transmit uplink control signaling (e.g., uplink control information (UCI)) to a base station. The uplink control signaling may comprise hybrid automatic repeat request (HARQ) acknowledgements for received DL-SCH transport blocks. The UE may transmit the HARQ acknowledgements after receiving a DL-SCH transport block. Uplink control signaling may comprise channel state information (CSI) indicating channel quality of a physical downlink channel. The UE may transmit the CSI to the base station. The base station, based on the received CSI, may determine transmission format parameters (e.g., comprising multi-antenna and beamforming schemes) for a downlink transmission. Uplink control signaling may comprise scheduling requests (SR). The UE may transmit an SR indicating that uplink data is available for transmission to the base station. The UE may transmit a UCI (e.g , HARQ acknowledgements (HARQ-ACK), CSI report, SR, and the like) via a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH). The UE may transmit the uplink control signaling via a PUCCH using one of several PUCCH formats.

[0214] There may be five PUCCH formats and the UE may determine a PUCCH format based on a size of the UCI (e.g., a number of uplink symbols of UCI transmission and a number of UCI bits). PUCCH format 0 may have a length of one or two OFDM symbols and may include two or fewer bits. The UE may transmit UCI in a PUCCH resource using PUCCH format 0 if the transmission is over one or two symbols and theDocket No.: 25-1028PCTnumber of HARQ-ACK information bits with positive or negative SR (HARQ-ACK / SR bits) is one or two. PUCCH format 1 may occupy a number between four and fourteen OFDM symbols and may include two or fewer bits. The UE may use PUCCH format 1 if the transmission is four or more symbols and the number of HARQ-ACK / SR bits is one or two. PUCCH format 2 may occupy one or two OFDM symbols and may include more than two bits. The UE may use PUCCH format 2 if the transmission is over one or two symbols and the number of UCI bits is two or more. PUCCH format 3 may occupy a number between four and fourteen OFDM symbols and may include more than two bits. The UE may use PUCCH format 3 if the transmission is four or more symbols, the number of UCI bits is two or more and PUCCH resource does not include an orthogonal cover code. PUCCH format 4 may occupy a number between four and fourteen OFDM symbols and may include more than two bits. The UE may use PUCCH format 4 if the transmission is four or more symbols, the number of UCI bits is two or more and the PUCCH resource includes an orthogonal cover code.

[0215] The base station may transmit configuration parameters to the UE for a plurality of PUCCH resource sets using, for example, an RRC message. The plurality of PUCCH resource sets (e.g ., up to four sets) may be configured on an uplink BWP of a cell. A PUCCH resource set may be configured with a PUCCH resource set index, a plurality of PUCCH resources with a PUCCH resource being identified by a PUCCH resource identifier (e.g., pucch-Resourceid), and / or a number (e.g. a maximum number) of UCI information bits the UE may transmit using one of the plurality of PUCCH resources in the PUCCH resource set When configured with a plurality of PUCCH resource sets, the UE may select one of the plurality of PUCCH resource sets based on a total bit length of the UCI information bits (e.g., HARQ-ACK, SR, and / or CSI). If the total bit length of UCI information bits is two or fewer, the UE may select a first PUCCH resource set having a PUCCH resource set index equal to “0’’. If the total bit length of UCI information bits is greater than two and less than or equal to a first configured value, the UE may select a second PUCCH resource set having a PUCCH resource set index equal to "1”. If the total bit length of UCI information bits is greater than the first configured value and less than or equal to a second configured value, the UE may select a third PUCCH resource set having a PUCCH resource set index equal to “2”. If the total bit length of UCI information bits is greater than the second configured value and less than or equal to a third value (e.g., 1406), the UE may select a fourth PUCCH resource set having a PUCCH resource set index equal to “3”.

[0216] After determining a PUCCH resource set from a plurality of PUCCH resource sets, the UE may determine a PUCCH resource from the PUCCH resource set for UCI (HARQ-ACK, CSI, and / or SR) transmission. The UE may determine the PUCCH resource based on a PUCCH resource indicator in a DCI (e.g , with a DCI format 1_0 or DCI for 1_1) received on a PDCCH. A three-bit PUCCH resource indicator in the DCI may indicate one of eight PUCCH resources in the PUCCH resource set. Based on the PUCCHDocket No.: 25-1028PCTresource indicator, the UE may transmit the UCI (HARQ-ACK, CSI and / or SR) using a PUCCH resource indicated by the PUCCH resource indicator in the DCI.

[0217] FIG. 15 illustrates an example of a wireless device 1502 in communication with a base station 1504 in accordance with embodiments of the present disclosure. The wireless device 1502 and base station 1504 may be part of a mobile communication network, such as the mobile communication network 100 illustrated in FIG. 1A, the mobile communication network 150 illustrated in FIG. 1B, or any other communication network. Only one wireless device 1502 and one base station 1504 are illustrated in FIG.15, but it will be understood that a mobile communication network may include more than one UE and / or more than one base station, with the same or similar configuration as those shown in FIG. 15.

[0218] The base station 1504 may connect the wireless device 1502 to a core network (not shown) through radio communications over the air interface (or radio interface) 1506. The communication direction from the base station 1504 to the wireless device 1502 over the air interface 1506 is known as the downlink, and the communication direction from the wireless device 1502 to the base station 1504 over the air interface is known as the uplink. Downlink transmissions may be separated from uplink transmissions using FDD, TDD, and / or some combination of the two duplexing techniques.

[0219] In the downlink, data to be sent to the wireless device 1502 from the base station 1504 may be provided to the processing system 1508 of the base station 1504. The data may be provided to the processing system 1508 by, for example, a core network. In the uplink, data to be sent to the base station 1504 from the wireless device 1502 may be provided to the processing system 1518 of the wireless device 1502. The processing system 1508 and the processing system 1518 may implement layer 3 and layer 2 OSI functionality to process the data for transmission. Layer 2 may include an SDAP layer, a PDCP layer, an RLC layer, and a MAC layer, for example, with respect to FIG. 2A, FIG. 2B, FIG. 3, and FIG. 4A. Layer 3 may include an RRC layer as with respect to FIG. 2B.

[0220] After being processed by processing system 1508, the data to be sent to the wireless device 1502 may be provided to a transmission processing system 1510 of base station 1504. Similarly, after being processed by the processing system 1518, the data to be sent to base station 1504 may be provided to a transmission processing system 1520 of the wireless device 1502. The transmission processing system 1510 and the transmission processing system 1520 may implement layer 1 OSI functionality. Layer 1 may include a PHY layer with respect to FIG. 2A, FIG. 2B, FIG. 3, and FIG. 4A. For transmit processing, the PHY layer may perform, for example, forward error correction coding of transport channels, interleaving, rate matching, mapping of transport channels to physical channels, modulation of physical channel, multiple-input multiple-output (MIMO) or multi-antenna processing, and / or the like.

[0221] At the base station 1504, a reception processing system 1512 may receive the uplink transmission from the wireless device 1502. At the wireless device 1502, a reception processing system 1522 mayDocket No.: 25-1028PCTreceive the downlink transmission from base station 1504. The reception processing system 1512 and the reception processing system 1522 may implement layer 1 OSI functionality. Layer 1 may include a PHY layer with respect to FIG. 2A, FIG. 2B, FIG. 3, and FIG. 4A. For receive processing, the PHY layer may perform, for example, error detection, forward error correction decoding, deinterleaving, demapping of transport channels to physical channels, demodulation of physical channels, MIMO or multi-antenna processing, and / or the like.

[0222] As shown in FIG. 15, a wireless device 1502 and the base station 1504 may include multiple antennas. The multiple antennas may be used to perform one or more MIMO or multi-antenna techniques, such as spatial multiplexing (e.g., single-user MIMO or multi-user MIMO), transmit / receive diversity, and / or beamforming. In other examples, the wireless device 1502 and / or the base station 1504 may have a single antenna.

[0223] The processing system 1508 and the processing system 1518 maybe associated with a memory 1514 and a memory 1524, respectively. Memory 1514 and memory 1524 (e.g., one or more non-transitory computer readable mediums) may store computer program instructions or code that may be executed by the processing system 1508 and / or the processing system 1518 to carry out one or more of the functionalities discussed in the present application. Although not shown in FIG. 15, the transmission processing system 1510, the transmission processing system 1520, the reception processing system 1512, and / or the reception processing system 1522 may be coupled to a memory (e.g., one or more non-transitory computer readable mediums) storing computer program instructions or code that may be executed to carry out one or more of their respective functionalities.

[0224] The processing system 1508 and / or the processing system 1518 may comprise one or more controllers and / or one or more processors. The one or more controllers and / or one or more processors may comprise, for example, a general-purpose processor, a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) and / or other programmable logic device, discrete gate and / or transistor logic, discrete hardware components, an onboard unit, or any combination thereof. The processing system 1508 and / or the processing system 1518 may perform at least one of signal coding / processing, data processing, power control, input / output processing, and / or any other functionality that may enable the wireless device 1502 and the base station 1504 to operate in a wireless environment.

[0225] The processing system 1508 and / or the processing system 1518 may be connected to one or more peripherals 1516 and one or more peripherals 1526, respectively. The one or more peripherals 1516 and the one or more peripherals 1526 may include software and / or hardware that provide features and / or functionalities, for example, a speaker, a microphone, a keypad, a display, a touchpad, a power source, a satellite transceiver, a universal serial bus (USB) port, a hands-free headset, a frequency modulated (FM)Docket No.: 25-1028PCTradio unit, a media player, an Internet browser, an electronic control unit (e.g., for a motor vehicle), and / or one or more sensors (e.g., an accelerometer, a gyroscope, a temperature sensor, a radar sensor, a lidar sensor, an ultrasonic sensor, a light sensor, a camera, and / or the like). The processing system 1508 and / or the processing system 1518 may receive user input data from and / or provide user output data to the one or more peripherals 1516 and / or the one or more peripherals 1526. The processing system 1518 in the wireless device 1502 may receive power from a power source and / or may be configured to distribute the power to the other components in the wireless device 1502. The power source may comprise one or more sources of power, for example, a battery, a solar cell, a fuel cell, or any combination thereof. The processing system 1508 and / or the processing system 1518 may be connected to a GPS chipset 1517 and a GPS chipset 1527, respectively. The GPS chipset 1517 and the GPS chipset 1527 may be configured to provide geographic location information of the wireless device 1502 and the base station 1504, respectively.

[0226] FIG. 16A illustrates an example structure for uplink transmission. A baseband signal representing a physical uplink shared channel may perform one or more functions. The one or more functions may comprise at least one of: scrambling; modulation of scrambled bits to generate complex-valued symbols; mapping of the complex-valued modulation symbols onto one or several transmission layers; transform precoding to generate complex-valued symbols; precoding of the complex-valued symbols; mapping of precoded complex-valued symbols to resource elements; generation of complex-valued time-domain Single Carrier-Frequency Division Multiple Access (SC-FDMA) or CP-OFDM signal for an antenna port; and / or the like. In an example, when transform precoding is enabled, a SC-FDMA signal for uplink transmission may be generated. In an example, when transform precoding is not enabled, a CP-OFDM signal for uplink transmission may be generated by FIG. 16A. These functions are illustrated as examples and it is anticipated that other mechanisms may be implemented in various embodiments.

[0227] FIG. 16B illustrates an example structure for modulation and up-conversion of a baseband signal to a carrier frequency. The baseband signal may be a complex-valued SC-FDMA or CP-OFDM baseband signal for an antenna port and / or a complex-valued Physical Random Access Channel (PRACH) baseband signal. Filtering may be employed prior to transmission.

[0228] FIG. 16C illustrates an example structure for downlink transmissions A baseband signal representing a physical downlink channel may perform one or more functions. The one or more functions may comprise: scrambling of coded bits in a codeword to be transmitted on a physical channel; modulation of scrambled bits to generate complex-valued modulation symbols; mapping of the complex-valued modulation symbols onto one or several transmission layers; precoding of the complex-valued modulation symbols on a layer for transmission on the antenna ports; mapping of complex-valued modulation symbols for an antenna port to resource elements; generation of complex-valued time-domain OFDM signal for anDocket No.: 25-1028PCTantenna port; and / or the like. These functions are illustrated as examples and it is anticipated that other mechanisms may be implemented in various embodiments.

[0229] FIG. 16D illustrates another example structure for modulation and up-conversion of a baseband signal to a carrier frequency. The baseband signal may be a complex-valued OFDM baseband signal for an antenna port. Filtering may be employed prior to transmission.

[0230] A wireless device may receive from a base station one or more messages (e.g. RRC messages) comprising configuration parameters of a plurality of cells (e.g. primary cell, secondary cell). The wireless device may communicate with at least one base station (e.g. two or more base stations in dual connectivity) via the plurality of cells. The one or more messages (e.g. as a part of the configuration parameters) may comprise parameters of physical, MAC, RLC, PCDP, SDAP, RRC layers for configuring the wireless device. For example, the configuration parameters may comprise parameters for configuring physical and MAC layer channels, bearers, etc. For example, the configuration parameters may comprise parameters indicating values of timers for physical, MAC, RLC, PCDP, SDAP, RRC layers, and / or communication channels.

[0231] A timer may begin running once it is started and continue running until it is stopped or until it expires. A timer may be started if it is not running or restarted if it is running. A timer may be associated with a value (e.g. the timer may be started or restarted from a value or may be started from zero and expire once it reaches the value). The duration of a timer may not be updated until the timer is stopped or expires (e.g , due to BWP switching). A timer may be used to measure a time period / window for a process When the specification refers to an implementation and procedure related to one or more timers, it will be understood that there are multiple ways to implement the one or more timers. For example, it will be understood that one or more of the multiple ways to implement a timer may be used to measure a time period / window for the procedure. For example, a random access response window timer may be used for measuring a window of time for receiving a random access response. In an example, instead of starting and expiry (or expiration) of a random access response window timer, the time difference between two time stamps may be used. When a timer is restarted, a process for measurement of time window may be restarted. Other example implementations may be provided to restart a measurement of a time window.

[0232] FIG. 17 illustrates an exemplary UE registration procedure as per an aspect of an embodiment of the present disclosure. For example, a UE registration procedure and a deregistration procedure may provide one or more key functionalities to register or deregister a UE / user with the 5GS. For example, a UE may register with a network to get authorized to receive services, to enable mobility tracking and to enable reachability. For example, the UE may initiate the registration procedure using at least one of the following registration types to get registered to a mobile communication system (e g., 5GS): i) an initial registration; ii) a mobility registration update; iii) a periodic registration update; iv) an emergency registration; v) a disasterDocket No.: 25-1028PCTroaming initial registration; vi) a disaster roaming mobility registration update; or vii) a standalone non-public network (SNPN) onboarding registration.

[0233] For example, the UE may initiate the mobility registration update due to at least one of the following reasons: i) upon changing to a new tracking area (TA) outside the UE's registration area in both CM-CONNECTED and CM-IDLE state; ii) when the UE needs to update one or more capabilities or protocol parameters that are negotiated in a registration procedure with or without changing to a new TA; iii) a change in the UE's preferred network behavior that would create an incompatibility with one or more supported network behaviors provided by a serving AMP; iv) when the UE intends to retrieve local area data network (LADN) information; v) with a (NR) satellite access upon changing to a suitable cell indicating one or more TAs for a registered PLMN (RPLMN) and the one or more TAsare outside the UE's registration area in both CM-CONNECTED and CM-IDLE state; vi) when a Multi-USIM UE needs a new 5G-GUTI assignment; vii) when the UE needs to indicate or returns from an unavailability period; viii) when the UE using a RAN that provides discontinuous coverage (e.g. for satellite access with discontinuous coverage) is about to leave the satellite network coverage as described; or ix) when the UE has informed the network it is unreachable and now returns to coverage using either satellite or terrestrial access.

[0234] For example, a UE may trigger the periodic registration update due to a predefined time period of inactivity. For example, a UE may trigger the SNPN onboarding registration to access an onboarding standalone non-public network (ON-SNPN) for the purpose of getting the UE provisioned with subscription owner standalone non-public network (SO-SNPN) credentials to enable SO-SNPN access.

[0235] For example, during the initial registration, an AMF may obtain a permanent equipment identifier (PEI) from the UE. If the PEI is needed (e.g. for EIR check), the AMF may retrieve the PEI when it establishes the NAS security context with a security mode command during the initial registration. The AMF may check the PEI with the help of an EIR. For example, the AMF may pass the PEI on to a UDM, to an SMF and a PCF. The UDM may store the PEI in a UDR

[0236] For example, during a registration procedure, a home network (or a credentials holder in case of access to an SNPN) may provide steering of roaming information to a UE via the AMF. The steering of roaming information may comprise at least one of: a list of preferred PLMN / access technology combinations; ii) a credentials holder controlled prioritized lists of preferred SNPNs or group IDs for network selection (GINs); iii) a credentials holder controlled prioritized lists of preferred SNPNs or GINs for accessing localized services; iv) or an HPLMN or a credentials holder indication that 'no change of the above list(s) stored in the UE is needed'. For example, the home network may include an indication for the UE to send an acknowledgement of the reception of this information.Docket No.: 25-1028PCT

[0237] For example, as illustrated in FIG. 17, the UE may send an access network (AN) message comprising at least one or more of the following: i) one or more AN parameters; ii) a registration request; iii) a 5G-S-TMSI; iv) a GUAMI iv) a selected PLMN ID; v) an NID; vi) NSSAI information; or vii) an establishment cause.

[0238] For example, the registration request may comprise at least one or more of: a registration type; a SUCI; a 5G-GUTI; a PEI; last visited TAI (if available); one or more security parameters; requested NSSAI; a mapping of requested NSSAI; a default configured NSSAI indication; a UE radio capability update; a UE MM core network capability; a PDU session status; a listof PDU sessions to be activated; a follow-on request; a MICO indication; a requested active time; requested DRX parameters for E-UTRA and NR; requested DRX parameters for NB-loT; extended idle mode DRX parameters; LADN DNN(s); an indicator of requesting LADN Information; a NAS message container; a support for restriction of use of enhanced coverage]; a preferred network behavior; a UE paging probability information; a paging subgrouping support indication; a low power wake up signal (LP-WUS) subgrouping support indication; a UE policy container; a UE radio capability ID; a release request indication; a paging restriction information; a PEI; a PLMN with a disaster condition; a requested periodic update time; an unavailability period duration; a start of an unavailability period; or an unavailability type.

[0239] For example, if the UE supports UE configuration of network-controlled slice usage policy and the UE stores slice usage policy, the UE may include an on demand S-NSSAI in the Requested NSSAI when applications in the UE require data transmission by a PDU session associated with the on demand S-NSSAI.

[0240] For example, the UE may send the UE MM core network capability information to the AMF during the initial registration or the mobility registration update procedure. For example, this may be to ensure that the UE MM Core Network Capability information stored in the AMF is up to date.

[0241] For example, if the UE supports 'strictly periodic registration timer indication', the UE may indicate its capability of 'strictly periodic registration timer indication' in the MICO indication. If the UE supports CAG, the UE may indicate its capability of "CAG supported1' in the UE MM Core Network Capability. If the UE operates a plurality of USIMs, supports and intends to use one or more multi-USIM feature(s), the UE may indicate one or more multi-USIM specific features in the UE MM core network capability. If the UE supports LADN per DNN and S-NSSAI, the UE may indicate its support of LADN per DNN and S-NSSAI in the UE MM core network capability. If the UE supports a network slice replacement feature, the UE indicates support for the network slice replacement feature. If the UE supports a UE configuration of network-controlled slice usage policy, the UE may indicate its capability of "UE configuration of network-controlled slice usage policy" in the UE MM core network capability. For example, if the UE supports RAGS and has a UE radio capability ID(s) assigned, the UE may indicate a UE Radio Capability ID. For example, if a UE supports subscription-based restrictions to simultaneous registration of network slices feature, the UE may include the NSSRG handling support indication in the UE 5GMM core network capability.Docket No.: 25-1028PCT

[0242] For example, the UE may indicate in the UE 5GMM core network capability if the UE supports at least one or more of the following: SMS over NAS; location services (LCS); radio capabilities signaling optimization (RAGS); network slice-specific authentication and authorization; network slice replacement; paging subgrouping support indication; LP-WUS paging subgrouping support indication; CAG; subscription-based restrictions to simultaneous registration of network slices; support of network slice access stratum group (NSAG); partial network slice support in a registration area; minimization of service interruption (MINT); equivalent SNPNs; an unavailability period support; a support for network reconnection due to RAN timing synchronization status change; UE configuration of network-controlled slice usage policy; temporarily available network slices; support of S-NSSAI location availability information; or support of network verified UE location over NR NTN.

[0243] For example, in step 2 of FIG. 17, on receiving a registration request message, a radio access network (RAN) may select an AMF based on an included 5G-S-TMSI or GUAMI of the registration request message. In case the included 5G-S-TMSI or GUAMI does not indicate a valid AMF, the RAN may select an AMF based on a RAT or requested NSSAI information that is included in the registration request message. For example, in case the (R)AN cannot select an appropriate AMF, it may forward the registration request message to an AMF (e.g., a default AMF) which has been configured, in (R)AN, to perform an AMF selection. A selected AMF in this step 2 may be termed a new AMF.

[0244] For example, in step 3 of FIG. 17, the (R)AN may encapsulate the registration request message in an N2 message and send the N2 message to a selected AMF. The N2 message may comprise at least one or more N2 parameters; and / or the registration message. The one or more N2 parameters may comprise at least one or more of the following: a selected PLMN (e.g., a PLMN ID); a NID; location information; cell identity of a cell in which the UE is camping; and / or a UE context request. For example, the UE context request may indicate that a UE context including security information needs to be established at the (R)AN (e.g , NG-RAN).

[0245] For example, if the UE includes a preferred network behavior, which is incompatible with what the network can support, the selected AMF may reject the registration request with an appropriate cause value.

[0246] For example, in step 4 of FIG. 17, the new AMF which is selected in step 2 may determine an old AMF using the UE's 5G-GUTI or NID and try to retrieve the stored UE's SUPI and UE context. For example, in step 5, if the old AMF holds information about established PDU session(s) and it is not an initial registration, the old AMF may include at least one or more of the following in a Namf_Communication_UEContextTransfer response and send to the new AMF: SMF information; DNN(s); S-NSSAI(s); PDU session ID(s). For example, if the old AMF holds information about AM policy association and information about UE policy association, the old AMF may include information about the AM policy association, the UE policy association and PCF ID in the Namf_Communication_UEContextTransfer response.Docket No.: 25-1028PCT

[0247] For example, in step 6 of FIG. 17, if the SUCI is not provided by the UE nor retrieved from the old AMF, the new AMF may trigger an identity request procedure by sending an identity request message to the UE requesting the SUCI. For example, in return, in step 7, the UE may respond with the SUCI. For example, in step 8, the (new) AMF may select an AUSF based on SUPI or SUCI and initiate UE authentication by invoking an AUSF.

[0248] For example, in step 9 of FIG. 17, the (new) AMF may request the AUSF to execute authentication of the UE. For example, the AUSF may select a UDM and get authentication data from the UDM. After executing authentication, the AUSF may provide relevant security related information to the AMF. For example, if the AMF provides a SUCI to AUSF, the AUSF may return the SUPI to the AMF after the authentication is successful.

[0249] For example, in step 10 of FIG. 17, the new AMF may notify the old AMF of an outcome the registration request. For example, if the new AMF is not able to get the PEI either from a UE or the old AMF, the new AMF may initiate an identity request procedure in step 11 by sending an identity request message to the UE to retrieve the PEI. For example, optionally in step 12, the new AMF may initiate an ME identity check.

[0250] For example, in case step 14 is required, the new AMF, based on the SUPI, may select a UDM, which, in turn, may select a UDR instance in step 13.

[0251] For example, in step 15, if the new AMF decides to use a (V-)PCF identified by a (V-)PCF ID included in UE context from the old AMF in step 5, the AMF may contact the (V-)PCF identified by the (V-)PCF ID to obtain policy. After finding the (V-)PCF, in step 16, the new AMF may perform an AM policy association establishment / modification . Fr example, if the new AMF notifies mobility restrictions (e.g. UE location) to the (V-)PCF for adjustment, or if the (V-)PCF updates the mobility restrictions itself due to some conditions (e.g. application in use, time and date), the (V-)PCF may provide the updated mobility restrictions to the AMF. If the (V-)PCF supports a slice replacement, the (V-)PCF may provide the new AMF with triggers for a slice replacement If a S-NSSAI is subject to network slice usage control, the (V-)PCF may provide a slice usage policy information including whether a network slice is on demand and a slice deregistration inactivity timer value, for one or more subscribed S-NSSAIs.

[0252] For example, in step 17 of FIG. 17, if the list of PDU sessions to be activated is included in the registration request in step 1, the AMF sends Nsmf_PDUSession_UpdateSM Context Request to SMF(s) associated with one or more PDU session(s) in order to activate user plane connections of the one or more PDU session(s).

[0253] For example, in step 18, if the new AMF and the old AMF are in the same PLMN, the new AMF may send a UE context modification request to at least one of: a non-3GPP inter working function (N3IWF); a trusted non-3GPP gateway function (TNGF); or a wireline access gateway function (W-AGF). In step 19, the N3IWF / TNGF / W-AGF may send a UE context modification response to the new AMF. After the new AMFDocket No.: 25-1028PCTreceives the response message from the N3IWF, W-AGF or TNGF in step 19, the new AMF may register with a UDM in step 19a using Nudm_UECM_Registration as step 14a, but with the Access Type set to "non-3GPP access". When the UDM stores the associated access type (i.e. non-3GPP) as indicated in step 19a, the UDM may initiate a Nudm_UECM_DeregistrationNotification to the old AMF in step 19b corresponding to the same (i.e. non-3GPP) access. The old AMF may remove the UE context for non-3GPP access. In step 19c, the Old AMF may unsubscribe with the UDM.

[0254] For example, in step 21 of FIG. 17, the (new) AMF may send a registration accept message. For example, the new AMF may include at least one or more of the following in the registration accept message: a 5G-GUTI; a registration area (RA); mobility restrictions; a PDU session status; allowed NSSAI; mapping of allowed NSSAI; partially allowed NSSAI; mapping of partially allowed NSSAI; a TAI list for S-NSSAIs in partially allowed NSSAI; a configured NSSAI for the serving PLMN; mapping of configured NSSAI; NSSRG information; NSAG information; rejected S-NSSAIs; a TAI list for any rejected S-NSSAI partially in the RA; pending NSSAI; mapping of pending NSSAI; periodic registration update timer; an active time; a strictly periodic registration timer indication; LADN information; a MICO indication; an IMS voice over PS session supported indication; an emergency service support indicator; accepted DRX parameters for E-UTRA and NR; accepted DRX parameters for NB-loT; extended idle mode DRX parameters; paging time window; network support of interworking without N26; access stratum connection establishment NSSAI inclusion mode; network slicing subscription change indication; operator-defined access category definitions; a list of equivalent PLMNs; enhanced coverage restricted information; supported network behavior; service gap time; a PLMN-assigned UE radio capability ID; a PLMN-assigned UE radio capability ID deletion; WUS assistance information; AMF PEIPS assistance information; AMF LP-WUSPS assistance information; a truncated 5G-S-TMSI configuration; connection release supported; paging cause indication for voice service supported; paging restriction supported; reject paging request supported; paging restriction information acceptance / rejection; a list of PLMN(s) to be used in disaster condition; disaster roaming wait range information; disaster return wait range information; forbidden TAI(s); a list of equivalent SNPNs; registered NID; unavailability period support; MBSR authorization information; return to coverage notification not required; unavailability period duration; start of unavailability period; S-NSSAI location availability information; mapping of alternative NSSAI; slice usage policy; maximum time offset.

[0255] For example, in step 21, if the requested NSSAI does not include S-NSSAIs which map to S-NSSAIs of the HPLMN subject to network slice-specific authentication and authorization and the (new) AMF determines that no S-NSSAI can be provided in the allowed NSSAI for the UE in the current UE's tracking area and if no default S-NSSAI(s) not yet involved in the current UE registration procedure could be further considered, the (new) AMF may reject the UE registration and may include in the rejection message the listDocket No.: 25-1028PCTof rejected S-NSSAIs, each of them with the appropriate rejection cause value. In relation to FIG. 17, terminologies such as the new AMF and the AMF may refer to each other and are used interchangeably.

[0256] For example, if the registration request message received over 3GPP access includes a paging restriction information, the (new) AMF may accept or reject the paging restriction information requested by the UE based on operator policy. If the (new) AMF rejects the paging restriction information, the (new) AMF may remove any stored paging restriction information from the UE context and discard the UE requested paging restriction information. If the (new) AMF accepts the paging restriction information from the UE, the (new) AMF may store the paging restriction information from the UE in the UE context and inform the UE about an acceptance / rejection of the requested paging restriction information in the registration accept message of step 21.

[0257] For example, if the registration request message received over 3GPP access includes a release request indication, the (new) AMF may not establish user plane resources and may trigger an access network (AN) release procedure after the completion of Registration procedure. For example, the access network (AN) release procedure may cause an entire UP connections of the UE to be deactivated. For example, if the UE indicates its support for slice usage policy in the UE 5GMM core network capability, the AMF may include slice usage policies for the slices in the configured NSSAI. If the UE indicates its support for subscription-based restrictions to simultaneous registration of network slices feature in the UE 5GMM core network capability, the AMF may include, if available, NSSRG Information.

[0258] For example, if the UE includes the MICO indication in the registration request, the AMF may respond in the registration accept message whether MICO mode should be used in the MICO indication. When the MICO mode is allowed for the UE, the AMF may include an active time value and / or a strictly periodic registration timer indication in the registration accept message. The AMF may determine the periodic registration update timer value, active time value and the strictly periodic registration timer indication based on at least one or more of the following: local configuration; expected UE behavior if available; UE indicated preferences; UE capability; UE subscription information; if using a RAN that provides discontinuous coverage, UE availability; or network policies. ]. If the AMF accepts the use of extended idle mode DRX, the AMF may include the extended idle mode DRX parameters and paging time window. For example, if the UE provides a paging subgrouping support indication in step 1 , the (supporting) AMF may provide the AMF PEIPS assistance information, including the paging subgroup ID. For example, if the UE provides an LP-WUS subgrouping support indication in step 1 , the (supporting) AMF may provide the AMF LP-WUSPS assistance information, including the LP-WUS subgroup ID.

[0259] For example, if the UE indicates the support of unavailability period in the UE MM core network capability in the registration request, the AMF may indicate to the UE whether the corresponding feature is supported by providing the "unavailability period support" indication. If the UE provides an unavailabilityDocket No.: 25-1028PCTperiod duration and / or start of unavailability period in step 1, the AMF may store the received unavailability period duration and / or start of unavailability period in UE context. The AMF may provide the periodic registration update timer based on the unavailability period duration and / or the start of unavailability period indicated by the UE.

[0260] For example, if the UE indicates a support for the network slice replacement feature in the 5GMM core network capability and the AMF determines that an S-NSSAI from an allowed NSSAI is to be replaced with an alternative S-NSSAI, the AMF may include a mapping of alternative NSSAI within the registration accept message to the UE and also adds the alternative S-NSSAI to the allowed NSSAI and / or configured NSSAI, if not already included.

[0261] For example, un step 21 b, the new AMF may perform a UE policy association establishment.

[0262] For example, in step 22, the UE may send a registration complete message to the AMF after successfully updating one or more of the following received in step 21 : the configured NSSAI for the serving PLMN; the mapping of configured NSSAI; the NSSRG information; the NSAG Information; the network slicing subscription change indication; or the CAG information. If the AMF provides updated slice deregistration timer value(s) to the UE in step 21, the AMF may use the corresponding slice deregistration inactivity timer value(s) next time the slice deregistration inactivity timer(s) starts.

[0263] For example, if the access and mobility subscription data provided by the UDM to the AMF in step 14b includes steering of roaming information with an indication that the UDM requests an acknowledgement of the reception of this information from the UE, the AMF may provide the UE acknowledgement to UDM in step 23. For example, for registration over 3GPP access, if the AMF does not release the signaling connection, the AMF may send the RRC inactive assistance information to the NG-RAN in step 23a. After step 14a and in parallel to any of the preceding steps, the AMF may send a "Homogeneous Support of IMS Voice over PS Sessions" indication to the UDM in step 24.

[0264] For example, if the UE indicates its support for network slice-specific authentication and authorization procedure in the UE MM core network capability in registration request and any S-NSSAI of the HPLMN is subject to network slice-specific authentication and authorization, the related procedure is executed in step 25.

[0265] FIG. 18 illustrates an exemplary UE-requested PDU session establishment procedure as per an aspect of an embodiment of the present disclosure. For example, FIG. 18 illustrates a UE requested PDU session establishment procedure in either a non-roaming or a roaming with local breakout situation. For example, a PDU session establishment may correspond to at least one of the following: a UE initiated PDU session establishment procedure; a UE initiated PDU session handover between 3GPP and non-3GPP; a UE initiated PDU session handover from EPS to 5GS; or a network triggered PDU session establishment procedure.Docket No.: 25-1028PCT

[0266] For example, a PDU session may be associated with at least one of the following: a single access type at a given time, i.e. either 3GPP access or non-3GPP access; or simultaneously with multiple access types, i.e. one 3GPP access and one non-3GPP access. A PDU session associated with multiple access types is referred to as multi access-PDU (MA PDU) session and it may be requested by ATSSS-capable UEs.

[0267] For example, in order for a UE to trigger a PDU session establishment procedure, it is assumed that the UE is already registered with the AMF meaning that the AMF has already retrieved the user subscription data from the UDM.

[0268] For example, in step 1 of FIG. 18, the UE may send a NAS message to the AMF, wherein the NAS message may comprise at least one or more of the following: S-NSSAI(s); alternative S-NSSAI; a UE Requested DNN; a PDU Session ID; a request type; an old PDU session ID; or an N1 SM container. The N1 SM container may comprise at least one or more of: a PDU session establishment request; or a port management information container. For example, in order to establish a new PDU Session, the UE may generate a new PDU Session ID. For example, the PDU session establishment request may comprise at least one or more of: a PDU session ID; a requested PDU session type; a requested SSC mode; a 5GSM capability; PCO; an SM PDU DN request container; a number of packet filters; a header compression configuration; a UE integrity protection maximum data rate; always-on PDU session requested; redundancy sequence number (RSN); URSP rule enforcement reports; or a PDU session pair ID.

[0269] For example, the request type may indicate "initial request" if the PDU session establishment is a request to establish a new PDU session and indicates "existing PDU session" if the request refers to an existing PDU session switching between 3GPP access and non-3GPP access or to a PDU session handover from an existing PDN connection in EPC. For example, the request type may indicate "emergency request" if the PDU session establishment is a request to establish a PDU session for emergency services.

[0270] For example, in step 1 of FIG. 18, the UE may indicate the number of packet filters supported for signaled QoS rules for the PDU Session that is being established. The number of packet filters indicated by the UE is valid for the lifetime of the PDU Session. In step 1, the UE may provide a UE integrity protection data rate capability independently of an access type over which the UE sends the PDU session establishment request. The UE integrity protection maximum data rate may indicate the maximum data rate up to which the UE can support UP integrity protection.

[0271] For example, the UE may include an S-NSSAI from the allowed NSSAI of the current access type or partially allowed NSSAI in step 1. If the UE is provided with the mapping of an S-NSSAI that is replaced by an alternative S-NSSAI, the UE may provide both the alternative S-NSSAI and the S-NSSAI that is replaced by it. The AMF may verify whether the alternative S-NSSAI and the S-NSSAI provided in the PDU session establishment request message is valid based on the UE context.Docket No.: 25-1028PCT

[0272] For example, the UE may include a capability to support reliable data service in the PCO of the PDU session establishment request message in step 1. If the UE requests to establish an always-on PDU session, the UE may include an always-on PDU session requested indication in the PDU session establishment request message in step 1 . For example, the UE may include a PDU session pair ID and / or RSN in the PDU session establishment request message in case the UE sets up two redundant PDU sessions over the 5G network supporting high reliability communication.

[0273] For example, in step 2, the AMF may select an SMF to handle a PDU session to be established based on at least one or more of the following: S-NSSAI(s); DNN; a PDU session ID; an old PDU session ID; an access type; an SMF-ID received from an UDM.

[0274] For example, in step 3, the AMF may create or update a session management (SM) context in the SMF selected in step 2 depending on whether the request type is "initial request" or "Existing PDU Session". To create the SM context, the AMF may send, for example, a Nsmf_PDUSession_CreateSMContext Request message. For example, the Nsmf_PDUSession_ CreateSMContext Request message may comprise at least one or more of the following: the SUPI; a selected DNN; the UE requested DNN; the S-NSSAI(s); the alternative S-NSSAI; a slice area restriction indication; the PDU Session ID; an AMF ID; the request Type; a PCF ID; a same PCF selection indication; a priority access; small data rate control status; an N1 SM container (PDU session establishment request); user location information; the access type, a RAT type; a PEI; a GPSI; UE presence in LADN service area; subscription for PDU session status notification; a DNN selection mode; trace requirements; a control plane CloT 5GS optimization indication or a control plane only indication; a control plane only indicator; a satellite backhaul category; a GEO satellite ID; provisioning server (PVS) FQDN(s); PVS IP address(es); an onboarding indication; or a disaster roaming service indication. For example, the SMF may configure a PDU session with the control plane only indication when the PDU session is for control plane CloT 5GS optimization.

[0275] To update the SM context, the AMF may send, for example, a Nsmf_PDUSession JJpdateSMContext Request message in step 3. For example, the Nsmf_PDUSession_Update SMContext Request message may comprise at least one or more of the following: the SUPI; the DNN; the S-NSSAI(s); an SM Context ID; an AMF ID; the request type; an N1 SM container (PDU session establishment request); user location information; an access type; a RAT type; a PEI; a serving network (a PLMN ID, or a PLMN ID and an NID), a satellite backhaul category; a GEO satellite ID; a PCF binding information; or a notification of SM policy association establishment indication.

[0276] For example, if the AMF does not have an association with an SMF for the PDU session ID provided by the UE (e.g. when the request type indicates "initial request"), the AMF may invoke the Nsmf_PDUSession_CreateSMContext Request message. On the other hand, if the AMF already has anDocket No.: 25-1028PCTassociation with an SMF for the PDU session ID provided by the UE (e.g. when the request type indicates "existing PDU session"), the AMF may invoke the Nsmf_PDUSession_UpdateSMContext Request message.

[0277] For example, when the AMF determines that the UE has priority subscription (e.g. MPS, MCX) in the UDM, the AMF may include a message priority header to indicate priority information in step 3. The SMF may use the message priority header to determine whether the UE request is subject to exemption from NAS level congestion control. For example, if an identity of an NWDAF is available to the AMF, the AMF may inform the SMF of the NWDAF ID(s) used for UE related analytics and corresponding analytics ID(s) in step 3.

[0278] For example, if session management subscription data for corresponding SUPI, DNN and S-NSSAI of the HPLMN is not available, then SMF may retrieve the session management subscription data from a UDM.

[0279] For example, in step 5, if the SMF receives Nsmf_PDUSession_CreateSMContext Request in step 3 and the SMF is able to process the PDU session establishment request, the SMF may create an SM context and respond to the AMF by providing the SM context ID.

[0280] For example, if the SMF needs to perform secondary authentication / authorization during the establishment of the PDU Session by a DN-AAA Server, the SMF may trigger a PDU session establishment authentication / authorization in step 6.

[0281] For example, if dynamic PCC is to be used for the PDU session, the SMF may performs a PDF selection in step 7a. For example, in step 7b, the SMF may perform an SM policy association establishment procedure to establish an SM policy association with the PCF and get the default PCC Rules for the PDU session.

[0282] For example, if the request type in step 3 indicates "Initial request", the SMF may select an SSC mode for the PDU session in step 8. The SMF may also select one or more UPFs as needed in step 8.

[0283] For example, the SMF may perform an SMF initiated SM policy association modification procedure to provide information on the policy control request trigger condition(s) that have been met in step 9.

[0284] For example, if the request type indicates "initial request", the SMF may initiate an N4 session establishment procedure with selected UPF(s) in step 10. On the other hand, when the request type indicates "existing PDU session", the SMF may initiate an N4 session modification procedure with the selected UPF(s). In step 10b, the selected UPF(s) acknowledge by sending an N4 session establishment / modification response.

[0285] For example, in step 11 , the SMF may provide at least one or more of the following to the AMF: the PDU Session ID; an N2 SM information; or an N1 SM container. The SMF may use Namf_Communication_N1 N2MessageTransfer message at least one or more of the following to the AMF: the PDU Session ID; the N2 SM information; or the N1 SM containerDocket No.: 25-1028PCT

[0286] For example, the N2 SM information may comprise at least one or more of the following: a PDU session ID; QFI(s); QoS profile(s); CN tunnel info; the S-NSSAI from the allowed NSSAI or partially allowed NSSAI; Session-AMBR; the PDU session type, user plane security enforcement information; a UE integrity protection maximum data rate; RSN; a PDU session pair ID; or a transport layer (TL)-container. For example, the N1 SM container may comprise a PDU session establishment accept message.

[0287] For example, the PDU session establishment accept message may comprise at least one or more of the following: QoS Rule(s) and associated UL protocol description(s) (if available); QoS flow level QoS parameters if needed for the QoS flow(s) associated with the QoS rule(s); a selected SSC mode; S-NSSAI(s); the UE Requested DNN; an allocated IPv4 address; an interface identifier; the Session-AMBR; a selected PDU session type; a reflective QoS Timer (if available); P-CSCF address(es); a control plane only indicator; header compression configuration; always-on PDU session granted; small data rate control parameters; small data rate control status; serving PLMN rate control; PVS FQDN(s); PVS IP address(es); or a non-3GPP QoS assistance information container.

[0288] For example, the SMF may include at least one or more of the following within the N1 SM and in the N2 SM information: one or more QoS rules; QoS flow level QoS parameters if needed for the QoS flow(s) associated with those QoS rule(s); or QoS profiles. For example, the SMF may provide the UE with per QoS-flow Non-3GPP QoS Assistance Information in the N1 SM container based on the S-NSSAI and DNN for a personal loT network (PIN).

[0289] For example, the AMF may send an N2 PDU session request to the (R)AN (e.g., NG-RAN) in step 12. For example, the N2 PDU session request may comprise at least one or more of the following: the N2 SM information; a NAS message; or one or more CN assisted RAN parameters tuning parameters. For example, the NAS message may comprise at least one or more of: the PDU Session ID; or the N1 SM container. For example, the N1 SM container may comprise the PDU session establishment accept message. For example, the AMF may send the NAS message containing the PDU Session ID and the PDU session establishment accept targeted to the UE and the N2 SM information received from the SMF within the N2 PDU session request to the (R)AN.

[0290] For example, the (R)AN may send the AN specific signaling exchange with the UE that is related with the information received from SMF. For example, the (R)AN may forward the NAS message (the PDU session ID, the N1 SM container (the PDU session establishment accept message)) provided in step 12 to the UE. For example, in the case of a NG-RAN, an RRC connection reconfiguration may take place with the UE establishing the requeired NG-RAN resources related to the QoS rules for the PDU session request received in step 12. For example, (R)AN also allocates (R)AN tunnel info for the PDU session. In the case of dual connectivity, a master RAN node may assign some (zero or more) QFIs to be set up at the master RAN node and others at a secondary RAN node. For example, the (R)AN tunnel info may include a tunnel endpoint forDocket No.: 25-1028PCTeach involved (R)AN node and the QFIs assigned to each tunnel endpoint. If the (R)AN receives two CN tunnel info for a PDU session in step 12 for redundant transmission, (R)AN may also allocate two (R)AN tunnel info correspondingly and indicate to the SMF that one of the (R)AN tunnel info is used as the redundancy tunnel of the PDU session.

[0291] For example, in step 14 of FIG. 18, the (R)AN may send an N2 PDU session response to the AMF. For example, the N2 PDU session response may comprise at least one or more of the following: the PDU Session ID; a cause; an N2 SM information. For example, the N2 SM information may comprise at least one or more of: PDU Session ID, (R)AN tunnel info; a list of accepted / rejected QFI(s); a user plane enforcement policy notification; a TL-container; established QoS flows status (active / not active); or a PDU set based handling support indication.

[0292] For example, in step 15 of FIG. 18, the AMF may send the N2 SM information received from (R)AN to the SMF. For example, the AMF may send the N2 SM information using a Nsmf_PDUSesslon_UpdateSMContext Request message. For example, if a list of rejected QFI(s) is included in the N2 SM information, the SMF may release one or more rejected QFI(s) associated QoS profiles.

[0293] For example, in step 16a of FIG. 18, the SMF may initiate an N4 session modification procedure with a UPF. The SMF may provide the (R)AN tunnel info to the UPF as well as the corresponding forwarding rules. For example, in step 16b, the UPF may send an N4 session modification response to the SMF. For example, in step 16c, the SMF may register with the UDM for a given PDU session.

[0294] For example, the SMF may send Nsmf_PDUSession_UpdateSMContext Response message to the AMF in step 17 of FIG. 18. The SMF may subscribe to the UE mobility event notification from the AMF (e.g. location reporting, UE moving into or out of area of interest). For example, in step 18 of FIG. 18, in case the PDU session establishment is not successful, the SMF may inform the AMF by invoking Nsmf_PDUSession_SMContextStatusNotify (Release) message.

[0295] For example, in case a PDU session is of IPv6 or IPv4v6 type, the SMF may generate an IPv6 router advertisement and send it to the UE in step 19 of FIG. 18. For example, in step 20, the SMF may initiate the SM policy association modification to provide 5GS bridge / router information to a PCF.

[0296] For example, in case the PDU session establishment failed after step 4, the SMF may unsubscribe to any modification of session management subscription data in step 21.

[0297] FIG. 19 illustrates an exemplary PDU session modification procedure as per an aspect of an embodiment of the present disclosure. For example, FIG. 19 illustrates a UE or network requested PDU session modification procedure either in a non-roaming or roaming with local breakout situation. For example, a UE or a network may trigger a PDU session modification procedure at least in one or more of the following cases: one or several of the QoS parameters exchanged between the UE and the network need to beDocket No.: 25-1028PCTmodified; to send updated ECS address configuration information to the UE; or to send updated DNS server address.

[0298] For example, the PDU session modification procedure may be triggered by at least one of: a UE; a PCF; an SMF; a RAN; or an AMF. For example, the UE may initiate the PDU session modification procedure by transmitting an NAS message. For example, the UE may initiate the PDU session modification procedure by transmitting an SM-NAS message. For example, the (SM-)NAS message may comprise at least one or more of the following: an N1 SM container; a PDU session ID; a UE integrity protection maximum data rate; or a port management information container. For example, the N1 SM container may comprise a PDU session modification request message. For example, the PDU session modification request message may comprise at least one or more of the following: the PDU session ID; one or more packet filters; an operation; requested QoS; segregation; a 5GSM core network capability; a number of packet filters; one or more URSP rule enforcement reports; an always-on PDU session requested; requested non-3GPP delay budget; or non-3GPP device connection information. For example, terminologies such as 5GSM capability and 5GSM core network capability mean the same - hence, are used interchangeably throughout the current disclosure.

[0299] For example, the UE may indicate a support for at least one or more of the following using the 5GSM core network capability: reflective QoS; a multi-homed IPv6 PDU session (if the requested PDU type is set to "IPv6" or "IPv4v6"); an ATSSS capability; a transfer of port management information containers; or (S)RTP multiplexed media identification information in IP packet filters.

[0300] For example, depending on the access type, if the UE is in the CM-IDLE state, the PDU session modification procedure may be preceded by a service request procedure. For example, an (R)AN may forward the SM-NAS message to the AMF with an indication of a user location Information. In turn, the AMF may invoke an operation to update an SM context associated with a PDU session which the PDU session modification procedure is associated with. For this purpose, the AMF may send an Nsmf_PDUSession_UpdateSMContext message to an SMF. For example, the Nsmf_PDUSession_UpdateSMContext message may comprise at least one or more of: an SM context ID; or the N1 SM container.

[0301] For example, when the UE requests specific QoS handling for one or more selected service data flows (SDFs), the UE may include at least one or more of the following in the PDU session modification request message: one or more packet filters describing the SDF(s); a requested packet filter operation (add, modify, delete) on the one or more packet filters; the requested QoS; or a segregation indication.

[0302] For example, a PCF may initiate an SM policy association modification procedure to notify SMF about the modification of policies. For example, the SM policy association modification procedure may trigger the PDU session modification procedure.Docket No.: 25-1028PCT

[0303] For example, an SMF may trigger the PDU session modification procedure due to at least one or more of the following: when an UDP updates session management (SM) subscription data; based on locally configured policy; triggered from the (R)AN; when UP connection is activated; to update QoS profile in the NG RAN; to send updated ECS address configuration information to the UE; to send updated DNS server address to the UE; or to send the EAS rediscovery indication to the UE.

[0304] For example, the (R)AN may trigger the PDU session modification procedure due to at least one or more of the following: when the (R)AN resources onto which a QoS flow is mapped are released; or when a notification control is triggered a GBR QoS Flow. For example, for this purpose, the (R)AN may send an N2 message comprising at least the PDU Session ID and / or N2 SM information to the AMF. The N2 SM information may comprise at least one or more of: the QFI; a user location Information; or an indication that the QoS Flow is released. For example, if notification control is configured for a GBR QoS flow, the N2 SM information may include the QFI and an indication that the QoS targets for that QoS Flow cannot be fulfilled or can be fulfilled again, respectively. For example, when QoS targets cannot be fulfilled, the N2 SM information may indicate a reference to an alternative QoS Profile matching the values of the QoS parameters that the NG-RAN is currently fulfilling.

[0305] For example, the AMF may trigger the PDU session modification procedure due to at least one or more of the following: when the AMF determines that a NAS-SM timer needs to be updated due to a change of enhanced coverage restriction; when a GEO Satellite ID needs to be updated to the SMF; to update NWDAF ID(s) used for UE related Analytics; when the AMF determines that an S-NSSAI is to be replaced with an alternative S-NSSAI; or when the AMF determines that the S-NSSAI is subject to an area restriction.

[0306] For example, in step 2 of FIG. 19, the SMF may report one or more subscribed events to the PCF by performing an SMF initiated SM policy association modification procedure.

[0307] For example, in step 2a of FIG. 19, the SMF may update a UPF with N4 Rules related to one or more new or modified QoS flow(s). For example, if redundant transmission has not been activated to the PDU session and the SMF decides to perform redundant transmission for the QoS flow, the SMF may indicate to the UPF to perform packet duplication and elimination for the QoS flow. For example, if redundant transmission has been activated on the PDU Session and the SMF decides to stop redundant transmission, the SMF may indicate the UPF to release an CN tunnel info which is used as the redundancy tunnel of the PDU session and also indicate the UPF to stop packet duplication and elimination for the corresponding QoS flow(s). For example, the SMF may make use of redundant transmission experience analytics provided by NWDAF, when SMF takes a decision whether to perform redundant transmission or stop redundant transmission if it has already been activated. For example, if the AMF initiated the PDU session modification procedure in step 1 h due to network slice replacement with the alternative S-NSSAI and if the SMF determines that the PDU session is retained, the SMF may send an N4 session modification request messageDocket No.: 25-1028PCTto the UPF to replace the S-NSSAI with the alternative S-NSSAI. For example, in step 2b, the UPF may respond to the SMF.

[0308] For example, in step 3a, the SMF may respond to the AMF especially for a UE or RAN orAMF initiated modification. For example, the SMF may respond using an Nsmf_PDU SessionJJpdateSMContext Response message. For example, the Nsmf_PDUSession_Update SMContext Response message may comprise at least one or more of: an N2 SM information; or an N1 SM container. For example, the N2 SM information may comprise at least one or more of: the PDU session ID; one or more QFI(s); one or more QoS profile(s); one or more alternative QoS profile(s)]; Session-AMBR; or one or more CN tunnel info(s). For example, the N1 SM container may comprise a PDU session modification command. For example, the PDU session modification command may comprise at least one or more of: the PDU session ID; one or more QoS rule(s) and associated UL protocol description(s) (if available); QoS rule operation; QoS flow level QoS parameters if needed for one or more QoS flow(s) associated with the one or more QoS rule(s); Session-AMBR, an always-on PDU session granted; a port management information container; or a non-3GPP QoS assistance information container. For example, the N2 SM information may carry information that the AMF may provide to the (R)AN. For example, the N1 SM container may carry the PDU session modification command that the AMF may provide to the UE.

[0309] For example, in case the UE triggers or sends the PDU session modification request message to modify a PDU session to an always-on PDU session, the SMF may include an always-on PDU session granted indication in the PDU session modification command to indicate whether the PDU session is to be changed to an always-on PDU session or not via the always-on PDU session granted indication in the PDU session modification command.

[0310] For example, in step 3b, for an SMF requested modification, the SMF may send an Namf_Communication_N1N2MessageTransfer message to the AMF. For example, in step 3c, for an SMF requested modification due to updated SMF-associated parameters from the UDM, the SMF may provide the SMF derived CN assisted RAN parameters tuning to the AMF. For example, in step 3d, for an SMF requested modification due to updated NWDAF ID, the SMF may inform the AMF of updates of the NWDAF I D(s) used for UE related analytics and corresponding analytics ID(s).

[0311] For example, in step 4, the AMF may send an N2 message to the (R)AN, where in the N2 message may comprise at least one or more of: an N2 SM information received from SMF; or a NAS message. For example, the NAS message may comprise at least one or more of: the PDU Session ID; or the N1 SM container. For example, the N1 SM container may comprise the PDU session modification command,

[0312] For example, in step 5, the (R)AN may send AN specific signaling to the UE that is related with the information received from the SMF. For example, an NG-RAN may send an RRC connection reconfigurationDocket No.: 25-1028PCTto the UE modifying the required (R)AN resources related to the PDU session or if N1 SM container is received in step 4 from AMP, RAN may transport the N1 SM container to the UE.

[0313] For example, in step 6, the (R)AN may acknowledge an N2 PDU session request by sending a N2 PDU session ack containing N2 SM information. For example, the N2 SM information may comprise at least one or more of: a list of accepted / rejected QFI(s); AN tunnel info; the PDU Session ID; secondary RAT usage data; TL-Container(s); a BAT offset; periodicity; an established QoS flows status (active / not active); or user location information.

[0314] For example, in step 7, the AMF may forward the N2 SM information and the user location information received from the AN to the SMF via a Nsmf_PDUSession_UpdateSM Context service operation. The SMF may reply with an Nsmf_PDUSession_UpdateSMContext response.

[0315] For example, in step 8, the SMF may update N4 session of the UPF(s) that are involved by sending an N4 session modification request message to the UPF.

[0316] For example, in step 9, the UE may acknowledge the PDU session modification command by sending a NAS message containing at least one or more of: the PDU session ID; or the N1 SM container. For example, the N1 SM container may comprise at least one or more of: an PDU session modification command ack; or port management information container.

[0317] For example, in step 10, the (R)AN may forward the NAS message to the AMF. For example, in step 11 , the AMF may forward the N1 SM container (PDU Session Modification Command Ack) and the user location information received from the AN to the SMF via the Nsmf_PDUSession_UpdateSMContext service operation. The SMF may reply with a Nsmf_PDUSession_UpdateSMContext response.

[0318] For example, in step 12, the SMF may update the N4 session of the UPF(s) that are involved by the PDU session modification by sending an N4 Session modification request message containing an N4 session ID to the UPF.

[0319] For example, in step 13, if the SMF interacted with the PCF in step 1b or 2, the SMF may notify the PCF whether the PCC decision could be enforced or not by performing an SMF initiated SM policy association modification procedure.

[0320] FIG. 20 illustrates an exemplary PDU session release procedure as per an aspect of an embodiment of the present disclosure. For example, FIG. 20 illustrates a UE or network requested PDU session release procedure in a non-roaming or roaming with local breakout situation. For example, a PDU session release procedure may be used to release one or more resources associated with a PDU session. The one or more resources comprise at least one or more of: one or more IP addresses / prefixes allocated for an IP-based PDU session including a release of multiple prefixes in the case of multi-homing; any UPF resource (including N3 / N9 / N19 termination) that was used by the PDU session; or any access resource that was used by the PDU session. For example, an SMF may notify any entity associated with a PDU session such as a PCF, aDocket No.: 25-1028PCTDN (e.g. when DN authorization has taken place at a PDU session establishment), etc. of a PDU session release.

[0321] For example, the PDU session release procedure allows a UE, an AMP, an SMF or a PCF to initiate release of radio and network resources associated with a PDU session. For example, as indicated by step 1a, a UE initiates a UE requested PDU session release procedure by sending an NAS message to a core network node via a (R)AN. For example, the core network node may be at least one of: an access and mobility management function (AMF); or a session management function (SMF). For example, the NAS message may comprise an N1 SM container. For example, the N1 SM container may comprise at least one or more of: a PDU session release request; or a PDU session ID. For example, the (R)AN may forward the NAS message to the AMF with an indication of a user location information. For example, the AMF may relay or forward the NAS message to an SMF handling a PDU session identified by a PDU session ID. For example, the AMF may invoke an Nsmf_PDUSession_UpdateSMContext service operation and send the N1 SM container to the SMF together with the user location information (ULI) received from the (R)AN. For example, depending on an access type, a UE may trigger a Service Request procedure before triggering the PDU session release procedure in case a UE is in the CM-IDLE state.

[0322] For example, as indicated by step 1b, a PCF may initiate a PDU session release procedure. For example, the PCF may invoke an SM policy association termination procedure to request a release of the PDU session. For example, as indicated by step 1c, an AMF may initiate a PDU session release procedure. For example, the AMF may invoke an Nsmf_PDUSession_ReleaseSMContext service operation to request a release of the PDU session in case there is a mismatch of PDU session status between the UE and the AMF or other cases where neither N1 nor N2 SM signaling may be needed before releasing an associated SM context. For example, the AMF may invoke the Nsmf_PDUSession_ReleaseSMContext service operation when the AMF determines to release the PDU session when an S-NSSAI is removed from an allowed NSSAI.

[0323] For example, as indicated by step 1 d, the (R)AN may initiate a PDU session release procedure. For example, the (R)AN may decide to indicate to the SMF that the PDU session related resource is released, e.g. when one or more the QoS flow(s) of the PDU session are released. For example, the SMF may decide whether to keep the PDU session with user plane connection deactivated or release the PDU session.

[0324] For example, the SMF may initiate a PDU session release procedure. For example, the SMF may decide to release a PDU session due to at least one or more of the following: based on a request from a DN (e.g., cancelling the UE authorization to access the DN); based on a request from the UDM (e.g., subscription change) or from the CHF; if the SMF receives an event notification from the AMF that the UE is out of LADN service area; based on locally configured policy (e.g. the release procedure may be related with the UPF reallocation for SSC mode 2 or mode 3); in case the (R)AN notifies the SMF that the PDU session resourceDocket No.: 25-1028PCTestablishment has failed during a mobility procedure; the SMF initiates release of an emergency PDU session when the UPF reports detection of PDU session inactivity for a specified period; based on a PDU session inactivity report from the UPF in case the S-NSSAI of a PDU session is subject to a usage control; or in case the AMF notifies the SMF that the S-NSSAI of the PDU session with SSC mode 1 or SSC mode 2 is to be replaced with an alternative S-NSSAI, and if the SMF determines that a new PDU session is to be established on the alternative S-NSSAI, the SMF initiates release of the PDU session.

[0325] For example, as indicated by step 1 f, the AMF may initiate a PDU session release procedure. For example, the AMF may invoke an Nsmf_PDUSession_UpdateSMContext service operation with a release indication to request the release of the PDU session because of at least one or more of the following: an N1 signaling and / or an N2 SM signaling may be needed before releasing the SM context with appropriate cause value (e.g. due to a change of the set of network slices for a UE where a network slice instance is no longer available); an AAA server triggered network slice-specific re-authentication and re-authorization fails; an AAA server triggered slice-specific authorization revocation takes place; the AMF determines that the control plane only indication associated with PDU session is not applicable any longer; a mobile base station relay (MBSR) authorization state is changed from "authorized" to "not authorized"; a mobile gNB with wireless access backhauling (MWAB) UE backhaul (BH) PDU session release is triggered due to S-NSSAIs / DNNs related to BH PDU sessions being removed from subscription or invalid; an associated network slice instance is congested or not available; or the PDU session is subject to LADN per LADN DNN and S-NSSAI and the AMF determines that the LADN service area for the DNN and S-NSSAI is removed (e.g. due to a notification from the UDM or local configuration update).

[0326] For example, when the SMF receives one of the triggers as indicated by steps 1a, 1b, 1c, 1e, or 1f of FIG. 20, the SMF may start the PDU session release procedure. For example, in step 2, the SMF may release one or more IP addresses / prefix(es) that were allocated to the PDU session and release associated user plane resources. For example, in step 2a, the SMF may send an N4 session release request (with an N4 session ID) message to one or more UPF(s) serving the PDU session. The one or more UPF(s) may drop any remaining packets of the PDU session and release tunnel resources and contexts associated with the N4 Session. For example, in step 2b, the one or more UPF(s) may acknowledge the SMF Request by sending an N4 session release response message. For example, the N4 session release response message may comprise at least one or more of: the N4 Session ID; small data rate control status; or APN rate control status.

[0327] For example, if the PDU session release procedure is triggered by steps 1a, 1b, 1d or 1e of FIG. 20, the SMF may create an N1 SM including a PDU session release command message. For example, a PDU session release command message may comprise at least one or more of: the PDU Session ID; a cause; or an alternative S-NSSAI. For example, the cause may indicate a trigger to establish a new PDU session with the same characteristics (e.g. when procedures related with SSC mode 2 are invoked). For example, if theDocket No.: 25-1028PCTcause value indicates that a PDU session re-establishment on the alternative S-NSSAI is required, the SMF may include the alternative S-NSSAI in the PDU session release command message. For example, in response, the UE may establish a new PDU session on the alternative S-NSSAI.

[0328] For example, step 3a of FIG. 20 may be used either when the UE triggers the PDU session release procedure in step 1a or when the (R)AN triggers the PDU session release procedure in step 1d. For example, in step 3a, the SMF may respond to the AMF with the Nsmf_PDUSession_UpdateSMContext response message. For example, the Nsmf_PDU SessionJJpdateSMContext response message may comprise at least one or more of: an N2 SM resource release request; or an N1 SM container. For example, the N1 SM container may comprise the PDU session release command. For example, the SMF may include the N2 SM resource release request in case the UE initiates the PDU session release procedure when the UP connection of the PDU session is active.

[0329] For example, step 3b of FIG. 20 may be used when the PDU session release procedure is initiated by the SMF or the PCF. In this case, for example, the SMF may invoke the Namf_Communication_N1N2MessageTransfer service operation while including an N1 SM container and / or a skip indicator. For example, the N1 SM container may comprise the PDU session release command. For example, if the UP connection of the PDU session is active, the SMF may include the N2 resource release request and / or the PDU session ID in the Namf_ Communication N2Message Transfer, to release the (R)AN resources associated with the PDU session. For example, the SMF may include the skip indicator to tell the AMF whether the AMF may skip sending the N1 SM container to the UE (e.g. when the UE is in CM-IDLE state).

[0330] For example, step 3c of FIG. 20 may be used when the PDU session release procedure is initiated by the AMF in step 1c. For example, step 3d of FIG. 20 may be used when the PDU session release procedure is initiated by the AMF in step 1f.

[0331] For example, in step 4, the AMF may send an N2 resource release request message to the (R)AN. For example, in step 4, the AMF may send an N2 SM request message to the (R)AN. For example, when the (R)AN receives the N2 SM request to release the access network (AN) resources associated with the PDU session, the (R)AN may issue AN specific signaling exchange(s) with the UE to release the corresponding access network (AN) resources in step 5. In the case of the NG-RAN, the NAS (e g., N2 SM request) message may be sent to the UE in an RRC message which may take place with the UE releasing the NG-RAN resources related to the PDU session. For example, in step 5, the (R)AN may send an NAS message with an N1 SM container including the PDU session release command received from the AMF.

[0332] For example, for the PDU Session of non-roaming subscribers, if the S-NSSAI of the released PDU session is subject to network slice usage control and there is no other PDU session using the S-NSSAI, the UE may start an access type-specific slice deregistration inactivity timer for the S-NSSAI.Docket No.: 25-1028PCT

[0333] For example, in step 6, if the (R)AN receives an N2 SM request to release the access network (AN) resources, the (R)AN may acknowledge the N2 SM resource release request by sending an N2 SM resource release ack message to the AMF. The (R)AN may include at least one of the following in the N2 SM resource release ack message: user location information; or secondary RAT usage data.

[0334] For example, in step 7a, the AMF may invoke the Nsmf_PDUSession_UpdateSM Context operation to the SMF. For example, the Nsmf_PDUSession_UpdateSMContext message may comprise at least one or more of: the N2 SM resource release ack; or user location information. For example, the N2 SM resource release ack may comprise secondary RAT usage data. For example, in step 7b, the SMF may respond to the AMF with the Nsmf_PDUSession_ UpdateSMContext response.

[0335] For example, in step 8, the UE may acknowledge the PDU session release command by sending an NAS message over the (R)AN. For example, the NAS message may comprise at least one or more of: the PDU session ID; or an N1 SM container. For example, the N1 SM container may comprise a PDU session release ack.

[0336] For example, in step 9, the (R)AN may forward the NAS message from the UE by sending a N2 NAS uplink transport (NAS message (PDU Session ID, N1 SM container (PDU Session Release Ack)), User Location Information) to the AMF. For example, the N2 NAS uplink transport may comprise at least one or more of: a NAS message; or user location information. For example, the NAS message may comprise at least one or more of: the PDU session ID; an N1 SM container. For example, the N1 SM container may comprise the PDU session release ack.

[0337] For example, in step 10a, the AMF may invoke the Nsmf_PDUSession_Update SMContext operation to the SMF. For example, the Nsmf_PDUSession_UpdateSMContext message may comprise at least one or more of: the N2 SM resource release ack; or user location information. For example, the N2 SM resource release ack may comprise secondary RAT usage data. For example, in step 10b, the SMF may respond to the AMF with the Nsmf_PDUSession_ UpdateSMContext response.

[0338] For example, in step 11 , the SMF may invoke the Nsmf_PDUSession_SM ContextStatusNotify operation to notify the AMF that the SM context for this PDU session is released. For example, for the PDU session of non-roaming subscribers, if the S-NSSAI of the released PDU session is subject to network slice usage control and if the SMF indicates the cause of slice inactivity and there is no other PDU session using the S-NSSAI, then AMF may remove the S-NSSAI from the allowed NSSAI or start an access type specific slice deregistration inactivity timer for the S-NSSAI.

[0339] For example, if dynamic PCC is applied to this session, the SMF may invoke an SM policy association termination procedure in step 12. For example, in step 13, the SMF may notify any entity that has subscribed to user location information related to a PDU session change.Docket No.: 25-1028PCT

[0340] For example, the released PDU session is the last PDU session SMF is handling for the UE for a given DNN and an S-NSSAI pair, the SMF may unsubscribe from a session management subscription data changes notification with the UDM in step 14. For example, the SMF may invoke a Nudm_SDM_Unsubscribe service operation while including at least one or more of: the SUPI; the DNN; or the S-NSSAI. In turn, the UDM may unsubscribe the subscription notification from the UDR.

[0341] For example, in step 15, the SMF may invoke the Nudm_UECM_Deregistration service operation while including the DNN and / or the PDU session ID. In return, the UDM may remove the association it had stored between the SMF identity and the associated DNN and PDU session ID. The UDM may update this information by triggering the Nudr_DM_Update service operation while including at least one or more of: the SUPI; subscription Data; or UE context in SMF data.

[0342] For example, the 5GC may provide policy information from the PCF to the UE. For example, the policy information given to the UE may include at least UE route selection policy (URSP). For example, the UE may use the URSP to determine how to route outgoing traffic. For example, traffic may be routed to an established PDU Session, may be offloaded to non-3GPP access outside a PDU session, may be routed via a ProSe layer-3 UE-to-network relay outside a PDU session, or can trigger the establishment of a new PDU Session.

[0343] For example, the URSP may include a prioritized list of URSP rules. A URSP rule may contain a traffic descriptor that determines when the URSP rule is applicable. A URSP rule may be determined to be applicable when every component in the traffic descriptor matches the corresponding information from the application. For example, each URSP rule may contain a list of route selection descriptors (RSDs) containing one or more route selection descriptors each having a different route selection descriptor precedence value.

[0344] For example, the traffic descriptor may comprise at least one or more of: application descriptors; IP descriptors; domain descriptors; non-IP descriptors; one or more connection capabilities; PIN ID; or connectivity group ID. For example, the application descriptors may comprise at least one of: an OSId; one or more OSAppld(s). For example, the OSId or the one or more OSAppld(s) may be used to identify one or more application(s) running in the UE's operating system (OS). For example, the OSId may not include an OS version number. For example, the OSAppId may not include a version number for the application. The IP descriptors may comprise 3 tuples(s) of a destination IP address. For example, the 3 tuple(s) may comprise at least one or more of: an IP address or IPv6 network prefix; a port number; or a protocol ID. For example, domain descriptors may comprise at least one of: FQDN(s); or a regular expression which is used as a domain name matching criterion. For example, non-IP descriptors may comprise descriptor(s) for destination information of non-IP traffic. For example, the one or more connection capabilities are matched against the information provided by a UE application when the UE application requests a network connection with certain capabilities. For example, a format and some values of connection capabilities may comprise at least one of: IMS; MMS; or Internet. For example, the format and values of one or more connection capabilities matchDocket No.: 25-1028PCToperator-specific one or more traffic categories. For example, the one or more traffic categories requested by the UE application are independent from the UE's Operating System.

[0345] For example, a route selection descriptor (RSD) may comprise at least one or more of the following: a session and service continuity (SSC) mode; network slice selection; DNN selection; PDU session type selection; non-seamless offload indication; ProSe layer-3 UE-to-network relay offload indication; ProSe multipath preference indication; access type preference; a PDU session pair ID; a redundancy sequence number (RSN); a time window; or location criteria. For example, the session and service continuity (SSC) mode may indicate that the traffic of the matching application may be routed via a PDU session supporting the SSC mode included. For example, the network slice selection may indicate that the traffic of the matching application may be routed via a PDU session supporting any of the included S-NSSAIs. For example, the DNN selection may indicate that the traffic of the matching application may be routed via a PDU session supporting any of the DNNs included. For example, the PDU session type selection may indicate that the traffic of matching application may be routed via a PDU session supporting the included PDU session type. For example, the non-seamless offload indication may indicate that traffic of the matching application may be offloaded to non-3GPP access outside of a PDU session when the rule is applied.

[0346] For example, the ProSe layer-3 UE-to-network relay offload indication may indicate that the traffic of the matching application may be sent via a ProSe layer-3 UE-to-network relay outside of a PDU session when the rule is applied. For example, ProSe multipath preference indication may indicate that the traffic of the matching application may be preferred to be sent via a PDU session over the Uu reference point and a ProSe layer-3 UE-to-network relay without N3IWF outside of a PDU session. For example, the access type preference may indicate the access type (3GPP or non-3GPP or multi-access) on which the PDU session is to be established. For example, the PDU session pair ID may be an indication shared by a plurality of redundant PDU sessions. For example, the time window may indicate that the RSD may not be considered valid outside of the time window. For example, the location criteria may indicate that the RSD may not be considered valid unless the UE's location matches the location criteria.

[0347] For example, an HPLMN PCF may provision (signal) a UE with URSP rules. For example, for every newly detected appl ication / P I N the UE may evaluate one or more URSP rules in the order of rule precedence and determine if the application / P IN is matching the traffic descriptor of any of the one or more URSP rules. For example, when the UE determines that a URSP rule is applicable for a given application / PIN, the UE may select a route selection descriptor within this URSP rule in the order of the route selection descriptor precedence. For example, when the UE finds a valid route selection descriptor, the UE may determine whether there is an existing PDU session that matches one or more components of the selected route selection descriptor. For example, the UE may compare one or more components of the selected route selection descriptor with one or more existing PDU sessions at least in one or more of the following ways: forDocket No.: 25-1028PCTa component which contains one value (e.g. SSC mode), the value of the PDU session needs to be identical to the value specified in the route selection descriptor; for a component which contains a list of values (e.g. Network Slice Selection), the value of the PDU session needs to be identical to one of the values specified in the route selection descriptor; or when the route selection descriptor includes a time window or a location criteria, the PDU session is considered matching if the PDU session is associated with an RSD that has the same time window or a location criteria validity conditions. For example, when a matching PDU session exists the UE may associate the appl ication / P I N with the existing PDU Session, i.e. route the traffic of the detected application / PIN on this PDU session. For example, if, on the other hand, none of the existing PDU sessions matches, the UE may try to establish a new PDU session using the values specified by the selected route selection descriptor.

[0348] For example, a route selection descriptor of a URSP rule may be considered valid if the following conditions are fulfilled: if one or more S-NSSAI(s) are present, the one or more S-NSSAI(s) are in an allowed NSSAI or in a partially allowed NSSAI for the non-roaming case and in the mapping of an allowed NSSAI (or of a partially allowed NSSAI) to HPLMN S-NSSAI(s) for the roaming case; if a DNN is present and the DNN is an LADN DNN, the UE needs to be in an area of availability of this LADN; if an access type preference is present and set to multi-access, the UE may support ATSSS; if a time window is present and the time matches what is indicated in the time window; if a location criteria is present and the UE location matches what is indicated in the location criteria; if ProSe layer-3 UE-to-network relay offload indication is present and the UE supports the ProSe capability of 5G ProSe layer-3 remote UE; and if ProSe multipath preference indication is present and the UE supports the ProSe capability of 5G ProSe layer-3 remote UE.

[0349] For example, if the UE does not find one or more S-NSSAIs appearing in the RSD in either the allowed NSSAI or partially allowed NSSAI during the validation of the route selection descriptor, the UE may request the one or more S-NSSAI(s) appearing in the RSD through a mobility registration update procedure to attempt to add the one or more S-NSSAI(s) to the allowed NSSAI (or to the partially allowed NSSAI),

[0350] For example, if a selected route selection descriptor contains a ProSe layer-3 UE-to-network relay offload indication and the UE has established a connection with a ProSe layer-3 UE-to-network relay, the UE may routes the traffic matching the traffic descriptor of the URSP rule (including the URSP rule with the "match-all" traffic descriptor) via the ProSe layer-3 UE-to-network relay outside of a PDU session.

[0351] FIG. 21 A, FIG. 21 B, FIG. 21 C and FIG. 21 D illustrate an example as per an aspect of an embodiment of the present disclosure. For example, most handheld devices or wireless devices (e.g., UE) are battery-powered and a network (e.g., 4G, 5G) may have little knowledge of battery capacity or current energy level of a UE. For example, in a potential implementation of existing technologies, any attempt to save energy of a UE may be solely placed on an operating system (OS) of the UE and there may not exist appropriate policies for a (cellular mobile) network to optimize traffic depending on current energy level or charging statusDocket No.: 25-1028PCTof the UE. For example, according to a recent survey or research on energy consumption analysis, roughly 25% of energy consumption may be attributed to maintaining constant connectivity to a cellular mobile network. For example, maintaining constant connectivity to a network can contribute to roughly 25% of energy consumption in a UE.

[0352] For example, solely relying on OS-based energy saving is not fully effective due to at least one of the following reasons: i) one or more network resources (e.g ., radio resources) allocated to a UE, for example, to ensure certain bit rate or latency or packet delay budget, are controlled by the network. For example, a UE may not be able to proactively reduce the resources allocated by the network. For example, the more resources the UE is allocated, the more energy the UE may consume making use of those resources; ii) Another relevant aspect that may largely determine the energy consumed by a UE is the distance to the base station that the UE is attached to. For example, the greater the distance to the base station, the more energy the UE needs to use to transmit radio signals.

[0353] For example, in a potential implementation of existing technologies (e.g., as of 3GPP Rel-19), based on a subscriber preference, a network may optimize energy usage within the network. This, however, may not consider an energy level of the UE. In addition, this mechanism may not apply to other subscribers who opt out from such an optimization that benefits a network operator.

[0354] For example, uncontrolled heavy traffic flowing may normally fully drain out a UE battery leaving a user in a helpless situation. For example, in a potential implementation of existing technologies, a radio resource allocation decision may not consider the energy level of a wireless device (e.g , UE). For example, allocating radio resources purely based on signal strength or QoS demand may fully drain out a battery of the UE, leaving an end user to situation where the end user is not able to make even an emergency call -this can be dangerous in a 911 situation.

[0355] FIG. 21A exemplarily illustrates resource allocation required to support a QoS profile 1 associated with a QoS flow 1 or a slice 1 (e.g., S-NSSAI 1). Although FIG. 21A depicts a grid of resource block, the actual resource elements or blocks required to support the QoS profile 1 or the slice 1 in relation to the QoS flow 1 may be smaller or larger than what is shown. FIG. 21 C exemplarily illustrates resource allocation required to support a QoS profile 2 associated with the QoS flow 1 or a slice 2 (e.g., S-NSSAI 2). Although FIG 21A depicts a grid of resource block, the actual resource elements or blocks required to support the QoS profile 2 or the slice 2 in relation to the QoS flow 1 may be smaller or larger than what is shown. However, it is assumed that the number of resource elements or blocks required to support the QoS profile 1 or the slice 1 is larger than the number of resource elements or blocks required to support the QoS profile 2 or the slice 2. For example, the QoS profile 1 may be superior than the QoS profile 2 in terms of QoS support. For example, the QoS support may be measured in terms of at least one or more of the following: a data rate; a bit rate; a maximum packet loss rate; a packet error rate; a packet delay budget; a latency; or a maximumDocket No.: 25-1028PCTdata burst volume (MDBV). For example, the bit rate may be measured in terms of at least one or more of the following: session or UE aggregated maximum bit rate (AMBR); guaranteed flow bit rate (GFBR); maximum flow bit rate (MFBR); per UE per slice maximum bit rate (UE-Slice-MBR). For example, supporting a high rate may require allocation of large amount of radio resources to the UE. For example, the higher the bit rate to support, the larger the amount of radio resources that may be required to be allocated to a UE. For example, the lower the packet error rate to support, the larger the amount of radio resources that may be required to be allocated to a UE. For example, the larger the amount of radio resources allocated to a UE, the greater the amount of energy a UE may consume.

[0356] For example, the QoS profile 1 may support higher data rate or bit rate than those of the QoS profile 2. For example, the QoS profile 1 may support larger maximum data burst volume (MDBV) than that of the QoS profile 2. For example, the QoS profile 1 may support lower packet delay budget or latency than that of the QoS profile 2. For example, the QoS profile 1 may support lower packet error rate than that of the QoS profile 2. For example, the QoS profile 1 may be strenuously demanding in terms of (radio) resource allocation and energy consumption at a UE when compared to those of the QoS profile 2.

[0357] For example, as illustrated by Fig. 21 B, if other conditions remain the same, suppose supporting the QoS flow 1 using the QoS profile 1 may fully drain the UE battery at time = t1. For example, as illustrated by Fig. 21 D, if other conditions remain the same, suppose running the QoS flow 1 using QoS profile 2 may fully drain the UE battery at time = t2 (> t1). For example, it is assumed that QoS profile 2 may be an alternative to QoS profile 1 - but in decreasing granularity in terms of the QoS support provided.

[0358] For example, the slice 1 may support higher data rate or bit rate than those of the slice 2. For example, the slice 1 may support larger maximum data burst volume (MDBV) than that of the slice 2. For example, the slice 1 may support lower packet delay budget or latency than that of the slice 2. For example, the slice 1 may support lower packet error rate than that of the slice 2. For example, suppose the slice 1 supports high data rate and low packet delay budget when compared to those of the slice 2. For example, the higher a bit rate to support, the larger the amount of radio resources that may be required to be allocated to a UE. For example, the lower a packet error rate to support, the larger the amount of radio resources that may be required to be allocated to a UE. For example, the larger the amount of radio resources allocated to a UE, the greater the amount of energy a UE may consume. For example, an energy consumption rate of the slice 1 may be higher than that of the slice 2. For example, the slice 1 may be strenuously demanding in terms of (radio) resource allocation and energy consumption at a UE when compared to those of the slice 2.

[0359] For example, as illustrated by Fig. 21 B, if other conditions remain the same, suppose supporting the slice 1 at the UE may fully drain the UE battery at time = t1. For example, as illustrated by Fig. 21 D, if other conditions remain the same, suppose supporting the slice 2 may fully drain the UE battery at time = t2 (> t1 ).Docket No.: 25-1028PCTFor example, it is assumed that slice 2 may be an alternative to slice 1 (e.g., alternative S-NSSAI) - but in decreasing granularity in terms of providing the QoS support.

[0360] In a potential implementation of existing technologies, given the fact that the network may not know instantaneous or current energy levels of the wireless device, the network may not make attempts to change alternative slices or alternative QoS profiles for the UE. This may result in speeding the draining out of a battery of the wireless device. For example, if a given UE application traffic is supported with the same QoS profile, the battery may be fully drained at time=t1.

[0361] For example, given that non-negligible portion of energy consumption may be attributed to maintaining constant network connectivity, in a potential implementation of existing technologies, leaving a rectifying action to an end user or an OS of a UE may lead to a loss of communications especially in emergency situations that can be life threatening. For example, a loss of communications may happen when a battery of a UE is fully drained out.

[0362] Embodiments of the present disclosure are related to an approach for solving the problems described above. These and other features of the present disclosure are described further below.

[0363] For example, a wireless device (e.g., a UE) may send to a core network node (e.g., SMF), a first message for a communication session, indicating that the wireless device supports a reporting of an energy level. For example, based on the first message indicating that the wireless device supports the reporting of the energy level, the wireless device may receive a second message from the core network node for the communication session, wherein the second message comprises at least one or more conditions for triggering the reporting of the energy level of the wireless device. For example, the wireless device may determine based on a first energy level of the wireless device, that a condition of the one or more conditions is fulfilled. For example, based on the condition being fulfilled, the wireless device may send a third message reporting the first energy level.

[0364] For example, the communication session may be at least one of: a protocol data unit (PDU) session; or packet data network (PDN) connection. For example, the first message may be at least one of: a session establishment message; a PDU session establishment request message; or a packet data network (PDN) connectivity request. For example, the second message may be at least one of: a session establishment accept message; a PDU session establishment accept message; or activate default EPS bearer context request. For example, the third message may be at least one of the following: a modification request message to change the level of QoS support per QoS flow per PDU session (e.g., a PDU session modification request message); or a release message to release one or more QoS flows of the PDU session (e.g., a PDU session release request).

[0365] For example, in case the third message is a modification request message to change the level of QoS support per traffic flow per communication session, the core network node may modify the level of QoSDocket No.: 25-1028PCTsupport given to each of one or more traffic flows that the communication session carries. For example, by replacing a high demanding (in terms of resource use and / or energy consumption) QoS support to a low demanding QoS support, the core network node may help the wireless device prolong a running time.

[0366] For example, in case the third message is a modification request message to change the level of QoS support per QoS flow per PDU session, the core network node may modify the level of QoS support given to each of one or more QoS flows that the PDU session carries. For example, by replacing a high demanding (in terms of resource use and / or energy consumption) QoS support to a low demanding QoS support, the core network node may help the wireless device prolong the running time of the wireless device.

[0367] For example, the running time may mean how far the wireless device can stay in an operational state before it runs out of battery energy (i e., before the wireless device is drained out of its battery). For example, the running time may be an operational time of the wireless device.

[0368] For example, in case the third message that the wireless device sends is the PDU session modification request message, the core network node may modify a QoS profile per each of one more QoS flows that the PDU session carries. For example, by changing a high demanding (in terms of resource use and / or energy consumption) QoS profile to a low demanding QoS profile, the core network node may help the wireless device prolong a running time.

[0369] For example, FIG. 22 exemplarily illustrates how the third message may help the core network node prolong the running or operational time of the UE or the wireless device. For example, suppose if QoS flow 1 uses QoS profile 1, the UE battery may drain out at time t3. However, if a UE triggers a PDU session modification procedure at time instance t1 (<t3) in order to get a QoS profile associated with a QoS flow 1 replaced from a more stringent QoS profile 1 to a less stringent QoS profile 2, suppose that the UE battery may drain out at time instance t5 (>t3). For example, a first condition is fulfilled at time = t1 . For example, at time=t1 , the current energy level of the wireless device (e.g., the first energy level or E1) falls below a first threshold (e.g., Threshold 1 of FIG. 22). For example, the wireless device may send the third message to the core network node by including the current energy level (e.g., the first energy level) when the first condition is fulfilled. For example, the first condition may be fulfilled when the current energy level falls or drops below a first threshold (e.g., Threshold 1 of FIG. 22).

[0370] For example, the core network node may receive the first energy level and based on the first energy level, determine an appropriate QoS profile per each of the one or more QoS flows that the PDU session carries. Based on determining the appropriate QoS profile per each of the one or more QoS flows that the PDU session carries, the core network node may decide on one or more appropriate QoS rules and send the one or more QoS rules to the wireless device. For example, the core network node may send to the wireless device at least one or more of: the one or more QoS rules; associated UL Protocol Description(s) (if available); one or more QoS flow level QoS parameters if needed for the one or more QoS flow(s) associatedDocket No.: 25-1028PCTrespectively with the one or more QoS rule(s); QoS rule operation and QoS flow level QoS parameters operation to notify the wireless device that the one or more QoS rules are added, removed or modified. For example, the core network node sends the appropriate QoS profile per each of the one or more QoS flows that the PDU session carries to a base station (e.g., (R)AN, NG-RAN) serving the wireless device. For example, the core network may modify or lower or downgrade the level of QoS provided to each of the one or more QoS flows the PDU session carries as a way to prolong running time of the wireless device.

[0371] For example, as depicted exemplarily in FIG. 22, the core network node may replace QoS profile 1 of QoS flow 1 by QoS profile 2 when the wireless device sends the third message on determining that the current energy level falls or drops below the first threshold (e.g., Threshold 1 of FIG. 22) at time=t1. For example, while keeping other factors constant or the same, by changing the QoS profile 1 to the QoS profile 2, the core network helps the wireless device prolong the running or operational time of the wireless device by (t5-t3) seconds or minutes or hours, where it is assumed that t5>t3.

[0372] For example, as exemplarily depicted in FIG.22, the wireless device may send the third message at time=t2 when the current energy level falls or drops below a second threshold (e.g., Threshold 2 of FIG. 22). For example, a second condition is fulfilled at time = t2. For example, the wireless device may send the third message to the core network node by including the current energy level (e.g., the second energy level) when the second condition is fulfilled. For example, the second condition may be fulfilled when the current energy level falls or drops below a second threshold (e.g., Threshold 2 of FIG. 22).

[0373] For example, as depicted exemplarily in FIG. 22, the core network node may replace QoS profile 2 of QoS flow 1 by QoS profile 3 when the wireless device sends the third message on determining that the current energy level falls or drops below the second threshold (e.g., Threshold 2 of FIG. 22). For example, while keeping other factors constant or the same, by changing a QoS profile 2 to QoS profile 3, the core network helps the wireless device prolong the running or operational time of the wireless device by (t6-t5) seconds or minutes or hours, where it is assumed that t6>t5. For example, similar behavior may be expected from the wireless device and the core network node, when a third condition is fulfilled; wherein the current energy level falls or drops below the third threshold (e.g., Threshold 3 of FIG. 22).

[0374] For example, the condition of the second message may comprise at least one of: a timer value for periodic reporting of the energy level; one or more thresholds for a threshold-based reporting of the energy level; or one or more event-based timer values for event-timer-based reporting of the energy level.

[0375] For example, the condition of the second message may comprise one or more events wherein an event may be fulfilled when the current energy level drops / falls below one of the one or more thresholds for the threshold-based reporting of the energy level. For example, the condition of the second message may comprise one or more events wherein an event may be fulfilled when the current energy level exceeds one of the one or more thresholds for the threshold-based reporting of the energy level.Docket No.: 25-1028PCT

[0376] For example, a wireless device (e.g., a UE) may send to a core network node (e.g., SME), a first message for a communication session, indicating that the wireless device supports a reporting of an energy level. For example, based on the first message indicating that the wireless device supports the reporting of the energy level, the wireless device may receive a second message from the core network node for the communication session, wherein the second message comprises at least one or more conditions for triggering the reporting of the energy level of the wireless device. For example, the wireless device may determine based on a first energy level of the wireless device, that a condition of the one or more conditions is fulfilled. For example, based on the condition being fulfilled, the wireless device may send a third message, for the communication session, reporting the condition being fulfilled.

[0377] For example, the communication session may be at least one of: a protocol data unit (PDU) session; or packet data network (PDN) connection.

[0378] For example, the third message may comprise a threshold of the one or more thresholds of the threshold-based reporting of the energy level; wherein the condition is fulfilled when the current energy level of the wireless device falls or drops below the threshold.

[0379] For example, the third message may comprise a threshold of the one or more thresholds of the threshold-based reporting of the energy level; wherein the condition is fulfilled when the current energy level of the wireless device exceeds the threshold.

[0380] For example, the third message may be at least one of the following: a modification request message to change the level of QoS support per QoS flow per PDU session (e.g., a PDU session modification request message); or a release message to release one or more QoS flows of the PDU session (e.g., a PDU session release request).

[0381] For example, when the core network node receives the third message and determines that the condition is fulfilled because the current energy level of the wireless device dropped or fell below the threshold, the core network may downgrade a QoS support per QoS flow of the one or more QoS flows that the PDU session carries.

[0382] For example, when the core network node receives the third message and determines that the condition is fulfilled because the current energy level of the wireless device exceeded the threshold, the core network may upgrade a QoS support per QoS flow of the one or more QoS flows that the PDU session carries.

[0383] For example, a wireless device (e.g., a UE) may send to a core network node (e.g., SME), a first message for a communication session, indicating that the wireless device supports a reporting of an energy level. For example, based on the first message indicating that the wireless device supports the reporting of the energy level, the wireless device may receive a second message from the core network node for the communication session, wherein the second message comprises at least one or more conditions forDocket No.: 25-1028PCTtriggering the reporting of the energy level of the wireless device. For example, the wireless device may determine based on a first energy level of the wireless device, that a condition of the one or more conditions is fulfilled. For example, based on the condition being fulfilled, the wireless device may send a third message, for the communication session, reporting an identifier of the condition being fulfilled.

[0384] For example, the communication session may be at least one of: a protocol data unit (PDU) session; or packet data network (PDN) connection.

[0385] For example, when the core network node receives the third message with the identifier of the condition being fulfilled, the core network may identify a threshold involved and determine whether the current energy level of the wireless device dropped below or exceeded the threshold involved when the condition was fulfilled. For example, depending on the threshold involved and whether the current energy level of the wireless device dropped below the threshold involved, the core network node may downgrade QoS support per traffic flow of the one or more traffic flows that the communication session carries. For example, depending on the threshold involved and whether the current energy level of the wireless device exceeded the threshold involved, the core network node may upgrade the QoS support per traffic flow of the one or more traffic flows that the communication session carries.

[0386] For example, when the core network node receives the third message with the identifier of the condition being fulfilled, the core network may identify a threshold involved and determine whether the current energy level of the wireless device dropped below or exceeded the threshold involved when the condition was fulfilled. For example, depending on the threshold involved and whether the current energy level of the wireless device dropped below the threshold involved, the core network node may downgrade QoS support per QoS flow of the one or more QoS flows that the PDU session carries. For example, depending on the threshold involved and whether the current energy level of the wireless device exceeded the threshold involved, the core network node may upgrade the QoS support per QoS flow of the one or more QoS flows that the PDU session carries.

[0387] For example, by allowing the core network node to know the key stages of a wireless device in terms of current energy level and to make measures to save energy by way of downgrading QoS support or releasing one or more communication sessions, the core network node may help the wireless device prolong the running or operational time of the wireless device. For example, these and other features of the present disclosure may drop a likelihood for a battery of the wireless device to be fully drained out. For example, these and other taught features of the present disclosure may drop a likelihood of a loss of communication because of a fully drained out battery of the wireless device. Example embodiments of the present disclosure solve the problems outlined earlier.

[0388] FIG. 23 illustrates an example as per an aspect of an embodiment of the present disclosure. For example, a wireless device (e.g., a UE) may send to a first core network node (e.g., SMF), a first messageDocket No.: 25-1028PCTfor a communication session, indicating that the wireless device supports a reporting of an energy level. For example, a wireless device that supports the reporting of the energy level may be termed energy level reporting (ELR) enabled wireless device. For example, support for reporting of an energy level may be encoded as part of at least one of: a 5GSM; protocol configuration options (PCO); or extended protocol configuration options (ePCO).

[0389] For example, based on the first message indicating that the wireless device supports the reporting of the energy level, the wireless device may receive a second message from the first core network node for the communication session, wherein the second message comprises at least one or more conditions for triggering the reporting of the energy level of the wireless device.

[0390] For example, the wireless device may determine based on a first energy level of the wireless device, that a condition of the one or more conditions is fulfilled. For example, based on the condition being fulfilled, the wireless device may send a third message reporting the first energy level.

[0391] For example, based on the reporting of the first energy level, the wireless device may receive a fourth message from the first core network node for the communication session. For example, the wireless device may send a fifth message acknowledging the fourth message.

[0392] For example, the communication session may be at least one of: a protocol data unit (PDU) session; or packet data network (PDN) connection. For example, the first message may be at least one of: a session establishment message; a PDU session establishment request message; or a packet data network (PDN) connectivity request. For example, the second message may be at least one of: a session establishment accept message; a PDU session establishment accept message; or activate default EPS bearer context request. For example, the third message may be at least one of the following: a modification request message to change the level of QoS support per QoS flow per PDU session (e.g . , a PDU session modification request message); or a release message to release one or more QoS flows of the PDU session (e.g., a PDU session release request) For example, the fourth message may be at least one of: a PDU session modification command; or a PDU session release command. For example, the fifth message may be at least one of: a PDU session modification command ack; or a PDU session release ack.

[0393] For example, the energy level of a wireless device may represent current charging status or charging level of a battery of the wireless device For example, the energy level of a battery may be a measure of electric charge of the battery. For example, the wireless device may comprise one or more batteries and the total energy available for use by the wireless device may be a total of energy level of each of the one or more batteries. For example, a battery may hold one or more charges, and the energy level of a battery may be a measure of how much charge(s) the battery holds. For example, the energy level of a battery may be a state-of-charge estimation. For example, the energy level of a battery may be an available capacity of one or more electrochemical cells making up the battery. For example, the amount of charge a battery holds may beDocket No.: 25-1028PCTtermed "state of charge" (e.g., SoC). For example, an accumulated or total energy level of one or more batteries powering a wireless device may be considered an energy level of the wireless device in the present disclosure. For example, a battery may be made up of one or more electrochemical cells and voltage per cell (VPC) for the individual cells makes up the total battery energy level.

[0394] For example, battery capacity may be a measure (typically in Amp-hr) of the charge stored by the battery and may be determined by the mass of active material contained in the battery. For example, the battery capacity may represent the maximum amount of energy that can be extracted from the battery under certain specified conditions. For example, the energy level of a battery may represent the battery capacity.

[0395] For example, an electrical battery powering a wireless device may be at least one of: a rechargeable battery, storage battery, or secondary cell. For example, an electrical battery or battery in short may be composed of one or more electrochemical cells.

[0396] For example, a battery may contain at least an electric charge and potential energy. For example, the fullness or emptiness of a battery may be expressed in Volt. For example, when a battery is full, the battery may contain the greatest amount of potential energy, and its Volt may be high. For example, as the battery is drained the Volt may drop because the battery has lost potential energy. For example, a battery may stop producing energy below a certain Voltage, usually about halfway.

[0397] For example, terminologies such as energy level, amount of charge being held, battery level, battery energy level, energy capacity, current energy level, remaining energy are used interchangeably throughout the present disclosure.

[0398] For example, terminologies such as the energy level of a battery, amount of charge a battery holds, battery level, battery energy level, energy capacity of a battery, current energy level of a battery, remaining energy of a battery are used interchangeably throughout the present disclosure.

[0399] For example, terminologies such as the energy level of a wireless device, the amount of charge a wireless device holds, battery level of a wireless device, battery energy level of wireless device, energy capacity of a wireless device, current energy level of a wireless device, remaining energy of a wireless device are used interchangeably throughout the present disclosure. For example, terminologies such as energy level, battery level, battery energy and energy value are used interchangeably throughout the present disclosure

[0400] For example, the energy level of a wireless device may mean an energy level of a battery of a wireless device throughout the present disclosure. For example, the energy level of a wireless device may mean the current energy level of the wireless device throughout the present disclosure. For example, the energy level of a wireless device may mean the remaining energy level of the wireless device throughout the present disclosureDocket No.: 25-1028PCT

[0401] For example, the energy level of a wireless device is measured in terms of at least one of: MilliAmpere hour (mAh); or Watt hour (Wh).

[0402] For example, a wireless device may use a measuring mechanism / technique / device, or a fuel gauging algorithm called a coulomb counter to measure (current) energy level of one or more batteries powering the wireless device. For example, the coulomb counter may measure the current from or to the one or more batteries as a way to calculate how much charge is "leaving" or "entering" the one or more battery.

[0403] For example, a fuel gauging algorithm of a wireless device may combine coulomb counting with periodic open-circuit voltage versus state-of-charge lookup tables for the purpose of exploiting the merits of each method to determine an accurate state-of-charge estimation or remaining capacity prediction.

[0404] For example, one or more conditions of the second message may comprise at least one of: a timer value for periodic reporting of the energy level; one or more thresholds for a threshold-based reporting of the energy level; or one or more event-based timer values for event-timer-based reporting of the energy level.

[0405] For example, one of the one or more thresholds may represent a first discrete energy level (e.g., energy value). For example, a first condition of the one or more conditions may refer to a case where the current energy level of the wireless device falls or drops below the first discrete energy level. For example, the first condition may be fulfilled when the current energy level of the wireless device falls or drops below the first discrete energy level. For example, the wireless device may report the current energy level when the first condition is fulfilled.

[0406] For example, one of the one or more thresholds may represent a first discrete energy level (e g., energy value). For example, a second condition of the one or more conditions may refer to a case where the current energy level of the wireless device exceeds or surpasses or goes above the first discrete energy level. For example, the second condition may be fulfilled when the current energy level of the wireless device exceeds or surpasses or goes above the first discrete energy level. For example, the wireless device may report the current energy level when the second condition is fulfilled.

[0407] For example, one of the one or more thresholds may represent a first discrete energy level (e.g., energy value) and a second discrete energy level (e.g., energy value). For example, a third condition of the one or more conditions may refer to a case where the current energy level of the wireless device lies between the first discrete energy level and the second discrete energy level. For example, the third condition may be fulfilled when the current energy level of the wireless device lies between the first discrete energy level and the second discrete energy level. For example, the wireless device may report the current energy level when the third condition is fulfilled.

[0408] For example, one of the one or more thresholds may represent a first discrete energy level (e.g., energy value) and a second discrete energy level (e.g., energy value), wherein the first discrete energy level is lower than the second discrete energy level. For example, a fourth condition of the one or more conditionsDocket No.: 25-1028PCTmay refer to a case where the current energy level of the wireless device is greater than the first discrete energy level and lower than the second discrete energy level. For example, the third condition may be fulfilled when the current energy level of the wireless device is greater than the first discrete energy level and lower than the second discrete energy level. For example, the wireless device may report the current energy level when the fourth condition is fulfilled.

[0409] For example, when a wireless device is configured with a timer value for periodic reporting of the energy level, the wireless device would start a first timer on receiving the second message. For example, when the first timer expires, a fifth condition of the one or more conditions of the second message is fulfilled. For example, when the wireless device determines that first timer expires, the fifth condition of the one or more conditions of the second message is fulfilled. For example, when the fifth condition is fulfilled, the wireless device may report the current energy level.

[0410] For example, one of the one or more thresholds may represent a third discrete energy level (e.g., energy value). For example, a sixth condition of the second message may comprise a first event wherein the first event may be fulfilled when the current energy level of a wireless device drops / falls below third discrete energy level. For example, the wireless device may report the current energy level when the sixth condition is fulfilled. For example, the seventh condition of the second message may comprise of a second event wherein the second event may be fulfilled when the current energy level of the wireless device exceeds the third discrete energy level. For example, the wireless device may report the current energy level when the seventh condition is fulfilled.

[0411] For example, when a wireless device is configured with an event-based timer values for an eventtimer-based reporting of the energy level, the wireless device would start a second timer when the first event or the second event happens. For example, when the second timer expires, an eighth condition of the one or more conditions of the second message is fulfilled. For example, when the wireless device determines that the second timer expires, the eighth condition of the one or more conditions of the second message is fulfilled. For example, when the eighth condition is fulfilled, the wireless device may report the current energy level.

[0412] For example, reporting of energy level may mean the wireless device reporting the current energy level of the wireless device. For example, reporting the current energy level and reporting the energy level may be used interchangeably throughout the present disclosure

[0413] For example, the communication session may be at least one of: a protocol data unit (PDU) session; or packet data network (PDN) connection. For example, the first message may be at least one of: a session establishment message; a PDU session establishment request message; or a packet data network (PDN) connectivity request. For example, the second message may be at least one of: a session establishment accept message; a PDU session establishment accept message; or activate default EPS bearer context request. For example, the third message may be at least one of the following: a modification request messageDocket No.: 25-1028PCTto change the level of QoS support per QoS flow per PDU session (e.g., a PDU session modification request message); or a release message to release one or more QoS flows of the PDU session (e.g., a PDU session release request). For example, the fourth message may be at least one of: a PDU session modification command; or a PDU session release command. For example, the fifth message may be at least one of: a PDU session modification command ack; or a PDU session release ack.

[0414] For example, the first message may comprise at least one of: a PDU session establishment request message; a PDU session modification request message; a PDU session release request; or an UL NAS transport message. For example, the second message may be at least one of: a PDU session establishment accept; a PDU session modification command; a PDU session release command; or a DL NAS transport message. For example, the third message may comprise at least one of: a PDU session establishment request message; a PDU session modification request message; a PDU session release request; or an UL NAS transport message. For example, the fourth message may be at least one of: a PDU session establishment accept; a PDU session modification command; a PDU session release command; or a DL NAS transport message.

[0415] For example, a wireless device may decide whether the wireless device needs to establish or set up a communication session. For example, if the wireless device needs to establish the communication session, the wireless device (e.g., a UE) may send to a first core network node (e.g., SMF), a first message for the communication session, indicating that the wireless device supports a reporting of an energy level. For example, after sending the first message, the wireless device may start a first timer (e.g., T3580). For example, a wireless device that supports the reporting of the energy level is termed energy level reporting (ELR) enabled wireless device. For example, support for reporting of the energy level may be encoded as part of at least one of: a 5GSM; protocol configuration options (PCO); or extended protocol configuration options (ePCO). For example, the wireless device may indicate that the wireless device supports the reporting of the energy level using at least one of: the 5GSM capability information element; protocol configuration options (PCO); or extended protocol configuration options (ePCO).

[0416] For example, the wireless device may include at least one or more of the following in the first message: current energy consumption rate of the wireless device; a number of active applications in the wireless device; an identifier of each of one or more active applications running in the wireless device; a battery capability ID of the wireless device; a brand or brand identifier of the wireless device; a model or model identifier of the wireless device; a charging status; current energy level; or a charging rate

[0417] For example, based on the first message indicating that the wireless device supports the reporting of the energy level, the wireless device may check whether the wireless device receives a second message from the first core network node for the communication session. If the wireless device receives the second message, the wireless device may further check whether the second message comprises at least one orDocket No.: 25-1028PCTmore conditions for triggering the reporting of the energy level of the wireless device. If, on the other hand, the second message does not comprise at least the one or more conditions for triggering the reporting of the energy level, the wireless device may further consider at least one or more of the following: the wireless device is not authorized to report the energy level; or the first core network node does not support reporting of the energy level. If either the wireless device is not authorized to report the energy level or the first core network node does not support reporting of the energy level, the wireless device may exhibit legacy behavior in terms of establishing, modifying or releasing a communication session. For example, if the wireless device does not receive the second message after the expiry of the first timer (e.g., T3580), the wireless device may retransmit the first message.

[0418] For example, if the wireless device receives the second message, wherein the second message comprises at least the one or more conditions for triggering the reporting of the energy level, the wireless device may determine based on a first energy level of the wireless device, that a condition of the one or more conditions is fulfilled. For example, based on the condition being fulfilled, the wireless device may send a third message reporting the first energy level. For example, after sending the third message, the wireless device may start a second timer (e.g., T3581 or T3582)

[0419] For example, the condition being fulfilled may comprise at least one of: the first condition; the second condition; the third condition; the fourth condition; the fifth condition; the sixth condition; the seventh condition; or the eighth condition.

[0420] For example, based on the reporting of the first energy level, the wireless device may receive a fourth message from the first core network node for the communication session. For example, in case the third message is a modification request message to change the level of QoS support per traffic flow per communication session, the wireless device may receive the fourth message that may comprise one or more configuration parameters for modifying the communication session. For example, the one or more configuration parameters of the fourth message comprise at least one or more of: a PDU session ID; one or more QoS rule(s) and associated UL protocol description(s) (if available); QoS rule operation; QoS flow level QoS parameters if needed for one or more QoS flow(s) associated with the one or more QoS rule(s); Session-AMBR; an always-on PDU session granted; a port management information container; or a non-3GPP QoS assistance information container. For example, the wireless device may send a fifth message acknowledging the fourth message.

[0421] For example, if the wireless device does not receive the fourth message after the expiry of the second timer (e.g., T3581 or T3582), the wireless device may retransmit the third message.

[0422] For example, the first core network node may receive a first message via the (R)AN and a second core network node from a wireless device. For example, the first message may comprise at least one or more of: an indication indicating that the wireless device supports the reporting of the energy level; an identifier ofDocket No.: 25-1028PCTeach of one or more slices (e.g., S-NSSAIs); a communication session ID (e.g., PDU session ID); a requested session type (e.g., IPv4, IPv6, 1 Pv4v6 , Ethernet and unstructured); a requested session and service continuity (SSC) mode (e.g., SSC mode 1, SSC mode 2, SSC mode 3); or header compression configuration; or UE integrity protection maximum data rate. For example, the (R)AN may receive the first message and send the first message to the second core network node. For example, after making key checks such as verifying the UE location in case of satellite access and selecting the first core network node, the second core network node may forward the first message to the (selected) first core network node. For example, the second core network node may include at least one or more of the following before forwarding the first message to the first core network node: a SUPI; AMF ID; user location information; access type; RAT type, PEI; GPSI; or UE presence in LADN service area.

[0423] For example, the first message may further comprise at least one or more of the following: current energy consumption rate of the wireless device; a number of active applications in the wireless device; an identifier of each of one or more active applications running in the wireless device; a battery capability ID of the wireless device; a brand or brand identifier of the wireless device; a model or model identifier of the wireless device; a charging status; current energy level; or a charging rate.

[0424] For example, the battery capability ID may comprise at least one of: one or more manufacturer details (e.g., brand, model number); or a year of manufacture. For example, the battery capability may indicate at least one of: a full capacity of a battery; battery efficiency; charging rate; discharging rate; or depth of discharge. For example, battery efficiency may refer to the ratio of energy a battery can output compared to the amount of energy put into it during charging, essentially measuring how effectively the battery stores and releases electrical energy with minimal loss, usually expressed as a percentage. For example, higher efficiency means less energy may be wasted during the charging and discharging process. For example, the depth of discharge (DOD) of a battery may determine the fraction of power that may be withdrawn from the battery. For example, if the DOD of a battery is given by the manufacturer as 25%, then only 25% of the battery capacity may be used by the load.

[0425] For example, the battery capability ID may be determined from a type allocation code (TAO). For example, the TAG may be a key component of an international mobile equipment identity (IMEI). For example, the first eight digits of the IMEI may represent the TAC, which may identify a make and model of a wireless device.

[0426] For example, the first core network node may set the one or more conditions for triggering the reporting of the energy level of the wireless device based on the battery capability, which may be identified by the battery capability ID. For instance, the third core network node may maintain a repository of battery capabilities, wherein the battery capability ID may help the third core network node to retrieve corresponding battery capabilities.Docket No.: 25-1028PCT

[0427] For example, the first core network node may receive the first message together with the indication indicating that the wireless device supports the reporting of the energy level, a SUPI, a GPSI, and a PEI. For example, based on the indication indicating that the wireless device supports the reporting of the energy level, the first core network node may identify a third core network node, and send at least one or more of the following to the third core network: the SUPI; GPSI; the PEI; current energy consumption rate of the wireless device; a number of active applications in the wireless device; an identifier of each of one or more active applications running in the wireless device; a battery capability ID of the wireless device; a brand or brand identifier of the wireless device; a model or model identifier of the wireless device; a charging status; or a charging rate. For example, the first core network node may request analytics data to set one or more conditions for triggering the wireless device to report the energy level.

[0428] For example, given that current energy consumption rate of the wireless device, a number of active applications running in the wireless device, an identifier of each of one or more active applications running in the wireless device, a battery capability ID of the wireless device, a brand or brand identifier of the wireless device, a model or model identifier of the wireless device, a charging status or a charging rate may vary from one wireless device to another, the one or more conditions for triggering the wireless device to report the energy level may be unique to each wireless device.

[0429] For example, the first core network node may comprise at least one of: a session management function (SMF); or an NF responsible for managing a communication session. For example, the second core network node may comprise at least one of: an access and mobility management function (AMF); or a mobility management entity. For example, the third core network node may comprise at least one of: a network analytics function; an NWDAF; an energy information function (EIF); or a PCF.

[0430] For example, at least from a battery capability ID of the wireless device, a brand or brand identifier of the wireless device; a model or model identifier of the wireless device, the third core network node may determine the full battery capacity, year of manufacture and battery efficiency that would help the first core network node or the third core network node to set appropriate the one or more conditions for triggering the wireless device to report the energy level. For example, the one of the one or more conditions for triggering the wireless device to report the energy level may be wireless device specific.

[0431] For example, in case the third message is a modification request message to change the level of QoS support per traffic flow per communication session, the first core network node may modify the level of QoS support given to each of one or more traffic flows that the communication session carries. For example, by replacing a high demanding (in terms of resource use and / or energy consumption) QoS support to a low demanding QoS support, the first core network node may help the wireless device prolong a running time.

[0432] For example, based on setting one or more conditions for triggering the wireless device to report the energy level, the first core network node may send a second message to the wireless device for theDocket No.: 25-1028PCTcommunication session, wherein the second message comprises at least the one or more conditions for triggering the wireless device to report the energy level.

[0433] For example, the first core network node may receive a third message containing reporting of the first energy level. Based on the first energy level, the first core network node may determine an appropriate level of QoS support required for each of one or more traffic flows that the communication session carries for the purpose of extending or prolonging the running or operational time ofthe wireless device. For example, based on determining the appropriate level of QoS support required for each of the one or more traffic flows that the communication session carries, the first core network node may send a fourth message to the wireless device for the purpose of configuring a level of QoS support required for each of the one or more traffic flows that the communication session carries.

[0434] For example, the fourth message may comprise one or more configuration parameters for modifying the communication session. For example, the one or more configuration parameters of the fourth message comprise at least one or more of: a PDU session ID; one or more QoS rule(s) and associated UL protocol description(s) (if available); QoS rule operation; QoS flow level QoS parameters if needed for one or more QoS flow(s) associated with the one or more QoS rule(s); Session-AMBR; an always-on PDU session granted; a port management information container; or a non-3GPP QoS assistance information container. For example, the first core network node may receive a fifth message for the communication session.

[0435] For example, the communication session may comprise at least one of: a PDU session . For example, one of the one or more traffic flows may comprise at least one of: a QoS flow. For example, the level of QoS support required may comprise at least one of: a QoS profile.

[0436] For example, the fourth message may be at least one of: a PDU session modification command. For example, the fifth message may be at least one of: a PDU session modification command ack.

[0437] For example, in case the third message is a modification request message to change the level of QoS support per QoS flow per PDU session, the first core network node may modify the level of QoS support given to each of one or more QoS flows that the PDU session carries. For example, by replacing a high demanding (in terms of resource use and / or energy consumption) QoS support to a low demanding QoS support, the first core network node may help the wireless device prolong the running time of the wireless device.

[0438] For example, the running time may mean how far the wireless device can stay in an operational state before it runs out of battery energy (i.e., before the wireless device is drained out of its battery). For example, the running time may be an operational time of the wireless device.

[0439] For example, in case the third message that the wireless device sends is the PDU session modification request message, the first core network node may modify a QoS profile per each of one more QoS flows that the PDU session carries. For example, by changing a high demanding (in terms of resourceDocket No.: 25-1028PCTuse and / or energy consumption) QoS profile to a low demanding QoS profile, the first core network node may help the wireless device prolong a running time.

[0440] For example, the condition of the second message may comprise at least one of: a timer value for periodic reporting of the energy level; one or more thresholds for a threshold-based reporting of the energy level; or one or more event-based timer values for event-timer-based reporting of the energy level.

[0441] For example, the condition of the second message may comprise one or more events wherein an event may be fulfilled when the current energy level drops / falls below one of the one or more thresholds for the threshold-based reporting of the energy level. For example, the condition of the second message may comprise one or more events wherein an event may be fulfilled when the current energy level exceeds one of the one or more thresholds for the threshold-based reporting of the energy level.

[0442] For example, when the first core network node receives the third message and determines that the condition is fulfilled because the current energy level of the wireless device dropped or fell below a threshold of the one or more first thresholds, the first core network may downgrade a QoS support per QoS flow of the one or more QoS flows that the PDU session carries.

[0443] For example, the current energy level of the wireless device may be measured in terms of at least one of the following: milli-Ampere hour (mAh); or Watt hour (Wh).

[0444] For example, when the first core network node receives the third message and determines that the condition is fulfilled because the current energy level of the wireless device exceeded a threshold of the one or more first thresholds, the first core network may upgrade the QoS support per QoS flow of the one or more QoS flows that the PDU session carries.

[0445] For example, by replacing a high demanding (in terms of resource use and / or energy consumption) QoS support to a low demanding QoS support, the first core network node may help the wireless device prolong running or operational time of the wireless device.

[0446] For example, if the third message is a PDU session release request message or anything similar, the fourth and fifth message may respectively be a PDU session release command and PDU session release ack.

[0447] For example, if the first core network node receives the third message which is the PDU session release request message or anything similar, the first core network node may determine which QoS or traffic flows to release or whether to release the entire communication session. For example, if a few QoS flows are to be released, the first core network node may send appropriate one or more configuration parameters, one or more QoS rules, one or more QFIs in the fourth message. For example, on receiving the fourth message, the wireless device may act upon the one or more configuration parameters, the one or more QoS rules to help the first core network release one or more QoS flows identified by the one or more QFIs.Docket No.: 25-1028PCT

[0448] For example, by replacing a high demanding (in terms of resource use and / or energy consumption) QoS support to a low demanding QoS support or releasing high demanding QoS flows or PDU sessions, the first core network node may help the wireless device prolong running or operational time of the wireless device.

[0449] FIG. 24 illustrates an example as per an aspect of an embodiment of the present disclosure. For example, a wireless device (e.g., a UE) may send to a first core network node (e.g., SMF), a first message for a communication session, indicating that the wireless device supports a reporting of an energy levelbased condition (being fulfilled). For example, a wireless device that supports the reporting of the energy level or energy level-based condition (being fulfilled) may be termed energy level reporting (ELR) enabled wireless device. For example, support for reporting of an energy level-based condition (being fulfilled) may be encoded as part of at least one of: a 5GSM; protocol configuration options (PCO); or extended protocol configuration options (ePCO).

[0450] For example, based on the first message indicating that the wireless device supports the reporting of the energy level-based condition (being fulfilled), the wireless device may receive a second message from the first core network node for the communication session, wherein the second message comprises at least: one or more conditions for triggering the reporting of the energy level-based condition (being fulfilled) by the wireless device; or an identifier of each of the one or more (UE-specific) conditions for triggering the reporting of the energy level based condition.

[0451] For example, based on the first message indicating that the wireless device supports the reporting of the energy level-based condition (being fulfilled), the wireless device may receive a second message from the first core network node for the communication session, wherein the second message comprises at least: a first condition of one or more conditions for triggering the reporting of the energy level-based condition (being fulfilled) by the wireless device; or an identifier of the first condition of the one or more (UE-specific) conditions for triggering the reporting of the energy level based condition.

[0452] For example, the wireless device may determine based on an energy level ofthe wireless device, that a first condition of the one or more conditions is fulfilled. For example, based on the first condition being fulfilled, the wireless device may send a third message reporting the identifier of the first condition being fulfilled.

[0453] For example, based on the reporting of the identifier of the first condition being fulfilled, the wireless device may receive a fourth message from the first core network node for the communication session. For example, the wireless device may send a fifth message acknowledging the fourth message.

[0454] For example, the communication session may be at least one of: a protocol data unit (PDU) session; or packet data network (PDN) connection. For example, the first message may be at least one of: a session establishment message; a PDU session establishment request message; or a packet data network (PDN)Docket No.: 25-1028PCTconnectivity request. For example, the second message may be at least one of: a session establishment accept message; a PDU session establishment accept message; or activate default EPS bearer context request. For example, the third message may be at least one of the following: a modification request message to change the level of QoS support per QoS flow per PDU session (e.g . , a PDU session modification request message); or a release message to release one or more QoS flows of the PDU session (e.g., a PDU session release request). For example, the fourth message may be at least one of: a PDU session modification command; or a PDU session release command. For example, the fifth message may be at least one of: a PDU session modification command ack; or a PDU session release ack.

[0455] For example, the energy level of a wireless device may represent current charging status or charging level of a battery of the wireless device For example, the energy level of a battery may be a measure of electric charge of the battery. For example, the wireless device may comprise one or more batteries and the total energy available for use by the wireless device may be a total of energy level of each of the one or more batteries. For example, a battery may hold one or more charges, and the energy level of a battery may be a measure of how much charge(s) the battery holds. For example, the energy level of a battery may be a state-of-charge estimation. For example, the energy level of a battery may be an available capacity of one or more electrochemical cells making up the battery. For example, the amount of charge a battery holds may be termed "state of charge" (e.g., SoC). For example, an accumulated or total energy level of one or more batteries powering a wireless device may be considered an energy level of the wireless device in the present disclosure For example, a battery may be made up of one or more electrochemical cells and voltage per cell (VPC) for the individual cells make up the total battery energy level.

[0456] For example, battery capacity may be a measure (typically in Amp-hr) of the charge stored by the battery and may be determined by the mass of active material contained in the battery. For example, the battery capacity may represent the maximum amount of energy that can be extracted from the battery under certain specified conditions. For example, the energy level of a battery may represent the battery capacity.

[0457] For example, an electrical battery powering a wireless device may be at least one of: a rechargeable battery, storage battery, or secondary cell. For example, an electrical battery or battery in short may be composed of one or more electrochemical cells.

[0458] For example, a battery may contain at least an electric charge and potential energy. For example, the fullness or emptiness of a battery may be expressed in Volt. For example, when a battery is full, the battery may contain the greatest amount of potential energy, and its Volt may be high. For example, as the battery is drained the Volt may drop because the battery has lost potential energy. For example, a battery may stop producing energy below a certain Voltage, usually about halfway.Docket No.: 25-1028PCT

[0459] For example, terminologies such as energy level, amount of charge being held, battery level, battery energy level, energy capacity, current energy level, remaining energy are used interchangeably throughout the present disclosure.

[0460] For example, terminologies such as the energy level of a battery, amount of charge a battery holds, battery level, battery energy level, energy capacity of a battery, current energy level of a battery, remaining energy of a battery are used interchangeably throughout the present disclosure.

[0461] For example, terminologies such as the energy level of a wireless device, the amount of charge a wireless device holds, battery level of a wireless device, battery energy level of wireless device, energy capacity of a wireless device, current energy level of a wireless device, remaining energy of a wireless device are used interchangeably throughout the present disclosure. For example, terminologies such as energy level, battery level, battery energy and energy value are used interchangeably throughout the present disclosure.

[0462] For example, the energy level of a wireless device may mean an energy level of a battery of a wireless device throughout the present disclosure. For example, the energy level of a wireless device may mean the current energy level of the wireless device throughout the present disclosure. For example, the energy level of a wireless device may mean the remaining energy level of the wireless device throughout the present disclosure.

[0463] For example, the energy level of a wireless device is measured in terms of at least one of: MilliAmpere hour (mAh); or Watt hour (Wh).

[0464] For example, a wireless device may use a measuring mechanism / technique / device, or a fuel gauging algorithm called a coulomb counter to measure (current) energy level of one or more batteries powering the wireless device. For example, the coulomb counter may measure the current from or to the one or more batteries as a way to calculate how much charge is "leaving" or "entering" the one or more battery.

[0465] For example, a fuel gauging algorithm of a wireless device may combine coulomb counting with periodic open-circuit voltage versus state-of-charge lookup tables for the purpose of exploiting the merits of each method to determine an accurate state-of-charge estimation or remaining capacity prediction.

[0466] For example, one or more conditions may comprise at least one of: a timer value for periodic reporting of the energy level; one or more thresholds for a thresh old -based reporting of the energy level; a user consent to modify one or more traffic flows of a communication session; a user consent to release one or more traffic flows of a communication session; a user consent to release one or more communication sessions; or one or more event-based timer values for event-timer-based reporting of the energy level.

[0467] For example, one of the one or more thresholds may represent a first discrete energy level (e.g., energy value). For example, the first condition of the one or more conditions may refer to a case where the current energy level of the wireless device falls or drops below the first discrete energy level. For example,Docket No.: 25-1028PCTthe first condition may be fulfilled when the current energy level of the wireless device falls or drops below the first discrete energy level. For example, the wireless device may report the identifier of the first condition being fulfilled when the first condition is fulfilled.

[0468] For example, one of the one or more thresholds may represent a first discrete energy level (e.g., energy value). For example, the first condition of the one or more conditions may refer to a case where the current energy level of the wireless device exceeds or surpasses or goes above the first discrete energy level. For example, the first condition may be fulfilled when the current energy level of the wireless device exceeds or surpasses or goes above the first discrete energy level. For example, the wireless device may report the identifier of the first condition being fulfilled when the first condition is fulfilled.

[0469] For example, a first condition of the one or more conditions may refer to getting a user consent. For example, the first condition may be fulfilled when the wireless device receives at least one of: a user consent to modify one or more traffic flows of a communication session; a user consent to release one or more traffic flows of a communication session; a user consent to release one or more communication sessions. For example, the wireless device may report the current energy level when the first condition is fulfilled.

[0470] For example, one of the one or more thresholds may represent a first discrete energy level (e g., energy value) and a second discrete energy level (e.g., energy value). For example, the first condition of the one or more conditions may refer to a case where the current energy level of the wireless device lies between the first discrete energy level and the second discrete energy level. For example, the first condition may be fulfilled when the current energy level of the wireless device lies between the first discrete energy level and the second discrete energy level. For example, the wireless device may report the identifier of the first condition being fulfilled when the first condition is fulfilled.

[0471] For example, one of the one or more thresholds may represent a first discrete energy level (e.g., energy value) and a second discrete energy level (e.g., energy value), wherein the first discrete energy level is lower than the second discrete energy level. For example, the first condition of the one or more conditions may refer to a case where the current energy level of the wireless device is greater than the first discrete energy level and lower than the second discrete energy level. For example, the first condition may be fulfilled when the current energy level of the wireless device is greater than the first discrete energy level and lower than the second discrete energy level. For example, the wireless device may report the identifier of the first condition being fulfilled when the first condition is fulfilled.

[0472] For example, when a wireless device is configured with a timer value for periodic reporting of the energy level, the wireless device would start a first timer on receiving the second message. For example, when the first timer expires, the first condition of the one or more conditions of the second message is fulfilled. For example, when the wireless device determines that the first timer expires, the first condition of the oneDocket No.: 25-1028PCTor more conditions of the second message is fulfilled. For example, when the first condition is fulfilled, the wireless device may report the identifier of the first condition being fulfilled.

[0473] For example, one of the one or more thresholds may represent a third discrete energy level (e.g., energy value). For example, the first condition of the second message may comprise a first event wherein the first event may be fulfilled when the current energy level of a wireless device drops / falls below third discrete energy level. For example, the wireless device may report the current energy level when the first condition is fulfilled. For example, the first condition of the second message may comprise of a second event wherein the second event may be fulfilled when the current energy level of the wireless device exceeds the third discrete energy level. For example, the wireless device may report the identifier of the first condition being fulfilled when the first condition is fulfilled.

[0474] For example, when a wireless device is configured with an event-based timer values for an eventtimer-based reporting of the energy level, the wireless device would start a second timer when the first event or the second event happens. For example, when the second timer expires, the first condition of the one or more conditions of the second message is fulfilled. For example, when the wireless device determines that the second timer expires, the first condition of the one or more conditions of the second message is fulfilled. For example, when the first condition is fulfilled, the wireless device may report the identifier of the first condition being fulfilled.

[0475] For example, the communication session may be at least one of: a protocol data unit (PDU) session; or packet data network (PDN) connection. For example, the first message may be at least one of: a session establishment message; a PDU session establishment request message; or a packet data network (PDN) connectivity request. For example, the second message may be at least one of: a session establishment accept message; a PDU session establishment accept message; or activate default EPS bearer context request. For example, the third message may be at least one of the following: a modification request message to change the level of QoS support per QoS flow per PDU session (e.g., a PDU session modification request message); or a release message to release one or more QoS flows of the PDU session (e.g., a PDU session release request). For example, the fourth message may be at least one of: a PDU session modification command; or a PDU session release command. For example, the fifth message may be at least one of: a PDU session modification command ack; or a PDU session release ack.

[0476] For example, the first message may comprise at least one of: a PDU session establishment request message; a PDU session modification request message; a PDU session release request; or an UL NAS transport message. For example, the second message may be at least one of: a PDU session establishment accept; a PDU session modification command; a PDU session release command; or a DL NAS transport message. For example, the third message may comprise at least one of: a PDU session establishment request message; a PDU session modification request message; a PDU session release request; or an ULDocket No.: 25-1028PCTNAS transport message For example, the fourth message may be at least one of: a PDU session establishment accept; a PDU session modification command; a PDU session release command; or a DL NAS transport message.

[0477] For example, a wireless device may decide whether the wireless device needs to establish or set up a communication session. For example, if the wireless device needs to establish the communication session, the wireless device (e.g., a UE) may send to a first core network node (e.g., SMF), a first message for the communication session, indicating that the wireless device supports a reporting the (identifier of the) first condition being fulfilled. For example, after sending the first message, the wireless device may start a first timer (e.g., T3580). For example, a wireless device that supports the reporting the (identifier of the) first condition being fulfilled is termed energy level reporting (ELR) enabled wireless device For example, support for reporting the (identifier of the) first condition being fulfilled may be encoded as part of at least one of: a 5GSM; protocol configuration options (PCD); or extended protocol configuration options (ePCO). For example, the wireless device may indicate that the wireless device supports the reporting the (identifier of the) first condition being fulfilled using at least one of: the 5GSM capability information element; protocol configuration options (PCO); or extended protocol configuration options (ePCO).

[0478] For example, the wireless device may include at least one or more of the following in the first message: current energy consumption rate of the wireless device; a number of active applications in the wireless device; an identifier of each of one or more active applications running in the wireless device; a battery capability ID of the wireless device; a brand or brand identifier of the wireless device; a model or model identifier of the wireless device; a charging status; current energy level; or a charging rate.

[0479] For example, based on the first message indicating that the wireless device supports the reporting the (identifier of the) first condition being fulfilled, the wireless device may check whether the wireless device receives a second message from the first core network node for the communication session. If the wireless device receives the second message, the wireless device may further check whether the second message comprises at least: the first condition of one or more conditions for triggering the wireless device to report the (identifier of the) first condition being fulfilled; or an identifier of the first condition of the one or more (UE-specific) conditions for triggering the wireless device to report the (identifier of the) first condition being fulfilled. If, on the other hand, the second message does not comprise at least the one or more conditions for triggering the wireless device to report the (identifier of the) first condition being fulfilled, the wireless device may further consider at least one or more of the following: the wireless device is not authorized to report the (identifier of the) first condition being fulfilled; or the first core network node does not support reporting the (identifier of the) first condition being fulfilled. If either the wireless device is not authorized to report the (identifier of the) first condition being fulfilled or the first core network node does not support reporting the (identifier of the) first condition being fulfilled, the wireless device may exhibit legacy behavior in terms ofDocket No.: 25-1028PCTestablishing, modifying or releasing a communication session. For example, if the wireless device does not receive the second message after the expiry of the first timer (e.g ., T3580), the wireless device may retransmit the first message.

[0480] For example, if the wireless device receives the second message, wherein the second message comprises at least: the first condition of one or more conditions for triggering the wireless device to report the (identifier of the) first condition being fulfilled; or an identifier of the first condition of the one or more (UE-specific) conditions for triggering the wireless device to report the (identifier of the) first condition being fulfilled, the wireless device may determine based on a first energy level of the wireless device, that a first condition of the one or more conditions is fulfilled. For example, based on the first condition being fulfilled, the wireless device may send a third message reporting the identifier of the first condition being fulfilled. For example, after sending the third message, the wireless device may start a second timer (e.g., T3581 or T3582).

[0481] For example, based on the reporting of the identifier of the first condition being fulfilled, the wireless device may receive a fourth message from the first core network node for the communication session. For example, in case the third message is a modification request message to change the level of QoS support per traffic flow per communication session, the wireless device may receive the fourth message that may comprise one or more configuration parameters for modifying the communication session. For example, the one or more configuration parameters of the fourth message comprise at least one or more of: a PDU session ID; one or more QoS rule(s) and associated UL protocol description(s) (if available); QoS rule operation; QoS flow level QoS parameters if needed for one or more QoS flow(s) associated with the one or more QoS rule(s); Session-AMBR; an always-on PDU session granted; a port management information container; or a non-3GPP QoS assistance information container. For example, the wireless device may send a fifth message acknowledging the fourth message.

[0482] For example, if the wireless device does not receive the fourth message after the expiry of the second timer (e.g., T3581 or T3582), the wireless device may retransmit the third message.

[0483] For example, the first core network node may receive a first message via the (R)AN and a second core network node from a wireless device. For example, the first message may comprise at least one or more of: an indication indicating that the wireless device supports the reporting of the energy level-based condition (being fulfilled); an identifier of each of one or more slices (e.g., S-NSSAIs); a communication session ID (e.g., PDU session ID); a requested session type (e.g., IPv4, IPv6, IPv4v6, Ethernet and unstructured); a requested session and service continuity (SSC) mode (e.g., SSC mode 1 , SSC mode 2, SSC mode 3); or header compression configuration; or UE integrity protection maximum data rate. For example, the (R)AN may receive the first message and send the first message to the second core network node. For example, after making key checks such as verifying the UE location in case of satellite access and selecting the firstDocket No.: 25-1028PCTcore network node, the second core network node may forward the first message to the (selected) first core network node. For example, the second core network node may include at least one or more of the ...

Claims

Docket No.: 25-1028PCTCLAIMS1. A method comprising:sending, by a wireless device to a session management function (SMF), an establishment request message, for a PDU session, indicating that the wireless device supports a reporting of an energy level;receiving, by the wireless device from the SMF and based on the sending, an establishment accept message, for the PDU session, comprising one or more conditions for triggering the reporting of the energy level of the wireless device;determining, by the wireless device and based on a first energy level of the wireless device, that a condition of the one or more conditions is fulfilled; andsending, by the wireless device based on the determining, a modification request message, for the PDU session, reporting the first energy level.

2. A method comprising:sending, by a wireless device to a session management function (SMF), a first message, for a protocol data unit (PDU) session, indicating that the wireless device supports a reporting of an energy level;receiving, by the wireless device from the SMF and based on the sending, a second message, for the PDU session, comprising:a condition for triggering the reporting of the energy level of the wireless device; sending, by the wireless device based on the condition being met, a third message, for the PDU session, reporting a first energy level of the wireless device.

3. The method of claim 2, further comprising determining, by the wireless device and based on the first energy level of the wireless device, that the condition is fulfilled.

4. The method of one of claims 2 to 3, wherein the third message is at least one of:a PDU session modification request message; ora PDU session release request.

5. The method of one of claims 2 to 4, wherein the first message further comprises at least one of:current energy consumption rate;a number of active applications;an identifier of each of one or more active applications;a brand or brand identifier of the wireless device;a model or model identifier of the wireless device;a charging status;a charging source; orDocket No.: 25-1028PCTa charging rate.

6. The method of one of claims 2 to 5, wherein the condition of the second message comprises at least one of:a timer value for periodic reporting of the energy level;one or more thresholds for a threshold-based reporting of the energy level; orone or more event-based timer values for event-timer-based reporting of the energy level.

7. The method of claim 6, wherein the one or more event-based timer values indicate an energy level of the wireless device either falls below or exceeds the first energy level.

8. The method of one of claims 2 to 7, wherein the first message is at least one of:a PDU session establishment request message; ora packet data network (PDN) connectivity request.

9. The method of one of claims 2 to 8, wherein the second message comprises a first cause indicating that the reporting of an energy level by the wireless device is allowed.

10. The method of one of claims 2 to 9, wherein the second message comprises an address or an identifier of at least one of the following network functions for direct reporting of the energy level:an energy information function (EIF);a network data analytics function (NWDAF);a policy control function (PCF); oran access and mobility management function (AMF).

11. The method of claim 10, wherein the address comprises at least one or more of:fully qualified domain name (FQDN);IPv4;IPv6; orIPv4v6.

12. The method of one of claims 2 to 11, wherein the wireless device indicates that the wireless device supports the reporting of an energy level using at least one of:a 5GSM capability; oran extended protocol configuration option.

13. The method of one of claims 2 to 12, wherein the second message comprises a third cause indicating at least one of:insufficient energy at a UE;a UE energy-level-based PDU session modification; orUE energy-level-based PDU session release.Docket No.: 25-1028PCT14. The method of one of claims 2 to 13, wherein the second message is a PDU session establishment accept.

15. The method of one of claims 2 to 14, wherein the third message further comprises a field indicating at least one of:an energy level of the wireless device falls below the first energy level; oran energy level of the wireless device exceeds the first energy level.

16. The method of one of claims 2 to 15, further comprising receiving, by the wireless device from the SMF, a modification command message, for the PDU session, indicating that QoS is downgraded per QoS flow in order to prolong running time of the wireless device.

17. The method of one of claims 2 to 16, further comprising receiving, by the wireless device from the SMF, a modification command message, for the PDU session, indicating that QoS is upgraded per QoS flow.

18. A method comprising:sending, by a wireless device to a session management function (SMF), an establishment request message, for a PDU session, indicating that the wireless device supports a reporting of an energy level;receiving, by the wireless device from the SMF and based on the sending, an establishment accept message, for the PDU session, comprising:one or more first conditions for triggering the reporting of the energy level of the wireless device via a PDU session modification request message; andone or more second conditions for triggering the reporting of the energy level of the wireless device via a PDU session release request message;sending a first message, for the PDU session, reporting a first energy level, wherein the first message is one of:the PDU session modification request message in response to determining, based on the first energy level, that at least one of the one or more first conditions is satisfied; and the PDU session release request message in response to determining, based on the first energy level, that at least one of the one or more second conditions is satisfied.

19. A method comprising:sending, by a wireless device to an access and mobility management function (AMF), a registration request message indicating that the wireless device supports reporting of an energy level;receiving, by the wireless device from the AMF, a registration accept message comprising one or more S-NSSAIs for which the reporting of the energy level of the wireless device is supported;Docket No.: 25-1028PCTsending, by a wireless device to a session management function (SMF), an establishment request message, for a PDU session using an S-NSSAI of the one or more S-NSSAIs, indicating that the wireless device supports reporting of an energy level;receiving, by the wireless device from the SMF, an establishment accept message, for the PDU session, comprising one or more conditions for triggering the reporting of the energy level of the wireless device;determining, by the wireless device and based on a first energy level of the wireless device, that a condition of the one or more conditions is met; andsending, by the wireless device based on the determining, a modification request message, for the PDU session, reporting the first energy level.

20. A method comprising:sending, by a wireless device to a session management function (SMF), a PDU session establishment request message including a capability information indicating a support for energy consumption reporting;receiving, by the wireless device from the SMF, an accept message for the PDU session establishment request, comprising:a first cause indicating that energy consumption reporting is allowed;one or more granularity of energy consumption reporting;a timer for periodic energy consumption reporting; anda first threshold and a second threshold for one or more thresholds for energy consumption reporting;determining, by the wireless device, that a current energy consumption of the wireless device meets the second threshold; andtransmitting, by the wireless device based on the determining, a PDU session modification request message; wherein the PDU session modification request message includes at least one of:a second cause;the second threshold; orthe current energy consumption per the one or more granularity.21 . A method comprising:sending, by a wireless device to an access and mobility management function (AMF), a registration request message including a capability information indicating a support for one or more energy-level-based service adjustments;receiving, by the wireless device from the AMF, an accept message for the registration request message, comprising:Docket No.: 25-1028PCTa feature authorization indication for the one or more energy-based service adjustments; a first threshold and a second threshold for the one or more energy-based service adjustments;a first S-NSSAI applicable at the first threshold; anda second S-NSSAI applicable at the second threshold;determining, by the wireless device, that a current energy-level of the wireless device meets the second threshold; andtransmitting, by the wireless device based on the determining, a PDU session establishment request message; wherein the PDU session establishment request message includes the second S-NSSAI.

22. A method comprising:sending, by a wireless device to an access and mobility management function (AMF), a registration request message including a capability information indicating a support for one or more energy-level-based service adjustments;receiving, by the wireless device from the AMF, an accept message for the registration request message, comprising:a feature authorization indication for the one or more energy-based service adjustments;a first threshold and a second threshold for the one or more energy-based service adjustments;an S-NSSAI applicable at the first threshold; andan alternative S-NSSAI applicable at the second threshold;determining, by the wireless device, that a current energy-level of the wireless device meets the second threshold; andtransmitting, by the wireless device based on the determining, a PDU session establishment request message; wherein the PDU session establishment request message includes the alternative S-NSSAI.

23. A method comprising:sending, by a wireless device to an access and mobility management function (AMF), a registration request message including:a capability information indicating a support for one or more energy-level-based service adjustments; anda current energy-level of the wireless device; andDocket No.: 25-1028PCTreceiving, by the wireless device from the AMF, an accept message for the registration request, comprising:successful registration of the wireless device;authorization for the one or more energy-based service adjustments; a first threshold and a second threshold of the one or more energy-based service adjustments;a first allowed NSSAI applicable at the first threshold; anda second allowed NSSAI applicable at the second threshold;wherein, the current energy-level of the wireless device is greater than the first threshold and the second threshold.

24. A method comprising:sending, by a wireless device to an access and mobility management function (AMF), a registration request message including a capability information indicating a support for one or more energy-level-based service adjustments;receiving, by the wireless device from the AMF, an accept message for the registration request message, comprising:successful registration of the wireless device;authorization for the one or more energy-based service adjustments; and an address of an EIF; andupdating, by the wireless device, the EIF with a current energy-level of the wireless device.

25. A method comprising:sending, by a wireless device to an access and mobility management function (AMF), a registration request message including a capability information indicating a support for one or more energy-level-based service adjustments;receiving, by the wireless device from the AMF, an accept message for the registration request message, comprising:successful registration of the wireless device;authorization for the one or more energy-based service adjustments; a first threshold and a second threshold for the one or more energy-based service adjustments; anda first slice deregistration inactivity timer value and a second slice deregistration inactivity timer value of an on-demand S-NSSAI;wherein, the first slice deregistration inactivity timer value is applicable at the first threshold and the second slice deregistration inactivity timer value is applicable at the second threshold.Docket No.: 25-1028PCT26. A wireless device comprising one or more processors and memory storing instructions that, when executed by the one or more processors, cause the wireless device to perform the method of any of claims 1 to 26.

27. A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors of a wireless device, cause the wireless device to perform the method of any of claims 1 to 26.

28. A method, comprising:receiving, by a session management function (SMF) from a wireless device, an establishment request message, for a PDU session, indicating that the wireless device supports a reporting of an energy level;determining, based on the receiving, one or more conditions for triggering the reporting of the energy level of the wireless device;sending, by the SMF to the wireless device, an establishment accept message, for the PDU session, comprising the one or more conditions;receiving, by the SMF from the wireless device, a modification request message, for the PDU session, reporting a first energy level of the wireless device;determining, based on the first energy level, a QoS profile for each of one or more one or more QoS flows of the PDU session;sending, by the SMF to the wireless device, a modification command message, for the PDU session; andreceiving, by the SMF from the wireless device, a modification complete message, for the PDU session.

Images