Uplink Transmission Handling with Subband Full-Duplex Operation

Abstract

A method comprises receiving, by a wireless device from a base station, one or more messages indicating to skip applying a timing advance offset. The method further comprises, based on the indication, transmitting, via a cell, a first uplink (UL) transmission during one or more subband full duplex (SBFD) symbols.

Description

Docket No.: 24-1191 PCTTITLEUplink Transmission Handling with Subband Full-Duplex Operation CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 693,741 , filed September12, 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.Docket No.: 24-1191 PCT

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

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

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

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

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

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

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

[0025] FIGs. 19A and 19B illustrate aspects of example embodiments according to the present disclosure.

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

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

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

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

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

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

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

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

[0034] FIGs. 28A and 28B illustrate aspects example embodiments according to the present disclosure.

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

[0036] FIG. 30 illustrates a flow chart of an example embodiment according to the present disclosure.DETAILED DESCRIPTION

[0037] 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 andDocket No.: 24-1191 PCT 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.

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

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

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

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

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

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

[0044] 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 theDocket No.: 24-1191 PCT three possible features, with any two of the three possible features or with three of the three possible features.

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

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

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

[0048] 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. DownlinkDocket No.: 24-1191 PCT transmissions may be separated from uplink transmissions using frequency division duplexing (FDD), timedivision duplexing (TDD), and / or some combination of the two duplexing techniques.

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

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

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

[0052] 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 / similarDocket No.: 24-1191 PCT 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.

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

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

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

[0056] 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 networkDocket No.: 24-1191 PCT 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).

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

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

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

[0060] 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 ofDocket No.: 24-1191 PCT 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.

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

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

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

[0064] 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). AlthoughDocket No.: 24-1191 PCT 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.

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

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

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

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

[0069] 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 messagesDocket No.: 24-1191 PCT 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.

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

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

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

[0073] 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.Docket No.: 24-1191 PCTThese 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.

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

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

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

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

[0078] FIG. 4B further illustrates MAC control elements (CEs) inserted into the MAC PDU by a MAC, such as MAC 223 or MAC 222 For example, FIG. 4B illustrates two MAC CEs inserted into the MAC PDU. MAC CEs may be inserted at the beginning of a MAC PDU for downlink transmissions (as shown in FIG. 4B) andDocket No.: 24-1191 PCT 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.

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

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

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

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

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

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

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

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

[0087] - a paging channel (PCH) for carrying paging messages that originated from the PCCH;Docket No.: 24-1191 PCT

[0088] -- a broadcast channel (BCH) for carrying the M IB from the BCCH;

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

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

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

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

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

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

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

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

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

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

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

[0100] 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 ofDocket No.: 24-1191 PCT 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.

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

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

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

[0104] 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 baseDocket No.: 24-1191 PCT 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.

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

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

[0107] An RRC state may be associated with a mobility management mechanism. In RRC idle 604 and RRC inactive 606, mobility is managed by the UE through cell reselection. The purpose of mobility management in RRC idle 604 and RRC inactive 606 is to allow the network to be able to notify the UE of an event via a paging message without having to broadcast the paging message over the entire mobile communications network. The mobility management mechanism used in RRC idle 604 and RRC inactive 606 may allow the network to track the UE on a cell-group level so that the paging message may be broadcast over the cells of the cell group that the UE currently resides within instead of the entire mobile communication network. The mobility management mechanisms for RRC idle 604 and RRC inactive 606 track the UE on a cell-group level. They may do so using different granularities of grouping. For example, there may be three levels of cell-grouping granularity: individual cells; cells within a RAN area identified byDocket No.: 24-1191 PCT 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).

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

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

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

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

[0112] In NR, the physical signals and physical channels (discussed with respect to FIG. 5A and FIG. 5B) may be mapped onto orthogonal frequency divisional multiplexing (OFDM) symbols. OFDM is a multicarrier communication scheme that transmits data over F orthogonal subcarriers (or tones). Before transmission, the data may be mapped to a series of complex symbols (e.g., M-quadrature amplitude modulation (M- QAM) or M-phase shift keying (M-PSK) symbols), referred to as source symbols, and divided into F parallel symbol streams. The F parallel symbol streams may be treated as though they are in the frequency domain and used as inputs to an Inverse Fast Fourier Transform (IFFT) block that transforms them into the time domain. The IFFT block may take in F source symbols at a time, one from each of the F parallel symbol streams, and use each source symbol to modulate the amplitude and phase of one of F sinusoidal basis functions that correspond to the F orthogonal subcarriers. The output of the IFFT block may be F timedomain samples that represent the summation of the F orthogonal subcarriers. The F time-domain samples may form a single OFDM symbol. After some processing (e.g., addition of a cyclic prefix) and up- conversion, an OFDM symbol provided by the IFFT block may be transmitted over the air interface on aDocket No.: 24-1191 PCT 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.

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

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

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

[0116] 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 spacingsDocket No.: 24-1191 PCT 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.

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

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

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

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

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

[0122] 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).Docket No.: 24-1191 PCT

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

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

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

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

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

[0128] FIG. 9 illustrates an example of bandwidth adaptation using three configured BWPs for an NR carrier. A UE configured with the three BWPs may switch from one BWP to another BWP at a switching point. In the example illustrated in FIG. 9, the BWPs include: a BWP 902 with a bandwidth of 40 MHz and a subcarrier spacing of 15 kHz; a BWP 904 with a bandwidth of 10 MHz and a subcarrier spacing of 15 kHz; and a BWP 906 with a bandwidth of 20 MHz and a subcarrier spacing of 60 kHz. The BWP 902 may be an initial active BWP, and the BWP 904 may be a default BWP. The UE may switch between BWPs at switching points. In the example of FIG. 9, the UE may switch from the BWP 902 to the BWP 904 at aDocket No.: 24-1191 PCT 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.

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

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

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

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

[0133] When CA is used, one of the aggregated cells for a UE may be referred to as a primary cell (PCell). The PCell may be the serving cell that the UE initially connects to at RRC connection establishment, reestablishment, and / or handover. The PCell may provide the UE with NAS mobility information and the security input. UEs may have different PCells. In the downlink, the carrier corresponding to the PCell may be referred to as the downlink primary CC (DL PCC). In the uplink, the carrier corresponding to the PCell may be referred to as the uplink primary CC (UL PCC). The otherDocket No.: 24-1191 PCT 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).

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

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

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

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

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

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

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

[0141] The SS / PBCH block may span one or more OFDM symbols in the time domain (e.g., 4 OFDM symbols, as shown in the example of FIG. 11 A) and may span one or more subcarriers in the frequency domain (e.g., 240 contiguous subcarriers). The PSS, the SSS, and the PBCH may have a common centerDocket No.: 24-1191 PCT 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.

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

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

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

[0145] 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-1191 PCT 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.

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

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

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

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

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

[0151] 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 downlinkDocket No.: 24-1191 PCTCSI-RS and SS / PBCH blocks when the downlink CSI-RS and SS / PBCH blocks are spatially QCLed and resource elements associated with the downlink CSI-RS are outside of PRBs configured for the SS / PBCH blocks.

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

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

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

[0155] 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 oneDocket No.: 24-1191 PCT configuration of a scheduled bandwidth. The UE may assume a same precoding for a DMRS port and a PT-RS port. A number of PT-RS ports may be fewer than a number of DMRS ports in a scheduled resource. Downlink PT-RS may be confined in the scheduled time / frequency duration for the UE. Downlink PT-RS may be transmitted on symbols to facilitate phase tracking at the receiver.

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

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

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

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

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

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

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

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

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

[0165] 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).Docket No.: 24-1191 PCTThe UE may receive a downlink transmission with a receive (Rx) beam determined based on the one or more TCI states. In an example, the UE may or may not have a capability of beam correspondence. If the UE has the capability of beam correspondence, the UE may determine a spatial domain filter of a transmit (Tx) beam based on a spatial domain filter of the corresponding Rx beam. If the UE does not have the capability of beam correspondence, the UE may perform an uplink beam selection procedure to determine the spatial domain filter of the Tx beam. The UE may perform the uplink beam selection procedure based on one or more sounding reference signal (SRS) resources configured to the UE by the base station. The base station may select and indicate uplink beams for the UE based on measurements of the one or more SRS resources transmitted by the UE.

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

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

[0168] 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 sweepDocket No.: 24-1191 PCT 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.

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

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

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

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

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

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

[0175] 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 UEDocket No.: 24-1191 PCT 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).

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

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

[0178] 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 preambleDocket No.: 24-1191 PCT 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) .

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

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

[0181] 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) mayDocket No.: 24-1191 PCT 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).

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

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

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

[0185] 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 mayDocket No.: 24-1191 PCT 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).

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

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

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

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

[0190] 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 theDocket No.: 24-1191 PCT transport block 1342 included in the Msg A 1331. The RACH parameters may indicate a modulation and coding schemes (MCS), a time-frequency resource, and / or a power control for the preamble 1341 and / or the transport block 1342. A time-frequency resource for transmission of the preamble 1341 (e.g., a PRACH) and a time-frequency resource for transmission of the transport block 1342 (e.g., a PUSCH) may be multiplexed using FDM, TDM, and / or CDM. The RACH parameters may enable the UE to determine a reception timing and a downlink channel for monitoring for and / or receiving Msg B 1332.

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

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

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

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

[0195] 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-Docket No.: 24-1191 PCTRNTI) 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.

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

[0197] 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 inDocket No.: 24-1191 PCT 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).

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

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

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

[0201] 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 PDCCHDocket No.: 24-1191 PCT 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).

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

[0203] 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 fourteenDocket No.: 24-1191 PCTOFDM 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.

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

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

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

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

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

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

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

[0211] 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 / orDocket No.: 24-1191 PCT beamforming. In other examples, the wireless device 1502 and / or the base station 1504 may have a single antenna.

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

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

[0214] 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 andDocket No.: 24-1191 PCT 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.

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

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

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

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

[0219] 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 configurationDocket No.: 24-1191 PCT 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.

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

[0221] A base station may transmit one or more MAC PDUs to a wireless device. In an example, a MAC PDU may be a bit string that is byte aligned (e.g., aligned to a multiple of eight bits) in length. In an example, bit strings may be represented by tables in which the most significant bit is the leftmost bit of the first line of the table, and the least significant bit is the rightmost bit on the last line of the table. More generally, the bit string may be read from left to right and then in the reading order of the lines. In an example, the bit order of a parameter field within a MAC PDU is represented with the first and most significant bit in the leftmost bit and the last and least significant bit in the rightmost bit.

[0222] In an example, a MAC SDU may be a bit string that is byte aligned (e.g., aligned to a multiple of eight bits) in length. In an example, a MAC SDU may be included in a MAC PDU from the first bit onward. A MAC CE may be a bit string that is byte aligned (e.g., aligned to a multiple of eight bits) in length. A MAC subheader may be a bit string that is byte aligned (e.g., aligned to a multiple of eight bits) in length. In an example, a MAC subheader may be placed immediately in front of a corresponding MAC SDU, MAC CE, or padding. A MAC entity may ignore a value of reserved bits in a DL MAC PDU.

[0223] In an example, a MAC PDU may comprise one or more MAC subPDUs. A MAC subPDU of the one or more MAC subPDUs may comprise: a MAC subheader only (including padding); a MAC subheaderDocket No.: 24-1191 PCT and a MAC SDU; a MAC subheader and a MAC CE; a MAC subheader and padding, or a combination thereof. The MAC SDU may be of variable size. A MAC subheader may correspond to a MAC SDU, a MAC CE, or padding.

[0224] In an example, when a MAC subheader corresponds to a MAC SDU, a variable-sized MAC CE, or padding, the MAC subheader may comprise: a Reserve field (R field) with a one bit length; an Format filed (F field) with a one-bit length; a Logical Channel Identifier (LCID) field with a multi-bit length; a Length field (L field) with a multi-bit length, indicating the length of the corresponding MAC SDU or variable-size MAC CE in bytes, or a combination thereof. In an example, F field may indicate the size of the L field.

[0225] In an example, a MAC entity of the base station may transmit one or more MAC CEs (e.g., MAC CE commands) to a MAC entity of a wireless device. The one or more MAC CEs may comprise at least one of: a SP ZP CSI-RS Resource Set Acti vation / Deacti vation MAC CE, a PUCCH spatial relation Acti vation / Deactivation MAC CE, a SP SRS Activation / Deactivation MAC CE, a SP CSI reporting on PUCCH Activation / Deactivation MAC CE, a TCI State Indication for UE-specific PDCCH MAC CE, a TCI State Indication for UE-specific PDSCH MAC CE, an Aperiodic CSI Trigger State Subselection MAC CE, a SP CSI-RS / CSI-IM Resource Set Activation / Deactivation MAC CE, a UE contention resolution identity MAC CE, a timing advance command MAC CE, a DRX command MAC CE, a Long DRX command MAC CE, an SCell activation / deactivation MAC CE (1 Octet), an SCell activation / deactivation MAC CE (4 Octet), and / or a duplication activation / deactivation MAC CE. In an example, a MAC CE, such as a MAC CE transmitted by a MAC entity of the base station to a MAC entity of the wireless device, may have an LCID in the MAC subheader corresponding to the MAC CE. In an example, a first MAC CE may have a first LCID in the MAC subheader that may be different than the second LCID in the MAC subheader of a second MAC CE. For example, an LCID given by 111011 in a MAC subheader may indicate that the MAC CE associated with the MAC subheader is a Long DRX command MAC CE.

[0226] In an example, the MAC entity of the wireless device may transmit to the MAC entity of the base station one or more MAC CEs. The one or more MAC CEs may comprise at least one of: a short buffer status report (BSR) MAC CE, a long BSR MAC CE, a C-RNTI MAC CE, a configured grant confirmation MAC CE, a single entry PHR MAC CE, a multiple entry PHR MAC CE, a Short truncated BSR, and / or a Long truncated BSR. In an example, a MAC CE may have an LCID in the MAC subheader corresponding to the MAC CE. In an example, a first MAC CE may have a first LCID in the MAC subheader that may be different than the second LCID in the MAC subheader of a second MAC CE. For example, an LCID given by 111011 in a MAC subheader may indicate that a MAC CE associated with the MAC subheader is a short-truncated command MAC CE.Docket No.: 24-1191 PCT

[0227] A base station may transmit one or more messages to a wireless device. The one or more messages may comprise the one or more MAC PDUs. The wireless device may receive at least one message of the one or more messages via / usi ng one or more PDSCHs / TBs.

[0228] The one or more messages may comprise one or more RRC messages. The one or more RRC messages may comprise at least one RRC connection / establishment / configuration / setup message. The one or more RRC messages may comprise at least one RRC reconnection / reestablishment / reconfiguration message. The one or more RRC messages may comprise at least one RRC release message.

[0229] The one or more messages may comprise one or more MAC CEs.

[0230] The one or more messages may comprise one or more DCIs.

[0231] The one or more messages may comprise one or more downlink information for control.

[0232] The one or more messages may comprise one or more commands (e.g., control commands) forUL / DL communications. The one or more messages may comprise one or more configuration parameters. The one or more configuration parameters may correspond to one or more signals / channels. The one or more channels / signals may comprise one or more DL signals / channels, e.g., PDSCH / CSI- RS / PDCCH / SSB / WUS (wake up signal) or the like. The one or more channels / signals may comprise one or more UL signals / channels, e.g., PUSCH / SRS / PUCCH / WUS or the like.

[0233] The one or more messages may configure the wireless device with a carrier aggregation (CA) operation. In the carrier aggregation (operation), two or more component carriers (CCs) may be aggregated. Each carrier may be also referred to by / as a cell (e.g., serving cell). The cell may be a secondary cell (SCell). The wireless device may, using the technique of CA, simultaneously receive or transmit on one or more CCs, depending on capabilities of the wireless device. The one or more configuration parameters may configure / indicate the one or more CCs. In an example, the wireless device may support CA for contiguous CCs and / or for non-contiguous CCs. In some implementations, the one or more CCs may be organized into one or more cells. For example, the one or more CCs may be organized into a combination of a primary cell (PCell) and one or more secondary cells (SCells).

[0234] The one or more configuration parameters may, for example via one or more serving cell configuration parameters, comprise / configure / indicate the one or more cells (e.g., ServingCellConfigCommon, ServingCellConfigCommonSIB, and / or ServingCellConfig). The one or more cells may comprise one or more serving cell (e.g., the one or more Serving Cells). The one or more serving cell configuration parameters may be for configuring one or more cells (e.g., the one or more Serving Cells). For example, the one or more cells may comprise a master (or primary) cell group (MSG) and / or a secondary cell group (SCG).

[0235] In some cases, a cell of the one or more cells may be a primary secondary cell (PSCell), or a primary cell (PCell), or a secondary cell (SCell), or a special cell (SpCell). In some other cases, a cell of theDocket No.: 24-1191 PCT one or more cells may belong to a first cell group corresponding to a primary TAG (pTAG) or a second cell group corresponding to a secondary TAG (sTAG). For example, the one or more configuration parameters may configure the wireless device for multi-cell communication and / or carrier aggregation.

[0236] In an example, the one or more cells may comprise a plurality of one or more SCells, depending on capabilities of the wireless device. When configured with CA, the base station and / or the wireless device may employ an activation / deactivation mechanism of an SCell to improve battery or power consumption of the wireless device. When the wireless device is configured with the one or more SCells, the base station may activate or deactivate (e.g., via MAC CE or DCI) at least one of the one or more SCells. Upon configuration of an SCell (e.g., via the one or more serving cell configuration parameters), the SCell may be deactivated unless the SCell state associated with the SCell is set to "activated” or “dormant”, via a DCI or MAC CE. The wireless device may activate / d eactivate the SCell in response to receiving an SCell Act! vation / Deactivation MAC CE.

[0237] For example, the base station may configure (e.g., via the one or more RRC messages / configuration parameters) the wireless device with uplink (UL) bandwidth parts (BWPs) and downlink (DL) BWPs to enable bandwidth adaptation (BA) on a PCell. If carrier aggregation (CA) is configured, the base station may further configure the wireless device with at least one DL BWP (i.e., there may be no UL BWP in the UL) to enable BA on an SCell. For the PCell, an initial active BWP may be a first BWP used for initial access. In paired spectrum (e.g., FDD), the base station and / or the wireless device may independently switch a DL BWP and an UL BWP. In unpaired spectrum (e.g., TDD), the base station and / or the wireless device may simultaneously switch the DL BWP and the UL BWP.

[0238] In an example, the one or more configuration parameters may comprise configuration parameters of one or more BWPs (e.g., one or more BWP configuration parameters). The one or more BWP configuration parameters may comprise parameters of the cell and one or more BWPs associated with the cell. Among the one or more BWPs, at least one BWP may be configured as the first active BWP (e.g., BWP 1), one BWP as the default BWP (e.g., BWP 0). In some cases, the wireless device may receive a command (e.g., an RRC message, a MAC CE or a DCI) to activate the cell at a slot. In some other cases (e.g., when the cell is a PCell), the wireless device may activate the cell (e.g., PCell) once the wireless device receives the command (e.g., the RRC message) comprising configuration parameters of the PCell. The wireless device may start monitoring a PDCCH (e.g., monitoring PDCCH candidates) on BWP 1 , e.g., in response to activating the cell.

[0239] A wireless device may start (or restart) a BWP inactivity timer (e.g., bwp-lnactivityTimer) at an m-th slot in response to receiving a DCI indicating DL assignment on BWP 1 . The wireless device may switch back to the default BWP (e.g., BWP 0) as an active BWP when the BWP inactivity timer expires, at s-th slot. The wireless device may deactivate the cell and / or stop the BWP inactivity timer when theDocket No.: 24-1191 PCT sCellDeactivationTimer expires (e.g., if the cell is a SCell). In response to the cell being a PCell, the wireless device may not deactivate the cell and may not apply the sCellDeactivationTimer on the PCell.

[0240] A MAC entity may apply normal operations on an active (or activated) BWP for an activated serving cell (e.g., the cell). For example, on the activated BWP and via the cell the wireless device may perform at least one of the following: transmitting on UL-SCH (PUSCH transmission); transmitting on RACH (preamble transmission); monitoring a PDCCH; transmitting PUCCH; receiving DL-SCH (PDSCH reception); and / or (re-) initializing configured uplink grants of configured grant Type 1 or Type 2 according to a stored configuration. The one or more configuration parameters may configure / provide configured uplink grants of configured grant Type 1 or Type 2.

[0241] On an inactive (or deactivated or dormant) BWP of the cell (or for each activated serving cell configured with a BWP), the wireless device may perform at least one of the following: not transmit on UL- SCH; not transmit on RACH; not monitor a PDCCH; not transmit PUCCH; not transmit SRS, not receive DL-SCH; clear any configured downlink assignment and configured uplink grant of configured grant Type 2; and / or suspend any configured uplink grant of configured Type 1 .

[0242] A DCI addressed to an RNTI may comprise a CRC of the DCI being scrambled with the RNTI. The wireless device may monitor PDCCH addressed to (or for) the RNTI for detecting the DCI. For example, the PDCCH may carry (or be with) the DCI. In an example, the PDCCH may not carry the DCI.

[0243] The one or more configuration parameters may comprise one or more PDCCH configuration parameters for configure / indicate a set of PDCCH candidates for the wireless device to monitor via / in terms of one or more search space sets. For example, the one or more PDCCH configuration parameters may configure / indicate the one or more search space sets. The one or more PDCCH configuration parameters may comprise at least PDCCH-ConfigCommon and / or pdcch-ConfigS I B1 and / or PDCCH-Config.

[0244] A search space set of the one or more search space sets may comprise a common search space (CSS) set, or a UE-specific search space (USS) set. The wireless device may monitor one or more PDCCH candidates (of the set of PDCCH candidates) in one or more of the search space sets.

[0245] A search space set may be a TypeO-PDCCH CSS set configured by the pdcch-ConfigSIB1 (e.g., in MIB) or by searchSpaceSIBI in the PDCCH-ConfigCommon or by searchSpaceZero in the PDCCH- ConfigCommon.

[0246] A search space set may be a TypeOA-PDCCH CSS set configured by searchSpaceOtherSystemlnformation in the PDCCH-ConfigCommon for a DCI format with CRC scrambled by the SI-RNTI on the primary cell of the MCG.

[0247] A search space set may be a Typel -PDCCH CSS set configured by ra-SearchSpace in the PDCCH-ConfigCommon for a DCI format with CRC scrambled by a RA-RNTI, a MSGB-RNTI, or a TC- RNTI on the primary cell.Docket No.: 24-1191 PCT

[0248] A search space set may be a Type2-PDCCH CSS set configured by pagingSearchSpace in the PDCCH-ConfigCommon for a DCI format with CRC scrambled by a P-RNTI on the primary cell of the MCG.

[0249] A search space set may be a Type3-PDCCH CSS set configured by SearchSpace in the PDCCH- Config with searchSpaceType = common for DCI formats with CRC scrambled by at least one RNTI. The at least one RNTI may comprise one of the following: an INT-RNTI, an SFI-RNTI, a TPC-PUSCH-RNTI, a TPC-PUCCH-RNTI, a TPC-SRS-RNTI, a CI-RNTI, or a power saving RNTI (PS-RNTI) and, only for the primary cell, a C-RNTI, an MCS-C-RNTI, or a CS-RNTI(s).

[0250] A search space set may be a USS set configured by SearchSpace in the PDCCH-Config with searchSpaceType = ue-Specific for DCI formats with CRC scrambled by the C-RNTI, the MCS-C-RNTI, a SP-CSI-RNTI, the CS-RNTI(s), a SL-RNTI, a SL-CS-RNTI, or a SL-L-CS-RNTI

[0251] The wireless device may monitor the one or more PDCCH candidates in one or more CORESETs for detecting one or more DCIs. The one or more PDCCH configuration parameters may configure / indicate the one or more CORESETs. Monitoring the one or more PDCCH candidates may comprise decoding at least one PDCCH candidate of the one or more PDCCH candidates according to the monitored DCI formats. For example, monitoring the one or more PDCCH candidates may comprise decoding (e.g., blind decoding) a DCI content of the at least one PDCCH candidate via possible (or configured) PDCCH location(s), possible (or configured) PDCCH format(s), e.g., number of CCEs, number of PDCCH candidates in CSS set(s), and / or number of PDCCH candidates in the USS(s), and / or possible (or configured) DCI format(s).

[0252] FIG. 17 illustrates an example of one or more UL / DL TDD configurations of / for a cell as per an aspect of an embodiment of the present disclosure. The one or more UL / DL TDD configurations of / for the cell may be (or comprise) a cell-specific UL / DL TDD configuration (e.g., tdd-UL-DL-ConfigurationCommon) of / for the cell. The one or more UL / DL TDD configuration of / for the cell may be (or comprise) a UE-specific UL / DL TDD configuration (e.g., tdd-UL-DL-ConfigurationDedicated}. In an example, the cell-specific UL / DL TDD configuration for the cell may be broadcasted via a SIB1 or a SIB message. In an example, the UE- specific UL / DL TDD configuration for the cell may be transmitted via one or more messages (e.g., RRC, MAC CE, DCI).

[0253] As shown in FIG. 17, the one or more configuration parameters may comprise one or more TDD configuration parameters. The one or more TDD configuration parameters may be / comprise the UL / DL TDD configuration. The one or more TDD configuration parameters may comprise one or more common TDD configuration parameters (e.g., TDD-UL-DL-ConfigurationCommon).

[0254] For a serving cell (of the one or more serving cells), one or more common TDD configuration parameters may indicate / configure slot format(s) of a plurality of slots. FIG. 18 shows examples of a slot format in a TDD carrier.Docket No.: 24-1191 PCT

[0255] The one or more TDD configuration parameters may indicate / configure the plurality of slots. The plurality of slots may comprise one or more consecutive slots. The plurality of slots may comprise one or more DL slots / symbols. The plurality of slots may comprise one or more UL slots / symbols. The plurality of slots may comprise one or more flexible slots / symbols.

[0256] A first symbol / slot of the plurality of slots may be an Uplink (‘U7U L) symbol. An UL symbol may be used by the wireless device for uplink transmission(s), e.g., via the serving cell. The one or more DL slots / symbols may comprise the first symbol / slot.

[0257] A second symbol / slot of the plurality of slots may be a downlink ('D7DL). A DL symbol may be used by the wireless device for downlink reception(s), e.g., via the serving cell. The one or more DL slots / symbols may comprise the second symbol / slot.

[0258] In some implementations, a third symbol in a slot of the plurality of slots may be a flexible (‘F’) symbol. The one or more flexible slots / symbols may comprise the third symbol / slot. Slot format / direction of the flexible symbol may be determined (by the wireless device and / or the base station) by other signaling, e.g., DCI format 2_0 and / or UL / DL grants and / or the one or more UE-specific TDD configuration parameters. The format ‘F’ is used by the network to control UL / DL transmission / reception of each wireless device flexibly. For example, the network may assign a symbol with 'F' for a wireless device not to transmit to or receive from a base station, e.g., for interference control and / or power saving purposes. For example, the network may use a slot format ‘F’ on one or more symbols to selectively initiate / trigger random access (RA) for a particular wireless device. Other wireless devices may not be allowed to transmit or receive on the one or more symbols, resulting in reduced interference for the wireless device.

[0259] The one or more common TDD configuration parameters may comprise at least one of: a reference subcarrier spacing (SOS)reand / or at least one TDD pattern. As shown in FIG. 18, the at least one TDD pattern may comprise a first TDD pattern (e.g., patternl) and / or a second TDD pattern (e.g., pattern ). A TDD pattern of the at least one TDD pattern may be a TDD-UL-DL pattern

[0260] A TDD pattern (e.g., the first TDD pattern or the second TDD pattern) of the at least one TDD pattern may comprise at least one of: a slot configuration period of P msec (e.g., a TDD periodicity); a number of slots dslotswith only downlink symbols (e.g., DL slot(s)); a number of downlink symbols dsym(e.g., DL symbol(s)); a number of slots usiotswith only uplink symbols (e.g., UL slot(s)); a number of uplink symbols usym(e.g., UL symbol(s)). The one or more DL symbols / slots may comprise the number of slots dsiotsand / or the number of downlink symbols dsym. The one or more UL symbols / slots may comprise the number of slots uslotsand / or the number of uplink symbols usytn.

[0261] FIG. 18 also shows a DL slot, an UL slot, and a slot comprising both UL symbol(s)) and DL symbol(s)). For example, the rest of slots / symbols in the TDD pattern (withing the slot configuration period P) not indicated by the TDD pattern as DL / UL slots / symbols may be flexible slots / symbols. The one orDocket No.: 24-1191 PCT more flexible slots / symbols may comprise the rest of slots / symbols in the TDD pattern (withing the slot configuration period P) not indicated by the TDD pattern as DL / UL slots / symbols.

[0262] Corresponding to each TDD pattern of the at least one TDD pattern, a TDD periodicity (e.g., the corresponding slot configuration period of the TDD pattern) may comprise S = P. 2^ref (consecutive) slots with SCS configuration pref. The one or more consecutive slots may comprise= P . 2^ref (consecutive) slots (of the first TDD pattern) and / or S2= P2- 2tlref (consecutive) slots (of the second TDD pattern). The TDD periodicity P may be a summation of a first TDD periodicity Pr(of the first TDD pattern) and a second TDD periodicity P2(of the first TDD pattern), e.g., P = P + P2.

[0263] From Stslots (i=1 corresponding to the first TDD pattern or i=2 corresponding to the second TDD pattern), a first / initial / starting / earliest dslotsslots may comprise the one or more DL slots / symbols. From Stslots, a last / final / ending / latest uslotsslots may comprise the one or more UL slots / symbols. A dsymsymbols after the first dslotsslots may comprise the one or more DL symbols. A usymsymbols before the last uslotsslots may comprise the one or more UL symbols. A remaining (S — dsiots— Usiots)- Nsymb ~ d-sym ~usym symbols may comprise the one or more flexible symbols / slots.

[0264] The one or more TDD configuration parameters may comprise one or more UE-specific TDD configuration parameters (e.g., tdd-UL-DL- Configurationdedicated). The one or more UE-specific TDD configuration parameters may overwrite the one or more flexible symbols / slots of the one or more consecutive slots configured by the tdd-UL-DL-ConfigurationCommon.

[0265] As shown in FIG. 17, the one or more UE-specific TDD configuration parameters may comprise at least one of: one or more UE-specific slot configurations (e.g., slotSpecificConfigurationsToAddModList and / or slotSpecificConfigurationsToReleaseLisf) and / or a slot index for a slot (e.g., slotindex).

[0266] As shown also in FIG. 17, a UE-specific slot configuration (e.g., TDD-UL-DL-SlotConfig) of the one or more UE-specific slot configurations may configure / indicate one or more symbols (e.g., symbols) of a slot with the slot index. The one or more symbols (N symbols) may be configured as flexible symbols by the one or more common TDD configuration parameters. The one or more flexible symbols / slots may comprise the one or more symbols (e.g., symbols) indicated by the UE-specific slot configuration.

[0267] The UE-specific slot configuration may indicate whether the one or more symbols are all DL symbols (e.g., allDownlink) or all UL symbols (e.g., allUplink). The UE-specific slot configuration may (via nrofDownlinkSymbols) indicate one or more first symbols (N1 symbols) of the one or more symbols are DL symbols. The UE-specific slot configuration may (via nrofUplinkSymbols) indicate one or more second symbols (W2 symbols) of the one or more symbols are UL symbols. For example, N-N1-N2 remining symbols may be flexible symbols. The one or more DL symbols / slots may comprise the one or more first symbols (N1 symbols). The one or more UL symbols / slots may comprise the one or more second symbols (N2 symbols). The one or more flexible symbols / slots may comprise N-N1-N2 remining symbols.Docket No.: 24-1191 PCT

[0268] Using / based on the one or more TDD configuration parameters, the wireless device may determine the slot format of each slot / symbol of the plurality of slots. Using / based on the one or more UE-specific TDD configuration parameters, the wireless device may determine a symbol format of each symbol of the plurality of slots. The symbol format may be the slot format.

[0269] In some implementations, the one or more configuration parameters may comprise / indicate a slot format indicator (e.g., SlotFormatlndicator). The one or more configuration parameters may comprise / indicate an SFI-RNTI by sfi-RNTI and with a payload size of DCI format 2_0 by dci-PayloadSize. The one or more configuration parameters may configure a plurality of slot format combinations (e.g., slotFormatCombToAddModList and slotFormatCombToReleaseList) of a cell.

[0270] A base station may indicate a slot format combination of the plurality of slot format combinations via a DCI format 2_0 with a CRC scrambled the SFI-RNTI. The DCI format 2_0 may notify a group of wireless devices one or more slot formats (corresponding to the plurality of slot format combinations). In an example, a slot format may be identified by a corresponding format index. Each symbol in the slot may be a downlink (‘D’) symbol and / or an uplink (‘ U’) symbol and / or a flexible (‘F’) symbol. A slot format 0 may comprise of all downlink ('D') symbols. For example, a slot format 1 may comprise of all uplink (‘U’) symbols. For example, a slot format 55 may comprise of two downlink (‘D’) symbols, followed by three flexible (‘F’) symbols, followed by three uplink ( ) symbols, followed by six downlink (‘D’) symbols. Each symbol may be indicated as downlink (‘D’) or uplink (‘U’) or flexible (‘F’) by one or more UL / DL TDD configurations and / or one or more slot formats.

[0271] The one or more slot formats may be predefined for the wireless device.

[0272] The one or more configuration parameters may configure / indicate the one or more slot formats.

[0273] An SFI-index field value in the DCI format 2_0 may indicate to a wireless device a slot format for a slot of the one or more consecutive slots. For each serving cell (of the one or more serving cells), the one or more configuration parameters may further indicate at least one of the following: an identity of the serving cell; and / or a location of an SFI-index field in the DCI format 2_0; and / or at least one slot format combination (e.g., slotFormatCombinations) of the plurality of slot format combinations.

[0274] For example, a slot format combination may comprise at least one of: at least one slot format of the one or more slot formats (e.g., slotFormats) for the slot format combination; and / or a mapping for the slot format to a corresponding SFI-index field value in the DCI format (e.g., slotFormatCombinationld)] and / or at least one reference SCS configuration.

[0275] The wireless device may use one or more TDD rules when communicating with a base station in a TDD carrier / spectrum (e.g., during the one or more consecutive slots). FIG. 18 also shows some examples of the one or more TDD rules.Docket No.: 24-1191 PCT

[0276] According to / based on the one or more TDD rules, a wireless device may consider (DL) symbols in a DL slot of the plurality of slots to be avail able / allowable for DL receptions. The wireless device may receive DL signals / channels (e.g., PDSCH / SSB / PDCCH or CSI-RS) during / in the DL symbols of the DL slot. The wireless device may not transmit UL signals / channels (even partially) during / in DL symbols of the DL slot.

[0277] According to / based on the one or more TDD rules, a wireless device may consider (UL) symbols in an UL slot of the plurality of slots to be available / allowable for UL transmissions. The wireless device may transmit UL signals / channels (e.g., PUSCH, PUCCH, PRACH, or SRS) during / in the UL symbols of the slot. The wireless device may not receive DL signals / channels (even partially) during / in the UL symbols of the UL slot.

[0278] The one or more configuration parameters may not configure a wireless device to monitor PDCCH for the DCI format 2_0. According to / based on the one or more TDD rules, for a set of (flexible) symbols of a slot (flexible slot) of the plurality of slots, the wireless device may receive DL signals / channels (e.g., PDSCH or CSI-RS) in the set of symbols of the slot. For example, the wireless device receives a DCI scheduling / indicating / triggering the reception of the DL signals / channels in during the set of flexible symbols.

[0279] The one or more configuration parameters may not configure a wireless device to monitor PDCCH for the DCI format 2_0. According to / based on the one or more TDD rules, for a set of (flexible) symbols of a slot (flexible slot) of the plurality of slots, the wireless device may transmit UL signals / channels (e.g., PUSCH, PUCCH, PRACH, or SRS) in the set of symbols of the slot. For example, the wireless device may receive a DCI, a RAR UL grant, fallbackRAR UL grant, or successRAR scheduling / indicating / triggering the transmission of the UL signals / channels in during the set of flexible symbols.

[0280] According to / based on the one or more TDD rules, if a wireless device is configured by higher layers (e.g., RRC / MAC) to receive a DL signal / channel (e g., PDCCH, a PDSCH, a CSI-RS, or a DL PRS) in a set of symbols of the plurality of slots, the wireless device may receive the DL signal / channel based on not detecting / receiving a DCI format scheduling / triggering / indicating a transmission of an UL signal / channel (e.g., a PUSCH, a PUCCH, a PRACH, or a SRS) in at least one symbol of the set of symbols. Based on detecting / receiving the DCI format scheduling / triggering / indicating the transmission of the UL signal / channel in at least one symbol of the set of symbols of the slot, the wireless device may not receive the DL signal / channel (e.g., PDCCH, or a PDSCH, or a CSI-RS, or a DL PRS) in the set of symbols of the slot. The wireless device may transmit the UL signal / channel (e.g., a PUSCH, a PUCCH, a PRACH, or an SRS) in at least one symbol of the set of symbols of the slot.

[0281] According to / based on the one or more TDD rules, for a set of flexible symbols of a flexible slot of the plurality of slots that are indicated, the wireless device may not expect to receive both dedicated higherDocket No.: 24-1191 PCT layer parameters configuring transmission from the wireless device (e.g., Type1 / 2 CG PUSCH, PRACH, MsgA PUSCH, SRS, PUCCH) in the set of flexible symbols and dedicated higher layer parameters configuring reception by the wireless device (e.g., SPS PDSCH, P / SP CSI-RS, SSB, CORESET) in the set of flexible symbols. For example, the one or more configuration parameters may not configure CG-PUSCH transmission occasions and SPS PDSCH reception occasions in the set of flexible symbols.

[0282] According to / based on the one or more TDD rules, for a set of symbols of a slot (of the plurality of slots) indicated to a wireless device for reception of SS / PBCH blocks (SSBs), the wireless device may not transmit UL signals / channels (e.g., PUSCH, PUCCH, PRACH) in the slot if the transmission occasion of the UL signal / channel overlaps with any symbol from the set of symbols. The wireless device may not transmit SRS in the set of symbols of the slot. For example, the one or more TDD configuration parameters do not indicate the set of symbols of the slot as uplink. The set of symbols for receiving the SSB may be configured by the one or more configuration parameters (e.g., by ssb-PositionsIn Burst in SIB1 or by ssb- PositionsInBurst in ServingCellConfigCommon).

[0283] According to / based on the one or more TDD rules, for a set of symbols of a slot (of the plurality of slots) corresponding to a valid PRACH occasion and N_gap symbols before the valid PRACH occasion, the wireless device may not receive the DL signals / channels (e.g., PDCCH, PDSCH, or CSI-RS) in the slot if the reception of the DL signal / channel overlaps with any symbol from the set of symbols. According to / based on the one or more TDD rules, the one or more TDD configuration parameters may not configure the set of symbols of the slot as downlink.

[0284] According to / based on the one or more TDD rules, for a set of symbols of a slot (of the plurality of slots) indicated to a wireless device by the pdcch-ConfigSIB1 in M / B for a CORESET for TypeO-PDCCH CSS set, the wireless device does not expect the set of symbols to be indicated as uplink by the one or more TDD configuration parameters.

[0285] According to / based on the one or more TDD rules, if a DCI schedules / configures / indicates PDSCH reception(s) over multiple slots (e.g., multi-PDSCH receptions or repetitions of a PDSCH), the wireless device may not receive a PDSCH (of the multi-PDSCHs) in a slot of the multiple slots the plurality of slots. The wireless device may not receive a repetition of the PDSCH in the slot. For example, the one or more consecutive slots comprise the multiple slots The slot may comprise at least one UL symbol configured / indicated by the one or more TDD configuration parameters.

[0286] According to / based on the one or more TDD rules, if a DCI schedules / configures / indicates PUSCH transmission(s) over multiple slots (e.g., multi-PUSCH transmissions or repetitions of a PUSCH), the wireless device may not transmit a PUSCH (of the multi-PUSCHs) in a slot of the multiple slots the plurality of slots. The plurality of slots may comprise a plurality of symbols. The wireless device may not transmit a repetition of the PUSCH in the slot. For example, the one or more consecutive slots comprise the multipleDocket No.: 24-1191 PCT slots. The slot may comprise at least one DL symbol configured / indicated by the one or more TDD configuration parameters.

[0287] FIGs. 19A and 19B show an example of subband full-duplex (SBFD) operation as per an aspect of an embodiment of the present disclosure. FIGs. 19A and 19B show two examples of SBFD operations in a carrier. Other examples are also possible. The carrier may be a TDD carrier. The carrier may be an FDD carrier.

[0288] In an example, a SBFD operation of a cell may be referred as (or interchangeably used in some embodiments) a SBFD mode of the cell, a new enhanced duplex mode of the cell, a hybrid TDD / FDD mode of the cell, an enhanced duplexing operation of the cell, configuration one or more UL subbands (and / or one or more DL subbands) via the cell, and / or the like. Using the SBFD operation, a wireless device and / or a base station may reduce UL transmission latency or UL transmission capacity, as the wireless device may be allowed / configured to transmit UL signals / channels in / during SBFD symbols / slots.

[0289] In an example, a SBFD symbol may be referred as (or interchangeably used with) a flexible symbol in a SBFD carrier / serving cell / cell, a SBFD symbol of a carrier / serving cell / cell, a downlink / flexible symbol with a UL subband configured, a symbol (e.g., a downlink or a flexible symbol) with a UL subband configured, a time unit configured with a UL subband, a symbol referred as a SBFD operation, a symbol where a wireless device operates a SBFD operation, a symbol indicated to apply a SBFD operation or a UL band by one or more SBFD configuration parameters and one or more RRC messages indicating to enable the SBFD operation on the symbol, and / or the like. For example, a downlink symbol may be referred as a symbol indicated as downlink via one or more UL / DL TDD configurations. An uplink symbol may be referred as a symbol indicated as uplink via the one or more UL / DL TDD configurations. A flexible symbol may be referred as a symbol indicted as flexible via the one or more UL / DL TDD configurations. A non- SBFD symbol may refer a uplink symbol, a downlink symbol or a flexible symbol based on the one or more UL / DL TDD configurations, but not indicated as a SBFD symbol based on the one or more SBFD configuration parameters. A SBFD symbol may refer a symbol indicated for a SBFD operation based on the one or more SBFD configuration parameters.

[0290] In an example, a SBFD symbol may refer a symbol on a cell / carrier / serving cell. In the example, the cell / carrier / serving cell is enabled / indicated / configured with a SBFD operation. The symbol may be indicated as a downlink symbol or a flexible symbol on the cell / carrier / serving cell via one or more messages (e.g., tdd-UL-DL-ConfigurationCommon and / or tdd-U L-DL-ConfigurationDedicated).

[0291] The SBFD symbols / slots are the DL slots / symbols (configured by the one or more configuration parameters) configured / indicated for the SBFD operation.

[0292] The one or more configuration parameters may configure a wireless device with the SBFD operation in the carrier. The one or more configuration parameters may comprise one or more SBFDDocket No.: 24-1191 PCT configuration parameters. The one or more TDD configuration parameters may comprise one or more SBFD configuration parameters.

[0293] The wireless device may be in an RRC connected state. For example, the one or more SBFD configuration parameters may indicate / configure / enable the wireless device for the SBFD operation only when the wireless device is in the RRC connected state. The wireless device may perform a handover procedure (to handover from a source cell of the one or more serving cells to a target cell) based on the one or more SBFD configuration parameters.

[0294] The wireless device may be in an RRC idle / inactive state. For example, the one or more SBFD configuration parameters may indicate / configure / enable the wireless device for the SBFD operation when the wireless device is in the RRC idle / inactive state. For example, during the RRC idle / inactive state of the wireless device, the wireless device may perform an initial access procedure (e.g., a random access procedure for the initial access) based on the one or more SBFD configuration parameters. For example, during the RRC idle / inactive state of the wireless device, the wireless device may perform a small data transmission (SDT) procedure based on the one or more SBFD configuration parameters. For example, during the RRC idle / inactive state of the wireless device, the wireless device may perform SRS transmission for positioning procedure based on the one or more SBFD configuration parameters.

[0295] The one or more SBFD configuration parameters may comprise one or more cell-specific (or common) SBFD configuration parameters.

[0296] The one or more SBFD configuration parameters may comprise one or more UE-specific (or dedicated) SBFD configuration parameters.

[0297] The one or more SBFD configuration parameters may configure one or more SBFD or uplink (UL) subbands. In an example, the wireless device may determine one or more DL subbands based on the one or more UL subbands (e.g., frequency regions of an active downlink BWP excluding the one or more UL subbands and guard band(s) is considered as the one or more DL subbands). The one or more SBFD configuration parameters may configure / indicate a SBFD / UL subband time locations of a SBFD / UL subband (of the one or more SBFD / UL subbands). The one or more SBFD configuration parameters may configure / indicate a SBFD / UL subband frequency locations of the SBFD / UL subband. For example, the SBFD / UL subband time locations may be within a first period. The first period may be a SBFD period (or a SBFD periodicity). In an example, a set of contiguous PRBs are configured as a SBFD or UL subband, where the wireless device may determine SBUL (UL subband) based on the set of contiguous PRBs and SBUL (DL subband) based on the active downlink BWP and the set of contiguous PRBs.

[0298] The one or more SBFD configuration parameters may configure / indicate a set of SBFD symbols in time locations. The one or more SBFD configuration parameters may configure / indicate one or more DL subbands in a SBFD symbol, and / or one or more UL subbands in a SBFD symbol. The wireless deviceDocket No.: 24-1191 PCT may determine one or more guard frequency region between a DL subband of the one or more DL subbands and a UL subband of the one or more UL subbands based on the one or more SBFD configuration parameters, e.g ., remaining PRBs not belonging to any DL subband or any UL subband, between two adjacent DL subband and UL subband, may be considered as a guard PRB for the guard frequency region.

[0299] The first period may be based on the at least one TDD pattern. For example, the first period may be the TDD periodicity. The first period may be larger than the TDD periodicity. The first period may be smaller than the TDD periodicity. The one or more SBFD configuration parameters may indicate / configure the first period.

[0300] The first period may be equal to a multiplication of a second value and the TDD periodicity. The one or more SBFD configuration parameters may indicate / configure the second value.

[0301] The first period may be based on the first TDD pattern. For example, the first period may be the first TDD periodicity P (of the first TDD pattern). Based on the one or more SBFD configuration parameters not indicating the first period, the wireless device may set the first period to a default value. The default value may be the first TDD periodicity.

[0302] The first period may be based on the second TDD pattern. For example, the first period may be the second TDD periodicity P2(of the second TDD pattern). Based on the one or more SBFD configuration parameters not indicating the first period, the wireless device may set the first period to the default value. The default value may be the second TDD periodicity.

[0303] In some examples, the default value may be a summation of the first TDD periodicity P1and the second TDD periodicity P2.

[0304] The one or more SBFD configuration parameters may further configure / indicate a second period. The second period may correspond to the second TDD pattern. The first period may correspond to the first TDD pattern. When the second period is absent from the one or more SBFD configuration parameters (e.g., the one or more SBFD configuration parameters not indicating the second period), the wireless device may determine the SBFD subband(s) is only configured within / correspond to the first TDD pattern.

[0305] It is noted that a SBFD subband, SBUL and UL subband are used interchangeably throughout the specification. SBFD subband DL, SBDL, and DL subband are used interchangeably throughout the specification.

[0306] In another example, when the second period is absent from the one or more SBFD configuration parameters (e.g., the one or more SBFD configuration parameters not indicating the second period), the wireless device may determine the SBFD subband(s) is configured within / correspond to the first TDD pattern and the second TDD pattern.Docket No.: 24-1191 PCT

[0307] In another example, when the first period is absent from the one or more SBFD configuration parameters (e.g., the one or more SBFD configuration parameters not indicating the second period), the wireless device may determine the SBFD subband(s) is only configured within / correspond to the second TDD pattern and the second TDD pattern.

[0308] In another example, when the first period is absent from the one or more SBFD configuration parameters (e.g., the one or more SBFD configuration parameters not indicating the second period), the wireless device may determine the SBFD subband(s) is only configured within / correspond to the second TDD pattern.

[0309] The one or more SBFD configuration parameters may indicate that a slot / symbol of a set of slots / symbols comprise of at least one SBFD slot / symbol. The one or more SBFD configuration parameters may indicate that a slot / symbol of the set of slots / symbols comprise of at least one non-SBFD slot / symbol. The plurality of slots may comprise the set of slots / symbols. A slot / symbols of the set of slots / symbols may be a DL slot (of the one or more DL slots) or a flexible slot (of the one or more flexible slots / symbols).

[0310] An SBFD slot / symbol of the at least one SBFD slot / symbol may be a DL slot / symbol (of the one or more DL slots / symbols) or a flexible slot / symbol (of the one or more flexible slots / symbols) configured for the SBFD operation. The SBFD slot / symbol may be within the SBFD time locations.

[0311] A non-SBFD slot / symbol of the at least one non-SBFD slot / symbol may be a DL slot / symbol (of the one or more DL slots) or an UL slots / symbol (of the one or more UL slots / symbols) or a flexible slot / symbol (of the one or more flexible slots / symbols). The non-SBFD symbol / slot may not be within the SBFD time locations.

[0312] For the SBFD subband frequency locations, FIGs. 19A and 19B provide two examples (or configurations). As shown in FIG. 19A / 19B, a maximum number of UL subbands (UL SBs) for SBFD operation in an SBFD symbol within a TDD carrier is one.

[0313] A first example may correspond to a first (TDD) carrier. An UL subband in an SBFD symbol / slot may be located at one side (e.g., a lowest frequency region or a highest frequency region of a carrier frequency range) of the first carrier. The first example may be referred to by a first type of SBFD operation. In the first type of the SBFD operation, the SBFD symbol / slot (e.g., a first type of SBFD symbol / slot) may correspond to / comprise a D-U or a U-D partitioning / configuration of frequency resources of the SBFD symbol / slot. The carrier may be the first carrier.

[0314] A second example may correspond to a second (TDD) carrier. An UL subband in an SBFD symbol / slot may be located at the middle part of the second carrier. The second example may be referred to by a second type of SBFD operation. In the second type of the SBFD operation, the SBFD symbol / slot (e.g , a second type of SBFD symbol / slot) may correspond to / comprise a D-U-D partitioning / configuration of frequency resources of the SBFD symbol. The carrier may be the second carrier.Docket No.: 24-1191 PCT

[0315] The D-U or the U-D or the D-U-D partitioning of the frequency resources of the SBFD symbol may provide / indicate examples of the SBFD subbanci frequency location(s). The one or more SBFD configuration parameters may indicate / configure the SBFD subband frequency location(s). The SBFD subband frequency location(s) may correspond to each SBFD symbol / slot within the SBFD subband time locations. In an example, the one or more SBFD configuration parameters may be received via a cellspecific signaling such as SIB, MIB or via a common search space or via a group-common DCI.

[0316] The SBFD symbol / slot may comprise an UL subband and at least one DL subband. The one or more SBFD configuration parameters may configure / indicate the SBFD subband frequency locations. The SBFD subband frequency locations may comprise frequency locations of UL subband and / or frequency locations of DL subband(s) (e.g., the at least one DL subband). The frequency locations of the UL subband may comprise at least one subband frequency-domain resources (e.g., PRBs or REs or subcarriers).

[0317] The frequency locations of UL subband may comprise a first set of resource blocks (RBs). The first set of RBs may comprise a first set of resource elements (REs) or a first set of subcarriers. The first set of resource blocks may comprise / be UL subband frequency resources (subcarriers). The first set of resource blocks may correspond to at least a cell-specific UL subband and / or a UE-specific UL subband. The UL subband frequency resources for each SBFD symbol / slot within the SBFD subband time locations may be the first set of RBs.

[0318] In the present disclosure, a set of RBs may interchangeably be used / referred to by “a set of PRBs’’ or "a set of subcarriers” or "a set of REs” or "a set of frequency resources”.

[0319] The frequency locations of DL subband(s) may comprise a second set of resource blocks (RBs). The second set of RBs may comprise a second set of resource elements (REs) or a second set of subcarrers. The second set of resource blocks may comprise / be DL subband frequency resources. The second set of resource blocks may correspond to at least cell-specific DL subband(s) and / or UE-specific DL subband(s). The DL subband(s) frequency resources may comprise / indicate (or be) the frequency locations of DL subband(s). The DL subband frequency resources for each SBFD symbol / slot within the SBFD subband time locations may be the second set of RBs.

[0320] In one example, the one or more SBFD configuration parameters may configure / indicate the first set of RBs and the second set of RBs. The wireless device may determine / derive a third set of resource blocks (RBs) corresponding to frequency locations of Guardband(s). The frequency locations of Guardband(s) are not within the UL subband or DL subband(s). The third set of RBs may comprise a third set of REs or a third set of subcarriers.

[0321] In another example, the one or more SBFD configuration parameters may configure / indicate the first set of RBs and the third set of RBs. The wireless device may determine / derive the second set ofDocket No.: 24-1191 PCT resource blocks (RBs), e.g., by excluding the first set of RBs and the third set of RBs from RBs of an active DL BWP (or the carrier).

[0322] In yet another example, the one or more SBFD configuration parameters may configure / indicate the second set of RBs and the third set of RBs. The wireless device may determine / derive the first set of resource blocks (RBs), e.g., by excluding the second set of RBs and the third set of RBs from RBs of an active UL BWP (or the carrier). The active UL BWP may correspond to / associated with the active DL BWP.

[0323] The frequency locations of Guardband(s)f or each SBFD symbol / slot within the SBFD subband time locations may be the third set of RBs.

[0324] One or more RBs of the active RBs of the active DL BWP (or the carrier) may comprise a set of (e.g , sum, union) the first set of RBs, the second set of RBs, and the third set of RBs. The first set of RBs may belong to RBs of the active UL BWP.

[0325] The second set of resource blocks / resource elements may comprise contiguous resource blocks / elements (e.g., for the D-U or U-D partitioning of the frequency resources) or non-contiguous blocks / elements (e.g., D-U-D partitioning of the frequency resources).

[0326] The third set of resource blocks / elements may be contiguous, e.g., when only one Guardband (e.g., the D-U or U-D partitioning of the frequency resources) is configured in the SBFD symbol / slot. The set of third resource blocks / elements may be non-contiguous, e.g., when at least two Guardbands (e.g., D- U-D partitioning of the frequency resources) are configured in the SBFD symbol / slot.

[0327] The one or more SBFD configuration parameters may indicate / configure Guardband(s) to reduce interference leakage between / among UL transmissions in the UL subband frequency resources in the SBFD symbol(s) / slot(s) (at a wireless device or a base station) and DL receptions in the DL subband frequency resources in the SBFD symbol(s) / slot(s) (at the wireless device or the base station).

[0328] As also shown in FIG. 20, the UL subband frequency resources (e.g., the first set of RBs) within the active UL BWP may also be referred to by UL usable PRBs. The UL usable PRBs may comprise UL usable resource blocks / elements. The wireless device may determine the UL usable PRBs (or the first set of RBs) as an intersection between the UL subband frequency resources configured via the SBFD configuration and the active UL BWP in the SBFD symbol(s) / slot(s). In an example, the wireless device may determine the UL usable PRBs based on the one or more SBFD configuration (e.g , frequency location of a UL subband) and one or more guardbands that the wireless device is required for supporting a SBFD operation.

[0329] The DL subband(s) frequency resources (e.g., the second set of RBs) within the active DL BWP may also be referred to by DL usable PRBs. The DL usable PRBs may comprise DL usable resource blocks / elements. The wireless device may determine the DL usable PRBs as an intersection between the DL subband(s) frequency resources and active DL BWP in the SBFD symbol(s) / slot(s).Docket No.: 24-1191 PCT

[0330] In some examples, the one or more SBFD configuration parameters may (explicitly or implicitly) configure / indicate the UL / DL usable PRBs within the active UL / DL BWP in the SBFD symbol(s) / slot(s).

[0331] The wireless device may use the UL usable PRBs for UL transmissions (e.g., transmission of UL signals / chan nels) during the at least one SBFD symbol / slot. During the at least one SBFD symbol / slot, DL receptions outside of the DL usable PRBs may not be allowed, e.g., the wireless device may not use the UL usable PRBs and / or the Guardband(s) for DL receptions during the at least one SBFD symbol / slot.

[0332] The wireless device may use the DL usable PRBs for DL receptions (e.g., reception of DL signals / channels) during at least one SBFD symbol / slot. UL transmissions outside the UL usable PRBs may not be allowed, e.g., the wireless device may not use the DL usable PRBs and / or the Guardband(s) for UL transmissions during at least one SBFD symbol / slot

[0333] For example, a maximum number of UL subbands (UL SBs) for SBFD operation in an SBFD symbol within a TDD carrier is a first number. The one or more SBFD configuration parameters may configure / indicate the first number. When the first number is absent / missing from the one or more SBFD configuration parameters, the wireless device may consider a default value for the first number. The default value may be one.

[0334] For example, the first number may be one. The first number may be more than one. The first number may be greater than or equal to one. In one example, if the first number is set to zero, the wireless device may consider / assume the SBFD symbol / slot as a DL symbol / slot or a flexible symbol / slot. In another example, if the first number is set to zero, the wireless device may consider / assume the SBFD symbol / slot as an UL symbol / slot.

[0335] As also shown in FIG. 20, the wireless device may determine a link direction (e.g., a DL link direction or an UL link direction) during / in (or corresponding to) a SBFD symbol / slot. The SBFD symbol / slot may comprise both the DL usable PRBs and the UL usable PRBs. By determining the link direction during / in the SBFD symbol / slot the wireless device may determine whether to receive DL signals / channels using / via the DL usable PRBs during / in the SBFD symbol / slot or transmit UL signals / channels using / via the UL usable PRBs during / in the SBFD symbol / slot.

[0336] As shown in FIG. 20, when the link direction is the DL link direction corresponding to / in a SBFD symbol / slot #1 (of the at least one SBFD symbol / slot), the wireless device may determine to receive DL signals / channels using / via the DL usable PRBs during / in the SBFD symbol / slot #1 . In an example, one or more SBFD configuration parameters may indicate a flexible symbol (‘F’) to indicate a SBFD symbol. In an example, a SBFD symbol may be considered as a flexible symbol. In an example, a SBFD symbol is called as a semi-flexible symbol. In an example, a SBFD symbol may be called as pseudo-downlink symbol. In an example, a SBFD symbol may be referred as a pseudo-uplink symbol. A symbol indicated by the one or more SBFD configuration parameters to apply (or to use) one or more UL subbands may be referred as aDocket No.: 24-1191 PCTSBFD symbol in the specification. In an example, a SBFD symbol, a wireless device may determine useable downlink PRBs and / or usable uplink PRBs which may be different from an active downlink bandwidth part and / or an active uplink bandwidth part respectively. The usable downlink PRBs or uplink PRBs may be same to PRBs of the active downlink bandwidth part or the active uplink bandwidth in a non- SBFD symbol.

[0337] As shown in FIG. 20, when the link direction is the UL link direction corresponding to / in a SBFD symbol / slot #2 (of the at least one SBFD symbol / slot), the wireless device may determine to transmit UL signals / channels using / via the UL usable PRBs during / in the SBFD symbol / slot #2.

[0338] The link direction of an SBFD symbol / slot of the at least one SBFD symbol / slot may be semi- statically configured / indicated by the one or more SBFD configuration parameters. The wireless device may determine the link direction (e.g., the DL link direction or the UL link direction) corresponding to the SBFD symbol / slot based on the one or more SBFD configuration parameters (e.g., explicit or semi-static manner / approach / technique). The one or more SBFD configuration parameters may indicate / configure the link direction of the SBFD symbol / slot semi-statistically (not dynamically). For example, the one or more SBFD configuration parameters indicate / configure a first bitmap The first bitmap may indicate / configure the link direction of a first set of SBFD slot(s) / symbol(s) (e.g., comprising the SBFD symbol / slot #1), within the SBFD time locations, as the DL link direction. The first bitmap may indicate / configure the link direction of a second set of SBFD slot(s) / symbol(s) (e.g., comprising the SBFD symbol / slot #2), within the SBFD time locations, as the UL link direction. The first bitmap may be applicable for the first period and / or the second period. Union of the first set of SBFD slots / symbols and the second set of SBFD slots / symbols may comprise (all) SBFD symbols / slots configured / indicated within the SBFD time locations.

[0339] In another example, the wireless device may determine the link direction (e.g., the DL link direction or the UL link direction) corresponding to the SBFD symbol / slot #1 based on a scheduling indication (e.g., dynamically). For example, the scheduling indication (e g., RRC or DCI) may indicate reception of DL signals / channels during an SBFD symbol / slot #1 of the at least one SBFD symbol / slot. The wireless device may, based on the scheduling indication, determine the link direction of the SBFD symbol / slot #1 is the DL link direction. For example, the determining the link direction of the SBFD symbol / slot #1 as the DL link direction may further based on the one or more SBFD configuration parameters indicating / configuring (semi-statistically) the link direction corresponding to the SBFD symbol / slot #1 as the DL link direction.

[0340] In one case, the one or more SBFD configuration parameters may not indicate / configure (semi- statistically) the link direction corresponding to the SBFD symbol / slot #1 . For example, the scheduling indication (e.g., RRC or DCI) may indicate reception of DL signals / channels during an SBFD symbol / slot #1 of the at least one SBFD symbol / slot. The wireless device may, based on the scheduling indication and the one or more SBFD configuration parameters not indicating / configuring (semi-statistically) the link directionDocket No.: 24-1191 PCT corresponding to the SBFD symbol / slot #1 , determine the link direction of the SBFD symbol / slot #1 is the DL link direction.

[0341] In one case, the one or more SBFD configuration parameters may indicate / configure (semi- statistically) the link direction corresponding to the SBFD symbol / slot #1 as the UL link direction. For example, the scheduling indication (e.g., RRC or DCI) may indicate reception of DL signals / channels during an SBFD symbol / slot #1 of the at least one SBFD symbol / slot. The wireless device may, based on the scheduling indication and the one or more SBFD configuration parameters indicating / configuring (semi- statistically) the UL link direction corresponding to the SBFD symbol / slot #1 , determine the link direction of the SBFD symbol / slot #1 is the DL link direction.

[0342] The scheduling indication (e.g., RRC or DCI) may indicate transmission of UL signals / channels during an SBFD symbol / slot #2 of the at least one SBFD symbol / slot. The wireless device may, based on the scheduling indication, determine the link direction of the SBFD symbol / slot #2 is the UL link direction. For example, the determining the link direction of the SBFD symbol / slot #2 as the UL link direction may further based on the one or more SBFD configuration parameters indicating / configuring (semi-statistically) the link direction corresponding to the SBFD symbol / slot #2 as the UL link direction.

[0343] In one case, the one or more SBFD configuration parameters may not indicate / configure (semi- statistically) the link direction corresponding to the SBFD symbol / slot #2. For example, the scheduling indication (e.g., RRC or DCI) may indicate transmission of UL signals / channels during the SBFD symbol / slot #2 of the at least one SBFD symbol / slot. The wireless device may, based on the scheduling indication and the one or more SBFD configuration parameters not indicating / configuring (semi-statistically) the link direction corresponding to the SBFD symbol / slot #2, determine the link direction of the SBFD symbol / slot #2 is the UL link direction.

[0344] In one case, the one or more SBFD configuration parameters may indicate / configure (semi- statistically) the link direction corresponding to the SBFD symbol / slot #2 as the DL link direction. For example, the scheduling indication (e.g., RRC or DCI) may indicate transmission of UL signals / channels during the SBFD symbol / slot #2 of the at least one SBFD symbol / slot. The wireless device may, based on the scheduling indication and the one or more SBFD configuration parameters indicating / configuring (semi- statistically) the DL link direction corresponding to the SBFD symbol / slot #2, determine the link direction of the SBFD symbol / slot #2 is the UL link direction.

[0345] FIG. 21 illustrate examples as per aspects of embodiments of the present disclosure. In an example, a base station (BS(s)) may communicate with a wireless device (UE). For example, the base station configures a cell (CC#1 ) to the wireless device.

[0346] The base station may configure a TAG for the cell.Docket No.: 24-1191 PCT

[0347] In an example, downlink, uplink and sidelink transmissions may be organized into frames. A duration of a frame may be 10 msec. The duration of the frame may be a number of a sample duration (Tc). The frame may comprise M subframes (e.g., M = 10). Each subframe may comprise N number of symbols based on a subcarrier spacing of a carrier. For example, N may be a function of a number of slots, based on the subcarrier spacing, and a number of symbols in a slot. For example, with 15 kHz subcarrier spacing, a subframe may comprise N = 14 symbols with normal CP, and N = 12 with extended CP.

[0348] In an example, the carrier may comprise a first set of frames in the uplink and a second set of frames in the downlink on the carrier.

[0349] An uplink frame number #i for transmission from a wireless device may start a timing advance (T_TA), as illustrated in FIG. 21 , before a start of a corresponding downlink frame (e.g., Downlink frame #i) at the wireless device (e.g., a time T3). In the example, a time corresponding to the start of a downlink frame #i at the wireless device is at T3. In the example, the start time of the downlink frame #i (T3) at the wireless device may be determined based on a propagation delay (e.g., N_TA / 2) between the base station and the wireless device and a timing of a downlink frame #i at the base station (e.g., T2). For example, a gap between a start time of a downlink frame #i at the base station (T2) and the start time of the downlink frame #i at the wireless device is a propagation delay or a timing advance value (e.g., N_TA * Tc) divided by 2 (to compensate one way propagation delay).

[0350] The wireless device may determine / compute / update / maintain the timing advance (T_TA) based on a timing advance value (N_TA) and a timing advance (TA) offset (N_TA_offset). For example, T_TA = (N_TA + N_TA_offset) *Tc. For example, T_TA = (N_TA + N_TA_offset + N_TA_adj_common + N_TA_adj_UE) *Tc. The base station may determine the timing advance value (N_TA*Tc) based on estimation / measurement of a round-trip-time (e.g., based on a propagation delay) between the base station and the wireless device.

[0351] For example, the wireless device may receive one or more RRC messages indicating / comprising a ta-Common, a ta-CommonDrift and a ta-Common DriftVariant. The wireless device may determine N_TA_adj_common as zero in response to not being provided with the ta-Common, the ta-CommonDrift and the ta-CommonDriftVariant via the one or more RRC messages. The one or more RRC messages may indicate one or more serving-satellite-ephemeris-related parameters The wireless device may determine N_TA_adj_UE in response to receiving the one or more RRC messages indicating / comprising the one or more serving-satellite-ephemeris-related parameters. In other cases, the wireless device may determine N_TA_adj_UE as zero.

[0352] A start time of an uplink frame #i at the wireless device (e.g., TO) may be determined based on the timing advance (T_TA) and the start time of the downlink frame #i at the wireless device (e.g., T3). The gap between T1 and T3 may be the timing advance.Docket No.: 24-1191 PCT

[0353] A start time of the uplink frame #i at the base station (e.g., T1) may be TO + a propagation delay from the wireless device to the base station (or TO + N_TA*Tc / 2).

[0354] The wireless device may apply the timing advance (T_TA) for an uplink transmission in the uplink frame #i for a PUCCH, a PUSCH (not comprising a msgA) or an SRS. The wireless device may apply only a TA offset value (e.g., N_TA_offset*Tc) for an uplink transmission in the uplink frame #i for a PRACH or a PUSCH comprising a msgA. In an example, a msgA may comprise a PRACH preamble and a PUSCH comprising a contention resolution payload. In an example, the wireless device may apply the TA offset value (N_TA_offset *Tc) for both the PRACH preamble of the msg A and the PUSCH comprising the contention resolution payload.

[0355] In an example, the one or more RRC messages may comprise / indicate the TA offset (N_TA_offset, TA_offset, TA offset). In some cases, the one or more RRC messages may not comprise one or more parameters of the timing advance (TA) offset. In such a case, the wireless device may determine the TA offset (e.g., N_TA_offset *Tc) for the cell based on one or more predefined or pre-configured values. In an example, at least a TGA is associated with the

[0356] For example, the base station may transmit one or more RRC messages comprising / indicating a N_TA_offset value for a cell. The wireless device may determine a TA offset value based on the N_TA_offset. In response to not receiving the N_TA_offset from the base station, the wireless device may determine N_TA_offset based on one or more (pre-)configured / determined values. For example, the wireless device may determine N_TA_offset as 25600, where N_TA_offset * Tc may correspond to 13 us for a serving cell operating in a TDD duplex mode and N_TA_offset as 0 for a serving cell operating in a FDD duplex mode in a frequency range 1 (e.g., below 7 GHz). In an example, the wireless device may determine N_TA_offset as 39936 that corresponding to 20 us for a serving cell if the serving cell may operate in a frequency band where LTE base station may operate.

[0357] In an example, the cell may be associated with a plurality of TAGs. The TA offset may be associated with a TAG of the plurality of TAGs that has a lowest index among those of the plurality of TAGs. The TA offset may be associated with a TAG, of the plurality of TAGs, that is associated with a coreset pool with a coreset pool index = 0. The TA offset may be associated with a TAG, of the plurality of TAGs, that is associated with a primary cell identifier (PCI) of the cell. The TA offset may be associated with a TAG, of the plurality of TAGs, that is associated with a TCI state of a CORESET #0 of the cell.

[0358] In the specification, a TA offset (or a TA offset, N_TA_offset, TA_offset) may be associated with a TAG of a cell, where the TAG is associated with a coreset pool with a coreset pool index = 0, a PCI of the cell, a TCI state of a CORESET#0 of the cell, and / or the like. A second TA offset (or a second TA offset, N_TA_offset2, TA_offset2) may not be associated with the TAG of the cell or may be associated with the TAG of the cell.Docket No.: 24-1191 PCT

[0359] In an example, a wireless device may be configured with a first UL carrier and a second UL carrier for a serving cell. In an example, the first UL carrier is an UL carrier. The second UL carrier is a supplemental UL (SUL) carrier. The wireless device may determine a single TA offset value applicable to both the first UL carrier and the second UL carrier in such a case. The wireless device may consider it as an error case, if the base station configures the second TA offset for the serving cell that is configured with the first UL carrier and the second UL carrier. In the example, the second UL carrier may be a supplemental uplink (SUL) carrier.

[0360] In an example, a wireless device may determine a single timing advance (TA) value (e.g., T_TA) for one or more serving cells that are associated / configured with or belong to a same TA group (TAG).

[0361] In an example, the base station may transmit one or more downlink control messages (e.g., MAC CE, RRC, DCI) comprising a timing advance command for a TAG. The one or more downlink control messages may comprise one or more MAC CEs that comprise the timing advance command for the TAG. The timing advance command may comprise one or more timing advance values. The one or more downlink control messages and / or the timing advance command (TAG) may comprise or indicate a TAG ID of the TAG.

[0362] In response to receiving the one or more downlink control messages for the TAG, the wireless device may update / adjust / determine an uplink timing for one or more PUSCH / SRS / PUCCH transmissions on one or more serving cells, that share the TAG, based on the one or more timing advance values and a value of a TA offset of the TAG. When a serving cell of the one or more serving cells is configured with a first TAG and a second TAG, the wireless device may be configured / indicated with a first TA offset and a second TA offset. The first TA offset is associated with the first TAG and the second TA offset is associated with the second TAG. The wireless device may apply the first TA offset or the second TA offset based on the TAG ID on the TAG and / or the one or more downlink control messages.

[0363] In response to receiving the one or more downlink signal, the wireless device may determine / update a timing advance (T_TA) based on the TA offset (N_TA_offset) and the one or more timing advance values.

[0364] The TA offset for a serving cell of the one or more serving cells may be configured via one or more RRC messages or may be determined based on one or more pre-defined values. In an example, the serving cell may be a primary cell of a cell group. In an example, the serving cell may be a secondary cell.

[0365] In an example, the wireless device may determine a TA offset based on a duplexing mode of a serving cell and / or a frequency band that the serving cell operates. For example, the wireless device may determine the TA offset as zero / 0 in response to the serving cell operating in the frequency band lower than 7GHz based on FDD duplexing mode. The wireless device may determine a non-zero value for the TA offset in response to the serving cell operating based on TDD duplexing mode.Docket No.: 24-1191 PCT

[0366] In an example, a wireless device may receive a downlink data (e.g., via PDSCH) comprising a MAC CE (e.g., comprising a TAG ID and a timing advance value) to update a timing advance, of a TAG associated with the TAG ID, based on a current uplink timing for the TAG. The wireless device may update a timing advance (T_TA) of the TAG based on the timing advance value. For example, the wireless device may determine a new value N_TA_new as N_TA_old (N_TA value at current) + (the timing advance value- 31) * 16 * 64 / M, where M is power (2, u) and u is determined based on a subcarrier spacing of the serving cell compared to 15 kHz (e.g., u = 2 in case of 60 kHz).

[0367] For example, an updated timing advance may be computed / determined based on a current timing advance and a received timing advance command / timing advance value. The received timing advance command and / or timing advance value may be conveyed / transmitted / delivered via one or more MAC CEs and / or RARs.

[0368] The wireless device may update a timing advance that is addition to a current timing advance and (a timing advance value - 31) * 16*64 / power (2, u). In the example, u may be determined based on a subcarrier spacing of an active BWP of a serving cell. For example, the subcarrier spacing of the active BWP = power (2, u) * 15 kHz.

[0369] The timing advance value via the MAC CE may comprise a value from {0, 1 , 2, ... , 63}. A subcarrier spacing of an active BWP of the serving cell may be power (2, u) * 15 kHz.

[0370] For example, a wireless device may switch from a first BWP to a second BWP as an active BWP of a serving cell, the wireless device may use a subcarrier spacing of the second BWP to determine a timing advance or to apply a timing advance command / timing advance value for a TAG for the serving cell.

[0371] In an example, the wireless device may receive a second TAC (e.g., comprising an absolute timing advance value), comprising a second timing advance value, that indicates adjustments of a current N_TA (N_TA_old) to a new N_TA (N_TA_new). The wireless device may update the new timing advance (N_TA_new) as the second timing advance value * 16 / 64 / power(2,u) *Tc.

[0372] In an example, a wireless device may receive a RAR comprising a TAC. The RAR may indicate a TAG ID of a TAG to apply the TAC. The TAC may comprise a timing advance value. In response to receiving the RAR, the wireless device may replace a current timing advance of the TAG with a new timing advance determined / computed based on the timing advance value.

[0373] In response to the receiving the RAR, the wireless device may apply a timing advance (T_TA) for a transmission other than a PUSCH scheduled by a RAR UL grant or a fallbackRAR UL grant or a PUCCH with HARQ-ACK information in response to a successRAR. The wireless device may transmit the transmission via a cell associated with the TAG.Docket No.: 24-1191 PCT

[0374] In an example, for operation with a single TAG for a serving cell, if two adjacent slot overlap based on a timing advance adjustment / command or based on updating a current N_TA value, the wireless device may reduce a latter slot duration. The wireless device may not change a N_TA during a transmission.

[0375] FIG. 22 illustrates examples as per aspects of embodiments of the present disclosure.

[0376] A wireless device may support a plurality of TAGs for a serving cell. For example, the wireless device supports two TAGs for a serving cell. The serving cell may operate a multi-TRP scenario. A base station of the serving cell comprises a first TRP (TRP#1) and a second TRP (TRP#2). The wireless device may indicate to support the plurality of TAGs for the serving cell (e.g., via multiDCI-lnterCellMultlTRP- TwoTA).

[0377] The base station may transmit one or more RRC messages indicating / comprising parameters indicating a plurality of coreset pools. For example, the plurality of coreset pools comprise a first coreset pool and a second coreset pool. In an example, a first coreset pool (Coreset Pool#1 ) may correspond to the first TRP. In an example, a coreset pool index of the first coreset pool may be indicated via the one or more RRC messages. In an example, the wireless device may determine a coreset pool index of the first coreset pool as a predefined value (e.g., zero / 0) in response to not being indicated / configured with the coreset pool index via the one or more RRC messages. In an example, the one or more RRC messages may not indicate the first coreset pool. The wireless device may determine a coreset pool index of one or more coresets as a predetermined value, where the first coreset pool comprises the one or more coresets.

[0378] A second coreset pool (Coreset Pool#2), of the plurality of coreset pools, may correspond to the second TRP. In an example, a second coreset pool index of the second coreset pool may be indicated via the one or more RRC messages.

[0379] In an example, the first coreset pool may be associated with or be configured with or be tied with a first TCI state.

[0380] In an example, the second coreset pool may be associated with or be configured with or be tied with a second TCI state.

[0381] The wireless device may be equipped with a plurality of panels. In the example, the wireless device is equipped with a first panel (Panel#1 ) and a second panel (Panel#2) . The first panel and the second panel may be a same or different.

[0382] In the specifications, a spatial domain filter parameter may be referred as a spatial domain filter, a spatial RX parameter, a spatial RX filter, a spatial parameter, and / or the like.

[0383] In an example, the first panel may be associated with or be configured with or be tied with a first spatial domain filter (Spatial Domain Filter #1).

[0384] In an example, the second panel may be associated with or be configured with or be tied with a second spatial domain filter (Spatial Domain Filter #2).Docket No.: 24-1191 PCT

[0385] The one or more RRC messages may configure / indicate / comprise parameters of a first TAG and a second TAG for the serving cell. In an example, the first TAG of the plurality of TAGs may be associated with or be configured with or be tied with the first spatial domain filter (Spatial Domain Filter #1).

[0386] In an example, the second TAG of the plurality of TAGs may be associated with or be configured with or be tied with the second spatial domain filter (Spatial Domain Filter #2).

[0387] In an example, the wireless device may receive one or more second RRC messages (RRC message(s) in FIG. 22) indicating / comprising a TA offset (N_TA_offset) for a serving cell (e.g., a parameter of n-TimingAdvanceOffset for the serving cell). When the wireless device is provided / configured with a plurality of coreset pools for the serving cell, the one or more second RRC messages may indicate a second TA offset (e.g., a second N_TA_offset) for the serving cell (e.g., a second parameter of n- TimingAdvanceOffset2).

[0388] The wireless device may be provided / configured with the plurality of coreset pools. The plurality of coreset pools may comprise a first coreset pool with a first corset pool index being 0 (zero) and a second coreset pool with a second coreset pool index being 1 (one). The wireless device may be provided / configured with the plurality of coreset pools that comprise a first coreset without a first coreset pool index being configured via RRC signaling and a second coreset with a second coreset pool index being configured via RRC signaling as one / 1 .

[0389] The wireless device may apply / use the TA offset for one or more transmissions associated with or based on or with one or more first spatial domain filters. In an example, the wireless device may determine one or more transmission configuration / parameters based on the one or more first spatial domain filters. The one or more first spatial domain filters may be associated with or corresponding to one or more first TCI states. For example, the one or more first spatial domain filters comprise the first spatial domain filter (Spatial Domain Filter #1). The one or more first TCI states comprise the first TCI state. The first TCI state is associated with the first coreset pool (Coreset Pool #1).

[0390] In an example, the wireless device may apply / use the second TA offset for one or more second transmissions associated with or based on or with one or more second spatial domain filters. The one or more second spatial domain filters may be associated with or corresponding to one or more second TCI states. For example, the one or more second spatial domain filters comprise the second spatial domain filter (Spatial Domain Filter #2). The one or more second TCI states comprise the second TCI state. The second TCI state is associated with the second coreset pool (Coreset Pool #2).

[0391] In another example, the wireless device may receive the one or more RRC messages indicating / comprising the second TA offset for one or more second transmissions associated with or based on or with one or more second spatial domain filters. The one or more second spatial domain filters may be associated with or corresponding to one or more second TCI states or one or more SSB receptionsDocket No.: 24-1191 PCT associated with / tied with / corresponding to a second physical cell index (e.g., physCell Id) that is different from a first physical cell index of the serving cell. The wireless device may apply / use the TA offset for the one or more first uplink transmissions associated with or based on or with one or more first spatial domain filters. The one or more first spatial domain filters may be associated with or corresponding to one or more first TCI states or one or more SSB receptions associated with / tied with / corresponding to a first physical cell index (e.g., physCellld) of the serving cell.

[0392] In an example, the TA offset may be used for the first timing advance group (TAG) for the serving cell. The second TA offset may be used for / associated with the second TAG for the serving cell. The wireless device may be configured / indicated with the first TAG and the second TAG for the serving cell. For example, a first ID of the first TAG is a first TAG-ID. A second ID of the second TAG is a second TAG-ID.

[0393] A MAC CE indicating one or more timing advance values (e.g., a MAC CE to update a timing advance value or a MAC to indicate an absolute timing advance value conveyed via a random access response) for one of the first TAG and the second TAG.

[0394] In an example, a RAR comprise a bit field that indicate / comprise a TAG identifier pointer (e.g., tag- Id-ptr) between a first value (e.g., 0) and a second value (e.g., 1). The first value may indicate / be associated with the one or more first TCI states and the second value may indicate / be associated with the one or more second TCI states, in response to a joint TCI state between downlink and uplink being enabled / configured / indicated (e.g., being configured with dl-OrJointTCI-StateList comprising the one or more first TCI states and the one or more second TCI states). The first value may indicate / be associated with the first TAG. The second value may indicate / be associated with the second TAG.

[0395] In another example, the first value may indicate / be associated with one or more first UL TCI states and the second value may indicate / be associated with one or more second UL TCI states, in response to a joint TCI state between downlink and uplink not being enabled / configured / indicated (or in response to being configured with a ul-TCI-State-List comprising the one or more first UL TCI states and the one or more second UL TCI states). In the example, the one or more first UL TCI states may be associated with or corresponding to the one or more first spatial domain filter parameters. The one or more second UL TCI states may be associated with or corresponding to the one or more second spatial domain filter parameters.

[0396] In another example, the first value may indicate / be associated with the one or more first spatial domain filters and the second value may indicate / be associated with the one or more second spatial domain filters, in response to.

[0397] In the examples, the first value may indicate / be associated with the first TAG. The second value may indicate / be associated with the second TAG. The first TAG may be associated with the one or more first TCI states (if dl-OrJointTCI-StateList is provided), the one or more first UL TCI states (if ul-TCI-State-Docket No.: 24-1191 PCTList is provided). The second TAG may be associated with the one or more second TCI states (if dl- OrJointTCI-StateList is provided), the one or more second UL TCI states (if ul-TCI-State-List is provided).

[0398] In an example, a wireless device may receive one or more timing advance commands (TACs) for a TAG. The one or more timing advance command may be conveyed via one or more MAC CEs / PDSCHs. In an example, a first a MAC CE may indicate an identifier of a TAG (TAG ID) and a TAC. The TAC may comprise a timing advance value to adjust / update / apply a TA of the TAG with the TAG ID compared to a current TA for a serving cell. The wireless device may apply / update / adjust the TA of the TAG based on the timing advance value of the TAC and the TAG ID based on the first MAC CE. In an example, the wireless device may add the timing advance value to the current TA of the TAG.

[0399] In an example, a second MAC CE may indicate a first TAG identifier point (e.g., tag-ld-ptr = 0) or a second TAG identifier pointer (e.g., tag-ld-ptr = 1) for a serving cell and an absolute timing advance value for the serving cell. For example, based on a tag2 flag (e.g., tag2-flag) being set to FALSE (0), the first TAG identifier point with value 0 may correspond to the first TAG and the second TAG identifier point with value 1 may correspond to the second TAG. For example, based on the tag2 flag (e.g., tag2-flag) being set to TRUE (1), the first TAG identifier point with value 0 may correspond to the second TAG and the second TAG identifier point with value 1 may correspond to the first TAG.

[0400] In an example, when a wireless device is configured / indicated with a plurality of TAGs for a serving cell, based on a capability, the wireless device may reduce in duration a latter transmission using a first TAG (e.g., tag-ld-ptr = 0) of the plurality of TAGs to avoid overlapping with a former transmission using a second TAG (e.g., tag-ld-ptr = 1) of the plurality of TAGs.

[0401] In an example, a MAC CE of a timing advance update / command may comprise a TAG ID and a timing advance value. The wireless device may apply the timing advance value to a TAG with the TAG ID.

[0402] As shown in FIG. 22, the wireless device receives one or more RRC messages (RRC message(s)) indicating / comprising a first TA offset value (N_TA_offset) for a first TAG (TAG#1) and a second TA offset value (N_TA_offset2) for a second TAG (TAG#2). In the example, the first TAG is associated with a first coreset pool and a first spatial domain filter parameter. The second TAG is associated with a second coreset pool and a second spatial domain filter parameter. A first TCI state may be associated with the first coreset pool and the first spatial domain filter parameter. A second TCI state may be associated with the second coreset pool and the second spatial domain filter parameter.

[0403] The wireless device may determine a first TA (T_TA) for the first TAG based on the first TA offset and one or more timing advance values (for N_TA) for the first TAG via one or more MAC CEs and / or RARs. The wireless device may determine a second TA (T_TA2) based on the second TA offset and one or more second timing advance values (for N_TA2) for the second TAG via one or more second MAC CEs and / or RARs.Docket No.: 24-1191 PCT

[0404] In an example, T_TA = (N_TA_offset + N_TA ) *Tc. T_TA2 = (N_TA_offset2 + N_TA2) *Tc.

[0405] The wireless device may transmit one or more uplink transmissions using / via the first spatial domain filter parameter based on the first TA (T_TA), where the one or more uplink transmission occurs T_TA before a reception timing of a downlink frame associated with the first coreset pool or the first TCI state. The downlink frame may correspond to an uplink frame of the one or more uplink transmissions.

[0406] The wireless device may transmit one or more second uplink transmissions using / via the second spatial domain filter parameter based on the second timing advance (T_TA2), where the one or more second uplink transmissions occur T_TA2 before a reception timing of a second downlink frame associated with the second coreset pool or the second TCI state. The second downlink frame may correspond to a second uplink frame of the one or more second uplink transmissions.

[0407] FIG. 22 illustrates that a start timing of the uplink frame (U (Spatial Domain Filter #1)) of the one or more uplink transmissions occurs T_TA before a start timing of the corresponding downlink frame (D (Coreset Pool #1)). FIG. 22 illustrates that a start timing of the second uplink frame (U (Spatial Domain Filter #2)) of the one or more second uplink transmissions occurs T_TA2 before a start timing of the corresponding second downlink frame (D (Coreset Pool #2)).

[0408] In an example, a base station may operate a subband-full-duplex (SBFD) operation in a cell. The base station may configure one or more SBFD symbols for the cell via one or more RRC messages and / or SIB messages. The base station may operate a single TRP for the cell. The base station may operate multiple TRPs for the cell

[0409] A wireless device may be configured with the cell as a serving cell. The wireless device may be configured with a single TRP (e.g., a single coreset pool or no coreset pool). The wireless device may be configured with one or more spatial domain filters associated with a TCI state (e.g., a RS of the one or more spatial domain filters is set to a first RS of the TCI state and a qcl-Type is set to typeD). The wireless device may be configured with a single-DCI based multi-TRP operation. For example, the wireless device may receive one or more DCIs via one or more CORESETs that belong to a same coreset pool or that are associated with a same SSB or a TCI state. The wireless device may receive a DCI scheduling one or more data reception or transmission based on a plurality of TCI states or a plurality of spatial domain filter parameters.

[0410] The base station may configure one or more UL subbands and one or more DL subbands on / during the one or more SBFD symbols of the cell. The base station may support simultaneous reception via the one or more UL subbands and transmission via the one or more DL subbands during a symbol of the one or more SBFD symbols. The base station may cancel (self-interference) from the transmission via the one or more DL subbands for the reception via the one or more UL subbands. To reduce the selfinterference (or enhance orthogonality between the transmission and the reception), the base station mayDocket No.: 24-1191 PCT align a first timing of the reception and a second timing of the transmission by configuring a first TA offset, to the wireless device, as zero / 0 for the cell. Based on the first TA offset as zero for the cell, the wireless device may determine a TA based on a propagation delay (or a round-trip time) without adding additional offset. Thus, the first timing of the reception would be aligned with the second timing of the transmission.

[0411] In an example, the base station may configu re / indicate a second TA offset value, for the cell, for a second uplink transmission during an uplink symbol that is not a SBFD symbol. The base station may receive one or more uplink transmission by one or more wireless devices during the uplink symbol. In an example, the one or more wireless devices may determine the second TA offset based on a frequency band of the cell and / or a duplexing mechanism / mode (e.g., TDD vs FDD) of the cell regardless of additional SBFD operation. For example, the wireless device may determine the second TA offset as non-zero value based on the cell operating on a TDD band or the cell operates in TDD duplexing mechanism / mode.

[0412] In an example, a first wireless device may be configu red / ind icated with only the second TA offset for the cell, where the first wireless device may not support or may not be enabled with a SBFD operation for the cell. The wireless device may be config ured / i ndicated with the first TA offset and the second TA offset for the cell based on the wireless device supporting / being enabled with the SBFD operation for the cell.

[0413] The base station may configure / indicate the second TA offset value being larger than or equal to a receiver-transmitter switching latency (TX-RX switching) of a wireless device and / or a transmitter-receiver switching latency (TX-RX switching) of the wireless device.

[0414] In an example, the second TA offset value may be set to a non-zero value (e.g., 25660).

[0415] In an example, the wireless device may transmit a first uplink transmission during an uplink symbol based on the second TA offset value (e.g., non-zero) and the wireless device may transmit a second uplink transmission during the symbol (e.g., an SBFD symbol), of the one or more SBFD symbols, based on the first TA offset value (e.g., zero).

[0416] In an example, the wireless device may transmit the first uplink transmission associated with a first spatial domain filter. The first spatial domain filter may be associated with a first TCI state. In an example, the wireless device may transmit the second uplink transmission associated with a second spatial domain filter. The second spatial domain filter may be associated with a second TCI state. In an example, the first TCI state and the second TCI state may be same. In an example, a first RS of the first TCI state with a qcl- Type set to ‘typeD’ may be same as a second RS of the second TCI state with a qcl-Type set to ‘typeD’. In an example, the first TCI may be associated with a SSB with a SSB index. The second TCI state may be associated with the SSB with the SSB index. In another example, the second TCI state may be associated with a second SSB with a second SSB index, where the second SSB index may be different from the SSB index.Docket No.: 24-1191 PCT

[0417] In existing technologies, a base station may configure a first TAG and a second TAG for a cell. The first TAG may be determined based on or associated with a first TA offset. The second TAG may be determined based on or be associated with a second TA offset. In the existing technologies, the wireless device may determine the first TA offset based on one or more predetermined values or may receive one or more RRC messages indicating / comprising a parameter indicating the first TA offset. The wireless device receives one or more second RRC messages indicating / comprising a parameter indicating the second TA offset for the cell.

[0418] The wireless device may maintain the plurality of TAGs for the cell, where a first TA of the first TAG and a second TA of the second TAG are independently managed / updated. A first downlink frame timing for / associated with the first TAG may be different from a second downlink frame timing for / associated with the second TAG.

[0419] The wireless device may transmit one or more first uplink transmissions, via the cell or an uplink carrier of the cell, during one or more uplink symbols based on the first TAG. The wireless device may transmit one or more second uplink transmissions, via the cell or the uplink carrier of the cell, during one or more SBFD symbols based on the second TAG. In the example, the uplink carrier of the cell is not a SUL carrier.

[0420] In the existing technologies, the wireless device may receive a first timing advance command for the first TAG. The wireless device may update a first timing advance (e.g., T_TA) of the first TAG based on the first timing advance command The timing advance command may be transmitted via a RAR and / or a MAC CE. The wireless device may receive a second timing advance command for the second TAG. The wireless device may update a second timing advance (e.g., T_TA_2) of the second TAG based on the second timing advance command. In the example, the first timing advance command and the second timing advance command may be received in different times.

[0421] FIG. 23 illustrates an example as per aspects of the existing technologies. A wireless device (e.g., UE 2300) may communicated with a base station (e.g., BS(s) 2320). The base station may configure a cell (e.g., CC#1 2340) to the wireless device.

[0422] The base station transmits one or more RRC messages 2302 to configure / indicate a first TAG and a second TAG to the wireless device. The one or more RRC messages 2302 may comprise one or more parameters indicating a first TA offset value (e.g.., TA_offset) for the first TAG and a second TA offset value (e.g., TA_offset_2) for the second TAG. The one or more RRC messages 2302 may comprise one or more SBFD configuration parameters comprising one or more UL subbands and / or one or more SBFD symbols. The wireless device may determine a symbol or a slot as a SBFD-UL (S-U) symbol or slot based on the one or more SBFD configurations (e.g , based on the symbol or the slot being indicated as a SBFD symbol or a SBFD slot by the one or more SBFD symbols). For example, the one or more SBFD symbols may beDocket No.: 24-1191 PCT indicated based on an index of a starting slot, an index of a starting symbol within the starting slot, an index of an ending slot, and an index of an ending symbol within the ending slot. One or more symbols between the starting symbol of the starting slot and the ending symbol of the ending slot may be considered as the one or more SBFD symbols.

[0423] The wireless device may experience a propagation delay change 2310 due to a fast mobility / speed and / or obstacles / buildings and / or handover and / or layer-1 mobility (e.g., LTM) and / or the like. In the existing technologies, the base station may transmit a plurality of messages updating a first TA of the first TAG and a second TA of the second TAG for the cell. For example, the base station transmits a first RAR 2304 comprising a first TAC for the first TAG. The base station transmits a second RAR 2306 comprising a second TAC for the second TAG.

[0424] The wireless device updates the first TA of the first TAG based on the first RAR 2304 and / or the first TAC at a time T 1 as shown in 2330. The wireless device may update the second TA of the second TAG based on the second RAR 2306 and / or the second TAC at a time T2 as shown in 2350. The wireless device may update the first TAG and the second TAG at different times (e.g., T 1 is not same as T2). For example, during a gap between T1 and T2, the first TAG and the second TAG may not be aligned. During the gap, the wireless device may transmit one or more uplink transmission, via the cell, based on the second TAG that is outdated.

[0425] The existing technologies may not enable / maintain an offset / difference between the first TA of the first TAG and the second TA of the second TAG being a same. The existing technologies may require high overhead to maintain / update the first TAG and the second TAG simultaneously (e.g., twice overhead compared to a single TAG for the cell). Mis-aligned gaps between the first TAG and the second TAG may lead performance degradation of uplink receptions at the base station.

[0426] In another existing technologies, a wireless device may receive one or more RRC messages comprising a first TA offset and a second TA offset for a cell. The one or more RRC messages may comprise a TAG for the cell. The wireless device may maintain the TAG for the cell. The wireless device may apply the first TA offset and the second TA offset to the TAG. In the existing technology, the wireless device may not be able to determine which TA offset to apply for an uplink transmission via one or more UL symbols or one or more SBFD symbols. In the existing technology, the wireless device may not be able to determine which TA offset to apply for an uplink transmission during one or more UL symbols and one or more SBFD-UL symbols.

[0427] In an example, a base station may have different capabilities in cancelling / suppressing selfinterference of downlink transmission to receive one or more uplink transmission by one or more wireless devices. For example, the base station may configure a guard band between an uplink subband (UL subband) and a downlink subband (DL subband) such that the base station may handle inter-carrierDocket No.: 24-1191 PCT interference via the guard band. For example, the base station may configure a smaller guard band or a zero-sized guard band where the base station may require a first timing of the reception of the one or more uplink transmissions and the downlink transmission being aligned.

[0428] In existing technologies, the two TAGs or a TAG with two TA offsets may be configured regardless of the base station capability. Existing technologies may not address different base station capabilities efficiently.

[0429] Existing technologies may increase overhead to maintain two different timing advance values for a cell operating a SBFD operation. Existing technologies may have limited flexibility in supporting various capabilities of a wireless device and / or a base station in supporting a SBFD operation. Existing technologies may result in mis-aligned TAs of two TAGs for the cell.

[0430] In an embodiment, a wireless device may receive one or more RRC messages for a cell. The one or more RRC messages may comprise / indicate a TA offset used for UL transmissions via a cell. In an example, the one or more RRC messages may comprise a parameter / indicate to skip applying the TA offset for the uplink transmissions during one or more SBFD symbols. Alternatively, the one or more RRC messages may comprise a parameter / indicate to setting the TA offset as zero / 0 for the uplink transmissions during the one or more SBFD symbols. The wireless device may transmit, via the cell and during the one or more SBFD symbols, an UL transmission, where the wireless device does not apply the timing advance offset to the UL transmission. Alternatively, the wireless device may transmit, via the cell and during the one or more SBFD symbols, the UL transmission, where the wireless device sets the timing advance offset to zero / 0 for the UL transmission.

[0431] Example embodiments may allow a base station to configure whether to apply a TA offset for uplink transmissions via a UL subband of a cell (and / or one or more SBFD symbols of a cell) or not based on capabilities of the base station and / or configuration of a guard band between the UL subband and a DL subband of the cell. Example embodiments may allow aligned timing advance values between the first UL transmission, via the cell or an uplink carrier of the cell, during one or more UL symbols and the second UL transmission, via the cell or the uplink carrier of the cell, during one or more SBFD symbols, where a gap between two timing advance values of the first UL transmission and the second UL transmission is the TA offset. Example embodiments may support different timing advance values for the first UL transmission and the second UL transmission with low overhead and low complexity of the wireless device. For example, the wireless device may maintain a single TAG for the cell. For example, a single RAR or a single MAC CE may update timing advance values for the first UL transmission and the second UL transmission.

[0432] In the example, the one or more RRC messages may not comprise / indicate a second TA offset for the cell. In the example, the one or more RRC messages may comprise / indicate one or more SBFD configuration parameters indicating the one or more SBFD symbols. The one or more SBFD configurationDocket No.: 24-1191 PCT parameters may indicate / comprise one or more UL subbands used / applied in the one or more SBFD symbols.

[0433] In an example, the wireless device may transmit a first UL transmission via the cell during one or more UL symbols based on the TA offset. In the example, the wireless device may determine the one or more UL symbols based on one or more UL / DL TDD configurations. The one or more UL symbols may comprise symbols indicated as uplink or flexible via the one or more UL / DL TDD configurations. The one or more UL symbols may not be indicated as SBFD symbols based on the one or more SBFD configuration parameters. The one or more UL symbols of the cell may not overlap with the one or more SBFD symbols of the cell. The wireless device may apply the TA offset for the first UL transmission in response to transmitting the first UL transmission during the one or more UL symbols.

[0434] In the example, the wireless device may not apply the TA offset for the UL transmission during the one or more SBFD symbols, in response to the one or more RRC messages indicating to skip applying the TA offset (or setting the TA offset as zero / 0) for the UL transmissions during the one or more SBFD symbols.

[0435] The base station may determine a necessary guard band between the UL subband of the one or more UL subbands and a DL subband of one or more DL subbands. The base station may determine a first set of PRBs as a guard band in response to a first timing of a downlink transmission and a second timing of an uplink transmission during a symbol, of the one or more SBFD symbols, not being aligned. The base station may determine a second set of PRBs as a guard band in response to the first timing and the second timing being aligned.

[0436] In an example, the second set of PRBs may be smaller or a subset of the first set of PRBs.

[0437] In an example, the one or more RRC messages may indicate a guard band between an UL subband of the one or more UL subbands and a DL subband that is adjacent to the UL subband in frequency domain. The wireless device may determine to skip applying the TA offset or setting the TA offset as zero / 0 for the UL transmission during the one or more SBFD symbols based on a size of the guard band. For example, if the size of the guard band is smaller than or equal to a number of PRBs (e.g., 0 PRB or M PRBs where M may be predetermined or configured via RRC messages / higher layer signaling), the wireless device may determine to skip applying the TA offset or setting the TA offset as zero for the UL transmissions during the one or more SBFD symbols. Otherwise, the wireless device may determine not to skip applying the TA offset or applying the TA offset for the UL transmissions during the one or more SBFD symbols.

[0438] In an example, the one or more RRC messages may indicate a single TAG for the cell or a plurality of TAGs (e.g., two TAGs) for the cell. The wireless device may determine to skip applying the TA offset (or setting the TA offset as zero / 0) for the UL transmissions during the one or more SBFD symbols in responseDocket No.: 24-1191 PCT to the single TAG being configured / indicated for the cell. The wireless device may determine to apply the TA offset for the UL transmissions during the one or more SBFD symbols based on the plurality of TAGs being configured / indicated for the cell.

[0439] In an example, the one or more RRC messages may indicate a second TA offset for the cell, where the cell is configured / indicated with a single TAG. The wireless device may determine to skip applying the TA offset or setting the TA offset as zero in response to the second TA offset being zero. The wireless device may determine an error when the second TA offset being non-zero value and the cell being configured / indicated with the single TAG. The wireless device may apply to apply the TA offset for the UL transmissions during the one or more SBFD symbols, in response to the second TA offset not being configured / indicated for the single TAG for the cell.

[0440] The wireless device may apply the TA offset for the UL transmissions via the cell during the one or more SBFD symbols, in response to not receiving the one or more RRC messages indicating skip applying the TA offset or setting the TA offset as zero / 0 for the UL transmission during the one or more SBFD symbols.

[0441] In the specifications, at least for some embodiments, the one or more RRC messages may comprise UE-specific RRC signaling / configurations, cell-specific RRC signaling / configurations, SIBs, SIB1 , MIB, and / or the like.

[0442] In an example, the wireless device may receive a SIB indicating the TA offset for the cell. The wireless device may receive a second SIB or a second RRC message indicating a second TA offset for the cell. The second TA offset may be one of {zero / 0, the TA offset}. The second SIB or the second RRC message may indicate 0 (or 1) to apply / set the zero / 0 as the second TA offset. The second SIB may or the second RRC message indicate 1 (or 0) to apply / set the TA offset as the second TA offset. The wireless device may skip applying the TA offset for the UL transmissions during the one or more SBFD symbols based on the second SIB or the second RRC message indicating 0 (or 1). The wireless device may apply the TA offset for the UL transmissions during the one or more SBFD symbols based on the second SIB or the second RRC message indicating 1 (or 0). In the example, the cell may be associated with the single TAG. Alternatively, if the cell is associated with a plurality of TAGs, the wireless device may apply the TA offset for a first TAG of the plurality of TAGs and the second TA offset for a second TAG of the plurality of TAGs.

[0443] In an example, the one or more RRC messages may indicate to use a different timing advance for the UL transmissions during the one or more SBFD symbols. The wireless device may determine to skip applying the TA offset based on the one or more RRC messages.Docket No.: 24-1191 PCT

[0444] In an example, the first UL transmission may be associated with a TCI state. The second UL transmission may be associated with the TCI state. In an example, the TCI state may be associated with a SSB with a SSB index.

[0445] In an example, the second UL transmission may be via a UL subband of the one or more UL subbands. The UL subband may comprise one or PRBs configured for an uplink during the one or more SBFD symbols.

[0446] In an example, the wireless device may skip applying the TA offset for a second UL transmission during one or more UL symbols and one or more second SBFD symbols, in response to the one or more RRC messages indicating to skip the TA offset for the UL transmissions during the one or more SBFD symbols. Alternatively, the wireless device may apply the TA offset for the second UL transmission regardless of the one or more RRC messages indicating to skip the TA offset for the UL transmissions during the one or more SBFD symbols.

[0447] In an example, the wireless device may skip applying the TA offset for each of a plurality of repetitions, via the cell, of an UL transmission (e.g., a PUSCH transmission, a PUCCH transmission, a PRACH transmission) in response to a repetition of the plurality of repetitions of the UL transmission occurs during one or more SBFD symbols of the cell. In an example, the wireless device may apply the TA offset for each of the plurality of repetitions, via the cell, of the UL transmission in response to a second repetition of the plurality of repetitions of the UL transmission occurs during one or more UL symbols of the cell.

[0448] In an example, the one or more RRC messages indicating {set TA offset as zero, apply the TA offset}. A DCI scheduling an uplink transmission (e.g., a PUSCH) for the cell may indicate whether to set TA offset as zero or to apply the TA offset for the uplink transmission. A DCI may indicate whether to apply the TA offset for the uplink transmission via the cell.

[0449] FIG. 24 illustrates an example as per an aspect of an embodiment of the present disclosure.Similar to FIG. 23, a base station and a wireless device may operate a SBFD via a cell (CC#1 2440). The base station may configure the cell (CC#1 2440) to the wireless device. The base station may operate a single TRP with the wireless device. The base station may configure / indicate a single coreset pool to the wireless device. The base station may configure a single-DCI based multi-TRP operation to the wireless device.

[0450] The base station may transmit one or more RRC messages 2402 comprising / indicating one or more SBFD configuration parameters as discussed in FIG. 23. The one or more RRC messages 2402 may comprise / indicate a TA offset (TA_offset) for the cell. The wireless device may determine the TA offset based on one or more predetermined values in response to one or more RRC messages 2402 not comprising the TA offset. The wireless device may determine the TA offset of the cell based on a first TA offset of a first cell in response to the cell and the first cell belonging to a same TAG. The wireless deviceDocket No.: 24-1191 PCT may determine the TA offset of the cell based on the cell being configured with the one or more SBFD configuration parameters.

[0451] The one or more RRC messages 2402 may further comprise / indicate a parameter to enable a different timing for an uplink transmission during one or more SBFD symbols and / or via a UL subband of the cell. For example, the parameter may indicate to skip applying the TA offset for the uplink transmission during the one or more SBFD symbols or via the UL subband. For example, the parameter may indicate to apply a TA offset of zero / 0 to the UL transmission. For example, the parameter may indicate the second TA offset being zero / 0, where the TA offset and the second TA offset may be associated with the TAG. In the example, the cell may not be associated with a plurality of TAGs.

[0452] Alternatively or in another example, the parameter may indicate to apply a second TAG for the UL transmissions during the one or more SBFD symbols. The base station may configure the second TAG for the cell. The wireless device may determine a second TA offset of the second TAG as zero / 0 in response to the parameter (or based on the second TAG).

[0453] In an example, the one or more RRC messages may comprise / indicate a TAG group / bundle for the cell. The TAG group / bundle may comprise a first TAG and a second TAG. The wireless device may apply / associate the TA offset for the first TAG. The one or more RRC messages may comprise / indicate a second TA offset for the second TAG. The wireless device may apply / associate the second TA offset for the second TAG.

[0454] In the example, the wireless device may determine the second TA offset as zero in response to the one or more RRC messages not comprising the second TA offset.

[0455] In the example, the wireless device may receive a first RAR or a first MAC CE comprising / indicating a first TAG ID of the first TAG and a TAC comprising a timing advance value. In the example, the wireless device may receive a second RAR or a second MAC CE comprising / indicate a second TAG ID of the second TAG and a second TAC comprising a second timing advance value. In response to the first TAG and the second TAG belonging to the TAG group / bundle of the cell, the wireless device may apply the first timing advance value to the first TAG and the second TAG based on the first RAR or the first MAC CE. In response to the first TAG and the second TAG belonging to the TAG group / bundle of the cell, the wireless device may apply the second timing advance value to the first TAG and the second TAG based on the second RAR or the second MAC CE.

[0456] In FIG. 24, the base station may transmit a first UL grant 2410 scheduling a first PUSCH transmission 2430 on a slot #i. The first PUSCH transmission is scheduled via a UL subband during one or more first SBFD symbols (illustrated as subband-UL, S-U). The base station may transmit a second UL grant 2450 scheduling a second PUSCH transmission 2470 on a slot #j. The second PUSCH transmission 2470 is scheduled via an active UL BWP during one or more first UL symbols (illustrated as UL, U).Docket No.: 24-1191 PCT

[0457] Based on the one or more RRC messages 2402, the wireless device may determine to apply the TA offset for the second PUSCH transmission 2470 during the one or more first UL symbols. Based on the one or more RRC messages 2402, the wireless device may determine to skip applying the TA offset for the first PUSCH transmission 2430 during the one or more first SBFD symbols.

[0458] In the example, a first timing advance for the first PUSCH transmission 2430 may be determined based on a timing advance value (e.g., N_TA 2403). The timing advance value (e.g., N_TA 2403) may be updated based on one or more timing advance commands via one or more RARs and / or MAC CEs (via PDSCHs). The wireless device may not apply the TA offset to the first PUSCH transmission 2430.

[0459] In the example, a second timing advance for the second PUSCH transmission 2470 may be determined based on the timing advance value (e.g., N_TA 2403) and the TA offset (TA_offset) as per 2407. The wireless device may apply the TA offset (as per 2409) for the second PUSCH transmission 2470.

[0460] In an example, the wireless device may apply a second TA offset for the first PUSCH transmission 2430 in response to skip applying the TA offset. The second TA offset may be configured via one or more messages such as RRC, MAC-CE or DCI format

[0461] In an example, the first PUSCH transmission 2430 may be associated with a first spatial domain filter parameter. The wireless device may transmit the first PUSCH transmission 2430 based on / using the first spatial domain filter parameter. The first spatial domain filter parameter may be associated with a first TCI state. The first TCI state may be associated with a SSB with a SSB index. The second PUSCH transmission 2470 may be associated with a second spatial domain filter parameter. The wireless device may transmit the second PUSCH transmission 2470 based on / using the second spatial domain filter parameter. The second spatial domain filter parameter may be associated with the first TCI state. The second spatial domain filter parameter may be associated with a second TCI state. The second TCI state may be associated with the SSB with the SSB index. In the example, the first TCI state and the second TCI state may be associated with a same SSB. In the example, the first TCI state and the second TCI state may be associated with a same TRP. In the example, the first spatial domain filter parameter and the second spatial domain filter parameter may be associated with a same TRP of the base station.

[0462] In an example, for an uplink carrier of a cell or the cell, a wireless device may transmit one or more messages indicating / comprising one or more capabilities to support not applying the TA offset (or set TA offset as zero) for an uplink transmission via the UL subband and / or during one or more SBFD symbols.

[0463] In an example, for an uplink carrier of a cell or the cell, a wireless device may indicate whether it supports a different TA offset for uplink transmissions during one or more SBFD symbols and / or an UL subband of a SBFD cell compared to (or in addition to) a TA offset applied / used for uplink transmissionsDocket No.: 24-1191 PCT during UL symbols In an example, the wireless device may indicate whether it supports a plurality of TA offsets associated with a TAG for the cell.

[0464] In an example, the base station may determine, for the cell, whether to configure to the wireless device to skip applying the TA offset for the uplink transmission during the one or more SBFD symbols and / or via the UL subband. The determining may be based on a guard band between the UL subband and a DL subband during the one or more SBFD symbols. The determining may be based on one or more capabilities of the base station. The base station may not determine to configure to the wireless device to skip applying the TA offset (or different TA offset from the TA offset of the cell) for the uplink transmission during the one or more SBFD symbols in response to not receiving the one or more capabilities from the wireless device.

[0465] In an example, a wireless device may be required / configured to support / use a second TA offset for an uplink transmission, via a cell or an uplink carrier of the cell, during one or more SBFD symbols and / or via an UL subband of the cell in response to supporting a SBFD operation on the cell. For example, the second TA offset may be different from the TA offset. The second TA offset and the TA offset may be associated with a TAG. The wireless device may apply the second TA offset for the uplink transmission in response to skipping applying the TA offset for the uplink transmission during the one or more SBFD symbols.

[0466] The wireless device may not indicate support of the SBFD operation on / for the cell (or on a frequency band for the cell) in response to not supporting different TA offset for the uplink transmission, via the cell, during the one or more SBFD symbols (and / or the UL subband). In an example, when the cell is configured with the uplink carrier (e.g., in a TDD carrier of the cell) and a supplemental uplink (SUL) carrier, the wireless device may support / apply the second TA offset for the uplink carrier. The wireless device may not support / apply the second TA offset for the SUL carrier. The wireless device may be deconfigured with the SUL carrier in response to being configured with the second TA offset. The wireless device may skip one or more uplink transmissions via the SUL carrier when each of the one or more uplink transmissions overlap, in time, with the one or more SBFD symbols of the cell. In an example, the wireless device may skip an uplink transmission via SUL carrier of the cell in response to the uplink transmission overlaps with a second uplink transmission via the uplink carrier during one or more SBFD symbols of the cell

[0467] In an example, a base station may not enable a SBFD operation of a cell for a wireless device in response to the wireless device not supporting different TA offset or may not support to skip applying a TA offset for SBFD symbols.

[0468] In an example, the wireless device may apply the TA offset for the first PUSCH transmission 2430 in response to not receiving the parameter indicating to skip applying the TA offset for the first PUSCH transmission 2430. In an example, the wireless device may apply the TA offset for an UL transmission via aDocket No.: 24-1191 PCT cell regardless of whether the UL transmission is during one or more UL symbols or one or more SBFD symbols when / in response to one or more RRC messages not indicating or comprising a parameter to apply a different TA offset for SBFD symbols.

[0469] In an example, a wireless device may support a plurality of TAGs for a cell or an uplink carrier of the cell. The cell may be configured with a first coreset pool and a second coreset pool. The first coreset pool may be associated with a first TRP of a base station. The second coreset pool may be associated with a second TRP of the base station. A capability of supporting the plurality of TAGs for the cell may be shared between a multi-TRP operation and a SBFD operation of a cell. For example, the wireless device may be configured with a multi-TRP of a cell or enabled with a SBFD operation of the cell based on supporting a plurality of TAGs. In an example, the wireless device may support up to two TAGs for the cell regardless of the multi-TRP and the SBFD operation (e.g., both are enabled or either one is enabled). In an example, a first coreset pool (or a first TCI state) may be associated with a first spatial domain filter parameters for one or more UL transmissions during one or more UL symbols. A second coreset pool (or a second TCI state) may be associated with a second spatial domain filter parameters for one or more second UL transmissions during one or more SBFD symbols. In an example, a first spatial domain filter parameter or a first UL TCI state may be associated with one or more UL transmissions during one or more UL symbols. A second spatial domain filter parameter or a second UL TCI state may be associated with one or more second UL transmissions during one or more SBFD symbols.

[0470] The wireless device may transmit / indicate a capability to inform whether the wireless device supports sharing support of a plurality of TAGs for a cell between a multi-TRP and a SBFD operation. In response to the capability, the base station may utilize support of a plurality of TAGs by the wireless device for a SBFD operation and / or a multi-TRP operation of a cell. The wireless device may indicate a capability to support a multi-DCI reception via a plurality of coreset pools for a SBFD enabled cell, where a first coreset pool of the plurality of coreset pools corresponds to one or more downlink (or non-SBFD) symbols and a second coreset pool of the plurality of coreset pools corresponds to one or more SBFD symbols. The wireless device may indicate a capability to support a multi-DCI based two TAGs for the cell (e.g., via multiDCI-lnterCellMultiTRP-TwoTA or multi DCI-lntraCellMultiTRP-TwoTA), where a first TCI state corresponds to a first TAG for uplink (or non-SBFD) symbols and a second TCI state corresponds a second TAG for one or more SBFD symbols.

[0471] In an example, a base station may configure a first coreset pool and a second coreset pool for a cell. The base station may configure one or more SBFD configuration parameters comprising / indicating a UL subband and / or one or more SBFD symbols for the cell. In an example, a wireless device may not enable a SBFD operation in response to being configured with the first coreset pool and the second coreset pool. In another example, a wireless device may apply one or more TCI states associated with the firstDocket No.: 24-1191 PCT coreset pool for one or more downlink (or non-SBFD) symbols. The wireless device may apply one or more second TCI states associated with the second coreset pool for one or more SBFD symbols. In an example, a wireless device may apply one or more spatial domain filter parameters associated with the first coreset pool for one or more uplink (or non-SBFD) symbols. The wireless device may apply one or more second spatial domain filter parameters associated with the second coreset pool for one or more SBFD symbols.

[0472] In an example, a wireless device may support a SBFD operation on a cell. The wireless device may indicate a capability to support a SBFD operation on a cell. In an example, the wireless device may indicate a first capability to support a SBFD operation on an uplink carrier of the cell. The wireless device may indicate a second capability to support a SBFD operation on a downlink carrier of the cell. In response to being enabled with a SBFD operation on a cell, the wireless device may not be configured with a SUL carrier of the cell. In an example, if a wireless device is configured with an UL carrier and a SUL carrier for a cell where the cell is enabled with a SBFD operation, the wireless device may apply a first TAG or a first TA offset applied in UL symbols of the UL carrier and the SUL carrier.

[0473] In an example, when a wireless device is configured / indicated with a first timing advance (TA) offset and a second TA offset for a cell or an uplink carrier of the cell, the wireless device may apply the first TA offset to one or more first uplink transmissions during one or more first uplink resources and the second TA offset to one or more second uplink transmissions during one or more second uplink resources.

[0474] In an example, the one or more first uplink resources (or the one or more first uplink transmissions) may be indicated as uplink based on one or more UL / DL TDD configuration (see FIG. 17) or flexible based on the one or more UL / DL TDD configurations but not being indicated as SBFD symbols based on one or more SBFD configuration parameters (see FIG. 20). The one or more second uplink resources (or the one or more second uplink transmissions) may be indicated as downlink or flexible based on the one or more UL / DL TDD configurations and being indicated as SBFD symbols based on one or more SBFD configuration parameters. Alternatively, the one or more second uplink resources (or the one or more second uplink transmissions) may overlap in time with one or more downlink symbols indicated based on the one or more UL / DL TDD configurations and being indicated as SBFD symbols based on the one or more SBFD configuration parameters.

[0475] In an example, the one or more first uplink resources (or the one or more first uplink transmissions) may be associated / tied / configured with a first TCI state. The one or more second uplink resources (or the one or more second uplink transmissions) may be associated / tied / configured with a second TCI state.

[0476] In an example, the one or more first uplink resources (or the one or more first uplink transmissions) may be associated / tied / configured with a first spatial domain filter parameter, a first spatial RX parameter, a first spatial filter, a first reference signal of a first spatial relationship info or a first TCI state associated with a first spatial relationship info. The one or more second uplink resources (or the one or more second uplinkDocket No.: 24-1191 PCT transmissions) may be associated / tied / configured with a second spatial domain filter parameter, a second spatial RX parameter, a second spatial filter, a second reference signal of a second spatial relationship info or a second TCI state associated with a second spatial relationship info. In the example, the first spatial domain filter parameter may be used for the one or more first uplink transmissions during one or more uplink / flexible symbols based on the one or more UL / DL TDD configurations (i.e. , one or more non-SBFD symbols). In the example, the second spatial domain filter parameter may be used for the one or more second uplink transmissions during one or more SBFD symbols based on one or more SBFD configuration parameters.

[0477] The one or more first resources and the one or more second resources may belong to an active uplink BWP of the UL carrier. The one or more first uplink transmissions and the one or more second uplink transmissions may be scheduled based on / by one or more DCI formats via one or more CORESETs. The one or more CORESETs may be associated with a TCI state. The one or more CORESETs may belong to a same CORESET pool. The one or more CORESETs may be associated with a TRP.

[0478] In an example, the wireless device may maintain a single downlink reception timing for the cell. The wireless device may apply the first TA offset based on the single downlink reception timing. The wireless device may apply the second TA offset based on the single downlink reception timing. The wireless device may determine the single downlink reception timing based on a cell-defining SSB or a reference SSB of the cell or a pathloss RS of the cell.

[0479] The wireless device may determine a first timing advance (TA) for the one or more first uplink transmission based on a downlink reception time. The wireless device may determine a second TA for the one or more second uplink transmissions based on the downlink reception time.

[0480] In an example, a wireless device may not be configured with an UL carrier and a SUL carrier for a cell, in response to the cell being enabled / configured with a SBFD operation (or with one or more SBFD symbols). In an example, a wireless device may not be configured with a plurality of TA offsets of a TAG for a cell, in response to the cell being enabled / configured with a SBFD operation ((or with one or more SBFD symbols). In an example, a wireless device may not be configured with a plurality of TAGs for a cell, in response to the cell being enabled / configured with a SBFD operation ((or with one or more SBFD symbols).

[0481] Example embodiments in above may be applicable to a cell or an uplink carrier of the cell with a single TA offset with a single TAG configured / indicated or two TA offsets with a single TAG configured / indicated or two TA offsets with two TAGs configured / indicated (respectively).

[0482] In the present disclosure, an UL (uplink) symbol of a cell / carrier may be determined / referred as uplink symbol indicated via one or more UL / DL TDD configuration of the cell / carrier or flexible symbol indicated via the UL / DL TDD configuration of the cell / carrier but not indicated as SBFD symbol via / by one or more SBFD configuration parameters. In the present disclosure, a SBFD symbol of the cell / carrier mayDocket No.: 24-1191 PCT be indicated via / by the one or more SBFD configuration parameters. In the present disclosure, a SBFD-UL symbol of the cell / carrier may be referred / determined as uplink symbol that are indicated as SBFD symbols via / by the one or more SBFD configuration parameters. The wireless device may determine a symbol is indicated as uplink based on one or more RRC configurations scheduling uplink transmissions / resources on the symbol. In the present disclosure, a SBFD-DL symbol of the cell / carrier be referred / determined as downlink symbol that are indicated as SBFD symbols via / by the one or more SBFD configuration parameters. The wireless device may determine a symbol is indicated as downlink based on one or more RRC configurations scheduling downlink reception / resources on the symbol. An SBFD symbol may be indicated as a downlink symbol or a flexible symbol via / by the one or more UL / DL TDD configurations.

[0483] In an example, a wireless device may receive one or more RRC messages comprising / indicating a first TAG and a second TAG for a cell or an UL carrier of the cell. In the example, the cell may be enabled with a SBFD operation. The wireless device may receive one or more SBFD configuration parameters indicating a set of SBFD symbols (or one or more SBFD symbols) and / or at least one UL subband and at least one DL subband.

[0484] FIG. 25 illustrates an example as per an aspect of an embodiment of the present disclosure. The base station (BSs) configures a cell (CC#1 2540) to the wireless device (UE). The base station transmits one or more RRC messages (RRC message(s) 2502) indicating the first TAG and the second TAG for the cell.

[0485] In an example, the RRC message(s) 2502 (or the one or more RRC messages) may comprise a first TA offset for the first TAG. The RRC message(s) 2502 (or the one or more RRC messages) may comprise a second TA offset for the second TAG. The wireless device may determine a first TA of the first TAG based on one or more TA commands received via one or more RARs and / or MAC CEs and the first TA offset. The wireless device may determine a second TA of the second TAG based on the one or more TA commands received via the one or more RARs and / or the MAC CEs and the second TA offset.

[0486] In an example, the RRC message(s) 2502 (or the one or more RRC messages) may comprise / indicate the first TAG and the second TAG belonging to a TAG bundle or a TAG group or being linked.

[0487] In an example, the wireless device may determine the first TAG and the second TAG are linked or belong to a same TAG bundle or a same TAG group, in response to the first TAG and the second TAG being configured for a cell / a carrier enabled with a SBFD operation.

[0488] In an example, a wireless device may receive a TA command via a RAR or a PDSCH carrying a MAC CE or a MAC CE. The TA command may comprise or be associated with a TAG. The wireless device may determine the TAG based on an ID or a pointer carried in the RAR or the MAC CE. In an example, the wireless device may apply the TA command for each TAG of the TAG bundle or the TAG group or theDocket No.: 24-1191 PCT linked TAGs, in response to the ID or the pointer indicating a TAG of the TAG bundle or the TAG group or the linked TAGs.

[0489] For example, due to a building / obstacle or mobility, in FIG. 25, a propagation delay between the base station and the wireless device may change as per 2510. The base station may transmit a new TA value via a message (e.g. , a RAR, a MAC CE).

[0490] For example, as shown in FIG. 25, the wireless device receives a first TA command for the first TAG 2504 via a MAC CE. The MAC CE may comprise / carry an I D / poin ter of the first TAG. The wireless device may determine that the first TAG and the second TAG are linked or belong to the same TAG bundle / group. Based on the determining, as per 2530, the wireless device applies the TA command for the first TAG 2504 for the first TAG. The wireless device may update a first TA of the first TAG based on the TA command for the first TAG 2504. The wireless device, as per 2550, applies the TA command for the first TAG 2504 for the second TAG. The wireless device may update a second TAG of the second TAG based on the TA command for the first TAG 2504.

[0491] For example, the first TA command for the first TAG 2504 may comprise an absolute TA value (a new TA). The wireless device applies the first TA command for the first TAG 2504 to the first TAG as per 2530. The wireless device applies the first TA command for the first TAG 2504 to the second TAG as per 2550.

[0492] A first TA of the first TAG and a second TA of the second TAG, based on updating / applying a new TA value of the first TA command for the first TAG 2504, simultaneously, may be maintained / updated consistently such that a gap between the first TA and the second TA being same. For example, the gap may be a difference between the first TA offset and the second TA offset. For example, the gap may be the first TA offset (e.g., as shown in FIG. 25 2508). For example, the gap may be a constant value.

[0493] In an example, the base station may configure a first TAG to the wireless device. The base station may configure a second TAG to the wireless device, where the wireless device may not update or apply a TA of the second TAG. For example, the wireless device may receive one or more RRC messages comprising / indicating a parameter that the wireless device may not be required to maintain uplink time alignment based on the second TAG or the second TAG is linked to the first TAG.

[0494] Instead, the wireless device may determine the TA of the second TAG based on a first TA of the first TAG and an offset. The base station may configure the offset via one or more RRC / MAC CE / DCI messages / signaling. The wireless device may determine the offset as a TA offset of the first TAG. The wireless device may determine the offset based on one or more predefined values.

[0495] The one or more RRC messages may indicate not to update or not to maintain separate TA counter / value for the second TAG or may not perform an uplink time alignment based on the second TAG.Docket No.: 24-1191 PCTFor example, the wireless device may not maintain separate time alignment timer (e.g., timeAlignmentTimer) for the second TAG.

[0496] The wireless device may determine the second TAG being linked to the first TAG based on the one or more RRC messages.

[0497] In an example, a first TAG of a cell / carrier and a second TAG of a cell / carrier are linked or belong to a same TAG group or a TAG bundle. Based on the first TAG and the second TAG being linked, the second TAG may be dependent on the first TAG. Based on the same TAG group or the TAG bundle, the second TAG may be linked to the first TAG. The wireless device may maintain or perform an uplink time alignment based on the first TAG but not based on the second TAG in response to the second TAG linked to / being dependent on the first TAG.

[0498] The wireless device may skip transmission of one or more second uplink transmissions based on the second TAG in response to a time alignment timer of the first TAG being expired (or in response to detecting unsync of the cell / carrier based on the first TAG or in response to loosing uplink synchronization of the cell / carrier based on the first TAG).

[0499] In an example, a wireless device may receive one or more RRC messages indicating / comprising a TAG for a cell / carrier. The one or more RRC messages may indicate a first TA offset for the TAG. The wireless device may determine the first TA offset based on one or more predetermined values in response to the one or more RRC messages not comprising the first TA offset. For example, the one or more RRC messages may indicate a second TA offset for the TAG. For example, the one or more RRC messages may comprise the second TA offset. For example, the one or more RRC messages may comprise a parameter to skip the first TA offset for one or more uplink transmissions during one or more SBFD symbols. For example, the one or more RRC messages may comprise a parameter to apply zero TA offset (or set the TA offset as zero) for one or more uplink transmissions during one or more SBFD symbols.

[0500] The wireless device may inform / indicate a number of TAGs that the wireless device may support for a frequency band or a frequency band combination. The cell or the carrier may operate on the frequency band or the frequency band combination. A base station may consider / count two TAGs for the TAG for the cell / carrier in response to configuring / indicating the second TA offset. The base station may consider / count two TAGs for the cell / carrier in response to configuring / indicating to skip applying the TA offset for UL transmissions during one or more SBFD symbols. In the example, the wireless device may be configured with a single TAG for the cell with the TA offset, two TAGs with the TA offset and zero offset respectively, a single TAG with two TA offsets (e.g., the TA offset and zero).

[0501] The base station may not configure more than the number of TAGs that the wireless device supports via one or more cel Is / carriers of the frequency band or the frequency band combination. For example, if the wireless device supports four (4) TAGs via a frequency band, and the wireless device isDocket No.: 24-1191 PCT configured / indicated with a second TA offset for a cell / carrier (e.g., two TA offsets for a TAG for the cell / carrier), the base station may configure additional two TAGs for other cel l(s) / carrier(s) of the frequency band or the frequency band combination.

[0502] In an example, a wireless device may be configured with a first carrier / cell operating in a frequency band. The wireless device may be configured with a second carrier / cell operating in the frequency band. The first carrier / cell and the second carrier / cell may be intra-band carrier aggregated. The wireless device may be configured with a first TA offset for the first carrier / cell and a second TA offset for the first carrier / cell.

[0503] Based on the intra-band carrier aggregation of the first carrier / cell and the second carrier / cell, the wireless device may be indicated / configu red with the first TA offset for the second carrier / cell and the second TA offset for the second carrier / cell. The wireless device may determine the first TA offset and the second TA offset for the second carrier / cell based on the intra-band carrier aggregation with the first carrier / cell.

[0504] The wireless device may consider an error case when a first uplink transmission is configured to use / is based on a first TA offset via the first carrier / cell and a second uplink transmission is configured to use / is based on a second TA offset via the second carrier / cell, where the first uplink transmission and the second uplink transmission overlap in time. This may be avoided for example based on a first set of SBFD symbols of the first cell / carrier overlaps, in time, with a second set of SBFD symbols of the second cell / carrier (or vice versa). Alternatively, a first set of SBFD-UL symbols of the first cell / carrier may be superset or subset of a second set of SBFD-UL symbols of the second cell / carrier.

[0505] In an example, the wireless device may use / be based on either the first TA offset or the second TA offset for a first UL transmission via the first cell / carrier and a second UL transmission via the second cell / carrier, where the first UL transmission and the second UL transmission may be via a same slot index in time or may overlap in time

[0506] In an example, the wireless device may indicate a parameter to indicate a capability that it supports two TA offsets of a cell / carrier based on a SBFD operation. The wireless device may indicate the capability for each cell / carrier of one or more carriers that the wireless device supports in a frequency band or a frequency band combination. For example, the wireless device may inform a number of TAGs that the wireless device supports for a frequency band or a frequency band combination. The wireless device may additionally inform / indicate the parameter to indicate that the wireless device supports two TA offsets for a cell / carrier operating on / of the frequency band or the frequency band combination.

[0507] The base station may not configure / enable a SBFD operation, to a wireless device, for a cell / carrier, when the wireless device may not support two TA offsets. In the example, the base station may require the two TA offsets for the SBFD operation.Docket No.: 24-1191 PCT

[0508] This may reduce complexity of a wireless device supporting two TA offsets for a cell. The wireless device may maintain two TA offsets efficiently without adding additional burden, for example, by linking two TAGs respectively associated with each TA of the two TA offsets.

[0509] In an example, a base station may broadcast, via one or more SIB messages, one or more SBFD configuration parameters for a cell / carrier. The one or more SBFD configuration parameters may comprise / indicate whether to skip applying or applying a TA offset for one or more uplink transmissions during one or more SBFD symbols of the cell / carrier. The TA offset may be configured / indicated for a TAG of the cell / carrier. The wireless device may apply the TA offset for one or more second uplink transmissions during one or more UL symbols. The wireless device may determine the one or more UL symbols that are not indicated as SBFD symbols based on the one or more SBFD configuration parameters.

[0510] In an example, a wireless device may not support two TA offsets for the cell / carrier. In response to not supporting the two TA offsets, the wireless device may determine that the wireless device does not support a SBFD operation for the cell / carrier. The wireless device may not inform that the wireless device supports the SBFD operation for the cell / carrier. The wireless device may inform that the wireless device may not support the SBFD operation for the cell / carrier. The wireless device may inform that the wireless device may support the SBFD operation with a single TAG and a single TA offset for the cell or one or more cells of a band or a band combination.

[0511] In an example, the base station may configure one or more random access resources via the one or more SIB messages The one or more random access resources may be indicated / configured with a second TA offset (e.g., zero) that may be different from the TA offset of the TAG for the cell / carrier. The wireless device, in response to supporting two TA offsets for the cell / carrier, may select a resource from the one or more random access resources and transmit a PRACH via the resource.

[0512] The wireless device, in response to not supporting two TA offsets for the cell / carrier, may select a resource from other than the one or more random access resources and transmit a PRACH via the resource.

[0513] FIG. 26 illustrates an example as per an aspect of an embodiment of the present disclosure. For example, a wireless device is configured with a cell / carrier enabled with a SBFD operation. FIG. 26 illustrates a plurality of frame boundaries / timings for transmissions and / or receptions of different downlink / uplink channels / signals. The plurality of frame boundaries / timings may comprise a first timing / frame boundary of a downlink frame (D#i), a second timing / frame boundary of a SBFD-downlink frame (S-D#i), a third timing / frame boundary of an uplink frame (U#i) for PUCCH / PUSCH / SRS transmissions, a fourth timing / frame boundary of a SBFD-uplink frame (S-U#i) for PUCCH / PUSCH / SRS transmissions, a fifth timing / frame boundary of the uplink frame (U#i) for PRACH transmissions, and a sixth timing / frame boundary of the SBFD-uplinkf rame (S-U#i) for PRACH transmissions.Docket No.: 24-1191 PCT

[0514] In an example, the first timing / frame boundary of the downlink frame (D #i), at the wireless device, for receiving one or more downlink signals via the cell / carrier during one or more non-SBFD symbols or downlink symbols is TO. The first timing / frame boundary may be after a propagation delay since the base station starts a corresponding downlink frame at the base station. The wireless device may determine downlink symbols based on one or more UL / DL TDD configurations and one or more SBFD configuration parameters for the cell (e.g., indicated as downlink or flexible, and not being indicated as SBFD symbols). The wireless device may determine the first time / frame boundary of the downlink frame based on a celldefining SSB of the cell.

[0515] In an example, the second timing / frame boundary of the SBFD-downlink frame (S-D#i) , at the wireless device, for receiving one or more second downlink signals via the cell / carrier during one or more SBFD symbols is TO. A first cell identifier for a first TCI state for one or more downlink receptions during one or more downlink symbols may be same to a second cell identifier for a second TCI state for one or more second downlink reception during one or more SBFD symbols. A first SSB associated with the first TCI state may be same to a second SSB associated with the second TCI state. Alternatively, the second timing / frame boundary of the SBFD-downlink frame may be different from the first timing / frame boundary of the downlink frame. In the example, the first cell identifier may be different from the second cell identifier. The first SSB may be different from the second SSB.

[0516] The wireless device may determine the one or more SBFD symbols based on the one or more SBFD configuration parameters In the example, the first starting time and the second starting time may be same. The wireless device may be configured with a first pathloss RS for one or more first uplink transmissions during a set of UL symbols for the cell. The wireless device may be configured with a second pathloss RS for one or more second uplink transmissions during a set of SBFD symbols for the cell. The first pathloss RS may be same as the second pathloss RS. The wireless device may be configured with a first UL TCI state for one or more first uplink transmissions during a set of UL symbols for the cell. The wireless device may be configured with a second UL TCI state for one or more second uplink transmissions during a set of SBFD symbols for the cell. The first UL TCI state and the second UL TCI state may be QCL- ed based on a QCL type ‘D’. The first UL TCI state and the second UL TCI state may be associated with a SSB of the cell.

[0517] In an example, the third timing / frame boundary of the uplink frame (U#i) for a plurality of uplink channels such as PUCCH, PUSCH and SRS may be determined based on the TO and a first TA offset. The wireless device may use / apply the third timing / frame boundary for an uplink transmission of the plurality of uplink channels during one or more UL symbols or non-SBFD symbols for the cell. In the example, the first TA offset may be indicated / configured via RRC / SIB message(s) or predetermined. The first TA offset may refer a TA offset associated with a TAG for the cell.Docket No.: 24-1191 PCT

[0518] The wireless device may determine the third timing / frame boundary that starts earlier than the first timing / frame boundary by a timing advance (TA) set to a sum of a timing advance value (N_TA) and the first TA offset (N_TA_offset) (e.g., TA = (N_TA + N_TA_offset) *Tc. N_TA may be updated based on one or more timing advance commands.

[0519] In an example, the fourth timing / frame boundary of the SBFD-uplink frame (S-U#i) for the plurality of uplink channels such as PUCCH, PUSCH and SRS may be determined based on the TO and not applying the first TA offset (or setting the first TA offset as zero / 0). The wireless device may use / apply the fourth starting time for an uplink transmission, via the cell, of the plurality of uplink channels during one or more SBFD symbols.

[0520] In an example, the fifth timing / frame boundary of the uplink frame (U#i) for a PRACH transmission or a PUSCH comprising a msgA during one or more UL symbols may be determined based on the third timing / frame boundary and the timing advance value (N_TA). The wireless device may not apply the timing advance value (N_TA) (or setting the timing advance value as zero / 0) for the PRACH transmission or the PUSCH comprising the msgA. The fifth timing / frame boundary may start earlier than or later than the third timing / frame boundary based on the timing advance value. The wireless device may apply the first TA offset and does not apply the timing advance value for the fifth timing / frame boundary.

[0521] In an example, the sixth timing / frame boundary of the SBFD-uplink frame (S-U#i) for a PRACH transmission or a PUSCH comprising a msgA during one or more SBFD symbols may be determined based on the fourth timing / frame boundary and the timing advance value (N_TA). The sixth timing / frame boundary may start earlier than or later than the fourth timing / frame boundary based on the timing advance value. The wireless device may not apply the first TA offset and does not apply the timing advance value for the sixth timing / frame boundary. For example, the sixth timing / frame boundary may be aligned with the first timing / frame boundary or the second timing / frame boundary.

[0522] In the specification, when a wireless device may not apply a TA offset for an uplink frame boundary and / or uplink transmissions, the wireless device may set (or may skip applying, may assume, may consider, may treat) the TA offset as zero for the uplink frame boundary and / or the uplink transmissions.

[0523] In the specification, when a wireless device may not apply a timing advance value (N_TA) for an uplink frame boundary and / or uplink transmissions, the wireless device may set (or may skip applying, may assume, may consider, may treat) the timing advance value (N_TA) as zero for the uplink frame boundary and / or the uplink transmissions.

[0524] In an example, a wireless device may receive one or more RRC messages indicating / comprising parameters for a first TAG and a second TAG for a cell or an uplink carrier of the cell. The wireless device may be configured / indicated with a first TA offset for the first TAG and a second TA offset for the second TAG for the cell or the uplink carrier of the cell. The wireless device may indicate to a base station that theDocket No.: 24-1191 PCT wireless device may require a gap between a first TA of the first TAG and a second TA of the second TAG being less than or equal to a threshold or a value (e.g., a CP length based on an active BWP of the cell or the uplink carrier of the cell). The wireless device may receive a first TAC for the first TAG. The wireless device may update the first TA based on the first TAC. The wireless device may receive a second TAC for the second TAG. The wireless device may update the second TA based on the second TAC. When a gap between the first TA and the second TA being larger than the gap, the wireless device may update the second TA based on the first TAC. The wireless device may update the second TA based on one or more TACs for the first TAG in such cases (e.g., the gap between two TAs is larger than the threshold / value). In the example, the first TAG may be associated with a first TCI state for one or more downlink or uplink symbols (non-SBFD symbols) of the cell The second TAG may be associated with a second TCI state for one or more SBFD symbols of the cell.

[0525] In an example, a wireless device may be configured with a TA offset of a TAG for a cel l / carrier. The wireless device may skip applying (or not applying) the TA offset for one or more uplink transmission during one or more SBFD symbols. The wireless device may not support simultaneous reception and transmission via the cell / carrier. The wireless device may either transmit or receive at a time via the cel l / carrier . The wireless device may require a switching time between reception (RX) and transmission (TX) for example between downlink reception to uplink transmission or vice versa. The wireless device may be scheduled with a first downlink reception during a first time and a second uplink transmission during a second time, where the first time and the second time may overlap partially or may not overlap

[0526] When the first time and the second time do not overlap, in some cases, a gap between the first time and the second time (e.g., a time interval between a start time of the second time and an end of the first time or an end time of the second time and a start time of the first time) may be smaller than a required reception to transmission (RX-TX) switching latency or transmission to reception (TX-RX) switching latency.

[0527] In an example, one or more guard symbols between the first time and the second time may be configured by a base station. In an example, a base station may not schedule the first reception and the second transmission where a gap between the first reception and the second transmission is smaller than the required RX-TX switching latency or TX-RX switching latency. This, however, may add high overhead in configuring the guard period or limit a scheduling flexibility of the base station.

[0528] In an example, a wireless device may reduce the first reception or the second transmission such that the gap between two becomes equal to or larger than the RX-TX switching l...

Claims

Docket No.: 24-1191 PCTCLAIMS1. A method comprising: receiving, by a wireless device from a base station, one or more radio resource control (RRC) messages indicating: a timing advance (TA) offset for uplink (UL) transmissions via a cell; one or more subband full duplex (SBFD) symbols for the cell; and to skip applying the TA offset to the UL transmissions during the one or more SBFD symbols; transmitting, via the cell and during one or more UL symbols, a first UL transmission based on the TA offset; and transmitting, via the cell and during the one or more SBFD symbols, a second UL transmission, wherein the TA offset is not applied to the second UL transmission.

2. A method comprising: receiving, by a wireless device from a base station, one or more messages indicating to skip applying a timing advance (TA) offset; and based on the indication, transmitting, via a cell, a first uplink (UL) transmission during one or more subband full duplex (SBFD) symbols.

3. The method of claim 2, wherein the TA offset is not applied to the first UL transmission.

4. The method of claim 2 or 3, further comprising transmitting, via the cell and during one or more UL symbols, a second UL transmission based on the TA offset.

5. The method of any one of claims 2-4, wherein the one or more messages indicate: the TA offset for UL transmissions via the cell; the one or more SBFD symbols for the cell; and to skip applying the TA offset to the UL transmissions during the one or more SBFD symbols.

6. The method of any one of claims 2-5, wherein the one or more messages are one or more radio resource control (RRC) messages.

7. The method of any one of claims 2-6, wherein: the TA offset is a first TA offset; the one or more messages indicate a timing advance group (TAG) for the cell with the first TA offset and a second TA offset; and the second TA offset is either 0 or the first TA offset.

8. The method of claim 7, wherein: the first TA offset is transmitted via a system information block (SIB) of the one or more messages; andDocket No.: 24-1191 PCT the second TA offset is transmitted via an RRC message of the one or more messages.

9. The method of any one of claims 2-8, wherein the one or more messages indicate a guard band, between an UL subband and a DL subband, which is during the one or more SBFD symbols.

10. The method of claim 9, further comprising determining to skip applying the TA offset in response to a size of the guard band being smaller than or equal to a number of physical resource blocks (PRBs).1 1 . The method of any one of claims 5-10, further comprising transmitting one or more messages indicating a capability to support not applying the TA offset for the UL transmissions via the cell during the one or more SBFD symbols.

12. The method of any one of claims 7-1 1 , further comprising determining to skip applying the TA offset for the UL transmissions via the cell during the one or more SBFD symbols, in response to the wireless device being configured with the second TA offset.

13. The method of any one of claims 2-12, further comprising dropping a reception during a time interval that is between a first time and a start time of the one or more SBFD symbols, wherein the first time starts a first preparation time before the start time of the one or more SBFD symbols.

14. The method of claim 13, wherein the first preparation time comprises a reception to transmission switching latency and a first timing advance (TA) value for a TAG of the cell.

15. The method of any one of claims 2-12, further comprising dropping a reception during a time interval that is between an end time of the one or more SBFD symbols and a second time, where the second time starts a second preparation time after the end time of the one or more SBFD symbols.

16. The method of claim 15, wherein the second preparation time comprises a transmission to reception switching latency.

17. The method of any one of claims 2-6 and 13-16, wherein: the TA offset is a first TA offset; the one or more messages further comprise a second TA offset; and the method comprises determining to skip applying the first TA offset, in response to receiving the second TA offset.

18. The method of claim 17, wherein the one or more messages further indicate: a first timing advance group (TAG) with the first TA offset; and a second TAG with the second TA offset.

19. The method of claim 17 or 18, further comprising receiving a medium access control control element (MAC CE) comprising a first TA command for the first TAG and the second TAG, wherein the MAC CE comprises either a first identifier (ID) of the first TAG or a second ID of the second TAG.

20. The method of claim 19, further comprising applying the first TA command for the first TAG and the second TAG, based on receiving the MAC CE.Docket No.: 24-1191 PCT21. The method of any one of claims 18-20, further comprising not starting a validity timer for the second TAG.

22. A method comprising: transmitting, by a wireless device to a base station, one or more messages indicating a capability of the wireless device, wherein the capability indicates that the wireless device supports reception of a downlink signal and transmission of an uplink signal during one or more subband full duplex (SBFD) symbols with a gap between the reception and the transmission being less than a switching gap for switching between signal reception and signal transmission; receiving one or more downlink commands scheduling a first downlink reception ending on a first symbol of a cell and a first uplink transmission starting on an SBFD symbol of the cell, wherein a gap between the SBFD symbol and the first symbol is less than the switching gap; and based on the capability of the wireless device, receiving, via the cell, the first downlink reception and transmitting, via the cell, the first uplink transmission, wherein the receiving of the first downlink reception and the transmitting of the first uplink transmission are based on shortening the first downlink reception or the first uplink transmission.

23. A method comprising transmitting, by a wireless device to a base station, one or more messages indicating a capability of the wireless device, wherein: the capability indicates that the wireless device supports reception of a downlink signal and transmission of an uplink signal during one or more subbband full duplex (SBFD) symbols; and a gap between the reception and the transmission is less than a switching gap.

24. The method of claim 23, wherein the switching gap is for the wireless device to switch between signal reception and signal transmission.

25. The method of claim 24, wherein the capability indicates that the wireless device supports the reception of the downlink signal and the transmission of the uplink signal during the one or more SBFD symbols, with the gap being less than the switching gap.

26. The method of any one of claims 23-25, further comprising receiving one or more downlink commands scheduling a first downlink reception ending on a first symbol of a cell and a first uplink transmission starting on an SBFD symbol of the cell, wherein a gap between the SBFD symbol and the first symbol is less than the switching gap.

27. The method of claim 26, further comprising, based on the capability of the wireless device, receiving, via the cell, the first downlink reception and transmitting, via the cell, the first uplink transmission, wherein the receiving of the first downlink reception and the transmitting of the first uplink transmission are based on shortening the first downlink reception or the first uplink transmissionDocket No.: 24-1191 PCT28. The method of any one of claims 23-27, wherein the switching gap is to switch from signal reception to signal transmission.

29. The method of any one of claims 26-28, wherein the first downlink reception is during one or more SBFD symbols.

30. The method of any one of claims 26-28, wherein the first downlink reception is during one or more non-SBFD symbols.31 . The method of any one of claims 26-30, wherein the first uplink transmission is during one or more non-SBFD symbols.

32. A method comprising: transmitting, by a base station to a wireless device, one or more radio resource control (RRC) messages indicating: a timing advance (TA) offset for uplink (UL) transmissions via a cell; one or more subband full duplex (SBFD) symbols for the cell; and to skip applying the TA offset to the UL transmissions during the one or more SBFD symbols; receiving, via the cell and during one or more UL symbols, a first UL transmission based on the TA offset; and receiving, via the cell and during the one or more SBFD symbols, a second UL transmission, wherein the TA offset is not applied to the second UL transmission.

33. A method comprising: transmitting, by a base station to a wireless device, one or more messages indicating to skip applying a timing advance (TA) offset; and based on the indication, receiving, via a cell, a first uplink (UL) transmission during one or more subband full duplex (SBFD) symbols.

34. The method of claim 33, wherein the TA offset is not applied to the first UL transmission.

35. The method of claim 33 or 34, further comprising receiving, via the cell and during one or more UL symbols, a second UL transmission based on the TA offset.

36. The method of any one of claims 33-35, wherein the one or more messages indicate: the TA offset for UL transmissions via the cell; the one or more SBFD symbols for the cell; and to skip applying the TA offset to the UL transmissions during the one or more SBFD symbols.

37. The method of any one of claims 33-36, wherein the one or more messages are one or more radio resource control (RRC) messages.

38. A method comprising:Docket No.: 24-1191 PCT receiving, by a base station from a wireless device, one or more messages indicating a capability of the wireless device, wherein the capability indicates that the wireless device supports reception of a downlink signal and transmission of an uplink signal during one or more subband full duplex (SBFD) symbols with a gap between the reception and the transmission being less than a switching gap for switching between signal reception and signal transmission; transmitting one or more downlink commands scheduling a first downlink reception ending on a first symbol of a cell and a first uplink transmission starting on an SBFD symbol of the cell, wherein a gap between the SBFD symbol and the first symbol is less than the switching gap; and based on the capability of the wireless device, transmitting, via the cell, the first downlink reception and receiving, via the cell, the first uplink transmission, wherein the transmitting of the first downlink reception and the receiving of the first uplink transmission are based on shortening the first downlink reception or the first uplink transmission.

39. A method comprising receiving, by a base station from a wireless device, one or more messages indicating a capability of the wireless device, wherein: the capability indicates that the wireless device supports reception of a downlink signal and transmission of an uplink signal during one or more subbband full duplex (SBFD) symbols; and a gap between the reception and the transmission is less than a switching gap.

40. The method of claim 39, wherein the switching gap is for the wireless device to switch between signal reception and signal transmission.41 . The method of claim 40, wherein the capability indicates that the wireless device supports the reception of the downlink signal and the transmission of the uplink signal during the one or more SBFD symbols, with the gap being less than the switching gap.

42. The method of any one of claims 39-41 , further comprising transmitting one or more downlink commands scheduling a first downlink reception ending on a first symbol of a cell and a first uplink transmission starting on an SBFD symbol of the cell, wherein a gap between the SBFD symbol and the first symbol is less than the switching gap.

43. The method of claim 42, further comprising, based on the capability of the wireless device, transmitting, via the cell, the first downlink reception and receiving, via the cell, the first uplink transmission, wherein the transmitting of the first downlink reception and the receiving of the first uplink transmission are based on shortening the first downlink reception or the first uplink transmission.

44. A wireless device comprising: one or more processors; andDocket No.: 24-1191 PCT memory storing instructions that, when executed by the one or more processors, cause the wireless device to perform the method of any one of claims 1 -31 .

45. A base station comprising: one or more processors; and memory storing instructions that, when executed by the one or more processors, cause the base station to perform the method of any one of claims 32-43.

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

47. A system comprising: a base station comprising: one or more first processors; and first memory storing instructions that, when executed by the one or more first processors, cause the base station to perform the method of any one of claims 1 -31 ; and a wireless device comprising: one or more second processors; and second memory storing instructions that, when executed by the one or more second processors, cause the wireless device to perform the method of any one of claims 32-43.

Images