Transmission and reception across multiple carriers in subband full-duplex

Abstract

A method comprises receiving, by a wireless device, one or more first messages indicating an uplink signal that is via a symbol on a first cell and a downlink resource, of a second cell, on the symbol. The first cell and the second cell are configured to operate in a same frequency band. The method further comprises, based on the symbol being indicated as a subband full duplex (SBFD) symbol on the first cell, transmitting the uplink signal via the first cell.

Description

Docket No.: 24-1171 PCTTITLETransmission and Reception Across Multiple Carriers in Subband Full-Duplex CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 681 ,107, filed August 8,2024, which is hereby incorporated by reference in its entirety.BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0032] FIGs. 26A, 26B, 26C, and 26D illustrate aspects of example embodiments according to the present disclosure.

[0033] FIGs. 27A, 27B, 27C, and 27D illustrate aspects of example embodiments according to the present disclosure.

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

[0035] FIGs. 29A, 29B, and 29C illustrate aspects of example embodiments according to the present disclosure.

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

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

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

[0039] FIGs. 33A, 33B, 33C, and 33D illustrate aspects of example embodiments according to the present disclosure.

[0040] FIGs. 34A, 34B, 34C, and 34D illustrate aspects of example embodiments according to the present disclosure

[0041] FIGs. 35A, 35B, 35C, and 35D illustrate aspects of example embodiments according to the present disclosure.Docket No.: 24-1171 PCT

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

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

[0044] FIGs. 38A, 38B, 38C, and 39D illustrate aspects of example embodiments according to the present disclosure.

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

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

[0047] FIG. 41 illustrates an aspect of an example embodiment according to the present disclosure.DETAILED DESCRIPTION

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

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

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

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

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

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

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

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

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

[0057] FIG. 1 A illustrates an example of a mobile communication network 100 in which embodiments of the present disclosure may be implemented. The mobile communication network 100 may be, for example,Docket No.: 24-1171 PCT 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0072] As shown in FIG. 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.

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

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

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

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

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

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

[0079] FIG. 3 illustrates an example of services provided between protocol layers of the NR user plane protocol stack. Starting from the top of FIG. 2A and FIG. 3, the SDAPs 215 and 225 may perform QoS flow handling. The UE 210 may receive services through a PDU session, which may be a logical connection between the UE 210 and a DN. The PDU session may have one or more QoS flows. A UPF of a CN (e.g., the UPF 158B) may map IP packets to the one or more QoS flows of the PDU session based on QoS requirements (e.g., in terms of delay, data rate, and / or error rate). The SDAPs 215 and 225 may perform mapping / de-mapping between the one or more QoS flows and one or more data radio bearers. The mapping / de-mapping between the QoS flows and the data radio bearers may be determined by the SDAP 225 at the gNB 220. The SDAP 215 at the UE 210 may be informed of the mapping between the QoS 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 indicatorDocket No.: 24-1171 PCT(QFI), which may be observed by the SDAP 215 at the UE 210 to determine the mapping / de-mapping between the QoS flows and the data radio bearers.

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

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

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

[0083] The MACs 212 and 222 may perform multiplexing / demultiplexing of logical channels and / or mapping between logical channels and transport channels. The multiplexing / demultiplexing may include multiplexing / demultiplexing of data units, belonging to the one or more logical channels, into / from Transport Blocks (TBs) delivered to / from the PHYs 211 and 221 . The MAC 222 may be configured to perform scheduling, scheduling information reporting, and priority handling between UEs by means of dynamic scheduling. Scheduling may be performed in the gNB 220 (at the MAC 222) for downlink and uplink. The MACs 212 and 222 may be configured to perform error correction through Hybrid Automatic Repeat Request (HARQ) (e.g., one HARQ entity per carrier in case of Carrier Aggregation (CA)), priority 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 transmissionDocket No.: 24-1171 PCT timing a logical channel may use. As shown in FIG. 3, the MACs 212 and 222 may provide logical channels as a service to the RLCs 213 and 223.

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

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

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

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

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

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

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

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

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

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

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

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

[0096] - a dedicated traffic channel (DTCH) for carrying user data to / from a specific the UE.Docket No.: 24-1171 PCT

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0114] FIG. 6 is an example diagram showing RRC state transitions of a UE. The UE may be the same or similar to the wireless device 106 depicted in FIG. 1A, the UE 210 depicted in FIG. 2A and FIG. 2B, or any other wireless device described in the present disclosure. As illustrated in FIG. 6, a UE may be in at 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).

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

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

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

[0118] An RRC state may be associated with a mobility management mechanism. In RRC idle 604 and RRC inactive 606, mobility is managed by the UE through cell reselection. The purpose of 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 606Docket No.: 24-1171 PCT track the UE on a cell-group level. They may do so using different granularities of grouping. For example, there may be three levels of cell-grouping granularity: individual cells; cells within a RAN area identified by a RAN area identifier (RAI); and cells within a group of RAN areas, referred to as a tracking area and identified by a tracking area identifier (TAI).

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

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

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

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

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

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

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

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

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

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

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

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

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

[0132] For a downlink BWP in a set of configured downlink BWPs on a primary cell (PCell), a base station may configure a UE with one or more control resource sets (CORESETs) for at least one search space. A search space is a set of locations in the time and frequency domains where the UE may find control information. The search space may be a UE-specific search space or a common search space (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.

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

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

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

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

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

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

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

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

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

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

[0143] In an example, up to 32 CCs may be aggregated. The aggregated CCs may have the same or different bandwidths, subcarrier spacing, and / or duplexing schemes (TDD or FDD). A serving cell for a 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.

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

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

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

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

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

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

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

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

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

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

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

[0155] The PBCH may use a QPSK modulation and may use forward error correction (FEC). The FEC may use polar coding. One or more symbols spanned by the PBCH may carry one or more DMRSs for demodulation of the PBCH. The PBCH may include an indication of a current system frame number (SFN) of the cell and / or a SS / PBCH block timing index. These parameters may facilitate time synchronization of the UE to the base station. The PBCH may include a master information block (MIB) used to provide the UE with one or more parameters. The MIB may be used by the UE to locate remaining minimum 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.

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

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

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

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

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

[0161] The base station may configure the UE to report CSI measurements. The base station may configure the UE to provide CSI reports periodically, aperiodically, or semi-persistently. For periodic CSI reporting, the UE may be configured with a timing and / or periodicity of a plurality of CSI reports. For aperiodic CSI reporting, the base station may request a CSI report. For example, the base station may command the UE to measure a configured CSI-RS resource and provide a CSI report relating to 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.

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

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

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

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

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

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

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

[0169] Uplink PT-RS (which may be used by a base station for phase tracking and / or phase-noise compensation) may or may not be present depending on an RRC configuration of the UE. The presence and / or pattern of uplink PT-RS may be configured on a UE-specific basis by a combination of RRC signaling and / or one or more parameters employed for other purposes (e.g., Modulation and Coding Scheme (MCS)), which may be indicated by DCI. When configured, a dynamic presence of uplink PT-RS may be associated with one or more DCI parameters comprising at least MCS. A radio network 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.

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

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

[0172] An antenna port is defined such that the channel over which a symbol on the antenna port is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed. If a first symbol and a second symbol are transmitted on the same antenna port, the receiver may infer the channel (e.g., fading gain, multipath delay, and / or the like) for conveying the second 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.

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

[0174] FIG. 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 followingDocket No.: 24-1171 PCT parameters may be configured by higher layer signaling (e.g., RRC and / or MAC signaling) for a CSI-RS resource configuration: a CSI-RS resource configuration identity, a number of CSI-RS ports, a CSI-RS configuration (e.g., symbol and resource element (RE) locations in a subframe), a CSI-RS subframe configuration (e.g., subframe location, offset, and periodicity in a radio frame), a CSI-RS power parameter, a CSI-RS sequence parameter, a code division multiplexing (CDM) type parameter, a frequency density, a transmission comb, quasi co-location (QCL) parameters (e.g., QCL-scramblingidentity, crs-portscount, mbsfn-subfrarreconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid), and / or other radio resource parameters.

[0175] The three beams illustrated in FIG. 11 B may be configured for a UE in a UE-specific configuration. Three beams are illustrated in FIG. 11 B (beam #1 , beam #2, and beam #3), more or fewer beams may be configured. Beam #1 may be allocated with CSI-RS 1101 that may be transmitted in one or more subcarriers in an RB of a first symbol. Beam #2 may be allocated with CSI-RS 1102 that may be transmitted in one or more subcarriers in an RB of a second symbol. Beam #3 may be allocated with CSI- RS 1103 that may be transmitted in one or more subcarriers in an RB of a third symbol. By using frequency division multiplexing (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.

[0176] CSI-RSs such as those illustrated in FIG 11 B (e.g., CSI-RS 1101 , 1102, 1103) may be transmitted by the base station and used by the UE for one or more measurements. For example, the UE may measure a reference signal received power (RSRP) of configured CSI-RS resources. The base station may configure the UE with a reporting configuration and the UE may report the RSRP measurements to a network (for example, via one or more base stations) based on the reporting configuration. In an example, the base station may determine, based on the reported measurement results, one or more transmission configuration indication (TCI) states comprising a number of reference signals. In an example, the base station may indicate one or more TCI states to the UE (e.g., via RRC signaling, a MAC CE, and / or a DCI). The UE may receive a downlink transmission with a receive (Rx) beam determined based on the one or more TCI states. In an example, the UE 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.Docket No.: 24-1171 PCT

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

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

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

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

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

[0182] A network (e.g., a gNB and / or an ng-eNB of a network) and / or the UE may initiate a random access procedure. A UE in an RRCJDLE state and / or an RRCJNACTIVE state may initiate the random access procedure to request a connection setup to a network. The UE may initiate the random 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0199] Msg A 1331 may be transmitted in an uplink transmission by the UE. Msg A 1331 may comprise one or more transmissions of a preamble 1341 and / or one or more transmissions of a transport block 1342. The transport block 1342 may comprise contents that are similar and / or equivalent to the contents of the Msg 3 1313 illustrated in FIG. 13A. The transport block 1342 may comprise UCI (e.g., an SR, a HARQ ACK / NACK, and / or the like). The UE may receive the Msg B 1332 after or in response to transmitting the Msg A 1331 . The Msg B 1332 may comprise contents that are similar and / or equivalent to the contents 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.

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

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

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

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

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

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

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

[0207] Depending on the purpose and / or content of a DCI, the base station may transmit the DCIs with one or more DCI formats. For example, DCI format 0_0 may be used for scheduling of PUSCH in a cell. DCI format 0_0 may be a fallback DCI format (e.g., with compact DCI payloads). DCI format 0_1 may be used for scheduling of PUSCH in a cell (e.g., with more DCI payloads than DCI format 0_0). DCI format 1_0 may be used for scheduling of PDSCH in a cell. DCI format 1_0 may be a fallback DCI format (e.g.,Docket No.: 24-1171 PCT 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.

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

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

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

[0211] The base station may transmit, to the UE, RRC messages comprising configuration parameters of one or more CORESETs and one or more search space sets. The configuration parameters may indicateDocket No.: 24-1171 PCT 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).

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

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

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

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

[0216] After determining a PUCCH resource set from a plurality of PUCCH resource sets, the UE may determine a PUCCH resource from the PUCCH resource set for UCI (HARQ-ACK, CSI, and / or SR)Docket No.: 24-1171 PCT 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.

[0217] FIG. 15 illustrates an example of a wireless device 1502 in communication with a base station 1504 in accordance with embodiments of the present disclosure. The wireless device 1502 and base station 1504 may be part of a mobile communication network, such as the mobile communication network 100 illustrated in FIG. 1A, the mobile communication network 150 illustrated in FIG. 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.

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

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

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

[0221] At the base station 1504, a reception processing system 1512 may receive the uplink transmission from the wireless device 1502. At the wireless device 1502, a reception processing system 1522 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.

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

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

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

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

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

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

[0228] FIG. 16C illustrates an example structure for downlink transmissions. A baseband signal representing a physical downlink channel may perform one or more functions. The one or more functions may comprise: scrambling of coded bits in a codeword to be transmitted on a physical channel; modulation of scrambled bits to generate complex-valued modulation symbols; mapping of the complex-valued modulation symbols onto one or several transmission layers; precoding of the complex-valued modulation symbols on a layer for transmission on the antenna ports; mapping of complex-valued modulation symbols for an antenna port to resource elements; generation of complex-valued time-domain OFDM signal for anDocket No.: 24-1171 PCT 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0245] The one or more configuration parameters may, for example via one or more serving cell configuration parameters, comprise / configure / indicate the one or more cells (e.g., ServingCellConfigCommon, ServingCellConfigCommonS'B, and / or ServingCellConfig). The one or more cells may comprise one or more serving cell (e.g., the one or more Serving Cells). The one or more serving cell configuration parameters may be for configuring one or more cells (e.g., the one or more ServingDocket No.: 24-1171 PCTCells). For example, the one or more cells may comprise a master (or primary) cell group (MSG) and / or a secondary cell group (SCG).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0263] FIG. 17 illustrates an example of UL / DL TDD configuration as per an aspect of an embodiment of the present disclosure. The UL / DL TDD configuration may be (or comprise) a cell-specific UL / DL TDD configuration (e.g., TDD-UL-DL-ConfigCommori). The UL / DL TDD configuration may be (or comprise) a UE-specific UL / DL TDD configuration (e.g., TDD-UL-DL-ConfigDedicated).

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

[0265] For a serving cell (of the one or more serving cells), one or more common TDD configuration parameters may indicate / configure slot format(s) of a plurality of slots. FIG. 18 shows examples of a slot format in a TDD carrier.

[0266] The one or more TDD configuration parameters may indicate / configure the plurality of slots. The plurality of slots may comprise one or more consecutive slots. The plurality of slots may comprise one orDocket No.: 24-1171 PCT more DL slots / symbols. The plurality of slots may comprise one or more UL slots / symbols The plurality of slots may comprise one or more flexible slots / symbols.

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

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

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

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

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

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

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

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

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

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

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

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

[0279] Using / based on the one or more TDD configuration parameters, the wireless device may determine the slot format of each slot / symbol of the plurality of slots. Using / based on the one or more UE-specificDocket No.: 24-1171 PCTTDD configuration parameters, the wireless device may determine a symbol format of each symbol of the plurality of slots. The symbol format may be the slot format.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0299] In an example, a SBFD operation may be referred as (or interchangeably used in some embodiments) a SBFD mode, a new enhanced duplex mode, a hybrid TDD / FDD mode, a enhanced duplexing operation, and / or the like. Using the SBFD operation, a wireless device may reduce UL transmission latency or UL transmission capacity, as the wireless device may be al lowed / con figured to transmit UL signals / channels in / during SBFD symbols / slots.

[0300] In an example, a SBFD symbol may be referred as (or interchangeably used with) a flexible symbol in a SBFD carrier / serving cell / cell, a SBFD symbol of a carrier / serving cell / cell, a downlink / flexible symbol with a UL subband configured, a symbol with a UL subband configured, a time unit configured with a UL subband, a symbol referred as a SBFD operation, a symbol where a wireless device operates a SBFD operation, a symbol indicated to apply a SBFD operation or a UL band by one or more SBFD configuration parameters and one or more RRC messages indicating to enable the SBFD operation on the symbol, and / or the like.

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

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

[0303] The one or more configuration parameters may configure a wireless device with the SBFD operation in the carrier. The one or more configuration parameters may comprise one or more SBFD configuration parameters. The one or more TDD configuration parameters may comprise one or more SBFD configuration parameters.

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

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

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

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

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

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

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

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

[0312] The first period may be based on the first TDD pattern. For example, the first period may be the first TDD periodicity P1(of the first TDD pattern). Based on the one or more SBFD configuration parameters not indicating the first period, the wireless device may set the first period to a value (e.g., a default value). The value may be the first TDD periodicity.Docket No.: 24-1171 PCT

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

[0314] In some examples, the value may be a summation of the first TDD periodicity and the second TDD periodicity P2.

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

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

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

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

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

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

[0321] An SBFD slot / symbol of the at least one SBFD slot / symbol may be a DL slot / symbol (of the one or more DL slots / symbols) or a flexible slot / symbol (of the one or more flexible slots / symbols) configured for the SBFD operation. The SBFD slot / symbol may be within the SBFD time locations.Docket No.: 24-1171 PCT

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

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

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

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

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

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

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

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

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

[0331] In the present disclosure, the second set of RBs may interchangeably be used / referred to by "a second set of PRBs” or "a second set of subcarriers” or "the second set of REs”.

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

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

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

[0335] The frequency locations of guardband(s) for each SBFD symbol / slot within the SBFD subband time locations may be the third set of RBs.

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

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

[0338] The second set of resource blocks / resource elements may comprise contiguous resource blocks / elements (e g., for the D-U or U-D partitioning of the frequency resources) or non-contiguous blocks / elements (e.g., D-U-D partitioning of the frequency resources).Docket No.: 24-1171 PCT

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

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

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

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

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

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

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

[0346] For example, a maximum number of UL subbands (UL SBs) for SBFD operation in an SBFD symbol within a TDD carrier is a first number. The one or more SBFD configuration parameters may configure / indicate the first number. When the first number is absent / missing from the one or more SBFD configuration parameters, the wireless device may determine (e.g., consider) a value (e.g., a default value) for the first number. The value may be one.Docket No.: 24-1171 PCT

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

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

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

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

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

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

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

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

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

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

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

[0358] FIGs. 21 A and 21 B illustrate examples as per aspects of embodiments of the present disclosure. FIG. 21A illustrates a capability signaling of a wireless device supporting a link direction handling when downlink and uplink resources are scheduled in a same time over a plurality of serving cells. A wireless device may be configured with a plurality of carriers / cel Is wherein the plurality of carriers / cells operate in a (same) frequency band (e.g., n 1 , n48, etc.). For example, the wireless device may be configured with intraband carrier aggregations of a plurality of serving cells. The wireless device may or may not support simultaneous transmission via a first serving cell of the plurality of cells while receiving via a second serving cell of the plurality of cells. The wireless device may or may not support (or the wireless device may have a capability) to determine a link direction or whether to transmit or receive when the wireless device is scheduled with downlink reception via a first cell of the plurality of serving cells and uplink transmission via a second cell of the plurality of serving cells. In response to supporting or having the capability, the wireless device may indicate directional collision handling (procedure) across multiple cells using a same subcarrier spacing for the frequency band.

[0359] In an example, the wireless device may transmit a capability signal via RRC to a base station that indicate whether the wireless device is capable of (e.g., supports) handling a link direction when a conflict between downlink of a first cell and uplink of a second cell among configured serving cells occur in time. The wireless device may transmit one or more capabilities (e.g., 'half-DuplexTDD-CA-SameSCS') indicating that the wireless device supports a directional collision handling (procedure) for a plurality of cells using a same subcarrier spacing, to the base station for each band combination or a band that the wireless device supports to be configured with a set of serving cells (e.g., a set of carrier aggregation combinations). The directional collision handling may be used for the plurality of cells that the wireless device may not support simultaneous reception and transmission via the plurality of cells.Docket No.: 24-1171 PCT

[0360] The wireless device may indicate whether the wireless device supports directional collision handling between a reference cell and another cell for a half-duplex operation in TDD CA with a same subcarrier spacing via the 'half-DuplexTDD-CA-SameSCS' capability signaling. The wireless device may operate in a half-duplex operation in TDD CA. When the wireless device operates in the half-duplex operation in TDD CA, the wireless device may support either receive or transmit via a plurality of serving cells of the TDD CA but not supporting receiving and transmission simultaneously via the plurality of serving cells at a same time.

[0361] The wireless device may indicate the capability for an intra-band TDD CA band combination or band or, if the wireless device may not support simultaneous transmission and reception over a second plurality of serving cells, wherein the second plurality of serving cells operate in a plurality of frequency bands, the wireless device may indicate the capability for the plurality of frequency bands.

[0362] Based on the capability signaling of the wireless device, the base station may transmit one or more RRC messages indicating to enable the collision handling or the link direction handling over a plurality of serving cells. FIG. 21 B illustrates the one or more RRC messages to enable the direction handling for a serving cell. In an example, the base station may transmit one or more RRC messages indicating 'directionalCollisionHandling' to be enabled (e.g., enabled) for the serving cell. In response to receiving the one or more RRC messages, the wireless device may perform a link direction procedure as illustrated in FIG. 25 for the serving cell.

[0363] The 'directionalCollisionHandling' may indicate that a serving cell configured with the 'directionalCollisionHandling' between a reference cell and a second serving cell. In the example, the second serving cell may be same as the serving cell or may be different from the serving cell and the reference cell may be same to the serving cell or may be different from the serving cell. The base station may configure one or more RRC messages of the ‘directionalCollisionHandling’ over one or more TDD serving cells that are using same subcarrier spacing, or operating in a same frequency band or belong to a same cell group. The operation (e.g., a directional collision handling procedure, a directional collision handling, a link direction collision handling, a link direction handling procedure, a link conflict handling, a downlink / uplink determination procedure, and / or the like) illustrated in FIG. 25, may be applied independently for one or more serving cells of a same frequency region / range or belonging to a same cell group (e.g., a master cell group / a secondary cell group, a first cell group / second cell group, a first coreset group / a second coreset group, and / or the like).

[0364] In an example, a wireless device may support a capability supporting receiving one or more downlink signals via one or more first serving cells while transmitting one or more uplink signals via one or more second serving cells. FIG. 22 illustrates an example signaling of the capability. The one or more first serving cells and the one or more second serving cells are configured as a carrier aggregation. The wireless device may indicate the capability for a band combination or a band. The capability may be appliedDocket No.: 24-1171 PCT for a TDD-FDD CA or a TDD-TDD CA. A capability signaling may be present in one or more signaling related to a dual connectivity (e.g., ParamtersNR-ForDC). The wireless device may indicate the capability to indicate that the wireless device supports simultaneous transmission and reception between any serving cell combinations within each cell group or across cell groups in a TDD-TDD or TDD-FDD inter-band dual connectivity.

[0365] FIG. 23 illustrates an example embodiment. A wireless device may receive one or more RRC messages indicating one or more parameters to determine which serving cells and / or how to apply directional collision handling procedure(s) across configured serving cells.

[0366] In an example, the wireless device is configured with a set of serving cells (2302). The wireless device may support simultaneous reception and transmission across a first set of serving cells (e.g., a plurality of cells 2306) and one or more remained serving cells 2308. The wireless device may receive via one or more cells of the plurality of cells 2306 while the wireless device may transmit via one or more second cells of the one or more remained serving cells, in response to supporting simultaneous reception and transmission across the plurality of cells and the one or more remained serving cells.

[0367] The wireless device may indicate support of simultaneous reception and transmission (e.g., simultaneousRxTxInterBandCA for a band combination) for one or more first frequency bands for the plurality of serving cells 2306 and one or more second frequency bands for the one or more remained serving cells 2308.

[0368] The wireless device may determine the plurality of cells 2306. In the example, the wireless device does not support simultaneous reception and transmission over the plurality of cells 2306. In response to not supporting simultaneous reception and transmission over the plurality of cells, the wireless device may receive via one or more cells of the plurality of cells at a time or transmit via one or more second cells of the plurality of cells at the time.

[0369] The wireless device may determine the plurality of cells 2303 in each frequency band, of one or more frequency bands of the set of configured serving cells 2301 , in response to the wireless device being capable of supporting simultaneous transmission and reception via the one or more frequency bands (or via the set of configured serving cells 2301). For example, if the wireless device supports simultaneous reception and transmission over three frequency bands, the wireless device may determine three sets of plurality of cells in each of the three frequency bands, where the wireless device may need to perform / operate a directional collision handling (if configured).

[0370] In an example, the wireless device may indicate supporting a directional collision handling (procedure) for a plurality of cells using a same subcarrier spacing (e.g., via a half-duplexTDD-CA- SameSCS). For example, the wireless device may indicate a parameter of half-DuplexTDD-CA-SameSCS as illustrated in FIG. 21 A for a band combination of one or more bands for the plurality of cells to indicateDocket No.: 24-1171 PCT that the wireless device supports a directional collision handling (procedure) for a plurality of cells using a same subcarrier spacing .

[0371] In an example, the plurality of cells 2306 may comprise serving cells in a same frequency band (e.g., an intra-band CA). In an example, the plurality of cells 2306 may comprise serving cells in different frequency bands where the wireless device may not support simultaneous reception and transmission capability across (e.g., inter-band CA half-duplex TDD CA).

[0372] For each set of the plurality of cells 2306, the wireless device may perform a directional collision handling procedure in response to one or more serving cells 2305 being configured with enabling directional collision handling. A directional collision handling procedure may be referred as directional collision handling, direction collision handling, a link direction collision handling, a link direction handling procedure, a link conflict handling, a downlink / uplink determination procedure, and / or the like.

[0373] In the example, the one or more serving cells comprise a first cell (CC#1) and a second cell (CC#K) in response to being configured with directional collision handling, respectively. The wireless device may perform the directional collision handling procedure for the plurality of cells 2303.

[0374] In the example, the wireless device is not configured with directional collision handling for any cell of a set of cells (e.g., the one or more remained serving cells 2308). When there is no cell of the set of cells configured with directional collision handling, the wireless device may not perform a directional collision handling procedure for the set of cells (e.g., the one or more remained serving cells 2304).

[0375] In an example, a wireless device may determine a reference cell for the plurality of cells 2306. The wireless device may determine a plurality of reference cells. In the example, each of the plurality of reference cells may be used for each set of serving cells requiring directional collision handling. In the example, 2306 is a set of serving cells requiring the directional collision handling.

[0376] Based on the capability and one or more RRC messages, a wireless device may handle a link direction or directional collision handling or collision handling over a plurality of serving cells. The wireless device may not support a simultaneous transmission and reception via the plurality of serving cells. FIG. 24 illustrates an example of the link direction or the collision handling procedure.

[0377] In an example, the plurality of serving cells may be configured with a same subcarrier spacing. In an example, the plurality of serving cells may be configured with one or more subcarrier spacings.

[0378] In an example, a wireless device may be configured with a plurality of serving cells (e.g., CC1 , CC2, and CC3), for operating / performing a directional collision handling procedure. For each serving cell of the plurality of serving cells may be configured with one or more TDD configurations (e.g., a cell-specific uplink and downlink TDD configuration such as tdd-UL-DL-ConfigurationCommon and / or UE-specific configuration such as tdd-UL-DL-ConfigurationDedicated) respectively tdd-UL-DL- Configurationcommon #1 , for a first serving cell (CC1), indicates DDDFFFUUU for where each D, F or U may be applicable to a time unit where the time unit comprises one or more slots and / or one or more symbols. TDD-UL-DL-Docket No.: 24-1171 PCTConfigurationcommon #2, for a second serving cell (CC2), indicates DFFFFFFFUU. The wireless device is configured with downlink resource overlapping with a fourth time unit / symbol / slot of the second serving cell. The wireless device is configured with a CSI-RS on the fourth time unit / symbol / slot. ‘D’ may represent downlink. may represent uplink. ‘F’ may represent flexible.

[0379] In the example, each time unit / symbol / slot may be contiguous or non-contiguous.

[0380] The wireless device receives TDD-UL-DL- Configurationcommon #3, for a third serving cell (CC3), indicates DDDDDFUUU. A second time unit of the third serving cell may be smaller than or equal to or larger than the time unit of the first serving cell and the second serving cell. In an example, a subcarrier spacing of the first cell, the second cell, and the third cell of the plurality of serving cells may be same. The wireless device is configured with uplink resource on N-th symbol / time unit / slot / time-domain resource. For example, the wireless device is configured with PUCCH resource overlapping on the N-th second symbol / time unit / slot / time-domain resource.

[0381] Example embodiments may be applicable to a slot, a time unit, a time-domain resource instead of a symbol. In an example, a symbol on a carrier / cell / serving cell may be referred as a slot on the carrier / cell / serving cell, a time unit on the carrier / cell / serving cell, or a time-domain resource on the carrier / cell / serving cell.

[0382] In an example, a wireless device may receive one or more RRC messages indicating direction collision handling (e.g., directionalCollisionHandling) being enabled for one or more cells of the plurality of serving cells The wireless device may receive the one or more RRC messages of the directional collision handling in response to indicating the wireless device is capable of supporting a directional collision handling (procedure) across multiple cells using a same subcarrier spacing. The wireless device may not be configured to monitor a group common DCI for a slot formation indication (SFI) via DCI format 2_0 for any of the plurality of serving cells.

[0383] The wireless device may perform directional collision handling in response to a first cell of the plurality of serving cells being configured / enabled to use a directional collision handling procedure (e.g., directionalCollisionHandling) and none of the plurality of serving cells being configured with a dynamic SFI (or to monitor DCI format 2_0).

[0384] The wireless device may perform directional collision handling for a symbol.

[0385] For the symbol, the wireless device may determine one or more second serving cells of the plurality of serving cells. Each of the one or more second serving cells satisfies one or more following conditions.

[0386] The symbol on a cell, of the one or more second cells, may be configured / indicated / determined as a downlink resource / symbol / slot / time / unit based on one or more TDD configurations for the cell.

[0387] In the specification, a downlink resource / symbol / slot / time unit of / on a second cell indicated via one or more TDD configurations (e.g., tdd-UL-DL-ConfigurationCommon for the second cell or the tdd-UL-DL-Docket No.: 24-1171 PCTConfigurationDedicated) for the second cell may be referred as semi-D resource / symbol / slot / time unit. In the specification, a semi-D symbol / slot / resource / time unit may be referred as a downlink symbol / slot / resource / time unit, on a second cell, by a TDD configuration, a downlink symbol / slot / resource / time unit via a tdd-UL-DL-ConfigurationCommon for the second cell, a downlink symbol / slot / resource / time unit via a tdd-UL-DL-ConfigurationCommon for the second cell or a tdd-UL-DL- ConfigurationDedicated for the second cell and / or the like. In FIG. 24, a first symbol / resource / slot / time unit of the first cell, the second cell, and the third cell are semi-D symbols / resources / slots / time units.

[0388] The symbol on the cell, of the one or more second cells, may be configured / indicated / determined as an uplink resource / symbol / slot / time / unit based on one or more TDD configurations for the cell. The one or more TDD configurations may comprise a tdd-UL-DL-ConfigurationCommon and / or a tdd-UL-DL- Configuration Dedicated.

[0389] In the specification, an uplink resource / symbol / slot / time unit of / on a second cell indicated via the one or more TDD configurations (e.g., tdd-UL-DL-ConfigurationCommon for the second cell or the tdd-UL- DL-ConfigurationDedicated) for the second cell may be referred as semi-U resource / symbol / slot / time unit. In the specification a semi-U symbol / slot / resource / time unit may be referred as an uplink symbol / slot / resource / time unit, on a second cell, by a TDD configuration, an uplink symbol / slot / resource / time unit via a tdd-UL-DL-ConfigurationCommon for the second cell, an uplink symbol / slot / resource / time unit via a tdd-UL-DL-ConfigurationCommon for the second cell or a tdd-UL-DL- ConfigurationDedicated for the second cell and / or the like. In FIG. 24, a last (eighth, 8th) symbol / resource / slot / time unit of the first cell, the second cell, and the third cell are semi-U symbols / resources / slots / time units.

[0390] The symbol on the cell may be indicated / configured / determined as an uplink symbol / slot / resource / time unit in response to / based on being configured / indicated / determined with uplink signal(s) on the symbol for the cell, via RRC signaling such as SRS, PUCCH, PUSCH or PRACH. Time resources of the uplink signal(s) overlap with the symbol or on the symbol.

[0391] In the specification, an uplink resource / symbol / slot / time unit of / on a second cell indicated / configured, via RRC signaling, to transmit uplink signals such as SRS, PUCCH, PUSCH or PRACH may be referred as a 'conf-U' symbol.

[0392] In an example, a conf-U symbol / slot / resource / time unit of / on / for a second cell may be referred as (or interchangeably used with) an uplink symbol / slot / resource / time unit, of / on / for the second cell, indicated as an uplink resource / slot / symbol / time unit via RRC signaling to transmit one or more uplink signals such as SRS, PUCCH, PUSCH or PRACH on the conf-U symbol / slot / resource / time unit. A conf-U symbol / slot / resource / time unit may be a semi-U symbol or a flexible symbol or a SBFD symbol. N-th symbol on the third carrier is a conf-U symbol in FIG. 24.Docket No.: 24-1171 PCT

[0393] The symbol may be configured / indicated / determined as a downlink resource / symbol / slot / time unit, if the wireless device is configured with downlink resources via RRC signaling such as PDCCH monitoring occasion, SPS PDSCH / PDSCH, CSI-RS resources overlapping with the symbol or on the system.

[0394] In the specification, a symbol not indicated as downlink nor uplink by one or more TDD configurations may be referred as a semi-F (semi-statically flexible, or flexible by semi-static configuration).

[0395] In the specification, a downlink resource / symbol / slot / time unit of / on a second cell indicated / configured, via RRC signaling, to receive downlink signals such as PDCCH, PDSCH, or CSI-RS may be referred as a ‘conf-D’ symbol.

[0396] A downlink signal / channel, configured by higher layers and / or via RRC signaling may comprise a PDCCH, a PDCCH monitoring occasion, a PDSCH, a SSB, a CSI-RS, and / or the like.

[0397] An uplink signal / channel, configured by higher layers and / or via RRC signaling may comprise a PUCCH, PUSCH, SRS, PRACH, a configured grant, and / or the like.

[0398] In an example, a conf-D symbol / slot / resource / time unit of / on / for a second cell may be referred as (or interchangeably used with) a downlink symbol / slot / resource / time unit, of / on / for the second cell, indicated as a downlink resource / slot / symbol / time unit via RRC signaling to receive one or more downlink signals such as PDCCH, PDSCH, CSI-RS, SSB, CORESET#0, and / or the like. A conf-D symbol / slot / resource / time unit may be a semi-D or a flexible symbol or a SBFD symbol. 4-th symbol on the second carrier is a conf-D symbol in FIG. 24.

[0399] For the symbol, the wireless device may determine a reference cell among the one or more second serving cells. A cell index of the reference may be a smallest / lowest among one or more cell indexes of the one or more second serving cells. The one or more second serving cells comprise the reference cell. In the example, the wireless device may not determine the reference cell in response to the one or more second serving cells being NULL (i.e., none of serving cells satisfy the above conditions).

[0400] In an example, a wireless device may determine a first reference cell for a first symbol, and a second reference cell for a second symbol. In the example, the first reference cell is different from the second symbol, for a plurality of cells.

[0401] FIG. 24 illustrates ‘candidate cells’ that correspond to the one or more second serving cells. For example, for the first (1st) symbol, the wireless device determines that the one or more second serving cells comprise CC1 , CC2 and CC3 based on the symbol on CC1 , CC2 and CC3 being configured / indicated / determined as a downlink symbol based on respective tdd-UL-DL- ConfigurationCommon of each cell. For the third symbol, the wireless device determines that the one or more serving cells comprise CC1 and CC3 as resource overlapping with the third symbol of CC2 is flexible (i.e., not determined as downlink or uplink). For example, the wireless device may determine zero cell for the one or more second serving cells for the M-th symbol as there is no serving cell indicated with aDocket No.: 24-1171 PCT downlink symbol or an uplink symbol (e.g., all symbols of CC1 , CC2 and CC3 overlapping with the M-th symbol are flexible symbols).

[0402] In the example, a downlink symbol on / of / for a cell may be a semi-D or a conf-U on / of / for the cell.

[0403] In the example, an uplink symbol on / of / for may be a semi-U or a conf-U on / of / for the cell.

[0404] The wireless device may determine a reference cell based on one or more cell indexes of the one or more second serving cells. The wireless device may determine the reference cell among the one or more second serving cells based on a cell index of the reference cell being a smallest / lowest among the one or more cell indexes. In the example, the wireless device determines CC1 for the first symbol, CC3 for the fifth symbol, and no reference cell for the M-th symbol.

[0405] The wireless device may determine or perform a directional collision handling procedure for / on a symbol in response to determining the reference cell. The wireless device may perform one or more steps of a directional collision handling procedure based on the reference cell. The wireless device may determine whether to communicate with a base station or skip communication via a first cell based on the reference cell in the directional collision handling procedure. When the wireless device does not determine a reference cell for / on a second symbol as the one or more second serving cell for / on the second cell is null / NULL, the wireless device may skip performing a direction collision handling procedure for / on the second symbol or may skip the steps of the directional collision handling procedure.

[0406] FIG. 25 illustrates a process 2500, performed by a wireless device, for a directional collision handling procedure across the plurality of serving cells based on determining a reference cell.

[0407] In an example, the wireless device is configured with directional collision handling for a first cell of the plurality of serving cells. As illustrated at step 2502, the wireless device may receive one or more RRC messages indicating / enabling the directional collision handling for the first cell based on a reference cell. The wireless device may be configured with directional collision handling for a reference cell of the plurality of serving cells. The wireless device may determine one or more conditions / cases as error case for a symbol (in time domain resource) and may not perform transmission or reception (e.g., skip communicating with the base station) on the symbol in response to determining an error case of the one or more conditions / cases.

[0408] For each of the plurality serving cells, the wireless device may perform embodiments in FIG. 25 respectively for the symbol. As illustrated at step 2504, the wireless device may determine whether the first cell and the reference cell operate in a same frequency.

[0409] In response to the first cell and the reference cell operating in the same frequency (e.g., step 2504 = Yes), the wireless device may check one or more conditions or perform one or more steps for an intraband CA as illustrated at step 2506.

[0410] The one or more conditions / cases / steps that the wireless device may check (e.g., in step 2506) for the first cell and the reference cell for the intra-band CA comprise the following:Docket No.: 24-1171 PCT

[0411] (1) The symbol on the reference cell is indicated as a semi-D symbol and the second symbol on the first cell is a semi-U symbol. The symbol on the reference cell is indicated as downlink via one or more TDD configurations for the reference cell and the symbol on the first cell is indicated as uplink via one or more second TDD configurations for the first cell. This case is considered as an error case. The wireless device may not communicate with the base station via the first cell if this is satisfied.

[0412] (2) The symbol on the reference cell is indicated as downlink via tdd-UL-DL-ConfigurationCommon or tdd-U L-DL-ConfigurationDedicadted for the reference cell and the wireless device receives a DCI scheduling a transmission on the symbol via the first cell. In an example, the symbol on the reference cell is indicated / configured as a conf-U symbol and the wireless device receives a DCI scheduling an uplink transmission on the symbol via the first cell. This is considered as an error case. The wireless device may not communicate with the base station via the first cell if this is satisfied.

[0413] (3) The symbol on the reference cell is indicated as downlink via RRC signaling and the wireless device receives a DCI scheduling a transmission on the symbol via the first cell. In an example, the symbol on the reference cell is indicated / configured as a conf-D symbol and the wireless device receives a DCI scheduling an uplink transmission on the symbol via the first cell. This is considered as an error case. The wireless device may not communicate with the base station via the first cell if this is satisfied.

[0414] On the other hand, in response to the reference cell and the first cell not operating in the same frequency (e.g . , operating in different frequency bands) (e.g. , step 2504 = No), the wireless device may check one or more conditions or perform one or more steps for an inter-band CA as illustrated at step 2508.

[0415] The one or more conditions / cases / steps that the wireless device may check (e.g., in step 2508) for the first cell and the reference cell for the inter-band CA comprise the following:

[0416] (1) The wireless device may assume the symbol on the reference cell and the symbol on the first cell as flexible, in response to tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated for the first cell indicates uplink (or downlink) while tdd-UL-DL-ConfigurationCommon or tdd-UL-DL- Configuration Dedicated for the reference cell indicates downlink (or uplink). In an example, the symbol on the reference cell is a semi-D symbol while the symbol on the first cell is a semi-U symbol. In an example, the symbol on the reference cell is a semi-U symbol while the symbol on the first cell is a semi-D symbol.

[0417] As a result, the wireless device may not be required (may not be expected, may not be mandated, may be allowed to skip, may skip, may drop, and / or the like) to receive PDCCH, PDSCH or CSI-RS configured via RRC signaling and may not be required (may not be expected, may not be mandated, may be allowed to skip, may skip, may drop, and / or the like) to transmit SRS, PUCCH, RUSCH or PRACH configured via RRC signaling via either of the first cell and the reference cell.

[0418] The wireless device may drop the SRS, PUCCH, PUSCH or PRACH and may not receive the PDCCH, PDSCH or CI-RS on the symbol via the first cell and / or the reference cell. In an example, the wireless device may drop uplink transmission(s) and skip receiving downlink reception(s) for a symbol, inDocket No.: 24-1171 PCT response to the symbol being configured as a semi-D (or a semi-U) on the first cell and being configured as a semi-U (or a semi-D) on the reference cell.

[0419] (2) The wireless device may transmit an uplink signal / channel (e.g ., PUSCH, Aperiodic SRS), via the first cell, scheduled on the symbol via a DCI format, where the symbol on the reference cell is indicated as downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-Configuration Dedicated for the reference cell and the first symbol and the second symbol overlap in time. In an example, the wireless device may transmit an uplink signal / channel (e.g., PUSCH, Aperiodic SRS) scheduled via a DCI during the symbol via the first cell, wherein the symbol is (indicated as) a semi-D on the reference cell.

[0420] (3) The wireless device may not be required to receive or may skip receiving the PDCCH, PDSCH, CSI-RS on the reference cell in / during a set of symbols, when the wireless device detects a DCI (format) scheduling a transmission on one or more symbols on the first cell that overlap with the set of symbols in time.

[0421] After both of step 2506 and 2506 (e.g., regardless of the intra-band CA or inter-band CA between the first cell and the reference cell), the wireless device may perform additional checking / steps at step 2510 as described below.

[0422] (1) The symbol on the reference cell is a semi-U symbol and the wireless device receives / detects a DCI (format) scheduling a reception during the symbol on / via the first cell. In an example, for a symbol, the reference cell is indicated as a semi-U symbol and the wireless device receives / detects a DCI (format) scheduling a reception on the first cell for / on the symbol.

[0423] (2) The first symbol on the reference cell is configured by higher layer signaling (e.g., RRC signaling) to transmit SRS, PUCCH, PUSCH or PRACH on a semi-statically flexible (or a semi-F) symbol (e.g., not indicated as downlink nor uplink via tdd-UL-DL-ConfigurationCommon or tdd-UL-DL- Configuration Dedicated for the reference cell) and the wireless device receives / detects a DCI (format) scheduling a reception during the symbol via the first cell. In an example, for the symbol, the reference cell is a conf-U symbol (and also flexible symbol) and the wireless device receives a DCI (format) scheduling a reception via the first cell on the symbol.

[0424] (3) The wireless device may not transmit (e.g., drop transmission) a PUCCH, PUSCH or PRACH that is configured by higher layers (e.g., via RRC signaling) on a set of symbols via the first cell, in response to at least one symbol of the set of symbols overlap with a first symbol of the reference cell and the first symbol is indicated as downlink (or a downlink symbol) via tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated for the reference cell or the first symbol corresponds to a PDCCH, PDSCH or CSI-RS resource / reception that is configured by higher layers (e.g., via RRC signaling) on the reference cell. In an example, the wireless device may drop transmission of an uplink signal (not an SRS) on a set of conf-U symbols of the first cell in response to at least one symbol of the set of conf-U symbols overlapping with a semi-D symbol or a conf-D symbol of the reference cell.Docket No.: 24-1171 PCT

[0425] (4) The wireless device may not transmit (e.g., drop transmission) a SRS that is configured by higher layers (e.g., via RRC signaling) on a set of symbols via the first cell, in response to the set of symbols overlap with one or more first symbols of the reference cell and the one or more first symbols are indicated as downlink (or a downlink symbol) via tdd-UL-DL-ConfigurationCommon or tdd-UL-DL- Configuration Dedicated for the reference cell or one or more first symbols correspond to PDCCH, PDSCH or CSI-RS resources / receptions that is configured by higher layers (e.g., via RRC signaling) on the reference cell. In an example, the wireless device may drop an SRS transmission on a set of conf-U symbols of the first cell in response to the set of conf-U symbols overlapping with one or more semi-D / conf- D symbols of the reference cell.

[0426] (5) The wireless device may not receive (e.g., skip receiving) a PDCCH, PDSCH or CSI-RS that is configured by higher layers (e.g., via RRC signaling) on a set of symbols via the first cell, in response to at least one symbol of the set of symbols overlap with a first symbol of the reference cell that are indicated as uplink (or an uplink symbol) via tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-Configuration Dedicated for the reference cell or the first symbol corresponds to a SRS, PUCCH, PUSCH, or PRACH resource / transmission that is configured by higher layers (e.g., via RRC signaling) on the reference cell. In an example, the wireless device may skip receiving on a set of conf-D symbols of the first cell, in response to at least one symbol of the set of conf-D symbols overlapping with a semi-U symbol or a conf-U symbol of the reference cell.

[0427] (6) The wireless device may assume a first symbol of the first cell as a flexible when the first symbol has been indicated as downlink or uplink via tdd-UL-DL-ConfigurationCommon or tdd-UL- DLConfigurationDedicated for the first cell in response to a second symbol, overlapping with the first symbol, of the reference cell is configured with uplink resource to transmit a SRS, PUCCH, PUSCH or PRACH or downlink resource to receive PDCCH, PDSCH or CSI-RS via higher layer signaling (e.g., RRC signaling) respectively. In an example, the wireless device may not transmit nor receive for a symbol via the first cell in response to the reference cell is configured with a conf-U symbol for the symbol. The wireless device may not receive nor transmit on a flexible symbol which is not a semi-F symbol (e.g., determined as flexible after applying slot formation indication / directional collision handling steps). The wireless device may drop both downlink reception and uplink transmission via the reference cell and the first cell if this condition is satisfied (or the wireless device assumes the symbol is flexible).

[0428] (7) The wireless device detects a DCI scheduling a transmission (or a reception) on a first symbol of a third cell of the plurality of serving cells and detects a second DCI scheduling a reception (or a transmission) of the first symbol of a fourth cell of the plurality of serving cells. The plurality of serving cells comprise the third cell and the fourth cell. The third cell may be different or equal to the reference cell or the first cell. The fourth cell may be different or equal to the reference cell or the first cell. The third cell may not be configured (or may be configured) with directional collision handling. The fourth cell may not beDocket No.: 24-1171 PCT configured (or may be configured) with directional collision handling. The wireless device may consider this case an error case. The wireless device may skip communicating with the base station if this condition is satisfied.

[0429] In an example, a wireless device may be configured with a first cell and a second cell. The wireless device may be configured with a plurality of cells, where the wireless device may not support simultaneous reception and transmission. The wireless device may perform a directional handling procedure for the plurality of cells based on one or more RRC messages. The plurality of cells may comprise the first cell and the second cell. In case, for each frequency band among one or more frequency bands of the plurality of cells, there are more than two cells, the wireless device may determine the followings for each cell of the more than two cells with a reference cell of the each frequency band.

[0430] In an example, the first cell and the second cell may operate in a same frequency. The wireless device may be configured with an intra-band CA between the first cell and the second cell. The wireless device may receive one or more RRC messages indicating at least one of the first cell and the second cell being enabled with a directional collision handling. The wireless device may perform a directional collision handling procedure described further below. In the example, the first cell corresponds to Cell#p ant the second cell corresponds to Cell#k. The second cell is the reference cell among the first cell and the second cell for a symbol (#i).

[0431] FIGs. 26A-26D illustrate cases / conditions referred in FIG. 25 step 2506. Example embodiments of FIGs. 26A-26D discuss an intra-band CA, where the Cell#k and Cell#p operate in a same frequency band. The wireless device may consider this for a plurality of cells operating in a same frequency band.

[0432] FIG. 26A illustrates an error case that the wireless device may not need to handle or may not be configured with. The wireless device may determine an error in response to the symbol on the first cell being indicated as a downlink symbol (e.g ., a semi-D symbol), via one or more TDD configurations, for the first cell and the symbol on the second cell (reference cell) being indicated as an uplink symbol (e.g., a semi-U symbol), via one or more second TDD configurations, for the second / reference cell.

[0433] FIG. 26B illustrates an error case that the wireless device may not need to handle or may not be configured with. The wireless device may determine an error in response to the symbol on the first cell being indicated as an uplink symbol (e.g , a semi-U symbol), via one or more TDD configurations, for the first cell and the symbol on the second cell (reference cell) being indicated as a downlink symbol (e.g., a semi-D symbol), via one or more second TDD configurations, for the second / reference cell.

[0434] FIG. 26C illustrates an example of an error case. In an example, the wireless device may not receive nor transmit via the first cell and the second cell on the symbol in such a case. In an example, the wireless device may receive or transmit up to implementation. The behavior of the wireless device may be up to the implementation. A base station may not schedule or configure the error case.Docket No.: 24-1171 PCT

[0435] In the example, the one or more second TDD configurations may comprise a tdd-UL-DL- ConfigurationCommon or a tdd-UL-DL-ConfigurationDedicated for the second / reference cell. The one or more TDD configurations may comprise a tdd-UL-DL-ConfigurationCommon or a tdd-UL-DL- ConfigurationDedicated for the first cell.

[0436] FIG. 26D shows a similar case to FIG. 26C. In the example, the base station may configure one or more downlink signals such as PDCCH, PDSCH, or CSI-RS overlapping on / via / during the symbol for the second / reference cell. Based on the symbol on the reference cell being a conf-D symbol and the symbol on the first cell being uplink, the wireless device may consider this case as an error ase. The base station may schedule an uplink grant during the symbol for the first cell. For example, the uplink grant may schedule an uplink signal such as SRS, PUSCH, and / or the like.

[0437] A base station may not schedule / configure any case illustrated in FIG. 26A / B / C / D across cells operating in a same frequency band. In an example, a wireless device may determine / apply a link direction between a cell of a plurality of cells and a reference cell. In the example, the plurality of cells may comprise one or more cells operating in a same frequency band (e.g., intra-band CA cells).

[0438] In an example, a cell operate in a frequency band in response to frequency range of the cell belongs to frequency range of the frequency band. In another example, a cell operates in a frequency band in response to a case where a center frequency or a frequency of cell-defining SSB of the cell may belong to one of channel raster of the frequency band. The cell operates in a frequency band may be referred as the cell of a frequency band or the cell is configured in a frequency band A first serving cell and a second serving cell operates in a same frequency band in response to each frequency band of the first serving cell and the second serving cell is same. A first serving cell and a second serving cell operates in different frequency bands in response to each frequency band of the first serving cell and the second serving cell is not same.

[0439] In an example, the first cell and the second cell may operate in different frequency bands (e.g., inter-band CA). Example embodiments illustrated on FIGs. 27A - 27D discuss a few directional collision cases and how a wireless device handles the cases for the inter-band CA. The cases may correspond to inter-band CA procedure as in FIG. 25 step 2508. In FIG. 27, the Cell#k and Cell#p operate in different frequency bands

[0440] FIG. 27A discusses a similar case to FIG. 26A. The wireless device, different from the intra-band CA case where the case is considered as an error case, may skip, on the symbol, receiving downlink signal(s) via the first cell and drop transmitting uplink signal(s) via the second / reference cell. In the example, the reference cell and the first cell operate in different frequency bands. The wireless device may consider the symbol on the first cell and the second cell as flexible, in response to the symbol on the first cell being indicated as a downlink symbol (e.g., a semi-D symbol) via the one or more TDD configurationsDocket No.: 24-1171 PCT for first cell and the second cell (reference cell) being indicated as an uplink symbol (e.g., a semi-U symbol) via the one or more second TDD configurations.

[0441] The wireless device may not be required to receive higher layer configured (e.g., via RRC signaling, MAC CE) PDCCH, PDSCH or CSI-RS on / during the symbol via the first cell, based on considering the symbol on the first cell being flexible. This may not comprise one or more PDSCHs, CSI- RSs, potentially PDCCHs that are scheduled via dynamic DCI / PDCCH / PDCCH format. The wireless device may not be required to transmit higher layer configured (e.g., via RRC signaling, MAC CE) SRS, PUCCH, RUSCH or PRACH on the symbol via the second / reference cell, based on considering the symbol on the second / reference cell being flexible.

[0442] FIG. 27B discusses a similar case to FIG. 27A except that the symbol on the first cell is a semi-D symbol and the symbol on the second / reference cell is a semi-U symbol. The wireless device, different from intra-band CA case of FIG.26B where the case is considered as an error case, may skip receiving or transmitting on the symbol. The wireless device may consider the symbol on the first cell and the second cell as flexible, in response to the symbol on the first cell being indicated as a downlink symbol (e.g., a semi-D symbol) via the one or more TDD configurations for first cell and the second cell (reference cell) being indicated as an uplink symbol (e.g., a semi-U symbol) via the one or more second TDD configurations.

[0443] The wireless device may skip one or more configured downlink or uplink signals on a symbol considered as flexible via a cell.

[0444] FIG. 27C discusses a similar case to FIG. 26C. The wireless device, different from intra-band CA case where the case is considered as an error case, may transmit uplink signal(s), scheduled via the uplink (UL) grant such as via a DCI, PDCCH format, PDCCH and / or the like, via the first cell in case of the interband CA between the reference cell and the first cell on the symbol (Cell#p) . In the example, the wireless device may skip receiving during the symbol via the second / reference cell.

[0445] FIG. 27D illustrates another case of a directional collision for an inter-band CA. The wireless device may receive one or more RRC messages indicating / configuring a downlink signal on a set of contiguous, in time, symbols (symbol #i, #j, and #k). In the example, the set of symbols may be indicated as a set of semi- statically flexible symbols (e.g., semi-F symbols). The wireless device may determine the set of semi- statically flexible symbols based on the one or more second TDD configurations if provided (e.g., semi- statically flexible symbols comprise a symbol that is not a semi-D symbol nor a semi-U symbol) or all symbols if such configuration is not provided.

[0446] For example, the set of contiguous symbols are a set of conf-D symbols with a downlink signal and the set of contiguous symbols are a set of semi-F symbols. For example, a PDCCH monitoring occasion, via the second / reference cell, is configured on the set of symbols. For example, a SPS PDSCH is scheduled on the set of symbols via the second / reference cell.Docket No.: 24-1171 PCT

[0447] The wireless device may receive a DCI format (or a PDCCH) scheduling an UL signal on one or more symbols. In the example, the one or more symbols may overlap with the set of symbols in time. In response to the overlapping, the wireless device may skip receiving the downlink signal during the set of symbols via the second / reference cell. The wireless device may transmit the uplink signal via the first cell during the one more symbols.

[0448] In FIG. 27D, the wireless device receives an UL grant scheduling an uplink signal on a symbol #j. In response to the symbol #j overlapping with the set of conf-D symbols (#i, #j, and #k) in time, the wireless device skips receiving a downlink signal over the set of symbols and the wireless device transmits the uplink signal during the symbol #j via the first cell. In the example, the downlink signal may be a DCI, a PDCCH a PDCCH, a PDSCH or a CSI-RS.

[0449] Regardless of intra-band CA or inter-band CA between the first cell and the second / reference cell, the wireless device may apply one or more of embodiments described below. This step is per 2506 of FIG. 25. The wireless device may determine one or more cases illustrated in FIGs. 28A-28D and FIGs. 29A- 29C. In the example, the first cell and the reference cell may operate in a same frequency band or different frequency bands

[0450] In an example, the wireless device may consider a case shown in FIG. 28A as an error case. The symbol #i on the second / reference cell is indicated as a semi-U symbol and the symbol #i on the first cell is scheduled with a downlink signal via one or more DCIs / DCI formats / PDCCHs.

[0451] The downlink signal may comprise a PDCCH, a PDCCH monitoring occasion, PDSCH, CSI-RS, SSB, and / or the like.

[0452] FIG. 28B shows a similar case to FIG. 27A except that the wireless device is configured with uplink signal(s) during the symbol #i via the reference / second cell (e.g., the symbol #i is a conf-U symbol) and the symbol #i on the second / reference cell is a semi-F symbol. The wireless device may handle this case similar to that of FIG. 28B.

[0453] The uplink signal(s) may comprise one or more of SRS, PUCCH, PUSCH or PRACH.

[0454] In an example, the wireless device may consider an error for a symbol in response to receiving a DCI scheduling a downlink signal during the symbol via the first cell and the symbol on the second / reference cell being a semi-F symbol and a conf-U symbol.

[0455] In an example, as shown in FIG. 28C, the wireless device may skip / drop transmission of an uplink signal / channel (e.g., PUCCH, PUSCH or PRACH) if the following conditions are satisfied. The wireless device may receive one or more RRC messages indicating the uplink signal / channel on a set of (contiguous) symbols (e.g., symbol #j, #j, and #k) for the first cell. The wireless device may receive the one or more second TDD configurations for the second / reference cell that indicate one or more symbols (e g., a symbol #j in FIG. 28C) as downlink (e.g., semi-D symbols) and the one or more symbols overlap with the set of symbols in time.Docket No.: 24-1171 PCT

[0456] FIG. 28D illustrates a similar case except that an overlapping symbol on the second / reference cell is a conf-D symbol instead of a semi-D symbol. The wireless device may skip the uplink signal / channel in response to the set of symbols overlapping, in time, with one or more second conf-D symbols (e.g., a symbol #k in FIG. 28D) on the second / reference cell. The wireless device may receive one or more RRC messages indicating / configuring a downlink signals / channel during the one or more second symbols via the second / reference cell (e.g., conf-D symbols). The uplink signal may be / comprise a PUCCH, a PUSCH or a PRACH.

[0457] In an example, the wireless device may receive one or more RRC messages config u ring / indicati ng one or more SRS configurations for the first cell. The wireless device may drop a SRS, of a SRS configuration of the one or more SRS configurations, on a set of symbols on the first cell in response to the set of symbols being indicated as downlink (e.g., semi-D symbol(s)) by the one or more second TDD configurations (as shown in FIG. 29A symbol #j, #k) or the set of symbols (e.g., conf-D symbol(s)) correspond to a downlink reception (e.g. a PDCCH, PDSCH or a CSI-RS) configured via one or more RRC messages (as shown in FIG. 29A symbol #i). The wireless device may receive one or more downlink symbols during the set of symbols via the second / reference cell.

[0458] In an example, the wireless device may skip monitoring / receiving a downlink signal / channel on a set of symbols on the first cell, in response to at least one symbol from the set of symbols being indicated as an uplink symbol (e.g., semi-U symbol) by the one or more second TDD configurations for the second / reference cell (as shown in FIG. 29B symbol #j).

[0459] In an example, the wireless device may skip monitoring / receiving a downlink signal / channel on a set of symbols on the first cell, in response to at least one symbol from the set of symbols corresponding to (e.g., overlapping in time with) an uplink transmission (e.g., a SRS, PUCCH, PUSCH or PRACH transmission) that is configured for the second / reference cell via one or more RRC signaling (as shown in FIG 29C symbol #j). The wireless device may transmit the uplink transmission during the at least one symbol via the second / reference cell.

[0460] The wireless device may consider a semi-D (or a semi-U) symbol of the first cell to be flexible (e.g., no transmit nor receive via the symbol for the first cell) in response the semi-D (or the semi-U) symbol of the first cell overlapping in time with a conf-U symbol (or a conf-D symbol) of the second / reference cell

[0461] For each pair of {a first serving cell, a second serving cell} of the plurality of cells and a second serving cell of the plurality of serving cells, regardless of the reference cell, the wireless device may not be required to handle a case where the wireless device receives a first DCI scheduling a transmission on a symbol on the first serving cell and a second DCI scheduling a reception on the symbol on the second cell respectively. A base station may not schedule a downlink signal, during a symbol, via a first cell of the plurality of cells, and schedule an uplink signal, during the symbol, via a second cell of the plurality of cells.Docket No.: 24-1171 PCT

[0462] In existing technologies, as illustrated in FIG. 30, a wireless device may determine a reference cell, if enabled to use a directional collision handling, among a plurality of cells for a symbol. For example, the reference cell may be a lowest indexed cell among one or more cells of the plurality of cells. The one or more cells may comprise a cell indicated with a downlink symbol (e.g., a semi-D or a conf-D symbol) or an uplink symbol (e.g., a semi-U or a conf-D symbol) on the symbol via one or more SIB and / or RRC messages. Based on the reference cell, the wireless device may determine whether to transmit or receive or drop scheduled / configured downlink / uplink signal / channel, on the symbol, via a first cell of the plurality of cells.

[0463] In an example, the plurality of cells may comprise a first cell (e.g., Cell#1 in FIG. 30) and a second cell (Cell#0 in FIG. 30). In the example, the first cell and the second cell may operate in a same frequency band. The plurality of cells may comprise more than one serving cells of an intra-band CA case. The wireless device may not support simultaneous reception and transmission across / via the first cell and the second cell of the same frequency band.

[0464] In an example, the wireless device may be configured / indicated / enabled with a SBFD operation on the first cell (e.g., Cell#1 in FIG. 30). For example, a symbol #1 and a symbol #2 of the first cell are configured as SBFD symbols on the first cell. Based on the SBFD operation, a base station may schedule / configure uplink transmission(s) on the symbol #1 and / or the symbol #2 via the first cell. In the example, the symbol #1 and the symbol #2 may be configured as downlink via one or more TDD configurations for the first cell The symbol #1 and symbol #2 on the first cell are semi-D symbols. The base station may schedule / configure downlink transmission(s) on the symbol #1 and / or the symbol #2 via the first cell.

[0465] Based on the existing mechanisms, the wireless device may determine the second cell (Cell#0) as a reference cell for a set of symbols shown in FIG. 30 based on the second cell having a smaller cell index (e.g , 0, zero) than the first cell (e.g., 1 , one).

[0466] The wireless device may receive one or more RRC signaling / messages configuring / indicating one or more uplink signals / channels via the first cell. For example, the wireless device is configured with one or more PUCCH resources on a symbol #2 and a symbol #4 for the first cell.

[0467] The wireless device may receive one or more DCI formats or PDCCHs scheduling one or more uplink signals (e.g., one or more UL grants). For example, the wireless device receives an UL grant (via a DCI format or a PDCCH) scheduling a PUSCH on a symbol #1 for the first cell.

[0468] One or more second TDD configurations for second cell may indicate that a symbol #1 , a symbol #2 and a symbol #4 as downlink symbols (e.g., semi-D symbols).

[0469] The wireless device may perform a directional collision handling procedure as illustrated in FIGs. 25-29.Docket No.: 24-1171 PCT

[0470] In existing technologies, the wireless device may not transmit the PUSCH (3001 ) during the symbol #1 (e.g., FIG. 26C). The wireless device may drop a PUCCH (3002) of the one or more PUCCH resources during the symbol #2 (e.g., FIG. 28C). The wireless device may not transmit a second PUCCH (3003) of the one or more PUCCH resources during the symbol #4 (e.g., FIG. 26B).

[0471] Based on existing technologies, the wireless device may drop one or more uplink transmissions scheduled via one or more RRC signaling and / or via one or more DCIs during one or more SBFD symbols via a cell of a plurality of cells, in response to the one or more SBFD symbols overlapping with one or more semi-D symbols of a reference cell. In an example, the wireless device may consider the case (e.g., a collision between a semi-D and a dynamically scheduled UL transmission) as an error case. This may reduce a flexibility for a base station to schedule an uplink transmission during a SBFD symbol of the cell, in particular in an intra-band CA.

[0472] This may degrade performance of a wireless device, enabled with a SBFD operation, while requiring increased complexity of the wireless device to support the SBFD operation. Potential performance loss may become more significant in an intra-band CA case. For example, one or more cells of the intra- band CA cells are configured / enabled with a SBFD operation. Based on a half-duplex capability (e.g., not supporting simultaneous reception and transmission) via the intra-band CA cells, the base station may be limited in utilizing SBFD symbols on the one or more cells. For example, when a primary cell of the intra- band CA cells is not enabled with a SBFD operation and a TDD configuration is given for the primary cell, the base station and the wireless device may follow the TDD configuration of the primary cell in determining link directions for the one or more cells. The base station may not be able to schedule / configure an uplink transmission via a SBFD symbol in such a case. This may considerably reduce flexibility of the SBFD symbols / the SBFD operation.

[0473] In existing technologies, a wireless device may drop one or more scheduled / configured uplink transmission via a cell of a plurality of serving cells. In the example, the cell may be enabled with a SBFD operation. Based on the SBFD operation, a base station may schedule / configure the one or more scheduled / configured uplink transmissions during a set of SBFD symbols that are semi-D symbol(s) and / or semi-F symbol(s). In response to the set of SBFD symbols overlapping with downlink symbols (e.g., semi-D symbols) of a reference cell, the wireless device may drop the one or more scheduled / configured uplink transmissions during the set of SBFD symbols.

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

[0475] In an example embodiment, as illustrated in FIG. 31 , a wireless device may receive one or more downlink control signals / commands. The one or more downlink control signals / commands may indicate / enable a first cell (CC1) to use a directional collision handling based on a reference cell. The one or more downlink control signals / commands may schedule / configure / indicate an uplink signal / transmissionDocket No.: 24-1171 PCT via a symbol on the first cell. The one or more downlink control signals / commands may indicate / configure a downlink resource of a second cell during the symbol. The second cell may be a first reference cell for the symbol. The one or more downlink signals / commands may be one or more RRC messages, one or more MAC CEs, one or more DCIs, or a combination of thereof.

[0476] In response to the symbol on the first cell being a SBFD symbol, the wireless device may transmit the uplink signal / transmission during symbol via the first cell.

[0477] Example embodiments may allow a base station to flexibly schedule / configure uplink resources of a first cell on a SBFD symbol, overlapping with a downlink symbol of a reference cell. Example embodiments may enable a wireless device to transmit uplink signals via a SBFD enabled cell during a symbol that overlaps with a downlink symbol of the reference cell.

[0478] Example embodiments may solve the problem and allow that a SBFD operation may be supported flexibly / efficiently and allow a wireless device to transmit scheduled UL transmissions via a symbol in response to the symbol being a SBFD symbol. This improves the uplink capacity of the wireless device. Example embodiments may enable a wireless device to transmit uplink signals via a SBFD enabled cell without requiring a capability of simultaneous reception and transmission across the SBFD enabled cell and a reference cell. For example, a base station may schedule downlink or uplink via a plurality of serving cells based on a link direction of a cell of the plurality of serving cells, wherein the cell is enabled / configured / indicated with a SBFD operation.

[0479] In FIG 31 , the one or more downlink control commands / signal may schedule an uplink transmission during a symbol #1 via the first cell (Cell#1). The one or more downlink control commands / signals may indicate the symbol #1 on the second cell (Cell#0) as a downlink symbol. In response to the symbol #i on the first cell being a SBFD symbol, the wireless device transmits the uplink transmission during the symbol #i via the first cell.

[0480] In the example, the wireless device may receive one or more RRC messages indicating / comprising / configuring one or more PUCCH resources. One resource of the one or more PUCCH resources may overlap in time on a symbol #4. The symbol #4 on the second cell (Cell#0) is a downlink symbol. In response to the symbol #4 on the first cell not being a SBFD symbol, the wireless device may drop a PUCCH of the one or more PUCCH resources during the symbol #4 via the first cell.

[0481] In the example, the wireless device may determine whether the symbol overlaps with the SBFD symbol of the first cell. In response to the determining, the wireless device may determine to transmit the uplink signal / transmission via the symbol on the first cell.

[0482] In an example, the second cell may be a second reference cell, of the first cell, for a second symbol. The wireless device may receive one or more RRC messages indicating a second uplink signal / transmission via the second symbol on the first cell and a second downlink resource of the second cell during the second symbol. The wireless device may drop the second uplink signal / transmission inDocket No.: 24-1171 PCT response to the second symbol on the first cell not being a SBFD symbol. The wireless device may (determine to) drop the second uplink signal / transmission in response to / based on the second symbol on the first cell not being a SBFD symbol.

[0483] In an example, the wireless device may (determine to) drop the second uplink signal / transmission, in response to none of the plurality of cells being a SBFD symbol during / for the second symbol. In an example, the wireless device may determine an error case for the second uplink signal / transmission, in response to none of the plurality of cells being a SBFD symbol during / for the second symbol.

[0484] In the example, a base station may not schedule one or more DCIs scheduling the second uplink transmission via the second symbol on the first cell and transmitting the one or more RRC messages indicating the second downlink resource of the second cell during the second symbol. The wireless device may not be required to handling such a case if occurred. The wireless device may consider such a case as an error case. The behavior of the wireless device in handling an error case may be up to the implementation.

[0485] In the example, the wireless device may not be required to process / handle a case that the wireless device receives the one or more DCIs scheduling the second uplink transmission via the first cell and receives the one or more RRC messages indicating the downlink resource of the second cell during the second symbol.

[0486] In an example, the one or more downlink control commands / signals may be transmitted via one or more RRC signaling / messages, MAC CEs, PDCCHs, DCIs, DCI formats or a combination thereof.

[0487] The wireless device may skip / avoid / drop receiving downlink data via the downlink resource in response to transmitting the uplink signal / transmission via the first cell, using / based on / in response to the directional collision handling.

[0488] In an example, the first cell and the second cell may operate in a same frequency band or different frequency bands

[0489] In an example, a first subcarrier spacing of the first cell may be same as a second subcarrier spacing of the second cell.

[0490] In an example, the one or more downlink control commands / signals may further indicate to enable a directional collision handling based on the reference cell for the second cell.

[0491] In an example, the wireless device may receive one or more RRC messages indicating / comprising one or more SBFD configuration parameters for the first cell. The one or more SBFD configuration parameters may comprise / indicate a set of SBFD symbols of the first cell. The one or more SBFD configuration parameters may comprise / indicate one or more DL subbands and / or one or more UL subbands.Docket No.: 24-1171 PCT

[0492] The symbol on the first cell is the SBFD symbol in response to the symbol overlapping in time with a first SBFD symbol of the set of SBFD symbols of the first cell. A SBFD symbol of the first cell may refer the first SBFD symbol of the set of SBFD symbols of the first cell.

[0493] The first SBFD symbol of the first cell may be determined that a first symbol, on / via the first cell, to operate a SBFD operation or to apply the one or more DL subbands and the one or more UL subbands during the symbol on the first cell.

[0494] In an example, one or more RRC messages (e.g., via one or more TDD configurations, a tdd-UL- DL-ConfigurationCommon and / or a tdd-UL-DL-ConfigurationDedicated) for the first cell may indicate / configure a downlink symbol or a flexible symbol that overlaps with the SBFD symbol of the first cell.

[0495] In the example, the uplink signal / transmission may comprise a RUSCH, PUCCH, PRACH, SRS, or a combination thereof.

[0496] In the example, the wireless device may receive a DCI format scheduling the uplink signal / transmission for the second cell.

[0497] In the example, the wireless device may receive one or more RRC messages configuring / indicating to transmit the uplink signal / transmission (e.g., PUCCH, PUSCH, PRACH, SRS) via / on the symbol on / via the first cell.

[0498] In the example, the wireless device may receive one or more RRC messages configuring / indicating to receive one or more downlink signals (e g., CSI-RS, PDCCH, PDSCH) on the downlink resource of the second cell on the symbol.

[0499] In the example, a first cell index of the second cell may be smaller (or larger) than a second cell index of the first cell.

[0500] In the example, a first frequency band of the first cell and a second frequency band of the second cell may be same or different.

[0501] In the example, a first subcarrier spacing used for the first cell may be same as a second subcarrier spacing used for the second cell.

[0502] In the example, the wireless device may receive one or more second RRC messages comprising one or more second TDD configurations (e.g., a tdd-UL-DL-ConfigurationCommon) for the second cell that indicate a downlink symbol on the symbol.

[0503] In an example, the wireless device may (determine to) transmit the uplink signal / transmission via the symbol on the first cell in response to: the symbol on the first cell being the SBFD symbol; receiving a DCI format scheduling the uplink signal / transmission; and receiving one or more SIBs or RRC messages indicating the symbol on the second cell being a downlink symbol.Docket No.: 24-1171 PCT

[0504] In an example, the wireless device may (determine to) transmit the uplink signal / transmission via the symbol on the first cell in response to the symbol on the first cell being the SBFD symbol; receiving a DCI format scheduling the uplink signal / transmission; and receiving one or more RRC messages scheduling one or more downlink signals during the symbol via the second cell.

[0505] In the example, the wireless device may (determine to) drop a second uplink signal / transmission via a second symbol on the first cell, in response to the second symbol on the second cell being a second downlink symbol and the second symbol on the first cell not being a SBFD symbol.

[0506] In an example, the wireless device may receive one or more second downlink control commands / signals indicating: a reception of a downlink signal via a third symbol on the first cell; and an uplink resource of the second cell during the third symbol.The second cell may be a third reference cell of the first cell, for the third symbol.In response to the third symbol on the first cell being a second SBFD symbol, the wireless device may receive the downlink signal during the third symbol via the first cell. The wireless device may skip transmitting during the third symbol via the first cell.

[0507] In the example, the wireless device may receive a second DCI format scheduling the reception of the downlink signal.

[0508] In the example, the wireless device may receive one or more RRC messages configuring an uplink signal (e.g. , SRS, PUCCH, RUSCH, or PRACH) via the uplink resource.

[0509] In the specification, "a wireless device may not expect to” may refer "a wireless device may not be required to handle a case corresponding to” or "a base station may not configure a wireless device to”.

[0510] A symbol of a cell, in determining a directional collision handling procedure, may be categorized as a semi-D, a semi-U, a conf-U, a conf-D, or a SBFD symbol.

[0511] A semi-D symbol of a cell may be determined as a symbol indicated as a downlink symbol by a tdd-UL-DL-ConfigurationCommon (and / or a tdd-UL-DL-ConfigurationDedicated) for the cell, and not being indicated as a SBFD symbol by one or more SBFD configuration parameters for the cell, and not being configured with one or more downlink signal(s) (e.g., PDCCH, PDSCH, CSI-RS) on the symbol by one or more RRC / SIB signaling / messages.

[0512] A semi-U symbol of a cell may be determined as a symbol indicated as an uplink symbol by a tdd- UL-DL-ConfigurationCommon (and / or a tdd-UL-DL-Configuration Dedicated) for the cell, and not being indicated as a SBFD symbol by one or more SBFD configuration parameters for the cell, and not being configured with one or more uplink signal(s) (e.g., PUCCH, PUSCH, SRS, PRACH) on the symbol by one or more RRC / SIB signaling / messages.

[0513] A conf-D symbol of a cell may be determined as a symbol that is configured with one or more downlink signal(s) (e.g., PDCCH, PDSCH, CSI-RS) on the symbol by one or more RRC / SIB signaling / messages. A conf-D symbol may be indicated as a semi-D or a semi-F by one or more TDDDocket No.: 24-1171 PCT configurations if any for the cell. A conf-D symbol may be indicated as a SBFD symbol via one or more SBFD configuration parameters.

[0514] A conf-U symbol of a cell may be determined as a symbol that is configured with one or more uplink signal(s) (e.g., PUCCH, PUSCH, SRS, PRACH) on the symbol by one or more RRC / SIB signaling / messages. A conf-U symbol may be indicated as a semi-U or a semi-F by one or more TDD configurations if any for the cell. A conf-U symbol may be indicated as a SBFD symbol via one or more SBFD configuration parameters.

[0515] A symbol may be configured via one or more RRC / SIBs with downlink / uplink resource(s) to be as a conf-D or a conf-U symbol.

[0516] A conf-D symbol may be a semi-D or a SBFD symbol or a semi-F symbol.

[0517] A conf-U symbol may be a semi-D or a SBFD symbol or a semi-F symbol.

[0518] A symbol that is a semi-D symbol and a conf-D symbol may be referred as a conf-D symbol.

[0519] A symbol that is a semi-U symbol and a conf-U symbol may be referred as a conf-U symbol.

[0520] A symbol that is a semi-F symbol and a conf-D symbol may be referred as a conf-D symbol.

[0521] A symbol that is a semi-F symbol and a conf-U symbol may be referred as a conf-U symbol.

[0522] A symbol that is a SBFD symbol and a conf-D symbol may be referred as a conf-D symbol.

[0523] A symbol that is a SBFD symbol and a conf-U symbol may be referred as a conf-U symbol.

[0524] A symbol that is a semi-D symbol and a SBFD symbol may be referred as a SBFD symbol.

[0525] A symbol that is a semi-F symbol and a SBFD symbol may be referred as a SBFD symbol.

[0526] A slot format of a symbol may be one of a semi-D symbol, a semi-U symbol, a flexible symbol, a semi-F, or a SBFD symbol. The wireless device may receive on the semi-D symbol. The wireless device may transmit during the semi-U symbol. The wireless device may not receive nor transmit on the flexible symbol. The wireless device may receive or transmit on the SBFD symbol.

[0527] In an example, a wireless device may be configured with a plurality of serving cells. The wireless device may be enabled with a directional collision handling, based on a reference cell, via the plurality of serving cells. The wireless device may determine a reference cell (Cell#k in FIGs. 32-40) for a symbol (#i in FIGs. 32-40). The wireless device may communicate with a base station or skip communication during the symbol for a first cell (Cell#p in FIG. 32-40), of the plurality of serving cells, based on the reference cell. The wireless device may determine whether to communicate with a base station or skip communication during the symbol for a first cell (Cell#p in FIG. 32-40), of the plurality of serving cells, based on the reference cell.

[0528] 'D / S' in FIG. 32-40 may represent a symbol that was a semi-D and becomes a SBFD symbol. ‘U / S’ in FIG. 32-40 may represent a symbol that was a semi-U symbol and becomes a SBFD symbol. ‘D / S' in FIG. 32-40 may represent a symbol that is a semi-D and is a SBFD symbol. ‘U / S’ in FIG. 32-40 may represent a symbol that is a semi-U symbol and is a SBFD symbol. ‘D / S’ or ‘U / S’ represents a SBFDDocket No.: 24-1171 PCT symbol. ‘D / S’ symbol may be indicated as downlink by a tdd-UL-DL-ConfigurationCommon and indicated as a SBFD symbol by one or more SBFD configuration parameters (e.g., SBFD-ConfigurationCommon). ‘U / S’ symbol may be indicated as uplink by a tdd-UL-DL-ConfigurationCommon and indicated as a SBFD symbol by one or more SBFD configuration parameters (e.g., SBFD-ConfigurationCommon).

[0529] In an example, the wireless device may determine the symbol on the first cell being a SBFD symbol (e.g., Case A in FIG. 32). Based on the determining, the wireless device may transmit, if scheduled / configured, an UL signal via / during the symbol on / via the first cell.

[0530] In an example, the wireless device may determine the symbol on the reference cell being a SBFD symbol (e.g., Case B in FIG. 32). Based on the determining, the wireless device may transmit, if scheduled / configured, an UL signal via / during the symbol on / via the reference cell.

[0531] When the symbol on the reference cell and the first cell are not SBFD symbol (e.g., neither Case A or Case B in FIG. 32), the wireless device may perform a directional collision handling as shown in FIGs. 25-29.

[0532] In an example, the reference cell and the first cell may operate in a same frequency band.

[0533] FIG. 33 and FIG. 34 discuss example embodiments for the case where the reference cell and the first cell operate in the same frequency band.

[0534] The wireless device may be configured with an intra-band CA between the reference cell and the first cell. The reference cell (e.g., a first cell, Cell#k) and the first cell (e.g., a second cell, Cell#p) may be contiguous (e.g., intra-band contiguous CA) or non-contiguous (e.g., intra-band non-contiguous CA) in frequency domain. The wireless device may receive one or more RRC messages indicating / comprising one or more configuration parameters enabling a directional collision handling for the first cell, for the reference cell or for both the first cell and the reference cell. The wireless device may be configured with a plurality of cells comprising the first cell and the reference cell. The wireless device may perform the directional collision handling via the plurality of cells.

[0535] In an example, FIG. 33A illustrates a similar configuration to FIG. 26A. For example, a symbol #i on the reference cell is indicated as a semi-U symbol and the symbol #i on the first cell is indicated as a semi- D symbol.

[0536] One or more SBFD configuration parameters of the first cell may indicate the symbol #i as a SBFD symbol. Based on the one or more SBFD configuration parameters, the wireless device may determine the symbol #i on the first cell being the SBFD symbol. Different from, FIG. 26A, the wireless device may consider this case as a normal case (e.g., no error case).

[0537] The wireless device may (determine to) transmit one or more uplink signals / transmissions / channels on / du ring the symbol #i via / on the first cell on the case of FIG. 33A, based on / in response to the symbol # being the SBFD symbol and the symbol #i on the reference cell being an uplink symbol. For example, the wireless device may transmit the one or more uplinkDocket No.: 24-1171 PCT signals / transmissions / channels on the symbol #i via one or more UL subbands of the first cell. The wireless device may receive one or more RRC messages and / or DCIs scheduling / configuring the one or more uplink signals / transmissions / channels.

[0538] In an example, the wireless device may skip receiving one or more downlink signals / transmissions / channels during the symbol #i via the first cell, in response to the symbol # being the SBFD symbol and the symbol #i on the reference cell being an uplink symbol.

[0539] In an example, if the first cell configured with a directionalHandlingCollision operates in the same frequency band as the reference cell, the wireless device does not expect (or is not required to handle a case where) a symbol to be indicated as uplink on the reference cell and downlink but not a SBFD symbol on the first cell respectively by a tdd-UL-DL-ConfigurationCommon or by a tdd-UL-DL- ConfigurationDedicated and / or a SBFD-ConfigurationCommon.

[0540] The wireless device may transmit a higher layer configured PUCCH, PUSCH, SRS, or PRACH on a symbol or a transmission scheduled by a DCI format on the symbol on the first cell, if the symbol on the reference cell is indicated as uplink by a tdd-UL-DL-ConfigurationCommon or by a tdd-UL-DL- ConfigurationDedicated and the symbol on the first cell is a SBFD symbol by a SBFD- Configuration Common.

[0541] The wireless device may not be required to receive a higher layer configured PDCCH, PDSCH, or CSI-RS on the symbol on the first cell, if the symbol on the reference cell is indicated as uplink by a tdd-UL- DL-ConfigurationCommon or by a tdd-UL-DL-ConfigurationDedicated and the symbol on the first cell is a SBFD symbol by a SBFD-ConfigurationCommon.

[0542] In an example, FIG. 33B illustrates a similar configuration to FIG. 26A For example, a symbol #i on the reference cell is indicated as a semi-U symbol and the symbol #i on the first cell is indicated as a semi- D symbol.

[0543] One or more SBFD configuration parameters of the reference cell may indicate the symbol #i as a SBFD symbol. Based on the one or more SBFD configuration parameters, the wireless device may determine the symbol #i on the reference cell being the SBFD symbol. This case may be considered as an error case. The wireless device may not expect (or may not be required to handle a case where) a semi-U symbol is indicated as a SBFD symbol. The wireless device may not communicate with the base station via the first cell and / or the reference cell during the symbol.

[0544] FIG. 33C illustrates a similar configuration to FIG. 26B. The symbol #i on the reference cell is a semi-D symbol and the symbol #i on the first cell is a semi-U symbol. In the example, the symbol #i on the first cell is a SBFD symbol. This case is considered as an error as the SBFD symbol is indicated on a semi- U symbol of the first cell. The wireless device may not communicate with the base station via the first cell and / or the reference cell during the symbol.Docket No.: 24-1171 PCT

[0545] FIG. 33D illustrates a similar configuration to FIG. 33C except that the symbol #i on the reference cell is a SBFD symbol and the symbol #i on the first cell is a semi-U symbol. Based on determining the symbol #i on the reference cell being the SBFD symbol, the wireless device may transmit one or more uplink signals / transmissions / channels during the symbol #i via the reference cell. The wireless device may determine to transmit one or more uplink signals / transmissions / channels during the symbol #i via and the reference cell.

[0546] In an example, if the first cell configured with a directionalHandlingCollision operates in the same frequency band as the reference cell, the wireless device does not expect a symbol to be indicated as downlink but not a SBFD symbol on the reference cell and uplink on the first cell respectively by a tdd-UL- DL-ConfigurationCommon or by a tdd-UL-DL-ConfigurationDedicated and / or a SBFD- Configuration Common.

[0547] The wireless device may receive a higher layer configured PDCCH, PDSCH or CSI-RS or a reception scheduled by a DCI format on a symbol on the first cell, if the symbol on the first cell is indicated as downlink by a tdd-UL-DL-ConfigurationCommon or by a tdd-U L-DL-ConfigurationDedicated and the symbol on the reference cell is a SBFD symbol by a SBFD-ConfigurationCommon.

[0548] The wireless device may not be required to transmit a higher layer configured PUCCH, PUSCH, SRS or PRACH on a symbol on the first cell, if the symbol on the reference cell is indicated as downlink by a tdd-UL-DL-ConfigurationCommon or by a tdd-UL-DL-ConfigurationDedicated and the symbol on the first cell is a SBFD symbol by a SBFD-ConfigurationCommon.

[0549] FIGs. 34A and 34B illustrate a similar configuration to FIG. 26C. In the example, the symbol #i on the reference cell is a semi-D symbol, and the wireless device may receive an uplink grant scheduling a transmission via / during the symbol #i on / via the first cell.

[0550] In the example of FIG. 34A, the symbol #i on the first cell is a SBFD symbol. The wireless device may consider this case as a normal case. The wireless device may transmit the transmission during the symbol #i on the first cell in the case of FIG. 34A. The wireless device may skip receiving downlink signals (e.g., PDCCH, PDSCH, or CSI-RS), configured by one or more RRC signaling, during the symbol #i on the reference cell in case of the FIG. 34A.

[0551] In an example, the wireless device may not be expected / required to be configured with downlink signals corresponding to CORESET#0 or SSB during / via the symbol #i on the reference cell in case of FIG. 34A. In an example, a bs may not schedule the uplink grant during the symbol #i when the base station schedules / configures CORESET#0 or SSB via the reference cell during the symbol #i.

[0552] For example, the wireless device may not be required to receive the UL grant for the first cell, when downlink signals corresponding to CORESET#0 or SSB during / via the symbol #i on the reference cell are configured.Docket No.: 24-1171 PCT

[0553] FIG. 34B illustrates a similar case to FIG. 34A except that the symbol #i on the reference cell is a SBFD symbol. In an example, the wireless device may transmit the transmission during the symbol #i on the first cell in the case of FIG. 34B. In another example, the wireless device may consider the case as an error case. The wireless device may not be expected to be configured with one or more of error cases. The base station may not configure / schedule any error case to the wireless device.

[0554] In an example, the wireless device may determine a link direction during the symbol #i on the reference cell as uplink in case of FIG. 34D.

[0555] In an example, in response to determining a link direction for a SBFD symbol on a cell as uplink, a first wireless device may transmit an UL signal during the SBFD symbol for the cell, if scheduled or configured. The wireless device may skip receiving a downlink signal, if scheduled or configured during the SBFD symbol on the cell. In an example, in response to determining a link direction for a SBFD symbol on a cell as downlink, a first wireless device may receive a DL signal during the SBFD symbol for the cell, if scheduled or configured. The wireless device may skip transmitting an uplink signal, if scheduled or configured during the SBFD symbol on the cell.

[0556] In an example, if the first cell configured with a directionalHandlingCollision operates in the same frequency band as the reference cell, the wireless device may transmit a signal / channel scheduled by a DCI format on a symbol of the first cell when the symbol is indicated as a SBFD symbol on the first cell by a SBFD-ConfigurationCommon and the symbol is indicated as downlink by a tdd-UL-DL- ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated on the reference cell.

[0557] In an example, if the first cell configured with a directionalHandlingCollision operates in the same frequency band as the reference cell, the wireless device may transmit a signal / channel scheduled by a DCI format on a symbol of the first cell when the symbol is indicated as downlink by a tdd-UL-DL- ConfigurationCommon or tdd-UL-DL-Configuration Dedicated on the reference cell and a SBFD symbol by a SBFD-ConfigurationCommon on the reference cell.

[0558] In an example, the reference cell and first cells among a plurality of cells configured with directional collision handling operate in different frequency bands or the symbol on the reference cell is a SBFD symbol or the symbol on the first cell is a SBFD symbol, the wireless device may transmit a signal / channel scheduled by a DCI format on a symbol of the first cell when the symbol is indicated as downlink by a tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated on the reference cell.

[0559] FIG. 34C / 34D illustrates a similar configuration to FIG. 26D. In the example, the symbol #i on the reference cell is a conf-D symbol, and the wireless device may receive an uplink grant scheduling a transmission via / during the symbol #i on / via the first cell.

[0560] In the example of FIG. 34C, the symbol #i on the first cell is a SBFD symbol.Docket No.: 24-1171 PCT

[0561] In an embodiment, the wireless device may consider this case as a normal case. The wireless device may transmit the transmission during the symbol #i on the first cell in the case of FIG. 34C. The wireless device may skip / drop the reception of the one or more downlink signals during the symbol #i via the reference cell.

[0562] In an embodiment, the wireless device may not be expected to be configured with downlink signals corresponding to CORESET#0 or SSB during / via the symbol #i on the reference cell in case of FIG. 34C. The base station may not schedule the uplink transmission via the first cell that overlaps with a CORESET#0 or SSB of the reference cell in time. For example, the wireless device may not expect to (be not required to handle the case where the wireless device) receive the UL grant for the first cell, when downlink signals corresponding to CORESET#0 or SSB during / via the symbol #i on the reference cell are configured.

[0563] In an embodiment, the wireless device may drop the transmission during the symbol #i on the first cell, in response to the one or more downlink signals corresponding to a CORESET#0 (e.g., a PDCCH monitoring occasion of a CORESET#0 and / or a CORESET#1 ) or a SSB (e.g., a cell defining SSB).

[0564] In an embodiment, the wireless device may consider this case as an error case. The wireless device may not be required to handle a case corresponding to receive the UL grant for the first cell, when the symbol #i on the reference cell is a conf-D symbol.

[0565] FIG. 34D illustrates a similar case to FIG. 34C except that the symbol #i on the reference cell is a SBFD symbol and the symbol #i on the first cell is any type of symbol. ‘S / D’ on FIG. 34C may refer that the symbol #i on reference cell is a SBFD symbol and the wireless device receives the one or more RRC messages and thus the symbol # is also the conf-D symbol.

[0566] In an embodiment, the wireless device may consider this case as a normal case. The wireless device may (determine to) transmit the transmission during the symbol #i on the first cell in the case of FIG. 34C. The wireless device may skip / drop the reception of the one or more downlink signals via the symbol #i on the reference cell. Similar to FIG. 34B, the wireless device may determine a link direction of the reference cell as uplink in response to transmitting the transmission (or determining to transmit).

[0567] In an embodiment, the wireless device may not be required to handle a case to (or not be required to handle a case where the wireless device) be configured with downlink signals corresponding to CORESET#0 or SSB during / via the symbol #i on the reference cell in case of FIG. 34C. For example, the wireless device may not be required to handle a case to receive the UL grant for the first cell, when downlink signals corresponding to CORESET 0 or SSB during / via the symbol #i on the reference cell are configured.

[0568] In an embodiment, the wireless device may drop the transmission during the symbol #i on the first in response to the one or more downlink signals corresponding to a CORESET#0 (e.g., a PDCCH monitoring occasion of a CORESET#0 and / or a CORESET#1) or a SSB (e.g., a cell defining SSB).Docket No.: 24-1171 PCT

[0569] In an embodiment, the wireless device may consider this case as an error case. The wireless device may not be required to handle a case to receive the UL grant for the first cell, when the symbol #i on the reference cell is a conf-D symbol.

[0570] In an example, if the first cell configured with a directionalHandlingCollision operates in the same frequency band as the reference cell, the wireless device may not be required to receive a higher layer configured PDCCH, PDSCH, or CSI-RS on a set of SBFD symbols on the reference cell in a set of symbols, if the wireless device detects / receives a DCI format scheduling a transmission on one or more symbols in the set of symbols on the first cell and the one or more symbols are SBFD symbol(s) of the first cell.

[0571] In an example, if the first cell configured with a directionalHandlingCollision operates in the same frequency band as the reference cell, the wireless device may transmit a signal / channel scheduled by a DCI format on a symbol of the first cell when the symbol is indicated as downlink by a tdd-UL-DL- ConfigurationCommon or tdd-UL-DL-Configuration Dedicated on the reference cell and a SBFD symbol by a SBFD-ConfigurationCommon on the reference cell.

[0572] In an example, the reference cell and first cells among a plurality of cells configured with directional collision handling operate in different frequency bands or the symbol on the reference cell is a SBFD symbol or the symbol on the first cell is a SBFD symbol, may not be required to receive a higher layer configured PDCCH, PDSCH, or CSI-RS on a set of SBFD symbols on the reference cell in a set of symbols, if the wireless device detects / receives a DCI format scheduling a transmission on one or more symbols in the set of symbols on the first cell and the one or more symbols are SBFD symbol(s) of the first cell.

[0573] In an example, in response to the symbol on the first cell being a SBFD symbol, the wireless device may perform a directional collision handling between the reference cell and the first cell based on an inter-band case (e.g., FIG. 27A-D) regardless of whether the first cell and the reference cell operates in a same frequency band or different frequency bands.

[0574] In an example, the reference cell and the first cell may operate in different frequency bands. FIGs. 35 - 37 discuss example embodiments for the case where the reference cell and the first cell operate in the different frequency bands (e.g., inter-band CA)

[0575] FIGs. 35A and 35B illustrate a similar configuration to FIG. 27A. The symbol #i on the reference cell is indicated as a semi-U symbol and the symbol #i on the first cell is indicated as a semi-D symbol respectively.

[0576] In the example of FIG. 35A, the symbol #i on the first cell is a SBFD symbol.

[0577] In an embodiment, the wireless device may consider this case as a normal case. The wireless device may transmit one or more UL signals, if scheduled or configured, during the symbol #i on the firstDocket No.: 24-1171 PCT cell in the case of FIG. 35A based on the reference cell. The wireless device may determine a link direction for the symbol #i on the first cell as uplink (e.g., UL link direction) based on the reference cell.

[0578] In an embodiment, the wireless device may not be required to handle a case to be configured with downlink signals on the symbol #i for the first cell in case of FIG. 35A. For example, the wireless device may not be required to handle a case to be configured with a downlink resource or a downlink signal corresponding to (e.g., a PDCCH monitoring occasion of a CORESET#0 and / or a CORESET#1 ) or a SSB (e.g., a cell defining SSB) during / via the symbol #i on the first cell in case of FIG. 35A. The base station may not configure downlink resource during the symbol #i in response to / based on the symbol #i on the reference cell being the uplink symbol.

[0579] In an embodiment, the wireless device may consider this case as an error case.

[0580] FIG. 35B illustrates a similar case to FIG. 35A except that the symbol #i on the reference cell is a SBFD symbol and the symbol #i on the first cell is a semi-D symbol.

[0581] In an embodiment, the wireless device may consider this case as an error case. The. wireless device may not be required to handle a case to be indicated as a SBFD symbol on a semi-U symbol for a cell regardless of intra-band / inter-band CA or a single serving cell scenario.

[0582] FIG. 35C and 35D illustrates a similar configuration to FIG. 27B. The symbol #i on the reference cell is indicated as a semi-D symbol and the symbol #i on the first cell is indicated as a semi-U symbol respectively.

[0583] In the example of FIG. 35C, the symbol #i on the first cell is a SBFD symbol.

[0584] In an embodiment, the wireless device may consider this case as an error case. The. wireless device may not be required to handle a case to be indicated as a SBFD symbol on a semi-U symbol for a cell regardless of intra-band / inter-band CA or a single serving cell scenario.

[0585] Behavior of a wireless device in handling an error case is up to implementation. The wireless device may not communicate with a base station in response to an error case during a symbol where the error case occurs.

[0586] FIG. 35D illustrates a similar case to FIG. 35C except that the symbol #i on the reference cell is a SBFD symbol and the symbol #i on the first cell is a semi-U symbol.

[0587] In an embodiment, the wireless device may consider this case as a normal case. The wireless device may transmit one or more UL signals, if scheduled or configured, during the symbol #i on the reference cell in the case of FIG. 35A based on the reference cell. The wireless device may determine a link direction for the symbol #i on the reference cell as uplink (e.g., UL link direction) based on the first cell being configured with a semi-U symbol.

[0588] In an embodiment, the wireless device may not be required to handle a case to be configured with downlink signals on the symbol #i for the reference cell in case of FIG. 35D. For example, the wireless device may not be required to handle a case to be configured with a downlink resource or a downlink signalDocket No.: 24-1171 PCT corresponding to (e.g., a PDCCH monitoring occasion of a CORESET#0 and / or a CORESET#1) or a SSB (e.g ., a cell defining SSB) during / via the symbol #i on the reference cell in case of FIG. 35D.

[0589] In an embodiment, the wireless device may consider this case as an error case.

[0590] FIGs. 36A and 36B illustrate a similar configuration to FIG. 27C. In the example, the symbol #i on the reference cell is a semi-D symbol, and the wireless device may receive an uplink grant scheduling a transmission via / during the symbol #i on / via the first cell.

[0591] In the example of FIG. 36A, the symbol #i on the first cell is a SBFD symbol. The wireless device may consider this case as a normal case. The wireless device may transmit the transmission during the symbol #i on the first cell in the case of FIG. 36A. The w...

Claims

Docket No.: 24-1171 PCTCLAIMS1. A method comprising: receiving, by a wireless device, one or more radio resource control (RRC) messages indicating: that a first cell is configured with a directional collision based on a reference cell; an uplink signal that is via a symbol on the first cell; and a downlink resource, of a second cell, on the symbol, wherein: the first cell and the second cell are configured to operate in a same frequency band; and the second cell is the reference cell for the symbol; in response to the symbol being indicated as a subband full duplex (SBFD) symbol on the first cell, determining to transmit the uplink signal; and based on the determining, during the symbol, transmitting the uplink signal via the first cell.

2. A method comprising: receiving, by a wireless device, one or more first messages indicating: an uplink signal that is via a symbol on a first cell; and a downlink resource, of a second cell, on the symbol, wherein the first cell and the second cell are configured to operate in a same frequency band; and based on the symbol being indicated as a subband full duplex (SBFD) symbol on the first cell, transmitting the uplink signal via the first cell.

3. The method of claim 2, wherein the one or more first messages comprise one or more radio resource control (RRC) messages.

4. The method of claim 3, wherein the one or more RRC messages further indicate that the first cell is configured with a directional collision based on a reference cell.

5. The method of any one of claims 2-4, wherein the second cell is the reference cell for the symbol.

6. The method of any one of claims 2-5, comprising determining to transmit the uplink signal, in response to the symbol being indicated as the SBFD symbol on the first cell, wherein the uplink signal is transmitted via the first cell based on the determining.

7. The method of any one of claims 2-6, wherein the uplink signal is transmitted during the symbol.

8. The method of any one of claims 2-7, further comprising skipping receiving downlink data via the downlink resource of the second cell during the symbol.

9. The method of claim 8, wherein the skipping is based on: the transmitting the uplink signal; or the first cell being configured with the direction collision handling based on the reference cell.Docket No.: 24-1171 PCT10. The method of any one of claims 2-9, further comprising receiving one or more second messages indicating: a second uplink signal that is via a second symbol on the first cell; and a second downlink resource, of the second cell, on the second symbol.11 . The method of claim 10, further comprising dropping the second uplink signal in response to the second symbol not being indicated as an SBFD symbol on the first cell.

12. The method of claim 10 or 1 1 , further comprising receiving downlink data via the second downlink resource during the second symbol.

13. The method of any one of claims 2-12, wherein: the one or more first messages further comprise one or more SBFD configuration parameters; and the one or more SBFD configuration parameters indicate: one or more time domain resources indicating a plurality of SBFD symbols of the first cell; one or more downlink (DL) subbands applied on the plurality of SBFD symbols; and an uplink (UL) subband applied on the plurality of SBFD symbols of the first cell.

14. The method of claim 13, wherein the symbol is indicated as the SBFD symbol, in response to the symbol overlapping, in time, with the plurality of SBFD symbols of the first cell.

15. The method of any one of claims 2-14, wherein the one or more first messages further indicate an enablement of a directional collision handling based on the reference cell for the second cell.

16. The method of any one of claims 2-15, wherein: the uplink signal is transmitted further based on the one or more first messages comprising a downlink control information (DCI) scheduling the uplink signal; and the symbol on the second cell is a downlink symbol.

17. The method of any one of claims 2-16, wherein the uplink signal is at least one of a physical uplink control channel (PUCCH), a physical uplink shared channel (PUSCH), a physical random access channel (PRACH), or a sounding reference signal (SRS).

18. The method of any one of claims 8-17, wherein the downlink data is at least one of a channel state information reference signal (CSI-RS), a physical downlink control channel (PDCCH), or a physical downlink data channel (PDSCH).

19. The method of any one of claims 2-18, wherein a cell index of the second cell is smaller than a cell index of the first cell.

20. A method comprising: receiving, by a wireless device, one or more radio resource control (RRC) messages indicating that a first cell, of a plurality of cells, is configured with a directional collision; receiving one or more messages indicating, for a symbol:Docket No.: 24-1171 PCT an uplink resource of the first cell; and a downlink resource of a second cell of the plurality of cells; determining whether to transmit an uplink signal via the uplink resource, based on the symbol overlapping with a subband full duplex (SBFD) symbol of the second cell; and based on the determining, transmitting or dropping the uplink signal during the symbol.21 . A method comprising transmitting or dropping, by a wireless device, an uplink signal that is via an uplink resource of a first cell and that is during a symbol, based on whether the symbol overlaps with a subband full duplex (SBFD) symbol of a second cell.

22. The method of claim 21 , comprising receiving, by the wireless device, one or more first messages indicating that the first cell, of a plurality of cells, is configured with a directional collision.

23. The method of claim 21 or 22, comprising receiving one or more second messages indicating, for the symbol: the uplink resource of the first cell; and a downlink resource of the second cell of the plurality of cells.

24. The method of any one of claims 21-23, comprising determining whether to transmit the uplink signal via the uplink resource, based on the symbol overlapping with the SBFD symbol of the second cell, wherein the uplink signal is either transmitted or dropped, based on the determining.

25. The method of claim 24, wherein the determining is further based on the symbol overlapping with a first SBFD symbol of the first cell.

26. The method of claim 25, wherein the determining comprises determining not to transmit the uplink signal, based on the symbol not overlapping with the SBFD symbol of the second cell.

27. The method of claim 25, wherein the determining comprises determining not to transmit the uplink signal, based on: the symbol overlapping with the SBFD symbol of the second cell; receiving a downlink control information (DCI) scheduling a downlink signal via the downlink resource of the second cell; and the uplink signal being configured by the one or more first messages.

28. The method of claim 25, wherein the determining comprises determining to transmit the uplink signal, based on the symbol overlapping with the SBFD symbol of the second cell.

29. The method of claim 28, wherein the determining to transmit the uplink signal is further based on receiving a second DCI scheduling the uplink signal that is via the uplink resource of the first cell.

30. The method of any one of claims 28 and 29, wherein the determining to transmit the uplink signal is further based on: the second cell being enabled with an SBFD operation; andDocket No.: 24-1171 PCT the downlink resource, of the second cell, overlapping with a second SBFD symbol of the second cell.

31. The method of any one of claims 21-30, wherein the first cell is a reference cell of the plurality of cells.

32. The method of any one of claims 22-31 , further comprising transmitting on the symbol via one or more cells of the plurality of cells.

33. The method of any one of claims 21-30, wherein the second cell is a reference cell of the plurality of cells.

34. The method of any one of claims 22-33, further comprising receiving on the symbol via one or more cells of the plurality of cells.

35. An apparatus comprising: one or more processors; and memory storing instructions that, when executed by the one or more processors, cause the wireless device to perform the method of any one of claims 1-34.

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

Images