Downlink receptions in subband full-duplex systems

Abstract

A wireless device receives downlink control information (DCI) scheduling downlink receptions in subband full duplex (SBFD) symbols and non-SBFD symbols. An offset between reception of the DCI and a starting symbol of the downlink receptions is less than a threshold. Based on the offset being less than the threshold, the wireless device receives the downlink receptions in a default symbol type among the SBFD symbols and the non-SBFD symbols.

Description

Docket No.: 24-1218PCTTITLEDownlink Receptions in Subband Full-Duplex SystemsCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 703,164, filed October 3, 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. 1 B 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. 11 A 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-1218PCT

[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 aCORESET 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] FIGs. 17A and 17B are signal flow diagrams illustrating aspects of transmission configuration indicator (TCI) state indication according to the present disclosure.

[0024] FIG. 18 is a signal flow diagram illustrating aspects of subband full-duplex (SBFD) operation according to the present disclosure.

[0025] FIG. 19 is a signal flow diagram illustrating aspects according to the present disclosure.

[0026] FIG. 20 is a flowchart illustrating aspects of a process performed by a wireless device according to the present disclosure.

[0027] FIG. 21 is a flowchart illustrating aspects of a process performed by a base station according to the present disclosure.DETAILED DESCRIPTION

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

[0029] 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 radioDocket No.: 24-1218PCT 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.

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

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

[0032] If A and B are sets and every element of A is an element of B, A is called a subset of B. In this specification, only non-empty sets and subsets are considered. For example, possible subsets of B = {celH , cell2} are: {celH}, {cell2}, and {celH , cell2}. The phrase “based on” (or equally “based at least on”) is indicative that the phrase following the term “based on” is an example of one of a multitude of suitableDocket No.: 24-1218PCT 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.

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

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

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

[0036] 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 definedDocket No.: 24-1218PCT 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.

[0037] FIG. 1A 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.

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

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

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

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

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

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

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

[0045] 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 nextgeneration RAN (NG-RAN). Embodiments may be applicable to RANs of other mobile communication networks, such as the RAN 104 in FIG. 1 A, 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.

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

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

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

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

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

[0051] The NG-RAN 154 may connect the 5G-CN 152 to the UEs 156 through radio communications over the air interface. The NG-RAN 154 may include one or more gNBs, illustrated as gNB 160A and gNB 160B (collectively gNBs 160) and / or one or more ng-eNBs, illustrated as ng-eNB 162A and ng-eNB 162B (collectively ng-eNBs 162). The gNBs 160 and ng-eNBs 162 may be more generically referred to as base stations. The gNBs 160 and ng-eNBs 162 may include one or more sets of antennas for communicating with the UEs 156 over an air interface. For example, one or more of the gNBs 160 and / or one or more of the ng-eNBs 162 may include three sets of antennas to respectively control threeDocket No.: 24-1218PCT 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.

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

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

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

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

[0056] As discussed, an interface (e.g., Uu, Xn, and NG interfaces) between the network elements in FIG. 1B 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.

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

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

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

[0060] 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 preventDocket No.: 24-1218PCT unauthorized decoding of data transmitted over the air interface, and integrity protection (to ensure control messages originate from intended sources. The PDCPs 214 and 224 may perform retransmissions of undelivered packets, in-sequence delivery and reordering of packets, and removal of packets received in duplicate due to, for example, an Intra-gNB 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0074] - a common control channel (CCCH) for carrying control messages together with random access;Docket No.: 24-1218PCT

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0090] 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 synchronizationDocket No.: 24-1218PCT 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.

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

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

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

[0094] 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.Docket No.: 24-1218PCT2B, 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., RRCJDLE), and RRC inactive 606 (e.g., RRCJNACTIVE).

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

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

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

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

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

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

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

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

[0103] 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 aDocket No.: 24-1218PCT 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 time-domain samples that represent the summation of the F orthogonal subcarriers. The F time-domain samples may form a single OFDM symbol. After some processing (e.g., addition of a cyclic prefix) and up-conversion, an OFDM symbol provided by the IFFT block may be transmitted over the air interface on a carrier frequency. The F parallel symbol streams may be mixed using an FFT block before being processed by the IFFT block. This operation produces Discrete Fourier Transform (DFT)-precoded OFDM symbols and may be used by UEs in the uplink to reduce the peak to average power ratio (PAPR). Inverse processing may be performed on the OFDM symbol at a receiver using an FFT block to recover the data mapped to the source symbols.

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

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

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

[0107] 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 275*12 = 3300 subcarriers. Such a limitation, if used, may limit the NR carrier to 50, 100, 200, and 400 MHz for subcarrier spacings of 15, 30, 60, and 120 kHz, respectively, where the 400 MHz bandwidth may be set based on a 400 MHz per carrier bandwidth limit.

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

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

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

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

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

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

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

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

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

[0117] 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 DCIDocket No.: 24-1218PCT 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).

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

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

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

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

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

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

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

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

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

[0127] 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 , UCI 1032, and UC1 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 , UCI 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.

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

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

[0130] 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 aDocket No.: 24-1218PCT 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.

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

[0132] 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. 11A) and may span one or more subcarriers in the frequency domain (e.g., 240 contiguous subcarriers). The PSS, the SSS, and the PBCH may have a common center frequency. The PSS may be transmitted first and may span, for example, 1 OFDM symbol and 127 subcarriers The SSS may be transmitted after the PSS (e.g., two symbols later) and may span 1 OFDM symbol and 127 subcarriers. The PBCH may be transmitted after the PSS (e.g., across the next 3 OFDM symbols) and may span 240 subcarriers.

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

[0134] 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 hasDocket No.: 24-1218PCT 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.

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

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

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

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

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

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

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

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

[0143] 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-M I MO, 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.Docket No.: 24-1218PCTThe UE may use the one or more downlink DMRSs for coherent demodulation / channel estimation of the PDSCH.

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

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

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

[0147] 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 mayDocket No.: 24-1218PCT 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.

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

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

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

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

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

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

[0154] 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. 11 B 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-RSDocket No.: 24-1218PCT 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.

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

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

[0157] 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 stationDocket No.: 24-1218PCT 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 (PM I), a channel quality indicator (CQI), and / or a rank indicator (Rl).

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

[0159] 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 U 1 ). Beamforming at the UE may include, e.g., a Tx beam sweep from a set of beams (shown in the bottom rows of U1 and U3 as ovals rotated in a clockwise direction indicated by the dashed arrow). Beamforming at the base station may include, e.g., an Rx beam sweep from a set of beams (shown, in the top rows of U1 and U2, as ovals rotated in a counterclockwise direction indicated by the dashed arrow). Procedure U2 may be used to enable the base station to adjust its Rx beam when the UE uses a fixed Tx beam. The UE and / or the base station may perform procedure U2 using a smaller set of beams than is used in procedure P1 , or using narrower beams than the beams used in procedure P1. This may be referred to as beam refinement The UE may perform procedure U3 to adjust its Tx beam when the base station uses a fixed Rx beam.

[0160] 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 errorDocket No.: 24-1218PCT 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).

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

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

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

[0164] 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'y, cellspecific parameters (e.g., RACH-ConfigCommon),' and / or dedicated parameters (e.g., RACH-Docket No.: 24-1218PCT config Dedicated). 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.

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

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

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

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

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

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

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

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

[0173] 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 PDUDocket No.: 24-1218PCT 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.

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

[0175] 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 message1320 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 11321 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.

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

[0177] After transmitting a preamble, the UE may start a time window (e.g., ra-ResponseWindow) to monitor a PDCCH for the RAR. In the event of a beam failure recovery request, the base station may configure the UE with a separate time window and / or a separate PDCCH in a search space indicated by an RRC message (e.g., recoverySearchSpaceld). The UE may monitor for a PDCCH transmission addressed to a Cell RNTI (C-RNTI) on the search space. In the contention-free random access procedure illustrated in FIG. 13B, the UE may determine that a random access procedure successfullyDocket No.: 24-1218PCT 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.

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

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

[0180] 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 UEs RRC state; a type of spectrum (e.g., licensed vs. unlicensed); and / or any other suitable factors.

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

[0182] The transport block 1342 may comprise data (e.g., delay-sensitive data), an identifier of the U E, 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).

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

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

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

[0186] DCIs may be used for different purposes. A purpose may be indicated by the type of RNTI used to scramble the CRC parity bits. For example, a DCI having CRC parity bits scrambled with a paging RNTI (P-RNTI) may indicate paging information and / or a system information change notification. The P-RNTI may be predefined as “FFFE” in hexadecimal. A DCI having CRC parity bits scrambled with a system information RNTI (SI-RNTI) may indicate a broadcast transmission of the system information. The SI-RNTI may be predefined as “FFFF" in hexadecimal. A DCI having CRC parity bits scrambled with a random access RNTI (RA-RNTI) may indicate a random access response (RAR). A DCI havingDocket No.: 24-1218PCTCRC 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.

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

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

[0189] 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 orDocket No.: 24-1218PCT 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.

[0190] FIG. 14B illustrates an example of a CCE-to-REG mapping for DOI 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.

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

[0192] 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 noninterleaved, and / or mapping parameters) for the CORESET based on configuration parameters of the CORESET. The UE may determine a number (e.g., al most 10) of search space sets configured on the CORESET based on the RRC messages. The UE may monitor a set of PDCCH candidates according to configuration parameters of a search space set. The UE may monitor a set of PDCCH candidates in one or more CORESETs for detecting one or more DCIs. Monitoring may comprise decoding one or more PDCCH candidates of the set of the PDCCH candidates according to the monitored DCI formats. Monitoring may comprise decoding a DCI content of one or more PDCCH candidates with possible (orDocket No.: 24-1218PCT 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).

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

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

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

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

[0197] 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-1218PCT

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

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

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

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

[0202] 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-antennaDocket No.: 24-1218PCT techniques, such as spatial multiplexing (e.g., single-user MIMO or multi-user M IMO), transmit / receive diversity, and / or beamforming. In other examples, the wireless device 1502 and / or the base station 1504 may have a single antenna.

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

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

[0205] 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 solarDocket No.: 24-1218PCT cell, a fuel cell, or any combination thereof. The processing system 1508 and / or the processing system 1518 may be connected to a GPS chipset 1517 and a GPS chipset 1527, respectively. The GPS chipset 1517 and the GPS chipset 1527 may be configured to provide geographic location information of the wireless device 1502 and the base station 1504, respectively.

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

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

[0208] 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 complexvalued modulation symbols on a layer for transmission on the antenna ports; mapping of complexvalued 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.

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

[0210] 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).Docket No.: 24-1218PCTThe wireless device may communicate with at least one base station (e.g. two or more base stations in dual connectivity) via the plurality of cells. The one or more messages (e.g. as a part of the configuration parameters) may comprise parameters of physical, MAC, RLC, PCDP, SDAP, RRC layers for configuring the wireless device. For example, the configuration parameters may comprise parameters for configuring physical and MAC layer channels, bearers, etc. For example, the configuration parameters may comprise parameters indicating values of timers for physical, MAC, RLC, PCDP, SDAP, RRC layers, and / or communication channels.

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

[0212] FIGs. 17A and 17B illustrate examples procedures for beam indication based on TCI states. FIG. 17A illustrates an example of a wireless device 1700 receiving, from a base station 1720, channelspecific beam indications for separate downlink physical channels, such as the PDCCH and the PDSCH. FIG. 17B illustrates an example of a wireless device 1740 receiving, from a base station 1760, beam indications applicable to multiple physical channels (i.e., common among physical channels), such as TCI states for downlink receptions and / or uplink transmissions. This approach of using a TCI state for multiple physical channels as illustrated in FIG. 17B may be referred to as a unified TCI state framework.

[0213] As illustrated in FIG. 17A, wireless device 1700 receives one or more RRC messages 1702 from base station 1720. One or more RRC messages 1702 may indicate one or more TCI states for one or more CORESETs. For example, one or more RRC messages 1702 may comprise a list of TCI states (e.g., a list of IDs of TCI states) for CORESETs of wireless device 1700.Docket No.: 24-1218PCT

[0214] Each TCI state may indicate one or more reference signals. For example, each TCI state may comprise one or more IDs of one or more reference signals. The one or more reference signals of a TCI state may be used for channel estimation (including beam determination) such that a signal that is quasi co-located (QCL'ed) with the reference signal of a TCI state may experience the same channel conditions (e.g., channel distortions) and properties as the reference signal of the TCI state. As the reference signal is a known sequence (e.g., a pilot signal), the effects of the channel on the signal may be inferred from the effects of the channel on the reference signal.

[0215] A TCI state may indicate which, so-called, large-scale channel properties may be inferred from the QCL association between a signal and a reference signal indicated by a TCI state. To do so, each of the one or more reference signals indicated by a TCI state may be associated with a QCL type. In an example, there may be four QCL types, such as QCL Type-A, QCL Type-B, QCL Type-C, and QCL Type-D. QCL Type-A may be used to estimate Doppler shift, Doppler spread, average delay, and delay spread. QCL Type-B may be used to estimate Doppler shift and Doppler spread. QCL Type-C may be used to estimate average delay and Doppler shift. QCL Type-D may be used for spatial domain parameters (e.g., one or more parameters for spatial domain filters, and / or QCL relationships between antenna ports, used to receive downlink signals).

[0216] A reference signal of a TCI state with a QCL type of QCL Type-D may be used for beam determination. For example, when a signal is quasi co-located with a reference signal of a TCI state with QCL Type-D, wireless device 1700 may determine (e.g., assume or infer) that base station 1720 applies the same spatial (domain) filter to both the signal and the reference signal of the TCI states. By being able to determine (e.g., assume or infer) the spatial domain (transmission) filter applied by base station 1720 to a signal (from the spatial domain filter applied to the QCL'd reference signal), wireless device 1700 may apply a spatial domain (reception) filter suitable to receive the signal. The spatial domain filter used to receive a downlink signal may be referred to as a spatial filter, a spatial domain filter parameter, a spatial domain reception filter, quasi co-location of (e.g., antenna ports of) a downlink signal with (e.g., antenna ports of) a reference signal. The quasi co-location of the downlink signal with the reference signal may be referred to as a QCL assumption, a QCL relationship, and / or QCL information.

[0217] Returning to FIG. 17A, wireless device 1700 receives one or more RRC messages 1702 that indicate TCI states. For example, one or more RRC messages 1702 may comprise a list of TCI states of a CORESET (e.g., a list of IDs of TCI states). Wireless device 1700 may use the TCI states in the list for receiving PDCCHs on the CORESETs. The TCI states indicated by one or more RRC messages 1702 may be referred to as configured TCI states or RRC-configured TCI states.

[0218] FIG. 17A illustrates that wireless device 1700 receives MAC CE 1704 from base station 1720. MAC CE 1704 may indicate, or activate, one or more TCI states configured by one or more RRCDocket No.: 24-1218PCT messages 1702. For example, MAC CE 1704 may indicate a (e.g., single) TCI state for one or more CORESETs (e.g., for PDCCH receptions via the one or more CORESETs). As another example, MAC CE 1704 may activate a plurality of TCI states that may be used (applied) for PDCCH receptions via CORESETs. The TCI states indicated by MAC CE 1704 may be referred to as activated TCI states or MAC-CE activated TCI states.

[0219] Wireless device 1700 may determine one or more spatial domain filter parameters (e.g., QCL information) based on a reference signal indicated by the TCI state. For example, FIG. 17A illustrates that wireless device 1700 receives PDCCH 1706, of a CORESET, via a TCI state of the CORESET.

[0220] For PDSCH reception, a DCI may be used to indicate which TCI state, among the TCI states (e.g., for the CORESETs) activated by MAC CE 1704, wireless device 1700 is to use (apply) for receiving PDSCH receptions (e.g., data, transport blocks, code block groups of a transport block). As illustrated, wireless device 1700 receives DC1 1708. DC1 1708 schedules a PDSCH reception 1710 and indicates which TCI state, among the activated TCI states, wireless device 1700 is to use (apply) for receiving PDSCH reception 1710. A TCI state indicated by a DCI may be referred to as an indicated TCI state. Similarly, a TCI state indicated by a MAC CE that indicates a single TCI (e.g., one TCI state) state may be referred to as an indicated TCI state.

[0221] Although DCI 1708 indicates a TCI state to use for receiving PDSCH reception 1710, wireless device 1700 may apply a different TCI state depending on an offset (e.g., in time) between receiving DCI 1708 and PDSCH reception 1710. For example, DC1 1708 may schedule PDSCH reception 1710 within an offset 1712. Offset 1712 may be referred to as a scheduling offset. Offset 1712 may be a duration or a number of symbols. Offset 1712 may be based on a UE-capability of wireless device 1700.

[0222] Based on DC1 1708 scheduling PDSCH reception 1710 within offset 1712, wireless device 1700 may apply the TCI state of the CORESET (e.g., instead of the TCI state indicated by DC1 1708). That is, wireless device 1700 applies the TCI state used to receive PDCCH 1706 (e.g., and does not apply the TCI state indicated by DC1 1708 for receiving PDSCH reception 1710).

[0223] Within offset 1712, wireless device 1700 may be unable to (successfully) decode DC1 1708, update the spatial filtering, and / or retune RF chains in time for receiving PDSCH reception 1710. By using the TCI state of the CORESET used to receive PDCCH 1706 (instead of the TCI state indicated in DC1 1708 for receiving the PDSCH reception 1710), this allows wireless device 1700 to receive PDSCH reception 1710 within offset 1712.

[0224] On the other hand, when, e.g., PDSCH reception 1710 is scheduled after offset 1712, wireless device 1700 may apply the TCI state indicated by DC1 1708 for receiving PDSCH reception 1710. For example, FIG. 17A illustrates that wireless device 1700 receives, from base station 1720, PDSCH reception 1710 via the TCI state indicated by DC1 1708. As another example (e.g., regardless of offsetDocket No.: 24-1218PCT1712), in response to DC1 1708 not comprising a field indicating a TCI state (any TCI state) for PDSCH reception 1710 (e.g., based on a DCI format of DC1 1708, such as DC1 1_0), wireless device 1700 may apply the TCI state of the CORESET for PDSCH reception 1710.

[0225] In the example illustrated in FIG. 17A, base station 1720 may transmit separate beam indications for the PDCCH and the PDSCH, along with separate beam indications for each PDSCH transmission. FIG. 17B illustrates an example of a unified TCI state framework. Under the unified TCI state framework, a single TCI state (or a set of TCI states) may be indicated for each of the downlink physical channels, such as a single TCI state is applied to both PDCCH and PDSCH transmissions A TCI state that is applied to both the PDCCH and PDSCH may be referred to as a downlink TCI state (or a joint-downlink TCI state). For uplink beam indications under the unified TCI state framework, a TCI state (or a set of TCI states) may be indicated for each of the uplink physical channels, such as a single TCI state is applied to both PUCCH and PUSCH transmissions. A TCI state that is applied to both the PUCCH and PUSCH may be referred to as an uplink TCI state.

[0226] In addition to providing TCI states that are applied to each of the physical channels in the downlink or uplink, the unified TCI state framework may also be used to indicate a single TCI state (or a set of TCI states) for both downlink and uplink. That is, the TCI state is applied to each of the downlink and uplink physical channels, such as the PDCCH, PDSCH, PUCCH, and PUSCH. A TCI state that is applicable to both downlink and uplink may be referred to as a joint TCI state, a joint-downlink TCI state, a joint DL / UL TCI state, or a common TCI state. A TCI state applicable to the unified TCI state framework may be referred to as a unified TCI state.

[0227] As an example of the unified TCI state framework, FIG. 17B illustrates that wireless device 1740 receives, from base station 1760, one or more RRC messages 1714. One or more RRC messages 1714 indicates a plurality of TCI states. The plurality of TCI states may be a plurality of unified TCI states. As an example, one or more RRC messages 1714 may comprise a list of TCI states. The list of TCI states may be applicable to downlink and / or uplink (e.g., each of the downlink physical channels and / or each of the uplink physical channels). The list of TCI states may be a list of downlink TCI states, and the absence of a (separate) list of uplink TCI states may imply that the list of downlink TCI states is applicable to both the downlink and uplink (physical channels). The list of downlink TCI states may be referred to as a list of joint-downlink TCI states.

[0228] In another example, one or more RRC messages 1714 may comprise separate lists of TCI states for downlink and uplink. For example, the list of TCI states may comprise a list of downlink TCI states and a list of uplink TCI states. In this example, the list of downlink TCI states are applicable to the downlink (physical channels) and the list of uplink TCI states are applicable to the uplink (physical channels). Additionally or alternatively, one or more RRC messages 1714 may comprise a parameterDocket No.: 24-1218PCT set to joint or separate to indicate that the list of TCI states is (e.g., jointly) applicable for both downlink and uplink or that separate lists are configured for downlink and uplink. It should be noted that a list of TCI states applicable to downlink may be referred to as a list of joint-downlink TCI states even when a separate list of uplink TCI states are configured.

[0229] As another example, one or more RRC messages 1714 may indicate one (e.g., a single) TCI state instead of a plurality of TCI states. In response to one or more RRC messages 1714 indicating one TCI state, wireless device 1740 may (e.g., start to) apply the TCI state (e.g., without additional signaling via MAC CE and / or DCI).

[0230] Similar to the TCI states indicated by one or more RRC messages 1702 of FIG. 17A, the plurality of TCI states indicated by one or more RRC messages 1714 may be referred to as configured TCI states or RRC-configured TCI states.

[0231] As illustrated in FIG. 17B, wireless device 1740 receives a MAC CE 1716 indicating activation of one or more TCI states (e.g., of the plurality of TCI states configured by one or more RRC messages 1714). For example, MAC CE 1716 may indicate TCI state IDs of a plurality of TCI states for activation. As an example, MAC CE 1716 may comprise a field indicating a TCI state ID for each of the one or more TCI states activated by MAC CE 1716. The field may be referred to as a TCI state ID field. The TCI states activated by MAC CE 1716 may be referred to as activated TCI states.

[0232] MAC CE 1716 may map (e.g., associate) TCI state ID fields, in MAC CE 1716, to a codepoint value corresponding to one or more TCI states (a TCI codepoint or TCI state codepoint). MAC CE 1716 may comprise a field indicating whether a TCI codepoint, corresponding to the field, is associated with (e.g., is mapped to) a single TCI state ID or multiple TCI state IDs (e.g., two TCI state IDs). For example, a first value (e.g., 0) of the field may indicate that a (single) TCI codepoint (e.g., 00) is mapped to a (single) TCI state ID field (e.g., the TCI codepoint is mapped to one TCI state ID indicated by one TCI state ID field MAC CE 1716). A second value (e.g., 1) of the field may indicate that a (single) TCI codepoint (e.g., 00) is mapped to multiple TCI state ID fields (e.g., the TCI codepoint is mapped to two TCI state IDs indicated by two consecutive TCI state ID fields of MAC CE 1716). The ordinal position of the field in MAC CE 1716 may correspond to a TCI state ID field is the same relative ordinal position (e.g., the last field may correspond to the last TCI state ID field in MAC CE 1716). The field may be referred to as a TCI codepoint mapping field.

[0233] MAC CE 1716 may comprise a field indicating whether a TCI state ID, indicated by a TCI state ID field (e.g., in the same octet as the field), is an ID of a joint-downlink TCI state or an uplink TCI state. This may enable wireless device 1740 to identify the TCI state ID from a list of joint-downlink TCI states and a list of uplink TCI states (e.g., in case the same value of a TCI state ID is used by a TCI state in the joint-downlink TCI states and another TCI state in the list of uplink TCI states). The field indicatingDocket No.: 24-1218PCT whether a TCI state ID is an ID of a joint-downlink TCI state or an uplink TCI state may be referred to as a D / U field (where D refers to TCI states applicable to downlink or to both downlink and uplink, and U refers to TCI states applicable to uplink).

[0234] There may be two signaling mechanisms to indicate which TCI state that wireless device 1740 is to apply among the TCI states configured by one or more RRC messages 1714. In a first signaling mechanism, MAC CE 1716 may indicate to (start to) apply (e.g., and / or indicate activation of) a TCI state (e.g., a single TCI state) (without any additional signaling by, e.g., a DCI). Additionally or alternatively, MAC CE 1716 may indicate to apply multiple TCI states in the first mechanism by indicating a mapping for a single TCI codepoint. For example, based on the field indicating that a TCI codepoint, corresponding to the field, is associated with multiple TCI state IDs (e.g., two TCI state IDs), MAC CE 1716 may indicate to (start to) apply multiple TCI states (without any additional signaling by, e.g., a DCI).

[0235] In a second signaling mechanism, MAC CE 1716 indicates activation of a plurality of TCI states. The plurality of TCI states are mapped, by MAC CE 1716, to a plurality of TCI codepoints and a DCI indicates one of the TCI codepoints for wireless device 1740 to apply. For example, as illustrated in FIG. 17B, wireless device 1740 receives a DC1 1718. DC1 1718 indicates a TCI state (e.g., a TCI codepoint) among the TCI states activated by MAC CE 1716 For example, DC1 1718 may comprise a field indicating a TCI codepoint. The field may be referred to as a TCI field or a TCI state field. The value of the TCI field may indicate the TCI state (e.g., the TCI codepoint value associated with the TCI state). Based on (e.g., the TCI field of) DC1 1718 indicating the TCI state among the activated TCI states, wireless device 1740 applies (starts to apply) the TCI state.

[0236] A TCI state indicated by MAC CE 1716 and / or DC1 1718 may be referred to as an indicated TCI state or an updated TCI state. The indicating by MAC CE 1716 and / or DCI 1718 may be referred to as updating the TCI state (e.g., the indicated TCI state or the current TCI state). For example, by indicating a TCI state for downlink and / or uplink, MAC CE 1716 (in the first mechanism) may be said to update the (indicated) TCI state. Similarly, when MAC CE 1716 indicates activation of a plurality of TCI states and DCI 1718 indicates a TCI state for downlink and / or uplink, DC1 1718 may be said to update the (indicated) TCI state.

[0237] After the TCI state is indicated by MAC CE 1716 and / or DC1 1718, wireless device 1740 applies the TCI state to receive downlink receptions and / or transmit uplink transmissions. The (indicated) TCI state may remain as the TCI state that wireless device 1740 applies to (subsequent) downlink receptions and uplink receptions (e.g., until another TCI state is indicated, or updated, by a subsequent MAC CE and / or DCI).Docket No.: 24-1218PCT

[0238] For example, returning to FIG. 1 ZB, wireless device 1740 receives a DC1 1722 from base station 1760 (e.g., after the TCI state indicated by MAC CE 1716 and / or DC1 1718 is applied). DC1 1722 schedules one or more downlink transmissions 1724 and / or schedules (or triggers) one or more uplink transmissions 1726. Wireless device 1740 receives one or more downlink transmissions 1724 based on the TCI state indicated by MAC CE 1716 and / or DC1 1718. Similarly, wireless device 1740 transmits one or more uplink transmissions 1726 based on the TCI state indicated by MAC CE 1716 and / or DC1 1718.

[0239] FIG. 18 illustrates an example of a wireless device 1800 and a wireless device 1820 communicating with a base station 1840 in a subband full-duplex (SBFD) system. The SBFD system may be referred to as an SBFD operation or a cell in SBFD operation.

[0240] As illustrated in FIG. 18, wireless device 1800 and wireless device 1820 communicate with base station 1840 in SBFD operation. In an example of SBFD operation, a cell (e.g., a carrier of a cell) operates in time division duplex (TDD) (e.g., a TDD mode, a TDD operation, and / or a TDD carrier of the cell). In TDD, uplink and downlink communications generally occur in the same frequency range (e.g., same frequency, same bandwidth, same channel, or same band). In TDD, units of time (within the same bandwidth) are divided into (reoccurring) time intervals that typically have the same duration in time for a given subcarrier spacing, such as subframes, slots, and / or symbols.

[0241] Generally, in TDD mode, communications are performed in a single link direction (e g., uplink or downlink) within a given time interval. For example, in TDD, wireless device 1800 and wireless device 1820 may both be able to transmit (e.g., be scheduled to transmit) uplink transmissions to base station 1840 in a given time interval, such as a slot (e.g., an uplink slot). The same principle applies to the downlink. A TDD mode may be referred to as a half-duplex operation (in which transmissions or receptions, and not both, occur during a given time interval, such as a slot). On the other hand, in SBFD operation, different link directions may be applied to the same time interval. For example, in a given time interval, such as a slot, wireless device 1800 may transmit an uplink transmission to base station 1840 while (in the same given time interval, such as the slot) wireless device 1820 may receive a downlink transmission from base station 1840. In SBFD, wireless device 1800 and wireless device 1820 may communicate in half-duplex operation (e.g., non-simultaneous transmission and reception) and base station 1840 may operate in a full-duplex operation (e.g., simultaneous transmission and reception in non-overlapping subbands or frequency resources). SBFD operation may be referred to as nonoverlapping full-duplex operation or non-overlapping SBFD operation.

[0242] As illustrated in FIG. 18, wireless device 1800 and wireless device 1820 may receive one or more RRC messages 1802. One or more RRC messages 1802 may be (or comprise), e.g., one or more one or more SIBs (e.g., SIB1) of the cell of base station 1840 and / or one or more RRC reconfiguration messages (e.g., RRCReconfiguration).Docket No.: 24-1218PCT

[0243] One or more RRC messages 1802 comprises a TDD configuration of a cell of base station 1840. The TDD configuration may comprise, or indicate, one or more parameters for TDD operation on the cell. For example, the TDD configuration may indicate a pattern of time intervals in a cell of base station 1840. As an example, the time intervals may be slots. The pattern may be referred to as a TDD pattern. The TDD configuration may indicate a plurality of patterns (e.g., a first pattern and a second pattern).

[0244] As an example of indicating a pattern, the TDD configuration may comprise one or more parameters of the pattern. For example, the one or more parameters of the pattern, indicated by the TDD configuration, may indicate (or comprise) a periodicity of the pattern. The periodicity may be a transmission periodicity, such as 0.5 ms, 0.65 ms, 1 ms, 1.25 ms, 2 ms, 3ms, 4 ms, 5 ms, 10 ms. The TDD configuration may indicate a subcarrier spacing (e.g., reference subcarrier spacing) to be used to determine the number of slots within a periodicity of a pattern indicated by the TDD configuration.

[0245] Additionally or alternatively, the one or more parameters of the pattern, indicated by the TDD configuration, may indicate a number of downlink slots in the pattern. The number of downlink slots may be a number of full downlink slots (e.g., which comprise all, or only, downlink symbols and / or no uplink symbols). The pattern may indicate a number of downlink symbols. The number of downlink symbols may be a number of consecutive downlink symbols. The number of downlink symbols may start from a reference point, such as the beginning of a slot after the last downlink slot indicated by the number of downlink slots. The pattern may indicate a number of uplink slots in the pattern. The number of uplink slots may be a number of full uplink slots (e.g., which comprise all, or only, uplink symbols and / or no downlink symbols). The pattern may indicate a number of uplink symbols. The number of uplink symbols may be a number of consecutive uplink symbols. The number of uplink symbols may start from a reference point, such as in a slot preceding an initial (e.g., earliest) uplink slot indicated by the number of uplink slots.

[0246] The pattern may indicate that one or more symbols (or slots) are flexible in which uplink or downlink may be scheduled (e.g., by base station 1840) or otherwise occur (e g., autonomously transmitted by wireless device 1800 and / or wireless device 1820). For example, the pattern may (explicitly) indicate a number of symbols (or slots) that are flexible symbols (or flexible slots). Additionally or alternatively, the pattern may (implicitly) indicate a number of symbols (or slots) that are flexible based on not (explicitly) indicating that a symbol (or slot) is uplink or downlink. That is, an absence of indicating that a symbol (or slot) is uplink or downlink, may indicate that the symbol (or the slot) is a flexible symbol (or a flexible slot). Additionally or alternatively, within a pattern, there may be one or more guard times (e.g., guard symbols or switching gaps) between uplink and downlink symbols (and / or slots). The guard times may, or may not, be indicated by the pattern.Docket No.: 24-1218PCT

[0247] The TDD configuration may be for a (e.g . , specific) wireless device in the cell of base station 1840 or common to all wireless devices in the cell of base station 1840. For example, the TDD configuration may be (or indicate) a common TDD configuration of the cell (e.g., to be applied commonly by, e.g., wireless device 1800, wireless device 1820, and all other wireless devices in the cell). As another example, the TDD configuration may be a UE dedicated (e.g., UE-specific) TDD configuration (e.g., to be applied by a particular wireless device, such as by wireless device 1800 and not by wireless device 1820 in response to wireless device 1800 receiving one or more RRC messages 1802 indicating a UE dedicated TDD configuration and wireless device 1820 not receiving the (same) UE dedicated TDD configuration).

[0248] Although FIG. 18 illustrates one or more RRC messages 1802 indicating the TDD configuration for the cell of base station 1840, the present disclosure is not limited to this example. For example, wireless device 1800 and wireless device 1820 may (e.g., autonomously) determine (e.g., assume) a TDD configuration for a cell in the absence of an (explicit) TDD configuration in one or more RRC messages 1802. For example, wireless device 1800 and wireless device 1820 may determine (e.g., based on the absence of a TDD configuration) that all slots within a cell of base station 1840 are (considered to be) flexible slots comprising flexible symbols in which uplink transmissions or downlink receptions may be (e.g., scheduled to) occur. A determination of all flexible symbols (or slots) may continue until additional signaling (e.g., RRC, MAC CE, or DCI) is received by wireless device 1800 and wireless device 1820. The same principle may be applied to flexible symbols in general (e.g., that additional signaling may be used to indicate that a flexible symbol is, e.g., an uplink symbol).

[0249] Additionally or alternatively, one or more RRC messages 1802 may indicate one or more slot formats (e.g., slot format combinations) that may be indicated by one or more messages, such as a DCI. A DCI may indicate one of the slot formats configured by one or more RRC messages 1802 (and / or preconfigured slot formats). For example, a field of the DCI may indicate an index, and the index may be associated with (e.g., correspond to) a slot format in the one or more slot formats configured by one or more RRC messages 1802. The slot format, indicated by the DCI, may indicate a number of downlink symbols, a number of uplink symbols, and / or a number of flexible symbols in the slot. The wireless device may identify the DCI (e.g., the DCI format of the DCI) based on an RNTI value of the DCI (e.g., a slot format indicator RNTI (sfi-RNTI)).

[0250] In SBFD, one or more uplink subbands and one or more downlink subbands are configured in (or within) a symbol (e.g., the same symbol). By being configured in a symbol, the one or more uplink subbands and the one or more downlink subbands overlap in the time duration of the symbol (i.e., overlap in time). The one or more uplink subbands and the one or more downlink subbands do not overlap in frequency in (the time duration of) the symbol. For example, an uplink subband may compriseDocket No.: 24-1218PCT one or more uplink frequency resources (e.g., contiguous uplink frequency resources), such as resource blocks (RBs) (e.g., or physical resource blocks (PRBs)). A downlink subband may comprise one or more downlink frequency resources (e.g., contiguous downlink reference resources), such as RBs (e.g., or PRBs). The RBs for the one or more uplink subbands and the RBs for the one or more downlink subbands are not the same within a particular symbol.

[0251] In the present disclosure, a symbol configured with one or more uplink subbands (e.g., at least one uplink subband) and one or more downlink subbands (e.g., at least one downlink subband) may be referred to as a SBFD symbol. As an example, an SBFD symbols may be configured with one uplink subband and two downlink subbands. A symbol configured with only uplink frequency resources (e.g., only uplink RBs, such as an uplink symbol) or only downlink frequency resources (e.g., only downlink RBs, such as a downlink symbol) may be referred to as a non-SBFD symbol. In addition, a flexible symbol may be referred to as a non-SBFD symbol.

[0252] Generally, a slot may be configured with both SBFD symbols and non-SBFD symbols, only SBFD symbols, or only non-SBFD symbols. For ease of discussion, an SBFD slot may refer to a slot in which all occasions for a transmission, or a reception, are in SBFD symbols. A non-SBFD slot may refer to a slot in which all occasions for a transmission, or reception, are in non-SBFD symbols. Although an SBFD slot may refer to the case where all occasions are SBFD symbols, this does not preclude other symbols within the SBFD slot from being non-SBFD symbols. The other symbols (e.g., non-SBFD symbols) in an SBFD slot may not be used, or configured with, occasions for the transmission or reception. Similarly, although a non-SBFD slot may refer to a slot in which all occasions are non-SBFD symbols, this does not preclude other symbols, within the non-SBFD slot, from being SBFD symbols. The other symbols (e.g., SBFD symbols) in a non-SBFD slot may not be used, or configured with, occasions for the transmission or reception.

[0253] As an example, FIG. 18 illustrates that wireless device 1800 and wireless device 1820 (both) transmit uplink transmission 1804 in a non-SBFD symbol (e.g., a non-SBFD symbol within a slot comprising a non-SBFD symbol or a non-SBFD slot). The non-SBFD symbol may be an uplink symbol or a flexible symbol (e.g., a flexible symbol scheduled with uplink transmission 1804). In this example, the non-SBFD symbol is an uplink symbol, which is configured with uplink RBs (and no downlink subbands or downlink RBs). From the perspective of base station 1840, the link direction is the same for (both) wireless device 1800 and wireless device 1820 during the non-SBFD symbol. It should be noted that other factors may be used to prevent interference during the non-SBFD symbols (e.g., different spatial parameters (e.g., uplink transmission filters or uplink beams) and / or different coding sequences being applied).Docket No.: 24-1218PCT

[0254] On the other hand, FIG. 18 illustrates that wireless device 1820 transmits an uplink transmission 1806 in an SBFD symbol (e.g., a SBFD symbol within a slot comprising an SBFD symbol or an SBFD slot). During the same symbol (i.e., the SBFD symbol) (or same slot (i.e., the SBFD slot)), wireless device 1800 receives a downlink transmission 1808 in the SBFD symbol (or the SBFD slot). In this example, the SBFD symbol is configured with an uplink subband via which uplink transmission 1804 is transmitted. In addition, the SBFD symbol is configured with one or more downlink subbands via which downlink transmission 1808 is transmitted. From the perspective of base station 1840, the link direction is different (within the same symbol) for wireless device 1800 (e.g., for which the link direction is uplink) and wireless device 1820 (e.g., for which the link direction is downlink) during the SBFD symbol (or SBFD slot).

[0255] One or more RRC messages 1802 may indicate one or more parameters of an SBFD operation in the cell of base station 1840 (e.g., in one or more SIBs of the cell and / or one or more RRC Reconfiguration messages). For example, the one or more parameters may indicate one or more periods (durations) of SBFD within the pattern indicated by the TDD configuration. The one or more periods may be referred to as one or more SBFD periods. The one or more parameters, indicated by one or more RRC messages 1802, may comprise a starting slot index, a starting symbol index, an ending slot index, and / or an ending symbol index. The starting slot index may represent a slot at the start of a period for SBFD (e.g., within a period indicated by the periodicity of the TDD configuration, such as a starting slot or an initial slot of the period for SBFD). The starting symbol index may indicate a symbol within the slot (e.g., indicated by the starting slot index) where the period for SBFD (symbols) starts (e.g., an earliest symbol or an initial symbol of the period for SBFD). The ending slot index may represent a slot at the end of the period for SBFD (e.g., within the period indicated by the periodicity of the TDD configuration, such as an ending slot or a last slot of the period for SBFD). The ending symbol index may indicate a symbol within the slot where the period for SBFD (symbols) ends (e.g., a last symbol or an ending symbol of the period for SBFD).

[0256] The one or more parameters of the SBFD operation may indicate (e.g., override) an indication of (e.g., the link direction of) a symbol type in the TDD configuration of the cell of base station 1840. For example, the one or more parameters of the SBFD operation may override downlink symbols (e.g., or downlink slots) to be SBFD symbols (or SBFD slots) (e.g., to comprise uplink subbands). Additionally or alternatively, the one or more parameters of the SBFD operation may override flexible symbols (e.g., or flexible slots) to be SBFD symbols (or SBFD slots) (e.g., to comprise downlink subbands and uplink subbands.

[0257] One or more RRC messages 1802 may indicate one or more parameters for indicating the frequency locations of the one or more uplink subbands and / or one or more downlink subbands forDocket No.: 24-1218PCTSBFD operation. For example, the one or more parameters may indicate a starting frequency resource (e.g., starting RB) of an uplink subband (e.g., comprising continuous RBs). The one or more parameters may indicate a bandwidth of the uplink subband. Downlink subbands may be (implicitly) indicated by the remaining frequency resources that are not configured within the uplink subband (e.g., there may be two downlink subbands, such as one lower frequency downlink subband and one higher frequency uplink subband with the uplink subband in between the lower frequency downlink subband and the higher frequency uplink subband). Additionally or alternatively, the one or more parameters may (explicitly) indicate the downlink subbands (e.g., by comprising a starting frequency resource and / or a bandwidth for the downlink subbands).

[0258] When uplink transmissions or downlink receptions (i.e. , uplink receptions and downlink transmissions, respectively, from the perspective of the base station) are performed across SBFD symbols and non-SBFD symbols (e.g., in multiple or different slots, where each slot comprises all SBFD symbols, and / or all non-SBFD symbols, for the occasions of the transmission or reception), a wireless device may need to apply different parameters (e.g., power control, spatial relation, MIMO configuration) for SBFD symbols and non-SBFD symbols. Depending on the capability of the wireless device, the wireless device may be able to apply (e.g., switch between) the different parameters for the transmissions across SBFD symbols and non-SBFD symbols (e.g., in different slots).

[0259] Examples of the uplink transmissions performed across SBFD symbols and non-SBFD symbols (e.g., in different slots or multiple slots) comprise repetitions of an uplink transmission (e.g., repetitions of a PUSCH transmission, repetitions of a PUCCH transmission); transmissions based on an uplink configured grant (e.g., uplink configuration grant of PUSCH transmissions); transmissions of a TB over multiple slots (TBoMS) (e.g., TB processing over multiple slots); periodic (or semi-persistent) transmissions of SRS, CSI-RS, and / or PUCCH; and multiple PUSCH transmissions (Multi-PUSH) scheduled by a (single) DCI.

[0260] Examples of the downlink receptions performed across SBFD symbols and non-SBFD symbols (e.g., in different slots or multiple) comprise repetitions of a downlink reception (e.g., repetitions of a PDSCH reception); transmissions based on a semi-persistent scheduling (SPS) configuration (e.g., SPS of PDSCH receptions); PDCCH receptions; and multiple PDSCH receptions (Multi-PDSCH) scheduled by a (single) DCI.

[0261] There may be two configurations used for uplink transmissions or downlink receptions performed across SBFD symbols and non-SBFD symbols (e.g., in different slots). In a first configuration, the transmissions or receptions are not performed across both SBFD symbols and non-SBFD symbols. For example, the transmissions or receptions may be restricted to SBFD symbols (e.g., restricted to SBFD symbols only) or non-SBFD symbols (e.g., restricted to non-SBFD symbols only). The symbolDocket No.: 24-1218PCT type used in the first configuration may be referred to as an allowed symbol type and the allowed symbol type for the first configuration may be SBFD symbols or non-SBFD symbols (and not both SBFD symbols and non-SBFD symbols). In a second configuration, the transmissions or receptions are (e.g performed) in (both) SBFD symbols and non-SBFD symbols (e.g., in different slots). The second configuration may be used depending on a capability (e.g., a UE capability) of the wireless device. In the present disclosure, the first configuration may be referred to as configuration 1 and the second configuration may be referred to as configuration 2.

[0262] Wireless device 1800 and / or wireless device 1820 may be configured with (e.g., keep or maintain) different sets of transmission parameters (e.g., different uplink power control parameters, different spatial relations, different MIMO configurations) for SBFD symbols and non-SBFD symbols. Different sets of transmission parameters may be used, e.g., due to the uplink interference being higher in the SBFD symbols than non-SBFD symbols. Additionally or alternatively, base station 1840 may use a single panel (or an uplink antenna element) for uplink reception in SBFD symbols while using two panels (or two uplink antenna elements) for non-SBFD symbols. The lower number of uplink antenna elements at base station 1840 during the SBFD symbols (or SBFD slots) may result in a lower uplink channel (e.g., PUSCH or PUCCH) decoding performance as compared to the non-SBFD symbols (e.g., such as uplink symbols or uplink slots).

[0263] In addition, some wireless devices may not be able to determine phase continuity between SBFD symbols and non-SBFD symbols (and / or detect the phase continuity, assume that there is phase continuity, compensate for a change in phase continuity, or adjust for a change in the phase between SBFD symbols and non-SBFD symbols). Configuration 1 may avoid this issue based on restricting transmissions, and / or receptions, to SBFD symbols only (e.g., all SBFD symbols) or non-SBFD symbols only (e.g., all SBFD symbols). However, this may cause increased latency and / or degrade performance due to the transmissions or receptions in the other symbol type (e.g., invalid symbol type or opposite symbol type) not being transmitted (e.g., skipped, dropped, canceled, or postponed). Furthermore, while configuration 1 may simplify the network procedures (e.g. scheduling), configuration 2 may allow full use of the advantages of SBFD operation, such as increased uplink capacity by utilizing both SBFD symbols and non-SBFD symbols for uplink transmissions.

[0264] As wireless devices (e.g., wireless device 1800 and / or wireless device 1820) may apply, maintain, and / or be configured with different sets of transmission parameters for SBFD symbols and non-SBFD symbols, capability signaling may be used to report whether, e.g., a particular wireless device supports configuration 2.Docket No.: 24-1218PCT

[0265] FIG. 18 illustrates an example of capability signaling for configuration 1 and configuration 2. In this example, wireless device 1800 supports both configuration 1 and configuration 2, and wireless device 1820 supports configuration 1 and does not support configuration 2.

[0266] As illustrated in FIG. 18, base station 1840 transmits one or more capability inquiry messages 1810 to wireless device 1800 and wireless device 1820. One or more capability inquiry messages 1810 may explicitly request wireless device 1800 and wireless device 1820 to indicate whether configuration 2 is supported (e.g., and / or configuration 1). Additionally or alternatively, one or more capability inquiry messages 1810 may request wireless device 1800 and wireless device 1820 to indicate capabilities (e.g., without explicitly requesting capability of configuration 1 and / or configuration 2).

[0267] Wireless device 1800 transmits a capability message 1812 to base station 1840. Capability message 1812 may be transmitted in response to receiving one or more capability inquiry messages 1810. Capability message 1812 indicates that wireless device 1800 supports configuration 2. For example, capability message 1812 may comprise a parameter that indicates that wireless device 1800 supports configuration 2. As another example, the parameter may indicate that wireless device 1800 is capable of performing transmissions, or receptions, in (both) SBFD symbols and non-SBFD symbols (e.g., across multiple slots or in different slots).

[0268] On the other hand, wireless device 1820 transmits a capability message 1814 to base station 1840. Capability message 1814 may be transmitted in response to receiving one or more capability inquiry messages 1810. Capability message 1814 indicates that wireless device 1820 does not support configuration 2. For example, capability message 1812 may comprise a parameter that indicates that wireless device 1820 does not support configuration 2. Additionally or alternatively, the parameter may indicate that wireless device 1820 supports configuration 1 only. As another example, the parameter may indicate that wireless device 1800 is not capable of performing transmissions, or receptions, in SBFD symbols and non-SBFD symbols (e.g., across multiple slots or in different slots). As yet another example, the parameter may indicate that wireless device 1800 is only capable of performing transmissions, or receptions, in SBFD symbols or non-SBFD symbols (e.g., across multiple slots or in different slots) (and not both SBFD symbols and non-SBFD symbols).

[0269] Base station 1840 may transmit one or more RRC messages 1816, such as one or more RRC reconfiguration messages, to wireless device 1800 and wireless device 1820. One or more RRC messages 1816 may be transmitted in response to capability message 1812 and capability message 1814. Alternatively, one or more RRC messages 1816 may be transmitted not in response to capability message 1812 and capability message 1814 (e.g., independent from capability message 1812 and capability message 1814).Docket No.: 24-1218PCT

[0270] One or more RRC messages 1816 may comprise one or more configuration parameters indicating configuration 1 and / or configuration 2. For example, the one or more configuration parameters, indicated by one or more RRC messages 1816, may comprise a parameter indicating a configuration among the first configuration and the second configuration. The parameter may indicate the configuration is to be used for uplink transmissions and / or downlink receptions. For example, the parameter may indicate that the configuration is to be used for an uplink transmission (or a downlink reception) across a plurality of slots (e.g., comprising both SBFD symbols and non-SBFD symbols).

[0271] Additionally or alternatively, one or more RRC messages 1816 may not explicitly indicate which configuration to be used. For example, based on transmitting capability message 1814, wireless device 1820 may determine (e.g., assume) that uplink transmissions or downlink receptions in SBFD symbols and non-SBFD symbols (e.g., across a plurality of slots or in different slots) are based on configuration 1. That is, based on transmitting capability message 1812 indicating that configuration 2 is not supported, wireless device 1820 may determine that uplink transmissions or downlink receptions in SBFD symbols and non-SBFD symbols (across a plurality of slots or in different slots) are (to be) performed based on configuration 1 .

[0272] As another example of an implicit indication of the configuration, based on transmitting capability message 1812, wireless device 1800 may determine (e.g., assume) that uplink transmissions or downlink receptions in SBFD symbols and non-SBFD symbols (e.g., across a plurality of slots or in different slots) are based on configuration 2. That is, based on transmitting capability message 1814 indicating that configuration 2 is supported, wireless device 1800 may determine that uplink transmissions or downlink receptions in SBFD symbols and non-SBFD symbols (e.g., across a plurality of slots or in different slots) are (to be) performed based on configuration 2.

[0273] Examples of configuration 1 and configuration 2 for an uplink transmission across SBFD symbols and non-SBFD symbols are provided below with reference to FIG. 18. In these examples, uplink transmission occurs across a plurality of slots, where each slot comprises SBFD symbols or non- SBFD symbols (e.g., occasions within each slot are in SBFD symbols or non-SBFD symbols for the uplink transmission). It should be noted that these examples equally apply to downlink receptions.

[0274] As an example of configuration 2, FIG. 18 illustrates that wireless device 1800 receives a DCI 1822. DC1 1822 schedules uplink transmissions 1824. Uplink transmissions 1824 are scheduled across SBFD symbols and non-SBFD symbols (e.g., in a plurality of slots or in different slots). In configuration 2, transmissions and / or receptions are performed across both SBFD symbols and non-SBFD symbols. As illustrated, uplink transmissions 1824 are transmitted in (both) non-SBFD symbols and SBFD symbols.Docket No.: 24-1218PCT

[0275] As an example of configuration 1 , FIG. 18 illustrates that wireless device 1820 receives a DCI 1826. DC1 1826 schedules uplink transmissions 1828. Uplink transmissions 1828 are scheduled across SBFD symbols and non-SBFD symbols (e.g., in a plurality of slots or in different slots). In configuration 1, transmissions and / or receptions are not performed across both SBFD symbols and non-SBFD symbols (e.g., are restricted to SBFD symbols only or are restricted to non-SBFD symbols only).

[0276] Based on configuration 1 , wireless device 1820 transmits uplink transmissions 1828 in the non- SBFD symbols and does not transmit uplink transmissions 1828 in the SBFD symbols. In this example, non-SBFD symbols are the allowed symbol type (e.g., valid symbol type) for configuration 1 . FIG. 18 illustrates that wireless device 1820 does not transmit uplink transmissions 1828 with dotted arrows for the SBFD symbols. As an example of not transmitting, wireless device 1820 may skip, drop, cancel, or postpone transmissions of uplink transmissions 1828 in the SBFD symbols (i.e. , the not allowed symbol type, the invalid symbol type, and / or the non-transmitted symbols).

[0277] Wireless device 1800 may determine the allowed symbol type (i.e., which symbols to transmit in and / or which symbols not to transmit it) based on the symbol type of the initial occasion of uplink transmissions 1828. As illustrated in FIG. 18, the initial occasion of uplink transmissions 1828 is in a non-SBFD symbol. Based on the initial occasion of uplink transmissions 1828 being in a non-SBFD symbol, wireless device 1820 transmits uplink transmissions 1828 in the non-SBFD symbols and does not transmit (e.g., skips, drops, cancels, or postpones) uplink transmissions 1828 in the SBFD symbols. That is, the allowed symbol type is non-SBFD symbols based on the initial transmission of uplink transmissions 1828 being in a non-SBFD symbol.

[0278] The symbol type of the initial occasion may be either the symbol type of the initial transmission as scheduled to be transmitted in an occasion (e.g., a transmission occasion or reception occasion) or the symbol type of the occasion that the initial transmission is actually transmitted. For example, one or more conflicts may occur between a scheduled transmission of uplink transmissions 1828 and another transmission or reception that is scheduled for the (same) non-SBFD symbol. Wireless device 1820 may not actually transmit the initial transmission in the non-SBFD symbol in FIG. 18. In this case, the scheduled transmission may be used to determine the symbol type for configuration 1 . Alternatively, the actual transmission may be used to determine the symbol type for configuration 1 . For example, after determining that uplink transmissions 1828 are to be transmitted, the symbol type for the (actual) transmission may be used for the symbol type in configuration 1 . In the examples that follow, the scheduled transmission is used for determining the symbol type of configuration 1 . However, the use of the actual transmission to determine the symbol type for configuration 1 is within the scope of the present disclosure. In addition, the initial occasion may be referred to as an earliest or starting occasion. Additionally or alternatively, the occasion in, e.g., the initial occasion, may be referred to as an initialDocket No.: 24-1218PCT transmission occasion (e.g., for the uplink from the wireless device perspective) or an initial reception occasion (e.g., for the downlink from the wireless device perspective).

[0279] As discussed above, different parameters may be applied to uplink transmissions in SBFD symbols and non-SBFD symbols. As an example, one or more RRC messages 1816 may indicate (separate) SRS resource sets for SBFD symbols and non-SBFD symbols. For example, one or more RRC messages 1816 may indicate an SRS resource set (e.g., an SRS resource set for non-SBFD symbols or a first SRS resource set) and an SRS resource set for SBFD symbols (e.g., a second SRS resource set). Each SRS resource set may be configured with different uplink power control parameters, spatial domain parameters, and / or frequency hopping parameters.

[0280] For example, wireless device 1800 may apply one or more parameters associated with the SRS resource set for non-SBFD symbols to uplink transmissions 1824 in non-SBFD symbols. Wireless device 1800 may apply one or more parameters associated with the SRS resource set for SBFD symbols to uplink transmissions 1824 in SBFD symbols. On the other hand, wireless device 1820 may apply one or more parameters associated with the SRS resource set for non-SBFD symbols to uplink transmissions 1828 in non-SBFD symbols. Wireless device 1800 may not apply the one or more parameters associated with the SRS resource set for SBFD symbols (e.g., based on uplink transmissions 1828 being in non-SBFD symbols due to the initial occasion of uplink transmissions 1828).

[0281] In existing technologies, a DCI may schedule uplink transmissions or downlink receptions. After a wireless device (successfully) decodes the DCI, the wireless device may transmit or receive starting from the time indicated by the DCI. For example, the wireless device may monitor, e.g., the PDSCH starting from a time indicated by the DCI scheduling (e.g., triggering) a downlink reception.

[0282] So long as the DCI schedules the downlink transmission with a sufficient duration of time after the wireless device (successfully) decodes the DCI, the wireless device may apply the corresponding parameters to monitor (and / or detect) the downlink transmission. For example, the wireless device may apply a QCL relation (e.g., receiving beam) to receive a downlink transmission (as discussed above in FIGs. 17A and 17B). If the downlink transmission is scheduled before the wireless device (successfully) decodes the DCI and / or is able to apply the corresponding parameters, the wireless device may apply another set of parameters to monitor (and / or detect) the downlink transmissions, such as a default QCL relation (and / or a QCL relation based on a reference signal, such as an SSB, identified during a random access procedure, such as most recent or last random access procedure).

[0283] Several problems may arise when these features are applied to SBFD operation. For example, based on configuration 1 (e.g., as illustrated in FIG. 18), a wireless device does not receive downlink receptions (and / or does not transmit uplink transmissions) in (both) SBFD symbols and non-SBFDDocket No.: 24-1218PCT symbols (e.g., downlink symbols or flexible symbols in the case of downlink receptions). That is, based on configuration 1 , downlink receptions are restricted to SBFD symbols only or are restricted to non- SBFD symbols only (not both SBFD symbols and non-SBFD symbols).

[0284] The symbol type (i.e., non-SBFD symbols or SBFD symbols) for configuration 1 is determined based on an initial occasion of, e.g., the downlink receptions scheduled by a DCI (or uplink transmissions in the uplink). This is illustrated from the uplink perspective in FIG. 18 and this example also applies to the downlink. However, if the DCI that schedules the downlink reception is not (yet) decoded (successfully), the wireless device cannot determine the initial occasion of the downlink transmissions (e.g., since the starting symbol of the downlink reception has not been decoded yet). Additionally or alternatively, the wireless device may not be able to apply the corresponding QCL relation associated with the symbol type before (e.g., the starting symbol of) the downlink reception.

[0285] According to embodiments of the present disclosure, a wireless device receives a DCI scheduling one or more downlink receptions. The wireless device monitors for the one or more downlink receptions in a symbol type, among SBFD symbols and non-SBFD symbols, based on an offset between the DCI and the downlink receptions being less than a threshold.

[0286] By using a symbol type for monitoring downlink receptions based on the offset being less than a threshold, this may increase reliability in the communications (e.g., based on aligning the operations between the wireless device and base station for which symbols are to be monitored in advance) and provide greater flexibility to the network (e.g., based on being able to schedule transmissions before DCI is successfully decoded) without increasing latency (e.g., based on scheduling the downlink transmission late enough so that the wireless device has finished decoding the scheduling information indicated by the DCI).

[0287] According to embodiments of the present disclosure, a wireless device transmits a capability message indicating whether the wireless device supports buffering across SBFD and non-SBFD symbols. The wireless device receives a DCI scheduling one or more downlink receptions, wherein an offset between a reception of the DCI and the one or more downlink receptions is less than a threshold. The wireless device monitors for the downlink receptions in at least one symbol type, among SBFD symbols and non-SBFD symbols, based on the capability message.

[0288] By using a capability message to determine the symbol type of the monitoring for downlink receptions scheduled within a threshold, this may increase reliability in the communications (e.g., based on aligning the operations between the wireless device and base station for which symbols are to be monitored in advance) and provide greater flexibility to the network (e.g., based on the capability of a particular wireless device to determine which symbol types are monitored) without increasing latencyDocket No.: 24-1218PCT(e.g. , based on scheduling the downlink transmission late enough so that the wireless device has finished decoding the scheduling information indicated by the DCI).

[0289] These and other additional effects may be provided by aspects of the embodiments of the present disclosure.

[0290] FIG. 19 illustrates an example of a wireless device 1900 communicating with a base station 1920 in SBFD operation. The communicating in SBFD operation may be performed based on FIG. 18.

[0291] As illustrated at tO, wireless device 1900 receives (e.g., from base station 1920 and / or on a cell) one or more RRC messages 1902 One or more RRC messages 1902 may be implemented based on one or more RRC messages 1802 and / or one or more RRC messages 1816. One or more RRC messages 1902 may indicate one or more parameters for SBFD operation in a cell of base station 1920. For example, the one or more parameters for SBFD operation may indicate one or more periods (or durations) of SBFD. The one or more periods of SBFD may be within a pattern indicated by a TDD configuration (e.g., implemented based on one or more RRC messages 1802 as discussed above, such as a common TDD configuration of the cell and / or a UE-dedicated TDD configuration). The one or more periods may be referred to as one or more SBFD periods.

[0292] Additionally or alternatively, the one or more parameters, indicated by one or more RRC messages 1902, may comprise a starting slot index, a starting symbol index, an ending slot index, and / or an ending symbol index. The starting slot index may represent a slot at the start of a period for SBFD (e.g., within a period indicated by the periodicity of the TDD configuration, such as a starting slot or an initial slot of the period for SBFD). The starting symbol index may indicate a symbol within the slot (e.g., indicated by the starting slot index) where the period for SBFD (symbols) starts (e.g., an earliest symbol or an initial symbol of the period for SBFD). The ending slot index may represent a slot at the end of the period for SBFD (e.g., within the period indicated by the periodicity of the TDD configuration, such as an ending slot or a last slot of the period for SBFD). The ending symbol index may indicate a symbol within the slot where the period for SBFD (symbols) ends (e.g., a last symbol or an ending symbol of the period for SBFD).

[0293] One or more RRC messages 1902 may indicate one or more parameters of a DC1 1904 (e.g., a DCI format of DC1 1904, such as DCI format 1_0, 1_1 , and / or 1_2) for scheduling one or more downlink receptions in one or more SBFD symbols and one or more non-SBFD symbols (e.g., one downlink reception in an SBFD symbol or a non-SBFD symbol, or a plurality of downlink receptions across a plurality of slots, and / or in different slots, comprising SBFD symbols and non-SBFD symbols). Examples of a downlink reception comprise a PDSCH reception and aperiodic CSI-RS. Examples of a plurality of downlink receptions performed across SBFD symbols and non-SBFD symbols (e.g., in different slots or multiple slots) comprise any of the following: PDSCH receptions; repetitions of aDocket No.: 24-1218PCTPDSCH reception; receptions based on a SPS configuration; multiple PDSCH receptions (Multi-PDSCH) scheduled by a single DCI; and / or aperiodic CSI-RSs. In the present disclosure, scheduling downlink receptions comprises triggering downlink receptions, indicating activation of downlink receptions (e.g., based on an SPS configuration), and scheduling retransmissions of downlink receptions.

[0294] As an example, one or more RRC messages 1902 may indicate a list of time domain resource allocations. DC1 1904 (or a DCI format of DC1 1904) may comprise a field indicating a time domain resource allocation in the list of time domain resource allocations. One or more of the time domain resource allocations may comprise a number of repetitions. The number of repetitions may indicate a number of slots to perform the downlink reception. The number of repetitions may be referred to as an aggregation factor.

[0295] As another example, one or more RRC messages 1902 may indicate a resource configuration (e.g., a downlink resource configuration). The resource configuration may comprise a parameter indicating a number of slots for the downlink receptions. The parameter may be an aggregation factor or a repetition number. The resource configuration may be a PDSCH configuration. DCI 1904 may indicate the resource configuration and a downlink reception in a plurality of slots based on the resource configuration indicating the number of slots for the downlink reception.

[0296] DC1 1904 may be used, in SBFD operation, to receive one or more downlink receptions in one or more SBFD symbols and one or more non-SBFD symbols. An example of the scheduling can be seen, for one or more uplink transmissions, in DC1 1822 and / or DC1 1826. The example also applies to scheduling one or more downlink transmissions. DC1 1904 may be implemented based on DC1 1708, DC1 1718, and / or DC1 1722.

[0297] One or more RRC messages 1902 may indicate one or more TCI states. One or more RRC messages 1902 may indicate the one or more TCI states in the same manner as one or more RRC messages 1702 in FIG. 17A and / or one or more RRC messages 1714 in FIG. 17B. As an example based on FIG. 17B, the one or more TCI states may be unified TCI states. The one or more TCI states may comprise one or more TCI states for SBFD symbols. One or more RRC messages 1902 may indicate the one or more TCI states in the same, or in a separate, list from the list of joint-DL TCI states and / or the list of uplink TCI states (e.g., discussed in connection with one or more RRC messages 1714).

[0298] As discussed above in connection with FIG. 17B, under the unified TCI state framework, there may be two signaling mechanisms to indicate which TCI states is to be applied among the TCI states configured by one or more RRC messages 1902 (and / or one or more RRC messages 1714). The TCI state to be applied may be referred to as an indicated TCI state.Docket No.: 24-1218PCT

[0299] In the first mechanism, a MAC CE may be used (e.g., without additional signaling from, e.g., a DCI) to indicate which TCI state to apply. For example, wireless device 1900 may receive, after tO, a MAC CE. The MAC CE may indicate a mapping of a single codepoint (e.g., to one or multiple TCI states). Based on the MAC CE indicating the mapping of (only) a single codepoint, wireless device 1900 applies the one or more T Cl states to uplink transmissions and / or downlink receptions. The MAC CE may be implemented based on MAC CE 1716.

[0300] In the second mechanism, a MAC CE may be used to indicate activation of a plurality of TCI states (e.g., mapped to a plurality of TCI codepoints) and additional signaling, such as a DCI, is used to indicate which of the (activated) TCI states (by the MAC CE) is to be applied to uplink transmissions and / or downlink receptions. The TCI states to be applied may be referred to as an indicated TCI state (or indicated TCI states). The DCI may comprise a field that indicates a TCI codepoint value (e.g., 00). The field may be referred to as a TCI field or a TCI state field. One or more RRC messages 1902 may comprise a parameter indicating that the TCI field is present in the DCI (e.g., based on the parameter being present or set to enabled). The one or more TCI states associated with (e.g., mapped to) the TCI codepoint value indicated by the field of the DCI are applied to uplink transmissions and / or downlink receptions (e.g., the one or more TCI states are the indicated TCI state or indicated TCI states). The MAC CE may be implemented based on MAC CE 1716 and the DCI may be implemented based on DCI 1718.

[0301] Returning to FIG. 19, wireless device 1900 receives a DC1 1904 at t1 . DCI 1904 schedules one or more downlink receptions 1906 in one or more SBFD symbols and / or one or more non-SBFD symbols.

[0302] One or more downlink receptions 1906 may be a downlink reception (e.g., one downlink reception) in an SBFD symbol or a non-SBFD symbol. Alternatively, one or more downlink receptions 1906 may be a plurality of downlink receptions in one or more SBFD symbols and one or more non- SBFD symbols (e.g., across a plurality of slots or in different slots). In the example as illustrated in FIG. 19, one or more downlink receptions 1906 comprises a plurality of downlink receptions that are scheduled across a plurality of slots. The plurality of slots comprise SBFD symbols and non-SBFD symbols. Additionally or alternatively, DC1 1904 may schedule one or more downlink receptions 1906 in one or more SBFD symbols and one or more non-SBFD symbols (e.g., across a plurality of slots and / or in different slots).

[0303] DC1 1904 may comprise a field (e.g., the TCI field as discussed above) indicating a first TCI state and a second TCI state to apply to one or more downlink receptions 1906. For example, the field may indicate a TCI codepoint that is mapped (e.g., by a MAC CE, such as MAC CE 1716) to (both) a first TCI state for non-SBFD symbols and a second TCI state for SBFD symbols.Docket No.: 24-1218PCT

[0304] DC1 1904 schedules one or more downlink receptions 1906 starting at t2 in FIG. 19. One or more downlink receptions 1906 may be indicated with configuration 1 or configuration 2 (e.g., based on one or more RRC messages 1902 and / or a capability message based on based on capability message 1812 and / or capability message 1814).

[0305] As illustrated in FIG. 19, the starting symbol (or slot) of one or more downlink receptions 1908 is an offset (e.g., a number of symbols or a duration in time (e.g., in ms)) from reception of DC1 1904 at t1 . The offset is less than a threshold. Examples of the threshold comprise a time duration for QCL (e.g., timeDurationForQCL) and a beam switching time (e.g., beamSwitchTiming)). The threshold may be indicated by one or more RRC messages 1902 and / or based on a capability of wireless device 1900 (e.g., as reported in a capability message transmitted to base station 1920 before tO based on capability message 1812 and / or capability message 1814).

[0306] As discussed above, a problem may arise when the offset between reception of DC1 1904 (at t1) and (e.g., a starting symbol of) downlink receptions 1906 (at t2) is less than the threshold. In an example, this problem may occur when one or more downlink receptions 1906 are indicated with configuration 1 or configuration 2. The following example is based on one or more downlink receptions 1906 being indicated with configuration 1 in which one or more downlink receptions 1906 are not received in both non-SBFD symbols and SBFD symbols (e.g , one or more downlink receptions 1906 are restricted to non-SBFD symbols only or are restricted to SBFD symbols only).

[0307] Based on one or more downlink receptions 1906 being indicated with configuration 1 , wireless device 1900 receives one or more downlink receptions 1906 in the symbol type of the initial occasion of one or more downlink receptions 1906. For example, as illustrated in FIG. 19, the initial occasion of one or more downlink receptions 1906 is a non-SBFD symbol (or non-SBFD slot). Based on the initial occasion being in a non-SBFD symbol (or non-SBFD slot), wireless device 1900 is to receive one or more downlink receptions 1906 in the non-SBFD symbols and not receive downlink receptions 1906 in the SBFD symbols.

[0308] However, when the offset between reception of DC1 1904 (at t1) and (e.g., a starting symbol of) one or more downlink receptions 1906 (at t2) is less than the threshold, wireless device 1900 may not (e.g., yet) determine whether the initial occasion of one or more downlink receptions 1906 is in a non- SBFD symbol or a SBFD symbol. For example, wireless device 1900 may (e.g., successfully) decode DC1 1904 at t3, which is illustrated after the initial occasion of one or more downlink receptions 1906. Although FIG. 19 illustrates that t3 is after the last symbol (or last slot) of one or more downlink receptions 1906, the present disclosure is not limited to this example. For example, t3 may occur at any time after t2 (e.g., after t2 and before the last symbol of one or more downlink receptions 1908).Docket No.: 24-1218PCT

[0309] As another example of a problem that may occur, DCI 1904 may indicate the first TCI state for non-SBFD symbols and the second TCI state for SBFD symbols. Based on the offset being less than the threshold, wireless device 1900 may not be able to determine the initial occasion of one or more downlink receptions 1906 and / or apply, e.g., the first TCI state to the initial occasion of one or more downlink receptions 1906.

[0310] As illustrated at t2 in FIG. 19, wireless device 1900 receives one or more downlink receptions 1906 in non-SBFD symbols. For example, wireless device 1900 may start receiving one or more downlink receptions 1906 in non-SBFD symbols based on the offset being less than the threshold. The non-SBFD symbols may be a default symbol type. The default symbol type may be used for receiving based on the offset between reception of DC1 1904 (at t1) and (e.g., a starting symbol of) one or more downlink receptions 1908 being less than a threshold.

[0311] As another example, wireless device 1900 may receive one or more downlink receptions 1906 in non-SBFD symbols using a default TCI state. For example, wireless device 1900 may start receiving one or more downlink receptions 1906 in non-SBFD symbols using the default TCI state based on the offset being less than the threshold. The default TCI state may be the TCI state for the non-SBFD symbols (i.e., the first TCI state in this example). The default TCI state may be used for receiving based on the offset between reception of DCI 1904 (at t1) and (e.g., a starting symbol of) one or more downlink receptions 1908 being less than a threshold.

[0312] Additionally or alternatively, the default TCI state may be determined based on the default symbol type. For example, based on the default symbol type being non-SBFD symbols, wireless device 1900 may apply the first TCI state to one or more downlink receptions 1906.

[0313] In addition to, or in the alternative to, the receiving by wireless device 1900 of one or more downlink receptions 1906 in non-SBFD symbols, wireless device 1900 may perform other actions, such as monitoring for one or more downlink receptions 1906 in non-SBFD symbols and / or buffering for one or more downlink receptions 1906 in non-SBFD symbols. The monitoring and / or buffering may be performed based on the offset being less than the threshold. The monitoring and / or buffering may be performed based on the default symbol type and / or default TCI state.

[0314] Base station 1920 may determine (e.g., before t1) that the offset between reception of DCI 1904 by wireless device 1900 (at t1) and (e.g., a starting symbol of) one or more downlink receptions 1906, by wireless device 1900, is (e.g., going to be) less than the threshold. Based on the determining, base station 1920 may schedule one or more downlink receptions 1906 to be in one or more non-SBFD symbols. Additionally or alternatively, base station 1920 may configure (e.g., ensure or guarantee) that one or more downlink receptions 1906 are in one or more non-SBFD symbols.Docket No.: 24-1218PCT

[0315] For example, base station 1920 may schedule one or more downlink receptions 1906 to be in one or more non-SBFD symbols based on the offset being less than the threshold and the default symbol type being non-SBFD symbols (and / or the default TCI state being associated with non-SBFD symbols).

[0316] As another example, in the case that one or more downlink receptions 1906 are a plurality of downlink receptions indicated with configuration 1 , base station 1920 may schedule the initial occasion of the plurality of downlink receptions to be in a non-SBFD symbol based on the default symbol type being non-SBFD symbols (and / or the default TCI state being associated with non-SBFD symbols).

[0317] As yet another example, base station 1920 may determine (e.g., before t1) that the offset between reception of DC1 1904 by wireless device 1900 (at t1) and (e.g., a starting symbol of) one or more downlink receptions 1906, by wireless device 1900, is equal to, or greater than the threshold. For example, based on one or more downlink receptions 1906 being scheduled in SBFD symbols, base station 1920 may schedule one or more downlink receptions 1906 such that the offset is greater than the threshold. Additionally or alternatively, base station 1920 may set a value of DC1 1904 indicating a time domain resource allocation (e.g., a time domain resource allocation field). The value may be set such that the offset is greater than the threshold based on the one or more downlink receptions 1906 being in SBFD symbols (and the default symbol type being non-SBFD symbols and / or the default TCI state being associated with SBFD symbols).

[0318] As another example, the default symbol type may be SBFD symbols and / or the default TCI state may be associated with SBFD symbols. Based on the default symbol type being SBFD symbols, wireless device 1900 may (e.g., start to) receive one or more downlink receptions 1906 in one or more SBFD symbols at t2. Additionally or alternatively, based on the default TCI state being associated with SBFD symbols, wireless device 1900 may (e.g., start to) receive one or more downlink receptions 1906 in one or more SBFD symbols at t2.

[0319] Similarly, base station 1920 may schedule one or more downlink receptions 1906 in one or more SBFD symbols based on the default symbol type being SBFD symbols and / or the default TCI state being associated with SBFD symbols. As another example, in case one or more downlink receptions 1906 are a plurality of downlink receptions indicated with configuration 1 , base station 1920 may schedule the initial occasion of one or more downlink receptions 1908 to be in an SBFD symbol based on the default symbol type being SBFD symbols and / or the default TCI state being associated with SBFD symbols. As yet another example, based on one or more downlink receptions 1906 being scheduled in non-SBFD symbols, base station 1920 may schedule one or more downlink receptions 1906 such that the offset is greater than the threshold.Docket No.: 24-1218PCT

[0320] By using a default symbol type and / or a default TCI state when the offset is less than a threshold, reliability may be improved (e.g., based on alignment in the operations between wireless device 1900 and base station 1920) without increasing latency (e.g., by delaying the scheduling one or more downlink receptions 1908 such that the offset is equal to, or greater than, the threshold).

[0321] In the present disclosure, default symbol type may be replaced with symbol type (without the term default) and / or with a particular symbol type corresponding to the example, such as SBFD symbol, non-SBFD symbol, downlink symbol, and / or flexible symbol.

[0322] In the present disclosure, default TCI state may be replaced with a TCI state associated with a symbol type (e.g., without the term default) and / or with a particular symbol type corresponding to the example, such as a TCI state for SBFD symbols (e.g., the first TCI state), a TCI state for non-SBFD symbols (e.g., the second TCI state), a TCI state for downlink (e.g., for downlink symbols and / or flexible symbols).

[0323] As explained above, DC1 1904 may indicate the first TCI state for non-SBFD symbols and the second TCI state for SBFD symbols. Based on the offset being less than the threshold, wireless device 1900 applies the first TCI state to one or more downlink receptions 1906. For example, wireless device 1900 may apply the first TCI state based on the symbol type associated with the first TCI state being non-SBFD symbols and the offset being less than the threshold. Additionally or alternatively, wireless device 1900 may apply the first TCI state based on the default symbol type being non-SBFD symbols and the first TCI state being associated with non-SBFD symbols.

[0324] Additionally or alternatively, wireless device 1900 may apply the first TCI state based on a rule. For example, wireless device 1900 may apply the first TCI state based on the first TCI state being associated with a lowest (or highest) TCI codepoint value, the first TCI state occurring first in an ordered set of TCI states (e.g., indicated by a MAC CE, such as MAC CE 1704 and / or MAC CE 1716, and / or indicated by one or more RRC messages, such as one or more RRC messages 1702, one or more RRC messages 1714, one or more RRC messages 1802, one or more RRC messages 1816, and / or one or more RRC messages 1902). As another example, wireless device 1900 may apply the first TCI state based on one or more RRC messages (e.g., one or more RRC messages 1702, one or more RRC messages 1714, one or more RRC messages 1802, one or more RRC messages 1816, and / or one or more RRC messages 1902) comprising a parameter (e.g., Apply-indiciatedTCIState-SBFD) with a value indicating the first TCI state.

[0325] As another example, the first TCI state and the second TCI state may be associated with the same reference signal. For example, the first TCI state may indicate a first reference signal (e.g., SSB or CSI-RS) and the second TCI state may indicate a second reference signal (e.g., SSB or CSI-RS). The first reference signal may be the same as the second reference signal. Additionally or alternatively, theDocket No.: 24-1218PCT first reference signal may be a QCL source of the second reference signal. The QCL type of the first reference signal and the second reference signal may be the same (e.g., spatial parameters or QCL Type-D). The first TCI state and the second TCI state may be associated with different transmission parameters (e.g., different power control parameter sets). Wireless device 1900 may determine a default symbol type based on the first TCI state and the second TCI state.

[0326] Similar to the discussion above, the default symbol type may be SBFD symbols. In this case, wireless device 1900 applies the second TCI state to one or more downlink receptions 1906. Wireless device 1900 may apply the second TCI state based on the symbol type associated with the second TCI state being SBFD symbols and the offset being less than the threshold. Additionally or alternatively, wireless device 1900 may apply the second TCI state based on the default symbol type being SBFD symbols and the second TCI state being associated with SBFD symbols.

[0327] Additionally or alternatively, wireless device 1900 may apply the second TCI state based on a rule. For example, wireless device 1900 may apply the second TCI state based on the second TCI state being associated with a lowest (or highest) TCI codepoint value, the second TCI state occurring first in an ordered set of TCI states (e.g., indicated by a MAC CE, such as MAC CE 1704 and / or MAC CE 1716, and / or indicated by one or more RRC messages, such as one or more RRC messages 1702, one or more RRC messages 1714, one or more RRC messages 1802, one or more RRC messages 1816, and / or one or more RRC messages 1902). As another example, wireless device 1900 may apply the second TCI state based on one or more RRC messages (e.g., one or more RRC messages 1702, one or more RRC messages 1714, one or more RRC messages 1802, one or more RRC messages 1816, and / or one or more RRC messages 1902) comprising a parameter (e.g., Apply-indiciatedTCIState- SBFD) with a value indicating the second TCI state.

[0328] As an example of applying a TCI state to receive one or more downlink receptions 1906, wireless device 1900 may use a spatial filter parameter determined based on a reference signal indicated by the TCI state to receive one or more downlink receptions 1906. The spatial filter parameter may be, e.g., a downlink spatial reception filter, a spatial domain reception filter, a spatial domain receiving filter, a beam, or a beam parameter. The spatial filter parameter may be the same (or substantially the same) as a spatial filter used to receive the reference signal indicated by the TCI state.

[0329] Additionally or alternatively, by applying the TCI state to receive one or more downlink receptions 1906, wireless device 1900 may receive one or more downlink receptions 1906 based on one or more downlink receptions 1906 being quasi co-located (QCL'ed) with a reference signal indicated by the TCI state. As an example of being quasi co-located, demodulation reference signal (DM-RS) ports of one or more downlink receptions 1906 may be quasi co-located with the reference signal indicated by the TCI state. As another example, wireless device 1900 may use QCL informationDocket No.: 24-1218PCT indicated by the TCI state and / or a QCL assumption indicated by the TCI state. In the case that one or more downlink receptions 1906 are one or more aperiodic CSI-RSs, CSI-RS ports of one or more downlink receptions 1906 (e.g., CSI-RS ports of a CSI-RS resource) may be quasi co-located with the reference signal indicated by the TCI state.

[0330] In addition to, or in the alternative to, wireless device 1900 receiving at t2 in the non-SBFD symbols, wireless device 1900 does not receive one or more downlink receptions 1906 in the SBFD symbols as illustrated in FIG. 19. Additionally or alternatively, wireless device 1900 may not monitor for one or more downlink receptions 1906, not buffer for one or more downlink receptions 1906, not decode for one or more downlink receptions 1906, skip one or more downlink receptions 1906, drop one or more downlink receptions 1906, and / or ignore one or more downlink receptions 1908 in SBFD symbols based on the offset being less than the threshold. The not receiving uplink transmissions 1918 in SBFD symbols is illustrated in FIG. 19 with dotted arrows pointing from the uplink subband in the SBFD symbols.

[0331] As explained above, one or more downlink receptions 1906 may be indicated with configuration 1 or configuration 2. Configuration 1 and configuration 2 are described above in connection with FIG. 18. Based on one or more downlink receptions 1906 being indicated with configuration 1 , wireless device 1900 is to receive one or more downlink receptions 1906 in non-SBFD symbols as the initial occasion of one or more downlink receptions 1906 is in a non-SBFD symbol in FIG. 19.

[0332] As an example of indicating configuration 1 for uplink transmissions, one or more RRC messages 1902 may indicate configuration 1 for one or more downlink receptions 1906. For example, one or more RRC messages 1902 may comprise a parameter that indicates configuration 1 is to be used for one or more downlink receptions 1906. The parameter may indicate a configuration, for the one or more downlink receptions 1906, among configuration 1 and configuration 2. A first value of the parameter (e.g., 0, false, config. 1) may indicate that the first configuration is used for one or more downlink receptions 1906. A second value of the parameter (e.g., 1 , true, config. 2) may indicate that the second configuration is used for one or more downlink receptions 1906. Additionally or alternatively, the absence of a parameter, in one or more RRC messages 1902, that indicates configuration 2 for one or more downlink receptions 1906 may (implicitly) indicate that configuration 1 is to be used for one or more downlink receptions 1906 (e.g., configuration 1 may be used as a default configuration).

[0333] Additionally or alternatively, as another example of indicating configuration 1 for one or more downlink receptions 1906, wireless device 1900 may transmit a capability message (e.g., to base station 1920 and / or on the cell) indicating that wireless device 1900 does not support configuration 2. ForDocket No.: 24-1218PCT example, the capability message may indicate that wireless device 1900 supports configuration 1 only. The capability message may be implemented, for example, based on capability message 1814.

[0334] Wireless device 1900 may determine that configuration 1 is indicated for one or more downlink receptions 1906 in SBFD symbols and non-SBFD symbols (e.g., in a plurality of slots or in different slots) based on transmitting the capability message. That is, based on the capability message indicating that wireless device 1900 does not support configuration 2 (e.g., supports configuration 1 only), wireless device 1900 may determine that configuration 1 is indicated for one or more downlink receptions 1906. This may be determined in the case that one or more RRC messages 1902 comprises a parameter indicating configuration 1 for one or more downlink receptions 1906 or in the case that one or more RRC messages 1902 does not comprise any parameter indicating configuration 1 for one or more downlink receptions 1906.

[0335] As an example of indicating configuration 2 for one or more downlink receptions 19068, one or more RRC messages 1902 may indicate configuration 2 for one or more downlink receptions 1906. As explained above, one or more RRC messages 1902 may comprise a parameter that indicates configuration 2 is to be used for one or more downlink receptions 1906. The parameter may indicate a configuration, for one or more downlink receptions 1906, among configuration 1 and configuration 2. A first value of the parameter (e.g., 0, false, config. 1) may indicate that the first configuration is used for one or more downlink receptions 1906. A second value of the parameter (e.g., 1 , true, config. 2) may indicate that the second configuration is used for one or more downlink receptions 1906. Additionally or alternatively, the absence of a parameter, in one or more RRC messages 1902, that indicates configuration 1 is used for one or more downlink receptions 1906 may (implicitly) indicate that configuration 2 is to be used for one or more downlink receptions 1906 (e.g., configuration 2 may be used as a default configuration). Additionally or alternatively, the absence of a parameter, in one or more RRC messages 1902, that indicates configuration 1 may (implicitly) indicate that configuration 2 is to be used for one or more downlink receptions 1906.

[0336] Additionally or alternatively, as another example of indicating configuration 2 for one or more downlink receptions 1906, wireless device 1900 may transmit a capability message (e.g., to base station 1920 and / or on the cell) indicating that wireless device 1900 supports configuration 2. For example, the capability message may indicate that wireless device 1900 supports configuration 1 and 2. The capability message may be implemented, for example, based on capability message 1812.

[0337] Wireless device 1900 may determine that configuration 2 is indicated for one or more downlink receptions 1906 in SBFD symbols and non-SBFD symbols (e.g., in a plurality of slots or in different slots) based on transmitting the capability message. That is, based on the capability message indicating that wireless device 1900 supports configuration 2 (e.g., in addition to configuration 1), wireless deviceDocket No.: 24-1218PCT1900 may determine that configuration 2 is indicated for one or more downlink receptions 1906. This may be determined in the case that one or more RRC messages 1902 comprises a parameter indicating configuration 2 for one or more downlink receptions 1906 or in the case that one or more RRC messages 1902 does not comprise any parameter indicating configuration 2 for one or more downlink receptions 1906.

[0338] In the example illustrated in FIG. 19, one or more downlink receptions 1906 are indicated with configuration 1 . In the following example, one or more downlink receptions 1906 are indicated with configuration 1 or configuration 2 and a capability message is used to determine whether wireless device 1900 is to receive both SBFD symbols and non-SBFD symbols.

[0339] As mentioned above, wireless device 1900 may transmit (e.g., to base station 1920) a capability message before tO in FIG. 19. The capability message may be implemented based on capability message 1812 and / or capability message 1814. In addition to, or in alternative to, indicating whether wireless device 1900 supports configuration 2, the capability message may indicate a buffering capability that the wireless device 1900 supports in SBFD operation.

[0340] For example, the capability message may indicate whether wireless device 1900 supports buffering across SBFD symbols and non-SBFD symbols (e.g., in different symbol types). A parameter in the capability message may indicate that wireless device 1900 supports buffering across SBFD symbols and non-SBFD symbols. A value of the parameter and / or the presence of the parameter in the capability message may indicate that wireless device 1900 supports buffering across SBFD symbols and non- SBFD symbols.

[0341] Additionally or alternatively, the parameter may indicate that wireless device 1900 does not support buffering across SBFD symbols and non-SBFD symbols. A value of the parameter and / or the presence of the parameter in the capability message may indicate that wireless device 1900 supports buffering across SBFD symbols and non-SBFD symbols.

[0342] Additionally or alternatively, the capability message may indicate whether wireless device 1900 supports a default QCL assumption with two TCI states in both SBFD symbols and non-SBFD symbols (e.g., in different symbol types). For example, the capability message may indicate whether wireless device 1900 supports default QCL assumption with a TCI state in SBFD symbols. For example, the capability message may indicate whether wireless device 1900 supports a default QCL assumption per symbol type. The default QCL assumption may be a default TCI state. In the present disclosure, default TCI state may be replaced with default QCL assumption.

[0343] The capability message may indicate the support by wireless device 1900 (e.g., the supported capabilities) per band, per band combination (BC), per feature set (e.g., per band per bandDocket No.: 24-1218PCT combination), per carrier (e.g., per feature set per component carrier (FSPC) and / or provide the capability per carrier per band per band combination).

[0344] Returning to FIG. 19, at t2, wireless device 1900 may receive in the default symbol type and / or using the default TCI state based on the capability message (e.g., transmitted before tO). For example, based on the capability message indicating that the wireless device 1900 does not support buffering across SBFD symbols and non-SBFD symbols and / or supports the default QCL assumption, wireless device 1900 may (e.g., start to) receive for one or more downlink receptions 1906 in non-SBFD symbols (e.g., as a default symbol type and / or based on the default TCI state) at t2. Additionally or alternatively, wireless device 1900 may not receive (e.g., ignore, not monitor for, and / or not buffer) one or more downlink receptions 1906 in the SBFD symbols based on the capability message.

[0345] As another example, based on the capability message indicating that wireless device 1900 does not support buffering across SBFD symbols and non-SBFD symbols and / or supports the default QCL assumption, wireless device 1900 may (e.g., start to) receive one or more downlink receptions 1906 in SBFD symbols as the default symbol type. Additionally or alternatively, wireless device 1900 may not receive (e.g., ignore, not monitor for, and / or not buffer) one or more downlink receptions 1908 in the non-SBFD symbols based on the capability message.

[0346] The examples above may be applied to configuration 1 and configuration 2 For example, in the case that the capability message indicates that wireless device 1900 supports configuration 2 (e.g., such as capability message 1812), wireless device 1900 may be capable of receiving one or more downlink receptions 1906 in SBFD symbols and non-SBFD symbols.

[0347] In an example, wireless device 1900 may only support configuration 2 when the offset between the reception of DC1 1904 at t1 and (e.g., a starting symbol of) one or more downlink receptions 1908 is equal to, or greater than, the threshold. For example, the capability message may indicate that wireless device 1900 does not support buffering across SBFD symbols and non-SBFD symbols and / or supports the default QCL assumption. Based on the capability message, wireless device 1900 may (e.g., start to receive) one or more downlink receptions 1906 (indicated with configuration 2) in non-SBFD symbols. Additionally or alternatively, wireless device 1900 may not receive (e.g., ignore, not monitor for, and / or not buffer) one or more downlink receptions 1906 in SBFD symbols.

[0348] On the other hand, the capability message (e.g., transmitted before tO) may (also) indicate that wireless device 1900 does not support buffering across SBFD symbols and non-SBFD symbols when the offset is less than the threshold. Based on the capability message indicating that the wireless device 1900 does not support buffering across SBFD symbols and non-SBFD symbols when the offset is less than the threshold, wireless device 1900 may (e.g., start to) receive one or more downlink receptions 1906 in non-SBFD symbols (e.g., as a default symbol type) at t2. Additionally or alternatively, wirelessDocket No.: 24-1218PCT device 1900 may not receive (e.g., ignore, not monitor for, and / or not buffer) one or more downlink receptions 1906 in the SBFD symbols based on the capability message. In this example, non-SBFD symbols may be used as a default symbol type and / or associated with the default TCI state. The default symbol type, and / or the default TCI state, may alternatively be SBFD symbols.

[0349] FIG. 20 illustrates a process 2000 according to an embodiment of the present disclosure. The aspects of process 2000 in FIG. 20 may be implemented by the wireless device discussed above in connection with FIGs. 17, 18, and / or 19.

[0350] As illustrated in FIG. 20, process 2000 comprises a step 2002 of receiving a DCI scheduling one or more downlink receptions. The one or more downlink receptions may be a downlink reception in an SBFD symbol or a non-SBFD symbol. Additionally or alternatively, the one or more downlink receptions may be a plurality of downlink receptions in SBFD symbols and non-SBFD symbols.

[0351] Process 2000 further comprises a step 2004 of monitoring for the one or more downlink receptions in a symbol type among SBFD symbols and non-SBFD symbols. The symbol type may be a default symbol type. Additionally or alternatively, the monitoring may be monitoring based on a default TCI state associated with the symbol type.

[0352] The monitoring in step 2004 may be based on an offset between the DCI and the one or more downlink receptions being less than a threshold. Additionally or alternatively, the offset between the DCI and the one or more downlink receptions may be less than threshold in step 2002. As an example, the offset may be between a reception of the DCI and (e.g., a starting symbol of) the one or more downlink receptions.

[0353] Additional aspects, with examples, of process 2000, step 2002 and step 2004 are discussed below. Each of the additional aspects, and examples, below may be considered an embodiment. Each aspect of the embodiments may be combined with, or substituted for, the aspects of the embodiment of process 2000 illustrated in FIG. 20, such as step 2002 and step 2004. Furthermore, each of the additional aspects and examples below may be combined with each other.

[0354] In an example, the one or more downlink receptions are indicated with a first configuration. In this example, the monitoring in step 2004 may be further be based on the one or more downlink receptions being indicated with the first configuration and the offset being less than the threshold.

[0355] In an example, the threshold is a time duration for quasi co-location or a beam switching time threshold. Process 2000 may further comprise receiving one or more RRC messages indicating a value of the threshold.

[0356] In an example, one or more RRC messages indicate a first TCI state and the second TCI state. The one or more RRC messages may indicate that the second TCI state is for SBFD symbols. The one or more RRC messages may indicate that the first TCI state is for non-SBFD symbols.Docket No.: 24-1218PCT

[0357] In an example, the one or more RRC messages indicate to apply the first TCI state and the second TCI state to downlink receptions. The one or more RRC messages may indicate to apply the first TCI state and / or the second TCI state to uplink transmissions and downlink transmissions.

[0358] In an example, process 2000 further comprises a step of receiving one or more commands indicating to apply the first TCI state and the second TCI state to downlink receptions. The one or more commands may indicate to apply the first TCI state and / or the second TCI state to uplink transmissions and downlink transmissions. The one or more commands may comprise a MAC CE and / or a first DCI. The first DCI may be the (same) DCI scheduling the one or more downlink receptions. In another example, the first DCI is not the (same) DCI that is scheduling the one or more downlink receptions. In this example, the first DCI may be received before the DCI scheduling the one or more downlink receptions.

[0359] The one or more commands may comprise a MAC CE. The MAC CE may indicate that the first TCI state and the second TCI state are associated with a TCI codepoint. The MAC CE may indicate that the first TCI state and the second TCI state are mapped to the TCI codepoint.

[0360] In an example, the one or more commands comprises a MAC CE and a first DCI. The first DCI may be the (same) DCI scheduling the downlink receptions. The MAC CE may indicate activation of a plurality of TCI states. The MAC CE may indicate activation of the first TCI state and the second TCI state. The MAC CE may indicate that the first TCI state and the second TCI state are associated with a TCI codepoint. The MAC CE may indicate that the first TCI state and the second TCI state are mapped to the TCI codepoint. In this example, the first DCI may indicate to apply the TCI state and the second TCI state. For example, the first DCI may comprise a TCI field indicating the TCI codepoint associated with the first TCI state and the second TCI state.

[0361] In an example, process 2000 further comprises applying a TCI state, among the first TCI state and the second TCI state, associated with the same symbol type as the symbol type. The applying the TCI state associated with the symbol type may be based on the offset being less than the threshold.

[0362] In an example, a DCI format of the DCI scheduling the one or more downlink receptions is DCI format 1_0, 1_1 , and / or 1_2.

[0363] In an example, process 2000 further comprises a step of not receiving the one or more downlink receptions in symbols not having the symbol type. Not receiving comprises at least one of: not monitoring, in the symbols not having the symbol type, for the one or more downlink receptions; not decoding, in the symbols not having the symbol type, for the one or more downlink receptions; ignoring, in the symbols not having the symbol type, the one or more downlink receptions; and / or not buffering in the symbols not having the default symbol type. Any of these steps may be performed for a downlink channel, such as the PDSCH. In this example, the step of monitoring in step 2004 may be replaced withDocket No.: 24-1218PCT the step of not receiving. Alternatively, process 2000 may comprise both step 2004 and the step of not receiving the one or more downlink receptions.

[0364] In an example, the one or more downlink receptions are at least one of: a PDSCH reception; a CSI-RS; PDSCH receptions; repetitions of a PDSCH reception; receptions based on a semi-persistent scheduling (SPS) configuration; multiple PDSCH receptions (Multi-PDSCH) scheduled by a single DCI; or aperiodic CSI-RSs.

[0365] In an example, the one or more downlink receptions are scheduled in non-SBFD symbols and SBFD symbols. The one or more downlink receptions may be scheduled in a plurality of slots or in different slots.

[0366] In an example, the one or more downlink receptions are scheduled in non-SBFD slots and SBFD slots. The non-SBFD slots may comprise non-SBFD symbols only. For example, each occasion of the one or more downlink receptions, in a first slot, may be in a non-SBFD symbol of the first slot. The first slot may be referred to as a non-SBFD slot. Each occasion of the one or more downlink receptions, in a second slot, may be in an SBFD symbol of the second slot. The second slot may be referred to as a SBFD slot.

[0367] In an example, the SBFD symbols are symbols configured with an uplink subband and a downlink subband. For example, the SBFD symbols may be configured with uplink frequency resources (e.g., uplink RBs or uplink PRBs) and downlink frequency resources (e.g., downlink RBs or downlink PRBs). The SBFD symbols may be configured with one uplink subband and two downlink subbands. A lowest RB of the first downlink subband may be a lower frequency than a lowest RB of the uplink subband. The lowest RB of the uplink subband may be a lower frequency than a lowest RB of the second downlink subband.

[0368] In an example, the non-SBFD symbols are downlink symbols. The downlink symbols are not configured with any uplink frequency resources (e.g., uplink subbands or uplink RBs).

[0369] In an example, the non-SBFD symbols are flexible symbols. The flexible symbols are not configured with any uplink frequency resources (e g., uplink subbands or uplink RBs). The flexible symbols are scheduled with the downlink receptions.

[0370] In an example, the one or more downlink receptions are not performed across both non-SBFD symbols and SBFD symbols in the first configuration. For example, the downlink receptions may be restricted to non-SBFD symbols only, or SBFD symbols only, in the first configuration.

[0371] In an example, based on the first configuration, the one or more downlink receptions are received in SBFD symbols based on an initial occasion of the one or more downlink receptions being in an SBFD symbol. The one or more downlink receptions in the non-SBFD symbols are not received. ForDocket No.: 24-1218PCT example, the one or more downlink receptions in the non-SBFD symbols may be not monitored, not decoded, not buffered, or ignored.

[0372] In another example, based on the first configuration, the one or more downlink receptions are received in non-SBFD symbols based on an initial occasion of the one or more downlink receptions being in a non-SBFD symbol. The non-SBFD symbol may be a downlink symbol or a flexible symbol. The one or more downlink receptions in the SBFD symbols are not received. For example, the one or more downlink receptions in the SBFD symbols may be not monitored, not decoded, not buffered, or ignored.

[0373] In an example, the one or more downlink receptions are performed across both non-SBFD symbols and SBFD symbols in a second configuration.

[0374] In an example, process 2000 further comprises transmitting a capability message indicating that the wireless device does not support the second configuration. For example, the capability message may indicate that the wireless device supports the first configuration only. The capability message may indicate that the wireless device does not support receiving one or more downlink receptions in SBFD symbols and non-SBFD symbols. The capability message may indicate that the wireless device does not support receiving one or more downlink receptions in SBFD symbols and non-SBFD symbols in different slots or a plurality of slots. The monitoring, in step 2004, may be based on the capability message indicating that the wireless device does not support the second configuration.

[0375] In another example, process 2000 further comprises transmitting a capability message indicating that the wireless device supports the second configuration. For example, the capability message may indicate that the wireless device supports the first configuration and the second configuration. The capability message may indicate that the wireless device support receiving downlink receptions in SBFD symbols and non-SBFD symbols. The capability message may indicate that the wireless device supports receiving the one or more downlink receptions in SBFD symbols and non- SBFD symbols in different slots or a plurality of slots. The monitoring, in step 2104, may be based on the capability message indicating that the wireless device supports the second configuration.

[0376] Additionally or alternatively, the capability message may indicate whether the wireless device supports buffering across SBFD symbols and non-SBFD symbols. For example, the capability message may indicate that the wireless device does not support buffering across SBFD symbols and non-SBFD symbols. The monitoring in step 2004 may be based on the capability message indicating that the wireless device does not support buffering across SBFD symbols and non-SBFD symbols and the offset being less than the threshold. In this example, the one or more downlink receptions may be indicated with configuration 1 or configuration 2.Docket No.: 24-1218PCT

[0377] In another example, the capability message may indicate that the wireless device supports buffering across SBFD symbols and non-SBFD symbols. The monitoring in step 2004 may be monitoring both SBFD symbols and non-SBFD symbols based on the capability message indicating that the wireless device does supports buffering across SBFD symbols and non-SBFD symbols and the offset being less than the threshold. In this example, the one or more downlink receptions may be indicated with configuration 1 or configuration 2.

[0378] Additionally or alternatively, the capability message may indicate whether the wireless device supports a default TCI state (or a default QCL assumption) for SBFD symbols and non-SBFD symbols. For example, the capability message may indicate that the wireless device supports the default TCI state for SBFD symbols and non-SBFD symbols. The monitoring in step 2004 may be based on the capability message indicating that the wireless device supports the default TCI state and the offset being less than the threshold. In this example, the one or more downlink receptions may be indicated with configuration 1 or configuration 2.

[0379] An apparatus (e.g., a wireless device) comprising one or more processors and memory storing instructions that, when executed by the one or more processors, may cause the apparatus to perform process 2000 and / or any one or more of the above examples.

[0380] A (non-transitory) computer-readable medium may comprise instructions that, when executed by one or more processors of an apparatus (e.g., a wireless device), may cause the apparatus to perform process 2000 and / or any one or more of the above examples.

[0381] A system may comprise a base station and an apparatus (e.g., a wireless device) that may comprise one or more processors and memory storing instructions that, when executed by the one or more processors, may cause the apparatus to perform process 2000 and / or any one or more of the above examples.

[0382] It should be understood that any of the aspects, and / or examples, of process 2100 in FIG. 20 from the perspective of the wireless device (e.g., receiver perspective) may be implemented from the perspective of a base station (e.g., transmitter perspective). The relationship between the wireless device and the base station may be considered as transmitter-receiver reciprocal relationship.

[0383] FIG. 21 illustrates a process 2100 according to an embodiment of the present disclosure. The aspects of process 2100 in FIG. 21 may be implemented by a base station above in connection with FIGs. 17, 18, 19, and / or 20.

[0384] As illustrated in FIG. 21 , process 2100 comprises a step 2102 of transmitting, to a wireless device, a DCI scheduling one or more downlink receptions. The one or more downlink receptions may be a downlink reception in an SBFD symbol or a non-SBFD symbol. Additionally or alternatively, the oneDocket No.: 24-1218PCT or more downlink receptions may be a plurality of downlink receptions in SBFD symbols and non-SBFD symbols.

[0385] Process 2100 further comprises a step 2104 of transmitting, to the wireless device, the one or more downlink receptions in a symbol type among SBFD symbols and non-SBFD symbols. The symbol type may be a default symbol type. Additionally or alternatively, the monitoring may be monitoring based on a default TCI state associated with the symbol type.

[0386] The transmitting in step 2104 may be based on an offset between the DCI and the one or more downlink receptions being less than a threshold. Additionally or alternatively, the offset between the DCI and the one or more downlink receptions may be less than threshold in step 2102. As an example, the offset may be between a reception of the DCI and (e.g., a starting symbol of) the one or more downlink receptions.

[0387] It should be noted downlink receptions are downlink transmissions from the perspective of the base station. In any of the examples in the present disclosure, downlink receptions of the wireless device may be replaced with downlink transmissions (e.g., by the base station) to the wireless device.

[0388] Additional aspects, with examples, of process 2100, step 2102 and step 2104 are discussed below. Each of the additional aspects, and examples, below may be considered an embodiment. Each aspect of the embodiments may be combined with, or substituted for, the aspects of the embodiment of process 2100 illustrated in FIG. 21 , such as step 2102 and step 2104. Furthermore, each of the additional aspects and examples below may be combined with each other.

[0389] In an example, the one or more downlink receptions are indicated with a first configuration 1 . In this example, the transmtiting in step 2104 may be further be based on the downlink receptions being indicated with the first configuration and the offset being less than the threshold.

[0390] In an example, the threshold is a time duration for quasi co-location or a beam switching time threshold. Process 2100 may further comprise transmitting, to the wireless device, one or more RRC messages indicating a value of the threshold.

[0391] In an example, one or more RRC messages indicate a first TCI state and the second TCI state. The one or more RRC messages may indicate that the second TCI state is for SBFD symbols. The one or more RRC messages may indicate that the first TCI state is for non-SBFD symbols.

[0392] In an example, the one or more RRC messages indicate to apply the first TCI state and the second TCI state to downlink receptions. The one or more RRC messages may indicate to apply the first TCI state and / or the second TCI state to uplink transmissions and downlink transmissions.

[0393] In an example, process 2100 further comprises a step of transmitting, to the wireless device, one or more commands indicating to apply the first TCI state and the second TCI state to downlink receptions. The one or more commands may indicate to apply the first TCI state and / or the second TCIDocket No.: 24-1218PCT state to uplink transmissions and downlink transmissions. The one or more commands may comprise a MAC CE and / or a first DCI. The first DCI may be the (same) DCI scheduling the downlink receptions. In another example, the first DCI is not the (same) DCI that is scheduling the one or more downlink receptions. In this example, the first DCI may be transmitted, to the wireless device, before the DCI scheduling the one or more downlink receptions.

[0394] The one or more commands may comprise a MAC CE. The MAC CE may indicate that the first TCI state and the second TCI state are associated with a TCI codepoint. The MAC CE may indicate that the first TCI state and the second TCI state are mapped to the TCI codepoint.

[0395] In an example, the one or more commands comprises a MAC CE and a first DCI. The first DCI may be the (same) DCI scheduling the downlink receptions. The MAC CE may indicate activation of a plurality of TCI states. The MAC CE may indicate activation of the first TCI state and the second TCI state. The MAC CE may indicate that the first TCI state and the second TCI state are associated with a TCI codepoint. The MAC CE may indicate that the first TCI state and the second TCI state are mapped to the TCI codepoint. In this example, the first DCI may indicate to apply the TCI state and the second TCI state. For example, the first DCI may comprise a TCI field indicating the TCI codepoint associated with the first TCI state and the second TCI state.

[0396] In an example, process 2100 further comprises applying a TCI state, among the first TCI state and the second TCI state, associated with the same symbol type as the symbol type. The applying the TCI state associated with the symbol type may be based on the offset being less than the threshold.

[0397] In an example, a DCI format of the DCI scheduling the one or more downlink receptions is DCI format 1_0, 1_1 , and / or 1_2.

[0398] In an example, process 2100 further comprises a step of not transmitting the one or more downlink receptions in symbols not having the symbol type. Not transmitting may comprise at least one of: skipping, in the symbols not having the symbol type, for the one or more downlink receptions; canceling, in the symbols not having the symbol type, for the one or more downlink receptions; and / or postponing, in the symbols not having the symbol type, the one or more downlink receptions. Any of these steps may be performed for a downlink channel, such as the PDSCH. In this example, the step of transmitting in step 2104 may be replaced with the step of not transmitting. Alternatively, process 2100 may comprise both step 2104 and the step of not transmitting the one or more downlink receptions.

[0399] In an example, the one or more downlink receptions are at least one of: a PDSCH reception; a CSI-RS; PDSCH receptions; repetitions of a PDSCH reception; receptions based on a semi-persistent scheduling (SPS) configuration; multiple PDSCH receptions (Multi-PDSCH) scheduled by a single DCI; or aperiodic CSI-RSs.Docket No.: 24-1218PCT

[0400] In an example, the one or more downlink receptions are scheduled in non-SBFD symbols and SBFD symbols. The one or more downlink receptions may be scheduled in a plurality of slots or in different slots.

[0401] In an example, the one or more downlink receptions are scheduled in non-SBFD slots and SBFD slots. The non-SBFD slots may comprise non-SBFD symbols only. For example, each occasion of the one or more downlink receptions, in a first slot, may be in a non-SBFD symbol of the first slot. The first slot may be referred to as a non-SBFD slot. Each occasion of the one or more downlink receptions, in a second slot, may be in an SBFD symbol of the second slot The second slot may be referred to as a SBFD slot.

[0402] In an example, the SBFD symbols are symbols configured with an uplink subband and a downlink subband. For example, the SBFD symbols may be configured with uplink frequency resources (e.g., uplink RBs or uplink PRBs) and downlink frequency resources (e.g., downlink RBs or downlink PRBs). The SBFD symbols may be configured with one uplink subband and two downlink subbands. A lowest RB of the first downlink subband may be a lower frequency than a lowest RB of the uplink subband. The lowest RB of the uplink subband may be a lower frequency than a lowest RB of the second downlink subband.

[0403] In an example, the non-SBFD symbols are downlink symbols. The downlink symbols are not configured with any uplink frequency resources (e.g., uplink subbands or uplink RBs).

[0404] In an example, the non-SBFD symbols are flexible symbols. The flexible symbols are not configured with any uplink frequency resources (e.g., uplink subbands or uplink RBs). The flexible symbols are scheduled with the downlink receptions.

[0405] In an example, the one or more downlink receptions are not performed across both non-SBFD symbols and SBFD symbols in the first configuration. For example, the downlink receptions may be restricted to non-SBFD symbols only, or SBFD symbols only, in the first configuration.

[0406] In an example, based on the first configuration, the one or more downlink receptions are transmitted in SBFD symbols based on an initial occasion of the one or more downlink receptions being in an SBFD symbol. The one or more downlink receptions in the non-SBFD symbols are not transmitted. For example, the one or more downlink receptions in the non-SBFD symbols may be skipped, canceled, or postponed.

[0407] In another example, based on the first configuration, the one or more downlink receptions are transmitted in non-SBFD symbols based on an initial occasion of the one or more downlink receptions being in a non-SBFD symbol. The non-SBFD symbol may be a downlink symbol or a flexible symbol. The one or more downlink receptions in the SBFD symbols are not transmitted. For example, the one or more downlink receptions in the SBFD symbols may be skipped, canceled, or postponed.Docket No.: 24-1218PCT

[0408] In an example, the one or more downlink receptions are performed across both non-SBFD symbols and SBFD symbols in a second configuration.

[0409] In an example, process 2100 further comprises receiving, from the wireless device, a capability message indicating that the wireless device does not support the second configuration. For example, the capability message may indicate that the wireless device supports the first configuration only. The capability message may indicate that the wireless device does not support receiving one or more downlink receptions in SBFD symbols and non-SBFD symbols. The capability message may indicate that the wireless device does not support receiving one or more downlink receptions in SBFD symbols and non-SBFD symbols in different slots or a plurality of slots. The transmitting, in step 2104, may be based on the capability message indicating that the wireless device does not support the second configuration.

[0410] In another example, process 2100 further comprises receiving, from the wireless device, a capability message indicating that the wireless device supports the second configuration. For example, the capability message may indicate that the wireless device supports the first configuration and the second configuration. The capability message may indicate that the wireless device support receiving downlink receptions in SBFD symbols and non-SBFD symbols. The capability message may indicate that the wireless device supports receiving the one or more downlink receptions in SBFD symbols and non-SBFD symbols in different slots or a plurality of slots. The transmitting, in step 2104, may be based on the capability message indicating that the wireless device supports the second configuration.

[0411] Additionally or alternatively, the capability message may indicate whether the wireless device supports buffering across SBFD symbols and non-SBFD symbols. For example, the capability message may indicate that the wireless device does not support buffering across SBFD symbols and non-SBFD symbols. The transmitting in step 2104 may be based on the capability message indicating that the wireless device does not support buffering across SBFD symbols and non-SBFD symbols and the offset being less than the threshold. In this example, the one or more downlink receptions may be indicated with configuration 1 or configuration 2.

[0412] In another example, the capability message may indicate that the wireless device supports buffering across SBFD symbols and non-SBFD symbols. The transmitting in step 2104 may be transmitting in both SBFD symbols and non-SBFD symbols based on the capability message indicating that the wireless device does support buffering across SBFD symbols and non-SBFD symbols and the offset being less than the threshold. In this example, the one or more downlink receptions may be indicated with configuration 1 or configuration 2.

[0413] Additionally or alternatively, the capability message may indicate whether the wireless device supports a default TCI state (or a default QCL assumption) for SBFD symbols and non-SBFD symbols.Docket No.: 24-1218PCTFor example, the capability message may indicate that the wireless device supports the default TCI state for SBFD symbols and non-SBFD symbols. The transmitting in step 2104 may be based on the capability message indicating that the wireless device supports the default TCI state and the offset being less than the threshold. In this example, the one or more downlink receptions may be indicated with configuration 1 or configuration 2.

[0414] An apparatus (e.g., a base station) comprising one or more processors and memory storing instructions that, when executed by the one or more processors, may cause the apparatus to perform process 2100 and / or any one or more of the above examples.

[0415] A (non-transitory) computer-readable medium may comprise instructions that, when executed by one or more processors of an apparatus (e.g., a base station), may cause the apparatus to perform process 2100 and / or any one or more of the above examples.

[0416] A system may comprise a wireless device and a base station that may comprise one or more processors and memory storing instructions that, when executed by the one or more processors, may cause the apparatus to perform process 2100 and / or any one or more of the above examples.

[0417] Additional working examples, and embodiments, are provided below. The working examples, and embodiments, may be combined with each other and FIGs. 18, 19, 20, 21 , and / or 22. Additionally or alternatively, the aspects of the working examples, and embodiments provided below may be substituted for any of the aspects of FIGs. 18, 19, 20, 21 , and / or 22.

[0418] A wireless device may receive, e.g., from a base station, one or more RRC messages. The one or more RRC messages may comprise one or more configuration parameters. The base station may transmit the one or more RRC messages.

[0419] The one or more configuration parameters may be, for example, for a cell. The one or more configuration parameters may be, for example, for a BWP of the cell.

[0420] In an example, the cell may operate in a second frequency range (FR2). The FR2 may, for example, comprise frequency bands from 24 GHz to 52.6 GHz.

[0421] The one or more RRC messages (or the one or more configuration parameters) may indicate an SBFD operation. The one or more RRC messages (or the one or more configuration parameters) may comprise one or more parameters (e.g., periods (durations) of SBFD within the pattern indicated by the TDD configuration, SBFD symbols, starting slot index, a starting symbol index, an ending slot index, and / or an ending symbol index) of the SBFD operation.

[0422] The one or more configuration parameters may comprise a TCI state list parameter (e.g., dl- OrJointTCI-StateList in PDSCH-Config) indicating a list of TCI states. The list of TCI state may indicate / provide a reference signal, for example, for the quasi co-location for DM-RS of PDSCH in the BWP of the cell. The list of TCI state may indicate / provide a reference signal, for example, for the quasiDocket No.: 24-1218PCT co-location for DM-RS of PDCCH in the BWP of the cell. The list of TCI state may indicate / provide a reference signal, for example, for the quasi co-location for CSI-RS.

[0423] The wireless device may receive a control command (e.g., MAC-CE, DCI) indicating two TCI states. The list of TCI states may comprise the two TCI states.

[0424] In an example, the control command (e.g., DCI) may comprise a TCI field. A TCI codepoint of the TCI field may indicate (or may be mapped to) the two TCI states. A value of the TCI field may indicate (or may be equal to) a TCI codepoint indicating (or mapped to) the two TCI states.

[0425] The two TCI states may comprise a first TCI state and a second TCI state.

[0426] The first TCI state may be associated with non-SBFD symbols (e.g., downlink symbols). The wireless device may apply the first TCI state to downlink receptions (e.g., PDSCH, PDCCH, CSI-RS) in the non-SBFD symbols. The wireless device may apply the first TCI state to downlink receptions (e.g., PDSCH, PDCCH, CSI-RS) occurring / overlapping in / with the non-SBFD symbols.

[0427] The second TCI state may be associated with SBFD symbols. The wireless device may apply the second TCI state to downlink receptions (e.g., PDSCH, PDCCH, CSI-RS) in the SBFD symbols. The wireless device may apply the second TCI state to downlink receptions (e.g., PDSCH, PDCCH, CSI-RS) occurring / overlapping in / with the SBFD symbols.

[0428] The wireless device may receive an activation command (e.g., MAC-CE) used to map sets of TCI states to one or more TCI codepoints of a TCI field in a DCI format. The activation command may indicate activation of the sets of TCI states among / from the list of TCI states. The sets of TCI states may comprise the two TCI states. The one or more TCI codepoints may comprise the TCI codepoint indicating (or mapped to) the two TCI states. Each set of the sets of TCI states may comprise, for example, up to two TCI states for downlink signals / channels and uplink signals / channels. Each set of the sets of TCI states may comprise, for example, up to two TCI states for downlink signals / channels and up to two TCI states for uplink signals / channels. A first set of the sets of TCI states may be mapped to the TCI codepoint. In an example, the first set may comprise the two TCI states. The first TCI state may occur first in the first set. The first TCI state may occur second in the first set.

[0429] The activation command may comprise a field (e.g., Fi ) indicating whether a j-th TCI state is present or not, where j = 1 , 2.

[0430] The activation command may comprise a first field (e.g., Fi ) indicating that a TCI state identifier field indicating / identifying the first TCI state is present. When j = 1 (e.g., Fi ), and the first field is set to one, a TCI state identifier field indicating / identifying j-th TCI state (e.g., the first TCI state) is present. The first TCI state is the 1stTCI state based on j being equal to one.

[0431] The activation command may comprise a second field (e.g., Fi ) indicating that a TCI state identifier field indicating / identifying the second TCI state is present. When j = 2 (e.g., Fi,2), and theDocket No.: 24-1218PCT second field is set to one, a TCI state identifier field indicating / identifying j-th TCI state (e.g., the second TCI state) is present. The second TCI state is the 2ndTCI state based on j being equal to two.

[0432] The wireless device may receive a DCI (e.g., DCI format 1 _0, DCI format 1_1 , DCI format 1 _2, DCI format 1_3, and the like).

[0433] The DCI may, for example, schedule a downlink reception (e.g., PDSCH reception, aperiodic CSI-RS). The downlink reception may be, for example, a scheduled downlink reception.

[0434] The DCI may, for example, trigger a downlink reception (e.g., aperiodic CSI-RS). The downlink reception may be, for example, a triggered downlink reception.

[0435] The DCI may, for example, indicate activation of a downlink reception (e.g., SPS PDSCH reception). The DCI may indicate activation of an SPS configuration. The downlink reception may be, for example, an activated downlink reception.

[0436] In an example, a time offset between reception of the DCI and the downlink reception may be less than a threshold (e.g., timeDurationForQCL, beamSwitchTiming). The time offset between reception of the DCI and the downlink reception may be a time offset between a last / ending / latest symbol of the reception of the DCI and a starting / earliest / first symbol of the downlink reception.

[0437] The wireless device may receive, from the base station, a UE capability enquiry message (e.g., UECapabilityEnquiry, UE capability enquiry). The wireless device may transmit, to the base station, a UE capability information message (e.g., UECapabilitylnformation, UE capability information message), for example, based on receiving the UE capability enquiry message

[0438] The UE capability information message may indicate the threshold (or a value of / for the threshold).

[0439] The wireless device may apply the first TCI state to the downlink reception. The wireless device may receive, using (or based on) the first TCI state, the downlink reception. The wireless device may apply the first TCI state to the downlink reception, for example, based on the time offset between reception of the DCI and the downlink reception being less than the threshold.

[0440] The wireless device may apply the first TCI state to the downlink reception, for example, based on the first TCI state being the 1stTCI state (e.g., j = 1).

[0441] The wireless device may apply the first TCI state to the downlink reception, for example, based on the first TCI state being associated with the non-SBFD symbols.

[0442] The wireless device may apply the first TCI state to the downlink reception, for example, based on the first TCI state being specific to the non-SBFD symbols.

[0443] The wireless device may apply the first TCI state to the downlink reception, for example, based on not reporting capability / support of the second configuration (e.g., configuration 2) to the base station in the UE capability information message.Docket No.: 24-1218PCT

[0444] The wireless device may apply the first TCI state to the downlink reception, for example, based on not reporting capability / support of a default QCL parameter (e.g., defaultQCL-TwoTCI-SBFD, defaultQCL-SBFD, defaultQCL-PerSymbolType) to the base station in the UE capability information message. The UE capability information message may not comprise the default quasi co-location (QCL) parameter.

[0445] The one or more configuration parameters may comprise a parameter (e.g., applylndicatedTCI-State, applylndicatedTCI-State-SBFD, apply SymbolType, applyDuplexType). The parameter may indicate, for example, whether to apply the first TCI state or the second TCI state to downlink receptions. The parameter may indicate, for example, whether to apply the first TCI state or the second TCI state to downlink receptions before the threshold (e.g., timeDurationForQCL, beamSwitchTiming). The parameter may indicate, for example, whether to receive / buffer downlink receptions in non-SBFD symbols or SBFD symbols. The parameter may indicate, for example, whether to receive / buffer downlink receptions in non-SBFD symbols or SBFD symbols before the threshold.

[0446] A first value of the parameter (e.g., 'first', ‘O', 'non-SBFD', 'downlink') may indicate the first TCI state associated with the non-SBFD symbols. For example, the first value of the parameter may indicate to apply the first TCI state to downlink receptions. For example, the first value of the parameter may indicate to apply the first TCI state to downlink receptions before the threshold (e.g., timeDurationForQCL, beamSwitchTiming). For example, the first value of the parameter may indicate to receive / buffer downlink receptions in non-SBFD symbols. For example, the first value of the parameter may indicate to receive / buffer downlink receptions in non-SBFD symbols before the threshold.

[0447] A second value of the parameter (e.g., ‘second’, ‘T, ‘SBFD’) may indicate the second TCI state associated with the SBFD symbols. For example, the second value of the parameter may indicate to apply the second TCI state to downlink receptions. For example, the second value of the parameter may indicate to apply the second TCI state to downlink receptions before the threshold (e.g., timeDurationForQCL, beamSwitchTiming). For example, the second value of the parameter may indicate to receive / buffer downlink receptions in SBFD symbols. For example, the second value of the parameter may indicate to receive / buffer downlink receptions in SBFD symbols before the threshold.

[0448] The wireless device may apply the first TCI state to the downlink reception, for example, based on the parameter (e.g., applylndicatedTCI-State, applylndicatedTCI-State-SBFD, applySymbolType, applyDuplexType) being set / equal to the first value.

[0449] The DCI may comprise a TDRA field. The base station may set / determine a value for the TDRA field. The value of the TDRA field may indicate the initial occasion. For example, the TDRA field may indicate / comprise start-and-length indicator value (SLIV) for the downlink reception (or for the initial occasion of the downlink reception). For example, the TDRA field may indicate, for the initial occasion ofDocket No.: 24-1218PCT the downlink reception, at least one of: a slot offset and a starting symbol, and a length of the downlink reception.

[0450] An initial occasion of the downlink reception may not be in SBFD symbols. The wireless device may not expect the initial occasion of the downlink reception being in SBFD symbols. The initial occasion of the downlink reception may not be in SBFD symbols, for example, based on applying the first TCI state to the downlink reception. The initial occasion of the downlink reception may not be in SBFD symbols, for example, based on the first configuration (e.g. , configuration 1) being indicated to the wireless device.

[0451] An initial occasion of the downlink reception may be in non-SBFD symbols. The wireless device may expect the initial occasion of the downlink reception being in non-SBFD symbols. The initial occasion of the downlink reception may be in non-SBFD symbols, for example, based on applying the first TCI state to the downlink reception. The initial occasion of the downlink reception may be in non- SBFD symbols, for example, based on the first configuration (e.g., configuration 1) being indicated to the wireless device.

[0452] The wireless device may apply the first TCI state to the downlink reception in the non-SBFD symbols. The wireless device may receive, in the non-SBFD symbols and using (or based on) the first TCI state, the downlink reception.

[0453] In an example, the wireless device may not apply the first TCI state to the downlink reception in SBFD symbols. The wireless device may not receive, in the SBFD symbols and using (or based on) the first TCI state, the downlink reception.

[0454] In an example, the wireless device may not apply the second TCI state to the downlink reception in SBFD symbols. The wireless device may not receive, in the SBFD symbols and using (or based on) the second TCI state, the downlink reception.

[0455] When the time offset between reception of the DCI and the downlink reception is less than the threshold, the wireless device may not apply the second TCI state to the downlink reception, for example, based on not reporting capability / support of the second configuration (e.g., configuration 2).

[0456] When the time offset between reception of the DCI and the downlink reception is less than the threshold, the wireless device may not apply the second TCI state to the downlink reception, for example, based on not reporting capability / support of a default QCL parameter (e.g., defaultQCL- TwoTCI-SBFD, defaultQCL-SBFD, defaultQCL-PerSymbolType).

[0457] The wireless device may receive a second DCI (e.g., DCI format 1_0, DCI format 1_1 , DCI format 1_2, DCI format 1_3, and the like).Docket No.: 24-1218PCT

[0458] The second DCI may, for example, schedule a second downlink reception (e.g., PDSCH reception, aperiodic CSI-RS). The second downlink reception may be, for example, a second scheduled downlink reception.

[0459] The second DCI may, for example, trigger a second downlink reception (e.g., aperiodic CSI- RS). The second downlink reception may be, for example, a second triggered downlink reception.

[0460] The second DCI may, for example, indicate activation of a second downlink reception (e.g., SPS PDSCH reception). The second DCI may indicate activation of a second SPS configuration. The second downlink reception may be, for example, a second activated downlink reception.

[0461] The second DCI may comprise a second TDRA field. The base station may set / determine a value for the second TDRA field. For example, the second TDRA field may indicate / comprise start-and- length indicator value (SLIV) for the second downlink reception. For example, the second TDRA field may indicate, for the second downlink reception, at least one of: a slot offset and a starting symbol, and a length of the second downlink reception.

[0462] The second downlink reception may be, for example, in SBFD symbols. The value of the second TDRA field may indicate the SBFD symbols for the second downlink reception.

[0463] In an example, a second time offset between reception of the second DCI and the second downlink reception may be equal to or greater than the threshold (e.g , timeDurationForQCL, beamSwitchTiming). The second time offset between reception of the second DCI and the second downlink reception may be a time offset between a last / ending / latest symbol of the reception of the second DCI and a starting / earliest / first symbol of the second downlink reception. The wireless device may not expect the second time offset between reception of the second DCI and the second downlink reception being less than the threshold.

[0464] The second time offset between reception of the second DCI and the second downlink reception in the SBFD symbols may not be less than the threshold, for example, based on not reporting capability / support of the second configuration (e.g., configuration 2). The second time offset between reception of the second DCI and the second downlink reception in the SBFD symbols may be equal to or greater than the threshold, for example, based on not reporting capability / support of the second configuration (e.g., configuration 2).

[0465] The second time offset between reception of the second DCI and the second downlink reception in the SBFD symbols may not be less than the threshold, for example, based on not reporting capability / support of a default QCL parameter (e.g., defaultQCL-TwoTCI-SBFD, defaultQCL-SBFD, defaultQCL-PerSymbolType). The second time offset between reception of the second DCI and the second downlink reception in the SBFD symbols may be equal to or greater than the threshold, forDocket No.: 24-1218PCT example, based on not reporting capability / support of a default QCL parameter (e.g., defaultQCL- TwoTCI-SBFD, defaultQCL-SBFD, defaultQCL-PerSymbolType).

[0466] The second time offset between reception of the second DCI and the second downlink reception in the SBFD symbols may not be less than the threshold, for example, based on applying the first TCI state to downlink receptions before the threshold.

[0467] The wireless device may apply the second TCI state to the second downlink reception. The wireless device may receive, using (or based on) the second TCI state, the second downlink reception. The wireless device may receive, in the SBFD symbols and using (or based on) the second TCI state, the second downlink reception.

[0468] The wireless device may apply the second TCI state to the downlink reception. The wireless device may receive, using (or based on) the second TCI state, the downlink reception. The wireless device may apply the second TCI state to the downlink reception, for example, based on the time offset between reception of the DCI and the downlink reception being less than the threshold.

[0469] The wireless device may apply the second TCI state to the downlink reception, for example, based on the second TCI state being the 2ndTCI state (e.g., j = 2).

[0470] The wireless device may apply the second TCI state to the downlink reception, for example, based on the second TCI state being associated with the SBFD symbols.

[0471] The wireless device may apply the second TCI state to the downlink reception, for example, based on the second TCI state being specific to the SBFD symbols.

[0472] The wireless device may apply the second TCI state to the downlink reception, for example, based on not reporting capability / support of the second configuration (e.g., configuration 2).

[0473] The wireless device may apply the second TCI state to the downlink reception, for example, based on not reporting capability / support of a default QCL parameter (e.g., defaultQCL-TwoTCI-SBFD, defaultQCL-SBFD, defaultQCL-PerSymbolType). The UE capability information message may not comprise the default quasi co-location (QCL) parameter.

[0474] The wireless device may apply the first TCI state to the downlink reception, for example, based on the parameter (e.g., applylndicatedTCI-State, applylndicatedTCI-State-SBFD, applySymbolType, apply DuplexType) being set / equal to the second value.

[0475] An initial occasion of the downlink reception may not be in non-SBFD symbols. The wireless device may not expect the initial occasion of the downlink reception being in non-SBFD symbols. The initial occasion of the downlink reception may not be in non-SBFD symbols, for example, based on applying the second TCI state to the downlink reception.

[0476] The wireless device may apply the second TCI state to the downlink reception in the SBFD symbols. The wireless device may receive, in the SBFD symbols and using (or based on) the secondDocket No.: 24-1218PCTTCI state, the downlink reception. The initial occasion of the downlink reception may not be in non- SBFD symbols, for example, based on the first configuration (e.g. , configuration 1) being indicated to the wireless device.

[0477] In an example, the wireless device may not apply the second TCI state to the downlink reception in non-SBFD symbols. The wireless device may not receive, in the non-SBFD symbols and using (or based on) the second TCI state, the downlink reception.

[0478] In an example, the wireless device may not apply the first TCI state to the downlink reception in non-SBFD symbols. The wireless device may not receive, in the non-SBFD symbols and using (or based on) the first TCI state, the downlink reception.

[0479] When the time offset between reception of the DCI and the downlink reception is less than the threshold, the wireless device may not apply the first TCI state to the downlink reception, for example, based on not reporting capability / support of the second configuration (e.g., configuration 2).

[0480] When the time offset between reception of the DCI and the downlink reception is less than the threshold, the wireless device may not apply the first TCI state to the downlink reception, for example, based on not reporting capability / support of a default QCL parameter (e.g., defaultQCL-TwoTCI-SBFD, defaultQCL-SBFD, defaultQCL-PerSymbolType) .

[0481] The second downlink reception scheduled / activated / triggered by the second DCI may be, for example, in non-SBFD symbols. The value of the second TDRA field may indicate the non-SBFD symbols for the second downlink reception.

[0482] In an example, a second time offset between reception of the second DCI and the second downlink reception may be equal to or greater than the threshold (e.g., timeDurationForQCL, beamSwitchTiming). The second time offset between reception of the second DCI and the second downlink reception may be a time offset between a last / ending / latest symbol of the reception of the second DCI and a starting / earliest / first symbol of the second downlink reception. The wireless device may not expect the second time offset between reception of the second DCI and the second downlink reception being less than the threshold.

[0483] The second time offset between reception of the second DCI and the second downlink reception in the non-SBFD symbols may not be less than the threshold, for example, based on not reporting capability / support of the second configuration (e.g., configuration 2). The second time offset between reception of the second DCI and the second downlink reception in the non-SBFD symbols may be equal to or greater than the threshold, for example, based on not reporting capability / support of the second configuration (e.g., configuration 2).

[0484] The second time offset between reception of the second DCI and the second downlink reception in the non-SBFD symbols may not be less than the threshold, for example, based on notDocket No.: 24-1218PCT reporting capability / support of a default QCL parameter (e.g., defaultQCL-TwoTCI-SBFD, defaultQCL- SBFD, defaultQCL-PerSymbolType). The second time offset between reception of the second DCI and the second downlink reception in the non-SBFD symbols may be equal to or greater than the threshold, for example, based on not reporting capability / support of a default QCL parameter (e.g., defaultQCL- TwoTCI-SBFD, defaultQCL-SBFD, defaultQCL-PerSymbolType).

[0485] The second time offset between reception of the second DCI and the second downlink reception in the non-SBFD symbols may not be less than the threshold, for example, based on applying the second TCI state to downlink receptions before the threshold.

[0486] The wireless device may apply the first TCI state to the second downlink reception. The wireless device may receive, using (or based on) the first TCI state, the second downlink reception. The wireless device may receive, in the non-SBFD symbols and using (or based on) the first TCI state, the second downlink reception.

[0487] In an example, the cell may operate in a first frequency range (FR1 ). The FR1 may, for example, comprise frequency bands below 6 GHz. A time offset between reception of the DCI and the downlink reception may be less than the threshold (e.g., timeDurationForQCL, beamSwitchTiming), or may be equal to or greater / larger than the threshold.

[0488] The downlink reception may be, for example, in non-SBFD symbols. The value of the TDRA field may indicate the non-SBFD symbols for the downlink reception. The wireless device may apply the first TCI state to the downlink reception in the non-SBFD symbols. The wireless device may receive, in the non-SBFD symbols and using (or based on) the first TCI state, the downlink reception. The wireless device may apply the first TCI state to the downlink reception, for example, based on the downlink reception being in the non-SBFD symbols.

[0489] The wireless device may apply the first TCI state to the downlink reception in the non-SBFD symbols, for example, based on the cell operating in the first frequency range (FR1). The wireless device may apply the first TCI state to the downlink reception in the non-SBFD symbols, for example, based on the wireless device being in the first frequency range (FR1)

[0490] The downlink reception may be, for example, in SBFD symbols. The value of the TDRA field may indicate the SBFD symbols for the downlink reception. The wireless device may apply the second TCI state to the downlink reception in the SBFD symbols. The wireless device may receive, in the SBFD symbols and using (or based on) the second TCI state, the downlink reception. The wireless device may apply the second TCI state to the downlink reception, for example, based on the downlink reception being in the SBFD symbols.

[0491] The wireless device may apply the second TCI state to the downlink reception in the SBFD symbols, for example, based on the cell operating in the first frequency range (FR1). The wirelessDocket No.: 24-1218PCT device may apply the second TCI state to the downlink reception in the SBFD symbols, for example, based on the wireless device being in the first frequency range (FR1 ).

[0492] The wireless device may apply the first TCI state to the downlink reception in the non-SBFD symbols, for example, based on reporting capability / support of the second configuration (e.g., configuration 2) to the base station in the UE capability information message. The wireless device may apply the second TCI state to the downlink reception in the SBFD symbols, for example, based on reporting capability / support of the second configuration (e.g., configuration 2) to the base station in the UE capability information message

[0493] The wireless device may apply the first TCI state to the downlink reception in the non-SBFD symbols, for example, based on reporting capability / support of a default QCL parameter (e.g., defaultQCL-TwoTCI-SBFD, defaultQCL-SBFD, defaultQCL-PerSymbolType) to the base station in the UE capability information message. The wireless device may apply the second TCI state to the downlink reception in the SBFD symbols, for example, based on reporting capability / support of a default QCL parameter (e.g., defaultQCL-TwoTCI-SBFD, defaultQCL-SBFD, defaultQCL-PerSymbolType) to the base station in the UE capability information message. The UE capability information message may comprise the default QCL parameter.

[0494] In an example, the wireless device may not report capability / support of the second configuration (e.g., configuration 2) to the base station in the UE capability information message. In an example, the wireless device may not report capability / support of a default QCL parameter (e.g., defaultQCL-TwoTCI-SBFD, defaultQCL-SBFD, defaultQCL-PerSymbolType) to the base station in the UE capability information message. A time offset between reception of the DCI and the downlink reception may be equal to or greater / larger than the threshold. The wireless device may apply the first TCI state to the downlink reception in the non-SBFD symbols, for example, based on the time offset between reception of the DCI and the downlink reception being equal to or greater / larger than the threshold. The wireless device may apply the second TCI state to the downlink reception in the SBFD symbols, for example, based on the time offset between reception of the DCI and the downlink reception being equal to or greater / larger than the threshold.

[0495] In an example, the downlink reception may not overlap in time with a downlink signal. There may be no downlink signal in the same symbols as the downlink reception.

[0496] In an example, the downlink reception may be an aperiodic CSI-RS (or an aperiodic CSI-RS resource). The one or more configuration parameters may comprise one or more CSI report configuration parameters (e.g., CSI-ReportConfig).

[0497] The one or more CSI report configuration parameters may comprise a parameter (e.g., applylndicatedTCI-State, applylndicatedTCI-State-SBFD, apply SymbolType, applyDuplexType). TheDocket No.: 24-1218PCT parameter may indicate, for example, whether to apply the first TCI state or the second TCI state to aperiodic CSI-RSs (or aperiodic CSI-RS resources). The parameter may indicate, for example, whether to apply the first TCI state or the second TCI state to aperiodic CSI-RSs (or aperiodic CSI-RS resources) before the threshold (e.g., beamSwitchTiming). The parameter may indicate, for example, whether to receive / buffer aperiodic CSI-RSs (or aperiodic CSI-RS resources) in non-SBFD symbols or SBFD symbols. The parameter may indicate, for example, whether to receive / buffer aperiodic CSI-RSs (or aperiodic CSI-RS resources) in non-SBFD symbols or SBFD symbols before the threshold. The parameter may indicate, for example, whether aperiodic CSI-RSs (or aperiodic CSI-RS resources) are restricted to non-SBFD symbols only or SBFD symbols only.

[0498] A first value of the parameter (e.g., 'first', ‘O’, ‘non-SBFD’, ‘downlink’) may indicate the first TCI state associated with the non-SBFD symbols. For example, the first value of the parameter may indicate to apply the first TCI state to the aperiodic CSI-RSs (or aperiodic CSI-RS resources). For example, the first value of the parameter may indicate to apply the first TCI state to aperiodic CSI-RSs (or aperiodic CSI-RS resources) before the threshold (e.g., timeDurationForQCL, beamSwitchTiming). For example, the first value of the parameter may indicate to receive / buffer aperiodic CSI-RSs (or aperiodic CSI-RS resources) in non-SBFD symbols. For example, the first value of the parameter may indicate to receive / buffer aperiodic CSI-RSs (or aperiodic CSI-RS resources) in non-SBFD symbols before the threshold.

[0499] A second value of the parameter (e.g., ‘second’, ‘T, 'SBFD') may indicate the second TCI state associated with the SBFD symbols. For example, the second value of the parameter may indicate to apply the second TCI state to aperiodic CSI-RSs (or aperiodic CSI-RS resources). For example, the second value of the parameter may indicate to apply the second TCI state to aperiodic CSI-RSs (or aperiodic CSI-RS resources) before the threshold (e.g., timeDurationForQCL, beamSwitchTiming). For example, the second value of the parameter may indicate to receive / buffer aperiodic CSI-RSs (or aperiodic CSI-RS resources) in SBFD symbols. For example, the second value of the parameter may indicate to receive / buffer aperiodic CSI-RSs (or aperiodic CSI-RS resources) in SBFD symbols before the threshold.

[0500] The wireless device may apply the first TCI state to the aperiodic CSI-RS (or the aperiodic CSI-RS resource) in the non-SBFD symbols, for example, based on the parameter (e.g., apply IndicatedTCi-State, applylndicatedTCI-State-SBFD, applySymbolType, apply DuplexType) being set / equal to the first value.

[0501] The wireless device may apply the second TCI state to the aperiodic CSI-RS (or the aperiodic CSI-RS resource) in the SBFD symbols, for example, based on the parameter (e.g., applylndicatedTCI-Docket No.: 24-1218PCTState, applylndicatedTCl-State-SBFD, applySymbolType, applyDuplexType) being set / equal to the second value.

[0502] In an example, the parameter (e.g., apply IndicatedTCI-State, applylndicatedTCl-State-SBFD, applySymbolType, applyDuplexType) may be per aperiodic CSI-RS resource. In an example, the parameter (e.g., applylndicatedTCI-State, applylndicatedTCl-State-SBFD, applySymbolType, applyDuplexType) may be per aperiodic CSI-RS resource set.

[0503] In an example, the default QCL parameter (e.g., defaultQCL-TwoTCI-SBFD, defaultQCL- SBFD, defaultQCL-PerSymbolType) may indicate whether the wireless device supports default QCL assumption with two TCI states in both SBFD symbols and non-SBFD symbols. The default QCL parameter may be a first default QCL parameter.

[0504] In an example, the default QCL parameter (e.g., defaultQCL-TwoTCI-SBFD, defaultQCL- SBFD, defaultQCL-PerSymbolType) may indicate whether the wireless device supports default QCL assumption with a TCI state in SBFD symbols. The default QCL parameter may be a second default QCL parameter.

[0505] In an example, the default QCL parameter (e.g., defaultQCL-TwoTCI-SBFD, defaultQCL- SBFD, defaultQCL-PerSymbolType) may indicate whether the wireless device supports default QCL assumption per symbol type (e.g , SBFD symbols and non-SBFD symbols). The default QCL parameter may be a third default QCL parameter.

[0506] In an example, the first default QCL parameter and the second default QCL parameter may be different. In an example, the first default QCL parameter and the third default QCL parameter may be different. In an example, the second default QCL parameter and the third default QCL parameter may be different.

[0507] The wireless device indicating support of default QCL assumption with two TCI states in both SBFD symbols and non-SBFD symbols may indicate support / capability of the second configuration (e.g., configuration 2). The UE capability information message may indicate support / capability of the second configuration (e.g., configuration 2), for example, in response to the UE capability information message comprising the default QCL parameter indicating support of default QCL assumption with two TCI states in both SBFD symbols and non-SBFD symbols.

[0508] The wireless device indicating support of default QCL assumption with a TCI state in SBFD symbols may indicate support / capability of the second configuration (e.g., configuration 2). The UE capability information message may indicate support / capability of the second configuration (e.g., configuration 2), for example, in response to the UE capability information message comprising the default QCL parameter indicating support of default QCL assumption with a TCI state in SBFD symbols.Docket No.: 24-1218PCT

[0509] The wireless device indicating support of default QCL assumption per symbol type (e.g., SBFD symbols and non-SBFD symbols) may indicate support / capability of the second configuration (e.g., configuration 2). The UE capability information message may indicate support / capability of the second configuration (e.g., configuration 2), for example, in response to the UE capability information message comprising the default QCL parameter per symbol type (e.g., SBFD symbols and non-SBFD symbols).

[0510] In an example, the UE capability information message may not comprise the default QCL parameter based on the UE capability information message not comprising a parameter indicating support / capability of the second configuration (e.g., configuration 2). The parameter indicating support / capability of the second configuration (e.g., configuration 2) may not be present (or may be absent) in the UE capability information message.

[0511] In an example, the UE capability information message may comprise the default QCL parameter based on the UE capability information message comprising a parameter indicating support / capability of the second configuration (e.g., configuration 2). The wireless device may include / add, in the UE capability information message, the default QCL parameter. The parameter indicating support / capability of the second configuration (e.g., configuration 2) may be present in the UE capability information message.

[0512] The default QCL parameter may be different from a parameter (e.g., defaultQCL-TwoTCI) indicating whether the wireless supports default QCL assumption with two TCI states using single-DCI based multi-TRP.

[0513] The default QCL parameter may be different from a parameter (e.g., defaultQCL- PerCORESETPoollndex) indicating whether the wireless device supports default QCL assumption per CORESET pool index using multi-DCI based multi-TRP.

[0514] The wireless device may receive, from the base station, a UE capability enquiry message (e.g., UECapabilityEnquiry, UE capability enquiry). The wireless device may transmit, to the base station, a UE capability information message (e.g., UECapabilitylnformation, UE capability information message), for example, based on receiving the UE capability enquiry message.

[0515] The UE capability information message may comprise a first parameter (e.g., SBFD-PUSCH- twoPHR-Reporting) .

[0516] The first parameter may indicate, for example, support of PHR repor...

Claims

Docket No.: 24-1218PCTCLAIMS1. A method comprising: receiving, by a wireless device, one or more radio resource control (RRC) messages indicating a first configuration is applied to downlink receptions, wherein, in the first configuration, downlink receptions are restricted to subband full duplex (SBFD) symbols only or non-SBFD symbols only; receiving downlink control information (DCI) scheduling downlink receptions in SBFD symbols and non-SBFD symbols, wherein an offset between reception of the DCI and a starting symbol of the downlink receptions is less than a threshold; and based on the offset being less than the threshold, receiving the downlink receptions in a default symbol type among the SBFD symbols and the non-SBFD symbols.

2. A method comprising: receiving, by a wireless device, downlink control information (DCI) scheduling downlink receptions in subband full duplex (SBFD) symbols and non-SBFD symbols, wherein an offset between reception of the DCI and a starting symbol of the downlink receptions is less than a threshold; and based on the offset being less than the threshold, receiving the downlink receptions in a default symbol type among the SBFD symbols and the non-SBFD symbols.

3. The method of claim 2, wherein the threshold is: a time duration for quasi co-location (QCL); or a beam switching time duration.

4. The method of any one of claims 2 to 3, further comprising receiving one or more radio resource control (RRC) messages.

5. The method of claim 4, wherein: the one or more RRC messages indicate a first configuration is applied to downlink receptions in which receptions are restricted to subband full duplex (SBFD) symbols only or non-SBFD symbols only.

6. The method of claim 5, wherein, in the first configuration, downlink receptions are restricted to SBFD symbols only or non-SBFD symbols only based on a symbol type of an initial occasion of the downlink receptions.

7. The method of any one of claims 5 to 6, wherein the receiving the downlink receptions in the default symbol type is further based on the downlink receptions being indicated with the first configuration and the offset being less than the threshold.

8. The method of any one of claims 4 to 7, wherein the one or more RRC messages indicate a value of the threshold.

9. The method of any one of claims 2 to 8, wherein the downlink receptions are at least one of:Docket No.: 24-1218PCT physical downlink shared channel (PDSCH) receptions; repetitions of a PDSCH reception; receptions based on semi-persistent scheduling (SPS) configuration; multiple PDSCH receptions (Multi-PDSCH) scheduled by a single DCI; or aperiodic channel state information reference signals (CSI-RSs).

10. The method of any one of claims 2 to 9, further comprising transmitting a capability message indicating at least one of: the wireless device supports only a first configuration in which downlink receptions are restricted to SBFD symbols only or non-SBFD symbols only; the wireless device does not support a second configuration in which downlink receptions are received in both SBFD symbols and non-SBFD symbols; or the wireless device does not support buffering across both non-SBFD symbols and SBFD symbols.11 . The method of claim 10, wherein the receiving the downlink receptions in the default symbol type is based on the wireless device not supporting buffering across both non-SBFD symbols and SBFD symbols.

12. The method of any one of claims 2 to 11 , further comprising not receiving the downlink receptions in symbols not having the default symbol type.

13. The method of claim 12, wherein not receiving comprises at least one of: not monitoring, in the symbols not having the default symbol type, for the downlink receptions; not decoding, in the symbols not having the default symbol type, for the downlink receptions; ignoring, in the symbols not having the default symbol type, the downlink; or not buffering a physical downlink shared channel (PDSCH) in the symbols not having the default symbol type.

14. The method of any one of claims 2 to 13, wherein the DCI indicates to apply: a first TCI state to SBFD symbols; and a second TCI state to non-SBFD symbols.

15. The method of claim 14, further comprising applying, to the downlink receptions, a default TCI state, among the first TCI state and the second TCI state, associated with the same symbol type as the default symbol type.

16. The method of claim 15, wherein the applying the default TCI state associated with the default symbol type is based on the offset being less than the threshold.

17. The method of any one of claims 15 to 16, wherein: the default TCI state is the first TCI state based on the default symbol type being SBFD symbols; andDocket No.: 24-1218PCT the default TCI state is the second TCI state based on the default symbol type being non-SBFD symbols.

18. The method of any one of claims 14 to 17, further comprising receiving a medium access control (MAC) control element (CE) indicating that the first TCI state and the second TCI state are mapped to one TCI codepoint.

19. The method of claim 18, wherein the DCI comprises a TCI field indicating the one TCI codepoint.

20. The method of any one of claims 14 to 19, wherein the first TCI state and the second TCI states are both applicable to uplink and downlink.21 . The method of any one of claims 14 to 20, wherein the first TCI state and the second TCI states are unified TCI states.

22. The method of any one of claims 2 to 21 , wherein the SBFD symbols are symbols configured with an uplink subband and at least one downlink subband.

23. The method of any one of claims 2 to 22, wherein the non-SBFD symbols are downlink symbols.

24. The method of any one of claims 2 to 23, further comprising transmitting a capability message indicating whether the wireless device supports a default QCL assumption for SBFD symbols and non- SBFD symbols.

25. The method of claim 24, wherein a default TCI state is applied, to the downlink receptions, based on the capability message indicating that the wireless device supports the default QCL assumption and the offset being less than the threshold.

26. The method of any one of claims 2 to 25, wherein receiving comprises at least one of: monitoring, in the symbols having the default symbol type, for the downlink receptions; decoding, in the symbols having the default symbol type, for the downlink receptions; or buffering a PDSCH in the symbols not having the default symbol type.

27. The method of any one of claims 2 to 26, wherein the default symbol type is one symbol type from among the SBFD symbols and the non-SBFD symbols.

28. The method of any one of claims 4 to 27, where in the one or more messages comprise: a first SRS resource set list parameter indicating the first SRS resource set; and a second SRS resource set list parameter indicating the second SRS resource set.

29. The method of any one of claims 2 to 28, further comprising receiving one or more messages indicating: a period of SBFD symbols within a time division duplex (TDD) pattern of slots in a TDD configuration of a cell; and frequency locations of an uplink subband of the SBFD symbols in the period.Docket No.: 24-1218PCT30. The method of claim 29, wherein the one or more messages comprise a system information block (SIB) indicating the period and the frequency locations of the uplink subband of the SBFD symbols in the period.31 . An apparatus comprising: one or more processors; and memory storing instructions that, when executed by the one or more processors, cause the apparatus to perform the method of any one of claims 1 to 30.

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

Images