Feedback for measurement gap skipping

Abstract

A wireless device receives one or more configurations indicating a plurality of measurement gaps (MGs) associated with a duration of time for performing one or more measurements. The wireless device receives downlink control information (DCI) indicating to cancel a first MG among the plurality of MGs, wherein the DCI does not schedule any physical downlink shared channel (PDSCH) receptions. The wireless device transmits feedback for the DCI in response to receiving the DCI indicating to cancel the first MG. The wireless device cancels the first MG based on the DCI.

Description

Docket No.: 24-1263PCTTITLEFeedback for Measurement Gap SkippingCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 717,055, filed November 6, 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 morePUCCH 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.Docket No.: 24-1263PCT

[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.DETAILED DESCRIPTION

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

[0032] 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.Docket No.: 24-1263PCT

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

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

[0035] 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 theDocket No.: 24-1263PCT 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.

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

[0037] In this disclosure, parameters (or equally called, fields, or Information elements: lEs) 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.

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

[0039] 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 logicDocket No.: 24-1263PCT 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.

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

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

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

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

[0044] 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, forDocket No.: 24-1263PCT 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).

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

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

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

[0048] 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. 1 A. 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). EmbodimentsDocket No.: 24-1263PCT 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.

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

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

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

[0052] 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),Docket No.: 24-1263PCT 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.

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

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

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

[0056] 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 interfaceDocket No.: 24-1263PCT management, UE context management, UE mobility management, transport of NAS messages, paging, PDU session management, and configuration transfer and / or warning message transmission.

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

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

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

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

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

[0062] 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 connectionDocket No.: 24-1263PCT 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.

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

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

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

[0066] 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 TransportDocket No.: 24-1263PCTBlocks (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.

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

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

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

[0070] 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 entirelyDocket No.: 24-1263PCT 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.

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

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

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

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

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

[0076] - 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 systemDocket No.: 24-1263PCT information messages may be used by the UEs to obtain information about how a cell is configured and how to operate within the cell;

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0092] - a physical random access channel (PRACH) for random access.Docket No.: 24-1263PCT

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

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

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

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

[0097] 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 anyDocket No.: 24-1263PCT 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 DLE), and RRC inactive 606 (e.g., RRCJNACTIVE).

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

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

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

[0101] An RRC state may be associated with a mobility management mechanism. In RRC idle 604 and RRC inactive 606, mobility is managed by the UE through cell reselection. The purpose of mobilityDocket No.: 24-1263PCT 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).

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

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

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

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

[0106] 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 domainDocket No.: 24-1263PCT 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.

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

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

[0109] 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.Docket No.: 24-1263PCT

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

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

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

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

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

[0115] 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.Docket No.: 24-1263PCT

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

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

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

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

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

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

[0122] 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 switchingDocket No.: 24-1263PCT 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.

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

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

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

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

[0127] 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 connectionDocket No.: 24-1263PCT 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).

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

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

[0130] 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 transmitDocket No.: 24-1263PCTUCI 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.

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

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

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

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

[0135] 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 frequencyDocket No.: 24-1263PCT 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.

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

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

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

[0139] 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, averageDocket No.: 24-1263PCT 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.

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

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

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

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

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

[0145] 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 andDocket No.: 24-1263PCT resource elements associated with the downlink CSI-RS are outside of PRBs configured for the SS / PBCH blocks.

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

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

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

[0149] 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 scheduledDocket No.: 24-1263PCT 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.

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

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

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

[0153] 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 SRSDocket No.: 24-1263PCT 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 RUSCH 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.

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

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

[0156] 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.Docket No.: 24-1263PCT

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

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

[0159] 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 determineDocket No.: 24-1263PCT 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.

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

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

[0162] 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.Docket No.: 24-1263PCT

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

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

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

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

[0167] 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: generalDocket No.: 24-1263PCT 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.

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

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

[0170] 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 withDocket No.: 24-1263PCT 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.

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

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

[0173] 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 ofDocket No.: 24-1263PCT 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:RA-RNTI= 1 + s_id + 14 x t_id + 14 x 80 x fjd + 14 x 80 x 8 x ul_carrier_id , where s_id may be an index of a first OFDM symbol of the PRACH occasion (e.g., 0 < sjd < 14), t_id may be an index of 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).

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

[0175] 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 SDUDocket No.: 24-1263PCT 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.

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

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

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

[0179] 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 contention-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 preambleDocket No.: 24-1263PCT 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.

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

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

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

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

[0184] 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 matchedDocket No.: 24-1263PCT 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).

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

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

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

[0188] 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.Docket No.: 24-1263PCT

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

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

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

[0192] 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 beDocket No.: 24-1263PCT 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.

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

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

[0195] 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 downlinkDocket No.: 24-1263PCT 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.

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

[0197] 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”. IfDocket No.: 24-1263PCT 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".

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

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

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

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

[0202] 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 systemDocket No.: 24-1263PCT1510 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.

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

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

[0205] The processing system 1508 and the processing system 1518 may be 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.

[0206] 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 / outputDocket No.: 24-1263PCT processing, and / or any other functionality that may enable the wireless device 1502 and the base station 1504 to operate in a wireless environment.

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

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

[0209] 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.Docket No.: 24-1263PCT

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

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

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

[0213] 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.Docket No.: 24-1263PCT

[0214] In an example embodiment, any two or more than two of the following sentences, paragraphs, (sub)-bullets, 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.

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

[0216] In an example embodiment, dependency, such as "based on”, "in response to”, "specifically”, "more specifically”, “preferably”, “in one / some embodiment”, “in one / some alternative”, “in one / some example”, “in one / some aspect”, “in one / some implementation”, “for example”, etc., In an example embodiment is just one possible example which would not restrict the specific method.

[0217] In an example embodiment, 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.

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

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

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

[0221] UE may transmit, to BS, one or more UE assistance information via an Information Element (IE) UEAssistancelnformation. UE may transmit, to BS, one or more UE assistance information via an IEDocket No.: 24-1263PCTUEAssistancelnformation based on one or more configurations received from the BS. The one or more configurations may be included in a Radio Resource Control (RRC) message (e.g., RRC Reconfiguration message).

[0222] Multi-modal Data may be defined to describe the input data from different kinds of devices / sensors or the output data to different kinds of destinations (e.g. one or more UEs) required for the same task or application. Multi-modal Data consists of more than one Single-modal Data, and there is strong dependency among each Single-modal Data. Single-modal Data can be seen as one type of data.

[0223] Data Burst may be a set of multiple PDUs generated and sent by the application in a short period of time. A Data Burst may be composed by one or multiple PDU Sets.

[0224] PDU Set may be composed of one or more PDUs carrying the payload of one unit of information generated at the application level (e.g., a frame or video slice for XR Services). In some example embodiments all PDUs in a PDU Set are needed by the application layer to use the corresponding unit of information. In other implementations, the application layer may still recover parts all or of the information unit, when some PDUs are missing.

[0225] PDU Set Error Rate (PSER) may define an upper bound for a rate of non-congestion related PDU Set losses between RAN and the UE. A PDU set may be considered as successfully delivered only when all PDUs of a PDU Set are delivered successfully, and if the PSER is available, the usage of PSER supersedes the usage of PER.

[0226] PDU Set Delay Budget (PSDB) may define time between reception of the first PDU (at the UPF in DL, at the UE in UL) and the successful delivery of the last arrived PDU of a PDU Set (at the UE in DL, at the UPF in UL). PSDB may be an optional parameter and when provided, the PSDB supersedes the PDB.

[0227] PDU Set Integrated Handling Indication (PSIHI) may indicate whether all PDUs of the PDU Set are needed for the usage of PDU Set by application layer.

[0228] PDU Set Importance (PSI) may identify the relative importance of a PDU Set compared to other PDU Sets within a QoS Flow. RAN may use it for PDU Set level packet discarding in presence of congestion.

[0229] Extended Reality (XR) may be referred to real-and-virtual combined environments and humanmachine interactions generated by computer technology and wearables. XR may be an umbrella term for different types of realities:Virtual reality (VR) may be a rendered version of a delivered visual and audio scene. The rendering may be designed to mimic the visual and audio sensory stimuli of the real world as naturally as possible to an observer or user as they move within the limits defined by the application. Virtual reality usually, but not necessarily, requires a user to wear a head mounted display (HMD), to completely replace the user's field of view with a simulated visual component, and to wear headphones, to provide the user with the accompanying audio. Some form of head and motion tracking of the user in VR is usually also necessary toDocket No.: 24-1263PCT allow the simulated visual and audio components to be updated in order to ensure that, from the user's perspective, items and sound sources remain consistent with the user's movements.Augmented reality (AR) may be when a user is provided with additional information or artificially generated items or content overlaid upon their current environment. Such additional information or content will usually be visual and / or audible and their observation of their current environment may be direct, with no intermediate sensing, processing and rendering, or indirect, where their perception of their environment is relayed via sensors and may be enhanced or processed.Mixed reality (MR) may be an advanced form of AR where some virtual elements are inserted into the physical scene with the intent to provide the illusion that these elements are part of the real scene.

[0230] The present application may use the acronym XR throughout to refer to equipment, applications and functions used for VR, AR and MR. Examples include, but are not limited to HMDs for VR, optical see- through glasses and camera see-through HMDs for AR and MR and mobile devices with positional tracking and camera. They may offer some degree of spatial tracking and the spatial tracking results in an interaction to view some form of virtual content.

[0231] Many of the XR use cases may be characterised by quasi-periodic traffic (with possible jitter) with high data rate in DL (i.e. , video steam) combined with the frequent UL (i.e., pose / control update) and / or UL video stream. Both DL and UL traffic are also characterized by relatively strict packet delay budget (PDB). Hence, there is a need to study and potentially specify possible solutions to better support such challenging services, i.e., by better matching the non-integer periodicity of traffic, such as 60 / 90 / 120 frames per second to the NR signalling.

[0232] Many of the end user XR devices are expected to be mobile and of small-scale, thus having limited battery power resources. Therefore, additional power enhancements may be needed to reduce the overall UE power consumption when running XR services and thus extend the effective UE battery lifetime. From the Release 17 Study Item on "XR evaluations” it is identified that the current DRX configurations do not fit well for (I) the non-integer XR traffic periodicity, (ii) variable XR data rate and (Hi) quasi-periodic XR periodicity, hence enhancements would be beneficial in this area.

[0233] The set of anticipated XR services has a certain variety and characteristics of the data streams (e.g , video) may change “on-the-fly”, while the services are running over NR Therefore, additional information on the running services from higher layers may be beneficial to facilitate informed choices of radio parameters.

[0234] The Table 1 shows the XR traffics characteristics:Table 1Docket No.: 24-1263PCT

[0235] XR content may be represented in different formats, e.g. panoramas or spheres depending on the capabilities of the capture systems. Since modern video coding standards are not designed to handle spherical content, projection is used for conversion of a spherical (or 360°) video into a two-dimensional rectangular video before the encoding stage. After projection, the obtained two-dimensional rectangular image can be partitioned into regions (e.g. front, right, left, back, top, bottom) that can be rearranged to generate "packed" frames to increase coding efficiency or viewport dependent stream arrangement.

[0236] The frame rate for XR video varies from 15 frames per second up to 90 or even 120 frames per second, with a typical minimum of 60 for VR. The latency of action of the angular or rotational vestibuloocular reflex is known to be of the order of 10 ms or in a range from 7-15 milliseconds and it seems reasonable that this should represent a performance goal for XR systems. This results in a motion-to- photon latency of less than 20 milliseconds, with 10ms being given as a goal. Regarding the bit rates, between 10 and 200Mbps can be expected for XR depending on frame rate, resolution and codec efficiency.

[0237] For Audio, it can be distinguished as channel-based and object-based representations: Channel-based representation using multiple microphones to capture sounds from different directions and post-processing techniques are well known in the industry, as they have been the standard for decades.Object-based representations represent a complex auditory scene as a collection of single audio elements, each comprising an audio waveform and a set of associated parameters or metadata. The metadata embody the artistic intent by specifying the transformation of each of the audio elements to playback by the final reproduction system. Sound objects generally use monophonic audio tracks that have been recorded or synthesized through a process of sound design. These sound elements can be further manipulated, so as to be positioned in a horizontal plane around the listener, or in full three-dimensional space using positional metadata.

[0238] Due to the relatively slower speed of sound compared to that of light, it is natural that users are more accustomed to, and therefore tolerant of, sound being relatively delayed with respect to the videoDocket No.: 24-1263PCT component than sound being relatively in advance of the video component Recent studies have led to recommendations of an accuracy of between 15 ms (audio delayed) and 5 ms (audio advanced) for the synchronization, with recommended absolute limits of 60 ms (audio delayed) and 40 ms (audio advanced) for broadcast video.

[0239] To maintain a reliable registration of the virtual world with the real world, as well as to ensure accurate tracking of the XR Viewer pose, XR applications require highly accurate, low-latency tracking of the device at about 1 kHz sampling frequency. The size of a XR Viewer Pose associated to time, typically results in packets of size in the range of 30-100 bytes, such that the generated data is around several hundred kbit / s if delivered over the network with latency requirements in the range of 10-20ms.

[0240] Repeatedly providing the XR Viewer Pose for the same display time may not necessarily return the same result (the prediction gets increasingly accurate as the information is closer to the time when a prediction is made) and there is a trade-off between providing several XR Viewer Pose for a display time and using the same XR Viewer Pose for several consecutive display times. However, it can be assumed that sending one XR Viewer Pose aligned with the frame rate of the rendered video may be sufficient, for example at 60fps.

[0241] Pose information has to be delivered with ultra-high reliability, therefore, similar performance as URLLC is expected, e.g., packet loss rate may be lower than 10E-4 for uplink sensor data.

[0242] XR-Awareness relies on QoS flows, PDU Sets, Data Bursts and traffic assistance information. PDU Set QoS Parameters may be provided by the SMF to the gNB as part of the QoS profile of the QoS flow:PDU Set Delay Budget (PSDB): upper bound for the duration between the reception time of the first PDU (at the UPF for DL, at the UE for UL) and the time when all PDUs of a PDU Set have been successfully received (at the UE in DL, at the UPF in UL). A QoS Flow is associated with only one PSDB, and when available, it applies to both DL and UL and supersedes the PDB of the QoS flow.PDU Set Error Rate (PSER): upper bound for a rate of non-congestion related PDU Set losses between RAN and the UE. A QoS Flow is associated with only one PSER, and when available, it applies to both DL and UL and supersedes the PER of the QoS flow.A PDU set may be considered as successfully delivered only when all PDUs of a PDU Set are delivered successfully.PDU Set Integrated Handling Information (PSIHI): indicates whether all PDUs of the PDU Set are needed for the usage of PDU Set by application layer.

[0243] The PDU Set QoS parameters may be common for all PDU Sets within a QoS flow.

[0244] UPF may identify PDUs that belong to PDU Sets, and may determine the following PDU Set Information which it sends to the gNB in the General Packet Radio System (GPRS) Tunnelling Protocol User Plane (GTP-U) header:PDU Set Sequence Number;Docket No.: 24-1263PCTIndication of End PDU of the PDU Set;PDU Sequence Number within a PDU Set;PDU Set Size in bytes;PDU Set Importance (PSI), which identifies the relative importance of a PDU Set compared to other PDU Sets within the same QoS Flow.

[0245] The following traffic assistance information may be provided by 5GC to the gNB:Via Time Sensitive Communication Assistance Indication (TSCAI):UL and / or DL Periodicity;N6 Jitter Information associated with the DL Periodicity.Indication of End of Data Burst in the GPRS Tunnelling Protocol-User Plan (GTP-U) header of the last PDU in downlink.

[0246] In the uplink, the UE may need to be able to identify PDU Sets and Data Bursts dynamically, including PSI.

[0247] When a certain number of PDUs of a PDU Set are known to be required by the application layer to use the corresponding unit of information (for instance due to the absence or limitations of error concealment techniques, the PSIHI is set for a QoS flow, as soon as the number of one PDUs of a PDU set is known to be lost exceeds this number, the remaining PDUs of that PDU Set may be considered as no longer needed by the application and may be subject to discard operation of data.

[0248] Most XR video frame rates (15, 30, 45, 60, 72, 90 and 120 fps) may correspond to periodicities that are not an integer (66.66, 33.33, 22.22, 16.66, 13.88, 11.11 and 8.33 ms respectively). The gNB may configure a DRX cycle expressed in rational numbers so that the DRX cycle matches those periodicities, e.g., for the traffic with a frame rate of 60 fps, the network may configure the UE with a DRX cycle of 50 / 3 ms.

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

[0250] The following enhancements for configured grant based transmission may be recommended: Support of multiple CG PUSCH transmission occasions within a single period of a CG configurationindication of unused CG PUSCH occasion(s) of a CG configuration with Uplink Control;Information multiplexed in CG PUSCH transmission of the CG configuration.

[0251] In order to enhance the scheduling of uplink resources for XR, the following improvements are introduced:One additional buffer size table to reduce the quantisation errors in BSR reporting (e.g. for high bit rates):Whether, for an LCG, the new table can be used in addition to the regular one is configured by the gNB;Docket No.: 24-1263PCTWhen the new table is configured for an LCG, it is used whenever the amount of the buffered data of that LCG is within the range of the new table, otherwise the regular table is used.Delay Status Report (DSR) of buffered data via a dedicated MAC CE:T riggered for an LCG when the remaining time before discard of any buffered PDCP SDU goes below a configured threshold (threshold configured per LCG by the gNB);When triggered for an LCG, reports the amount of data buffered with a remaining time before discard below the configured threshold, together with the shortest remaining time of any PDCP SDU buffered.Reporting of uplink assistance information (jitter range, burst arrival time, UL data burst periodicity) per QoS flow by the UE via UE Assistance Information.

[0252] When the PSIHI is set for a QoS flow, as soon as one PDU of a PDU set is known to be lost, the remaining PDUs of that PDU Set can be considered as no longer needed by the application and may be subject to discard operation at the transmitter to free up radio resources. In uplink, the UE may be configured with PDU Set based discard operation for a specific DRB. When configured, the UE discards all packets in a PDU set when one PDU belonging to this PDU set is discarded, e.g. based on discard timer expiry. In case of congestion, the PSI may be used for PDU set discarding. In uplink, dedicated signalling is used to trigger discard mechanism based on PSI. How SDUs are identified as low importance may be determined by UE. When a PDU Set Importance (PSI) is available, it may be used to classify the PDCP SDUs of a PDU Set.

[0253] The network activates and deactivates PSI-based SDU discard by sending the PSI-Based SDU Discard Activation / Deactivation MAC CE. The PSI-based SDU discard is initially deactivated upon (reconfiguration by upper layers and after reconfiguration with sync.

[0254] The MAC entity shall for each DRB configured with PSI-based SDU discard:1 > if a PSI-Based SDU Discard Activation / Deactivation MAC CE is received activating the PSI- based SDU discard for the DRB: indicate the activation of the PSI-based SDU discard for the DRB to upper layers;1 > if a PSI-Based SDU Discard Activation / Deactivation MAC CE is received deactivating the PSI- based SDU discard for the DRB: indicate the deactivation of the PSI-based SDU discard for the DRB to upper layers.

[0255] The PSI-Based SDU Discard Activation / Deactivation MAC CE may be identified by MAC subheader with an one-octet eLCID. It has a fixed size and consists of one octet defined as follows: Di: This field may indicate the activation / deactivation status of the PSI-based SDU discard of DRB i, where i is the ascending order of the DRB ID among the DRBs configured with PSI-based SDU discard. The Di field set to 1 indicates that the PSI-based SDU discard shall be activated for DRB i. The Di field set to 0 indicates that the PSI-based SDU discard shall be deactivated for DRB i.Docket No.: 24-1263PCT

[0256] Multi-modal Data may be defined to describe the input data from different kinds of devices / sensors or the output data to different kinds of destinations (e.g. one or more UEs) required for the same task or application. Multi-modal Data consists of more than one Single-modal Data, and there is strong dependency among each Single-modal Data. Single-modal Data can be seen as one type of data.

[0257] Tactile and multi-modal communication services enable multi-modal interactions, combining ultralow latency with extremely high availability, reliability and security. Tactile Internet can be applied in multiple fields, including: industry, robotics and telepresence, virtual reality, augmented reality, healthcare, road traffic, serious gaming, education and culture, smart grid, etc.

[0258] Multiple modalities can be used in combination in a service to provide complementary methods that may convey redundant information but can convey information more effectively. With the benefit of combining input from more than one source and / or output to more than one destination, interpretation in communication services will be more accurate and faster, response can also be quicker, and the communication service will be smoother and more natural.

[0259] For a typical tactile and multi-modal communication service / application, there can be different modalities affecting the user experience, e g.:Video / Audio media;Information perceived by sensors about the environment, e.g. brightness, temperature, humidity, etc.;Haptic data: can be feelings when touching a surface (e.g , pressure, texture, vibration, temperature), or kinaesthetic senses (e.g. gravity, pull forces, sense of position awareness).

[0260] Multiple modalities can be transmitted at the same time to multiple application servers for further processing in a coordinated manner, in terms of QoS coordination, traffic synchronization, power saving, etc.Multiple outcomes may be generated as the feedback. In the scenario of real time remote virtual reality service, a VR user may use a plurality of independent devices to separately collect video, audio, ambient and haptic data from the person and to receive video, audio, ambient and haptic feedback from one or multiple application servers for a same VR application. In this case, an end user could wear VR glasses to receive images and sounds, and a touch glove to receive a touch sensation, a camera to collect video inputs, a microphone to collect audio inputs, multiple wearable sensors to provide haptic information and environmental information associated to the user. The real time remote virtual reality service can also be conducted between two users.Multiple outcomes may need to reach the distributed UEs at the very same time. In the scenario of sound field reappearing, different channels of sounds are sent to the distributed sound boxes to simulate the sound from a particular direction. A small time difference may cause big direction error to impact user experience. In some cases, time difference of 1 ms may cause more than 30° angle error.Docket No.: 24-1263PCTMulti-modal applications may involve a big number of UEs at a long distance. In the scenario of multi-modal telepresence, tens of UEs may need synchronization for time, control signal and visual signal.

[0261] In another scenario, the devices associated to the same tactile and multi-modal communication service may be triggered to wake up by the discovery of a tactile and multi-modality capable user / UE in proximity. And a different group of tactile and multi-modality capable devices can serve the user as he moves. Other scenarios that can be investigated are industrial manufacturing and drones' real-time applications, which require synchronous control of visual-haptic feedback.

[0262] Multi-modal outputs may be generated based on the inputs from multiple sources. In the multimodal interactive system, modality is a type or representation of information in a specific interactive system. Multi-modal interaction is the process during which information of multiple modalities are exchanged. Modal types consist of motion, sentiment, gesture, etc. Modal representations consist of video, audio, tactition (vibrations or other movements which provide haptic or tactile feelings to a person), etc.

[0263] A multi-modal service is a communication service that consists of several data flows that relate to each other and that are subject to application coordination. The data flows can transfer different types of data (for example audio, video, positioning, haptic data) and may come from different sources (e.g a single UE, a single device or multiple devices connected txwxwo the single UE, or multiple UEs).

[0264] For the single UE case, it is expected that those data flows are closely related and require strong application coordination for the proper execution of the multi-modal application and therefore, all those data flows are transmitted in a single PDU session. xww

[0265] The Nnef_AFsessionWithQoS service allows the Application Function (AF) to provide, at the same time, for each data flow that belongs to the multi-modal service, a Multi-modal Service ID, the service requirements and the QoS monitoring requirements:The Multi-modal Service ID is an explicit indication that data flows are related to a multi-modal service. The Policy Control Function (PCF) may use this information to derive the correct PCC rules and to apply appropriate QoS policies for the data flows that are part of a specific multi-modal application.The AF may provide QoS monitoring requirements for data flows associated to a multi-modal service to the PCF. The PCF generates the authorized QoS Monitoring policy for each data flow.

[0266] A synchronization threshold can be defined as the maximum tolerable temporal separation of the onset of two stimuli, one of which is presented to one sense and the other to another sense, such that the accompanying sensory objects are perceived as being synchronous. The delay between two or more media components should be less than the certain latency KPI.The audio-video synchronization requirements: in the range of [125ms-5ms] for audio delayed and in the range of [45ms-5ms] for audio advanced.Docket No.: 24-1263PCT

[0267] In other words, it can be interpreted as the maximum tolerable delay between data units from different QoS flows, since each stimuli (e.g., video, audio, or tactile data) is associated with different QoS flows with different QoS flow requirements and companies may think that QoS flow level support would be sufficient for multi-modal traffic.

[0268] The 3GPP XR work item aims for enhancements addressing system capacity, efficient and effective mechanisms to meet QoS requirements and lower device power consumption, in the context of the demanding scenarios and traffic characteristics requirements of XR, including also multi-modal applications.

[0269] The 3GPP XR work item aims to facilitate efficient and effective support for XR application with Multiple QoS flows with multi-modal inter-dependencies, meeting multi-modal QoS requirements, e.g. synchronization and / or coordination, see also TR 22.847, TR 23.700 60. Efficiency enhancements are expected to be visible in terms of capacity or power consumption. Related Potential Impacts has been proposed as follows: a) Enhanced RAN Awareness, by signaling from Core Network and / or indication by UE, b) Enhancements User Plane, e.g. Scheduling, LCP, Resource allocation, Discard, c) Support for multiple DRX configurations, without the potentially problematic restrictions of Pre-Rel-19 2nd DRX.

[0270] The 3GPP XR work item aims to realize system capacity gains by enabling transmission / reception in gaps / restrictions that are caused by RRM measurements, while keeping impact to mobility performance limited.

[0271] The 3GPP XR work item aims to facilitate efficient and effective support of scheduling to enable high system capacity, e.g. by relaxing time constraints for resource allocation as far as possible, while meeting delay requirements / avoiding too late PDUs. Related Potential Impacts has been proposed as follows: a) by UE LCP prioritization, rate enforcement / starvation avoidance b) UE BSR / DSR enhancements for better gNB awareness c) Awareness of application buffering working point d) Other UE MAC enhancements based on awareness of delay and / or deadline.

[0272] RLC-AM is useful to limit data loss, however RLC-AM feedback or retransmission triggering mechanisms are not well adapted for short packet delay budgets applicable to XR traffic. Also, for RLC AM, considerable amounts of data may be in-flight, i.e. in the window, and there is no current way to avoid retransmitting this data, even if the data is old.

[0273] At least one of the following alternatives or combinations may be used for triggering / enabling / disabling by network signaling to enable / disable / skip Tx / Rx in gaps / restrictions that are caused by Radio resource management (RRM) measurements.

[0274] Alt 1 : Dynamic indication (e.g., DCI) to enable Tx / Rx in particular gap(s) / restriction(s) that are caused by RRM measurements

[0275] Alt 1-1 : Explicit indication by DCI to skip a particular gap(s) / restriction(s); Indication may be included as part of scheduling DCI. Bit-field size may be one bit; The bit in the indication (DCI) may be usedDocket No.: 24-1263PCT to indicate whether to skip the first gap / restriction occasion after a minimum time offset required between the last symbol of the PDCCH carrying the DCI format and the start time unit of corresponding skipped gap / restriction occasion indicated by the DCI. Bit equal to 1 may indicate the corresponding gap / restriction occasion is to be "skipped”. When bit equal to 0, UE may ignore the indication of this field in the DCI. Once a gap / restriction is indicated to be “skipped” by a indication / DCI, UE may assume the gap / restriction is skipped irrespective of indication by a later DCI for the same gap / restriction. Bit-field size may be >1 bit; Minimum time offset(s) may be between the end of [the first / the last] received dynamic indication (e.g., DCI) and start time unit of corresponding gap(s) / restriction(s) occasion that is going to be skipped. At least for self-scheduling case, for explicit indication by DCI to skip a particular gap / restriction, one bit indication may be included as part of DCI formats 0_1 / 1_1 and 0_2 / 1_2. In case of cross carrier scheduling, for explicit indication by DCI to skip a particular gap / restriction, one bit indication included as a part of DCI formats 0_1 / 1_1 and 0_2 / 1 _2 may correspond to a scheduled cell. Explicit indication may be configu red / enabled / d isabled for each DCI format individually by one or more configuration parameters.

[0276] Alt 1-2: Explicit indication by DCI to indicate a time window where to skip a particular gap(s) / restriction(s); Minimum time offset between the end of received dynamic indication (e.g., DCI) and start time unit of RRM gap(s) / restriction(s) occasion in time window that is going to be skipped may be introduced.

[0277] Alt 1-3: Implicit indication by DCI scheduling a transmission / reception overlapping with a gap(s) / restriction(s) to skip the gap(s) / restriction (s) ; Minimum time offset between the end of received dynamic indication and start time unit of gap(s) / restriction(s) occasion that is going to be skipped may be introduced.

[0278] Alt 2: Semi-persistent indication to deactivate and / or re-activate one or more of gaps / restrictions that are caused by RRM measurements and to enable Tx / Rx during the deactivated gaps / restrictions that are caused by RRM measurements.

[0279] Alt 3: Semi-static indication to enable / disable / skip TX / RX in gaps / restrictions that are caused by RRM measurements.

[0280] Alt 3-1 : Configure one or more pattern(s) via one or more RRC messages to indicate occasions where to skip gaps / restrictions. Pattern may be based on periodicity, offset and duration; Pattern may be based on a bitmap; Pattern may be applied to all or subset of gap(s) / restriction(s).

[0281] Alt 3-2: Gaps / restrictions that are caused by RRM measurements may be skipped if collided with particular semi-statically pre-configured Tx / Rx occasions.

[0282] Alt 3-3: Gaps / restrictions that are caused by RRM measurements may be skipped based on semi- statically configured priority information for particular semi-statically pre-configured Tx / Rx and / or particular gaps / restrictions.

[0283] UE may receive one or more configuration parameters for measurements, from BS, for:Docket No.: 24-1263PCT multiple SSB-based RRM Measurement Timing Configurations (SMTCs) in parallel per carrier and for a given set of cells depending on UE capabilities; measurement gaps based on multiple SMTCs; assistance information (e.g., ephemeris, Common TA parameters) provided in SIB19 for UE to perform measurement on neighbour cells in RRC_IDLE / RRC_INACTIVE / RRC_CONNECTED.

[0284] BS-controlled adjustment of SMTCs may be based on UE assistance information reported in RRC_CONNECTED. A UE in RRCJDLE / RRC J N ACTIVE can adjust SMTCs based on its location and assistance information in SIB19.

[0285] UE assistance information may consist of the service link propagation delay difference(s) between serving the cell and neighbour cell(s) .

[0286] For a UE in idle / inactive mode, it is up to UE implementation whether to perform NTN neighbour cell measurements on a cell indicated in SIB3 / SIB4 but not included in SIB19.

[0287] For a UE in connected mode, it is up to UE implementation whether to perform NTN neighbour cell measurements on a cell included in the measurement configuration, but without corresponding satellite information in measurement configuration or in SIB19.

[0288] UE may perform time-based and location-based measurements on neighbour cells in RRCJDLE / RRCJNACTIVE:The timing and location information associated to the serving cell is provided in SIB19;Timing information refers to the UTC time when the serving cell stops serving the current geographical area;Location information refers:In the quasi-Earth fixed cell scenario, to the reference location of the serving cell and a distance threshold to the reference location.In the Earth moving cell scenario, to the reference location of the serving cell at the epoch time and a distance threshold to the reference location.

[0289] The time-based measurement initiation may be applicable for the feeder link switchover case for cell (re)selection.

[0290] Measurement rules for cell re-selection may be based on timing information and location information.

[0291] The network may configure an RRC_CONNECTED UE to perform measurements. The network may configure the UE to report them in accordance with the measurement configuration and / or perform conditional reconfiguration evaluation in accordance with the conditional reconfiguration. The measurement configuration is provided by means of dedicated signalling e.g., using the RRCReconfiguration or RRCResume.

[0292] The network may configure the UE to perform the following types of measurements:Docket No.: 24-1263PCTNR measurements;Inter-RAT measurements of E-UTRA frequencies;Inter-RAT measurements of UTRA-FDD frequencies;NR sidelink measurements of L2 U2N Relay UEs.

[0293] The network may configure the UE to report the following measurement information based on SS / PBCH block(s):Measurement results per SS / PBCH block;Measurement results per cell based on SS / PBCH block(s);SS / PBCH block(s) indexes.

[0294] The network may configure the UE to report the following measurement information based on CSI- RS resources:Measurement results per CSI-RS resource;Measurement results per cell based on CSI-RS resource(s);CSI-RS resource measurement identifiers.The network may configure the UE to perform the following types of measurements for NR sidelink and V2X sidelink:CBR measurements.

[0295] The network may configure the UE to report the following CLI measurement information based on SRS resources:Measurement results per SRS resource;SRS resource(s) indexes.

[0296] The network may configure the UE to report the following CLI measurement information based on CLI-RSSI resources:Measurement results per CLI-RSSI resource;CLI-RSSI resource(s) indexes.

[0297] The network may configure the UE to report the following Rx-Tx time difference measurement information based on CSI-RS for tracking or PRS:UE Rx-Tx time difference measurement result.

[0298] The measurement configuration may include the following parameters:Measurement objects: A list of objects on which the UE shall perform the measurements.Reporting configurations: A list of reporting configurations where there can be one or multipleMeasurement identities: For measurement reporting, a list of measurement identities where each measurement identity links one measurement object with one reporting configuration.Quantity configurations: The quantity configuration defines the measurement filtering configuration used for all event evaluation and related reporting, and for periodical reporting of that measurement.Docket No.: 24-1263PCTMeasurement gaps: Periods that the UE may use to perform measurements.Effective measurement window: Periods that the UE may use to perform inter RAT measurements.

[0299] An RRC_CONNECTED UE may derive cell measurement results by measuring one or multiple beams associated per cell as configured by the network. For all cell measurement results, except for RSSI, and CLI measurement results in RRC_CONNECTED, the UE may apply the layer 3 filtering before using the measured results for evaluation of reporting criteria, measurement reporting or the criteria to trigger conditional reconfiguration execution.

[0300] For cell measurements, the network can configure RSRP, RSRQ, SINR, RSCP or EcNO as trigger quantity. For CLI measurements, the network can configure SRS-RSRP or CLI-RSSI as trigger quantity. For cell and beam measurements, reporting quantities can be any combination of quantities (i.e. only RSRP; only RSRQ; only SINR; RSRP and RSRQ; RSRP and SINR; RSRQ and SINR; RSRP, RSRQ and SINR; only RSCP; only EcNO; RSCP and EcNO), irrespective of the trigger quantity, and for CLI measurements, reporting quantities can be either SRS-RSRP or CLI-RSSI. For conditional reconfiguration execution, the network can configure up to 2 quantities, both using same RS type. The UE does not apply the layer 3 filtering to derive the CBR measurements. The UE does not apply the layer 3 filtering as to derive the Rx-Tx time difference measurements. The UE does not apply the layer 3 filtering to derive the altitude measurements.

[0301] The network may also configure the UE to report measurement information per beam (which can either be measurement results per beam with respective beam identifier(s) or only beam identifier(s)). If beam measurement information is configured to be included in measurement reports, the UE may apply the layer 3 beam filtering. On the other hand, the exact L1 filtering of beam measurements used to derive cell measurement results may be implementation dependent.

[0302] The network may configure the UE in RRC_CONNECTED to derive RSRP, RSRQ and SINR measurement results per cell associated to NR measurement objects based on parameters configured in the measObject (e.g. maximum number of beams to be averaged and beam consolidation thresholds) and in the reportConfig (rsType to be measured, SS / PBCH block or CSI-RS).

[0303] The network may configure the UE in RRCJDLE or in RRCJNACTIVE to derive RSRP and RSRQ measurement results per cell associated to NR carriers based on parameters configured in measIdleCarrierListNR within VarMeasIdleConfig for measurements performed.

[0304] UE may receive an IE MeasGapConfig may comprise one or more measurement gap configurations and controls setup / release of measurement gaps.

[0305] The MeasGapConfig, one or more measurement configurations, and / or one or more measurement gap configurations may comprise one or more of the following configuration parameters: gapAssociationPRS may Indicate that PRS measurement is associated with this measurement gap. The network only includes this field for one per-UE gap or for one per-FR gap. If concurrent gap isDocket No.: 24-1263PCT configured and no gap is configured with this field, the PRS measurement is associated with the gap configured via GapConfig (without suffix), if available. If both per-UE gap and per-FR gap are configured via GapConfig and / or GapConfig-r17, the PRS measurement is always associated with the per-UE gap. gapFRI may indicate measurement gap configuration that applies to FR1 only. In (NG)EN-DC, gapFRI cannot be set up by NR RRC (i.e. only LTE RRC can configure FR1 measurement gap). In NE- DC, gapFRI can only be set up by NR RRC (i.e. LTE RRC cannot configure FR1 gap). In NR-DC, gapFRI can only be set up in the measConfig associated with MCG. gapFRI can not be configured together with gapUE. gapFR2 may indicate measurement gap configuration applies to FR2 only. In (NG)EN-DC or NE- DC, gapFR2 can only be set up by NR RRC (i.e. LTE RRC cannot configure FR2 gap). In NR-DC, gapFR2 can only be set up in the measConfig associated with MCG. gapFR2 cannot be configured together with gapUE.

[0306] The MeasGapConfig, one or more measurement configurations, and / or one or more measurement gap configurations may comprise one or more of the following configuration parameters: gapOffset may indicate the gap offset of the gap pattern with MGRP indicated in the field mgrp. The value range is from 0 to mgrp-1 . If ncsg Ind-r17 is present, this offset value refers to the starting point of VIL1 (the visible interruption length before the ML). gapPriority may indicates the priority of this measurement gap. Value 1 indicates highest priority, value 2 indicates second level priority, and so on gapSharing may indicate the measurement gap sharing scheme that applies to this GapConfig. For applicability of the different gap sharing schemes, see TS 38.133

[0014] , Value schemeOO corresponds to scheme "00", value schemeOl corresponds to scheme "01", and so on.

[0307] The MeasGapConfig, one or more measurement configurations, and / or one or more measurement gap configurations may comprise one or more of the following configuration parameters: gapToAddModList may indicate a list of of measurement gap configuration to be added or modified. If more than one measurement gap is configured (i.e. concurrent measurement gap), the maximum number of configured measurement gap is limited by the gap. In this version of the specification, the network configures this field only in NR standalone. This field is used only for a UE that supports preconfigured measurement gap, concurrent measurement gap, or NCSG. In this version of the specification, the network does not configure concurrent measurement gap together with preconfigured measurement gap for positioning. For the UE not supporting the capability of musim-GapPriorityPreference, the network does not configure concurrent measurement gap together with MUSIM gap. gapToAddModList may indicate a list of of measurement gap configuration to be added or modified. If more than one measurement gap is configured (i.e. concurrent measurement gap), the maximum number of configured measurement gap is limited by the gap combinations. In this version of theDocket No.: 24-1263PCT specification, the network configures this field only in NR standalone. This field is used only for a UE that supports pre-configured measurement gap, concurrent measurement gap, or NCSG. In this version of the specification, the network does not configure concurrent measurement gap together with preconfigured measurement gap for positioning. For the UE not supporting the capability of musim-GapPriorityPreference, the network does not configure concurrent measurement gap together with MUSIM gap. gapToReleaseList may indicate a list of measurement gap configuration to be released.

[0308] The MeasGapConfig, one or more measurement configurations, and / or one or more measurement gap configurations may comprise one or more of the following configuration parameters: gapType may indicates the type of this measurement gap. Value perUE indicates that it is a per UE measurement gap, value perFRI indicates that it is an FR1 measurement gap, and value perFR2 indicates that it is an FR2 measurement gap. gapUE may indicate measurement gap configuration that applies to all frequencies (FR1 and FR2). In (NG)EN-DC, gapUE cannot be set up by NR RRC (i.e. only LTE RRC can configure per UE measurement gap). In NE-DC, gapUE can only be set up by NR RRC (i.e. LTE RRC cannot configure per UE gap). In NR-DC, gapUE can only be set up in the measConfig associated with MCG. If gapUE is configured, then neither gapFRI nor gapFR2 can be configured. measGapId may indicate the ID of this measurement gap configuration. mgl may be the measurement gap length in ms of the measurement gap.Mgrp may indicate the measurement gap repetition period in (ms) of the measurement gap. If ncsg Ind-r17 is present, the mgrp field indicates the Visible Interruption Repetition Period (VIRP) of NCSG pattern and is configured.

[0309] The MeasGapConfig, one or more measurement configurations, and / or one or more measurement gap configurations may comprise one or more of the following configuration parameters: mgta may indicate the measurement gap timing advance in ms. ncsg Ind may indicatee that the measurement gap is a NCSG. posMeasGapPreConfigToAddModList may indicate a list of preconfigured measurement gap for positioning to add and / or modify. posMeasGapPreConfigToReleaseList may inidcate a list of preconfigured measurement gap for positioning to release. preConfig Ind may indicate whether the measurement gap is a pre-configured measurement gap. refFR2ServCellAsyncCA may indicate the FR2 serving cell identifier whose SFN and subframe is used for FR2 gap calculation for this gap pattern with asynchronous CA involving FR2 carrier(s). refServCell Indicator may indicate the serving cell whose SFN and subframe are used for gap calculation for this gap pattern. Value pCell corresponds to the PCell, pSCell corresponds to the PSCell, and mcg-FR2 corresponds to a serving cell on FR2 frequency in MCG.Docket No.: 24-1263PCT

[0310] The IE MeasGapId may used to identify a per UE or per ER measurement gap configuration. The IE MeasGapSharingConfig may indicate the measurement gap sharing scheme and controls setup / release of measurement gap sharing.

[0311] During an activated measurement gap, the UE / MAC entity may, on the Serving Cell(s) in the corresponding frequency range of the measurement gap configured by measGapConfig:1 > not perform the transmission of HARQ feedback, SR, and / or CSI;1 > not report SRS;1 > not transmit on UL-SCH except for Msg3 or the MSGA payload;1 > if the ra-ResponseWindow or the ra-ContentionResolutionTimer or the msgB- ResponseWindow is running, or if there is an ongoing RACH-less LTM cell switch, or if there is an ongoing RACH-less handover:2> monitor the PDCCH as specified in clauses 5.1 .4, 5.1.5, and 5.7.1 > else:2> not monitor the PDCCH;2> not receive on DL-SCH

[0312] If the UE is configured with pre-configured measurement gaps, the network may send DL MAC CE for Positioning Measurement Gap Acti vation / Deactivation Command to the UE. For the activated measurement gap, the UE may follow the specified UE behavior.

[0313] Upon the reception of the MAC CE for Positioning Measurement Gap Acti vation / Deactivation Command, the UE / MAC entity may:1 > if the Positioning Measurement Gap Activation / Deactivation Command MAC CE indicates the deactivation of a pre-configured positioning measurement gap:2> deactivate the positioning measurement gap.1> else if the Positioning Measurement Gap Activation / Deactivation Command MAC CE indicates the activation of a pre-configured measurement gap:2> activate the positioning measurement gap and perform the procedure.

[0314] If the UE is configured with pre-configured positioning measurement gap and the request of the activation / deactivation of the positioning measurement gap by UL MAC CE, the UE may request the network to activate or deactivate the Positioning measurement gap with UL MAC CE for Positioning Measurement Gap Acti vation / Deactivation Request.

[0315] The UE / MAC entity may, when triggered by the upper layer (e.g., RRC) to send Positioning Measurement Gap Activation / Deactivation Request, cancel the triggered Positioning Measurement Gap Activation / Deactivation Request, if any and trigger another Positioning Measurement Gap Activation / Deactivation Request according to the upper layer (e.g., RRC) 's request.

[0316] The UE / MAC entity may,Docket No.: 24-1263PCT1 > if Positioning Measurement Gap Acti vation / Deacti vation Request MAC CE has been triggered, and not cancelled:2> if indication from upper layer (e.g., RRC) has been received that the triggered Positioning Measurement Gap Activation / Deactivation Request MAC CE should be cancelled; or2> if the pre-configured measurement gap indicated in the Positioning Measurement Gap Activation / Deactivation Request MAC CE has already been activated / deactivated:3> cancel the triggered Positioning Measurement Gap Activation / Deactivation Request MAC CE.2> if UL-SCH resources are available for a new transmission and these UL-SCH resources can accommodate the Positioning Measurement Gap Activation / Deactivation Request MAC CE plus its subheader as a result of logical channel prioritization:- 3> instruct the Multiplexing and Assembly procedure to generate the Positioning Measurement Gap Activation / Deactivation Request MAC CE according to the upper layer (e.g., RRC) 's request;- 3> cancel triggered Positioning Measurement Gap Activation / Deactivation Request MAC CE.2> else:- 3> trigger a Scheduling Request for Positioning Measurement Gap Activation / Deactivation Request MAC CE.

[0317] The Positioning Measurement Gap Activation / deactivation request MAC CE may be identified by MAC subheader with eLCID. It may have a fixed 8-bit size defined as follows:Positioning MG ID field may indicate the identifier for the pre-configured positioning measurement gap. The length of the field is 4 bits;A / D field may indicate the activation or deactivation of the Positioning Measurement Gap. The field is set to 1 to indicate activation, otherwise it indicates deactivation. The length of the field is 1 bit;R field may be reserved bit, e.g., set to 0.

[0318] The Positioning Measurement Gap Activation / Deactivation Command MAC CE may be identified by MAC subheader with a eLCID. It may have a fixed 8-bit size defined as follows:Positioning MG ID field may indicate the identifier for the preconfigured positioning measurement gap. The length of the field is 4 bits;A / D field may indicate the activation or deactivation of the Positioning Measurement Gap. The field is set to 1 to indicate activation, otherwise it indicates deactivation. The length of the field is 1 bit;R field may be reserved bit, e.g., set to 0.

[0319] In an aspect, the terms “UE", “wireless device”, “NAS", “AS”, “Application”, “SDAP”, “RRC”, “PDCP”, “RLC”, “MAC”, “PHY” layer / entity may be used interchangeably.Docket No.: 24-1263PCT

[0320] In an aspect, the terms “gNB”, “eNB,” "base station (BS)”, "network (NW)”, “network node (NN)” “NAS”, "AS”, "Application", “SDAP”, “RRC”, "PDCP", “RLC”, "MAC", “PHY” layer / entity may be used interchangeably may be used interchangeably.

[0321] In an aspect, the terms “layer”, “entity”, “sublayer” may be used interchangeably.

[0322] In an aspect, the terms NAS / AS / Application / SDAP / RRC / PDCP / RLC / MAC / PHY layer / entity may be a layer / entity of the UE / wireless device.

[0323] In an aspect, the terms NAS / AS / Application / SDAP / RRC / PDCP / RLC / MAC / PHY layer / entity may be a layer / entity of the base station.

[0324] In an aspect, the upper layer may be one or more of “NAS”, “AS”, “Application”, “SDAP”, “RRC”, “PDCP”, “RLC", “MAC”, “PHY” layer / entity.

[0325] In an aspect, the lower layer may be one or more of “NAS”, “AS”, “Application”, “SDAP”, “RRC”, “PDCP”, “RLC”, “MAC”, “PHY" layer / entity.

[0326] In an aspect, the terms “determine”, “derive”, “detect”, “consider”, “identify”, “indicate” may be used interchangeably.

[0327] In an aspect, the terms “configure”, “indicate”, “send”, “transmit”, “report” “schedule”, “allocate”, “submit” may be used interchangeably.

[0328] In an aspect, the terms “comprise”, “include”, “indicate” may be used interchangeably.

[0329] In an aspect, the terms “indication”, “configuration”, “configuration parameter", “parameter", “RRC message”, “RRC configuration”, “RRC configuration parameter”, “RRC parameter”, “information element (IE)”, “control PDU”, “control element (CE), “MAC CE”, “DCI", “UCI” may be used interchangeably.

[0330] - In an aspect, the UE is configured with a configuration / parameter / IE / RRC message may be referred to as the UE receives the configuration / parameter / IE / RRC message from the BS.

[0331] In an aspect, the terms “enable”, “activate”, “initialize”, “eligible”, “allow”, “trigger”, “able”, “presence" may be used interchangeably.

[0332] In an aspect, the terms “disable”, “deactivate", “release”, “disallow”, “cancel”, “not eligible”, “absent" may be used interchangeably.

[0333] In an aspect, the terms “perform”, “apply”, “determine”, “use” may be used interchangeably.

[0334] In an aspect, the terms “construct”, “generate”, “build”, “multiplex” may be used interchangeably.

[0335] In an aspect the terms “not transmitting”, “omitting transmitting”, “refraining from transmitting", “limiting to transmitting", “avoid transmitting” may be used interchangeably.

[0336] In an aspect the terms “not receiving”, “omitting receiving", “refraining from receiving”, “limiting to receiving”, “avoid receiving” may be used interchangeably.

[0337] In an aspect, the terms “setup”, “set to true”, “present”, “configured", “configured with true” may be used interchangeably.Docket No.: 24-1263PCT

[0338] In an aspect, the terms “not configured with true”, “absent", “not configured" may be used interchangeably.

[0339] In an aspect, the terms “ignore”, “not apply", “consider as absent”, “skip”, “cancel, “not apply” may be used interchangeably.

[0340] In an aspect the terms “if', “when”, “after”, “upon”, “in response to”, “based on” may be used interchangeably.

[0341] In an aspect the terms “threshold”, “threshold value”, “threshold parameter” may be used interchangeably.

[0342] In an aspect, the terms “ID”, “index”, “identifier” may be used interchangeably.

[0343] In an aspect, the terms “enhanced”, “extended”, “refined”, “new” may be used interchangeably

[0344] In an aspect, the terms “entry”, “octet”, “8-bits” may be used interchangeably.

[0345] In an aspect, the terms “number”, “quantity” may be used interchangeably.

[0346] In an aspect, the terms “first”, “earliest”, “next”, “subsequent” may be used interchangeably

[0347] In an aspect, the Cell Group may be a Master Cell Group (MCG) and / or a Secondary Cell Group(SCG).

[0348] In an aspect, the Cell may be a PCell, PSCell, SpCell, and / or SCell.The cell may be a FR1 cell and / or a FR2 cell.The cell may be a serving cell and / or a non-serving cell.The cell may be an activated cell and / or a deactivated cell.

[0349] In an aspect, the UL resource may be UL-SCH resource, PUSCH resource, PUCCH resource, and / or PRACH resource.

[0350] In an aspect, the DL resource may be DL-SCH resource, PDSCH resource, PDCCH resource.

[0351] In an aspect, the time unit may be slot / symbol / subframe / system frame / millisecond / second.

[0352] In an aspect, data may be referred to as a data unit, and vice versa.

[0353] The data unit may be an uplink data unit and / or a downlink data unit.

[0354] The data unit may be a SDU, a PDU, a PDU set, an IP packet, and / or a data burst.

[0355] The data unit (e.g., SDU) may be at least one of a SDAP SDU, PDCP SDU, RLC SDU, RLC SDU segment, MAC SDU, PHY SDU, Transport Block (TB).

[0356] The data unit (e.g., PDU) may be at least one of a SDAP PDU, PDCP PDU, control PDU, PDCP control PDU, RLC PDU, RLC data PDU, RLC control PDU, MAC PDU, PHY PDU, Transport Block (TB).

[0357] The RLC PDU may be either RLC data PDU or RLC control PDU.

[0358] The PDU set may comprise one or more PDUs carrying a payload of one unit of information generated at an application level.

[0359] The data burst may be a set of multiple PDUs generated and sent by the application in a short period of time. The data burst may comprise one or multiple PDU Sets.Docket No.: 24-1263PCT

[0360] In an aspect, the terms “total data volume”, “data amount”, “data volume”, “PDCP data volume”, “RLC data volume”, “buffer size" may be used interchangeably.

[0361] In an aspect, the data unit may be a delay-critical data unit (e.g., delay-critical RLC SDU and / or delay-critical PDCP SDU).

[0362] A data unit may be a delay-critical data unit if pdu-SetDiscard is not configured, a PDCP SDU for which the remaining time till discardTimer expiry is less than the remainingTimeThreshold. If pdu- SetDiscard is configured, a PDCP SDU belonging to a PDU Set of which at least one PDCP SDU has the remaining time till discardTimer expiry less than the remainingTimeThreshold.

[0363] A data unit may be a delay-critical PDCP SDU if pdu-SetDiscard is not configured, a PDCP SDU for which the remaining time till discardTimer expiry is less than the remainingTimeThreshold. If pdu- SetDiscard is configured, a PDCP SDU belonging to a PDU Set of which at least one PDCP SDU has the remaining time till discardTimer expiry less than the remainingTimeThreshold.

[0364] A data unit may be a delay-critical RLC SDU if a RLC SDU corresponding to a PDCP PDU indicated as delay-critical by PDCP.

[0365] In an aspect, the data units may not be delay-critical data unit.

[0366] The data units may comprise delay-critical data unit and / or non-delay-critical data unit.

[0367] The remaining time of the non-delay-critical data units does may not be lower than any thresholds.

[0368] The remaining time of the non-delay-critical data units may be higher th an / eq ual to the one or more remaining time thresholds.

[0369] In an aspect, the terms “gap”, “restriction”, “measurement”, “measurement gap”, “measurement restriction", “scheduling restriction", “gap / restriction”, “measurement gap / restriction”, “gap / restriction occasion”, “measurement occasion”, “measurement gap occasion”, “gaps / restrictions that are caused by RRM measurement”, “RRM gaps / restrictions” may be used interchangeably.

[0370] For the measurement gap (MG) configuration, the UE may adjust its radio frequency (RF) to the target frequency band to conduct Radio Resource Management (RRM) measurements. During this period, the UE may refrain from transmitting or receiving certain signals to or from the Base Station (BS) in the serving cell. Accordingly, the BS may choose not to schedule the UE for data transmission or reception within the serving cell during the designated measurement gap period. In scenarios involving Synchronization Signal Block (SSB)-based measurements without measurement gaps, the UE may impose a scheduling restriction that prevents it from transmitting Physical Uplink Control Channel (PUCCH), Physical Uplink Shared Channel (PUSCH), or Sounding Reference Signal (SRS) on SSB symbols identified for measurement. Additionally, the UE is restricted from transmitting on the data symbol preceding and following each consecutive SSB symbol within the Synchronization Signal Measurement Timing Configuration (SMTC) window duration.Docket No.: 24-1263PCT

[0371] The MG configuration may define a periodic pattern, which could be derived from parameters provided via Radio Resource Control (RRC) signaling and may include the following elements:MGL (Measurement Gap Length) may indicates the duration of the measurement gap in milliseconds.MGRP (Measurement Gap Repetition Period) may indicate the interval at which the measurement gap recurs.MGTA (Measurement Gap Timing Advance) may indicate the timing advance for the measurement gap, allowing the UE to assume that the measurement gap begins MGTA milliseconds prior to subframe timing. gapOffset may indicate the slot offset for the measurement gap pattern.

[0372] Based on the MG configuration / parameters, the UE may calculate the System Frame Number (SFN) and subframe number of the first subframe for each measurement gap. Additionally, SS / PBCH block measurement timing configuration (SMTC) may be established through several Information Elements (lEs) within RRC signaling.

[0373] More specifically, the MG configuration / parameters be an activated MG and / or a deactivated MG (e.g., based on a MG activation / deactivation command MAC CE).

[0374] More specifically, the MG configuration / parameters may or may not be configured / used for Positioning.

[0375] In an aspect, one or more UE assistance information / UE capability for (measurement) gaps / restrictions and / or for skipping for the (measurement) gaps / restrictions may comprise at least one of: UE assistance information related to measurement occasions:Information about the maximum number of MGs / SMTC with restrictions that can be skipped within a time period.Information about the patterns of gap(s) / restriction(s) where skipping is feasible or acceptable.The number of needed measurement gaps / SMTC with restrictions within a time period;The maximum number or ratio of MGs / SMT C with restrictions that can be skipped within a time period;The number of required SSBs within a time period;The number of consecutive RRM measurements that can be skipped;The maximum interval between two consecutively reserved gap / restriction occasions for RRM measurements;The patterns of gap(s) / restriction(s) where skipping is feasible or acceptable;UE assistance information related to channel conditions, e.g., RSRP is below / above search threshold (e.g., s-MeasureConfig);UE assistance information related to traffic, e.g., based on PSI (PDU set importance); and / orDocket No.: 24-1263PCTUE assistance information related to UE mobility, e.g.L3 parameters related to mobility, e.g., static or not.

[0376] In an aspect, the “indication", the “dynamic indication”, the “DCI” may be used interchangeably. In an aspect, the indication may be used for a MG skipping. In an aspect, the indication may be an indication for skipping (measurement) gap.

[0377] In an aspect, the indication may be used to enable Tx / Rx in particular gap(s) / restriction(s) that are caused by RRM measurements. In an aspect, the indication may be used to skip a particular gap(s) / restriction(s). In an aspect, the indication may be used to skip all overlapped (or concurrent) gaps / restrictions.

[0378] In an aspect, the indication may comprise one or more bits. A bit in the indication may be used to indicate whether to skip the first gap / restriction occasion after a minimum time offset required between the last symbol of the PDCCH carrying the DCI format and the start time unit of corresponding skipped gap / restriction occasion indicated by the DCI. The bit equal to a first value (e.g., 1) may indicate the corresponding gap / restriction occasion is to be “skipped”. Bit equal to a second value (e.g., 0) may indicate the corresponding gap / restriction occasion is to be “skipped”. The bit equal to a second value (e.g., 0), UE may ignore the indication of this field in the DCI. Once a gap / restriction is indicated to be “skipped” by a indication / DCI, UE may assume the gap / restriction is skipped irrespective of indication by a later DCI for the same gap / restriction.

[0379] In an aspect, the indication may be a scheduling DCI. In an aspect, the indication may be a certain DCI format, e.g., DCI formats 0_1 / 1_1 , DCI formats, 0_2 / 1_2, and / or DCI formats 0_3 / 1_3.

[0380] In an aspect, the indication may or may not schedule data (e.g., on PDSCH / PUSCH).

[0381] In an aspect, the indication may or may not be used for other purposes, e.g., SPS release, SCell dormancy, BWP chance / switch.

[0382] In an aspect, the indication may indicate MG configuration(s) that can or cannot be skipped.

[0383] In an aspect, one or more parameters may be used to configure the indication in All DCI formats supported to include the indication. In an aspect, one or more parameters may be used to configure indication per DCI format supported to include the indication.

[0384] In an aspect, the indication may be transmitted from PHY to MAC layer when the UE / PHY layer receives the indication from BS.

[0385] In an aspect, the time offset and the offset may be used interchangeably.

[0386] In an aspect, the time offset may be minimum time offset(s) between the end of [the first / last / earliest] received dynamic indication (e.g., DCI) and start time unit of corresponding gap(s) / restriction(s) occasion that is going to be skipped.

[0387] In an aspect, the UE may apply an indication after the time offset from receiving the indication. In an aspect, the UE may apply an indication when time offset expires / ends from receiving the indication.Docket No.: 24-1263PCT

[0388] The time offset may start time unit from the first / last symbol / slot of the indication reception

[0389] In an aspect, the time offset may be the specific value(s) for the minimum time offset(s) between the indication to skip (measurement) gap and / or the skipped measurement occasion.

[0390] In an aspect, the (value of) time offset may be larger than (DL) processing time which is applied to scheduling.

[0391] In an aspect, the (value of) time offset may be indicated by an indication for skipping the (measurement) gap. In an aspect, the (value of) time offset may be indicated by a RRC message, a MAC CE, and / or a DCI.

[0392] In an aspect, the (value of) time offset may be a number of time unit (e.g., slot / symbol / subframe / system frame / millisecond / second) before the (measurement) gap

[0393] In an aspect, the (value of) time offset may be based on a field in an indication (e.g., DCI) (e.g., 'Minimum applicable scheduling offset indicator' field).

[0394] In an aspect, the (value of) time offset may be a certain integer (e.g., 0, 1 , 2, 3, 4, 5, etc.).

[0395] In an aspect, when the UE is scheduled with the indication (e.g., DCI format 0_1 , 0_3, 1_1 or 1_3) with a 'Minimum applicable scheduling offset indicator' field in slot n, the UE may determine the KOmin and K2min values, if configured respectively, to be applied, while the previously applied KOmin and / or K2min values are applied until the new values take effect.

[0396] If the indication (e.g., DCI format 0_1 , 0_3, 1_1 or 1_3) in slot n also indicates an active DL (UL) BWP change for a serving cell, the indicated KOmin (K2min) value in the new active DL (UL) BWP, if configured, is applied from the slot indicated by the slot offset value of the time domain resource assignment field in the DCI. Otherwise, change of applied minimum scheduling offset restriction indication carried by DCI in slot n, shall be applied in slot n+X of the scheduling cell.

[0397] The UE may not expect to be scheduled with the indication (e.g., DCI format 0_1 , 0_3, 1_1 or 1_3) with 'Minimum applicable scheduling offset indicator' field indicating another change to KOmin or K2min for the same active BWP of the scheduled cell before slot n+X of the scheduling cell.

[0398] When the UE is configured with a Measurement Gap (MG) and / or Synchronization Signal Measurement Timing Configuration (SMTC) for Radio Resource Management (RRM), the measurement periods may not align with the periodic arrival times of XR packets, which are influenced by the frame generation rate and network delay jitter. RRM measurements, whether for inter-frequency handovers or intra-frequency BWP switching, can restrict XR data transmission, potentially impacting the system's capacity to support XR services. In addition to data transmission and reception, the UE is required to perform RRM measurements. For instance, if the signal quality of the serving cell falls below a specified threshold, the UE initiates measurements of neighboring cells. As part of this process, when the UE is configured to perform RRM measurements at a scheduled time, it must prioritize these measurements over UL and / or DL d transmissions during the measurement interval.Docket No.: 24-1263PCT

[0399] To enhance the system’s capacity for supporting XR services and / or to mitigate restrictions on XR data transmission and reception, a mechanism may be implemented that allows for the dynamic skipping of configured measurement gaps and / or scheduling restrictions.

[0400] Figure 17 provides an example illustrating the concept of skipping measurement gaps. The UE may transmit a UE capability / UE assistance information to the BS, indicating relevant information about the measurement gap(s). For instance, this information may specify whether the UE supports measurement gap skipping and / or outline the types of MG configurations that are compatible.

[0401] The UE may receive one or more configurations (e.g., via RRC message) that enable / disable an indication (e.g., DCI) to skip the (measurement) gap. Additionally, the UE may receive one or more configurations specifying which MG patterns are feasible or infeasible for skipping.

[0402] The BS may also send an indication (e.g., DCI) instructing the UE to skip or not skip one or more measurement gaps. Based on this indication, the received RRC configurations, and / or the UE’s capability / assistance information, the UE can determine whether to skip certain (measurement) gaps.

[0403] FIG. 18 illustrates an example of indication-based (measurement) gap skipping.

[0404] UE may determine the MGs based on MG configurations, defining a periodic MG pattern, comprises one or more parameters. For example:MGL (Measurement Gap Length) may indicates the duration of the MG.MGRP (Measurement Gap Repetition Period) may indicate the interval at which the MG recurs.

[0405] UE may receive an indication (e g., DCI) indicating, e.g., by a bit field, whether to skip a (e.g , the first) (measurement) gap after a time offset. For example:A bit field of the indication set to a first value (e.g., 1) may indicate the (measurement) gap is to be “skipped”.A bit field of the indication set to a second value (e.g., 0) may indicate the (measurement) gap is to be “not skipped”.A bit field of the indication set to a second value (e.g., 0), UE may ignore the bit field in the indication.

[0406] The time offset may be between the last symbol of the PDCCH carrying the indication (e.g., DCI) and the start time unit of corresponding skipped (measurement) gap indicated by the indication.

[0407] In an aspect, the start time unit of the corresponding skipped (measurement) gap may be a first / start time unit (e.g., slot / symbol / subframe / system frame / millisecond / second) of the (measurement) gap.

[0408] In the existing technologies, as shown in FIG. 19, UE may receive an indication (e.g., DCI) for skipping a (measurement) gap. If the indication for skipping the (measurement) gap indicates that the UE should skip the (measurement) gap, the BS may assume that the UE will indeed skip the measurementDocket No.: 24-1263PCT during this period. Consequently, the BS is permitted to schedule UL / DL transmissions during the skipped measurement gap, allowing the UE to transmit or receive data and / or monitoring PDCCH as needed.

[0409] However, the reliability of the indication (e.g., DCI) is not as robust as upper layer signaling (e.g., RRC message), increasing the possibility that the UE might fail to correctly detect the indication for skipping (measurement) gap.

[0410] In the event of a misdetection, where the UE fails to detect / receive the indication for skipping a (measurement) gap, the UE will proceed with its measurement during the measurement gap, rendering it unavailable for scheduling by the BS. In such a scenario, the BS may still attempt to schedule UL / DL transmissions and allocate resources for the UE within the measurement gap since the BS is not aware of the UE missed the indication for skipping (measurement) gap. However, since the UE would not be able to receive these transmissions, the BS would end up wasting power and resources on the unsuccessful scheduling attempt.

[0411] In the present application, several embodiments are proposed for solving, but not limited to, the problems described above.

[0412] In an example embodiment, UE may transmit feedback (e.g., ACK / NACK) in response to receiving an indication (e.g., DCI) for skipping a (measurement) gap, to the BS, to indicate whether the UE successfully received the indication for skipping the (measurement) gap.

[0413] Based on the feedback from the UE, the BS can be aware of the UE receiving the indication for skipping the (measurement) gap or not and determine whether to schedule DL / UL data transmission for the UE during the (measurement) gap without wasting power and resources on the unsuccessful scheduling attempt.

[0414] Embodiments of the present application are related to an approach for solving, but not limited to, the problems described above. These and other features of the present disclosure are described further below

[0415] FIG.20 illustrates an example as per an aspect of an embodiment of the present disclosure.

[0416] UE may receive an indication (e.g., DCI) indicating, e.g., by a bit field, whether to skip a (e.g., the first) (measurement) gap after a time offset. For example:A bit field of the indication set to a first value (e.g., 1) may indicate the (measurement) gap is to be “skipped” .A bit field of the indication set to a second value (e.g., 0) may indicate the (measurement) gap is to be “not skipped”.A bit field of the indication set to a second value (e.g., 0), UE may ignore the bit field in the indication.

[0417] The time offset may be between the last symbol of the PDCCH carrying the indication (e.g., DCI) and the start time unit of corresponding skipped (measurement) gap indicated by the indication.Docket No.: 24-1263PCT

[0418] In an aspect, the start time unit of the corresponding skipped (measurement) gap may be a first / start time unit (e.g., slot / symbol / subframe / system frame / millisecond / second) of the (measurement) gap.

[0419] In some example embodiments, UE may transmit feedback (e.g., ACK / NACK), to the BS, for the indication for skipping the (measurement) gap in response to receiving an indication (e.g., DCI) for skipping the (measurement) gap.

[0420] In an aspect, the indication may be a certain DCI format, e.g., DCI formats 0_1 / 1_1 , DCI formats, 0_2 / 1 _2, and / or DCI formats 0_3 / 1_3.

[0421] In an example, the indication may or may not indicate scheduling (e.g., on PDSCH / PUSCH). In an example, the indication may or may not indicate / schedule DL data reception and / or UL data transmission. In an example, the indication may or may not indicate / schedule PDSCH reception and / or PUSCH transmission.

[0422] In an example, the DCI format for indication for skipping the (measurement) gap may be referred to as a DCI format having associated HARQ-ACK information without scheduling a PDSCH reception.

[0423] In an example, the indication may or may not be used for other purposes, e.g., SPS release, SCell dormancy, BWP chance / switch.

[0424] In an aspect, the feedback may be ACK / NACK. The feedback may be HARQ-ACK / HARQ-NACK.

[0425] In an example, the feedback may be an ACK and / or HARQ-ACK.

[0426] The UE may send the feedback (e.g , ACK and / or HARQ-ACK) to indicate that the UE receives the indication for skipping the (measurement) gap successfully.

[0427] In an example, the feedback may be a NACK and / or HARQ-NACK.

[0428] The UE may send the feedback (e.g., NACK and / or HARQ-NACK) to indicate that the UE receives the indication for skipping the (measurement) gap unsuccessfully.

[0429] The UE may send the feedback (e.g , NACK and / or HARQ-NACK) to indicate that the UE does not receive the indication for skipping the (measurement) gap.

[0430] In an example, if the UE does not receive the indication for skipping the (measurement) gap, the UE may not send the feedback for the indication for skipping the (measurement) gap.

[0431] In an aspect, the UE may determine a HARQ-ACK priority for the feedback based on a priority indicator field of the indication for skipping the (measurement) gap.

[0432] In an aspect, the UE may transmit the feedback on PUCCH and / or PUSCH.

[0433] In an aspect, the UE may receive one or more resources (e.g., on PUCCH / PUSCH) for transmitting the feedback.

[0434] The one or more resources (e.g., on PUCCH / PUSCH) may be indicated by one or more configuration parameters.Docket No.: 24-1263PCT

[0435] The one or more resources (e.g., on PUCCH / PUSCH) may be indicated by the indication for skipping the (measurement) gap.

[0436] In an example, the UE may or may not transmit the feedback if the UE does not receive the one or more resources (e.g., on PUCCH / PUSCH).

[0437] In some example embodiments, UE may transmit feedback (e.g., ACK / NACK), to the BS, for the indication for skipping the (measurement) gap in response to receiving an indication (e.g., DCI) for skipping the (measurement) gap.

[0438] In an example, UE may transmit the feedback (e.g., ACK / NACK) an offset after / from receiving the indication for skipping the (measurement) gap.

[0439] In an example, UE may transmit the feedback (e.g., ACK / NACK) an offset after / from the first / last time unit (e.g., symbol / slot) of a PDCCH providing the indication (e.g., DCI / DCI format) for skipping the (measurement) gap.

[0440] In an example, UE may transmit the feedback (e.g., ACK / NACK) an offset after / from the start / end time unit of a time offset for the indication for skipping the (measurement) gap.

[0441] In an example, UE may transmit the feedback (e.g., ACK / NACK) an offset after / from the first / last time unit (e.g., symbol / slot) of a time offset for the indication for skipping the (measurement) gap.

[0442] Specifically, the time offset may be between the last symbol of the PDCCH carrying the indication (e.g., DCI) and the start time unit of corresponding skipped (measurement) gap indicated by the indication.

[0443] In an example, the UE may generate a HARQ-ACK information bit (e.g., for HARQ-ACK codebook determination) for an indication for skipping the (measurement) gap.

[0444] The HARQ-ACK information bit value may be ACK / NACK.

[0445] The indication may provide pdsch-HARQ-ACK-Codebook = dynamic or pdsch-HARQ-ACK- Codebook-r16.

[0446] In an aspect, the offset may be a number (e.g., N) of time units (e.g., slot / symbol / subframe / system frame / millisecond / second).

[0447] In an example, UE may receive the (value of the) offset by a RRC message, a configuration parameter, a MAC CE, and / or a DCI.

[0448] In an example, UE may receive the (value of the) the offset by the indication for skipping the (measurement) gap.

[0449] For example, a field of the indication for skipping the (measurement) gap may indicate the (value of the) the offset.

[0450] For example, the offset may be based on a field in an indication (e.g., DCI) (e.g., 'Minimum applicable scheduling offset indicator' field).

[0451] In an example, the offset may be larger than (DL) processing time which is applied to scheduling.Docket No.: 24-1263PCT

[0452] In an example, the offset may be smaller / equal to / larger than a time offset for the indication for skipping the (measurement) gap.

[0453] Specifically, the time offset may be between the last symbol of the PDCCH carrying the indication (e.g., DCI) and the start time unit of corresponding skipped (measurement) gap indicated by the indication.

[0454] In an aspect, UE may determine the offset based on a UE capability / UE assistance information.

[0455] In an example, UE may transmit one or more configuration parameter / indications (e.g., UE capability information / UE assistance information) to indicate that the UE supports / prefers / desired / recommended the (value of the) offset.

[0456] In an example, if the indication for skipping the (measurement) gap further indicates an active DL (UL) BWP change (e.g., based on a "Bandwidth part indicator" field of the indication) for a serving cell, the (length / time units of the) offset may be based on the (SCS / granularity of) new active DL (UL) BWP of the serving cell. For example, if the UE receive an indication for skipping the (measurement) gap on a first BWP indicates an active DL (UL) BWP change from the first BWP for a serving cell to a second BWP for the serving cell, the UE may determine the (length / time units of the) offset based on the second BWP for the serving cell.

[0457] In an example, if the indication for skipping the (measurement) gap further indicates an active DL (UL) BWP change (e.g., based on a "Bandwidth part indicator” field of the indication) for a serving cell, the (length / time units of the) offset may be based on the (SCS / granularity of) old DL (UL) BWP. For example, if the UE receive an indication for skipping the (measurement) gap on a first BWP indicates an active DL (UL) BWP change from the first BWP for a serving cell to a second BWP for the serving cell, the UE may determine the (length / time units of the) offset based on the first BWP for the serving cell.

[0458] In an example, if the indication for skipping the (measurement) gap further indicates cross-carrier scheduling (e.g., based on a "Carrier indicator" field of the indication), the (length / time units of the) offset may be based on the (SCS / granularity of) scheduled cell. For example, if the UE receive an indication for skipping the (measurement) gap on a first cell indicates cross-carrier scheduling (e.g., based on a "Carrier indicator" field of the indication) for a second cell, the UE may determine the (length / time units of the) offset based on the second cell.

[0459] In an example, if the indication for skipping the (measurement) gap further indicates cross-carrier scheduling (e.g., based on a "Carrier indicator" field of the indication), the (length / time units of the) offset may be based on the (SCS / granularity of) scheduling cell. For example, if the UE receive an indication for skipping the (measurement) gap on a first cell indicates cross-carrier scheduling (e.g., based on a "Carrier indicator" field of the indication) for a second cell, the UE may determine the (length / time units of the) offset based on the first cell.

[0460] In Scenario 1, illustrated in FIG. 21 , it is possible for the UE to receive an indication (e.g., DCI) for (measurement gap) skipping within / during a measurement gap (e.g., 1st MG) that has been previouslyDocket No.: 24-1263PCT indicated as skipped. Additionally, the time offset associated with this indication may expire / end within / during the measurement gap (e.g., 1st MG) that was indicated as skipped. In this situation, it is unclear whether the indication applies to the current measurement gap (e.g., 1st MG) or to the next measurement gap (e.g., 2nd MG).

[0461] Similarly, in another scenario shown in FIG. 21 , the UE might receive an indication for measurement gap skipping before the start time unit of a measurement gap (e.g., 1st MG), but the time offset for this indication might expire / end within / during the measurement gap (e.g., 1st MG). Here as well, it is ambiguous whether the indication should apply to the current measurement gap (e.g., 1st MG) or to the subsequent measurement gap (e.g., 2nd MG).

[0462] These ambiguities create a misalignment between the BS and UE regarding which measurement gap to skip, leading to degraded scheduling performance. Such misalignment may cause issues such as unintended interruptions in data transmission or inefficient resource allocation.

[0463] In the present application, several embodiments are proposed for solving but not limited to the problems described above.

[0464] In an example embodiment, UE may determine a second / subsequent (measurement) gap of a first (measurement) gap, to be skipped in response to receiving an indication for measurement gap skipping before / within the first (measurement) gap and / or a time offset for the indication expires / ends within the first (measurement) gap.

[0465] In an example embodiment, UE may ignore or may not expect to receive an indication for measurement gap skipping before / within the first (measurement) gap and / or a time offset for the indication expires / ends within the first (measurement) gap.

[0466] In an example embodiment, UE may ignore or may not expect to receive a second indication for measurement gap skipping within a time offset (or before the time offset expires / ends) for a first indication for measurement gap skipping.

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

[0468] UE may receive an indication (e.g., DCI) indicating, e.g., by a bit field, whether to skip a (e.g., the first) (measurement) gap after a time offset. For example:A bit field of the indication set to a first value (e.g., 1) may indicate the (measurement) gap is to be “skipped".A bit field of the indication set to a second value (e.g., 0) may indicate the (measurement) gap is to be “not skipped”.A bit field of the indication set to a second value (e.g., 0), UE may ignore the bit field in the indication.Docket No.: 24-1263PCT

[0469] The time offset may be between the last symbol of the PDCCH carrying the indication (e.g., DCI) and the start time unit of corresponding skipped (measurement) gap indicated by the indication.

[0470] In an aspect, the start time unit of the corresponding skipped (measurement) gap may be a first / start time unit (e.g., slot / symbol / subframe / system frame / millisecond / second) of the (measurement) gap.

[0471] In an example embodiment, UE may determine a second / subsequent (measurement) gap, after a first (measurement) gap, to be skipped in response to receiving an indication for (measurement) gap skipping before / within the first (measurement) gap and / or a time offset for the indication expires / ends within the first (measurement) gap.

[0472] In an example, UE may receive an indication for (measurement gap) skipping before a first (measurement) gap, wherein a time offset for the indication may start from receiving the indication (e.g., the first / last symbol / slot of the indication reception) and / or the time offset for the indication may expire / end within the first (measurement) gap. UE may determine the indication for (measurement gap) skipping is applied for a second / subsequent (measurement) gap. UE may skip the second / subsequent (measurement) gap based on the indication.

[0473] In an example, UE may receive an indication for (measurement gap) skipping within a first (measurement) gap, wherein a time offset for the indication may start from receiving the indication (e.g., the first / last symbol / slot of the indication reception) and / or the time offset for the indication may expire / end within the first (measurement) gap. UE may determine the indication for (measurement gap) skipping is applied for a second / subsequent (measurement) gap, wherein the second / subsequent (measurement) gap is a subsequent (measurement) gap of the first measurement) gap. UE may or may not skip the second / subsequent (measurement) gap based on the indication. Specifically, the first (measurement) may be indicated to be skipped based on another indication for (measurement) gap skipping received before the indication for (measurement gap) skipping.

[0474] In an example, UE may receive an indication for (measurement gap) skipping within a first (measurement) gap, wherein a time offset for the indication may start from receiving the indication (e.g., the first / last symbol / slot of the indication reception) and / or the time offset for the indication may expire / end after the first (measurement) gap and / or before a second / subsequent (measurement) gap. UE may determine the indication for (measurement gap) skipping is applied for a second / subsequent (measurement) gap, wherein the second / subsequent (measurement) gap is a subsequent (measurement) gap of the first measurement) gap. UE may or may not skip the second / subsequent (measurement) gap based on the indication. Specifically, the first (measurement) may be indicated to be skipped based on another indication for (measurement) gap skipping received before the indication for (measurement gap) skipping.Docket No.: 24-1263PCT

[0475] In an example embodiment, UE may ignore or may not expect to receive an indication for measurement gap skipping before / within the first (measurement) gap and / or a time offset for the indication expires / ends within the first (measurement) gap.

[0476] In an example, UE may ignore or may not expect to receive an indication for (measurement gap) skipping before a first (measurement) gap, wherein a time offset for the indication may start from receiving the indication (e.g., the first / last symbol / slot of the indication reception) and / or the time offset for the indication may expire / end within the first (measurement) gap. UE may or may not skip a second / subsequent (measurement) gap based on the indication, wherein the second / subsequent (measurement) gap is a subsequent (measurement) gap of the first measurement) gap.

[0477] In an example, UE may ignore or may not expect to receive an indication for (measurement gap) skipping within a first (measurement) gap, wherein a time offset for the indication may start from receiving the indication (e.g., the first / last symbol / slot of the indication reception) and / or the time offset for the indication may expire / end within the first (measurement) gap. UE may or may not skip a second / subsequent (measurement) gap based on the indication, wherein the second / subsequent (measurement) gap is a subsequent (measurement) gap of the first measurement) gap.

[0478] In an example, UE may ignore or may not expect to receive an indication for (measurement gap) skipping within a first (measurement) gap, wherein a time offset for the indication may start from receiving the indication (e.g., the first / last symbol / slot of the indication reception) and / or the time offset for the indication may expire / end after the first (measurement) gap and / or before a second / subsequent (measurement) gap. UE may or may not skip a second / subsequent (measurement) gap based on the indication, wherein the second / subsequent (measurement) gap is a subsequent (measurement) gap of the first (measurement) gap.

[0479] In an example embodiment, UE may ignore or may not expect to receive a second indication for (measurement) gap skipping within a time offset for a first indication (measurement) gap skipping, wherein the time offset for the first indication may start from receiving the first indication (e.g., the first / last symbol / slot of the first indication reception).

[0480] In an example, UE may receive a first indication for (measurement) gap skipping, wherein a time offset for the first indication may start from receiving the first indication (e.g., the first / last symbol / slot of the indication reception). UE may ignore or may not expect to receive a second indication for (measurement) gap skipping within the time offset for the first indication. After receiving the first indication, the UE may (only) expect to receive a second indication for (measurement)gap skipping after the time offset for the first indication expires / ends.

[0481] In an example embodiment, UE may ignore or may not expect to receive an indication for (measurement) gap skipping in a time unit if the time unit is not at least a time gap / time offset before (a start / end time unit of) a measurement gap.Docket No.: 24-1263PCT

[0482] In an example, UE may ignore or may not expect to receive in a first slot a PDCCH on an active DL BWP that provides a DCI format indicating (measurement) gap skipping, if the first slot is not at least a time gap / time offset (e.g., symbols) before a second slot where is (a start / end time unit of) a measurement gap.

[0483] In an example embodiment, UE may ignore or may not expect to receive an indication for (measurement) gap skipping in a time unit if the time unit is not at least a time gap / time offset after (a start / end time unit of) a measurement gap.

[0484] In an example, UE may ignore or may not expect to receive in a first slot a PDCCH on an active DL BWP that provides a DCI format indicating (measurement) gap skipping, if the first slot is not at least a time gap / time offset (e.g., symbols) after a second slot where is (a start / end time unit of) a measurement gap.

[0485] In an example embodiment, UE may ignore or may not expect to receive a second indication for (measurement) gap skipping in a second time unit if the second time unit is not at least a time gap / time offset after a first time unit, wherein the first time unit may be where the UE receives a first indication (e.g., the first / last symbol / slot of the indication reception).

[0486] In an example embodiment, UE may ignore or may not expect to receive a second indication for (measurement) gap skipping in a second time unit if the second time unit is not at least a time gap / time offset after a first time unit, wherein the first time unit may be where the time offset for the first indication expires / ends.

[0487] In an example, UE may ignore or may not expect to receive in a second slot a PDCCH on an active DL BWP that provides a second DCI format indicating (measurement) gap skipping, if the second slot is not at least a time gap / time offset (e.g., symbols) after a first slot where the UE receives a first DCI format indicating (measurement) gap skipping.

[0488] In an example, UE may ignore or may not expect to receive in a second slot a PDCCH on an active DL BWP that provides a second DCI format indicating (measurement) gap skipping, if the second slot is not at least a time gap / time offset (e.g., symbols) after a first slot where the time offset for a first DCI format indicating (measurement) gap skipping expires / ends.

[0489] In an example embodiment, UE may (only) expect to receive an indication for (measurement) gap skipping between two measurement gap.

[0490] In an example, UE may (only) expect to receive an indication for (measurement) gap skipping after an end time unit of a first measurement gap and before a start time unit of a second measurement gap.

[0491] In an example, UE may (only) expect to receive an indication for (measurement) gap skipping after an end (symbol / slot) of a first measurement gap and before a start (symbol / slot) of a second measurement gap.

[0492] In an example, UE may (only) expect to receive an indication for (measurement) gap skipping, wherein the time offset for the indication expires / ends after an end time unit of a first measurement gap and before a start time unit of a second measurement gap.Docket No.: 24-1263PCT

[0493] In an example, UE may (only) expect to receive an indication for (measurement) gap skipping, wherein the time offset for the indication expires / ends after an end (symbol / slot) of a first measurement gap and before a start (symbol / slot) of a second measurement gap.

[0494] More specifically, the time gap / time offset may be a number of time unit (e.g., slot / symbol / subframe / system frame / millisecond / second)

[0495] More specifically, the time gap / time offset may be indicated by a RRC message, a MAC CE, and / or a DCI.

[0496] More specifically, the time gap / time offset may be indicated by an indication for skipping the (measurement) gap.

[0497] More specifically, the time gap / time offset may be based on a field in an indication (e.g., DCI).

[0498] UE may determine the MGs based on MG configurations, defining a periodic MG pattern, comprises one or more parameters. For example:MGL (Measurement Gap Length) may indicates the duration of the MG.MGRP (Measurement Gap Repetition Period) may indicate the interval at which the MG recurs.

[0499] UE may receive an indication (e g., DCI) indicating, e.g., by a bit field, whether to skip a (e.g , the first / earliest) (measurement) gap after a time offset. For example:A bit field of the indication set to a first value (e.g., 1) may indicate the (measurement) gap is to be “skipped”.A bit field of the indication set to a second value (e.g., 0) may indicate the (measurement) gap is to be “not skipped”.A bit field of the indication set to a second value (e.g., 0), UE may ignore the bit field in the indication.

[0500] The time offset may be between the last symbol of the PDCCH carrying the indication (e.g., DCI) and the start time unit of corresponding skipped (measurement) gap indicated by the indication.

[0501] In an aspect, the start time unit of the corresponding skipped (measurement) gap may be a first / start time unit (e.g., slot / symbol / subframe / system frame / millisecond / second) of the (measurement) gap.

[0502] During an (activated) measurement gap which is skipped (e.g., in response to a MG skipping indication from BS and / or a MG skipping indication from PHY to MAC), the UE / MAC entity may (allowed / eligible to) perform (e.g., on the Serving Cell(s) in the corresponding frequency range of the measurement gap configured by measGapConfig) at least one / more / all of the following: transmission of HARQ feedback; and / or transmission of SR; and / or transmission of CSI; and / or report SRS; and / orDocket No.: 24-1263PCT transmit on UL-SCH (e.g., except for Msg3 or the MSGA payload); and / or receive on DL-SCH; and / or monitor the PDCCH; and / or monitor the PDCCH (e.g., if the ra-ResponseWindow or the ra-ContentionResolutionTimer or the msgB-ResponseWindow is running,); and / or monitor the PDCCH (e.g., if there is an ongoing RACH-less LTM cell switch); and / or monitor the PDCCH (e.g., if there is an ongoing RACH-less handover).

[0503] During an (activated) measurement gap which is skipped (e.g., in response to a MG skipping indication from BS and / or a MG skipping indication from PHY to MAC), the UE / MAC entity may not (allowed / eligible to) perform (e.g., on the Serving Cell(s) in the corresponding frequency range of the measurement gap configured by measGapConfig) at least one / more / all of the following: transmission of HARQ feedback; and / or transmission of SR; and / or transmission of CSI; and / or report SRS; and / or transmit on UL-SCH (e.g., except for Msg3 or the MSGA payload); and / or receive on DL-SCH; and / or monitor the PDCCH; and / or monitor the PDCCH (e.g., if the ra-ResponseWindow or the ra-ContentionResolutionTimer or the msgB-ResponseWindow is running,); and / or monitor the PDCCH (e.g., if there is an ongoing RACH-less LTM cell switch); and / or monitor the PDCCH (e.g., if there is an ongoing RACH-less handover).

[0504] During an (activated) measurement gap which is not skipped (e.g., in response to a MG skipping indication from BS and / or a MG skipping indication from PHY to MAC), the UE / MAC entity may not (allowed / eligible to) perform (e.g., on the Serving Cell(s) in the corresponding frequency range of the measurement gap configured by measGapConfig) at least one / more / all of the following: transmission of HARQ feedback; and / or transmission of SR; and / or transmission of CSI; and / or report SRS; and / or transmit on UL-SCH (e.g., except for Msg3 or the MSGA payload); and / or receive on DL-SCH; and / or monitor the PDCCH; and / or monitor the PDCCH (e.g., if the ra-ResponseWindow or the ra-ContentionResolutionTimer or the msgB-ResponseWindow is running,); and / orDocket No.: 24-1263PCT monitor the PDCCH (e.g., if there is an ongoing RACH-less LTM cell switch); and / or monitor the PDCCH (e.g., if there is an ongoing RACH-less handover).

[0505] During an (activated) measurement gap which is not skipped (e.g., in response to a MG skipping indication from BS and / or a MG skipping indication from PHY to MAC), the UE / MAC entity may (allowed / eligible to) perform (e.g., on the Serving Cell(s) in the corresponding frequency range of the measurement gap configured by measGapConfig) at least one / more / all of the following: transmission of HARQ feedback; and / or transmission of SR; and / or transmission of CSI; and / or report SRS; and / or transmit on UL-SCH (e.g., except for Msg3 or the MSGA payload); and / or receive on DL-SCH; and / or monitor the PDCCH; and / or monitor the PDCCH (e.g., if the ra-ResponseWindow or the ra-ContentionResolutionTimer or the msgB-ResponseWindow is running,); and / or monitor the PDCCH (e.g., if there is an ongoing RACH-less LTM cell switch); and / or monitor the PDCCH (e.g., if there is an ongoing RACH-less handover).

[0506] In an example, if the indication for skipping the (measurement) gap further indicates an active DL (UL) BWP change (e.g., based on a "Bandwidth part indicator" field of the indication) for a serving cell, the (length / time units of the) time offset may be based on the (SCS / granularity of) new active DL (UL) BWP of the serving cell. For example, if the UE receive an indication for skipping the (measurement) gap on a first BWP indicates an active DL (UL) BWP change from the first BWP for a serving cell to a second BWP for the serving cell, the UE may determine the (length / time units of the) time offset based on the second BWP for the serving cell.

[0507] In an example, if the indication for skipping the (measurement) gap further indicates an active DL (UL) BWP change (e.g., based on a "Bandwidth part indicator” field of the indication) for a serving cell, the (length / time units of the) time offset may be based on the (SCS / granularity of) old DL (UL) BWP. For example, if the UE receive an indication for skipping the (measurement) gap on a first BWP indicates an active DL (UL) BWP change from the first BWP for a serving cell to a second BWP for the serving cell, the UE may determine the (length / time units of the) time offset based on the first BWP for the serving cell.

[0508] In an example, if the indication for skipping the (measurement) gap further indicates cross-carrier scheduling (e.g., based on a "Carrier indicator" field of the indication), the (length / time units of the) time offset may be based on the (SCS / granularity of) scheduled cell. For example, if the UE receive an indication for skipping the (measurement) gap on a first cell indicates cross-carrier scheduling (e.g., basedDocket No.: 24-1263PCT on a "Carrier indicator" field of the indication) for a second cell, the UE may determine the (length / time units of the) time offset based on the second cell.

[0509] In an example, if the indication for skipping the (measurement) gap further indicates cross-carrier scheduling (e.g., based on a "Carrier indicator" field of the indication), the (length / time units of the) time offset may be based on the (SCS / granularity of) scheduling cell. For example, if the UE receive an indication for skipping the (measurement) gap on a first cell indicates cross-carrier scheduling (e.g., based on a "Carrier indicator" field of the indication) for a second cell, the UE may determine the (length / time units of the) time offset based on the first cell.

[0510] In some example embodiments, UE may receive one or more configuration / parameter / indication, from a BS, indicating whether an indication for skipping (measurement) gap is enabled / disable (allowed / disallowed).

[0511] In an example, the configuration / parameter / indication indicates a first value to indicate an indication for skipping (measurement) gap is enabled (allowed).

[0512] In an example, the configuration / parameter / indication indicates a second value to indicate an indication for skipping (measurement) gap is disabled (not allowed).

[0513] In some example embodiments, UE may receive one or more configuration / parameter / indication, from a BS, indicating whether feedback (e.g., ACK / NACK) in response to receiving an indication for skipping the (measurement) gap is enabled / disable (allowed / disallowed) to be transmitted by the UE.

[0514] In an example, the configuration / parameter / indication indicates a first value to indicate feedback (e.g., ACK / NACK) in response to receiving an indication for skipping the (measurement) gap is enabled (allowed).

[0515] In an example, the configuration / parameter / indication indicates a second value to indicate feedback (e.g., ACK / NACK) in response to receiving an indication for skipping the (measurement) gap p is disabled (not allowed).

[0516] In some example embodiments, UE may transmit one or more configuration parameter / indications (e.g., UE capability information / UE assistance information) to indicate that the UE supports / prefers / desired / recommended an indication for skipping (measurement) gap.

[0517] In some example embodiments, UE may transmit one or more configuration parameter / indications (e.g., UE capability information / UE assistance information) to indicate that the UE supports / prefers / desired / recommended feedback (e.g., ACK / NACK) in response to receiving an indication for skipping the (measurement) gap.

[0518] In an example embodiment, a DCI format indicating a MG skipping without scheduling PDSCH reception is referred to as a DCI format having associated HARQ-ACK information without scheduling a PDSCH reception.Docket No.: 24-1263PCT

[0519] In an example embodiment, if a UE detects a DCI format (e.g . , DCI format 1_1 or a DCI format 1_3) indicating a MG skipping (without scheduling PDSCH reception) and / or is provided pdsch-HARQ- ACK-Codebook = dynamic or pdsch-HARQ-ACK-Codebook-r16, the UE may generate a HARQ-ACK information bit for a DCI format (e.g., DCI format 1_1 or a DCI format 1_3) indicating a MG skipping (without scheduling PDSCH reception), and / or the HARQ-ACK information bit value is ACK.

[0520] In an example embodiment, a UE may be expected to provide HARQ-ACK information in response to a detection of a DCI format (e.g., DCI format 1_1 or a DCI format 1_3) indicating MG skipping (without scheduling PDSCH reception) after N symbols from the last symbol of a PDCCH providing the DCI format (e.g., DCI format 1_1 or a DCI format 1 _3).

[0521] FIG. 22 illustrates an example as per an aspect of an embodiment of the present disclosure. In an example embodiment, a wireless device may receive one or more measurement gap (MG) configurations indicating a plurality of MGs. The wireless device may receive downlink control information (DCI) indicating MG skipping for a first MG among the plurality of MGs, wherein the DCI does not schedule any physical downlink shared channel (PDSCH) reception. The wireless device may transmit feedback (e..g, HARQ- ACK) for the DCI in response to receiving the DCI indicating MG skipping. The wireless device may skip one or more radio resource measurements (RRMs) during the first MG based on the DCI.

[0522] According to an example embodiment, the wireless device may transmit or receiving one or more signals during the first MG.

[0523] FIG. 23 illustrates an example as per an aspect of an embodiment of the present disclosure. In an example embodiment, a wireless device may receive downlink control information (DCI) indicating MG skipping, wherein the DCI does not schedule any data. The wireless device may transmit feedback (e.g., HARQ-ACK) for the DCI in response to receiving the DCI indicating MG skipping.

[0524] FIG. 24 illustrates an example as per an aspect of an embodiment of the present disclosure. In an example embodiment, a wireless device may receive downlink control information (DCI) indicating MG skipping. The wireless device may transmit feedback (e.g., HARQ-ACK) for the DCI indicating MG skipping.

[0525] In an aspect, the feedback (e.g., HARQ-ACK) for the DCI is transmitted after an offset (e.g., a quantity of symbols) from a timing (e.g., last symbol) of a physical downlink control channel (PDCCH) that provides the DCI.

[0526] According to an example embodiment, the wireless device may determine a HARQ-ACK priority for the feedback based on a field (e.g., priority indicator field) of the DCI.

[0527] In an aspect, each MG configuration, of the one or more MG configurations, comprises MG length and MG repetition period to indicate the plurality of MGs.

[0528] In an aspect, the MG is for radio resource measurement (RRM). In an aspect, the MG is for a scheduling restriction. In an aspect, the MG is based on a SMTC window.

[0529] In an aspect, the first MG is an earliest MG occurs after a time offset from receiving the DCI.Docket No.: 24-1263PCT

[0530] In an aspect, the time offset is a minimum time offset between the end the DCI reception and the start of the first MG.

[0531] In an aspect, the DCI is indicated by a scheduling DCI format.

[0532] In an aspect, the DCI comprises a bit field with a first value to indicate the first MG is skipped. In an aspect, the DCI comprises a bit field with a second value to indicate the first MG is not skipped.

[0533] In an aspect, the feedback is a HARQ-ACK. In an aspect, the feedback is a HARQ-NACK.

[0534] In an aspect, the measurement is a radio resource measurement (RRM). In an aspect, the measurement is SSB-based measurement.

[0535] In an aspect, the one or more signals comprise at least one of UL signals and DL signals.

[0536] In an aspect, the one or more signals are at least one of HARQ feedback, Scheduling Request (SR), CSI, SRS, RA preamble, Msg3, and / or MsgA payload.

[0537] In an aspect, the one or more signals are transmitted on PRACH, PDCCH, PUCCH, PUSCH, UL- SCH, PDSCH, and / or DL-SCH.

[0538] In some aspects, the techniques described herein relate to a method including: receiving, by a wireless device, one or more configurations indicating a plurality of measurement gaps (MGs) associated with a duration of time for performing one or more measurements; receiving downlink control information (DCI) indicating to cancel a first MG among the plurality of MGs, wherein the DCI does not schedule any physical downlink shared channel (PDSCH) receptions; transmitting feedback for the DCI in response to receiving the DCI indicating to cancel the first MG; and canceling the first MG based on the DCI.

[0539] In some aspects, the techniques described herein relate to a method including: receiving, by a wireless device, an indication to cancel a first measurement gap (MG) of a plurality of MGs; and transmitting feedback for the indication.

[0540] In some aspects, the techniques described herein relate to a method, further including receiving one or more configurations indicating the plurality of MGs.

[0541] In some aspects, the techniques described herein relate to a method, wherein each of the plurality of MGs is associated with a duration of time for performing one or more measurements.

[0542] In some aspects, the techniques described herein relate to a method, further including receiving a message including the indication.

[0543] In some aspects, the techniques described herein relate to a method, wherein the message is one of: downlink control information (DCI); or a medium access control control element (MAC CE).

[0544] In some aspects, the techniques described herein relate to a method, wherein the indication does not schedule any physical downlink shared channel (PDSCH) receptions.

[0545] In some aspects, the techniques described herein relate to a method, wherein the indication does not schedule any physical uplink shared channel (PUSCH) transmissions.Docket No.: 24-1263PCT

[0546] In some aspects, the techniques described herein relate to a method, wherein the indication does not schedule any data.

[0547] In some aspects, the techniques described herein relate to a method, further including canceling the first MG based on the indication.

[0548] In some aspects, the techniques described herein relate to a method, wherein the indication further indicates to cancel one or more MGs including the first MG.

[0549] In some aspects, the techniques described herein relate to a method, further including canceling one or more MGs including the first MG.

[0550] In some aspects, the techniques described herein relate to a method, wherein canceling the first MG includes canceling or not performing one or more radio resource measurements (RRMs) during the first MG.

[0551] In some aspects, the techniques described herein relate to a method, wherein the feedback is hybrid automatic repeat-request (HARQ) feedback.

[0552] In some aspects, the techniques described herein relate to a method, wherein the feedback is HARQ-ACK or HARQ-NACK.

[0553] In some aspects, the techniques described herein relate to a method, further including transmitting or receiving, based on the canceling, one or more signals during the first MG.

[0554] In some aspects, the techniques described herein relate to a method, wherein the feedback for the indication is transmitted after an offset from receiving a physical downlink control channel (PDCCH) including the indication.

[0555] In some aspects, the techniques described herein relate to a method, wherein the offset is a quantity of symbols.

[0556] In some aspects, the techniques described herein relate to a method, wherein the feedback for the indication is transmitted after an offset from a last symbol of a physical downlink control channel (PDCCH) including the indication.

[0557] In some aspects, the techniques described herein relate to a method, further including determining a HARQ-acknowledgement (ACK) priority for the feedback.

[0558] In some aspects, the techniques described herein relate to a method, further including determining a priority for the feedback based on a field of a message including the indication.

[0559] In some aspects, the techniques described herein relate to a method, further including determining a priority for the feedback based on a priority indicator field of a message including the indication.

[0560] In some aspects, the techniques described herein relate to a method, wherein the priority is a HARQ-ACK priority.Docket No.: 24-1263PCT

[0561] In some aspects, the techniques described herein relate to a method, wherein each of the one or more configurations includes a respective MG length and a respective MG repetition period to indicate each of the plurality of MGs.

[0562] In some aspects, the techniques described herein relate to a method, wherein each of the plurality of MGs is for radio resource measurement (RRM).

[0563] In some aspects, the techniques described herein relate to a method, wherein each of the plurality of MGs is for a scheduling restriction.

[0564] In some aspects, the techniques described herein relate to a method, wherein the first MG is an earliest MG occuring after a time offset from receiving the indication.

[0565] In some aspects, the techniques described herein relate to a method, wherein the time offset is a minimum time offset between an end reception of a message, including the indication, and the start of the first MG.

[0566] In some aspects, the techniques described herein relate to a method, wherein the message is DCI indicated by a scheduling DCI format.

[0567] In some aspects, the techniques described herein relate to a method, wherein the message includes a bit field with a first value to indicate the first MG is cancelled.

[0568] In some aspects, the techniques described herein relate to a method, wherein the message includes a bit field with a second value to indicate the first MG is not cancelled.

[0569] In some aspects, the techniques described herein relate to a method, wherein the one or more measurement are one or more radio resource measurements (RRMs).

[0570] In some aspects, the techniques described herein relate to a method, wherein the one or more measurements are one or more synchronization signal block (SSB)-based measurements.

[0571] In some aspects, the techniques described herein relate to a method, wherein the one or more signals include at least one of UL signals and DL signals.

[0572] In some aspects, the techniques described herein relate to a method, wherein the one or more signals are at least one of: HARQ feedback; one or more scheduling requests (SRs); channel state information (CSI); one or more sounding reference signals (SRSs); one or more random access preambles; Msg3 payload; or MsgA payload.

[0573] In some aspects, the techniques described herein relate to a method, wherein the one or more signals are transmitted on at least one of: a physical random access channel (PRACH); a physical downlink control channel (PDCCH); a physical uplink control channel (PUCCH); a physical uplink shared channel (PUSCH); an uplink shared channel (UL-SCH); a physical downlink shared channel (PDSCH); or a downlink shared channel (DL-SCH).

[0574] In some aspects, the techniques described herein relate to a method including: transmitting, by a base station to a wireless device, one or more configurations indicating a plurality of measurement gapsDocket No.: 24-1263PCT(MGs) associated with a duration of time for performing one or more measurements; transmitting, to the wireless device, downlink control information (DCI) indicating to cancel a first MG among the plurality of MGs, wherein the DCI does not schedule any physical downlink shared channel (PDSCH) receptions; and receiving, from the wireless device, feedback for the DCI in response to transmitting the DCI indicating to cancel the first MG.

[0575] In some aspects, the techniques described herein relate to a method including: transmitting, by a base station to a wireless device, an indication to cancel a first measurement gap (MG) of a plurality of MGs; and receiving, from the wireless device, feedback for the indication.

[0576] In some aspects, the techniques described herein relate to a method, further including transmitting, to the wireless device, one or more configurations indicating the plurality of MGs.

[0577] In some aspects, the techniques described herein relate to a method, wherein each of the plurality of MGs is associated with a duration of time for performing one or more measurements.

[0578] In some aspects, the techniques described herein relate to a method, further including transmitting, to the wireless device, a message including the indication.

[0579] In some aspects, the techniques described herein relate to a method, wherein the message is one of: downlink control information (DCI); or a medium access control control element (MAC CE).

[0580] In some aspects, the techniques described herein relate to a method, wherein the indication does not schedule any physical downlink shared channel (PDSCH) receptions.

[0581] In some aspects, the techniques described herein relate to a method, wherein the indication does not schedule any physical uplink shared channel (PUSCH) transmissions.

[0582] In some aspects, the techniques described herein relate to a method, wherein the indication does not schedule any data.

[0583] In some aspects, the techniques described herein relate to a method, further including canceling the first MG based on the indication.

[0584] In some aspects, the techniques described herein relate to a method, wherein the indication further indicates to cancel one or more MGs including the first MG.

[0585] In some aspects, the techniques described herein relate to a method, further including canceling one or more MGs including the first MG.

[0586] In some aspects, the techniques described herein relate to a method, wherein canceling the first MG includes canceling or not performing one or more radio resource measurements (RRMs) during the first MG.

[0587] In some aspects, the techniques described herein relate to a method, wherein the feedback is hybrid automatic repeat-request (HARQ) feedback.

[0588] In some aspects, the techniques described herein relate to a method, wherein the feedback is HARQ-ACK or HARQ-NACK.Docket No.: 24-1263PCT

[0589] In some aspects, the techniques described herein relate to a method, further including receiving or transmitting , based on the canceling, one or more signals during the first MG.

[0590] In some aspects, the techniques described herein relate to a method, wherein the feedback for the indication is received after an offset from transmitting a physical downlink control channel (PDCCH) including the indication.

[0591] In some aspects, the techniques described herein relate to a method, wherein the offset is a quantity of symbols.

[0592] In some aspects, the techniques described herein relate to a method, wherein the feedback for the indication is received after an offset from a last symbol of a PDCCH including the indication.

[0593] In some aspects, the techniques described herein relate to a method, further including determining a HARQ-acknowledgement (ACK) priority for the feedback.

[0594] In some aspects, the techniques described herein relate to a method, further including determining a priority for the feedback based on a field of a message including the indication.

[0595] In some aspects, the techniques described herein relate to a method, further including determining a priority for the feedback based on a priority indicator field of a message including the indication.

[0596] In some aspects, the techniques described herein relate to a method, wherein the priority is a HARQ-ACK priority.

[0597] In some aspects, the techniques described herein relate to a method, wherein each of the one or more configurations includes a respective MG length and a respective MG repetition period to indicate each of the plurality of MGs.

[0598] In some aspects, the techniques described herein relate to a method, wherein each of the plurality of MGs is for radio resource measurement (RRM).

[0599] In some aspects, the techniques described herein relate to a method, wherein each of the plurality of MGs is for a scheduling restriction.

[0600] In some aspects, the techniques described herein relate to a method, wherein the first MG is an earliest MG occurring after a time offset from receiving the indication.

[0601] In some aspects, the techniques described herein relate to a method, wherein the time offset is a minimum time offset between an end reception of a message, including the indication, and the start of the first MG.

[0602] In some aspects, the techniques described herein relate to a method, wherein the message is DCI indicated by a scheduling DCI format.

[0603] In some aspects, the techniques described herein relate to a method, wherein the message includes a bit field with a first value to indicate the first MG is cancelled.

[0604] In some aspects, the techniques described herein relate to a method, wherein the message includes a bit field with a second value to indicate the first MG is not cancelled.Docket No.: 24-1263PCT

[0605] In some aspects, the techniques described herein relate to a method, wherein the one or more measurements are one or more radio resource measurements (RRMs).

[0606] In some aspects, the techniques described herein relate to a method, wherein the one or more measurements are one or more synchronization signal block (SSB)-based measurements.

[0607] In some aspects, the techniques described herein relate to a method, wherein the one or more signals include at least one of UL signals and DL signals.

[0608] In some aspects, the techniques described herein relate to a method, wherein the one or more signals are at least one of: HARQ feedback; one or more scheduling requests (SRs); channel state information (CSI); one or more sounding reference signals (SRSs); one or more random access preambles; Msg3 payload; or MsgA payload.

[0609] In some aspects, the techniques described herein relate to a method, wherein the one or more signals are transmitted on at least one of: a physical random access channel (PRACH); a physical downlink control channel (PDCCH); a physical uplink control channel (PUCCH); a physical uplink shared channel (PUSCH); an uplink shared channel (UL-SCH); a physical downlink shared channel (PDSCH); or a downlink shared channel (DL-SCH).

[0610] In some aspects, the techniques described herein relate to an apparatus including: one or more processors; and memory storing instructions that, when executed by the one or more processors, cause the apparatus to perform any of the techniques or methods disclosed herein.

[0611] In some aspects, the techniques described herein relate to a non-transitory computer-readable medium including instructions that, when executed by one or more processors of an apparatus, cause the apparatus to perform any of the techniques or methods disclosed herein.

Claims

Docket No.: 24-1263PCTCLAIMSWhat is claimed is:

1. A method comprising: receiving, by a wireless device, one or more configurations indicating a plurality of measurement gaps (MGs) associated with a duration of time for performing one or more measurements; receiving downlink control information (DCI) indicating to cancel a first MG among the plurality of MGs, wherein the DCI does not schedule any physical downlink shared channel (PDSCH) receptions; transmitting feedback for the DCI in response to receiving the DCI indicating to cancel the first MG; and canceling the first MG based on the DCI.

2. A method comprising: receiving, by a wireless device, an indication to cancel a first measurement gap (MG) of a plurality of MGs; and transmitting feedback for the indication.

3. The method of claim 2, further comprising receiving one or more configurations indicating the plurality of MGs.

4. The method of any one of claims 1-3, wherein each of the plurality of MGs is associated with a duration of time for performing one or more measurements.

5. The method of any one of claims 1-4, further comprising receiving a message comprising the indication.

6. The method of any one of claims 1-5, wherein the message is one of: downlink control information (DCI); or a medium access control control element (MAC CE).

7. The method of any one of claims 1-6, wherein the indication does not schedule any physical downlink shared channel (PDSCH) receptions.

8. The method of any one of claims 1-7, wherein the indication does not schedule any physical uplink shared channel (PUSCH) transmissions.

9. The method of any one of claims 1-8, wherein the indication does not schedule any data.

10. The method of any one of claims 1-9, further comprising canceling the first MG based on the indication.11 . The method of any one of claims 1-10, wherein the indication further indicates to cancel one or more MGs comprising the first MG.

12. The method of any one of claims 1-11, further comprising canceling one or more MGs comprising the first MG.Docket No.: 24-1263PCT13. The method of any one of claims 1-12, wherein canceling the first MG comprises canceling or not performing one or more radio resource measurements (RRMs) during the first MG.

14. The method of any one of claims 1-13, wherein the feedback is hybrid automatic repeat-request (HARQ) feedback.

15. The method of any one of claims 1-14, wherein the feedback is HARQ-ACK or HARQ-NACK.

16. The method of any one of claims 1-15, further comprising transmitting or receiving, based on the canceling, one or more signals during the first MG.

17. The method of any one of claims 1-16, wherein the feedback for the indication is transmitted after an offset from receiving a physical downlink control channel (PDCCH) comprising the indication.

18. The method of any one of claims 1-17, wherein the offset is a quantity of symbols.

19. The method of any one of claims 1-18, wherein the feedback for the indication is transmitted after an offset from a last symbol of a physical downlink control channel (PDCCH) comprising the indication.

20. The method of any one of claims 1-19, further comprising determining a HARQ-acknowledgement (ACK) priority for the feedback.

21. The method of any one of claims 1-20, further comprising determining a priority for the feedback based on a field of a message comprising the indication.

22. The method of any one of claims 1-21, further comprising determining a priority for the feedback based on a priority indicator field of a message comprising the indication.

23. The method of any one of claims 1-22, wherein the priority is a HARQ-ACK priority.

24. The method of any one of claims 1-23, wherein each of the one or more configurations comprises a respective MG length and a respective MG repetition period to indicate each of the plurality of MGs.

25. The method of any one of claims 1-24, wherein each of the plurality of MGs is for radio resource measurement (RRM).

26. The method of any one of claims 1-25, wherein each of the plurality of MGs is for a scheduling restriction.

27. The method of any one of claims 1-26, wherein the first MG is an earliest MG occuring after a time offset from receiving the indication.

28. The method of any one of claims 1-27, wherein the time offset is a minimum time offset between an end reception of a message, comprising the indication, and the start of the first MG.

29. The method of any one of claims 1-28, wherein the message is DCI indicated by a scheduling DCI format.

30. The method of any one of claims 1-29, wherein the message comprises a bit field with a first value to indicate the first MG is cancelled.

31. The method of any one of claims 1-30, wherein the message comprises a bit field with a second value to indicate the first MG is not cancelled.Docket No.: 24-1263PCT32. The method of any one of claims 1-31 , wherein the one or more measurement are one or more radio resource measurements (RRMs).

33. The method of any one of claims 1 -32, wherein the one or more measurements are one or more synchronization signal block (SSB)-based measurements.

34. The method of any one of claims 1-33, wherein the one or more signals comprise at least one of UL signals and DL signals.

35. The method of any one of claims 1-34, wherein the one or more signals are at least one of:HARQ feedback; one or more scheduling requests (SRs); channel state information (CSI); one or more sounding reference signals (SRSs); one or more random access preambles;Msg3 payload; orMsgA payload.

36. The method of any one of claims 1-35, wherein the one or more signals are transmitted on at least one of: a physical random access channel (PRACH); a physical downlink control channel (PDCCH); a physical uplink control channel (PUCCH); a physical uplink shared channel (PUSCH); an uplink shared channel (UL-SCH); a physical downlink shared channel (PDSCH); or a downlink shared channel (DL-SCH).

37. A method comprising: transmitting, by a base station to a wireless device, one or more configurations indicating a plurality of measurement gaps (MGs) associated with a duration of time for performing one or more measurements; transmitting, to the wireless device, downlink control information (DCI) indicating to cancel a first MG among the plurality of MGs, wherein the DCI does not schedule any physical downlink shared channel (PDSCH) receptions; and receiving, from the wireless device, feedback for the DCI in response to transmitting the DCI indicating to cancel the first MG.

38. A method comprising: transmitting, by a base station to a wireless device, an indication to cancel a first measurement gap (MG) of a plurality of MGs; andDocket No.: 24-1263PCT receiving, from the wireless device, feedback for the indication.

39. The method of claim 38, further comprising transmitting, to the wireless device, one or more configurations indicating the plurality of MGs.

40. The method of any one of claims 37-39, wherein each of the plurality of MGs is associated with a duration of time for performing one or more measurements.41 . The method of any one of claims 37-40, further comprising transmitting, to the wireless device, a message comprising the indication.

42. The method of any one of claims 37-41 , wherein the message is one of: downlink control information (DCI); or a medium access control control element (MAC CE).

43. The method of any one of claims 37-42, wherein the indication does not schedule any physical downlink shared channel (PDSCH) receptions.

44. The method of any one of claims 37-43, wherein the indication does not schedule any physical uplink shared channel (PUSCH) transmissions.

45. The method of any one of claims 37-44, wherein the indication does not schedule any data.

46. The method of any one of claims 37-45, further comprising canceling the first MG based on the indication.

47. The method of any one of claims 37-46, wherein the indication further indicates to cancel one or more MGs comprising the first MG.

48. The method of any one of claims 37-47, further comprising canceling one or more MGs comprising the first MG.

49. The method of any one of claims 37-48, wherein canceling the first MG comprises canceling or not performing one or more radio resource measurements (RRMs) during the first MG.

50. The method of any one of claims 37-49, wherein the feedback is hybrid automatic repeat-request (HARQ) feedback.51 . An apparatus comprising: one or more processors; and memory storing instructions that, when executed by the one or more processors, cause the apparatus to perform the method of any one of claims 1-50.

52. A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors of an apparatus, cause the apparatus to perform the method of any one of claims 1 - 50.

Images