WO2026020005A1 - Transmission Management Mobility - Google Patents

Abstract

A wireless device sends, to a base station and when the wireless device is in a no transmission zone (NTZ), a measurement report message, wherein transmission by the wireless device via one or more first frequency bands is restricted within the NTZ, and the measurement report message does not comprise a measurement report of one or more cells of a plurality of cells that are in the one or more first frequency bands.

Description

TITLE

Transmission Management Mobility

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 63/672,997, filed July 18,

2024, which is hereby incorporated by reference in its entirety.

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. 11 B 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. [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 illustrates an aspect of an example embodiment according to the present disclosure.

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

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

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

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

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

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

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

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

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

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

DETAILED DESCRIPTION

[0038] 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.

[0039] 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.

[0040] 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.

[0041] 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 or more.” 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.

[0042] 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 = {celH , 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.

[0043] 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. [0044] 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) K, 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.

[0045] 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.

[0046] 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.

[0047] 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.

[0048] 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.

[0049] 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.

[0050] 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.

[0051] 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).

[0052] 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.

[0053] 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.

[0054] 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.

[0055] 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.

[0056] 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. 1 B, mobile communication network 150 includes a 5G core network (5G-CN) 152, an NG-RAN 154, and UEs 156A and 156B (collectively UEs 156). These components may be implemented and operate in the same or similar manner as corresponding components described with respect to FIG 1 A.

[0057] 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 3GPP 4G 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).

[0058] As illustrated in FIG. 1 B, 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

[0059] 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.

[0060] 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 Exposure Function (NEF), a Unified Data Management (UDM), an Application Function (AF), and/or an Authentication Server Function (AUSF).

[0061] 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.

[0062] As shown in FIG. 1 B, 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. 1 B, 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. 1 B 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.

[0063] 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.

[0064] 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 4G radio-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.

[0065] 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. 1 B, 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.

[0066] 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.

[0067] 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.

[0068] 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. [0069] 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 flows and 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.

[0070] 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.

[0071] 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.

[0072] 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.

[0073] 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 handling between 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.

[0074] 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.

[0075] 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.

[0076] 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.

[0077] 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.

[0078] 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.

[0079] 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 EDGE 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.

[0080] 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.

[0081] 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 RHY 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:

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

[0083] - 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;

[0084] - a common control channel (CCCH) for carrying control messages together with random access; [0085] - a dedicated control channel (DCCH) for carrying control messages to/from a specific the UE to configure the UE; and

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

[0087] Transport channels are used between the MAC and RHY 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:

[0088] - a paging channel (RCH) for carrying paging messages that originated from the RCCH; [0089] -- a broadcast channel (BCH) for carrying the M IB from the BCCH;

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

[0091] - an uplink shared channel (UL-SCH) for carrying uplink data and signaling messages; and [0092] - a random access channel (RACH) for allowing a UE to contact the network without any prior scheduling.

[0093] 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:

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

[0095] - 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;

[0096] - 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;

[0097] - 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;

[0098] -- 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

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

[0100] 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 signals defined 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.

[0101] 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. [0102] 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.

[0103] 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.

[0104] 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 least one of three RRC states: RRC connected 602 (e.g., RRC_CONNECTED), RRC idle 604 (e.g., RRC_I DEE), and RRC inactive 606 (e.g., RRCJNACTIVE).

[0105] 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. 1 B, 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.

[0106] 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.

[0107] 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.

[0108] 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 mobility management 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).

[0109] 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.

[0110] 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.

[0111] 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.

[0112] A gNB, 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.

[0113] 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 parallel symbol 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.

[0114] 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.

[0115] 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.

[0116] 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 as needed for a transmission. These partial slot transmissions may be referred to as mini-slot or subslot transmissions.

[0117] 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.

[0118] 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.

[0119] 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.

[0120] 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.

[0121] 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.

[0122] 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 (potentially usable 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.

[0123] 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). [0124] 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.

[0125] 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.

[0126] 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.

[0127] 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).

[0128] 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 between configured BWPs may occur based on RRC signaling, DCI, expiration of a BWP inactivity timer, and/or an initiation of random access.

[0129] 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.

[0130] 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.

[0131] 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.

[0132] 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).

[0133] 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 UE using 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.

[0134] 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).

[0135] 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).

[0136] 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.

[0137] 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 be configured 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 UCI 1071 , UC1 1072, and UCI 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. [0138] 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

[0139] 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.

[0140] 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.

[0141] 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 within the 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.

[0142] 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.

[0143] 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.

[0144] 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.

[0145] 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 system information (RMSI) associated with the cell. The RMSI 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.

[0146] 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.

[0147] 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.

[0148] 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.

[0149] 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.

[0150] 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.

[0151] 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 the measurements. 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.

[0152] 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.

[0153] 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.

[0154] 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).

[0155] 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.

[0156] 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.

[0157] 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.

[0158] 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.

[0159] 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 may support 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.

[0160] 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. [0161] 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.

[0162] 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 symbol on 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.

[0163] 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. [0164] FIG. 11 B 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.

[0165] 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 (FDM), 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.

[0166] 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 may or 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.

[0167] 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).

[0168] 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 . This may 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.

[0169] 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.

[0170] 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).

[0171] 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.

[0172] 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 access procedure 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. [0173] 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). [0174] 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. [0175] 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-Con fig Index). 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.

[0176] 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).

[0177] 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.

[0178] 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-OccasionLisf) may indicate an association between the PRACH occasions and the one or more reference signals.

[0179] 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) .

[0180] 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:

[0181] 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 s sjd < 14), t_id may be an index of a first 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).

[0182] 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).

[0183] 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.

[0184] 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).

[0185] 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 of the 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.

[0186] 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).

[0187] 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., recoverySearchSpaceld). 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.

[0188] 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

[0189] 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 of the Msg 2 1312 (e.g., an RAR) illustrated in FIGS. 13A and 13B and/or the Msg 4 1314 illustrated in FIG. 13A.

[0190] 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.

[0191] 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.

[0192] 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).

[0193] 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.

[0194] 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 control information (DCI). In some scenarios, the PDCCH may be a group common PDCCH (GC-PDCCH) that is common to a group of UEs.

[0195] 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).

[0196] 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.

[0197] 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 SRS transmissions 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.

[0198] 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).

[0199] 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.

[0200] 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.

[0201] 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 of CCEs 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).

[0202] 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).

[0203] 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.

[0204] 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 the number 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.

[0205] 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”.

[0206] 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 PUCCH resource 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.

[0207] 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. 1 B, 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. [0208] 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.

[0209] 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.

[0210] 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.

[0211] 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 may receive 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.

[0212] 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.

[0213] 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.

[0214] 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.

[0215] 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) radio 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.

[0216] 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.

[0217] 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.

[0218] 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 an antenna port; and/or the like. These functions are illustrated as examples and it is anticipated that other mechanisms may be implemented in various embodiments.

[0219] 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.

[0220] 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.

[0221] 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. [0222] In the present disclosure, any two or more than two of the following sentences, paragraphs, (subbullets, points, actions, behaviors, terms, alternatives, aspects, examples, or claims described in the following invention(s) may be combined logically, reasonably, and properly to form a specific method.

[0223] In the present disclosure, any sentence, paragraph, (sub)-bullet, point, action, behaviors, terms, alternatives, aspects, examples, or claims described in the following in vention(s) may be implemented independently and separately to form a specific method.

[0224] In the present disclosure, dependency, such as "based on”, “more specifically”, “preferably”, “in one embodiment", “in one alternative”, “in one example”, “in one aspect”, “in one implementation”, etc., in the present disclosure is just one possible example which would not restrict the specific method.

[0225] In the present disclosure, it should be understood that any discussion of operations from the perspective of wireless device may also be applied to a base station. Reciprocal operations may not be stated explicitly for each and every operation, although it is implied and a part of the present disclosure. For example, when the present disclosure describes one or more embodiments in which a transmitter device (e.g., a wireless device or a base station) transmits a signal, a receiver device (e.g., a wireless device or a base station) receives the signal. Reciprocal determinations and/or timer operations may occur to ensure alignment between operations of the transmitter device and receiver device. Furthermore, as an example of reciprocal operations, a wireless device may determine a time to transmit a signal based on a grant and a base station may determine the time to receive the signal and/or determine the time to schedule the signal for the wireless device to transmit via the grant. Similarly, as another reciprocal operation, if a receiver device (e.g., a wireless device or a base station) monitors for a signal or monitors a channel, a transmitter device (e.g., a wireless device or a base station) transmits the signal or transmits the channel.

[0226] User Equipment (UE) may report its UE radio access capabilities which are static at least when the Base Station (BS) requests. The BS may request what capabilities for the UE to report based on band information. The UE capability may be represented by a capability ID, which may be exchanged in Non- Access Stratum (NAS) signaling over the air and in network signaling instead of the UE capability structure. [0227] UE may receive a UECapabilityEnquiry message from the BS. In response to the UECapabilityEnquiry message, UE may set the contents of UECapabilitylnformation message based on some conditions and/or UE may transmit the UECapabilitylnformation message to the BS.

[0228] BS may initiate a procedure to a UE in RRC_CONNECTED when it needs (additional) UE capability information. BS may retrieve UE capabilities after AS security activation. Network may not forward UE capabilities that were retrieved before Access Stratum (AS) security activation to the Core Network (CN).

[0229] UE may transmit, to BS, an UE assistance information via an IE UEAssistancelnformation. UE may transmit, to BS, an UE assistance information via an IE UEAssistancelnformation based on a configuration received from the BS. The configuration may be included in a Radio Resource Control (RRC) message (e.g., RRC Reconfiguration message).

[0230] Configured grants may be configured without the need for the UE to monitor possible UL retransmissions, thus increasing the number of power saving opportunities for the UE.

[0231] FIG. 17 illustrates an example as per an aspect of an embodiment of the present disclosure.

[0232] As illustrated in FIG. 17, an unmanned aerial vehicle (UAV, drone, uncrewed aerial vehicle, aerial vehicle, etc.) may move (fly over) different areas at an altitude. The UAV may comprise (be) a UE (e.g., a wireless device), the UAV may be an aerial UE type (e.g., a UE type in which a UE is attached to (integrated into, provide services to) the UAV, a UE type in which a UE operates in the UAV, above certain altitude, and/or the like). The UAV may be controlled remotely by a remote operator (or a remote application), the UAV may be controlled by a human onboard the UAV, the UAV may have an autonomous driving (flying) capability and/or the like. The UAV may be used for remote surveillance, for transportation, for logistics, and/or the like. The UAV may need to communicate with a remote server, for controlling, maneuvering, reporting, streaming, etc. For example, the UAV may transmit one or more uplink packets to the remote server, and/or may receive one or more downlink packets from the remote server. The UAV may use 4G connectivity (e.g., LTE, via E-UTRAN), 5G connectivity (e.g., NR via NG-RAN), 6G connectivity (e.g., 6G radio, 6G-RAN), and/or the like, to communicate with the remote server. The remote server may be associated with an application running on the remove server and/or may be interacting with one or more operators connected to the remote server. For the transmission of the one or more uplink packets, the UAV may use one or more uplink resources. The one or more uplink resources may be associated with one or more uplink frequencies and/or one or more time periods (slots, symbols). For the reception of the one or more downlink packets, the UAV may use one or more downlink resources. The one or more downlink resources may be associated with one or downlink frequencies and/or one or more time periods. In an example, a downlink frequency may be the uplink frequency. In another example, the downlink frequency may not be the uplink frequency.

[0233] In an example, one or more areas (e.g., locations, defined by geographical coordinates, and/or the like) may be designated as (indicated by) no transmission zone (NTZ, non-transmission zone, notransmission zone). The NTZ may be associated with one or more wireless devices (e.g., one or more transmitters, one or more communication devices, and/or the like), with one or more UAVs, with one or more UAVs communicating with one or more remote servers, and/or the like. The NTZ may be applicable to some wireless devices (UEs) (e.g., wireless device attached to (integrated with) UAVs) while the NTZ may not be applicable to other wireless devices (UEs) (e.g., wireless device on the ground). The NTZ may be applicable during some time periods (e.g., 10:00-11 :00, Tuesday), while the NTZ may not be applicable during other time periods (e.g., 12:00-13:00, Sunday). The NTZ may be applicable to some locations (e.g., an area near an airport, an area above 1KM above ground level), while the NTZ may not be applicable to other locations (e.g., within a shopping mall). One or more conditions (e.g., time periods, device types, locations, altitudes) where the NTZ is applicable (enforced) may be defined to ensure critical devices (machines, public safety devices, etc.) not to be impacted (interfered) by a certain wireless device operating above ground.

[0234] For example, a first UAV may fly from a first zone (e.g., area, location, cell, tracking area) to a third zone via a second zone. In the second zone, one or more machines may operate, and/or one or more factories may be located. In the first zone and/or in the third zone, there may be no critical equipment (e.g., no machine, no factory). The first UAV may use a first frequency (here, for simplicity reason, a single frequency is mentioned. It may be understood that the first frequency may comprise multiple frequencies, a range of frequencies, and/or the like) for communication toward the remote server. The one or more machines and/or the one or more factories may use the first frequency, for communication among the one or more machines or within the one or more factories. When the first UAV flies over the second zone, if the first UAV transmits and/or receives one or more packets, the transmission performed by the first UAV may generate interference to the one or more machines, because the first UAV uses the same frequency as the one or more machines. Because the first UAV flies over the one or more factories over the second zone, the transmission by the first UAV may cause line-of-sight (LOS) interference. On the other hand, one or more UEs on the ground (e.g., used by ground vehicle, pedestrian) may not cause interference to communication among the one or more machines, because the factory may be distant from nearby roads, or there may be no LOS interference because there are many objects between the one or more UEs on the ground and the one or more machines.

[0235] To prevent unwanted transmission caused by the first UAV from impacting the critical equipment (e.g., wireless device), the NTZ may be defined (enforced). When the first UAV is outside of (or out of, outside, exiting) the NTZ, the first UAV may not be restricted from using one or more frequencies defined (associated, allocated, effective, restricted, etc.) for the NTZ. When the first UAV is inside of (or in, entering) the NTZ, the first UAV may not be allowed to make transmission using the one or more frequencies defined (restricted) for the NTZ. This may help to protect communication of critical equipment (e.g., the one or more machines). However, the NTZ may cause reduced communication opportunity for the UAV, as shown in FIG. 18.

[0236] FIG. 18 illustrates an example as per an aspect of an embodiment of the present disclosure.

[0237] In an example, a UE (e.g., a UE of the UAV, a UE attached/integrated to the UAV) may have a first configuration parameter configuring the UE with information of a first NTZ. For example, the UE may be configured (receives from) with the first configuration parameter by a first entity (e.g., a manufacturer of the UE, in a ME (mobile equipment) of the UE). For example, the first configuration parameters may comprise one or more first parameters indicating one or more first areas (e.g., area 1 , area 2, list of cells, list of TAs, list of networks) of the first NTZ, and/or one or more second parameters indicating one or more frequencies restricted in the one or more first areas. The one or more frequencies may comprise a first frequency (e.g., F1). For example, the one or more first areas may not comprise one or more second areas (e.g., area 3). The first configuration parameters may help the UE to determine which area (e.g., location) belongs to the NTZ, and/or which frequencies are restricted

[0238] In an example, the UE may camp on a first cell of a first base station. For example, the first cell may be configured with the first frequency and/or the first cell may not comprise a portion of the one or more first areas. For example, the first cell may be configured with the first frequency and/or the first cell may not comprise any portion of the one or more first areas. In an example, based on the first configuration parameter and/or based on measuring current location of the UE, the UE may determine that the UE is not within the one or more first areas, and/or the UE may perform transmission via one or more first configured frequencies of the first cell.

[0239] In an example, the UE may move out of a first coverage of the first cell and/or may move into a second coverage area of one or more second cells of a second base station. The one or more second cells may be configured with one or more uplink frequencies. For example, the one or more uplink frequencies of the one or more second cells may comprise the first frequency (e.g., F1) and/or a second frequency band (e.g., F2).

[0240] In an example, the UE may search/ detect/ monitor one or more neighboring cells of the first cell. In some technologies, because the UE uses the first frequency of the first cell, because the first frequency is also configured for the one or more second cells, and/or because a signal quality (e.g., RSRP, RSRQ, of RS, and/or the like) of the first frequency of the one or more second cells are above a threshold (e.g., RSRP threshold, RSRQ threshold), the UE may determine to select the first frequency of the one or more second cells, for a cell reselection procedure.

[0241] In an example, at least a portion of the one or more second cells may comprise partially the one or more first areas. In an example, at least a portion of the one or more second cells may comprise entirely the one or more first areas. When the UE reselects to the one or more second cells, if the UE determines that the UE enters the one or more first areas, the UE may determine that the first frequency is one of the one or more restricted frequencies and/or the UE may stop transmission to the one or more second cells. This may result that the UE cannot communicate data. This may raise a critical issue if the UE is remotely controlled by a remote server.

[0242] In other example, after the UE is configured with the first configuration parameters, the information of the first NTZ may change. For example, an impacted area of the first NTZ may increase, decrease, and/or change. For example, a first portion of the one or more first areas may be removed from the one or more first areas, and/or one or more additional areas may be added to the one or more first areas. In another example, the one or more restricted frequencies may change (e.g., some are added, some are removed). For example, due to increased demand for critical devices (e.g., radars), more frequencies may be designated as restricted and/or more areas may be designated as restricted.

[0243] For example, one or more areas (e.g., the area 3) of the one or more second areas may be added for the first NTZ. For example, the UE may move to the area 3. In some technologies, based on the first configuration parameters, the UE may determine that the UE is not in the NTZ and/or the UE may determine to use the first frequency based on determining that the UE is not in the NTZ. This may cause interference and/or may generate undesirable signals. In other example, if the UE receives second configuration parameters indicating a second NTZ, the UE may have an issue because the UE may not be able to determine which configuration parameter is valid.

[0244] Example embodiments of the present disclosure solve the above issues by receiving one or more configurations of one or more neighbor cells, by checking whether one or more UL frequencies of the one or more neighbor cells are not restricted, by performing cell reselection to a target cell having one or more uplink resources not restricted by the NTZ, and/or the like. This may help in reducing unnecessary cell- reselection to a cell not providing relevant uplink resources to the UE. In another example, for efficient use of power of a UE, the UE may consider whether a neighboring cell has a non-restricted uplink resource, may determine one or more priorities of one or more candidate frequencies, may determine whether to send a measurement report, and determine whether to perform a measurement of the cell. This may help the UE to reduce unnecessary power consumption. In another example, a first base station may receive from a second base station, information of one or more cells and/or restriction of the one or more cells. This may help the first base station to determine a target cell for handover and/or to construct a system information. In another example, a paging information may comprise restriction information to assist paging efficiency. In another example, a UE may receive one or more configurations for one or more NTZs, and the UE may compare and determine one or more priorities of the one or more configurations and select a configuration of the one or more configurations of the NTZ. This may help in preventing the UE from using inaccurate configurations for the NTZ.

[0245] In the specification, the term “network system” may be interpreted as, or may refer to, a communication system, and/or a generation of the communication system. For example, one or more network systems may comprise an EPS, a 5GS, a 6th generation (6G) system, and/or the like. For example, a first network system may be the EPS The EPS may comprise of one or more UEs, one or more eNB, one or more en-gNBs, and/or one or more EPCs. The one or more EPCs may comprise a MME, a SGW, a PGW (e.g., a PGW-C+SMF, a PGW-U+UPF), HSS, PCRF, and/or the like. For example, a second network system may be the 5GS. The 5GS may comprise of one or more UEs, one or more g N B , one or more ng-eNBs, one or more 5G core networks. The one or more 5G core networks may comprise one or more core network nodes. The one or more core network nodes may comprise an AMF, a SMF, a PCF, a UPF, a UDM, a NEF, and/or the like. In some embodiments, a core network node may be a combination of one or more core network nodes of one or more core networks. For example, a SMF+PGW-C (e.g., PGW- C+SMF) may act as both a SMF and a PGW (e.g., PGW-C). For example, a SMF may act as a 5G core network node and a 6G core network node. For example, a third network system may be a 6th generation (6G) system (6GS). The 6GS may comprise of one or more UEs, one or more 6G-RAN (e.g., a radio access network node of 6G system), one or more 6gNBs (e.g., an equivalent of gNB for 6GS), one or more 6G core networks. The one or more 6G core networks may comprise one or more 6G core network nodes (e.g , 6G core network functions). Each of the one or more core network nodes may support (implement) one or more functions (or services) provided by each of the one or more 5G core network nodes. For example, a node of the 6GS may perform a function of a radio access network and/or one or more roles performed by one or more 6G core network nodes (or by 5G core network nodes).

[0246] In the specification, the term “5G System” may be interpreted as, or may refer to, a 3GPP system consisting of at least one of 5G access network (or NG-RAN), 5G core network and/or a UE [0247] In the specification, the term "EPS” may be interpreted as, or may refer to, a 3GPP system consisting of at least one of EPC, E-UTRAN and/or a UE.

[0248] In the specification, the term "network node” may be interpreted as, or may refer to, at least one of a core network node, an access node, a base station, a UE, the like, and/or a combination thereof. A network may comprise one or more network nodes.

[0249] In the specification, the term "core network node” may be interpreted as, or may refer to, a core network device, which may comprise at least one of an AMF, a SME, a NSSF, a UPF, a NRF a UDM, a PCF, a SoR-AF, an AF, an DDNMF, an MB-SMF, an MB-UPF, a MME, a SGW, a PGW, a SMF+PGW-C, a SMF+PGW-U, a UDM+HSS and/or the like. The core network node may be a 5G core network node, a 6G core network node, a 4G core network node, the likes, and/or a combination thereof. One or more names may be used by a core network node. A function performed by a first core network node of 5GS may be performed by a second core network node of 6GS.

[0250] In the specification, the term “5G core network" may be interpreted as, or may refer to, a core network connecting to a 5G access network. This may be 5G core (5GC).

[0251] In the specification, the term "RAT type” may be interpreted as, or may refer to, identifying the transmission technology used in the access network for 3GPP accesses and/or for non-3GPP accesses. For example, RAT type for 3GPP access may comprise at least one of NR, NB-IOT, E-UTRA, 6GR (i.e., a radio access technology of 6GS) and/or the like. For example, RAT type for non-3GPP access may comprise at least one of untrusted non-3GPP, trusted non-3GPP, trusted IEEE 802 11 non-3GPP access, Wireline, Wireline-Cable, Wireline-BBF, WiFi, etc.

[0252] In the specification, the term "3GPP RAT” may be interpreted as, or may refer to, a radio access technology based on 3rd generation partnership (3GPP) project. For example, this may comprise at least one of a NR, a E-UTRA, UTRA, GSM, 6GR (6G radio), the like, and/or a combination thereof.

[0253] In the specification, the term "N3GPP RAT" may be interpreted as, or may refer to, a radio access technology not based on 3rd generation partnership project. This may be an access technology not developed by 3GPP. For example, this may comprise a WiFi, trusted WiFi, non-trusted WiFi, fixed access, wireline broadband, the like, and/or a combination thereof.

[0254] In the specification, the term "5G access network” may be interpreted as, or may refer to, an access network comprising at least one of a NG-RAN and/or non-3GPP RAN, and connecting to a 5G core network.

[0255] In the specification, the term “3GPP RAN” may be interpreted as, or may refer to, a radio access network using 3GPP RAT. For example, this may comprise at least one of a g N B, an eNB, a ng-eNB, an en-gNB, the like, and/or a combination thereof. For example, this may be at least one of an E-UTRAN, NG- RAN, 6G-RAN (6th generation RAN), the like, and/or a combination thereof. The 3GPP RAN may be 3GPP access node.

[0256] In the specification, the term "NG-RAN” may be interpreted as, or may refer to, a base station, which may comprise at least one of a g NB, a ng-eNB, a relay node, a base station central unit (e.g., gNB- CU), a base station distributed unit (e.g., gNB-DU), and/or the like. This may be a radio access network that connects to 5GC, supporting at least one of NR, E-UTRA, and/or a combination thereof.

[0257] In the specification, the term "E-UTRAN” may be interpreted as, or may refer to, a base station, which may comprise at least one of an eNB, an en-gNB, and/or the like. This may be a radio access network that connects to evolved packet core (EPC), supporting at least one of NR, E-UTRA, and/or a combination thereof.

[0258] In the specification, the term "mobility management node” may be interpreted as, or may refer to, a function and/or a node performing mobility management for a UE. For example, mobility management may be at least one of management of registration status, management of context, management of authorization, management of registration area, management of paging, and/or the like. For example, the mobility management node may comprise at least one of a MME, AMF, and/or the like.

[0259] In the specification, a term "procedure" may be interpreted as, or may refer to, comprising sending by a first node to a second node a first message, receiving by the second node from the first node the first message, sending by the second node to the first node a second message, and/or receiving by the first node from the second node the second message. The first node may be one or more first network nodes, and the second node may be a one or more second network nodes. The procedure may comprise a registration procedure, a deregistration procedure, a service request procedure, a notification procedure, a PDU session establishment procedure, a PDU session modification procedure, a UE configuration update procedure, a cell selection procedure, a cell reselection procedure, a random access procedure, a capability update procedure, and/or the like.

[0260] In the specification, a term "NAS message" may be interpreted as, or may refer to, a message exchanged between a UE and a core network node. The NAS message may be exchanged via a 3GPP access and/or via a N3GPP access. The NAS message may comprise a MM (mobility management) message, a SM (session management) message, and/or the like. The MM message may comprise a registration request message, a registration accept message, a registration reject message, a UE configuration update message, a UL NAS transport message, a DL NAS transport message, a deregistration message, a service request message, a service accept message, a service reject message, a PDU session establishment request message, a PDU session establishment accept message, a PDU session establishment reject message, a PDU session modification request message, a PDU session modification accept message, a PDU session modification reject message, a PDU session modification command message, a PDU session release request message, a PDU session release command message, and/or the like.

[0261] In an example, 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 change of the value). 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 network slice inactivity window timer (e.g., a NS UE monitoring timer, a NS PDU monitoring timer) may be used for measuring a window of time for measuring the network slice inactivity. In an example, instead of starting and expiry of a network slice inactivity 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.

[0262] In an example, indication (e.g., indicate, indicating) may be achieved in various ways. For example, a first indication may be done by including a first field in a first signalling (e.g., a message). Alternatively and/or additional, a second indication may be done by not including the first field in the first signalling. For example, if a first message comprises the first field (e.g., used/ assigned for the first indication, e.g., field A), the first indication (e.g., a timer is used) may be done (e.g., achieved, delivered from a sender to a receiver). For example, if the first field in the first message is set to a value A, a third indication (e.g., timer value is value A) may be done. For example, if the first message does not comprise the first field, the second indication (e.g., timer is not used) may be done. In another example, a fourth indication (e.g., a UE is allowed for action C) may be done by sending a second signalling (e.g., a message whose name comprises ‘C and/or 'accept'). Alternatively and/or additionally, a fifth indication (e.g., a UE is not allowed for action C) may be done by not sending the second signalling (e.g., a message, a field (e.g., allowed bit)). For example, the sender can indicate A, by sending a message A1 comprising an indicator (e.g., an information element) indicating A and/or by sending a message A2. For example, the message A2 may be used only to indicate A and/or the message A2 itself may indicate the A. For example, when a first entity indicates to a second entity about first something, the first entity may send to the second entity, an indicator (e.g., an information element) indicating the first something, and/or may send to the second entity, a message comprising the indicator and/or may send a first dedicated message for the first something. In other example, when a first entity does not indicate to a second entity about second something, the first entity may not send to the second entity, a first indicator (e.g., an information element) indicating the second something, may not send to the second entity, a message comprising the first indicator, and/or may send to the second entity, a second indicator indicating that the second something does not apply, and/or may send a message not comprising the first indicator, and/or may send to the second entity, a second dedicated message for indicating the second something. In another example, not sending any message may be interpreted as an indication. In an example, indicate may mean comprise one or more parameter indicating.

[0263] In an example, ‘based on a message (or one or more messages)' may be interpreted, or may refer to, as, ‘based on one or more information (or one or more parameters) included in the message (or the one or more messages)', ‘using (e.g , acting) on one or more information (or one or more parameters) included in the message (or the one or more messages)', and/or the like.

[0264] In the specification, "protocol entity” may be interpreted, or may refer to, as an entity performing a set of specific functions related to a wireless access (e.g., LTE access, NR access) and/or a wireline access (e.g., Ethernet) and/or communication (e.g., TCP, IP). In an example, an entity (or a layer) may be interpreted as a protocol entity (or a protocol layer). In an example, the protocol entity of LTE and/or NR may be at least one of a SDAP entity, a PDCP entity, a RLC entity, a MAC entity, a RRC entity, a NAS entity, and/or a PHY entity. In an example, a layer (e.g., a SDAP layer, a PDCP layer, a RLC layer, a MAC layer a PHY layer, a RRC layer, a NAS layer) may be interpreted as a protocol entity (e.g., SDAP entity, a PDCP entity, a RLC entity, a MAC entity, a PHY entity, a RRC entity, a NAS entity).

[0265] In the specification, no transmission zone (NTZ) may be no-transmission zone or no-transmission zones. In a first example, the NTZ may be a geographical area where one or more aerial UEs (e.g., drones, UAVs) are not allowed to operate (e.g., transmit a radio signal) in a certain frequency band. ECC Decision (22)07 describes purpose and requirements of NTZ. The ECC Decision 22(07) (e.g., CEPT Decision 22(07) is a decision made by CEPT in November 2022, is about harmonized technical conditions for the usage of aerial UE for communications based on LTE and 5G NR in several bands harmonized for MFCN. The decision assumes multiple technical conditions and requirements to support aerial UEs in mobile systems (both LTE and NR). Two notable ones are no-transmit zone (NTZ) and out-of-band emission (OOBE). In ECC Decision 22(07), the NTZ is defined at national level as a geographical area where aerial UE are not allowed to operate in a certain frequency band. Another measure to achieve coexistence is to define additional OOB emission limits specific to aerial UE (to avoid interference to other services in some other bands (e.g. to protect MetSat at 1675-1710 MHz). The requirement may apply to aerial UE according to their operational frequency band, e.g. aerial UE operating in a specific band or specific channel. In some cases, operation of aerial UE also requires respective cross-border coordination agreements. No-fly zone definition is set out in ECC Report 309. On the other hand, no flying zone (e.g., NFZ, no-fly zone), may be an area whether the UAV is not allowed to fly. An area of the NFZ may be a NTZ and/or may not be an NTZ. In a second example, the NTZ may be a geographical area where one or more UEs (e.g smartphones, machines, terrestrial devices, devices on the ground, devices under certain altitudes, devices which does not have capability to fly, etc.) are not allowed to operate (e.g., transmit a radio signal) in a certain frequency band (ranges). In a third example, the NTZ may be associated with one or more conditions. When the one or more conditions (e.g., geographical areas, certain time slots/ periods) are met, one or more UEs (e.g., smartphones, machines, terrestrial devices, devices on the ground, devices under certain altitudes, devices which does not have capability to fly, etc.) are not allowed to operate (e.g., transmit a radio signal) in a certain frequency band (e.g., frequency range). When the one or more conditions (e.g., geographical areas, certain time slots) are not met, one or more UEs (e.g., smartphones, machines, terrestrial devices, devices on the ground, devices under certain altitudes, devices which does not have capability to fly, etc.) are allowed to operate (e.g., transmit a radio signal) in a certain frequency band (e.g., frequency range).

[0266] In the specification, an aerial UE may be an uncrewed (unmanned) aerial vehicle (UAV), a drone, a communication device attached to the UAV, a communication device integrated into the UAV, and/or the like.

[0267] In the specification ‘restriction’ and/or 'restricted' may be interpreted, may refer to “not allowed to use, transmit, send, operate, and/or the like”. For example, if a frequency A (e.g., 1 .1 GHz) is restricted, it may be interpreted at least one of that transmission (of a signal, data, etc.) using the frequency A is not allowed, that reception (of a second signal, data, etc.) using the frequency A may and/or may not be allowed, that communication via the frequency A is not allowed, sending feedback (e.g., HARQ ACK/NACK, PUCCH, UCI, etc.) via the frequency A is not allowed while being allowed to receive one or more downlink signal, and/or the like. For example, if the frequency A is restricted, the UE may not send any signal, using the frequency A, if a certain condition (e g., transmitter of the UE supports the frequency A, a resource using the frequency A is allocated, the UE is in the NTZ, the UE is an aerial UE type, and/or the like) is met. For example, if the frequency A is not restricted, the UE may send a signal, using the frequency A, if some conditions (e.g., transmitter of the UE supports the frequency A, a resource using the frequency A is allocated, the UE is not in the NTZ, the UE is not an aerial UE type, and/or the like) are met. In some cases, a first cell may be restricted and/or a second cell may not be restricted. In some cases, a first uplink carrier of one or more uplink carriers may be restricted and/or a second uplink carrier of the one or more uplink carriers may not be restricted. In some cases, a first BWP of one or more BWPs may be restricted and/or a second BWP of the one or more BWPs may not be restricted. In some cases, that a portion of cells (or, BWPs, frequencies, uplink carriers, areas) is restricted may be that a resource of the cells are partially restricted and/or that entire resource of the cells are not restricted and/or at least a segment (e.g., a portion of) resource of the cells are allowed. Restriction may be for not allowing to use, for not allowing to access, for preventing access, for preventing use. Restriction may apply partially and/or entirely for an area, a cell, a frequency, a frequency band, an BWP, an RACH resource, and/or the like. Restriction may apply in uplink direction and/or may apply in downlink direction. Restriction may apply in uplink direction and/or may not apply in downlink direction. Restriction may not apply in uplink direction and/or may apply in downlink direction. For example, when a UE is restricted in uplink, the UE may be allowed to receive a downlink signal (e.g., SIBs, MBMS).

[0268] In the specification, ‘one or more frequency', ‘frequency bands’, ‘frequency block’, ‘frequency set’ and/or ‘frequency range” may be interpreted, may refer “a set of frequencies". For example, a first frequency band (e.g., covering from 10 MHz to 11 MHz) may be one or more frequencies (e.g., 10 1 , 10.11 , 10.3 MHz, .... 10MHz) within a first lower edge frequency (e.g., 10 MHz) and a first upper edge frequency (11 MHz). For example, the first frequency band may comprise the one or more frequencies within starting from the first lower edge frequency and up to the first upper edge frequency. The one or more frequencies may be expressed by the first lower edge frequency and/or by the first upper edge frequency. The one or more frequencies may be a frequency band, a frequency range, a block of frequencies, a set of frequencies, and/or the like. In some case, ‘a frequency' may be ‘one or more frequencies'.

[0269] FIG. 19 illustrates an example as per an aspect of an embodiment of the present disclosure. In an example, a UE may receive one or more messages comprising one or more parameters of one or more neighboring cells, for a cell re-selection procedure. Based on the one or more parameters, the UE may determine one or more candidate cells, select a target cell, exclude some cells from the one or more candidate cells, may determine whether to perform measurement, and/or the like. This may help in reducing out-of-service time of the UE. For brevity, based on the other part of the present disclosure, redundant details will be omitted.

[0270] In an example, a UE may receive one or more first messages.

[0271] The UE may receive the one or more first messages from at least one of a mobility management node (e.g., an AMF, a MME, a mobility management node of 6GS), an application server (e.g., a server associated operation of the aerial UE, a USS (UAS (unmanned aircraft system) service supplier), a UTM (UAS traffic management), an application server controlling an aerial UE, and/or the like), a manufacture of the UE (or hard-coded information in the hardware of the UE, ME (mobile equipment)), a home network (e.g., via a node of the home network, a SIM card (e.g, UICC), stored in the SIM card (e.g, USIM)), and/or the like.

[0272] The one or more first messages may comprise at least one of:

[0273] - a first information (e.g., one or more first parameters) indicating (e.g., associated with) the NTZ. For example, this (i.e., the first information) may indicate one or more areas (e.g., locations, cells, tracking areas) of the NTZ. Within (e.g., when located inside of, near, a guard area (e.g., addition area outside and/or adjacent of the NTZ, of) each of the one or more areas, and/or when the UE is configured with the first information, the UE may not be allowed to transmit (e.g., send) an uplink signal (e.g., reference symbols, PUCCH signal, PUSCH signal, MAC CE, MAC PDU) using at least a portion and/or entirely the one or more restricted frequencies (or an uplink resource indicated by the one or more restricted frequencies). Outside (e.g., when located outside of) each of the one or more areas, and/or when not configured with the first information, the UE may be allowed to transmit using the one or more restricted frequencies. The one or more restricted frequencies may be restricted for the NTZ. Within (e.g., when located inside of, near) each of the one or more areas, the UE may be allowed to transmit using other frequencies not indicated by the one or more restricted frequencies. The first information may be a NTZ areas (e.g., location) information.

[0274] - a second information (e.g., one or more second parameters) indicating the one or more restricted frequencies. The one or more restricted frequencies may indicate one or more sets of frequencies (or frequency ranges, frequency blocks). The UE may not be allowed to transmit using the one or more restricted frequencies, while the UE is inside the NTZ. For example, a set of the one or more sets may be expressed by a lower edge frequency (e.g., lower bound frequency, a starting frequency) of the set and/or an upper edge frequency (e.g., upper bound frequency, an ending frequency) of the set. The set may comprise one or more frequencies within the lower edge frequency and the upper edge frequency. For example, a first set of the one or more sets may be (e.g., comprise) frequencies in a range of 1100 MHz to 1200 MHz, where the lower edge frequency is 1100 MHz and the upper edge frequency is 1200 MHz. For example, a second set of the one or more sets may be (e.g., comprise) frequencies in a range of 2100 MHz to 2200 MHz, in which the lower edge frequency is 2100 MHz and the upper edge frequency is 2200 MHz. [0275] The one or more first messages may be at least one of a registration accept message, a UE configuration update message, a policy container, a NAS transport message, a OMA (open mobile alliance) DM (device management) message, a configuration message, a downlink RRC transfer message, a service-level-AA container, a payload container, a UE policy container, NAS transparent container, a SOR transparent container, and/or the like. The one or more first message may be received via a control plane, via a user plane, be locally configured, and/or the like.

[0276] The one or more first messages may be used to configure the UE with information (e.g., one or more parameters) of the NTZ. The one or more first messages may be used to provide the UE with the information. For example, this may help the UE to identify one or more areas of the NTZ, and/or the one or more restricted frequencies associated with the NTZ, before the UE initiates access to a cell and/or the network. A network node may send the one or more first messages to the UE, if the UE is an aerial UE type, and/or if the UE supports handling of the NTZ related information. For example, if the UE sends to the network a capability information indicating that the UE can interpret (e.g., handle, process) the NTZ information (e.g., the UE can interpret the first information and/or the second information), and/or if the UE sends to the network a request for the NTZ information, the network may send the one or more first messages (e.g., the first information and/or the second information) to the UE. For example, if the UE does not send to the network the capability information, and/or if the UE does not send to the network the request, the network may not send the one or more first messages (e.g., the first information and/or the second information) to the UE. This may help in reducing abnormal behavior of a UE, in reducing signalling resource, if the one or more first messages are sent to the UE that may not be able to interpret the first information and/oror the second information.

[0277] In an example, the UE may receive one or more second messages. For example, the UE may receive the one or more second messages from one or more radio access node, one or more base station, via one or more cells and/or the like. For example, the UE may receive the one or more second messages from a first cell of a first base station. For example, the one or more second messages may be at least one of a system information blocks (e.g., SIB, MIB, SIB 1 , SIB 2, SIB 3, SIB 4, and/or the like), a RRC message (e.g , RRC Setup message, RRC Reconfiguration message, RRC Release message, and/or the like).

[0278] The one or more second messages may comprise one or more third information (e.g., one or more third parameters). The one or more third information may be (e.g., comprise) at least one of:

[0279] - IntraFreqNeighCellList: This may indicate one or more neighbor cells of intra-frequency. For each cell, the one or more second messages may further comprise IntraFreqNeighCelllnfo.

[0280] - IntraFreqNeighCelllnfo: This indicates one or more parameter of a cell, one or more parameters of the cell of the intrafrequency, and/or the like. For example, this may comprise at least one of physCellld, q-OffsetCell, q-RXLevMinOffsetCell, q-RXLevMinOffsetCellSUL, q-QualMinOffsetCell, noTransmissionZonelnd, cellBarredAerial, list of UplinkConfigCommonSIB, cellareainfo, and/or the like. [0281] - intra FreqExcluded Cell List : This may indicate list of exclude-listed intra-frequency neighbouring cells.

[0282] - IntraFreqAllowedCell List: This may indicate list of allow-listed intra-frequency neighbouring cells. [0283] - cellBarredAerial (e.g., aerial UEallowed) : This may be an information indicating whether the cell (or a frequency) is barred to an aerial type UE. If cellBarredAerial is set to Barred, and if the UE is the aerial type UE (e.g., aerial UE), the UE may not perform reselection to this cell, and/or may consider the cell as barred. If cellBarredAerial is set to notBarred, and/or if the UE is the aerial type UE (e.g., aerial UE), the UE may reselect this cell, and/or may consider the cell as not barred. This may help the UE to avoid selection of the cell, when certain conditions are met.

[0284] - noTransmissionZonelnd: This may be an information indicating whether the cell (or a frequency) is associated with the NTZ, whether a part of the cell comprises the NTZ, whether the entire cell belongs to the NTZ, and/or the like. If this is set to yes (or true), this may indicate that the cell is associated with the NTZ, that a part of the cell comprises the NTZ, that the entire cell belongs to the NTZ, and/or the like. This may help the UE to avoid selection of the cell, when certain conditions are met.

[0285] - list of UplinkConfigCommonSIB. This may indicate one or more uplink resources of one or more uplink carriers of the cell. This may comprise uplinkConfigCommon and/or supplementaryUplink. Each of the uplinkConfigCommon and/or supplementaryUplink may comprise at least one of FrequencylnfoUL, initialUplinkBWP, and/or the like. The uplinkConfigCommon may indicate a first uplink carrier configuration of the cell and/or may be associated with a NUL carrier. The supplementaryUplink may indicate a second uplink carrier configuration of the cell and/or may be associated with an SUL carrier of the cell, if the SUL carrier is configured in the cell.

[0286] - FrequencylnfoUL (FrequencylnfoUL-SIB): This may be an information of an uplink carrier configuration of the cell. This may comprise absoluteFrequencyPointA, frequencyBandList, and/or the like. This may be associated with an uplink carrier of the cell. Different uplink carrier may use different values for FrequencylnfoUL.

[0287] - absoluteFrequencyPointA: This may indicate absolute frequency of a reference resource block (Common RB 0) of an uplink carrier, of a cell. A lowest subcarrier of the uplink carrier may be a Point A of the uplink carrier. Different uplink carrier may use different values for absoluteFrequencyPointA.

[0288] - frequencyBandList: This may provide information regarding the frequency band indicator (i.e., indicating one or more operating bands of the uplink carrier) and a list of additionalPmax and additionalSpectrumEmission values, for each of the one or more operating bands, of a cell. The UE may apply a first listed band (e.g., a first listed frequency band, a first listed operating band) which the UE supports in the frequencyBandList field, if the NTZ does not apply. The UE may apply a first listed (frequency, operating) band which the UE supports in the frequencyBandList field, except one or more frequency bands for which the NTZ applies, if the NTZ applies (e.g., when the UE is inside the NTZ). For example, this may comprise at least one of frequencyBandList (e.g., N195, N100, indicating list of frequency operating band that the cell belongs to, indicates list of frequency bands for which the NR cell reselection parameters apply). If the UE is configured with the first information and/or the second information, and if the UE is in the NTZ, the UE may apply a first listed band which the UE supports in the frequencyBandList, excluding one or more bands overlapping (e.g., comprising) the one or more frequencies indicated by the second information. This may help the UE to apply adequate additionalPmax and additionalSpectrumEmission values, when the UE is in the NTZ. For example, the frequencyBandList may comprise a first element of frequency band N100 and a second element of frequency band N101. For example, frequency band N100 may span from a frequency 2000 MHz to a frequency 2100 MHz, and frequency band N101 may span from a frequency 2050 MHz to a frequency 2150 MHz. For example, the second information may indicate a frequency range from a frequency 1980 MHz to a frequency 2020 MHz. In this case, when the UE is capable of both N100 and N101 , if the UE is inside the NTZ indicated by the first information, the UE may exclude the frequency band N100, the UE may select N101 , which does not overlap (e.g., comprise) the frequency range indicated by the second information. In this case, when the UE is capable of both N100 and N101 , if the UE is not inside the NTZ indicated by the first information, the UE may select N100, which may be listed first (e.g., earlier than) the N101 .

[0289] - InitialUplinkBWP: This may indicate an initial uplink BWP of an uplink carrier. This may comprise information of BWP-uplinkcommon.

[0290] - BWP-uplinkcommon: This may comprise information of a BWP and/or rach-configcommon of (associated with) the BWP. The BWP may be associated with an uplink carrier. For example, the information of the BWP may comprise locationAnd Bandwidth. The locationAndBandwidth may indicate frequency domain location and bandwidth of the BWP. This may help the UE to determine frequency range (e.g., from which frequency to which frequency) of the (initial) BWP of a UL carrier of the cell.

[0291] - interFreqCarrerFreq List: This is list of neighbouring carrier frequencies (list of one or more interfrequencies) and frequency specific cell re-selection information. This may indicate one or more interfrequencies (inter-frequencies) configured for one or more neighboring cells. For each carrier (e.g., interfrequency), the one or more second messages may comprise InterFreqCarrierFreqlnfo.

[0292] - InterFreqCarrierFreqlnfo: For each interfrequency of the list of one or more interfrequencies, this may indicate at least one of dl-carrierFreq, frequencyBandList, frequencyBandListSUL, cell Reselection Priority, InterFreqNeighCellList, interFreqExcludedCellList, noTransmissionZonelnd, cellBarredAerial, list of UplinkConfigCommonSIB, and/or the like.

[0293] - InterFreqNeighCellList: This may indicate one or more neighbor cells of the inter-frequency. For each cell of the inter-frequency, the one or more second messages may further comprise InterFreqNeighCelllnfo.

[0294] - InterFreqNeighCelllnfo: This indicates one or more parameter of a cell. For example, this may comprise at least one of physCell Id, q-OffsetCell, q-RXLevMinOffsetCell, q-RXLevMinOffsetCellSUL, q- QualMinOffsetCell, noTransmissionZonelnd, cellBarredAerial, list of UplinkConfigCommonSIB, cellareainfo, list of UplinkConfigCommonSIB, noTransmissionZonelnd, cellBarredAerial, and/or the like.

[0295] - cellareainfo. This may indicate an area covered (e.g., operated) by the cell. This may indicate an area that the cell intends to server a UE (e.g., the UE in this area can send data, receive data from this cell). This may be one or more geographical coordinates.

[0296] - a threshold value. For example, if a measured signal quality (e.g., RSRP, RSRQ, RS) of the first cell is above this threshold value, the UE may determine not to measure one or more intrafrequency neighbouring cells and/or one or more interfrequency neighboring cells. [0297] In an example, based on the one or more second messages (e.g., based on one or more third parameters indicated by the second messages), the UE may determine which one or more frequencies (or which one or more frequency bands, which one or more frequency ranges, which one or more portion of the one or more frequencies) are configured for each (interfrequency, intrafrequency) neighboring cell of the first cell (e.g., currently serving the UE) and/or for each interfrequency of the first cell, for uplink. For example, the UE may determine one or more configured (uplink) frequencies of the each neighboring cell of the one or more neighbouring cells indicated by the one or more second messages. For example, based on the one or more second message, for the each neighboring cell, the UE may determine that the each neighboring cell uses one or more configured frequencies ranges for the uplink direction (for uplink resources) and/or the UE may determine that/whether the each neighboring cell does not use the one or more restricted frequencies ranges for the uplink direction (and/or for uplink resources).

[0298] For example, the one or more second messages may indicate information of one or more neighboring cells. The one or more neighboring cells may comprise one or more intra-frequency neighboring cells and/or one or more inter-frequency neighboring cells. For example, the one or more intra- frequency neighboring cells may comprise a first intra-frequency neighboring cell, a second intra-frequency neighboring cell, and/or the like. For example, the first cell and/or the one or more intra-frequency cells may use a same center frequency for a SSB, and/or for a CSI-RS.

[0299] For example, the one or more inter-frequency neighboring cells may comprise a first interfrequency neighboring cell, a second inter-frequency neighboring cell, and/or the like. For example, the first cell and/or the one or more inter-frequency cells may not use a same center frequency, for a SSB, and/or for a CSI-RS, as the current cell (or the intra-frequency cell).

[0300] For example, the one or more second message may indicate, for the first intra-frequency neighboring cell (e.g., cell D1), at least one of:

[0301] - the first intra-frequency neighboring cell comprises entirely and/or partially comprise an area of an NTZ.

[0302] - one or more uplink carriers, one or more configured uplink carriers, one or more uplink frequencies, one or more configured uplink frequencies, of the first intra-frequency neighboring cell. The one or more uplink carrier may comprise at least a portion of the one or more restricted frequencies. This may help the UE to determine whether one or more uplink frequencies of the cell overlaps with a restricted frequency of the one or more restricted frequencies.

[0303] - barring status of the first intra-frequency neighboring cell. For example, the first intra-frequency neighboring cell may be barred/prohibited from cell-reselection for a UE configured with the NTZ (and/or a UE of an aerial UE type). This may help the UE to determine whether the select the cell [0304] - information of a first coverage of the first intra-frequency neighboring cell. For example, the first coverage may comprise at least a portion of an area of the NTZ. This may help the UE to determine whether the first coverage overlaps at least a portion of the NTZ.

[0305] - one or more frequencies configured for the first intra-frequency neighboring cell. The one or more (uplink) frequencies configured for one or more uplink carriers of the first intra-frequency neighboring cell and/or the one or more (uplink) frequencies configured for the first intra-frequency neighboring cell may comprise at least a portion of the one or more restricted frequencies. This may help the UE to determine whether one or more uplink frequencies of the cell overlaps with a restricted frequency of the one or more restricted frequencies.

[0306] For example, the one or more second message may indicate, for the second intra-frequency neighboring cell (e.g., cell E1), at least one of:

[0307] - the second intra-frequency neighboring cell does not comprise a (e.g., any) portion of an area of an NTZ.

[0308] - one or more uplink carriers (and/or one or more uplink frequencies) of the second intra-frequency neighboring cell. The one or more uplink carrier may not comprise a (e.g , any) portion of the one or more restricted frequencies.

[0309] - barring status of the second intra-frequency neighboring cell. For example, the second intra- frequency neighboring cell may not be barred/prohibited from cell-reselection for a UE configured with the NTZ (or a UE of an aerial UE type).

[0310] - information of a second coverage of the second intra-frequency neighboring cell. For example, the second coverage may not comprise a (e.g., any) portion of an area of the NTZ.

[0311] - one or more frequencies configured for the second intra-frequency neighboring cell. The one or more (uplink) frequencies configured for the second intra-frequency neighboring cell and/or the one or more (uplink) frequencies configured for one or more uplink carriers of the second intra-frequency neighboring cell may not comprise a (e.g., any) portion of the one or more restricted frequencies.

[0312] For example, the one or more second message may indicate, for the first inter-frequency neighboring cell (e.g., cell D2), at least one of:

[0313] - the first inter-frequency neighboring cell comprises entirely and/or partially comprise an area of an NTZ.

[0314] - one or more uplink carrier (and/or one or more uplink frequencies) of the first inter-frequency neighboring cell. The one or more uplink carrier may comprise at least a portion of the one or more restricted frequencies. [0315] - barring status of the first inter-frequency neighboring cell. For example, the first inter-frequency neighboring cell may be barred/prohibited from cell-reselection for a UE configured with the NTZ (or a UE of an aerial UE type).

[0316] - information of a first coverage of the first inter-frequency neighboring cell. For example, the first coverage may comprise at least a portion of an area of the NTZ.

[0317] - one or more frequencies configured for the first inter-frequency neighboring cell. The one or more (uplink) frequencies configured for one or more uplink carriers of the first inter-frequency neighboring cell and/or the one or more (uplink) frequencies configured for the first inter-frequency neighboring cell may comprise at least a portion of the one or more restricted frequencies.

[0318] For example, the one or more second message may indicate, for the second inter-frequency neighboring cell (e.g., cell E2), at least one of:

[0319] - the second inter-frequency neighboring cell does not comprise entirely and/or partially comprise an area of an NTZ.

[0320] - one or more uplink carrier (and/or one or more uplink frequencies) of the second inter-frequency neighboring cell. The one or more uplink carrier may not comprise a (e.g , any) a portion of the one or more restricted frequencies.

[0321] - barring status of the second inter-frequency neighboring cell. For example, the second interfrequency neighboring cell may not be barred/prohibited from cell-reselection for a UE configured with the NTZ and/or a UE of an aerial UE type.

[0322] - information of a second coverage of the second inter-frequency neighboring cell. For example, the second coverage may not comprise a (any) portion of an area of the NTZ.

[0323] - one or more frequencies configured for the second inter-frequency neighboring cell. The one or more (uplink) frequencies configured for (one or more uplink carriers of) the second inter-frequency neighboring cell may not comprise a (any) portion of the one or more restricted frequencies.

[0324] For example, the one or more second message may indicate, for each interfrequency (and/or for intrafrequency), a value for cel I Reselection Priority parameter. For example, for a first inter-frequency of the one or more inter-frequencies, the cell ReselectionPriority may indicate a first value (e.g., 0, 1 ). For example, for a second inter-frequency of the one or more inter-frequencies, the cell Reselection Priority may indicate a second value (e.g., 3, 4). For example, the one or more second message may indicate that, for the intra-frequency (e.g., the frequency of the first cell), the cellReselectionPriority may indicate a third value (e.g., 5, 6). In one example, a higher value (e.g., 5) may indicate a high priority than a lower value (e.g., 1 ). In another example, a higher value (e.g., 5) may indicate a lower priority than a lower value (e.g., 1). In another example, a higher value (e.g., 7) may indicate a high priority than a lower value (e.g., 0). In another example, a highest value (e.g., 7) may indicate the highest priority than any other values. In another example, a lowest value (e.g., 0) may indicate the lowest priority than any other values.

[0325] In an example, based on information received by the one or more first messages and/or the one or more second messages, the UE may determine one or more candidate cells for cell-reselection procedure. For example, the UE may trigger the cell-reselection procedure, if a measure signal quality (e.g., RSRP, RSRQ) of the first cell is lower than a threshold value (e.g., 10 dBm, 2 d B), and/or if a radio link failure (or handover failure, or a beam failure) occurs. For example, the UE may trigger the cell-reselection procedure, if the UE enters (or exist) an area (e.g., an area restriction of one or more frequencies are applicable) indicated by the NTZ.

[0326] In response to determining to perform the cell-reselection procedure, the UE may start measurement of one or more neighboring cells using the one or more interfrequencies indicated by the one or more second messages and/or the UE may start measurement of one or more neighbouring cells using the one or more intrafrquencies (e.g., using same center frequency as the first cell). In another example, the UE may start measurement of the one or more neighboring cells before determining to perform the cell- reselection procedure.

[0327] In an example, the UE may determine, for each interfrequency of one or more interfrequencies indicated by the one or more second messages, whether to perform measurement of one or more neighboring cells on the each interfrequency. For example, based on information in the one or more first messages and/or based on the information in the one or more second messages, the UE may determine whether to perform measurement of one or more neighboring cells on the each interfrequency. Based on information in the one or more first messages and/or based on the information in the one or more second messages, the UE may determine a priority (e.g., a priority value) for the each interfrequency. For example, if the UE determines that the UE is in (or near, enter) an area indicated by the first information, and/or if the UE determines that the each interfrequency comprises at least a portion of the one or more restricted frequency, the UE may consider that the each interfrequency is the lowest priority (e.g., lower than any other frequencies, and/or lower than any other interfrequency which is not indicated by the second information) and/or that a priority value of the each interfrequency may be a certain value (e.g., the lowest number, 0, 99, etc.) and/or that other interfrequencies than the each interfrequency is prioritized, and/or that the each interfrequency is not prioritized. For example, if the UE determines that the UE is out (or near, exit) the area indicated by the first information, and/or if the UE determines that the each interfrequency does not comprise a (any) portion of the one or more restricted frequencies, the UE may consider that the each interfrequency is not the lowest priority, that the each interfrequency is highest priority and/or that a priority value of the each interfrequency may be the value of the cel I Reselection Priority for the each interfrequency (indicated by the one or more second messages). [0328] In an example, the UE may determine, for current frequency (the frequency of the first cell, the intrafrequency), whether to perform measurement of one or more neighboring cells on the current frequency. For example, based on information in the one or more first messages and/or based on the information in the one or more second messages, the UE may determine whether to perform measurement of one or more neighboring cells on the current frequency. Based on information in the one or more first messages and/or based on the information in the one or more second messages, the UE may determine a priority for the current frequency. For example, if the UE determines that the UE is in (or near, enter) an area indicated by the first information, and/or if the UE determines that the current frequency comprises at least a portion of the one or more restricted frequency, the UE may consider that the current frequency is the lowest priority (e.g., lower than any other frequencies, and/or lower than any other interfrequency which may be (and/or may not be) indicated by the second information) and/or that a priority value of the current frequency may be a certain value (e.g., the lowest number, when cell Reselection Priority is set to 0, value 0, etc.) and/or that other interfrequencies than the current frequency is prioritized, and/or that the current frequency is not prioritized. For example, if the UE determines that the UE is out (or near, exit) the area indicated by the first information, and/or if the UE determines that the current frequency does not comprise a (any) portion of the one or more restricted frequencies, the UE may consider that the current frequency is not the lowest priority, that the current frequency is highest priority (e.g., a value 7, when cell Reselection Priority is set to 7) and/or that a priority value of the current frequency may be the value of the cel I Reselection Priority for the current frequency (indicated by the one or more second messages). [0329] In an example, based on determining one or more priorities of the one or more frequencies (e.g., inter-frequencies, intra-frequencies), the UE may perform measurement of one or more neighboring cells. [0330] For example, the UE may determine whether the first cell (e.g., current serving cell) fulfills one or more first conditions. For example, the one or more first conditions may be that Srxlev is larger (>) than SlntraSearchP, that Squal is larger (>) than SlntraSearchO, and/or the like

[0331] For example, if the one or more first conditions are met, the UE may determine not to perform intrafrequency measurements (e.g., measurement of one or more cells of intra-frequency). For example, if the one or more first conditions are met and/or if the UE is not inside the NTZ (e.g., the area indicated by the first information), the UE may determine not to perform intra-frequency measurements (e.g., measurement of one or more cells of intra-frequency). For example, if the one or more first conditions are met and/or if the UE is inside the NTZ (e.g., the area indicated by the first information), the UE may determine to perform intra-frequency measurements (e.g., measurement of one or more cells of intra-frequency). For example, if the one or more first conditions are not met and/or if the UE is inside the NTZ (e.g., the area indicated by the first information), the UE may determine to perform intra-frequency measurements (e.g., measurement of one or more cells of intra-frequency). The intra-frequency measurements may be measuring one or more neighboring cells using the intra-frequency.

[0332] For example, based on the determined one or more priorities of the one or more interfrequencies, and/or based on information of the one or more first messages, and/or based on the information of the one or more second messages, the UE may determine whether to perform measurement of the one or more neighboring cells of the one or more interfrequencies.

[0333] For example, if a first interfrequency of the one or more interfrequencies have a higher priority than the current frequency (e.g., intrafrequency, the frequency of the current cell, the frequency of the first cell), the UE may determine to perform inter-frequency measurements, may determine to perform measurement of one or more first interfrequency neighboring cells using the first interfrequency.

[0334] For example, if a first interfrequency of the one or more interfrequencies have a higher priority than the current frequency (e.g., intrafrequency, the frequency of the current cell, the frequency of the first cell) and/or if the UE is near (inside, enters) an area of the NTZ, and/or if the first interfrequency (and/or a cell of the first interfrequency) is configured with at least one of the one or more restricted frequencies, the UE may determine not to perform inter-frequency measurements, may determine not to perform measurement of one or more first interfrequency neighboring cells using the first interfrequency, and/or may determine to consider the first interfrequency as of lowest priority.

[0335] In another example, if a first interfrequency of the one or more interfrequencies have a higher priority than the current frequency (e.g., intrafrequency, the frequency of the current cell, the frequency of the first cell) and/or if the UE is not near (inside, enters) an area of the NTZ, and/or if the first interfrequency, one or more cells of the first interfrequency and/or a cell of the first interfrequency is configured with at least one of the one or more restricted frequencies, the UE may determine to perform inter-frequency measurements, may determine to perform measurement of one or more first interfrequency neighboring cells using the first interfrequency, and/or may determine to consider the first interfrequency as of higher priority.

[0336] For example, if a second interfrequency of the one or more interfrequencies have a lower priority than the current frequency (e.g., intrafrequency, the frequency of the current cell, the frequency of the first cell), the UE may determine not to perform inter-frequency measurements, may determine not to perform measurement of one or more second interfrequency neighboring cells using the second interfrequency. For example, if the one or more first condition is not met, if (the one or more cells of) the second interfrequency is configured with at least one of the one or more restricted frequencies, and/or if the UE is inside an area of the NTZ, the UE may determine not to perform inter-frequency measurements of the one or more second interfrequency, may determine not to perform measurement of one or more second interfrequency neighboring cells using the second interfrequency. For example, if the one or more first condition is not met, if the second interfrequency (e.g., the one or more cells of the second interfrequency) is configured with at least one of the one or more restricted frequencies, and/or if the UE is outside an area of the NTZ, the UE may determine to perform inter-frequency measurements of the one or more second interfrequency, may determine to perform measurement of one or more second interfrequency neighboring cells using the second interfrequency.

[0337] For example, if a third interfrequency of the one or more interfrequencies have a lowest priority, the UE may determine not to perform inter-frequency measurements, may determine not to perform measurement of one or more third interfrequency neighboring cells using the third interfrequency. For example, if the one or more first condition is not met, if (one or more cells of) the third interfrequency is configured with at least one frequency of the one or more restricted frequency, and/or if the UE is inside an area of the NTZ, the UE may determine not to perform inter-frequency measurements, may determine not to perform measurement of one or more third interfrequency neighboring cells using the third interfrequency.

[0338] For example, if the one or more first condition is not met, the UE may determine to perform interfrequency measurements, may determine to perform measurement of one or more third interfrequency neighboring cells using the third interfrequency, the UE may determine to perform inter-frequency measurements, may determine to perform measurement of one or more second interfrequency neighboring cells using the second interfrequency.

[0339] For example, if the one or more first condition is not met, the UE may determine to perform interfrequency measurements, may determine one or more priorities of the one or more inter-frequencies. Based on the determined one or more priorities, the UE may perform measurement of one or more neighboring cells of the one or more inter-frequencies, in the order of priority. For example, the UE may perform measurement of one or more neighboring cells of interfrequency X (with higher priority), before performing measurement of one or more neighboring cells of interfrequency Y (with lower priority than the interfrequency X).

[0340] In an example, the UE may perform measurement of the one or more neighboring cells. The UE may rank the one or more neighboring cells. The UE may select a highest ranked cell (e.g., a cell with strongest signal (e.g., RSRP, RSRQ) quality, power) among the one or more (measured) neighboring cells. The UE may perform cell-reselection to the highest ranked cell. In an example, during ranking, the UE may exclude one or more measured neighboring cells which may be configured with at least one frequency of the one or more restricted frequencies.

[0341] In an example, the UE may check whether access to the highest ranked cell is restricted, based on the first information and/or the second information. For example, if the highest ranked cell is inside the NTZ, if the UE is inside the NTZ, and/or if the highest ranked cell is configured with at least one of the one or more restricted frequency, the UE may determine that the highest ranked cell is restricted, and/or may not perform cell-reselection to the highest ranked cell. If the highest ranked cell is restricted due to the NTZ, the UE may determine next highest ranked cell which is not restricted due to the NTZ, may select the next highest ranked cell and/or may perform cell reselection to the next highest ranked cell.

[0342] In an example, when the UE perform ranking of one or more neighboring cell (for which the UE performs the measurement), the UE may exclude a cell from the ranking, if the cell is restricted due to the NTZ (e.g., either inside the NTZ, and/or being configured with at least one of the one or more restricted frequencies). For example, the UE may not select a cell which is excluded due to the NTZ, the UE may exclude the cell from one or more candidate cells, and/or the UE may select a sell which is not excluded due to the NTZ, among the one or more candidate cells.

[0343] In an example, after selecting a cell from the one or more neighboring cell (e.g., one or more candidate neighboring cell), and/or based on determining to perform cell reselection, the UE may send a registration request message, and/or a RRC resume request message via the cell.

[0344] Additionally and/or alternatively, when a UE determines whether a cell is restricted or not, during cell reselection procedure, the UE may check one or more uplink carriers (or BWPs) of the cell. For example, if at least one uplink carrier (e.g., either SUL or NUL) (or BWPs) of the cell is not restricted (e.g., does not comprise a (any) the one or more restricted frequencies, e.g., some portion of the at least one uplink carrier (or BWPs) does not overlap with the one or more restricted frequencies), the UE may determine that the cell is not restricted due to the NTZ. If the cell is not restricted, the cell may be considered during the ranking, for measurement, for candidate, may not be excluded, may be considered as a candidate for cell reselection.

[0345] Additionally and/or alternatively, when a UE determines whether a frequency (e.g., interfrequency) is restricted or not, during cell reselection procedure, the UE may check one or more uplink carriers (or BWPs) configured for the frequency. For example, if at least one uplink carrier (e.g., either SUL or NUL) (or BWPs) of the frequency is not restricted (e.g., does not comprise a (any) the one or more restricted frequencies, e.g., some portion of the at least one uplink carrier does not overlap with at least one of the one or more restricted frequencies), the UE may determine that the frequency is not restricted due to the NTZ. If the frequency is not restricted, the frequency may be considered with priority indicated by the cell Reselection Priority of the frequency during the cell reselection procedure described above.

[0346] Example embodiments of FIG. 19 may help in reducing an amount of time during which a UE cannot communicate with a network if the UE is configured with information associated with a NTZ, may help in reselecting a target cell.

[0347] FIG. 20 illustrates an example as per an aspect of an embodiment of the present disclosure. In an example, a UE may determine whether the UE is inside and/or outside of an area indicated by information of a NTZ, and/or the UE may adjust (update) one or more priorities of one or more frequencies (e.g., interfrequency and/or intrafrequency). Based on the one or more priorities of the one or more frequencies, the UE determines one or more candidate cells. This may help in reducing out-of-service time of the UE. For brevity, based on the other part of the present disclosure, redundant details will be omitted.

[0348] In an example, the UE may receive the one or more second messages. For example, the UE may receive the one or more second messages from the one or more radio access nodes, the one or more base stations, via the one or more cells and/or the like. For example, the UE may receive the one or more second messages from the first cell of the first base station. For example, the one or more second messages may be at least one of the system information blocks (SIB, MIB, SIB 1 , SIB 2, SIB 3, SIB 4, and/or the like), the RRC message (e.g., RRC Setup message, RRC Resume message, RRC Reconfiguration message, RRC Release message, and/or the like).

[0349] The one or more second messages may indicate the one or more third information. For example, the one or more third information may indicate one or more frequencies (e.g., one or more candidate frequencies, one or more neighboring frequencies, one or more current frequencies) for cell-reselection procedure, and/or one or more reselection priorities (e.g., cellReselectionPriority) for the one or more frequencies. The one or more frequencies may comprise one or more candidate interfrequencies and/or an intrafrequency and/or a current frequency (e.g., of the first cell). For example, the one or more frequencies may comprise a first candidate frequency (e.g., F1 , a first candidate center frequency), a second candidate frequency (e.g , F2, a second candidate center frequency), and/or the like. For example, a first priority value (e.g., value 2) may be set as a first priority (e.g., cellReselectionPriority) of the first candidate frequency, a second priority value (e.g., value 4) may be set as a second priority of the second candidate frequency (e.g., second candidate interfrequency frequency, second candidate intrafrequency frequency). [0350] In an example, the UE may determine whether the UE is inside or approaches (enters) an area of the NTZ and/or whether the UE is outside or exits the area of the NTZ. For example, the UE may compare the UE's current location with the area of the NTZ (e.g., indicated by the first information).

[0351] For example, based on determining that the UE is not inside or does not approach the area of the NTZ and/or that the UE is outside or exits the area of the NTZ, the UE may determine to use the first priority value as the first priority of the first candidate frequency and/or the UE may determine to use the second priority value as the second priority of the second candidate frequency. For example, based on that the second priority value is higher than the first priority value, and/or based on the second candidate frequency is prioritized than the first candidate frequency, the UE may determine that the second candidate frequency is prioritized, and the UE may measure one or more second candidate cells of the second candidate frequency and/or the UE may not measure one or more first candidate cells of the first candidate frequency. Or, the UE may start measurement of the first candidate frequency after measuring the second candidate frequency. Based on the measurement, the UE may select a cell among the one or more second candidate cells.

[0352] For example, based on determining that the UE is inside or approaches the area of the NTZ and/or that the UE is not outside or does not exit the area of the NTZ, the UE may determine, for each candidate frequency of the one or more candidate frequencies, whether the each candidate frequency comprises partially and/or entirely one or more restricted frequencies, based on e.g ., one or more restricted frequencies indicated by the NTZ information, the first information, and/or the second information. For example, if (one or more configured uplink frequencies of) the each candidate frequency comprises partially and/or entirely the one or more restricted frequencies, the UE may determine that the priority (and/or a priority value) of the each candidate frequency is the lowest, and/or lower than any other candidate frequency. For example, if (one or more configured uplink frequencies of) the each candidate frequency (e.g., one or more configured uplink frequencies of the each candidate frequency) does not comprise a/any of the one or more restricted frequencies, the UE may determine that the priority (and/or a priority value) of the each candidate frequency is (a value) indicated by a cellReselectionPriority of the each candidate frequency. For example, (one or more configured uplink frequencies of) the second candidate frequency may comprise at least a portion of the one or more restricted frequencies and/or (one or more configured uplink frequencies of) the first candidate frequency may not comprise a (e.g., any) portion of the one or more restricted frequencies. For example, the UE may determine that a priority value of the second candidate frequency is the lowest (e.g , the value 0) and/or that the second candidate frequency is lowest priority. For example, the UE may determine that a priority value of the first candidate frequency is the first priority value (e.g., indicated by the cellReselectionPriority) of the first candidate frequency. For example, based on the first candidate frequency is prioritized than the second candidate frequency, the UE may determine that the first candidate frequency is prioritized, and the UE may measure one or more first candidate cells of the first candidate frequency and/or the UE may not measure one or more second candidate cells of the second candidate frequency. Based on the measurement, the UE may select a cell among the one or more first candidate cells.

[0353] Example embodiments of FIG. 20 may help in reducing an amount of time during which a UE cannot communicate with a network if the UE is configured with information associated with a NTZ, may help in reselecting a target cell.

[0354] FIG. 21 illustrates an example as per an aspect of an embodiment of the present disclosure. In an example, a UE may determine whether the UE is inside and/or outside of an area indicated by information of a NTZ, and/or the UE may determine whether to send measurement report or not, to a base station. This may help in saving UE battery. For brevity, based on the other part of the present disclosure, redundant details will be omitted. [0355] In an example, the UE may receive the one or more second messages (for example, as shown in FIG 22, 23). For example, the UE may receive the one or more second messages from the one or more radio access nodes, the one or more base stations, via the one or more cells and/or the like. For example, the UE may receive the one or more second messages from the first cell of the first base station. For example, the one or more second messages may be at least one of the system information blocks (SIB, MIB, SIB 1 , SIB 2, SIB 3, SIB 4, and/or the like), the RRC message (e.g., RRC Setup message, RRC Reconfiguration message, RRC Release message, and/or the like).

[0356] The one or more second messages may indicate the one or more third information. For example, the one or more third information may indicate one or more frequencies for cell-reselection procedure, and/or one or more reselection priorities (e.g , cellReselection Priority) for the one or more frequencies. The one or more frequencies may comprise one or more candidate interfrequencies and/or an intrafrequency and/or a current frequency (e.g., of the first cell). For example, the one or more frequencies may comprise a first candidate frequency (e.g., F1 , a first candidate center frequency), a second candidate frequency (e.g., F2, a second candidate center frequency), and/or the like. For example, a first priority value (e.g., value 2) may be set as a first priority of the first candidate frequency, a second priority value (e.g., value 4) may be set as a second priority of the second candidate frequency.

[0357] In an example, the UE may determine whether the UE is inside or approaches (e.g., enters) an area of the NTZ and/or whether the UE is outside or exits the area of the NTZ. For example, the UE may use the first information and/or the second information and/or the third information, to determine whether the UE is inside/outside of one or more areas of the NTZ.

[0358] For example, based on determining that the UE is inside or approaches (e.g., enters) the area of the NTZ and/or that the UE is not outside or does not exit the area of the NTZ, the UE may determine, for each candidate frequency of the one or more candidate frequencies, whether the each candidate frequency (e.g , one or more configured uplink frequencies of the each candidate frequency) comprises partially and/or entirely one or more restricted frequencies (e.g., one or more restricted frequencies indicated by the NTZ information, the first information, and/or the second information). For example, if (one or more configured uplink frequencies of) the each candidate frequency (e.g., one or more configured uplink frequencies of the each candidate frequency) comprises partially and/or entirely the one or more restricted frequencies, the UE may determine to suspend (e.g., stop, hold, not perform) measurement of the each candidate frequency and/or one or more neighboring cells of the each candidate frequency and/or one or more candidate cells on the each frequency, the UE may determine not to send a measurement report to a base station, the UE may determine to suspend (e.g., delay) sending the measurement report to the base station, and/or may deprioritize the each candidate frequency, and/or may determine to send a measurement report which excludes (e.g., does not comprises) result of the one or more cells of the each candidate frequency.

[0359] For example, based on determining that the UE is not inside or does not approach (e.g., enters) the area of the NTZ and/or that the UE is outside or exits the area of the NTZ, the UE may determine, for each candidate frequency of the one or more candidate frequencies, to resume (e.g., continue, re-activate, perform) measurement of the each candidate frequency and/or one or more candidate cells on the each frequency, the UE may determine to send a measurement report to a base station, the UE may determine to send the measurement report to the base station, and/or may determine to send a measurement report which comprises result of the one or more cells of the each candidate frequency.

[0360] Example embodiments of FIG. 21 may help in reducing an amount of time during which a UE cannot communicate with a network if the UE is configured with information associated with a NTZ, may help in reselecting a target cell.

[0361] FIG. 24 illustrates an example as per an aspect of an embodiment of the present disclosure. In an example of FIG. 19, 20, the base station sends information of the one or more neighboring cells (and/or one or more interfrequencies) to the UE. If a subset of the one or more neighboring cells are updated (and/or added/removed), the information sent to the UE may not accurate, the UE may perform cell reselection to an invalid cell. In an example, one or more base stations exchanges information of the one or more neighbouring cells, to assist a base station to construct the one or more second messages. This may help in saving UE battery For brevity, based on the other part of the present disclosure, redundant details will be omitted.

[0362] In an example, a fourth base station (e.g., a BS-DU-2) may send to a third base station (e.g., a BS- CU-2) a first message. The first message may be at least one of a first F1 message. The first F1 message may be a message between a central control entity (e.g., central base station) and a distributed control entity (e g., a distributed base station). For example, the first F1 message may be a F1 setup message, a F1 configuration update message, and/or the like. The first F1 message may comprise information of one or more fourth cells served by the fourth base station. For example, for each cell of the one or more fourth cells, the first F1 message may indicate at least one of:

[0363] - a PCI of the each cell

[0364] - information of one or more uplink/downlink carriers (e.g., NUL, SUL) of the each cell. For example, this may indicate one or more frequencies (e.g., a range of frequency, a block of frequencies, a lower edge (lowest frequency) of the one or more frequencies, a upper edge (e.g., highest frequency) of the one or more frequencies, and/or the like) of the one or more uplink carriers.

[0365] - information of one or more uplink/downlink BWPs of the each cell. For example, this may indicate one or more frequencies (e.g., a range of frequency, a block of frequencies, a lower edge (lowest frequency) of the one or more frequencies, a upper edge (e.g., highest frequency) of the one or more frequencies, and/or the like) of the one or more (uplink) BWPs.

[0366] - an indication of whether the each cell comprises partially and/or entirely a location of the NTZ. [0367] - an indication of whether the each cell is a NTZ or not.

[0368] - an information of one or more restricted frequencies due to a NTZ.

[0369] - an information on an area served by each cell.

[0370] - an information of range of frequencies for each interfrequencies configured by the each cell. [0371] - an information on one or more downlink carriers and/or one or more downlink frequencies configured by the each cell,

[0372] In an example, the fourth base station (e g., a BS-DU-2) may receive from the third base station (e.g., a BS-CU-2) one or more second messages. The one or more second messages may be at least one of a second F1 message. For example, the one or more second messages may be a F1 setup response (acknowledgement, accept, reject) message, a F1 configuration update response (acknowledgement, accept, reject) message, a request message requesting a setup of a UE context for the UE, and/or the like. The one or more second messages may indicate at least one of:

[0373] - acknowledgement of the F1 setup

[0374] - an information of one or more restricted frequencies due to a NTZ. For example, this may indicate one or more restricted frequencies for which the UE is not allowed to use, e.g., when the UE is inside the NTZ.

[0375] - the first information.

[0376] - the second information.

[0377] - whether NTZ enforcement is applicable to the UE. E.g., indicating whether the fourth base station should apply the restriction of the one or more restricted frequencies to the UE.

[0378] The information delivered by the second F1 message may help the fourth base station to construct (determine) a radio resource configuration of the UE, avoiding use of the one or more restricted frequencies, may construct a RRC configuration message, and/or may transmit the RRC configuration message to the UE.

[0379] In an example, the third base station (e.g., a BS-CU-2) may send to a second base station (e.g., a BS-CU-1 ) one or more third messages. The one or more third messages may be at least one of a first Xn message. The first Xn message may be a message between a central control entity (e.g., central base station, a master node, MN) and another central entity (e.g., a central base station, a secondary node, SN). For example, the one or more third messages may be a Xn (or X1) setup message, a Xn configuration update message The one or more third messages may comprise information of the one or more fourth cells served by the fourth base station (e.g., one or more information indicated by the first F1 message). The one or more third messages may assist the second base station to determine one or more resources of the third (or fourth) base station, and to request for the UE.

[0380] In an example, the third base station (e.g., a BS-CU-2) may receive from the second base station (e.g . , a BS-CU-1) one or more fourth messages. The one or more fourth messages may be at least one of one or more second Xn messages. For example, the one or more second Xn messages may be one or more Xn (or X1) setup response (acknowledgement, accept, reject) messages, one or more Xn configuration update response messages, a SN addition request message, a SN configuration request message, and/or the like. The one or more fourth messages may comprise information of one or more first cells served by a first base station (e.g., BS-DU-1 ). For example, the one or more fourth messages may further comprise:

[0381] - acknowledgement of the Xn setup

[0382] - an information of one or more restricted frequencies due to a NTZ. For example, this may indicate one or more restricted frequencies for which the UE is not allowed to use, e.g., when the UE is inside the NTZ. For example, this may indicate one or more restricted frequencies for each cell served by the second base station.

[0383] - the first information.

[0384] - the second information.

[0385] - whether NTZ enforcement is applicable to the UE. E.g., indicating whether the fourth (or the third) base station should apply the restriction of the one or more restricted frequencies to the UE.

[0386] In an example, based on the information received by the one or more fourth messages, the fourth base station and/or the third base station may transmit the one or more second messages comprising information of neighbouring cells (e.g., served by the first base station and/or the second base station) and/or information of one or more interfrequencies of the one or more neighboring cells.

[0387] In an example, based on the information received by the one or more third messages, the first base station and/or the second base station may transmit the one or more second messages comprising information of neighbouring cells (e.g., served by the fourth base station and/or the third base station) and/or information of one or more interfrequencies of the one or more neighboring cells.

[0388] In an example, the second (third) base station may send one or more N1 messages to a first core network. For example, the first core network node may be a node managing a mobility of the UE. For example, the one or more N1 messages may be a message between a base station and/or a core network node. For example, the one or more N1 messages may be a N1 interface setup message, initial UE context setup request message, and/or the like. For example, the one or more N1 messages may comprise information indicating one or more cells served by the first base station and/or the second base station For example, the one or more N1 messages may indicate: [0389] - a PCI of the each cell of the one or more cells served by the first base station and/or the second base station.

[0390] - information of one or more uplink carriers (e.g., NUL, SUL) of the each cell. For example, this may indicate one or more (configured) frequencies (e.g., a range of frequency, a block of frequencies, a lower edge (lowest frequency) of the one or more frequencies, a upper edge (highest frequency) of the one or more frequencies, and/or the like) of the one or more uplink carriers of the each cell. For example, the each cell may be a cell from which the UE is connected to the second base station.

[0391] - information of one or more BWPs of the each cell. For example, this may indicate one or more frequencies (e.g., a range of frequency, a block of frequencies, a lower edge (lowest frequency) of the one or more frequencies, a upper edge (highest frequency) of the one or more frequencies, and/or the like) of the one or more BWPs of the each cell.

[0392] - an indication of whether the each cell comprises partially and/or entirely a location of the NTZ.

[0393] - an indication of whether the each cell is a NTZ or not.

[0394] - an information of one or more restricted frequencies due to a NTZ.

[0395] The one or more N1 message may help the core network node to determine whether enforcement of the NTZ is supported by the second base station, and/or to determine which cell is impacted by the NTZ. [0396] In an example, the second base station may receive one or more second N1 messages from the core network node. For example, the one or more second N1 messages may indicate at least one of: [0397] - acknowledgement of the N1 setup

[0398] - an information of one or more restricted frequencies due to a NTZ. For example, this may indicate one or more restricted frequencies for which the UE is not allowed to use, e.g., when the UE is inside the NTZ.

[0399] - the first information.

[0400] - the second information.

[0401] - whether NTZ enforcement is applicable to the UE. E.g.

[0402] - a request to setup a context of the UE.

[0403] The one or more second N1 message may help the second base station to determine whether to apply enforcement of the NTZ to the UE or not.

[0404] Example embodiments of FIG. 24 may help a base station to acquire one or more information of neighboring cell and to determine one or more information to deliver to the UE.

[0405] FIG. 25 illustrates an example as per an aspect of an embodiment of the present disclosure. As shown in the example of FIG. 19, 20, the UE may camp on a cell which does not comprise a (any) of the one or more restricted frequencies. On the other hand, in this case, if a network does not know exact location of the UE, the network may send one or more paging messages in a cell which the UE does not consider as a candidate for cell reselection, due to the NTZ. This may cause waste of paging resources. In an embodiment, a network node may deliver information of the one or more restricted frequencies with paging request, to a base station. This may help in saving UE battery. For brevity, based on the other part of the present disclosure, redundant details will be omitted.

[0406] In an example, a core network node (e.g ., a mobility management functions, an AMF) may send a paging request message (e.g., N2 paging request) to a base station. For example, the AMF may trigger a paging procedure, when the AMF receives a data notification. For example, the paging request message may comprise at least one of: an identifier associated with the UE; information of an NTZ; the first information; the second information; a first parameter indicating whether the UE is an aerial UE type; a second parameter indicating one or more frequencies restricted for the UE; and/or the like.

[0407] In an example, the base station may receive the paging request message. Based on the paging request message, the base station determine one or more cells (TAs) in which one or more paging messages are transmitted. For example, the base station may serve one or more first cells and/or one or more second cells. The one or more first cells may be configured with one or more configured frequencies. A portion of the one or more configured frequencies may comprise at least one frequency of the one or more restricted frequencies. Because the one or more first cells operates the at least one frequency, the base station may determine not to transmit the one or more paging messages via the one or more first cells. The one or more second cells may be configured with one or more second configured frequencies. The one or more second configured frequencies may not comprise a (any) frequency of the one or more restricted frequencies. Because the one or more second cells do not operate any restricted frequencies, the base station may determine to transmit the one or more paging messages via the one or more second cells. As shown in the example of FIG. 19, 20, the UE may not camp on the one or more first cells, and/or this may help the base station to waste a paging resource via the one or more first cells.

[0408] In an example, the base station may send a second paging request message to a second base station (e.g., a second BS-CU, a second BS-DU). The second base station may manage one or more areas of RAN notification area (RNA) of the UE. The second paging request message may comprise at least one of: the identifier associated with the UE; the information of the NTZ; the first information; the second information; the first parameter indicating whether the UE is the aerial UE type; the second parameter indicating the one or more frequencies restricted for the UE; and/or the like. Similar to behavior of the base station, the second base station may send the one or more paging message via a cell which does not comprise a (any) frequency of the one or more restricted frequencies.

[0409] Alternatively and/or additionally, the UE may receive a paging message via a cell (as shown in FIG. 26). For example, the UE may camp on the cell, if the UE fails to detect one or more cell not comprising the one or more restricted frequencies. If the UE receives the paging message, the UE may determine whether the UE is inside the NTZ or not. If the UE determines that the UE is inside the NTZ and/or (a portion of) one or more configured frequencies of the cell is restricted, e.g., based on the first information and/or the second information, the UE may not respond to the paging message. If the UE receives the paging message, the UE may determine whether the UE is inside the NTZ or not. If the UE determines that the UE is outside the NTZ and/or one or more configured frequencies of the cell is not restricted, e.g., based on the first information and/or the second information, the UE may respond to the paging message and/or the UE may send a RRC connection Setup request.

[0410] Example embodiments of FIG. 25, FIG.26 may help a base station to prevent unnecessary transmission of a paging message in a cell restricted due to the NTZ.

[0411] FIG. 27 illustrates an example as per an aspect of an embodiment of the present disclosure. As shown in examples of FIG. 19, 20, the UE may perform cell selection based on the one or more first messages and/or the one or more second messages. If the UE has different/old contents (e.g., configuration information, policy information) for the first information and/or the second information, the UE may cause interference to other devices (e.g., transmission in a forbidden area). In an embodiment, the UE may determine which one or more parameters to use and/or may update the one or more parameters associated with the NTZ. This may help in avoiding unnecessary transmission. For brevity, based on the other part of the present disclosure, redundant details will be omitted.

[0412] In an example, the UE may receive one or more configuration messages from one or more nodes. For example, the one or more configuration messages may be the one or more first messages. For example, the one or more nodes may be at least one of a mobility management node (e.g., an AMF, a MME, a mobility management node of 6GS), an application server (e.g., a server associated operation of the aerial UE, a USS (UAS (unmanned aircraft system) service supplier), a UTM (UAS traffic management), an application server controlling an aerial UE, and/or the like), OMA DM server, and/or the like. In another example, information (e.g., the first information and/or the second information) delivered by the one or more configuration messages may be hard-coded (e.g., stored in memory of, into ME of the UE) into the UE (e.g., into memory, disk) by a manufacturer of the UE and/or by a server run by the manufacturer. In another example, the information delivered by the one or more configuration messages may be sent to the UE by a home network (e.g , via a node of the home network) In another example, the information may be stored (pre-configured, provided) in a SIM card (USIM, UICC), and/or the UE may read the information from the SIM card, and/or the like. For example, a UE may comprise the ME and/or the UICC.

[0413] Each configuration message of the one or more configuration messages may comprise at least one of: [0414] - the first information indicating (associated, of) the NTZ. For example, this (the first information) may indicate one or more areas (locations, cells, tracking areas) of the NTZ. Within (when located inside of, near, a guard area of) each of the one or more areas, the UE may not be allowed to transmit (send) an uplink signal (e.g., reference symbols, PUCCH, MAC CE, MAC PDU) using the one or more restricted frequencies (or an uplink resource indicated by (comprising at least a portion of) the one or more restricted frequencies). Outside (when located outside of) each of the one or more areas, and/or when not configured with the first information, the UE may be allowed to transmit using the one or more restricted frequencies. The one or more restricted frequencies may be restricted for the NTZ. Within (when located inside of, near) each of the one or more areas, the UE may be allowed to transmit using other frequencies not indicated by the one or more restricted frequencies. This may be a NTZ area (location) information,

[0415] - the second information indicating the one or more restricted frequencies. The one or more restricted frequencies may indicate one or more sets of frequencies (or frequency ranges, frequency blocks). For example, a set of the one or more sets may be expressed by a lower edge frequency (e.g., lower bound frequency, a starting frequency) of the set and/or an upper edge frequency (e.g., upper bound frequency, an ending frequency) of the set The set may comprise frequencies within the lower edge frequency and the upper edge frequency. For example, a first set of the one or more sets may be (comprise) frequencies in a range of 1100 MHz to 1200 MHz, in which the lower edge frequency is 1100 MHz and the upper edge frequency is 1200 MHz. For example, a second set of the one or more sets may be (comprise) frequencies in a range of 2100 MHz to 2200 MHz, in which the lower edge frequency is 2100 MHz and the upper edge frequency is 2200 MHz.

[0416] The one or more configuration messages may be at least one of a registration accept message, a UE configuration update message, a policy container, an OMA (open mobile alliance) DM (device management) message, a configuration message, a downlink RRC transfer message, a service-level-AA container, a payload container, a UE policy container, NAS transparent container, a SOR transparent container, and/or the like. The one or more configuration messages may be received via a control plane (e.g., via one or more core network nodes), via a user plane (e.g., not via the one or more core network nodes, via a PDN connection, via a PDU session, and/or the like), be locally configured, and/or the like. [0417] For example, the one or more configuration messages may comprise:

[0418] - a first configuration message. A first core network node (e.g., a visited AMF, a visited PCF, a visited policy control node) of a visiting (visited) network may send the first configuration message to the UE. The visited network may be a network to which the UE does not subscribe to. The first configuration message may comprise a first set (e.g., one or more first set configuration parameters, one or more first values for the first information and/or the second information) of the first information and/or the second information. The UE may receive the first configuration message, when the UE roams into the visiting network and/or cannot register to the home network. The UE may delete the first set, if the UE de-registers from the visiting network, if the UE registers to another visiting network, and/or if a certain (e.g., a configured time value) elapses after receiving the first set. This may help the UE keeps the information unnecessary long.

[0419] - a second configuration message. A first core network node (e.g., a home AMF, a home PCF, a home policy control node) of a home network may send the second configuration message to the UE. The home network may be a network to which the UE subscribes to. The second configuration message may comprise a second set (e.g., one or more second set configuration parameters, one or more second values for the first information and/or the second information) of the first information and/or the second information. The UE may receive the second set, while the UE is registered to the home network. The UE may not delete the second set, when the UE registers to the visiting network. This may help the UE to determine the NTZ, when the UE returns from the visiting network.

[0420] - a third configuration message. An application server/fu notion (e.g., e.g., USS server, a UTM server, a server of the manufacture, a server managing the NTZ, and/or the like) may send the third configuration message to the UE. The third configuration message may comprise a third set (e.g., one or more third set configuration parameters, one or more third values for the first information and/or the second information) of the first information and/or the second information. This may help the authority and/or a remote operator to provide application specific information to the UE.

[0421] - a sixth configuration message. One or more base stations may send the sixth configuration message to the UE via one or more RRC messages. The sixth configuration message may comprise a sixth set (e.g., one or more sixth set configuration parameters, one or more sixth values for the first information and/or the second information) of the first information and/or the second information. This may help when an entity managing one or more radio network is different from another entity managing a core network.

[0422] For example, the UE may receive the one or more configuration messages.

[0423] In another example, the UE (e.g., ME (mobile equipment)) may be configured with a fourth set (e.g., one or more fourth set configuration parameters, one or more fourth values for the first information and/or the second information) of the first information and/or the second information. For example, the manufacture of the UE may (pre-) configure the UE with the fourth set and/or a user of the UE may configure the UE with the fourth set. For example, a user may use (switch) from one UICC to another UICC (which may not have a valid configuration). In this case, information stored in the ME may help.

[0424] In another example, the SIM card (e.g., UICC (universal integrated circuit card), USIM card) of the UE may be configured with a fifth set (e.g., one or more fifth set configuration parameters, one or more fifth values for the first information and/or the second information) of the first information and/or the second information. For example, the home network of the UE may configure the SIM card with the fifth set. For example, when the UE initially powers up and need to connect to a network, an information stored in the SIM card may help.

[0425] For example, the UE may be configured (and/or receive) with one or more sets (of the first information and/or the second information). For example, the one or more configuration message may comprise a subset of the one or more sets. For example, the UE (e.g., ME, SIM card) may have another subset of the one or more sets.

[0426] In an example, for the first information and/or the second information, different sets may have different values (information). For example, the first information of the first set may indicate an area X as a NTZ and/or the first information of the second set may indicate an area Y as the NTZ. For example, the second information of the third set may indicate a frequency X (e.g., 1 .00 GHz) as one of the one or more restricted frequencies and/or the second information of the fourth set may indicate a frequency X (e.g., 1 .00 GHz) not as one of the one or more restricted frequencies

[0427] In an example, the UE may power on and/or may start to measure/ detect one or more cells to camp on. In an example, the UE may need to determine whether the one or more cells (of one or more measured/ detected cells) are allowed for the UE and/or whether a configured uplink frequency of the one or more cells are restricted to the UE and/or whether the UE is approaching (and/or inside, outside, exiting, entering, near) an area designated as a NTZ, and/or the like. For example, as shown in other examples in this disclosure, the UE may select a target cell based on whether the UE is in the NTZ, and/or which frequencies are restricted, based on measured signal strength, and/or the like.

[0428] To determine whether the UE is in the NTZ and/or to determine whether a cell is configured with uplink resource overlapping at least a portion of the one or more restricted frequencies, the UE may determine (select) a selected set of the one or more sets of the first information and/or the second information. To select a set among the one or more sets, to use for determining one or more areas of a NTZ and/or one or more restricted frequencies, the UE may determine a priority of each set of the one or more sets of the first information and/or the second information and/or the UE may determine precedence among the one or more sets.

[0429] In an example, the UE may determine that the first set of the first information and/or the second information is prioritized (is more important, is high priority, of higher priority) than the second set of the first information and/or the second information. For example, if the UE is not in a coverage area of the home network, if the UE is in a coverage of the visited network, and/or if the UE is registered to the visited (visiting) network, the UE may determine that the first set is prioritized than the second set. For example, if the UE is registered to the visiting network, the UE may determine that the first set is prioritized. For example, if the UE is registered to a second visiting network, and/or if the UE received the first set from a first visiting network, the UE may determine that the first set is not prioritized, that the first set is lowest priority, and/or the UE may discard the first set. For example, if the UE does not have the second set and/or if the UE have the first set, the UE may prioritize the first set.

[0430] In an example, the UE may determine that the second set of the first information and/or the second information is prioritized (is more important, is high priority) than the first set of the first information and/or the second information. For example, if the UE is not in a coverage area of the visited network and/or if the UE is in a coverage of the home network, the UE may determine that the second set is prioritized than the first set. For example, if the UE is registered to the home network, the UE may determine that the second set is prioritized. For example, if the UE does not have the second set and/or if the UE have the first set, the UE may prioritize the first set.

[0431] In an example, the UE may determine that the third set of the first information and/or the second information is prioritized (is more important, is high priority) than the fourth set of the first information and/or the second information. For example, if the UE does not have the first set and/or the second set, the UE may determine to prioritize the third set. For example, if the UE does not receive an updated information of the fourth set (e.g., due to manufacturer not having connection to the UE), the fourth set may be obsolete, and/or it may be helpful to use the third set. In another example, for example, when instructed, the UE may prioritize the third set than the first set and/or the second set.

[0432] In another example, the UE may determine that the first (and/or the second) set of the first information and/or the second information is prioritized (is more important, is high priority) than the third set (and/or the second set) of the first information and/or the second information. For example, if the application server does not have contact information of the UE (e.g., IP address), the third set information may be obsolete, and/or the first set and/or the second set may be more accurate.

[0433] In another example, the UE may determine that the third set of the first information and/or the second information is prioritized (is more important, is high priority) than the first set (and/or the second set) of the first information and/or the second information. For example, if the application server delivers the first information and/or the second information to the home (and/or visiting) network and/or to UE, the first information and/or the second information directly delivered to the UE may be more accurate.

[0434] In an example, the UE may determine that the fifth set of the first information and/or the second information is prioritized (is more important, is high priority) than the fourth set of the first information and/or the second information. For example, if the UE does not receive an updated information from a manufacture, and/or if the stored information in the ME is old, information indicated by the fifth set may be an updated information.

[0435] In another example, the UE may determine that the fourth set of the first information and/or the second information is prioritized (is more important, is high priority) than the fifth set of the first information and/or the second information. For example, if the manufacturer has more accurate information of geography and regulation and/or if the manufacture has control over the UE, the fifth set may be more accurate than the fourth set.

[0436] In another example, the UE may determine that the sixth set of the first information and/or the second information is prioritized (is more important, is high priority) than the first (and/or the second, and/or the third) set of the first information and/or the second information. For example, if a base station controls a cell, the base station may have more accurate information in supporting the connectivity of the UE and may be able to provide more up-to-date information.

[0437] In another example, the UE may determine that the first (and/or the second) set of the first information and/or the second information is prioritized (is more important, is high priority) than the sixth set of the first information and/or the second information. For example, if a base station is not updated to support the NTZ, the base station may not be able to provide up-to-date information in relation to the NTZ. [0438] In an example, based on determining priority of the one or more sets of the first information and/or the second information, and/or based on determining a precedence among the one or more sets, and/or based on determining the most prioritized set among the one or more sets, the UE may determine the selected set. For example, the selected set may be the set prioritized than other one or more sets and/or the selected set may be a set with highest priority and/or the selected set may be the one of highest precedence.

[0439] For example, the UE may determine that the first set of the first information and/or the second information is of the first (highest) precedence, of highest priority than other one or more sets (e.g., the second set, the third set, the fourth set, the fifth set, the sixth set). If the first set is not available, the UE may determine that the second set is next highest precedence (next highest priority) than other one or more sets (e.g., the third set, the fourth set, the fifth set, the sixth set). If the first set and/or the second set is not available, the UE may determine that the third set is next highest precedence (next highest priority) than other one or more sets (e.g., the fourth set, the fifth set, the sixth set). If the first set, the second set, and/or the third set is not available, the UE may determine that the fifth set is next highest precedence (next highest priority) than other one or more sets (e.g., the fourth set, the sixth set). If the first set, the second set, the third set, and/or the fifth set is not available, the UE may determine that the fourth set is next highest precedence (next highest priority) than other one or more sets (e.g., the sixth set).

[0440] For example, the UE may determine that the second set of the first information and/or the second information is of the first (highest) precedence, of highest priority than other one or more sets (e.g., the first set, the third set, the fourth set, the fifth set, the sixth set). If the second set is not available, the UE may determine that the first set is next highest precedence (next highest priority) than other one or more sets (e.g., the third set, the fourth set, the fifth set, the sixth set). If the first set and/or the second set is not available, the UE may determine that the third set is next highest precedence (next highest priority) than other one or more sets (e.g., the fourth set, the fifth set, the sixth set). If the first set, the second set, and/or the third set is not available, the UE may determine that the fifth set is next highest precedence (next highest priority) than other one or more sets (e.g., the fourth set, the sixth set). If the first set, the second set, the third set, and/or the fifth set is not available, the UE may determine that the fourth set is next highest precedence (next highest priority) than other one or more sets (e.g., the sixth set).

[0441] For example, the UE may determine that the third set of the first information and/or the second information is of the first (highest) precedence, of highest priority than other one or more sets (e.g., the first set, the second set, the fourth set, the fifth set, the sixth set). In other example, if the first set and/or the second set and/or the third set is available, the UE may determine that the third set is next highest precedence (next highest priority) than other one or more sets (e.g., the first set, the second set, the fourth set, the fifth set, the sixth set). If the first set, the second set, and/or the third set is not available, the UE may determine that the fifth set is next highest precedence (next highest priority) than other one or more sets (e.g., the fourth set, the sixth set). If the first set, the second set, the third set, and/or the fifth set is not available, the UE may determine that the fourth set is next highest precedence (next highest priority) than other one or more sets (e.g., the sixth set).

[0442] For example, the UE may determine that the fifth set of the first information and/or the second information is of the first (highest) precedence, of highest priority than other one or more sets (e.g., the first set, the second set, the third set, the fourth set, the sixth set). In other example, if the first set and/or the second set and/or the third set and/or the fifth set is available, the UE may determine that the fifth set is next highest precedence (next highest priority) than other one or more sets (e.g., the first set, the second set, the third set, the fourth set, the sixth set). In other example, if the first set, the second set, and/or the third set is not available, the UE may determine that the fifth set is next highest precedence (next highest priority) than other one or more sets (e.g., the fourth set, the sixth set). If the first set, the second set, the third set, and/or the fifth set is not available, the UE may determine that the fourth set is next highest precedence (next highest priority) than other one or more sets (e.g., the sixth set).

[0443] For example, the UE may determine that the fourth set of the first information and/or the second information is of the first (highest) precedence, of highest priority than other one or more sets (e.g., the first set, the second set, the third set, the fifth set, the sixth set). In other example, if the first set and/or the second set and/or the third set and/or the fourth set and/or the fifth set is available, the UE may determine that the fourth set is next highest precedence (next highest priority) than other one or more sets (e.g., the first set, the second set, the third set, the fifth set, the sixth set). If the first set, the second set, and/or the third set and/or the fifth set is not available, the UE may determine that the fourth set is next highest precedence (next highest priority) than other one or more sets (e.g., the sixth set). If the first set, the second set, the third set, and/or the fifth set is not available, the UE may determine that the fourth set is next highest precedence (next highest priority) than other one or more sets (e.g., the sixth set).

[0444] For example, the UE may determine that the sixth set of the first information and/or the second information is of the first (highest) precedence, of highest priority than other one or more sets (e.g., the first set, the second set, the third set, the fourth set, the fifth set). In other example, if the first set and/or the second set and/or the third set and/or the fourth set and/or the fifth set and/or the sixth set is available, the UE may determine that the sixth set is next highest precedence (next highest priority) than other one or more sets (e.g., the first set, the second set, the third set, the fifth set, the fourth set). If the first set, the second set, and/or the third set and/or the fifth set and/or the fourth set is not available, the UE may determine that the sixth set is next highest precedence (next highest priority) than other one or more sets. [0445] In an example, the UE may select the selected set, among the available (e.g., the UE has) sets and/or the UE may select, as the selected set, a set of the highest precedence (e.g., priority) among the available (received, stored, configured) sets. Based on selecting the selected set, the UE may use the first information and/or the second information of the selected set, as shown in other examples of this disclosure

[0446] In an example, the UE may select the first information and/or the second information, from following precedence, from the one or more (available, which the UE has) sets: the first set (e.g., the first information and/or the second information received from a (visited) PCF, a (visited) AMF, a (visited) policy function, a (visited) mobility management function, a (visited) unified data management, of a network (e.g., a PLMN, a SNPN, a NPN)); the second set (e.g., the first information and/or the second information received from a home PCF, a home AMF, a home policy function, a home mobility management function, a home unified data management, of a network (e.g., a (home) PLMN, a (home) SNPN, a (home) NPN)); the third set (e.g., the first information and/or the second information received from an application server (e.g., USS, UTM, an application server associated with an UAV, which may be located outside of a network (e.g., PLMN, SNPN, NPN)); the fifth set (e.g., the first information and/or the second information of a USIM card (SIM card)); a fourth set (e.g., the first information and/or the second information stored in the ME (mobile equipment of the UE, where the UE comprises the ME and/or the USIM card (UICC)); the sixth set (e.g., the first information and/or the second information received from a base station (e.g., via SIB, a RRC message)).

[0447] In another example, the UE may select the first information and/or the second information, from following precedence, from the one or more (available, which the UE has) sets: the second set; the first set; third set; the fifth set; the fourth set; the sixth set. [0448] In another example, the UE may select the first information and/or the second information, from following precedence, from the one or more (available, which the UE has) sets: third set; the second set; the first set; the fifth set; the fourth set; the sixth set.

[0449] In another example, the UE may select the first information and/or the second information, from following precedence, from the one or more (available, which the UE has) sets: third set; the first set; the second set; the fifth set; the fourth set; the sixth set.

[0450] In another example, the UE may select the first information and/or the second information, from following precedence, from the one or more (available, which the UE has) sets: the sixth set (e.g., the first information and/or the second information received from a base station (e.g., via SIB, a RRC message)); the first set (e.g., the first information and/or the second information received from a (visited) PCF, a (visited) AMF, a (visited) policy function, a (visited) mobility management function, a (visited) unified data management, of a network (e.g., a PLMN, a SNPN, a NPN)); the second set (e.g., the first information and/or the second information received from a home PCF, a home AMF, a home policy function, a home mobility management function, a home unified data management, of a network (e.g., a (home) PLMN, a (home) SNPN, a (home) NPN)); the third set (e.g., the first information and/or the second information received from an application server (e.g., USS, UTM, an application server associated with an UAV, which may be located outside of a network (e.g., PLMN, SNPN, NPN)); the fifth set (e.g., the first information and/or the second information of a USIM card (SIM card)); a fourth set (e.g., the first information and/or the second information stored in the ME (mobile equipment of the UE, where the UE comprises the ME and/or the USIM card (UICC)).

[0451] In another example, the UE may select the first information and/or the second information, from following precedence, from the one or more (available, which the UE has) sets: the third set; the first set; the second set; the fifth set; the fourth set; the sixth set.

[0452] In another example, the UE may select the first information and/or the second information, from following precedence, from the one or more (available, which the UE has) sets: the fourth set; the third set; the first set; the second set; the fifth set; the sixth set.

[0453] In another example, the UE may select the first information and/or the second information, from following precedence, from the one or more (available, which the UE has) sets: the fourth set; the first set; the second set; the third set; the fifth set; the sixth set.

[0454] In an example, based on the precedence of the one or more sets, the UE may select the set which is first in the order of the precedence (e.g., appear prior to other sets; first in the order of the list) as the selected set (e.g., the selected first information and/or the selected second information)). For example, the UE may select the set with highest precedence (e.g., appear first in the order of precedence), before selecting other remaining set. [0455] In an example, after selecting the selected set, the UE may use the first information and/or the second information of the selected set, (e.g., as shown in the example of the FIG. 19, FIG. 20, and so on) in determining a cell for cell reselection procedure, and/or to determine whether to perform uplink transmission.

[0456] Example embodiments of FIG. 27 may help a UE to select relevant information for determining restriction associated with the NTZ.. For example, after the UE receives a set from a first source, the UE may not be able to receive updated information from the source. Later, the UE may receive another set from a second source. The example of FIG. 27 may help the UE to receive an updated information and/or the UE may determine to relevant information for the cell reselection.

[0457] FIG. 28 illustrates an example as per an aspect of an embodiment of the present disclosure. For brevity, based on the other part of the present disclosure, redundant details will be omitted.

[0458] In an example, the UE may receive the one or more first messages and/or the UE may get the first information and/or the second information. For example, if the UE receives (has) one or more sets of the first information and/or the second information, the UE may select a set of the one or more sets, and use the first information and/or the second information of the set. (as shown in the example of FIG. 27) The first information may indicate one or more areas of a NTZ. The second information may indicate one or more restricted frequencies in the one or more areas. For example, when a frequency is restricted, the UE may not transmit an uplink signal using the frequency, when the UE is inside the one or more areas of the NTZ. For example, when the frequency is restricted, the UE may not transmit the uplink signal using the frequency, after the UE receives (has) a valid uplink assigned by a network, when the UE is inside the one or more areas of the NTZ.

[0459] In an example, the UE may receive, from (via) a first cell of a base station, the one or more second message. The one or more second message may indicate information of one or more neighboring cells of the first cell and/or one or more interfrequencies used by the one or more neighboring cells. For the first cell and/or for a UE camping on the first cell, a neighboring cell may be an interfrequency cell (or a neighboring cell on the interfrequency) if a first center frequency (of a SSB and/or a CSI-RS) of the neighboring cell is different from a second center frequency of the first cell. For example, the one or more second message may indicate one or more uplink carriers of the one or more neighboring cells and/or of the interfrequencies, may indicate one or more downlink carriers of the one or more neighboring cells and/or of the interfrequencies, may indicate whether the interfrequency is reserved for a NTZ (or an aerial UE), may indicate whether a neighboring cell of the interfrequency comprises partially and/or entirely a portion of the one or more areas of the NTZ, may indicate a block of uplink frequencies configured for the neighboring cell, a block of uplink frequencies configured for a SUL carrier of the neighboring cell, an block of uplink frequencies configured for a NUL carrier of the neighboring cell, a cellReselectionPriority of the interfrequency, an area of the neighboring cell, and/or the like.

[0460] In an example, the UE may measure one or more neighboring cells, based on the information indicated by the one or more first messages and/or the one or more second messages. One or more cells measured by the UE may be one or more candidate cells. For example, based on the area of the neighboring cell and/or the first information, the UE may determine whether the neighboring cell overlaps (partially and/or entirely) with the one or more areas of the NTZ. If the neighboring cell overlaps (partially and/or entirely) with the one or more areas of the NTZ, and/or if one or more configured frequencies of the neighboring cell comprises at least one the UE may and/or may not measure the neighboring cell [0461] In an example, based on measuring the one or more neighboring cells, the UE may perform ranking of the one or more candidate cells, for cell reselection procedure. During the ranking, the UE may exclude one or more cells which may be configured with at least one of the one or more restricted frequencies, if the UE is near (inside) of the one or more areas of the NTZ, from the one or more candidate cells.

[0462] In an example, the UE may check whether the highest ranked cell (e.g., the cell of highest signal quality (e.g., RSRP, RSRQ) among the one or more candidate cells) is configured (e.g., comprises) with at least one of the restricted frequencies, and/or whether the UE is inside the NTZ. In an example, if the UE is not near/inside the NTZ, the UE may consider that there is no restricted frequencies (e.g., due to NTZ). If the highest ranked cell is determined to be restricted, the UE may check similarly next highest ranked cell and may continue this procedure, until the UE finds the highest ranked cell which is not restricted.

[0463] In an example, the UE's hardware may support measurement of frequency C1 and/or may not support the measurement of frequency C2. In this case, the frequency C2 is not restricted (by the NTZ), because the UE cannot measure any signal of the frequency C2. In this disclosure, restriction may be result of the application of the NTZ, not result of limited UE (hardware) capability.

[0464] In an example, if the UE finds a cell which is not restricted due to NTZ, the UE may select the highest ranked cell. The UE may send an uplink signal to the selected cell and/or may perform cell reselection to the cell.

[0465] Example embodiments of FIG. 28 may help to prevent a UE from unnecessary transmission in a cell restricted due to the NTZ.

[0466] FIG. 29 illustrates an example as per an aspect of an embodiment of the present disclosure. For brevity, based on the other part of the present disclosure, redundant details will be omitted.

[0467] In an example, the UE may receive the first information and/or the second information, and/or the one or more second messages (as shown in the examples in this disclosure) [0468] In an example, the UE may determine, for each interfrequency of the one or more interfrequencies, whether the each interfrequency is restricted (due to NTZ). For example, based on the first information and/or the second information, the UE may determine whether the each interfrequency is restricted or not. For example, if the UE is near/inside the NTZ (area of the NTZ) and/or if the at least one frequency of the each interfrequency belongs to the one or more restricted frequencies, the UE may determine that the interfrequency is restricted. For example, based on that the each interfrequency is restricted, the UE may not consider one or more cells of the each interfrequency for candidate for cell reselection.

[0469] For example, if the each interfrequency is restricted, the UE may not perform measurement of the one or more cells of the interfrequency and/or may exclude the one or more cells from candidate for cell reselection. For example, if the each interfrequency is not restricted, the UE may perform measurement of the one or more cells of the interfrequency and/or may consider the one or more cells from candidate for cell reselection.

[0470] Example embodiments of FIG. 29 may help to prevent a UE from unnecessary transmission in a cell restricted due to the NTZ.

[0471] FIG. 30 illustrates an example as per an aspect of an embodiment of the present disclosure. For brevity, based on the other part of the present disclosure, redundant details will be omitted.

[0472] In an example, the UE may receive the first information and/or the second information, and/or the one or more second messages (as shown in the examples in this disclosure).

[0473] In an example, the UE may determine whether the UE is inside (enters, near) the one or more areas of the NTZ.

[0474] Based on whether the UE determines that the UE is inside the one or more areas of the NTZ, based on the one or more first messages and/or based on the one or more second messages, the UE may determine whether a first frequency (e.g ., of the current frequency, of the one or more interfrequencies) are restricted or not, and/or whether a second frequency (e g., of the current frequency, of the one or more interfrequencies) are restricted or not. For example, if the UE's current location is inside of an area indicated by one or more coordinates (indicated by the first information), the UE may determine that the UE is inside the NTZ. For example, if the UE’s current location is outside of an area indicated by one or more coordinates (indicated by the first information), the UE may determine that the UE is not inside the NTZ. [0475] If the first frequency is restricted and/or if the second frequency is not restricted, the UE may consider that the first frequency is of lowest priority, that the priority of the first frequency is lower than the priority of the second frequency, and/or the like. If the first frequency is not restricted and/or if the second frequency is restricted, the UE may consider that the second frequency is of lowest priority, that the priority of the second frequency is lower than the priority of the first frequency, and/or the like. If the first frequency is not restricted and/or if the second frequency is not restricted, the UE may consider that the priority of the second frequency is a value of cell Reselection Priority of the second frequency, that the priority of the first frequency is a value of cellReselectionPriority (e.g., indicated by RRC messages, SIBs) of the first frequency, and/or the like. If the first frequency is restricted and/or if the second frequency is restricted, the UE may consider that the second frequency is of lowest priority, the UE may consider that the first frequency is of lowest priority, and/or the like. If a frequency is not restricted due to NTZ, the priority of the frequency may be a value of cellReselectionPriority of the frequency. If a frequency is restricted due to NTZ, the priority of the frequency may be lowest, and/or may be lower than any other frequency that is not restricted.

[0476] In an example, based on the one or more priorities of the one or more frequency, the UE may perform measurement (and perform cell reselection), in the order of the one or more priorities of the one or more frequencies. For example, before measuring one or more cells (of a frequency) of lower priority, the UE may perform measurement of the one or more cells of (another frequency of) higher priority. For example, before measuring one or more cells restricted due to NTZ, the UE may perform measurement of one or more cells which are not restricted due to NTZ.

[0477] Example embodiments of FIG. 30 may help a base station to prevent unnecessary transmission of a paging message in a cell restricted due to the NTZ.

[0478] FIG. 31 illustrates an example as per an aspect of an embodiment of the present disclosure. For brevity, based on the other part of the present disclosure, redundant details will be omitted.

[0479] In an example, the UE may receive (get, have) a first set of the first information and/or the second information, from a first source. In an example, the UE may receive (get, have) a second set of the first information and/or the second information, from a second source.

[0480] In an example, the UE may determine a priority among the one or more sets of the first information and/or the second information. For example, the one or more sets may comprise the first set and/or the second set.

[0481] In an example, the UE may determine that the first set is prioritized (has higher precedence) than the second set, based on the receiving the first set from the first source and the second set from the second source. For example, the first source may be at least one of a policy function of a core network node, of a network and/or the second source may be at least one of a manufacture of the UE, a ME of the UE, a UICC of the UE, an application server associated with a UAV (and/or the NTZ, UAM, USS, UTM, and/or the like).

[0482] In another example, the UE may determine that the first set is prioritized (has higher precedence) than the second set, based on the receiving the first set from the first source and the second set from the second source. For example, the first source may be at least one of an application server associated with a UAV (and/or the NTZ, UAM, USS, UTM, and/or the like) and/or the second source may be at least one of a manufacture of the UE, a ME of the UE, a II ICC of the UE, a policy function of a core network node, of a network.

[0483] In another example, the UE may determine that the first set is prioritized (has higher precedence) than the second set, based on the receiving the first set from the first source and the second set from the second source. For example, the first source may be at least one of a UICC of the UE and/or the second source may be at least one of a manufacture of the UE, a ME of the UE, an application server associated with a UAV (and/or the NTZ, UAM, USS, UTM, and/or the like), a policy function of a core network node, of a network.

[0484] In an example, among the available sets (e.g., the sets that the UE has, receives), the UE may determine the set of highest priority (e.g., higher than other available sets). The UE may use the set of the highest priority as the selected set. For example, the UE may use the first information and/or the second information, of the selected set, as shown in other examples in this disclosure.

[0485] Example embodiments of FIG. 31 may help a base station to prevent unnecessary transmission of a paging message in a cell restricted due to the NTZ.

[0486] In this disclosure, a UE determine whether a cell (interfrequency, a uplink carrier, an uplink BWP) is restricted or not based on whether the cell (interfrequency, a uplink carrier, an uplink BWP) comprise at least a portion of the one or more restricted frequencies. Additionally and/or alternatively, the UE may determine whether a cell (interfrequency, a uplink carrier, an uplink BWP) is restricted or not, based on whether the cell (interfrequency, a uplink carrier, an uplink BWP) comprise at least a portion of uplink frequencies (e.g., uplink carrier, uplink BWP) which is not restricted by the one or more restricted frequencies. For example, if a cell is configured with uplink frequencies from 1000 MHz to 1100 MHz, and if the restricted frequencies is from 1050 MHZ to 1150 MHz, the cell may have an uplink frequencies which are not restricted by the one or more restricted frequencies, and the UE may select this cell, when the UE is inside the NTZ. This way of determining may be applicable to in other examples in this disclosure.

[0487] Clause 1. A method comprising: receiving, by a wireless device, one or more messages comprising: one or more first parameters indicating one or more first frequencies, wherein transmission by the wireless device via the one or more first frequencies is restricted within a no transmission zone (NTZ); and one or more second parameters indicating one or more second frequencies for cell selection procedure; in response to entering the NTZ, determining a first priority of the one or more first frequencies being lower than a second priority of the one or more second frequencies; and performing, based on the determining, measurement of one or more cells of the one or more second frequencies.

[0488] Clause 2. A method comprising: determining, by a wireless device, a priority of one or more first frequencies, in response to the wireless device entering a location indicated by a no transmission zone (NTZ), wherein, in the NTZ, transmission via the one or more first frequencies is restricted for the wireless device; and performing, by the wireless device and based on the determining, measurement of one or more cells of one or more second frequencies.

[0489] Clause 3. The method of clause 2, further comprising receiving by the wireless device, one or more messages comprising one or more first configuration parameters and one or more second configuration parameters, associated with the NTZ.

[0490] Clause 4. The method of clause 3, wherein the one or more second configuration parameters indicate the one or more second frequencies of one or more neighboring cells.

[0491] Clause 5. The method of clause 3, wherein the one or more first configuration parameters indicate the one or more first frequencies and transmission via the one or more first frequencies are restricted in the location.

[0492] Clause 6. The method of clause 2, wherein the wireless device is in a first cell using at least one of the one or more the first frequencies.

[0493] Clause 7. The method of clause 6, wherein a first measure signal strength of the first cell is above a first threshold value.

[0494] Clause 8. The method of clause 2, wherein the priority of the one or more first frequencies is lower than a second priority of the one or more second frequencies, based on the wireless device is inside the location.

[0495] Clause 9. The method of clause 8, wherein the wireless device considers the priority as the lowest, in response to the wireless device entering the NTZ.

[0496] Clause 10. The method of clause 2, wherein the priority of the one or more first frequencies changes from a first value to a second value, based on whether the wireless device is inside the location. [0497] Clause 11 . The method of clause 2, further comprising exiting by the wireless device, the location of the NTZ.

[0498] Clause 12. The method of clause 11 , wherein the wireless device stop measurement of one or more second cells on the one or more second frequencies, in response to exiting the NTZ.

[0499] Clause 13. The method of clause 11 and 7, wherein the wireless device stop measurement of the one or more second frequencies, if a second signal strength of the first cell is above the first threshold. [0500] Clause 14. The method of clause 2 and claim 5, further comprising removing by the wireless device, one or more first cells of the one or more first frequencies, from a list of candidate cells for cell reselection, based on that the wireless device is in the NTZ and based on the one or more first configuration parameters.

[0501] Clause 15. The method of clause 14, wherein one or more uplink frequencies of the one or more first cells comprise at least one of the one or more first frequencies indicated by the one or more first configuration parameters. [0502] Clause 16. The method of clause 3, wherein the wireless device receives a first set of the one or more first configuration parameters from an application server associated with the NTZ and the first set comprises one or more first information associated with a first NTZ.

[0503] Clause 17. The method of clause 3, wherein the wireless device receives a second set of the one or more first configuration parameters from a core network node and the second set comprises one or more second information associated with a second NTZ.

[0504] Clause 18. The method of clause 16 and 17, wherein the wireless device selects for the one or more first configuration parameter, among the first set and the second set.

[0505] Clause 19. The method of clause 18, wherein the wireless device selects the first set as a selected set, based on prioritizing the first set over the second set.

[0506] Clause 20. The method of clause 18, wherein the wireless device selects the second set as the selected set, based on prioritizing the second set over the first set.

[0507] Clause 21 . The method of clause 19 and 20, wherein the wireless device uses the one or more first configuration parameters of the selected set, for determining the priority.

[0508] Clause 22. The method of clause 2, wherein the wireless device determines the priority of the one or more first frequencies, in response to entering the location.

[0509] Clause 23. The method of clause 4, wherein one or more system information blocks (SIBs) of the first cell comprises the one or more second configuration parameters.

[0510] Clause 24. The method of clause 23, wherein the one or more second configuration parameters indicate one or more normal uplink (NUL) carriers of the one or more neighboring cells.

[0511] Clause 25. The method of clause 23, wherein the one or more second configuration parameters indicate one or more supplementary uplink (SUL) carriers of the one or more neighboring cells.

[0512] Clause 26. The method of clause 2, wherein the one or more second frequencies is one or more uplink frequencies configured by the one or more neighboring cell.

[0513] Clause 27. The method of clause 24 and 25, wherein the wireless device determines whether the one or more neighboring cells are configured with at least a portion of the one or more first frequencies, based on the one or more second configuration parameters.

[0514] Clause 28. The method of clause 24 and 25, wherein the wireless device determines whether the one or more neighboring cells are configured with at least a portion of the one or more second frequencies, based on the one or more second configuration parameters.

[0515] Clause 29. The method of clause 23, wherein the one or more second configuration parameters indicate at least one of: whether a cell of the one or more neighboring cells is a NTZ cell; whether a cell of the one or more neighboring cells is allowed to an aerial wireless device; whether a cell of the one or more neighboring cells is entirely covered by the NTZ; whether a cell of the one or more neighboring cells is partially covered by the NTZ; information on coverage area of a cell of the one or more neighboring cells [0516] Clause 30. The method of clause 2, wherein the wireless device skip measurement of one or more first cells configured with the one or more first frequencies, based on at least one of that the priority of the one or more first frequencies are lowest, that the priority of the one or more first frequencies are lower than the one or more second frequencies.

[0517] Clause 31 . The method of clause 2, wherein the wireless device initiates measurement of one or more second cells configured with the one or more second frequencies, based on at least one of that the priority of the one or more first frequencies are lowest, that the priority of the one or more first frequencies are lower than the one or more second frequencies.

[0518] Clause 32. A method comprising: determining, by a wireless device, a priority of one or more first frequencies, based on one or more parameters indicating conditions allowing use of the one or more first frequencies; and performing, by the wireless device and based on the determining, measurement of one or more cells of one or more second frequencies.

[0519] Clause 33. A method comprising: receiving, by a wireless device, one or more messages comprising: one or more first parameters indicating one or more first frequencies, wherein transmission by the wireless device via the one or more first frequencies is restricted within a no transmission zone (NTZ); and one or more second parameters indicating one or more second frequencies for cell selection procedure; in response to entering the NTZ, determining one or more priorities: a first priority, of the one or more priorities, of the one or more first frequencies; and a second priority, of the one or more priorities, of the one or more second frequencies; and based on the determining the one or more priorities: performing measurement of one or more cells of the one or more second frequencies, skipping measurement of one or more cells of the one or more first frequencies.

[0520] Clause 34. A method comprising: receiving, by the wireless device, one or more messages, wherein: a first message, of the one or more messages, received from an application server, comprises one or more first configuration parameters for one or more first no transmission zones (NTZs), wherein, in the NTZ, transmission is not allowed for the wireless device; a second message, of the one or more messages, received from a core network function, comprises one or more second configuration parameters for one or more second NTZs; determining, by the wireless device: a first priority of the one or more first configuration parameters, based on receiving from the application server; and a second priority of the one or more second configuration parameters, based on receiving from the core network function; selecting, by the wireless device based on the determining, as selected configuration: the one or more first configuration parameters, based on that the first priority is higher than the second priority; and the one or more second configuration parameters, based on that the second priority is higher than the first priority; transmitting, by the wireless device, via one or more frequencies not indicated by the selected configuration.

[0521] Clause 35. A method comprising: receiving, by the wireless device from an application server associated with no transmission zones (NTZ), one or more first configuration parameters of one or more first NTZs, wherein, in the NTZ, transmission is not allowed for the wireless device; receiving, by the wireless device from a core network function, one or more second configuration parameters of one or more second NTZs; determining, by the wireless device, to prioritize the one or more second configuration parameters over the one or more first configuration parameters; and transmitting, by the wireless device to a cell, an uplink signal, in response to: the wireless device being outside of the one or more second NTZs. [0522] Clause 36. A method comprising: receiving, by the wireless device from an application server, one or more first configuration parameters of one or more first no transmission zones (NTZs), wherein, in the NTZ, transmission is not allowed for the wireless device; receiving, by the wireless device from a core network function, one or more second configuration parameters of one or more second NTZs; and prioritizing, by the wireless device, one or more second configuration parameters over the one or more first configuration parameters.

[0523] Clause 37.A method comprising: receiving, by the wireless device from an application server, one or more configuration parameters associated with one or more no transmission zones (NTZs), wherein: in the NTZ, transmission is not allowed for the wireless device; the wireless device receives a first configuration parameter, of the one or more configuration parameters, from a policy control function of a network; the wireless device receives a second configuration parameter, of the one or more configuration parameters, from an application server associated with a NTZ; prioritizing, by the wireless device, the first configuration parameters over the second configuration parameters; and applying, by the wireless device, the first configuration parameters.

[0524] Clause 38. A method comprising: receiving, by the wireless device from an application server, one or more configuration parameters associated with one or more no transmission zones (NTZs), wherein: in the NTZ, transmission is not allowed for the wireless device; the wireless device receives a first configuration parameter, of the one or more configuration parameters, from a policy control function of a network; the wireless device is configured with a third configuration parameter, of the one or more configuration parameters, of a Universal Integrated Circuit Card (UICC); prioritizing, by the wireless device, the first configuration parameters over the second configuration parameters; and applying, by the wireless device, the first configuration parameters.

[0525] Clause 39. A method comprising: sending, by a base station to a wireless device via a first cell, a second messages comprising one or more second parameters, wherein: the one or more second parameters indicate one or more inter-frequencies comprising a second frequency. [0526] Clause 40. The method of clause 39, wherein the one or more second parameters comprise an information of a normal uplink (NUL) frequency of a neighboring cell.

[0527] Clause 41 . The method of clause 39, wherein the one or more second parameters comprise an information of a supplementary uplink (SUL) frequency of a neighboring cell.

[0528] Clause 42. The method of clause 39, wherein the base station receives from a second base station, the one or more second parameters.

[0529] Clause 43. The method of clause 42, wherein the base station is a base station central unit (CU) and the second base station is at least one of a second base station CU or a base station distributed unit (DU).

[0530] Clause 44. The method of clause 39, further comprising sending by the base station to a core network node, one or more third parameter, wherein the one or more third parameter indicate at least one of a first NUL frequency or a first SUL frequency of the base station.

[0531] Clause 44. A method comprising: sending, by a base station to a wireless device via a first cell, a second messages comprising one or more second parameters, wherein: the one or more second parameters indicate one or more inter-frequencies comprising a second frequency.

[0532] Clause 45. A method comprising: receiving, by a base station from a wireless device via a first cell, a radio resource control (RRC) message requesting setup of a RRC connection; and sending, by the base station to a core network node, an information of uplink frequency of the first cell of the base station.

[0533] Clause 46. A method comprising: receiving, by a base station from a core network node, a paging request for a wireless device, wherein the paging request comprises one or more frequencies not allowed for the wireless device.

[0534] Clause 47. A method comprising: receiving, by a wireless device in a first cell, a second messages comprising one or more second parameters, wherein: the one or more second parameters indicate one or more inter-frequencies comprising a second frequency; receiving, by the wireless device, a first message comprising one or more first parameters indicating a non-transmission zone (NTZ) where transmission via a first frequency is restricted for the wireless device; measuring, by the wireless device, a second cell on the second frequency, in response to: the wireless device being in the NTZ; a received power of the first cell of the first frequency is above a first threshold; and performing, by the wireless device and based on the measuring, a cell reselection to a second cell on the second frequency from the first cell.

[0535] Clause 48. A method comprising: receiving, by a wireless device, a first message comprising one or more first parameters indicating a non-transmission zone (NTZ) where transmission via a first frequency is restricted for the wireless device; receiving, by the wireless device, a second messages comprising one or more second parameters, wherein: the one or more second parameters indicate one or more interfrequencies comprising a frequency and a second frequency; excluding, by the wireless device from a candidate list of cells, one or more first cells, in response to: the wireless device being in the NTZ; the one or more first cells using the first frequency; and performing, by the wireless device and based on the measuring, a cell reselection to a second cell on the second frequency.

[0536] Clause 49. A method comprising: receiving, by a wireless device, a first message comprising one or more first parameters indicating a non-transmission zone (NTZ) where transmission via a first frequency is restricted for the wireless device; receiving, by the wireless device from a second cell, a third message comprising information of one or more uplink frequencies of the second cell; excluding, by the wireless device from a candidate list of cell re-selection, the second cell, in response to: the wireless device being in the NTZ; the one or more uplink frequencies comprises the first frequency; performing, by the wireless device and based on the measuring, a cell reselection to a third cell from the candidate list.

[0537] Clause 50. A method comprising: receiving, by a wireless device, a first message comprising one or more first parameters indicating a non-transmission zone (NTZ) where transmission via a first frequency is restricted for the wireless device; and performing, by the wireless device and based on the one or more first parameters, a cell reselection procedure, in response to: the wireless device being in the NTZ; the second cell using the first frequency; and signal quality of the second cell is above a first threshold.

[0538] Clause 51 .A method comprising: receiving, by a wireless device from a base station, one or more radio resource control (RRC) messages comprising one or more parameters indicating: a list of one or more inter-frequencies, comprising a first frequency and a second frequency; and that the first frequency is prioritized than the second frequency; and receiving, by the wireless device, one or more configuration parameters indicating an area where transmission is not allowed for the wireless device; determining, by the wireless device, to deprioritize the first frequency, based on that: the wireless devices is in the NTZ; and transmission via the first frequency is restricted in the NTZ; and selecting, by the wireless device and based on the determining, a cell on the second frequency.

[0539] Clause 52. A method comprising: receiving, by a wireless device, a first message indicating a nontransmission zone (NTZ) where transmission via a second frequency is restricted for the wireless device; receiving, by the wireless device, one or more radio resource control (RRC) messages comprising one or more parameters of one or more inter-frequencies, wherein; the one or more inter-frequencies comprise the first frequency; the one or more parameters comprises at least one of: a first parameter indicating whether a first cell of the first frequency is a cell of non-transmission zone (NTZ); a second configuration parameter indicating that an uplink frequency of the first cell is the second frequency; and excluding, by the wireless device from a list of candidate cells and based on the one or more parameters, the first cell; and performing cell reselection, by the wireless device, to a second cell from the list of candidate cells.

[0540] Clause 53. A method comprising: receiving, by a wireless device, one or more first parameters indicating one or more first frequencies, wherein: within a location indicated by a non-transmission zone (NTZ), transmission via the one or more first frequencies is restricted for the wireless device; receiving, by the wireless device, one or more second parameters indicating one or more second frequencies; in response to entering the location, determining, by the wireless device and based on the one or more first parameters, a priority of the one or more first frequencies being the lowest; and performing, by the wireless device and based on the determining, measurement of one or more cells of the one or more second frequencies.

Claims

CLAIMS What is claimed is:

1. A method comprising: sending, by a wireless device, a message comprising an information indicating support for no transmission zone (NTZ) information; receiving, by the wireless device from a base station of a network, one or more first radio resource control (RRC) messages indicating a plurality of frequencies of a plurality of cells; receiving, by the wireless device from a unmanned aerial service (UAS) application server, a NTZ policy container message comprising one or more first parameters indicating one or more first frequency bands, wherein transmission by the wireless device via the one or more first frequency bands is restricted within the NTZ; performing, by the wireless device, cell measurement, based on the one or more first messages; selecting, by the wireless device in NTZ and based on the cell measurement, a cell of the plurality of cells for camping, based on determining whether the cell is in the one or more first frequency bands associated with the NTZ; based on the one or more first messages, sending, to a base station and when the wireless device is in the NTZ, a first measurement report message, wherein the first measurement report message does not comprise measurement report of one or more cells of the plurality of cells, based on the one or more cells being in the one or more first frequency bands; and sending, to the base station and based on determining that the wireless device exits the NTZ, a second measurement report message, wherein the second measurement report message comprises a second measurement report of the one or more cells of the plurality of cells.

2. A method comprising: receiving, by a wireless device, one or more first messages indicating a plurality of frequencies of a plurality of cells; receiving a second message comprising one or more first parameters indicating one or more first frequency bands, wherein transmission by the wireless device via the one or more first frequency bands is restricted within a no transmission zone (NTZ); performing cell measurement based on the one or more first messages; and based on the one or more first messages, sending, to a base station and when the wireless device is in the NTZ, a measurement report message, wherein the measurement report message does not comprise a measurement report of one or more cells of the plurality of cells, based on the one or more cells being in the one or more first frequency bands.

3. A method comprising: sending, by a wireless device to a base station and when the wireless device is in a no transmission zone (NTZ), a measurement report message, wherein: transmission by the wireless device via one or more first frequency bands is restricted within the NTZ; and the measurement report message does not comprise a measurement report of one or more cells of a plurality of cells that are in the one or more first frequency bands.

4. The method of claim 3, further comprising: receiving, by the wireless device, one or more first messages indicating a plurality of frequencies of a plurality of cells; receiving a second message comprising one or more first parameters indicating the one or more first frequency bands; and performing cell measurement based on the one or more first messages, wherein the sending is based on the one or more first messages.

5. The method of claim 4, wherein the wireless device receives the second message, from an unmanned aircraft system (UAS) application server, and the wireless device receives the one or more first messages from the base station.

6. The method of one of claims 4 to 5, wherein the second message comprises one or more NTZ policy containers.

7. The method of one of claims 4 to 6, wherein the wireless device receives the second message, based on sending a message indicating support for no transmission zone (NTZ) information.

8. The method of one of claims 3 to 7, wherein the sending is based on the one or more cells being in the one or more first frequency bands.

9. The method of one of claims 3 to 8, wherein the measurement report message comprises a measurement report of one or more second cells, of the plurality of cells, that does not overlap the one or more first frequency bands.

10. The method of one of claims 3 to 9, wherein the one or more cells of the plurality of cells overlap in frequency with the one or more frequency bands associated with the NTZ.

11 . The method of one of claims 3 to 10, wherein the one or more first messages comprise one or more first RRC messages.

12. The method of one of claims 3 to 11 , wherein the plurality of frequencies of the plurality of cells is associated with performing cell measurement.

13. The method of one of claims 3 to 12, further comprising selecting by the wireless device in NTZ, a cell of the plurality of cells, for camping, based on the cell not being in the one or more first frequency bands associated with the NTZ.

14. The method of claim 13, wherein the one or more first messages comprise one or more indications indicating whether a first cell of the plurality of cells comprises the NTZ.

15. The method of one of claims 3 to 14, wherein the one or more first message further indicates, for each frequency of the plurality of frequencies, a frequency band associated with the each frequency.

16. The method of claim 15, wherein the measurement report message does not comprise the measurement report, based on that a second frequency band of the one or more cells are at least one of the one or more first frequency bands.

17. The method of one of claims 3 to 16, wherein the one or more first messages indicates, for each frequency of the plurality of frequencies, a selection priority associated with the each frequency.

18. The method of claim 17, wherein, the wireless device determines that a first selection priority associated with the one or more cells is lowest, based on at least one of that the one or more cells being in the one or more first frequency bands, or that the wireless device is in the NTZ.

19. The method of claim 18, wherein, the first selection priority is set to a second selection priority value, when the wireless device exits the NTZ.

20. The method of one of claims 3 to 19, wherein the wireless performs cell measurement of the plurality of the cells.

21 . The method of claim 20, wherein the wireless device performs ranking of the plurality of the cells, based on performing cell measurement.

22. The method of claim 21 , wherein the wireless device determines whether a highest ranking cell is in the one or more first frequency bands.

23. The method of claim 22, wherein the wireless device selects the highest ranked cell as the cell, based on that the highest ranked cell is not in the one or more first frequency bands.

24. The method of one of claims 21 to 23, wherein the wireless device excludes the one or more cells from when the wireless device performs ranking.

25. The method of one of claims 3 to 24, further comprising sending by the wireless device a response message in the cell, based on that the wireless device receives a paging message and that the cell is not in the one or more first frequency bands.

26. The method of one of claims 3 to 25, wherein the one or more first message indicates a first selection priority value for the one or more cells and a second selection priority value for the one or more second cells

27. The method of claim 26, wherein, the wireless device determines that a second selection priority associated with the one or more second cells is the second selection priority value, based on at least one of that the one or more second cells not being in the one or more first frequency bands, or that the wireless device is not in the NTZ.

28. The method of claim 27, wherein, based on the determining, the measurement report message does not comprise the measurement report.

29. The method of one of claims 3 to 28, wherein the one or more cells are configured with a normal uplink (NUL) and a supplemental uplink (SUL), and at least one of the NUL and the SUL is in the one or more first frequency bands.

30. The method of one of claims 3 to 29, wherein the one or more cells are configured with a normal uplink (NUL) and a supplemental uplink (SUL), and both the NUL and the SUL is in the one or more first frequency bands.

31 . The method of one of claims 29 and 30, wherein, based on the NUL and the SUL, the wireless device determines that the one or more cells is in the one or more first frequency bands.

32. The method of one of claims 3 to 31 , wherein the one or more messages are at least one of one or more system information block or one or more RRC Reconfiguration messages.

33. The method of one of claims 3 to 32, wherein the one or more first messages indicates, for each frequency of the plurality of frequencies, whether a NTZ area exists on the each frequency.

34. The method of one of claims 3 to 33, wherein the wireless device performs measurement of cells, when the wireless device is in the NTZ.

35. The method of one of claims 3 to 34, wherein the plurality of frequencies is at least one of a plurality of SSB frequencies of the plurality of cells or a plurality of frequency bands.

36. A method comprising: receiving, by a wireless device, one or more first messages indicating a plurality of frequencies of a plurality of cells; receiving, by the wireless device, a second message comprising one or more first parameters indicating one or more first frequency bands, wherein transmission by the wireless device via the one or more first frequency bands is restricted within a no transmission zone (NTZ); performing cell measurement, based on the one or more first RRC message; selecting, when the wireless device is in NTZ, a cell of the plurality of cells for camping, based on the cell not being in the one or more first frequency bands associated with the NTZ; based on the one or more first messages, sending, to a base station and when the wireless device is in NTZ, a measurement report message, wherein the measurement report message does not comprise measurement report of one or more cells of the plurality of cells, based on the one or more cells being in the one or more first frequency bands.

37. A method comprising: receiving, by a wireless device, one or more first messages indicating a plurality of frequencies of a plurality of cells; receiving, by the wireless device, a second message comprising one or more first parameters indicating one or more first frequency bands, wherein transmission by the wireless device via the one or more first frequency bands is restricted within a no transmission zone (NTZ); performing cell measurement, based on the one or more first RRC message; excluding, based on the second message, from a plurality of candidate cells, one or more cells in the one or more first frequency bands; and selecting, when the wireless device is in NTZ, a cell of the plurality of candidate cells for camping, based on the cell not being in the one or more first frequency bands associated with the NTZ.

38. 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 37.

39. 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 37.